Project Procedures for implementing TDOC
Project Procedures
In order to implement TDOC to its fullest extent, it is important to involve the other organisations on a project with whom you communicate. Making communications easy reduces administration costs for bot you and them.
Project Procedure
Suggested Distribution
Summary
All organisations who create Technical Documents, e.g. design and specifications etc, which are moved under cover of a transmittal document.
Explains how to number documents, and revisions, revision dates and the ASCII table. Defines contents of title blocks and transmittal notes. Suggests a File Naming convention for electronic documents.
All organisations who create, and receive back Technical Documents with a comments and status.
TDOC can provide an effective "Project Management Document Control Service" for a main contractor or project manager.
All organisations who are involved in reviewing Technical Documents
Explains the process of issuing documents. Coordinating the status and comment of a technical document submitted for approval prior to its return. Explains how to use Supplier Document Requirement Scheduling (SDRS). Mentions Document Change Notices (DCN's) for managing changes.
All organisations who raise RFI's / TQ's and or respond to them.
RFI's or TQ's may cover virtually anything, and need not be restricted to just the raising of questions. They can also be used for other purposes, where the response may depend on the answers received from other people, such as:
- Proposing a Change,
- Notification of Events possibly leading to a contract claim.