Cheat sheet
Document control in a CDE (UK)
Every rule of the course on one page: how each figure is built, the mistake people usually make, and where it comes up at work. Print it or keep it open while you work.
- Rule
- On the register is not the same as authorised. Read the state and the code before anyone cuts, orders or builds.
- How it is built
- Steel at risk = Steel on S-2101 P02 + Steel on S-2103 P01
- Usual mistake
- Only the drawings on the register counted. S-2103 came by e-mail and is not authorised either.
- At work
- A document controller checks every cutting list, order and method statement against the register before it is released.
- Rule
- Authorise, then transmit. The register says what may be built; the transmittal proves who got it and when.
- How it is built
- Working days = Days 26 Mar to 2 Apr − Weekend − Bank holidays
- Usual mistake
- Good Friday and Easter Monday counted as working days. Both are bank holidays.
- At work
- The controller publishes the construction revision, issues it by transmittal the same day and flags any tight lead time.
- Rule
- A superseded drawing is only dead when nobody holds it. Send the new revision to every holder of the old one.
- How it is built
- Still on P02 = P02 holders − Sent C01 in task 2
- Usual mistake
- The originator counted. The engineer wrote C01; they are not on P02.
- At work
- Each new revision goes out against the old distribution list, and the controller records who has the current one.
- Rule
- A name is data. Check it field by field; return a bad one to its originator instead of fixing it quietly.
- How it is built
- Returned = Names submitted − Names that pass
- Usual mistake
- One fault missed. Check every field: one name breaks the level, another the type.
- At work
- Submissions are checked against the information standard on arrival; failures go back to the originator with the field named.