Controlled technical documents

Documents as part of the scope

Documents are part of what is supplied. A unit without its drawings, manual and records is harder to install, operate and service. Invitrona states in each proposal which documents the scope includes, and treats them with the same control as the equipment.

Typical document set

The documents supplied depend on the product and the agreed scope. A typical set may include:

• Technical proposal: the requirement basis, proposed configuration, assumptions and departures
• Datasheet: class or configuration specification with conditions stated
• Drawings: general arrangement and, where agreed, wiring or terminal details
• Test plan and inspection records: as agreed for the configuration
• Installation and operating manual: preparation, safe operation and routine care
• Commissioning record: settings, measurements and observations at commissioning, where commissioning is in scope

Identification

Each controlled document carries an identity, a revision, a date and a status. A proposal or drawing that changes is re-issued at a new revision, and the change is described. Documents that refer to each other cite the revision they refer to.

Approval before manufacture

Where a project requires drawings or documents to be approved before manufacture, the approval steps are listed in the order and planned into the programme. Manufacture proceeds on the approved revision.

Keeping documents with the equipment

At handover, the documents for the supplied scope are provided for the equipment owner. Keeping them with the equipment, or in the owner's asset records, means the facts are available when the unit is serviced or extended. For multi-site programmes, documents use the same site and unit identifiers as the equipment records.

Public downloads

Datasheets published on this website describe product classes with typical values. They are a starting point for selection. The configuration-specific documents in a proposal take precedence for a supplied unit.

Language and format

Projects often have their own document conventions: a numbering system, a title-block template, a submission format or a required language. Where a project needs documents in a particular form, state the requirement in the enquiry so that it can be planned and priced with the rest of the scope, rather than added after the order.

Questions you can ask

• Which documents are included in the scope, and at which stage are they issued?
• Which documents need my approval before manufacture?
• How will I know that a document I hold has been superseded?

What this means for a buyer

You can ask before ordering which documents are included and in what form. When you receive a document, its revision tells you whether it is current. If two documents disagree, the controlled source decides; see controlled product data.