Hangar-3211-DRAFT-Specifications.pdf

Hangar 3211 Fire Alarm System Upgrades

DOCUMENT 00 01 15

LIST OF DRAWINGS

02/24

PART 1 GENERAL

1.1 SUMMARY

This section lists the drawings for the project pursuant to contract clause "DFARS 252.236-7001, Contract Drawings and Specifications."

1.2 CONTRACT DRAWINGS

Contract drawings are as follows:

DRAWING NO. REVISION NO. NAVFAC DWG NO. TITLE

G-001 00 COVER

SHEET

G-002 00 GENERAL

NOTES

F-001 00 ELECTRICAL

SYMBOLS,

GENERAL

NOTES,

AND

ABBREVIATIONS

F-101 00 OVERALL

FIRE

PROTECTION

SITE KEY

PLAN

FD-101 00 NORTH

HANGAR

FIRE

PROTECTION

REMOVALS

FD-102 00 SOUTH

HANGAR

FIRE

PROTECTION

REMOVALS

FD-103 00 EAST

HANGAR

FIRE

PROTECTION

REMOVALS

DOCUMENT 00 01 15 Page 1

DRAFT

DRAWING NO. REVISION NO. NAVFAC DWG NO. TITLE

FD-104 00 MECHANICAL

ROOM FIRE

PROTECTION

REMOVALS

FD-601 00 FIRE

ALARM

RISER

DEMOLITION

DIAGRAM

FD-105 00 NORTH

HANGAR

FIRE

ALARM

REMOVALS

FD-106 00 SOUTH

HANGAR

FIRE

ALARM

REMOVALS

FD-107 00 SOUTH

HANGAR

FIRE

ALARM

REMOVALS

FD-108 00 MECHANICAL

ROOM FIRE

ALARM

REMOVALS

FA-101 00 NORTH

HANGAR

FIRE

ALARM

INSTALLATIONS

FA-102 00 SOUTH

HANGAR

FIRE

ALARM

INSTALLATIONS

FA-103 00 EAST

HANGAR

FIRE

ALARM

INSTALLATIONS

FA-104 00 MECHANICAL

ROOM FIRE

ALARM

INSTALLATIONS

FA-601 00 FIRE

ALARM

RISER

INSTALLATION

DIAGRAM

DOCUMENT 00 01 15 Page 2

DRAWING NO. REVISION NO. NAVFAC DWG NO. TITLE

FA-602 00 FIRE

ALARM

MATRIX OF

OPERATIONS

M-101 00 MECHANICAL

INSTALLATIONS

M-102 00 MECHANICAL

DETAILS

-- End of Document --

DOCUMENT 00 01 15 Page 3

SECTION 01 11 00

SUMMARY OF WORK

02/24

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Salvage Plan ; G

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

The work includes demolition of an existing High Expansion Foam (HEF) fire suppression system, the demolition of the existing fire alarm system, and the design of a new mass notification / fire alarm system and incidental related work.

1.2.2 Location

The work is located at the Hangar 3211 at Joint Base McGuire-Dix-Lakehurst, New Jersey , approximately as indicated. The exact location will be shown by the Contracting Officer.

1.3 OCCUPANCY OF PREMISES

Building(s) will be occupied during performance of work under this Contract. Occupancy notifications will be posted in a prominent location in the work area.

Before work is started, arrange with the Contracting Officer a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches, corridors, and stairways.

1.4 EXISTING WORK

Remove or alter existing work in such a manner as to prevent injury or damage to any portions of the existing work which remain.

Repair or replace portions of existing work which have been altered during construction operations to match existing or adjoining work, as approved by the Contracting Officer. At the completion of operations, existing work must be in a condition equal to or better than that which existed before new work started.

1.5 LOCATION OF UNDERGROUND UTILITIES

Obtain digging permits prior to start of excavation, and comply with Installation requirements for locating and marking underground utilities.

SECTION 01 11 00 Page 1

Contact local utility locating service a minimum of 48 hours prior to excavating, to mark utilities, and within sufficient time required if work occurs on a Monday or after a Holiday. Verify existing utility locations indicated on contract drawings, within area of work.

1.5.1 Notification Prior to Excavation

Notify the Contracting Officer at least 15 days prior to starting excavation work.

1.6 SALVAGE MATERIAL AND EQUIPMENT

Items designated by the Contracting Officer to be salvaged remain the property of the Government. Segregate, itemize, deliver and off-load the salvaged property at the Government designated storage area located within 15 miles of the construction site.

Provide a salvage plan , listing material and equipment to be salvaged, and their storage location. Maintain property control records for material or equipment designated as salvage. Provide a system for property control in the salvage plan. Store and protect salvaged materials and equipment until disposition by the Contracting Officer.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 2

SECTION 01 14 00

WORK RESTRICTIONS

11/22, CHG 3: 08/24

PART 1 GENERAL

1.1 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.

1.2 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

List of Contact Personnel

SD-07 Certificates

1.3 CONTRACTOR ACCESS AND USE OF PREMISES

1.3.1 Activity Regulations

Ensure that Contractor personnel employed on the Activity become familiar with and obey Activity regulations including safety, fire, traffic and security regulations. Keep within the limits of the work and avenues of ingress and egress. Wear appropriate personal protective equipment (PPE) in designated areas. Do not enter any restricted areas unless required to do so and until cleared for such entry. Ensure all Contractor equipment, include delivery vehicles, are clearly identified with their company name.

1.3.1.1 Subcontractors and Personnel Contacts

Provide a list of contact personnel of the Contractor and subcontractors including addresses and telephone numbers for use in the event of an emergency. As changes occur and additional information becomes available, correct and change the information contained in previous lists.

1.3.1.2 No Smoking Policy

Smoking is prohibited within and outside of all buildings on installation, except in designated smoking areas. This applies to existing buildings, buildings under construction and buildings under renovation. Discarding tobacco materials other than into designated tobacco receptacles is considered littering and is subject to fines. The Contracting Officer will identify designated smoking areas.

SECTION 01 14 00 Page 1

1.3.2 Working Hours

Regular working hours will consist of an 8 1/2 hour hour period established by the Contracting Officer, between 7 a.m. and 3:30 p.m., Monday through Friday , , excluding Government holidays.

1.3.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval.

Make application 15 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, contract number and project title. Based on the justification provided, the Contracting Officer may approve work outside regular hours. During periods of darkness, the different parts of the work must be lighted in a manner approved by the Contracting Officer.

1.3.4 Exclusionary Period

No work may be performed during the period 17:00 to 06:00 , inclusive, without prior written approval of the Contracting Officer. This period has not been considered in computing the time allowed for the performance of this contract.

1.3.5 Occupied Building

The Contractor shall be working in an existing building which is occupied.

Do not enter the building without prior approval of the Contracting Officer.

The existing buildings and their contents must be kept secure at all times. Provide temporary closures as required to maintain security as directed by the Contracting Officer.

Provide dust covers or protective enclosures to protect existing work that remains, and Government material located in the offices and hangar during the construction period.

Relocate movable furniture as required to perform the work, protect the furniture, and replace the furniture in its original location upon completion of the work. Leave attached equipment in place, and protect it against damage, or temporarily disconnect, relocate, protect, and reinstall it at the completion of the work.

The Government will remove and relocate other Government property in the areas of the building scheduled to receive work.

1.4 SECURITY REQUIREMENTS

Contract Clause FAR 52.204-2 Security Requirements and Alternate II and the following apply:

SECTION 01 14 00 Page 2

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 14 00 Page 3

SECTION 01 20 00

PRICE AND PAYMENT PROCEDURES

11/20, CHG 4: 08/24

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

1.2 CONTRACTOR'S INVOICE AND CONTRACT PERFORMANCE STATEMENT

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 20 00 Page 1

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

11/20, CHG 4: 08/24

PART 1 GENERAL

1.1 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.

U.S. ARMY CORPS OF ENGINEERS (USACE)

EM 385-1-1 (2024) Safety -- Safety and Occupational Health (SOH) Requirements

1.2 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

View Location Map

Progress and Completion Pictures

SD-04 Samples

Color Boards ; G

1.3 COLOR BOARDS

Submit five sets of color boards within 90 calendar days after Contract Award. Each set of boards must include samples of colors and finishes of interior surfaces, such as walls, floors, and ceilings. Present the samples on 8 by 10-1/2 inches boards (modules) with a maximum spread of 24 by 31-1/2 inches for foldouts. Design modules to fit in a standard loose-leaf, three-ring binder. Where special finishes such as architectural concrete, carpet, or prefinished textured metal panels are required, submit samples not less than 12 inches square with the board.

If more space is needed, more than one board per set may be submitted.

Certify that the color samples have been reviewed in detail, and that the color samples are in strict accordance with contract drawings and specifications, except as may be otherwise explicitly stated. Submittal of color samples does not relieve the Contractor of the responsibility to submit samples required elsewhere herein.

1.4 VIEW LOCATION MAP

Submit, prior to or with the first digital photograph submittals, a sketch or drawing indicating the required photographic locations. Update as required if the locations are moved.

SECTION 01 30 00 Page 1

1.5 PROGRESS AND COMPLETION PICTURES

Photographically document site conditions prior to start of construction operations. Provide monthly, and within one month of the completion of work, digital photographs, 1600x1200x24 bit true color minimum resolution in JPEG file format showing the sequence and progress of work. Take a minimum of 20 digital photographs each week throughout the entire project from a minimum of ten different viewpoints selected by the Contractor unless otherwise directed by the Contracting Officer. Submit with the monthly invoice two sets of digital photographs, each set on a separate compact disc (CD) or data versatile disc (DVD), cumulative of all photos to date. Indicate photographs demonstrating environmental procedures.

Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch on the CD or DVD as a digital file.

Include a date designator in file names. Photographs provided are for unrestricted use by the Government.

1.6 MINIMUM INSURANCE REQUIREMENTS

Provide the minimum insurance coverage required by FAR 28.307-2 Liability, during the entire period of performance under this contract. Provide other insurance coverage as required by New Jersey law.

1.7 SUPERVISION

1.7.1 Superintendent Qualifications

Provide project superintendent with a minimum of 15 years experience in construction with at least 5 of those years as a superintendent on projects similar in size and complexity. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as for the project superintendent. The Contracting Officer may request proof of the superintendent's qualifications at any point in the project if the performance of the superintendent is in question.

For projects where the superintendent is permitted to also serve as the Quality Control (QC) Manager as established in Section 01 45 00 QUALITY CONTROL, the superintendent must have qualifications in accordance with that section.

1.7.2 Minimum Communication Requirements

Have at least one qualified superintendent, or competent alternate, capable of reading, writing, and conversing fluently in the English language, on the job-site at all times during the performance of Contract work. In addition, if a Quality Control (QC) representative is required on the Contract, then that individual must also have fluent English communication skills.

1.7.3 Duties

The project superintendent is primarily responsible for managing subcontractors and coordinating day-to-day production and schedule adherence on the project. The superintendent is required to attend Red Zone meetings, partnering meetings, and quality control meetings. The

SECTION 01 30 00 Page 2 superintendent or qualified alternative must be on-site at all times during the performance of this contract until the work is completed and accepted.

1.7.4 Non-Compliance Actions

The Project Superintendent is subject to removal by the Contracting Officer for non-compliance with requirements specified in the contract and for failure to manage the project to ensure timely completion.

Furthermore, the Contracting Officer may issue an order stopping all or part of the work until satisfactory corrective action has been taken. No part of the time lost due to such stop orders is acceptable as the subject of claim for extension of time for excess costs or damages by the Contractor.

1.8 PRECONSTRUCTION

Immediately after award, prior to commencing any work at the site, coordinate with the Contracting Officer a time and place to meet for the Preconstruction. The must take place within 35 calendar days after award of the contract, but prior to commencement of any work at the site. The purpose of this is to discuss and develop a mutual understanding of the administrative requirements of the Contract including but not limited to:

daily reporting, invoicing, value engineering, safety, base-access, outage requests, hot work permits, schedule requirements, quality control, schedule of prices or earned value report, shop drawings, submittals, cybersecurity, prosecution of the work, government acceptance, final inspections and contract close-out. Contractor must present and discuss their basic approach to scheduling the construction work and any required phasing.

1.8.1 Attendees

Contractor attendees must include the Project Manager, Superintendent, Site Safety and Health Officer (SSHO), Quality Control Manager and major subcontractors.

1.9 FACILITY TURNOVER PLANNING MEETINGS (Red Zone Meetings)

Meet with the Government to identify strategies to ensure the project is carried to expeditious closure and turnover to the Client. Start planning the turnover process at the Pre-Construction Conference meeting with a discussion of the Red Zone process and convene at regularly scheduled NAVFAC Red Zone Meetings beginning at approximately 75 percent of project completion. Include the following in the facility Turnover effort:

1.9.1 Red Zone Checklist

a. Contracting Officer's Technical Representative (COTR) will provide the Contractor a copy of the Red Zone Checklist template.

b. Prior to 75 percent completion, modify the Red Zone Checklist template by adding or deleting critical activities applicable to the project and assign planned completion dates for each activity. Submit the modified Red Zone Checklist to the Contracting Officer. The Contracting Officer may request additional activities be added to the Red Zone Checklist at any time as necessary.

SECTION 01 30 00 Page 3

1.9.2 Meetings

a. Conduct regular Red Zone Meetings beginning at approximately 75 percent project completion, or three to six months prior to Beneficial Occupancy Date (BOD), whichever comes first.

b. The Contracting Officer will establish the frequency of the meetings, which is expected to increase as the project completion draws nearer.

At the beginning, Red Zone meetings may be every two weeks then increase to weekly towards the final month of the project.

c. Using the Red Zone Checklist as a Plan of Action and Milestones (POAM) and basis for discussion, review upcoming critical activities and strategies to ensure work is completed on time.

d. During the Red Zone Meetings discuss with the COTR any upcoming activities that require Government involvement.

e. Maintain the Red Zone Checklist by documenting the actual completion dates as work is completed and update the Red Zone Checklist with revised planned completion dates as necessary to match progress.

Distribute copies of the current Red Zone Checklist to attendees at each Red Zone Meeting.

1.10 PARTNERING

Host the partnering session within 45 calendar days of contract award. To most effectively accomplish this Contract, the Contractor and Government must form a cohesive partnership with the common goal of drawing on the strength of each organization in an effort to achieve a successful project without safety mishaps, conforming to the Contract, within budget and on schedule. The partnering team must consist of personnel from both the Government and Contractor including project level and corporate level leadership positions. Key Personnel from the supported command, end user, , Contractor, key subcontractors and the Designer of Record are required to participate in the Partnering process.

1.10.1 Facilitated (Formal) Partnering

a. Within 35 calendar days after award and prior to the start of work, host a Formal Partnering session with key personnel from the project team including both Contractor and Government personnel. All costs associated with the Partnering session including the third-party independent Facilitator Consultant, meeting room and other incidental items are the responsibility of the Contractor.

b. Before the Facilitated (Formal) Partnering session, coordinate with the Facilitator all requirements for incidental items (such as audio-visual equipment, easels, flipchart paper, colored markers, note pads, pens/pencils, colored flash cards) and have these items available at the Partnering session. Provide copies of any documents required for distribution to all attendees. Participants will bear their own costs for meals, lodging and transportation associated with Partnering .

c. The Initial Partnering Session must be a duration of one day and be held at a location off base as agreed to by the Contracting Officer.

Partnering session may take place concurrently with the Pre-Construction Meeting.

SECTION 01 30 00 Page 4

d. Facilitator must be experienced in conducting corporate Partnering sessions and must be a third-party independent facilitating consultant

- not an employee of the Contractor. The Facilitator is responsible for leading all aspects of the Partnering session necessary to achieve the Partnering goal.

e. An outcome of the Partnering session must be an escalation matrix agreed upon by both the Government and Contractor, which identifies key Government and Contractor decision makers by name and anticipated decision durations.

f. Host follow-on Partnering Sessions at three- to six-month intervals or more frequently if needed and lasting generally a half day or less.

Attendees need only be those required to resolve current issues. The same Facilitator used in the Initial Partnering session must lead the follow-on sessions unless an alternative is permitted by the Contractor Officer. All costs associated with follow-on Partnering sessions are the responsibility of the Contractor.

1.10.2 Team-Led (Informal) Partnering

a. The Contracting Officer will coordinate the initial Team-Led (Informal) Partnering Session with key personnel of the project team, including Contractor and Government personnel. The Partnering Session will be co-led by the Government Construction Manager and Contractor's Project Manager.

b. The Initial Team-led Partnering session may be held concurrently with the Pre-Construction meeting. Partnering sessions will be held at a location mutually agreed to by the Contracting Officer and the Contractor, typically at a conference room on-base or at the Contractor's temporary trailer.

c. The Initial Team-Led Partnering Session will be conducted and facilitated using electronic media (a video and accompanying forms) provided by Contracting Officer.

d. The Partners will determine the frequency of the follow-on sessions.

e. Participants will bear their own costs for meals, lodging and transportation associated with Partnering.

1.11 MOBILIZATION

Contractor shall mobilize to the jobsite within 60 calendar days after contract award . Mobilize is defined as having equipment AND having a physical presence of at least one person from the contractor's team on the jobsite.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 30 00 Page 5

SECTION 01 30 00 Page 6

SECTION 01 31 20

PROJECT TECHNICAL DATA MANAGEMENT AND VISUALIZATION

05/22

PART 1 GENERAL

1.1 MEASUREMENT AND PAYMENT

1.1.1 Develop The Data Management System

1.1.1.1 Payment

Payment will be made for development and delivery of products to provide a complete and fully functioning data management system, as specified herein and in the Contract documents including required preconstruction submittals, complete construction and testing of the enterprise database (EDB), all components of the a functional SFTP site, data management planning meeting completion, delivery of the initial training session, and approval of the quick reference guide. Related costs include, but are not limited to, uploading of all existing data as provided by the Government into the data management system, , and including incidental items per the Contract documents. All incidental costs associated with the performance of work in this section are included in the Contract price. The Government will make no additional separate payment for items included herein or by reference.

1.1.1.2 Measurement

Measurement for payment of DEVELOP THE DATA MANAGEMENT SYSTEM will be paid in one lump sum. Payment for the data management system will be made after completion of the following work:

a. The data management staff have been submitted and approved,

b. All preconstruction submittals have been submitted and approved,

c. The data management planning meeting with the Government has been conducted,

d. The 100 Percent Data Management Plan (and all related addenda) submitted and approved,

e. The initial training session has been conducted, and the quick reference guide submitted and approved, and

f. The database, being fully developed to 95 percent including all available design features and historical project data loaded to the system, as submitted/demonstrated by the Contractor and approved by the Government. The five percent will account for any changes needed just prior to the start of work for which various components of the system has been built, or testing required to be conducted once initial data has been received.

1.1.1.3 Unit of Measurement

Unit of Measurement: Lumps Sum (Ea).

SECTION 01 31 20 Page 1

1.1.2 Maintain The Data Management System And Turnover Of Final Products

1.1.2.1 Payment

Payment will be made on a monthly basis for the maintenance of the data management system in a fully functional state with 24/7 accessibility by the Government, and up to date as specified in PART 1, "Data Turnover Timeframes". This includes the enterprise database, SFTP site to be up to date (as defined by the turnover time requirements) at all times, and timely resolution of any issues with data correctness, completeness or other quality control measures identified by the Government as defined in this contract.

These payments include the timely submittal of all required data, progress drawings, periodic as-built updates, and reports - as required by this and other sections of the Contract - throughout the Contract duration. This item includes all required support staff. This item also includes all final turnover items detailed in Part Three, FINAL EDB TURNOVER, PART 1, SUBMITTALS, SD-11 CLOSEOUT SUBMITTALS, and throughout this section. An amount not to exceed 10 percent of the total payments may be withheld if the Contractor fails to perform the required work. All incidental costs associated with the performance of work in this section are included in the Contract price. The Government will make no additional separate payment for items included herein or by reference.

1.1.2.2 Measurement

Measurement of payment for MAINTAIN THE DATA MANAGEMENT SYSTEM AND TURNOVER OF FINAL PRODUCTS will be made monthly for work completed and submitted as described above for the duration of the Contract activities for which the data management system applies.

1.1.2.3 Unit of Measure

Monthly (Mo) for the number of months which data management work is ongoing.

1.2 DEFINITIONS

1.2.1 Data

A representation of facts, concepts or instructions in a structured, semi-structured or unstructured format, suitable for processing and interpretation by humans or machines. Records generated by any activities related to features of construction detailed in this Contract or by any instrumentation or monitoring equipment or processes in use on the project. Includes raw data generated by automated collection systems, recorded manually on paper or tablets, and data tables and databases and their constituent records which can be used with custom or off-the-shelf software.

1.2.2 Data Cleaning

The process of preparing data for analysis by correcting or qualifying data that is incorrect, incomplete, irrelevant, duplicated, or improperly formatted.

SECTION 01 31 20 Page 2

1.2.3 Data Management

The identification, definition, collection, organization, verification, correction, storage, protection, processing, communication, and transfer of data in order to maintain project records in an organized, complete, and rapidly accessible archive for immediate and future use.

1.2.4 Data Management System (DMS)

The hardware, software and network components, architecture, policies, technical processes, and workflows that efficiently manage data and information for the duration of the contract-required activities.

1.2.5 Data Validation/Verification

The process of checking the accuracy and quality of source data before using, importing or otherwise processing data. The same process as data QA or QC. One form of data cleaning.

1.2.6 Documented Enterprise Database (EDB)

A relational database hosted on a server that is utilized to contain, organize, and relate large collections of data stored in individual tables. Capable of handling a range of 100 or more users at a time, and running queries of multiple users simultaneously. A database that is "documented" has detailed written documentation of the schema, in which all items from DEFINITIONS "Schema" are provided in table format, as well as an accompanying entity relationship diagram supplemented with explanatory text.

1.2.7 Metadata

A set of data that gives information about data. For geospatial data this includes information about the feature or dataset location in space (i.e.

datums, projections, resolution, collection resolution and accuracy, and other common requirements), entered into the appropriate form in the GIS software platform; as well as information about the data attributes (units, assumptions, sources, and other common information). File metadata are stored in a text file with the same name as the target file.

Database metadata are stored in table descriptions or in appropriately labeled metadata fields.

1.2.8 Report

Any data or information in a format designed for human communication, where file format is not tabular but comprised of conceptual narrative, formatted tables, or static visualizations, and the contained data is either static or requires conversion to other file formats or manual cleaning or entry for aggregation, processing and analysis by machines.

1.2.9 Schema

Also referred to as "database schema", it is the logical structure of the of the database. Schema consists of the following database elements:

(1) Table definitions and names;

(2) Field names;

(3) Field definitions;

(4) Field types (constraints), including precision and units for

SECTION 01 31 20 Page 3 numeric fields;

(5) Primary and Foreign Keys (to determine table relationships);

(6) Field default values;

(7) Domains;

(8) Calculated fields and the calculations and equations to produce values that populate them;

(9) Selected database views required to produce values displayed in the web interface, used to derive reports, for ongoing CAD/GIS feature generation, or as requested by the COR.

1.2.10 Secure File Transfer Protocol (SFTP)

Also SSH File Transfer Protocol, a networked protocol to handle file transfers between computers over the internet. It provides file transfer, access and management over a secure connection communicating on server data port 22. This should not be confused with similarly-named "Simple File Transfer Protocol" which operates on server data port 115, and does not meet the requirements of an SFTP site for the purpose of this contract.

1.2.11 Tabular Data

Any structured or semi-structured numerical or qualitative facts in a character-limited field and record format. Suitable for processing by machines with minimal human interpretation, cleaning or processing, and in a file format suitable for importing into a database software program without any structural changes to the file.

1.2.12 Tag

A keyword or term applied to a computer file that is stored in the file metadata that can aid in searching for that file or document. Most commonly used with files such as imagery to aid in computer-based searching.

1.3 ADMINISTRATIVE REQUIREMENTS

1.3.1 Data Management Planning Meeting

Hold a collaborative meeting with the Contracting Officer (COR) within 15 days of the approval of all applicable SD-01 submittals. This collaborative effort will consist of a meeting over 4 full consecutive business days, where primary Contractor and data management Contractor (if subcontracted) each provide in-person attendance. The data manager, and data management QC must physically attend this meeting with COR in order to facilitate the building of rapport and efficient communication. Additionally, personnel from each subcontractor having technical knowledge of data collection and processing for that subcontractor's features of work must also attend this meeting in person during designated days to be decided in the agenda. The meeting must not take place until submittals from paragraph SUBMITTALS - SD-01 are received and approved including:

(1) 50 Percent Data Management Plan

(2) Automated and Manual Data Collection Output Examples

(3) Data Cleaning and Verification Plan

(4) QC Data Collection Plan

(5) Backups, Archiving And Disaster Recovery Plan

(6) Data Transfer Workflow

(7) Data Management System Demobilization Plan

SECTION 01 31 20 Page 4

The goals of this meeting are:

a. To provide a venue for problem-solving on data requirements and workflows;

b. Discuss and decide on needed changes to the database schema;

d. Discuss and provide feedback on the SFTP file organization structure;

e. Discuss and resolve any Government questions about Contractor workflows as detailed in submittals;

f. Presentation and discussion of any Contractor-proposed changes to methods of execution;

g. Development of field data collection app form formats and associated products (if applicable);

h. Collaborate to support the Contractor in submittal of a 100 Percent Data Management Plan that meets the Government's expectations -including documentation of all requested or agreed changes to facilitate completion of the 100 Percent Data Management Plan submittal;

i. To establish a working rapport between all data management personnel;

j. To communicate and clarify the specific goals and expectations of the Government with respect to any part of the data management system.

1.3.2 Additional Planning Meetings

An additional data management planning meeting specifically for the Concrete Placement is required no later than 30 days prior to the start of work on that feature. For any feature of work where the data-generating Contractor will not be on site, and specific data-generating equipment will not be detailed until the start of that work which would affect the data management system, hold a specific data management planning meeting no later than 30 days prior to the start of work on that feature. These delayed coordination meetings must be of at least 4 hours duration (or as directed by COR) and must not be combined with other kickoff or coordination meetings. All the same personnel are required to be in attendance as the initial data management planning meeting.

1.3.3 Coordination and Technical Meetings

The Contractor's Data Manager, or another employee that can act competently on their behalf, must participate in recurring data management technical meetings as needed, scheduled at COR request. These meetings will be critical prior to, and at the start of work for which intensive or voluminous data collection will take place, but are not intended to be ongoing weekly throughout the entire project. For bidding purposes assume monthly meetings for the duration of work. Conduct these meetings in order to ensure the timely and adequate collection, formatting, quality, and flow of data from site to the EDB, SFTP site, and web interface, and to troubleshoot any recurring problems. These meetings are also a venue for collaboration to solve technical problems, make data management progress updates, give feedback, and make technical decisions about data.

Include high level data management updates in the overall weekly

SECTION 01 31 20 Page 5 coordination meeting for the project.

1.4 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

50 Percent Data Management Plan ; G

Automated and Manual Data Collection Output Examples ; G

Data Cleaning and Verification Plan ; G

QC Data Collection Plan ; G

QC Daily Information Collection Plan ; G

Backups, Archiving And Disaster Recovery Plan ; G

Data Transfer Workflow ; G

Data Management System Demobilization Plan ; G

100 Percent Data Management Plan ; G

Proposed Changes To The Enterprise Database Schema ; G

Quick Reference Guide ; G

System Testing ; G

SD-05 Design Data

SD-06 Test Reports

Photograph PDF'S ; G

Digital Photographs ; G

Database Files ; G

SD-07 Certificates

Data Manager ; G

SECTION 01 31 20 Page 6

SD-10 Operation and Maintenance Data

Data Management Plan Updates ; G

Data Transfer and QC Reports ; G

Ongoing Schema Updates ; G

SD-11 Closeout Submittals

Data Management System Demobilization Plan Updates ; G

Finalized Enterprise Database ; G

Final File Indexes ; G

Data Management Manual ; G

1.5 PERSONNEL

1.5.1 Qualifications 1.5.1.1 Data Manager

The data manager must have the following verifiable credentials:

a. Have a minimum of 5 years of advanced experience occurring in the past 8 years overseeing the import, cleaning, verification, processing, storage, backup and scripted transfer of construction data, similar to the type that will be generated by work in the contract.

b. Have a minimum of 5 years' experience occurring in the past 5 years designing and editing enterprise databases.

c. Have served as the data manager on at least two construction projects of similar complexity, with similar data production volume and data management requirements. Each project should be described in the resume detailing the data management tasks performed.

d. Be approved by the COR before any data is transferred into the EDB.

Submit the resume for approval within 15 calendar days after notice to proceed.

1.5.2 Roles and Responsibilities 1.5.2.1 Data Manager

The Data Manager is responsible for:

a. Population, maintenance, quality control, and oversight of the Contractor's Data Management System and components;

b. Coordination with data collection professionals from the primary Contractor and sub-contractors, QC personnel, and other parties

SECTION 01 31 20 Page 7 performing work on and offsite as necessary to obtain data;

c. Automated and manual input of data into the enterprise database (EDB);

d. Ensuring all data generated physically or digitally during construction is captured, converted, cleaned, validated, QC-checked, and organized in the appropriate tabular and non-tabular formats as described in this specification;

e. Coordination with all other data management personnel to ensure data flows efficiently from site to database to visualizations or other end use;

f. Scripting of autogenerated reports required in this specification;

g. Automated and manual transfer of database .csv and backup files, non-tabular files, raw data, and all other documents to the SFTP site within the specified turnover timeframes;

h. Develop and oversee the processes for QC review of data entered into the EDB as required by this specification;

i. Develop and oversee the processes for backups of data as required by this specification;

j. Participate in all data-related technical meetings and report and speak on technical data matters when requests are made by the Government.

k. Author and compile the data management plans and other data-related submittals.

l. Provide username and password access to platforms required by this specification including the web interface and SFTP site, and any web applications utilized;

m. Work with the Data Management QC to develop and incorporate the workflows for integrating QC data into the data management system (via digital collection methods and automated transfer processes as applicable);

n. Design forms for QA digital data collection and processes to facilitate direct input of data by the Government to the database (as applicable).

o. All other data management tasks not specifically assigned.

If the Data Manager does not know how to execute any part of the technical processes needed to accomplish any work specified, provide them with the appropriate training. Provide training within 30 days of the data management kickoff meeting.

1.6 EXISTING DATA

The Government will provide existing data for use by the Government in the data management system including but not limited to boring logs, CAD drawings, and GIS feature classes and rasters. The Government will provide all files via the SFTP site once it has been established.

SECTION 01 31 20 Page 8

1.7 DATA REQUIREMENTS

1.7.1 Data Integrity

Maintain integrity of data such that records are accurate and internally consistent, that all data and records reflect the quality of the data gathered on the site, and that all data is preserved and archived for future use.

1.7.2 Data Ownership

All data generated on-site by instrumentation, monitoring, anchorage, excavation, construction equipment, sampling, concrete and soil testing, grouting, blasting, surveying, concrete production, conveyance and placement, tunneling, mapping, cutoff wall construction, equipment calibration, maintenance, and all other data associated with the work performed is the property of the Government. All calculations and formulae and any constants or variables used to produce data, reports, or analytical products are the property of the Government and must be included in any required database fields, and turned over in an editable or otherwise specified format upon request.

For any data to be excluded from the system, submit a written request for a Government determination of whether data can be classified as proprietary, along with a detailed justification. No data source is exempt from these data requirements unless a specific exemption is requested of and granted in writing by the COR. Under no circumstances will "proprietary data" impede the Government's ability to monitor construction, perform analyses, or evaluate the effectiveness of construction.

1.7.2.1 Custom Algorithms

If software developed by or for the Contractor will be used for processing of data provided to the Government, detail to the Government the algorithms and procedures used to process the data. The Contractor maintains ownership of its computer code, unless otherwise specified, but must allow the Government access to the algorithms (with all values/variables defined) and procedures to verify how the data is processed so that the quality of the final data can be assessed.

1.7.3 Disclosure of Data or Advertisement of Project

Do not disclose any project data to third parties, and do not publish any data without prior written approval of the COR. Request and receive permission in writing prior to publishing or presenting any data from the project to any third parties not associated with this contract, this includes data with project references removed. If the data management system is the subject of any Contractor-produced papers, proper design credit must be explicitly attributed to the Government's data management designers, as well as appropriate Contractor/subcontractor personnel.

1.7.4 Backups, Archiving and Disaster Recovery

Avoid data loss by backup and archival of all digital and paper data records from the time of data generation until final data turnover. This includes having specific policies, workflows, and infrastructure in place to archive and have redundant backups on servers in either a commercial cloud computing platform or multiple locations according to industry

SECTION 01 31 20 Page 9 standard practice. Address backups, archiving and disaster recovery plans in the appropriate submittal, as specified in paragraph SUBMITTALS, SD-01 Preconstruction Submittals.

If a data loss occurs, the Contractor is responsible for regeneration of the data. Any data which are re-generated from a non-primary source must be clearly noted in the record as shown in the EDB. Backup data within 24 hours of generation. Should a data loss occur, even if is within this 24-hour window, the Contractor is responsible for all steps necessary to recover from this data loss and will receive no additional payment for these data recovery efforts. Notify the COR of any data loss in writing within 12-hours of discovery that it has occurred.

1.7.5 Contractor Quality Control of Technical Data Including Metadata

Verify and perform cleaning (see definitions provided in paragraph DEFINITIONS) of all tabular data entered into the databases including at a minimum:

(1) Verification of completeness of records such that all records are completed with all data within required turnover times;

(2) Correction of entry errors;

(3) Verification of source field data;

(4) Data review for verification of entry correctness;

(5) Consistency and accuracy of naming convention;

(6) Consistency and accuracy of field formats;

(7) Standardized character entry of fields and records, for example consistent use of spelling, capitalization, spaces and special characters (where allowed);

(8) Entry of required QC or correction metadata associated with the records (per paragraph RECORD TRACKING REQUIREMENTS).

Conduct this process in accordance with all procedures and policies outlined in the submitted and approved "Data Cleaning and Verification Plan" in paragraph SUBMITTALS, SD-01 Preconstruction Submittals. See paragraph DATA TURNOVER TIMEFRAMES for turnover time requirements.

1.7.6 Raw Data Requirements

1.7.6.1 Digital Raw Data

Submit raw digital data files for any data gathering system used on the project in accordance with the following:

a. Provide these files in a format readable by the current version (at the time of the contract) of Microsoft Excel, such as a tab-delimited ASCII file, a CSV file, or other format readable by MS Excel.

b. To the extent possible, use data gathering systems that will generate "non-proprietary" or industry standard format data files readable in ASCII, CSV or with Microsoft Excel. Any necessary export or conversion, or software required to perform conversions, will be completed at the Contractor's expense.

c. Label all data columns so that it is apparent what data they contain, and provide metadata to COR including units, any formulae used to calculate the data, and any criteria used to generate the data.

Detail metadata for these files in the Data Management Plan or in addenda to that plan as appropriate.

SECTION 01 31 20 Page 10

d. Where these files as generated are not directly readable by Microsoft Excel, submit raw data to the COR in their raw format and in a second file created in Microsoft Excel with column headings that include units.

e. Detect and correct any inconsistencies, mistakes, missing records or fields, or other anomalies in the data that may be generated through use of automated data collection systems - including but not limited to the automated grout monitoring and data collection system, and the instrumentation data collections system. Provide a written explanation of the nature and cause of any anomalies, and any corrected records within 48 hours of the resolution of the anomaly.

Paragraph RECORD TRACKING REQUIREMENTS, Items 7-9 apply to corrections made as required in this section.

f. All data columns must be labeled so that it is apparent what data they contain, and metadata provided to COR including units, any formulae used to calculate the data, and any criteria used to generate the data. Metadata for these files must be detailed in the Data Management Plan or in addenda to that plan as appropriate. For all files with the same structure, metadata may be provided for the set of data documents and is not required for every single file. Data included in the EDB data tables from these raw data sources may be uploaded from the data source to minimize any duplicate data entry of tracking data.

1.7.6.2 Analog Raw Data

Submit clear, complete, readable, center-justified digital scans or photographs of all analog raw data collected for the project in accordance with the following requirements:

a. All analog reports of raw data must be scanned and transferred to the Government via the Secure File Transfer Protocol (SFTP) site within 24 hours of generation in the field.

b. Any data collected via manual methods must be entered into the database by the Contractor within 48 hours of field generation.

Analog data entered in the database must include a field in the appropriate table of the database with a hyperlink to the scan of the analog file for URL referencing. Ensure coordinate X, Y, and Z of features are included for any data collected by analog methods and entered into the database table for the associated record.

c. Handwriting and scan quality must be clear and legible, and contain any related information needed to place the data in context, to which the raw data pertains.

d. Scanned digital files must be named according to the approved naming convention, and stored in the appropriate location of the SFTP according to the file structure organization provided in the attachments.

e. Adjust data collection forms utilized at any time at COR request.

1.7.7 Data Turnover Timeframes

Provide all data from any automated data gathering system or manual

SECTION 01 31 20 Page 11 collection system which is not otherwise described specifically in the feature of work sections, or this section, according to the following requirements:

Data Format Turnover Time Turnover Location Section

Raw Data Files 24 hours SFTP a

Converted Raw Data Files 24 hours SFTP b

Reports 24 hours SFTP c

Generated Data as required by data dictionary

24 hours EDB/Dynamic Data Interface c

Appended QC Data 48 hours EDB/Dynamic Data Interface d

QC Data collected synchronously to work

24 hours EDB/Dynamic Data Interface d

Instrumentation Readings - Automated 10 mins Field Interface/Dynamic Data Interface e

Instrumentation Readings - Manual 1 hour - or as directed by COR

USGS/MIDAS

database as directed by COR /Dynamic Data Interface e

Cofferdam Piezometer Readings collect hourly

24 hours

EDB f

Seismograph 10 mins Seismic Website f

Concrete Thermal 10 mins Concrete Thermal Data Website f

QC Verification of Data 72 hours EDB g

Metadata 72 hours EDB g

GIS Project Package (.aprx) 24 hours when updated

SFTP h

ESRI Geodatabase (.gdb) 24 hours when updated

SFTP h

Enterprise Database Tables (.csv) 24 hours SFTP

Enterprise Database backup files Quarterly SFTP

a. Submit all raw data within 24 hours of data collection to the COR via

SECTION 01 31 20 Page 12 the SFTP site.

b. If conversion of this raw data is necessary in order for it to be readable by Microsoft Excel, submit this converted raw data file within 24 hours of data collection.

c. Transfer all non-tabular files (as defined in Part One, DEFINITIONS "REPORT") to the SFTP site within 24 hours of submittal to RMS unless otherwise stated elsewhere in the Contract.

d. Import data records into the Enterprise Database (EDB) within 24 hours of generation.

e. Enter or append, as applicable, QC data collected after the initial generation of data for a given…