- Coordination checklist
- Every deferred requirement across a project's standards, in one list. An item is checked off by hand, or resolves on its own once a value is specified.
- Datasheet
- The fields of a standard that take a value: the equipment and material choices for one scope of work. In a project, a datasheet is the filled-in record of those values.
- Datasheet for a scope of work
- One standard can have several datasheets in a project, each for its own scope (indoor panelboards and outdoor panelboards, supply fans and exhaust fans). Each has its own values and its own history.
- Deferred requirement
- A field whose value is left to the drawings or to the project engineer instead of being fixed in the specification ("As indicated on the drawings"). Deferred requirements are listed, so a decision still owed is not read as complete.
- Derived value
- A datasheet field whose value follows from inputs already specified: a basic impulse level that follows from the system voltage and the site altitude, for example. The field names the basis, so whoever computes it arrives at the same answer. Different from a value deferred to the drawings, which another document carries.
- Drawing reference
- A mark on a datasheet field whose value is usually shown on the drawings rather than in the specification. It labels the field as deferred and puts the requirement on the project's coordination checklist.
- Project parameter
- A fact about the project (site altitude, seismic design category) answered once and used by every standard that refers to it, instead of being asked again in each datasheet. Where a standard refers to it, the answer is substituted. Unanswered, it shows as TBD.
- Reconcile
- Bring a datasheet to the revision of the standard its project now follows. Values that still fit carry forward. A removed option, a changed field or a value that no longer fits needs your decision before the change applies.
- Requirement (clause)
- One requirement in a specification, usually a single statement with "shall", "should" or "may". Each is a numbered clause (1.4.2, for example) so it can be cited exactly.
- Section
- A heading in a standard that groups related content (Scope, Products, Installation). Sections appear in the table of contents. They are not the numbered requirement clauses.
- Specification
- The written clauses of a standard. In a project, a specification is the project's copy of those clauses, tailored to the job with its own requirements and comments. It is also the construction-industry word for this kind of document.
- Standard
- The master for one subject: the specification clauses and the datasheet fields that go with them. A standard has its own revisions. Projects take their specifications and datasheets from it.
- Standards markup
- The syntax a standard is written in. It turns a plain text file into a configurable specification by marking which lines are sections, which are requirement clauses, and which datasheet fields take a value. The Standards markup syntax guide has the full reference.