Plant Design Work to be Performed by the Engineering Contractor

1      General

1. The ENGINEERING CONTRACTOR is responsible for developing the detailed design and implementing the scope of work to ensure the safe and successful completion on site within the key date schedule.
2. EPC Company will issue a contract scope with a section for each relevant discipline. This contract scope must be used to determine the full detailed scope of work to be performed by the EC. The contract scope and the primary documents described above provide a definition of the scope of design work and the split of engineering services among Air Products, the EC, and others for the different areas of the plant.
3. Work by the ENGINEERING CONTRACTOR shall be based on, but not limited to, deliverables issued by EPC Company including the standards, specifications, codes, regulations, etc., referenced in this document and in the contract scope.
4. If the ENGINEERING CONTRACTOR have standards, specifications, procedures, etc., that are not significantly different from EPC Company and that provide the same information perhaps in a different format, EPC Company will review and accommodate these to the fullest extent practical. This is subject to meeting the project requirements in paragraph 4.1.5.1.
5. The ENGINEERING CONTRACTOR shall include the following in the proposal for each project:
   • Any proposed deviations to EPC Company standards, specifications, and procedures with examples of alternative standards, specifications, or procedures.
   • Preliminary drawing and document register.
   • Supplier List with details of proposed suppliers of equipment to be procured or supplied by the EC.
   • Any additional documentation as requested in the contract scope.
6. The ENGINEERING CONTRACTOR shall procure equipment and materials in accordance with the requirements of the relevant sections of this document and the contract scope.
7. The ENGINEERING CONTRACTOR shall provide construction management services in accordance with the requirements of the relevant sections of this document when required by the contract scope.

2  Deliverables from the EC

1. This specification and the contract scope will provide a description of the documents that are to be produced by the ENGINEERING CONTRACTOR during the contract execution. If local, regional, or federal authorities or EPC Company require that documents (e.g., drawings, calculations) produced by the ENGINEERING CONTRACTOR have certifications applied to them, such as professional engineer stampings, the ENGINEERING CONTRACTOR shall obtain all required certifications and/or stampings. The contract scope will state if EPC Company requires certification and/or stamping.
2. The ENGINEERING CONTRACTOR shall produce complete and accurate design drawings to define the procurement, prefabrication, and construction of a complete and operable facility or section of facility as required in the contract scope of work. The design may be broken down into unit operations for focus, scheduling, and general organization. The deliverables and/or data shall be formatted as required by the project. The documentation shall be submitted to EPC Company in the electronic file formats defined in the job contract scope. They shall be editable to support plant modifications during the plant’s operating life.
3. The following electronic file formats are generally preferred by Company. The list is in order of preference, starting with the most preferred.
   • PDS models with Micro Station drawings format for full or partial plant designs.
   • Micro Station, Smart Plant PID, Smart Plant Instrumentation, or PowerDraft formats for work limited to P&ID, instruments, electrical, or structural drawings.
   • MicroStation drawings format when work is limited to layout graphics and general drawings. AutoCAD dwg format is less preferred but acceptable. A dxf format is acceptable only if dwg format is not available.
   • TIFF format images are an absolute minimum requirement and the very least acceptable.
4. These portions of the plant included in each unit operation are shown on the EPC Company drawing included in the contract scope.
5. Multiple releases of deliverables will typically be required. The following are the minimum required releases.
   • Issue for EPC Company review and comment.
   • Issue for customer review and approval (when relevant).
   • Issue approved for purchase or construction.
   • Issue as-built.

Further details will be provided in the contract scope. Refer to paragraph 3.4.6 for revision codes.

3      EC’s Drawing and Document Register

1. The ENGINEERING CONTRACTOR shall submit a complete list of drawings and documents that will be issued to fulfill the scope of services under the contract. This list must be submitted before the date of the contract kick-off meeting and preferably within three weeks from the date of contract award. The deliverables of each engineering design discipline shall be included. This list will provide the estimated number of specifications, plans, sections, details, schematics, isometrics, schedules, and bills of materials for all design work to be performed by the EC. EPC Company will provide information in the contract scope on the desired format for these deliverables. The following information shall be provided for each item on the list and shall be maintained up-to-date by the EC:
   • Drawing number
   • Title
   • Estimated number of sheets
   • Start date (scheduled/forecast/actual)
   • Issue dates (scheduled/forecast/actual)
   • Current revision
   • Estimated number of man-hours
2. The list of drawings and documents referenced above is a key engineering and design control document. In addition to providing the ENGINEERING CONTRACTOR with an appropriate level of planning and control, it will enable EPC Company to plan its own review activities.
3. As such, the drawing and document register will be subject to review and approval by Air Products.
4. At the end of the project, the drawing and document register shall be finalized by the ENGINEERING CONTRACTOR and issued to Air Products.

4  Computer-Aided Design

1. The ability to interface with models produced by EPC Company is essential. In general, EPC Company requires that Smart Plant PID, Intergraph PDS, and MicroStation be used for the CAD design of the plant. Under limited circumstances, EPC Company may allow the use of some other types of CAD design for the plant. This will be decided on a case-specific basis. EPC Company must approve the use of the alternative CAD system in advance. Each section of this scope of work details the requirements for the content of the CAD model.
2. EPC Company will provide PDS CAD piping specifications where necessary. If the ENGINEERING CONTRACTOR requires any additions/changes to these specifications, requests should be submitted to EPC Company for consideration.
3. EPC Company may require that SmartPlant Instrumentation (formerly INtools) be used for the instrumentation design of the plant. This will be defined in the contract scope requirements. If SmartPlant Instrumentation is a project requirement, the ENGINEERING CONTRACTOR shall use it to produce the instrument index, instrument specifications, and wiring design at a minimum.
4. When SmartPlant Instrumentation is a project requirement, the ENGINEERING CONTRACTOR shall use the version and revision level specified by Air Products.

5  Bills of Materials

The ENGINEERING CONTRACTOR is required to prepare bills of materials (BOMs) or material take-offs (MTOs) only if this is explicitly specified in the contract scope.

6  Interface Data Sheets

1. The ENGINEERING CONTRACTOR shall prepare Interface data sheets for each portion (unit operation) of the plant for which the ENGINEERING CONTRACTOR is responsible. All interface connections between the EC’s portion of the plant and Company portion of the plant shall be included. These data sheets shall be maintained and updated monthly throughout the project. This process will ensure the interface design is complete and that there are no “HOLDS”.
2. An example blank interface data sheet is attached in Appendix A.
3. Interface data shall be prepared for each design discipline. The data shall provide the information needed by the ENGINEERING CONTRACTOR and EPC Company to do their respective design work connected at the interface points.

7      Design Completion Statements (DCS)

1. As specified in the contract scope, the ENGINEERING CONTRACTOR shall prepare design completion statements (DCSs) and issue them to Air Products. Each design discipline shall prepare DCSs for each portion (unit operation) of the plant for which the ENGINEERING CONTRACTOR is responsible.
2. The DCS identifies:
   • The basis of a design package issued for an installation contract.
   • Any areas of concern such as incomplete supplier data, omissions, hold areas, and risk areas in sufficient detail to enable estimating the cost impact on the installation contract.
   • The forecast dates for issue of drawing revisions.
3. DCSs shall be prepared immediately before the awarding of the construction contract. Each DCS should list all areas of the construction package that are incomplete or subject to change and identify any outstanding installation materials to be requisitioned.
4. Design completion statements for all work packages relevant to an installation contract shall be completed at the same time.
5. The ENGINEERING CONTRACTOR shall maintain the log of DCS numbers, revisions, and issue dates. The ENGINEERING CONTRACTOR and EPC Company shall retain copies of the design completion statements.
6.  An example blank design completion statement is attached in Appendix B. The blank form includes instructions for completing the form.

8  Construction Engineering Support Scope of Work

1. The ENGINEERING CONTRACTOR shall prepare, coordinate, and write the scope of work documents for each site construction contract and request any information required from EPC Company and other contractors. This is to ensure that a complete scope has been identified.
2. The ENGINEERING CONTRACTOR is responsible for identifying to EPC Company any omissions that may affect site coordination.

9  Queries from Site Engineering Support

As part of the job contract, the ENGINEERING CONTRACTOR shall be responsible for providing timely and accurate responses to questions from suppliers, prefabrication contractors, or the site construction team that result from errors, omissions, or lack of clarity in the deliverables issued “Approved for Construction” by the EC.

10  As-Built Drawings

1. Any changes to materials of construction; any physical, dimensional, or manufacturer changes; or any substitutes that occur during the construction phase of the facility must be reflected on as-built drawings.
2. When Smart Plant Instrumentation is a project requirement, the ENGINEERING CONTRACTOR shall also provide an as- built database.
3. The contract scope will contain project-specific information on as-built document requirements.
4. An “Approved for Construction” version of the relevant drawings will be kept at the construction site. The field contractor(s) will mark any deviations from the original design on these drawings as they occur. When field work is completed, these marked-up drawings will be returned to the ENGINEERING CONTRACTOR for preparing “as-built” revisions.
5. All drawings originally prepared by the ENGINEERING CONTRACTOR shall be revised in their original CAD version and re-issued clearly indicating the as-built status. The submittal of the as-built drawings to EPC Company shall be as required by the contract scope.