bds:Process
typeOperationscoreA repeatable way the business gets a piece of work done, such as "Monthly invoicing" or "New-hire onboarding". A Process has an schema:owner, a cadence or trigger, steps (via schema:step), the Tools it usesTool, the Policy it is governedBy, and the Metrics it is measuredBy. Because it is a schema:HowTo, the same record can be published as a readable procedure.
Subclass of schema:HowTo · inherits 280 schema.org properties from HowTo and above
Properties
Declared by BDS on this type. Everything else is inherited from schema.org.
| Property | Expected type | Description |
|---|---|---|
| bds:businessUnit | schema:Organization, bds:BusinessUnit | The unit or organization this item belongs to. |
| bds:cadence | bds:Cadence | How often the item repeats: how often a Process runs, a Metric is read, a Tool is billed, or a ComplianceRequirement comes due. For exact recurrence use schema:eventSchedule or a schema:Schedule. |
| bds:cost | schema:MonetaryAmount | What the item costs. For a recurring charge, give the amount per billing period and set cadence to the period. |
| bds:governedBy | bds:Policy | A policy or rule this item must follow. |
| bds:input | schema:Text, schema:Thing | Something the process needs before it can run. |
| bds:lifecycleStatus | bds:LifecycleStatus | Where the item is in its life: draft, active, on hold, completed, cancelled, archived or superseded. For a Task use schema:actionStatus instead; for a Deal use dealStatus. |
| bds:measuredBy | bds:Metric | A metric that tells whether this item is working. |
| bds:output | schema:Text, schema:Thing | Something the process produces when it runs. |
| bds:reviewDate | schema:Date | When the item should next be reviewed to confirm it is still right. |
| bds:supersedes | bds:Agreement, bds:Decision, bds:Policy, bds:Process | An earlier item of the same kind that this one replaces. The earlier item should carry SupersededStatus or DecisionSuperseded. |
| bds:trigger | schema:Text | What starts the process, in words: an event ("a customer signs up"), a condition, or a schedule. Pair with cadence when it is time-based. |
| bds:usesTool | bds:Tool | A tool the process depends on. |
Widened onto it
schema.org properties declared usable on this type. Reuse these before proposing a new one.
Subtypes
References
Where this term shows up elsewhere in the vocabulary.
- Referenced as expected type by
- bds:affects, bds:appliesTo, bds:enforcedBy, bds:measures, bds:mitigation, bds:supersedes, bds:supportsProcess
- Properties declared on it
- bds:businessUnit, bds:cadence, bds:cost, bds:governedBy, bds:input, bds:lifecycleStatus, bds:measuredBy, bds:output, bds:reviewDate, bds:supersedes, bds:trigger, bds:usesTool