Job Description for Document Controller in Oil and Gas

Standard Operating Procedure: Document Controller Role Profile & Operational Execution (Oil & Gas EPCC)

Document ID: SOP-OG-DC-001
Effective Date: October 24, 2023
Version: 3.2.0
Review Cadence: Bi-Annual
Owner: Julian Vance, Chief Architect, Template Registry

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) establishes the institutional standard for the position, operational mandate, and execution workflows of the Document Controller within Oil & Gas Engineering, Procurement, Construction, and Commissioning (EPCC) environments.

The purpose of this document is to define the exact competencies, software prerequisites, quality controls, and lifecycle procedures required to manage technical, commercial, and operational documentation across upstream, midstream, and downstream assets. Strict adherence guarantees regulatory compliance (ISO 9001:2015 Clause 7.5, ISO 15489, CFIHOS), mitigates project risk, prevents catastrophic revision control failures, and ensures audit readiness throughout project execution and handover.

---

2. Scope & Prerequisites

2.1 Operational Scope

This SOP applies to all Document Control personnel operating across Onshore/Offshore Greenfield and Brownfield facilities, Major Capital Projects (CAPEX), Operational Asset Management (OPEX), and EPC Subcontractor interfaces.

2.2 System & Software Prerequisites

To execute the responsibilities in this document, the Document Controller must possess certified proficiency and system access rights to:

• Enterprise Document Management Systems (EDMS): OpenText Content Suite, Bentley ProjectWise, Procore, or Aconex.
• Engineering Data Standards: CFIHOS (Capital Facilities Information Handover Specification) or IOGP S-561 data dictionaries.
• PDF Markup & Verification Tools: Bluebeam Revu Extreme (with CAD plugin integration) or Adobe Acrobat Pro.
• Reporting & Analytics Tools: Microsoft Power BI / SQL Interface for Document Register auditing and KPI tracking.

2.3 Field & Site Prerequisites (Site-Based Personnel)

• Personal Protective Equipment (PPE): Minimum OSHA/HSE Standard (Hard Hat, ANSI Z87.1 Impact-Resistant Safety Glasses, Steel-Toe Work Boots, Flame-Retardant Clothing [FRC] NFPA 2112 certified, H2S Monitor).
• Certifications: BOSIET/HUET (Offshore assignments), HUET/FOET, Site Safety Induction Card, ISO 9001 Lead/Internal Auditor awareness certification.

---

3. Roles & Responsibilities (RACI Matrix)

The RACI Matrix defines stakeholder engagement across the document management lifecycle:

Legend: R = Responsible for execution; A = Accountable (Final Approver); C = Consulted for input; I = Informed of progress; S = Submits data.

---

4. Step-by-Step Procedure

 [Phase 1: Intake] ──> [Phase 2: Indexing] ──> [Phase 3: Review Workflow] ──> [Phase 4: Transmittal] ──> [Phase 5: Handover]

Phase 1: Intake & Technical Screening

• 1.1 Receive Deliverable Package: Capture incoming documents via formal Vendor/Engineering transmittal channels. Direct email attachments or unauthorized file-share links are strictly rejected.
• 1.2 Perform Initial Quality Gate Screening:
  • Verify document numbering complies with the Project Document Numbering Specification (e.g., PROJ-ZONE-DISC-TYPE-0001).
  • Verify file format (e.g., Native DWG/DGN along with fully searchable PDF/A).
  • Check physical and digital page orientation, clarity, vector layer integrity, and signature block availability.
• 1.3 Rejection Routing: If non-compliant, issue an automated Rejection Notice back to the originator within 4 working hours using the standardized Rejection Template.

Phase 2: Metadata Indexing & System Registration (EDMS)

• 2.1 Assign Revision Status: Ensure incoming revision code matches project lifecycle rules:
  • Rev A1, A2...: Internal Draft / In-Progress.
  • Rev A, B, C...: Issued for Review (IFR) / Approval.
  • Rev 0, 1, 2...: Issued for Construction (IFC) / Operations (IFO).
• 2.2 Register Mandatory Attributes: Populate all CFIHOS-aligned mandatory attributes in the Master Document Register (MDR):
  • Document Title, Document Number, Revision Number, Document Type Code (e.g., PID, ISO, SPEC, CALC), Discipline Code (e.g., MEC, ELE, PIP, CIV), Facility Code, Sub-System Code, Page Count, and Purchase Order (PO) Reference.
• 2.3 Check In to EDMS: Upload native and Rendition (PDF) files into the central vault. Lock native files against unrecorded edits.

Phase 3: Workflow Routing & Technical Review Management

• 3.1 Initiate Internal Workflow: Route document package to designated Lead Discipline Engineers via EDMS workflow according to the Project Matrix Responsibilities.
• 3.2 Monitor Review SLAs: Track review turn-around times against target SLAs (Standard: 10 working days for Engineering Review; 5 working days for Field Change Notices).
• 3.3 Consolidate Comments: Consolidate markup redlines and compile the formal Comment Review Sheet (CRS). Ensure single-voice technical direction before returning to vendor.
• 3.4 Apply Document Status Codes: Stamp document with appropriate status:
  • Code 1: Approved / Unconditional Acceptance.
  • Code 2: Approved Subject to Comments (Proceed with work, resubmit).
  • Code 3: Rejected / Revise and Resubmit (Do NOT proceed with work).
  • Code 4: Information Only.

Phase 4: Issue for Construction (IFC) & Transmittal Dispatch

• 4.1 Verify IFC Pre-requisites: Confirm document bears a Code 1 or approved Code 2 status and possesses professional engineer sign-off signatures/stamps.
• 4.2 Apply Security Stamps & Watermarks: Apply dynamic digital security watermarks across the canvas: ISSUED FOR CONSTRUCTION - REV [X] - DATE [YYYY-MM-DD].
• 4.3 Generate Outgoing Transmittal: Produce formal Outgoing Transmittal Note (TRN) generated directly from the EDMS.
• 4.4 Execute Distribution: Dispatch package to site fabrication/construction yards and external entities via secure automated transmittal protocols. Record dispatch timestamps.

Phase 5: As-Built Reconciliation & Final Handover

• 5.1 Process Field Redlines: Receive As-Built redline drawings from Field Construction Engineers. Verify physical/digital redlines are clean, legible, and executed in standardized color codes (Red = Additions, Green = Deletions, Blue = Notes).
• 5.2 Coordinate Final Native Updates: Transmit field redlines to the Home Office Design Team to update native CAD/3D Model assets.
• 5.3 Compile Operations Handover Package: Format final closeout documentation to match Asset Owner Operations Handover Specifications (tag-to-document mapping verification via CFIHOS schema).
• 5.4 Execute Final Vault Lockdown: Transition document statuses in EDMS from active lifecycle state to AS-BUILT or SUPERSEDED/ARCHIVED. Lock write access.

---

5. Quality Assurance & Pro-Tips

5.1 Key Performance Indicators (KPIs)

+------------------------------------+------------------+-------------------+
| Metric                             | Target SLA       | Critical Threshold|
+------------------------------------+------------------+-------------------+
| Intake Processing & Screening Time | < 8 Hours        | > 24 Hours        |
| Indexing Metadata Accuracy         | > 99.8%          | < 98.0%           |
| Review Cycle On-Time Closure       | > 95% within SLA | < 85%             |
| Outgoing Transmittal Turnaround    | < 12 Hours       | > 24 Hours        |
| Audit Non-Conformances (ISO 9001)  | 0 Major          | > 1 Minor         |
+------------------------------------+------------------+-------------------+

5.2 Critical Pitfalls & Mitigation Strategies

• Pitfall: Non-Standard Revision Progression (The "Rev 0 Issue"). Skipping revision steps (e.g., moving directly from Rev A to Rev 0 without resolving Code 3 comments).
  • Mitigation: Program strict EDMS hard-stops preventing transition to Rev 0 if open Code 3 review tasks or unresolved CRS items exist in the system architecture.
• Pitfall: Field Execution on Uncontrolled Documents. Site personnel using local, printed copies of drawings that have since been revised.
  • Mitigation: Mandate dynamic QR codes on all printed outputs that query the live EDMS database when scanned, returning an instant VALID: LATEST REVISION or INVALID: SUPERSEDED status page.
• Pitfall: Orphaned Vendor Documentation. Vendor packages submitted without corresponding Purchase Order (PO) or Tag/Equipment references.
  • Mitigation: Automatically block intake processing if mandatory Supplier Document Requirements List (SDRL) / Vendor Document Requirements List (VDRL) tracking line-item IDs are absent from the transmittal header.

---

6. Frequently Asked Questions (Operational Troubleshooting)

FAQ 1: A vendor has submitted a technical drawing with mismatched revision numbers on the title block versus the transmittal cover sheet. How should this be handled?

Answer: Stop intake immediately. Do not process the document into the EDMS register. Issue a formal Transmittal Rejection Notice within the 4-hour window detailing the specific delta between the title block revision and the cover sheet. The vendor must resubmit a clean, reconciled transmittal package. Manual override by the Document Controller is strictly prohibited to preserve audit trail integrity.

FAQ 2: What is the formal protocol when an emergency field revision (Field Change Notice - FCN) occurs on-site during active fabrication/construction?

Answer: The site Document Controller must receive the signed FCN PDF from the Site Construction Manager. Register the FCN in the EDMS as an interim document linked directly to the parent drawing. Update the parent drawing's metadata to reflect an ACTIVE FCN ATTACHED flag. The physical and digital distribution must be updated within 2 hours to ensure field crews execute against the combined Master Drawing + FCN markup package.

FAQ 3: How does the Document Controller ensure audit readiness for ISO 9001 and Operator Quality Audits?

Answer: Run weekly EDMS automated integrity scripts that evaluate metadata completion, orphan documents, pending workflows past SLA, and missing native files. Ensure that 100% of active documents have an un-broken digital chain of custody (Intake -> Review -> Approval -> Distribution). Any exception flagged by the script must be cleared within 24 hours to maintain continuous, audit-ready status.

---

APPROVED BY:

Julian Vance
Chief Architect, Template Registry
ISO 9001 Systems Engineering & Technical Governance