CSI O-PAS EPC SAMPLE DELIVERABLES Version 1 | November 19, 2026 Illustrative planning samples, not ACT or other customer project records. EPC scope discussion · Illustrative sample O-PAS EPC Sample Deliverables Turn an owner requirement into a reviewable scope: a requirements register, an architecture boundary and a responsibility matrix.Download Editable Text PackExplore CSI's EPC Services Before you use the samples A starting point for an agreed project scope Collaborative Systems Integration (CSI) helps EPC teams review O-PAS requirements, define architecture and supplier boundaries, and plan integration and acceptance work. These samples show the form of those outputs; the project team agrees the actual content, responsibilities and commercial scope.Illustrative material, not a customer project record. The scenario is an early planning review for a proposed OPA subsystem at an existing facility. No product, supplier, O-PAS edition or profile has been selected. No design, test result, saving or acceptance decision is implied. Bring these inputs - Owner specification and business decision - Installed-system inventory and available drawings - Retained interfaces, operating constraints and outage windows - Bid assumptions, supplier offers and known information gaps Agree these outputs - Requirements and clarifications register - Architecture boundary and interface assumptions - Responsibility allocation and unresolved decisions - Evidence needed before the next project gate Sample 01 Requirements and clarifications register Each entry connects a proposed requirement to a question, an evidence item and a decision owner. All four entries are illustrative and open. Example entries for a pre-FEED or bid review Record Proposed requirement Clarification and evidence Decision owner and gate R-01 Requirement basis Proposed requirement: The proposed subsystem uses an agreed O-PAS requirement basis. Clarification and evidence: Identify the applicable edition, profiles, project exceptions and exact product/version evidence. Record these in the design basis; do not accept an unqualified “O-PAS compliant” statement. Decision owner and gate: Owner technical authority, with EPC review. Open: resolve before supplier selection. R-02 Retained interface Proposed requirement: Required information is exchanged with retained plant systems. Clarification and evidence: Confirm data and command direction, protocol, security boundary, quality and failure behavior. Obtain the retained-system interface specification and assign interface ownership. Decision owner and gate: Owner and EPC nominate the interface decision owner. Open: resolve before architecture freeze. R-03 Recovery Proposed requirement: The subsystem meets the owner's operating and recovery needs. Clarification and evidence: Agree allowable interruption, recovery behavior, degraded operation and test conditions. Define measurable acceptance criteria in an approved verification plan. Decision owner and gate: Owner operations and technical authority. Open: resolve before test scope and price are frozen. R-04 System accountability Proposed requirement: One named party coordinates integrated system performance. Clarification and evidence: Name the integration authority and allocate diagnosis, correction, retest, configuration and handover obligations in the contract responsibility matrix. Decision owner and gate: Owner and EPC commercial and technical leads. Open: resolve before contract award. A row closes only when its decision, supporting evidence and approval are recorded. A proposed requirement is not an approved design instruction. Sample 02 Architecture boundary for the scope discussion This is a conceptual boundary map, not a network design or a proposed bill of materials. Retained plant systems Existing controls, historian and operating interfaces remain outside the proposed subsystem scope unless expressly included.↔ Defined interface boundary Agree information, commands, access, failure behavior and change ownership. Protocols and products remain to be selected.↔ Proposed OPA subsystem Allocate control applications, I/O, compute, operator access and system management to named suppliers in the approved design. Boundary decisions still required: cybersecurity zones and access, availability, safety-system separation, interface permissions and deployment responsibility. The arrows identify interfaces to define; they do not authorize bidirectional traffic. Safety-system changes and live cutover are outside this illustrative planning scope. Download the conceptual boundary diagram (SVG) Sample 03 Responsibility allocation before contract award Example allocation for discussion. Replace every role with an agreed organization, named authority and contractual obligation; this table assigns no real project contract. Proposed roles and the decisions that remain open Work item Prepare or coordinate Approve or accept Resolve before award Requirements and architecture basis Prepare or coordinate: EPC engineering, with CSI specialist support if contracted Approve or accept: Owner technical authority Resolve before award: Applicable requirements, evidence, exceptions and interface boundaries Integrated configuration and supplier interfaces Prepare or coordinate: Named integration authority, with assigned supplier obligations Approve or accept: Named project design authority, subject to owner acceptance requirements Resolve before award: Who holds system accountability, controls versions and coordinates correction FAT evidence, correction and retest Prepare or coordinate: Named integration authority coordinates; suppliers perform assigned tests and corrections Approve or accept: Acceptance authority named in the approved test plan Resolve before award: Witness points, pass criteria, evidence ownership and included retest effort Site work and operating handover Prepare or coordinate: Separately contracted site delivery and integration parties Approve or accept: Owner operations and designated acceptance authority Resolve before award: Site scope, operating authority, handover assets and ongoing support CSI's participation in planning does not automatically assign it prime integration, site execution or lifecycle-support accountability. Those roles require a separately agreed scope. See the O-PAS Responsibility Matrix guide. Actual project evidence ExxonMobil ACT shows why project roles matter At ExxonMobil's Anchorage Chemical Terminal, CSI designed the COPA 500 system and collaborated on implementation. Wood led system integration and project execution; CPLANE supplied Fusion orchestration. ACT automated a previously manual brownfield facility; it was not a legacy-DCS replacement. That project account supports these specific contributions. The samples above are new illustrative planning material, not ACT drawings, contracts or acceptance records.Read CSI's ACT case study →Read COPA's project account ↗ Scope an EPC engagement with CSI Bring your owner specification, project phase and unresolved decisions. Agree the inputs, outputs, review participants, exclusions, schedule and commercial terms before work begins.Discuss Your EPC ScopeDownload Editable Text Pack Canonical page: https://csi-automation.com/opas-epc-sample-deliverables/