What is engineering document numbering?
Engineering document numbering is the rule that turns facts about a document into one unique identifier. Each field of the number answers a question: which project the document belongs to, which part of the plant it covers, which discipline produced it, what kind of document it is and where it sits in its series.
A good document number does three jobs. It identifies the document without ambiguity, even when two disciplines produce documents with the same title. It sorts the archive, because similar documents line up in any listing. And it links the controls: the master document register, the transmittal, the drawing title block and the EDMS record all use the same number.
Numbering is the first decision in engineering document management. It must exist before the first drawing and is written into a numbering procedure, which belongs to the project’s engineering document control plan.
Which fields make up an engineering document number?
There is no universal numbering system. Every owner defines its own. Even so, engineering procedures tend to use the same building blocks, ordered from general to specific:
| Field | What it identifies | Example value | Note |
|---|---|---|---|
| Project or facility | The project, plant or contract | P123 | Set by the owner and shared by every company on the project |
| Area or unit | The physical or functional part of the plant | U200, utilities unit | Taken from the project’s area list |
| Discipline | Who produced the technical content | ME for mechanical, EL for electrical | Closed list, one or two letters |
| Document type | The nature of the document | DE for drawing, ET for technical specification, FD for datasheet | Closed list with a definition per type |
| Sequence number | Order within the series | 0012 | No meaning of its own, only to distinguish |
| Sheet | One page of a multi-sheet document | 02/05 | Usually outside the number, in the title block |
| Revision | The document’s state | B or 1 | Outside the number, as an attribute |
Putting the fields together, mechanical drawing number 12 for the utilities unit of project P123 would read as follows, in a fictitious example:
P123-U200-ME-DE-0012, sheet 02, revision B.
Sheet and revision sit next to the number, not inside it. If the revision were part of the number, every new revision would create a “new document” in the register and the history would be lost.
How does Petrobras standard N-1710 structure the number?
N-1710, “Codificação de Documentos Técnicos de Engenharia”, meaning coding of engineering technical documents, is Petrobras’ technical standard on this subject and the reference most suppliers to Brazilian oil and gas meet first. The revision reviewed for this guide is Rev. N, April 2020, published on Petrobras’ supplier portal. It applies to engineering documents for the company’s facilities across design, construction, assembly, commissioning, operation, inspection, maintenance and decommissioning, and suppliers must use it under the conditions of their contracts.
The N-1710 “coded number” has seven basic groups, ordered from general to specific and separated by hyphens:
| Group | N-1710 name, translated | Format | What it identifies |
|---|---|---|---|
| 0 | Language | A | Only for documents not in Portuguese, for example I for English |
| 1 | Document category per annex A | BB | Two letters, for example DE drawing, MA manual, RM material requisition |
| 2 | Facility per annex B | CDDD.EE | Business area, facility and a geographic differentiation code |
| 3 | Activity area per annex C or E | FGGGG | Unit, system or building; F distinguishes repeated units |
| 4 | Service, material and equipment class per annex D or F | HHH | Discipline, equipment or service, for example 200 piping |
| 5 | Document origin | III | Who issued it: a Petrobras unit or a contractor |
| 6 | Sequence | JJJ | Numeric order within the same combination of groups |
The standard includes full examples. One is DE-5285.00-22212-550-PPC-001: category DE, for drawing; facility 5285.00, the REVAP refinery; activity area 22212, the second delayed coking unit; class 550, for towers; origin PPC, which is CENPES; and sequence 001. Another, I-FD-3010.95-1220-451-PEP-002, shows group 0 in use: the I marks a datasheet issued in English.
Three points in N-1710 often cause confusion:
- Codes come from the annexes. The standard states that the structure must not be used as if it were N-1710 without correctly applying the annexes.
- The revision is not in the number. N-1710 covers the coded number and lists N-2064, “Emissão e Revisão de Documentos de Projeto”, on the issue and revision of design documents, as a normative reference.
- Transfers restart the revision. When equipment or systems move between facilities, the latest revision of the affected documents must be issued as revision 0, the original issue, with the destination facility’s code.
For international EPCs and vendors entering Brazilian oil and gas, N-1710 is a prerequisite for delivering documents to Petrobras.
How does ISO 19650 identify documents?
ISO 19650 covers information management using BIM for buildings and civil engineering works. Part 2, on the delivery phase of assets, calls each file an “information container”. The UK BIM Framework guidance summarises what the common data environment (CDE) must ensure: each container has a unique ID based on an agreed and documented convention made of fields separated by a delimiter, and each field takes a value from an agreed codification.
The UK National Annex is the most cited reference for those fields. In its 2021 version the seven fields are:
| Field | UK National Annex name, 2021 | What it identifies |
|---|---|---|
| 1 | Project | Unique project code used by the whole team |
| 2 | Originator | The organisation that actually produced the content |
| 3 | Functional breakdown, formerly “volume/system” | System, zone or functional package |
| 4 | Spatial breakdown, formerly “level/location” | Level, section, chainage or location |
| 5 | Form | How the information is presented: M model, D drawing, T text, I image |
| 6 | Discipline | The discipline the container relates to |
| 7 | Number | Sequence that makes the ID unique |
The 2021 annex removed the recommended field lengths and replaced the old “type” field with the “form” of presentation, which is why older material using codes like DR for drawing and M3 for 3D model is still in circulation. The National Annex guidance published by the Centre for Digital Built Britain shows a complete ID as one string: 123456-ORG-A1-ZZ-MO-A-0001. The values ZZ, for all, and XX, for none, cover fields that do not apply.
One difference matters for people coming from process industries: under ISO 19650, status and revision are metadata, not part of the name. The same guidance recommends prefixed two-digit revisions, such as P01 for preliminary and C01 for contractual versions. The revision control guide compares this convention with the letter-then-number practice common in Brazilian engineering.
How to build your project’s numbering table
- List the planned documents. Start from the contract’s document list. It shows which types and disciplines the number must cover.
- Choose the fields and their order. From general to specific. Fewer fields are easier to use; each field needs a search or control reason to exist.
- Close the value lists. Every field gets a list of allowed values with descriptions. Free text produces variants like
MEC,MEandMECH. - Set length and separator. Fixed-length fields sort well in spreadsheets; a hyphen separator makes numbers easy to read.
- Decide what stays outside the number. Sheet, revision, status and vendor number are usually attributes.
- Publish and control the procedure. The numbering procedure is itself a controlled document with its own revision.
- Configure the EDMS. Fields become attributes with value lists, and the system builds the number or validates what users type.
Document numbering template
Copy this structure into your procedure or supporting spreadsheet:
| Position | Field | Characters | Allowed values | Example | List owner |
|---|---|---|---|---|---|
| 1 | Project | 4 | Contract list | P123 | Owner’s document control |
| 2 | Area or unit | 4 | Project area list | U200 | Process engineering |
| 3 | Discipline | 2 | Discipline list | ME | Engineering management |
| 4 | Document type | 2 | Type list with definitions | DE | Document control |
| 5 | Sequence | 4 | 0001 to 9999 | 0012 | Generated by the EDMS or the register |
| Attribute | Sheet | free | 01/05 | 02/05 | Document author |
| Attribute | Revision | 1 to 2 | Per revision procedure | B | Document control |
What are the most common numbering mistakes?
- Giving the sequence number a meaning. If 0100 “means” something, the series runs out before the project ends.
- Putting the revision in both the file name and the number. The result is copies with different names for the same document.
- Reusing numbers. A cancelled document keeps its number; the number never goes back into the pool.
- Using letters that look like digits. N-1710 excludes the letters I and O in some fields precisely to avoid confusion with 1 and 0.
- Renumbering vendor documents without keeping the original. Traceability to the manufacturer is lost.
- Changing the rule mid-project without a cross-reference table. Old and new documents stop finding each other in search.
Document numbering and EDMS migration
The document number is the most important metadata in an engineering archive. In a migration between platforms, such as Meridian to ProjectWise or to Greendocs, every field of the number needs a defined target in the new system. Non-compliant numbers tend to surface exactly at that point.
In 29docs’ EDMS migration pipeline, metadata is extracted from the source, normalised and validated document by document against quality rules before loading. Only batches that meet the agreed quality thresholds go to the target, and comparison reports show what changed between source and target. This is the kind of organising and standardisation work 29docs did for Petrobras when it consolidated the engineering of three fertilizer plants into a single Accruent Meridian environment, described in the fertilizer case.
Updated on .