COBie 2.4 · Operations guide
Job
Defines preventive, corrective, safety, and operational tasks for maintainable assets.
Can the owner turn delivered task information into an actionable maintenance plan?
Turn handover data into actionable work
The Job worksheet defines work needed to operate, inspect, adjust, calibrate, test, maintain, start, shut down, or troubleshoot a product Type. Annex A's spreadsheet schema marks Name, TypeName, and TaskNumber as compound-key fields and requires TaskNumber to be unique for each Name and TypeName. Its embedded COBieLite definition describes the key as Name and TypeName, so the contract-issued workbook and validator should control the exact uniqueness rule.
A useful Job should be suitable for conversion into a maintenance template, not merely repeat a manual title. Category, Status, Description, Duration, start offset, and frequency establish what the work is, how long it takes, when it first becomes due, and how often it repeats. Every numeric schedule value must be read with its associated unit.
Describe procedures, sequence, and resources
Job.Description can summarize a task that is fully explained in a linked Document, contain a complete set of steps, or describe one step in a multi-row procedure. TaskNumber and Priors support the last approach by making order and dependency explicit. Teams should choose one convention and apply it consistently so the receiver can interpret the rows without guesswork.
ResourceNames connects the task to required labor, tools, materials, and training. The list should be reconciled with safety requirements, manufacturer instructions, commissioning procedures, and owner maintenance policy. A technically valid interval is not enough if the task omits the resources or predecessor steps needed to perform it safely.
Maintain task data alongside Revit assets
Most Job content comes from O&M manuals, maintenance standards, commissioning plans, and manufacturer recommendations, not directly from Revit. The model provides the Type identity that determines which installed Components inherit the task, while the operational procedure remains curated project information.
BIMRelay keeps Job rows associated with active Type records, preserves user-approved task content through model regeneration, and validates referenced Resources. Teams can review the affected model-backed products without pretending that a Revit parameter is the authoritative source for maintenance frequency or procedure.
Key relationships
References a Type through Job.TypeName
May require Resources
May define predecessor tasks
Practical quality checks
- Use consistent duration units
- Validate task sequence
- Confirm intervals with the owner
Job worksheet FAQ
- What is the COBie Job worksheet?
- Job contains preventive, corrective, operational, safety, startup, shutdown, inspection, testing, and troubleshooting tasks associated with a COBie Type.
- Does a COBie Job apply to a Type or a Component?
- The standard Job.TypeName field references a Type. The task can then be applied to the installed Components that belong to that Type in the receiving maintenance system.
- How are multi-step COBie Jobs represented?
- TaskNumber can identify individual steps and Priors can identify predecessor step numbers. Projects should use a consistent convention and link detailed procedures when needed.
- How does BIMRelay manage Job data during regeneration?
- BIMRelay preserves project-managed Job content, rechecks its Type and Resource references, and refreshes the related Revit-derived asset evidence without overwriting approved task values.
This is an independent practical summary, not a reproduction of the COBie specification. Refer to the official standard for normative definitions and field requirements.
Reviewed against the official NIBS COBie 2.4 publication and Annex A worksheet schemas.
Where the official documents, contract-issued workbook, and project validator differ, follow the contract requirements and accepted validation process.
Open the official COBie 2.4 publicationOpen the official COBie 2.4 Annex A worksheet schemas