DOCUMENT LOG. Issue Date Comment Author
DOCUMENT LOG. Issue Date Comment Author V1 19 July 2019 First draft sent to customer for review Xxxxx Xxxxxxxxx Xxxxxxxxxx Xxxxxxxxx V2 6 Aug 2019 Incorporated feedback from provider Xxxxx Xxxxxxxxx TERMINOLOGY The EGI glossary of terms is available at: xxxxx://xxxx.xxx.xx/wiki/Glossary For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Contents
DOCUMENT LOG. Issue Date Comment Author V1 19 July 2019 First draft sent to customer for review Xxxxx Xxxxxxxxx Xxxxxxxxxx Xxxxxxxxx VFINAL 25 July 2019 Final version agreed with customer Xxxxx Xxxxxxxxx Xxxxxxxxxx Xxxxxxxxx
DOCUMENT LOG. Issue Date Comment Author 10/01/2019 First Version Xxxxxx Xxxxxxxx
DOCUMENT LOG. Date Comment Author 01/03/2016 Final version OLA Xxxxxxxxxx Xxxxxxxxx Xxxxxxxx xx Xxxxx 10/04/2017 New final version: • Extension till 1/01/2018 Xxxxxxxxxx Xxxxxxxxx Xxxxxxxx xx Xxxxx TERMINOLOGY The EGI glossary of terms is available at: xxxxx://xxxx.xxx.xx/wiki/Glossary For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Contents
DOCUMENT LOG. Issue Date Comment Author V1 19 July 2019 First draft sent to customer for review Xxxxx Xxxxxxxxx Xxxxxxxxxx Xxxxxxxxx VFINAL 25 July 2019 Final version Xxxxx Xxxxxxxxx Xxxxxxxxxx Xxxxxxxxx V2 19 Aug. 20 Updated with extension of pilot until the end of the project Xxxx Xxxxxxxxx TERMINOLOGY The EGI glossary of terms is available at: xxxxx://xxxx.xxx.xx/wiki/Glossary For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Contents
DOCUMENT LOG. The Engineer shall maintain a record (“log”) of all documents it receives, creates or transmits during the construction/manufacturing of the Project. The log shall include time requirements of responses if needed. Deliverables Construction contract administration. Contract award recommendation. City staff meetings. Pre-work conference. Survey control. Plan interpretation, RFIs, field orders. Testing coordination. Lab voucher review. Site visits. Pay estimate review. Monthly Progress payment review. Monthly progress reports. Submittal review. Quality observations. Daily report review.
DOCUMENT LOG. The Engineer shall maintain a record (“log”) of all documents it receives, creates or transmits during the manufacturing process of the Project. The log shall include time requirements of responses if needed.
DOCUMENT LOG. The Engineer shall maintain a record (“log”) of all documents it receives, creates or transmits during the construction/manufacturing of the Project. The log shall include time requirements of responses if needed. Deliverables Vendor/Contract coordination. Procurement contract administration. City staff meetings. Pre-work conference. RFP interpretation, RFIs, field orders. Testing coordination. Progress payment review. Monthly progress reports. Submittal review. Submittal Management Plan. Progress reports. Web-based document management system. Review and Evaluation of CDRLs. Design review meetings. Meeting minutes and/or reports Manage design review drawings. Written responses to design submittals Pre-production meetings. Pre-delivery configuration audit. Updates to production schedule. Certificates of compliance and data packages. Inbound or receiving inspection. Document comments and resolution tracking. Review and approval of critical documents from the following categories: - Bills of material - Training programs - Safety program plans
