JB-08-Q1CO-017 Rev.3
JB-08-Q1CO-017 Rev.3
Contract: Q1CO
JOB BULLETIN
JB-08-Q1CO-017
Rev.3
September 10, 2019
ORGANIZATION LOCATION
Applicable for: Santiago
AAQSA Lima
Aplicable a: Houston/Manila
Vancouver
New Delhi
x FLUOR Site
X Complete Project
This Job Bulletin provides specific instructions to Company and Contractor Field personnel with respect to
“As-Built” documents. This illustrates how “As-Built” documents are to be managed by the Company for
the Quellaveco Project.
Este Boletín de Trabajo provee instrucciones específicas al personal terreno Flúor con respecto a los
documentos según construidos (Documentos “As-Built” (“Como-Construido”)). Este ilustrara como planos
y documentos según construidos se trataran por el proyecto Quellaveco.
FC:cpr
Attachment: Appendix I
1. Scope
This Job Bulletin provides instructions to Company and Contractor Field personnel with respect to
“As-Built” documentation. It illustrates how “As-Built” documents are to be managed by the
Company for the Quellaveco Project.
2. Overview
Generation of “As-Built” data is the responsibility of each construction contractor for work performed
within their contract. Coordination and validation will be performed by the Company Field
Engineering group, with assistance from the Contract Administrator.
Specific documents that are required to be “As-Built” are described in Appendix I of this Job
Bulletin. This also includes phase where it is required for turnover (Mech. Comp, TCCC, etc.).
3
“As-Builts” required by the Company at Mechanical Completion stage are the following:
x Process Flow Diagrams
x Piping & Instrumentation Diagrams
x Mechanical General Arrangements drawings
x Mechanical Detailed drawings
x Concrete and Structural drawings
x Civil/Bulk Earthworks drawings
x Electrical SLD, schematics and panel schedules
x All electrical wiring diagrams
x All instrumentation loop and wiring diagrams
x Cable and Raceway schedule
x Pipes, pipelines and pipe supports lists
Format of “As-Built” documents will be consistent with JB-08-Q1CO-002 (Drawing format) and JB-
08-Q1CO-003 (Document Format). Exceptions may be permitted at the discretion of the Company
Field Engineering Manager.
3. Responsibilities
The Company Field Engineering Manager is responsible for assigning the discipline specific
field engineer / technician to review the “As Built” information being generated and to
determine whether the “As-Built” documents have been correctly performed. The Field
Engineering Manager will continue to advise the Contract Administrator the status until all
“As-Built” documents are finalized.
The Company Field PDDM is responsible for the identification, distribution, maintenance and
control of the “As-Built” documents and is the sole control point of the project, during the
processing of the “As-Built” documents. PDDM will manage the transfer of “As-Built”
documents to the pre-commissioning, commissioning teams and final transfer to AAQ.
The Contractor shall work on the latest numerical document revision issued for construction (IFC).
“As-Built” data is to be provided by construction contractors in all following formats:
x Drawings 2D CAD files must be updated in (AutoCAD *.DWG format, version 2017)
x Acrobat (.pdf) files with annotations shall be done using Adobe Acrobat in A1 size format
x Field Hard Copies, printed in A1 or A3 size: Contractor shall mark-up hard copies by hand
(these must be clear, legible and use of red ink only).
Hand marked up drawings and documents must be original and legible. All written instructions and
signatures on red lined documentation must be in red ink only. Documents not following revision
control practices, such as documents containing white out or illegible markings may be deemed
“VOID” and returned to the applicable contractor for re-submission.
Changes that have occurred (to coordinates, sizes, alignment etc.) shall be indicated within a cloud
(implosive) next to the change. The corresponding reference shall be included as a request for
information (RFI) change notice to the design (FCN / DCN) etc.
The document shall then be submitted in PDF format for review via Document Control by adding an
extension to the name with the letters RL (Example file: MQ13-02-DR-6030-CE2001_RL). Once
approved by the Company, the Contractor shall convert the document to a final "as-built" drawing
(without clouds or other unbound references). Red lines once reviewed and approved by Company
Engineering/Commissioning must can be used to be included as part of the Turnover package
supporting documentation, but such files (drawings and others), must be updated in their native file
format as part of final contract completion prior to final payment approval.
For the specific case of PI&Ds and data sheets, these will be provided to Contractors in PDF format
only. These will be Red lined in PDF and Fluor will coordinate their final native update for client
turnover.
Contractors may receive drawings in Intergraph Micro-Station format and/or AutoCAD format from
Fluor. Nevertheless, conversions from Micro-Station to AutoCAD of such drawings are the
Contractor's responsibility (the Company may assist with the guidelines for proper conversion).
The IFC drawings to be returned/delivered in its final turnover format, shall be stamped “As-Built”
when the final mark ups have been made that accurately reflect actual field conditions and the
Contractor has completed all work scope for the area in reference.
As-built document formatting shall be consistent with the established document formats of the
Project. The original title block of the document shall be maintained. The only fields to be updated
are REV., New revision line (REV No., DATE, DESCRIPTION) All others items such as, (PROJECT
NAME, DISCIPLINE LEAD, ENGINEERING MANAGER, PROJECT MANAGER and CLIENT,
DRAWING NUMBER AND REFERENCE DRAWING), are to be kept intact to maintain traceability
and so that associated drawings may capture all changes. Final As-Built revision will be logged as
Rev “AB”.
Once all the modifications in the drawing have been incorporated in AutoCAD (eliminating clouds
and references) the Contractor shall print two copies in A3. When more than one original signed
copy is required, or a hard copy in A1 size is required by the Owner or for delivery to the
authorities, the Company shall notify the Contractor of such cases.
All printed copies of drawings shall be stamped and signed by the qualified Contractor Engineer
(leading discipline of the drawing) certifying that the information presented in the drawing accurately
reflects the completed works. The Contractor shall also coordinate with the Company to obtain the
stamp and signature on the drawing of the Fluor or Third Party Design Engineer. When the
Contractor is also the Design Engineer, the qualified Contractor CIP Design Engineer must also
stamp and sign the drawing.
The Contractor shall submit the final As-built drawing through transmittal to Document Control via
Coreworks System, issued for information purposes, and must contain the following documents:
x Electronic AutoCAD format (AutoCAD *.dwg format, compatible with version 2017)
x PDF format of the CAD file plotted in A1 size
x 2 hard copies printed in black and white, size A1 or A3, as appropriate, with stamp and
signature of the CIP Engineer of the leading discipline of the drawing, and signature of the
Design Engineer.
x Scanned PDF in A1 (before folding) or A3 (as appropriate) signed by the Contractor
Engineers.
Note: Hard copies of drawings shall be delivered in 3-hole plasticized binders. A3 and A4 drawings
shall be contained in A3 and A4 binders, respectively. Also, drawings shall be delivered folded and
protected in plastic covers.
Layers and text sizes used in the original native file drawing shall be preserved. AutoCAD
Procedure and the native original file containing the layers shall be attached.
Coding
The original drawing file title shall be maintained and renamed as an AB revision (File example:
MQ13-02- DR-6030-CE2001_AB)
The electronic "As-Built" stamp (attached as 1:1 scale block) shall be inserted above the
aforementioned title block where the Contractor's logo and Contract number will go. See the
example provided below:
Attachments:
5. “As-Built” of 3D Models
The extent and strategy for incorporation of as-built data into 3D will follow definition within
Appendix I.
Appendix I
1. Alcance
Este Boletín de Trabajo entrega instrucciones para el personal de Fluor y para los Contratistas de
terreno respecto de los documentos “As-Built” (“Según-Construido”). Este indica cómo deben ser
gestionados dichos documentos por la compañía para el Proyecto Quellaveco.
2. General
La generación de información según obra será responsabilidad de cada uno de los Contratistas de
Construcción en el caso de aquellos trabajos realizados como parte de su contrato. El equipo de
Ingeniería en terreno, Fluor, con la colaboración del Administrador de Contratos, se encargará de
coordinar y validar de este tipo de información.
En el Apéndice I de este Job Bulletin se describen documentos específicos que deben estar "As-
Built". Esto también incluye la fase de traspaso (Mech. Comp, TCCC, etc.).
3
Los "As-Builts" requeridos por la Compañía en la etapa de finalización mecánica son los
siguientes:
El formato de los documentos “según obra” deberá cumplir con lo indicado en JB-08-Q1CO-002
(formato de planos) y JB-08-Q1CO-003 (formato de documentos). El Gerente de Ingeniería en
Terreno podrá efectuar excepciones a su discreción.
3. Responsabilidades
x Los archivos CAD de Planos 2D deben actualizarse en (formato AutoCAD * .DWG, versión
2017).
x Los archivos Acrobat (.pdf) con anotaciones se realizarán con Adobe Acrobat en formato de
tamaño A1.
x Copias impresas en terreno, deben estar en tamaño A1 o A3: El contratista deberá marcar
las copias impresas a mano (deben ser claras, legibles y solo con tinta roja).
Los planos y documentos marcados a mano deben ser originales y legibles. Todas las
instrucciones escritas y firmas en la documentación corregida deben estar en tinta roja solamente.
Los documentos que no siguen las prácticas de control de revisión, como los documentos que
contienen corrector líquido o son ilegibles, pueden considerarse "ANULADOS" y devolverse al
contratista correspondiente para su reenvío.
Los cambios que ocurran (coordenadas, tamaños, alineación, etc.) se indicarán dentro de una
nube de texto (implosiva) junto al cambio. La referencia correspondiente se incluirá como un aviso
de cambio de solicitud de información (RFI) para el diseño (FCN / DCN), etc.
Para el caso específico de PI&D y Hojas de Datos, estos se proporcionarán a los Contratistas sólo
en formato PDF. Se realizarán correcciones en PDF y Fluor coordinará su actualización final al
formato original para la entrega al cliente.
Los contratistas pueden recibir de Fluor planos en formato Intergraph Microstation y/o AutoCAD.
Sin embargo, las conversiones de Microstation a AutoCAD de dichos planos son responsabilidad
del Contratista (la Compañía puede ayudar con las pautas para la conversión adecuada).
El formato del documento As-Built debe ser consistente con los formatos de documento
establecidos del Proyecto. Se mantendrá el bloque de título original del documento. Los únicos
campos que se actualizarán son REV., Nueva línea de revisión (REV N°, FECHA, DESCRIPCIÓN)
Todos los demás elementos como (NOMBRE DEL PROYECTO, LÍDER DE DISCIPLINA,
GERENTE DE INGENIERÍA, GERENTE DE PROYECTO y CLIENTE, NÚMERO DE PLANO Y
PLANO DE REFERENCIA), deben mantenerse intactos para mantener la trazabilidad y para que
los planos asociados puedan capturar todos los cambios. La revisión final As-Built se registrará
como Rev "AB".
Una vez que todas las modificaciones en el plano se hayan incorporado en AutoCAD (eliminando
nubes y referencias), el Contratista imprimirá dos copias en A3. Cuando se requiere más de una
copia original firmada, o el Propietario requiere una copia impresa en tamaño A1 o para entregarla
a las autoridades, la Compañía notificará al Contratista de tales casos.
Todas las copias impresas de los planos estarán timbradas y firmadas por el Ingeniero Contratista
calificado (líder de disciplina del plano) certificando que la información presentada en el plano
refleja con precisión los trabajos terminados. El Contratista también se coordinará con la
Compañía para obtener el timbre y la firma en el plano del Ingeniero de Diseño de Fluor o del
Ingeniero de Diseño del Cliente. Cuando el Contratista también es el Ingeniero de Diseño, el
Ingeniero de Diseño CIP calificado del Contratista timbrará y firmará el plano.
Si un plano que será convertido en un As-Built no ha sufrido cambios (fue construido tal cual indica
el último plano IFC) entonces se puede obviar el paso de “4.1 Stage I” de enviar un plano redline
consolidado. Puede pasar directamente a la presentación del plano As-Built con la nota en el
plano “sin cambios”.
El Contratista presentará el plano final As-built a través de un envío a Control de Documentos a
través de Coreworks System, emitido con fines informativos; y debe contener los siguientes
documentos:
x Formato electrónico de AutoCAD (formato AutoCAD * .dwg, compatible con la versión 2017)
x Formato PDF del archivo CAD ploteado en tamaño A1
x Dos (2) copias impresas en blanco y negro, tamaño A1 o A3, según corresponda, con timbre
y firma del Ingeniero CIP de la disciplina principal del plano, y firma del Ingeniero de diseño.
x Scaneo de pdf en A1 (antes del plegado) o A3, según corresponda, firmado por los
ingenieros contratistas.
Nota: Las copias impresas de los planos se entregarán en archivadores plásticos de 3 agujeros.
Los planos en A3 y A4 se incluirán en archivadores A3 y A4, respectivamente. Además, los planos
se entregarán doblados y protegidos en fundas plásticas.
Los planos en formato PDF serán codificados por SMI como "informativos".
3
Del Alcance o Contenido del Plano
El mismo alcance del plano original, se reflejará en todos los formatos; es decir, si el plano original
cubre 1 km el “as-built” debe cubrir el mismo alcance y reflejar los mismos componentes del plano
original, manteniendo la misma disposición de detalles y figuras.
El sello electrónico “As-Built” (adjunto como bloque en escala 1:1) se insertará sobre el bloque de
título antes mencionado, donde irán el logo del Contratista y el número del Contrato. Ver el
ejemplo que se muestra más abajo
Adjuntos:
5. ‘As-Built’ de Modelos 3D
Appendix I
APPENDIX I
1
TECHNICAL DELIVER ABLES MATRIX
Precondition to:
Updated
Red line
Revision
Item (As-Built) Mech Transfer Pract Final Comments
(As-Built)
Required Comp CC&C Comp Comp
Required
▪ Project Procedures Manual (including discipline procedures) X Develop at beginning and update as appropriate
▪ Execution Plans (for all disciplines/phases of the Work) X Develop at beginning and update as appropriate
▪ Project Master & Detailed Scheduled X X Develop at beginning and update as appropriate
▪ Progress Curves X Include in project completion report
▪ Time-phased Expenditure and Commitment Tables and Curves X Include in project completion report
▪ Change Management Reports X Include in project completion report
Develop on design basis and update as appropriate;
▪ Design Criteria and Calculations in all disciplines X X
AAQ to update after Practical Completion
▪ Equipment list with pertinent descriptions X X Update as appropriate
▪ Material/Equipment Requisition with Recommended Bidders Lists X Update as appropriate
▪ Purchase Requisition and Purchase Orders X Update as appropriate
▪ Purchase Order Log & Contract Register X Update as appropriate
▪ Warehouse Inventory List X Update as appropriate
▪ Construction/Commissioning Spare Parts List X X Doc turnover for MC; need earlier for procurement
▪ Operational/Insurance Spare Parts List X X Doc turnover for MC; need earlier for procurement
▪ Facility Parts Manuals X Update as appropriate at CCC of Operable System
▪ Equipment data sheets X Update as appropriate at CCC of Operable System
▪ Instrumentation Index and data sheets X Update as appropriate at CCC of Operable System
▪ Other data sheets X Update as appropriate at CCC of Operable System
▪ Specifications (include <COMOS, expret control, SIMIT, SIC) X Update as appropriate at CCC of Operable System
▪ Vendor drawings, data, certifications, warranties X X X Update as appropriate at CCC of Operable System
▪ Contractor (execution) drawings, data, certifications, and warranties X X X Determine AAQ or Contractor redline update revision
▪ Sub-tier contractor drawings, data, certifications, and warranties X X X
▪ Technical documentation, to include:
o Data sheets X
o Plot plans X X
o Process Flow Diagrams / Heat Balances X X X X Issue redline at MC and update as appropriate PC
o Mechanical general arrangements X X X X Issue redline at MC and update as appropriate PC
o Piping and Instrumentation Diagrams X X X X Issue redline at MC and update as appropriate PC
o Mechanical and Detailed Drawing X X X X Issue redline at MC and update as appropriate PC
o Concrete and Structural Drawings X X X X Issue redline at MC and update as appropriate PC
o Civil/bulk earthworks drawings X X X X Issue redline at MC and update as appropriate PC
o Electrical single line diagrams, schematics and panel schedules X X X X Issue redline at MC and update as appropriate PC
o Electrical Layout and System Functional Descriptions X X X X Issue redline at MC and update as appropriate PC
o All instrumentation loop and wiring diagrams; X X X X Issue redline at MC and update as appropriate PC
o System control logic descriptions X X X X Issue redline at MC and update as appropriate PC
o PLC program and logic program (and changes thereto) X X X X Issue redline at MC and update as appropriate PC
o Bills of Materials/MTO’s (Excel Format) X
o System Descriptions X
o All as built buried piping, cables, ducts, infrastructure, vessels etc X X X
o Pipeline & Pipe Support Lists X X Issue redline at MC and update as appropriate PC
o Electrical Load List X X X Update as appropriate
o All as built fire, security or safety system drawings; X X X
o Cable and Raceway Schedule X
o Instrument List X
o DCS I/O List X Per operable system
o Isometrics X X Update as appropriate
o 3D Plant Model X X Update as appropriate
▪ Field eng annotations for drawings, specifications, lists, models, etc. X X X Update as appropriate
▪ Construction bid packages X
▪ Constructability and HazOp report including risk analysis X
▪ Asset register; X Per operable system consolidated
▪ Project Completion Report; X Precondition to PC, completed through project
▪ Daily construction reports (including Daily Work Reports) X Available as needed throughout project
▪ QA/QC docs incl on-site test reports, concrete slump, cable tensions,
X Available as needed throughout project
compact, etc
▪ Plant and system start-up manuals and procedures (incl input from eng and
X Delivered in time for operator training and start up
vendors)
▪ Weekly Safety and Incidents Reports X
▪ System turnover package description and schedule X In time to plan and implement system turnover
▪ Pre-commissioning, Commissioning and Turnover Plan and Procedure X In time to plan and implement system turnover
▪ Record Documents not otherwise included in this Matrix X Made available per contract as required
▪ Monthly Project Reports X
▪ Weekly progress reports during eng, const and commissioning X
1
In the event of termination and otherwise as a precondition to Final Completion, all above documents are to be
delivered to Company