Performance Specifications - W912EQ21B0003-Amended.pdf

SECTION 01 45 00.15 10 Page 1

PART 1

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 45 00.15 10

RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM)

GENERAL

1.1 REFERENCES

1.2 MEASUREMENT AND PAYMENT

1.3 CONTRACT ADMINISTRATION

1.3.1 Correspondence and Electronic Communications

1.3.2 Other Factors

1.4 RMS SOFTWARE

1.5 SYSTEM REQUIREMENTS

1.6 CONTRACT DATABASE - GOVERNMENT

1.7 CONTRACT DATABASE - CONTRACTOR

1.7.1 Administration

1.7.1.1 Contractor Information

1.7.1.2 Subcontractor Information

1.7.1.3 Correspondence

1.7.1.4 Equipment

1.7.1.5 Reports

1.7.1.6 Request For Information (RFI)

1.7.2 Finances

1.7.2.1 Pay Activity Data

1.7.2.2 Payment Requests

1.7.3 Quality Control (QC)

1.7.3.1 Quality Control (QC) Reports

1.7.3.2 Deficiency Tracking.

1.7.3.3 Three-Phase Control Meetings

1.7.3.4 Labor and Equipment Hours

1.7.3.5 Accident/Safety Reporting

1.7.3.6 Definable Features of Work

1.7.3.7 Activity Hazard Analysis

1.7.4 Submittal Management

1.7.5 Schedule

1.7.6 Closeout

SECTION 01 45 00.15 10 Page 1

1.8 IMPLEMENTATION

1.9 NOTIFICATION OF NONCOMPLIANCE

PART 2 PRODUCTS

PART 3 EXECUTION

-- End of Section Table of Contents --

SECTION 01 45 00.15 10 Page 3

SECTION 01 45 00.15 10

RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM)

PART 1 GENERAL

1.1 REFERENCES

The publications listed below form a part of this section 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 (2014) Safety and Health Requirements Manual

1.2 MEASUREMENT AND PAYMENT

The work of this section is not measured for payment. The Contractor is responsible for the work of this section, without any direct compensation other than the payment received for contract items.

1.3 CONTRACT ADMINISTRATION

The Government will use the Resident Management System (RMS) to assist in its monitoring and administration of this contract. The Government accesses the system using the Government Mode of RMS (RMS GM) and the Contractor accesses the system using the Contractor Mode (RMS CM). The term RMS will be used in the remainder of this section for both RMS GM and RMS CM. The joint Government-Contractor use of RMS facilitates electronic exchange of information and overall management of the contract. The Contractor accesses RMS to record, maintain, input, track, and electronically share information with the Government throughout the contract period in the following areas:

Administration Finances Quality Control Submittal Monitoring Scheduling Closeout Import/Export of Data

1.3.1 Correspondence and Electronic Communications

For ease and speed of communications, exchange correspondence and other documents in electronic format to the maximum extent feasible. Some correspondence, including pay requests and payrolls, are also to be provided in paper format with original signatures. Paper documents will govern, in the event of discrepancy with the electronic version.

1.3.2 Other Factors

Other portions of this document have a direct relationship to the reporting accomplished through RMS. Particular attention is directed to Contract Clause, 52.236-15 "Schedules for Construction Contracts"; Contract Clause, 52.232-27 "Prompt Payment for Construction Contracts"; Contract

SECTION 01 45 00.15 10 Page 4

Clause, 52.232-15 "Payments Under Fixed-Priced Construction Contracts"; Section 01 32 01.00 10 PROJECT SCHEDULE; Section 01 33 00 SUBMITTAL PROCEDURES; Section 01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS; and Section 01 45 00.00 10 QUALITY

CONTROL.

1.4 RMS SOFTWARE

RMS is a Windows-based program that can be run on a Windows-based PC meeting the requirements as specified in paragraph SYSTEM REQUIREMENTS. Download, install and be able to utilize the latest version of the RMS software within 7 calendar days of receipt of the Notice to Proceed. RMS software, user manuals, access and installation instructions, program updates and training information are available from the RMS website ( http://rmsdocumentation.com). The Government and the Contractor will have different access authorities to the same contract database through RMS. The common database will be updated automatically each time a user finalizes an entry or change.

1.5 SYSTEM REQUIREMENTS

The following is the recommended system configuration to run the Contractor Mode RMS for full utilization of all features for all types and sizes of contracts. Smaller, less complicated, projects may not require the configuration levels described below. Required configuration also noted below.

Recommended RMS System Requirements

Hardware

Windows-based PC 1.7 GHz i3; AMD A6 3650 GHz or higher processor (REQUIRED)

RAM 8 GB

Hard drive disk 100 GB space for sole use by RMS system

Monitor Screen resolution 1366 x 768

Mouse or other pointing device

Windows compatible printer Laser printer must have 4 MB+ of RAM

Connection to the Internet minimum 4 Mbs per user

Software

MS Windows Windows 7 x 64 bit (RMS requires 64 bit O/S) or newer (REQUIRED)

Word Processing software Viewer for MS Word 2013, MS Excel 2013 or newer (REQUIRED)

E-mail MAPI compatible (REQUIRED)

Recommended RMS System Requirements

Virus protection software Regularly upgraded with all issued Manufacturer's u updates and is able to detect most zero day viruses (REQUIRED) http://rmsdocumentation.com/

SECTION 01 45 00.15 10 Page 5

1.6 CONTRACT DATABASE - GOVERNMENT

The Government will enter the basic contract award data in RMS prior to granting the Contractor access. The Government entries into RMS will generally be related to submittal reviews, correspondence status, and Quality Assurance (QA) comments, as well as other miscellaneous administrative information.

1.7 CONTRACT DATABASE - CONTRACTOR

Contractor entries into RMS establish, maintain, and update data throughout the duration of the contract. Contractor entries generally include prime and subcontractor information, daily reports, submittals, RFI's, schedule updates and payment requests. RMS includes the ability to import attachments and export reports in many of the modules, including submittals. The Contractor responsibilities for entries in RMS typically include the following items:

1.7.1 Administration

1.7.1.1 Contractor Information

Enter all current Contractor administrative data and information into RMS within 7 calendar days of receiving access to the contract in RMS. This includes, but is not limited to, Contractor's name, address, telephone numbers, management staff, and other required items.

1.7.1.2 Subcontractor Information

Enter all missing subcontractor administrative data and information into RMS CM within 7 calendar days of receiving access to the contract in RMS or within 7 calendar days of the signing of the subcontractor agreement for agreements signed at a later date. This includes name, trade, address, phone numbers, and other required information for all subcontractors. A subcontractor is listed separately for each trade to be performed.

1.7.1.3 Correspondence

Identify all Contractor correspondence to the Government with a serial number. Prefix correspondence initiated by the Contractor's site office with "S". Prefix letters initiated by the Contractor's home (main) office with "H". Letters are numbered starting from 0001. (e.g., H-0001 or S-0001). The Government's letters to the Contractor will be prefixed with "C" or "RFP".

1.7.1.4 Equipment

Enter and maintain a current list of equipment planned for use or being used on the jobsite, including the most recent and planned equipment inspection dates.

1.7.1.5 Reports

Track the status of the project utilizing the reports available in RMS. The value of these reports is reflective of the quality of the data input. These reports include the Progress Payment Request worksheet, Quality Control (QC) comments, Submittal Register Status, and Three-Phase Control worksheets.

1.7.1.6 Request For Information (RFI)

Create and track all Requests For Information (RFI) in the RMS Administration Module for Government review and response.

SECTION 01 45 00.15 10 Page 6

1.7.2 Finances

1.7.2.1 Pay Activity Data

Develop and enter a list of pay activities in conjunction with the project schedule. The sum of pay activities equals the total contract amount, including modifications. Each pay activity must be assigned to a Contract Line Item Number (CLIN). The sum of the activities assigned to a CLIN equals the amount of each CLIN.

1.7.2.2 Payment Requests

Prepare all progress payment requests using RMS. Update the work completed under the contract at least monthly, measured as percent or as specific quantities. After the update, generate a payment request and prompt payment certification using RMS. Submit the signed prompt payment certification and payment request as well as supporting data either electronically or by hard copy. Unless waived by the Contracting Officer, a signed paper copy of the approved payment certification and request is also required and will govern in the event of discrepancy with the electronic version.

1.7.3 Quality Control (QC)

Enter and track implementation of the 3-phase QC Control System, QC testing, transferred and installed property and warranties in RMS. Prepare daily reports, identify and track deficiencies, document progress of work, and support other Contractor QC requirements in RMS. Maintain all data on a daily basis. Insure that RMS reflects all quality control methods, tests and actions contained within the Contractor Quality Control (CQC) Plan and Government review comments of same within 7 calendar days of Government acceptance of the CQC Plan.

1.7.3.1 Quality Control (QC) Reports

The Contractor's Quality Control (QC) Daily Report in RMS is the official report. The Contractor can use other supplemental formats to record QC data, but information from any supplemental formats are to be consolidated and entered into the RMS QC Daily Report. Any supplemental information may be entered into RMS as an attachment to the report. QC Daily Reports must be finalized and signed in RMS within 24 hours after the date covered by the report. Provide the Government a printed signed copy of the QC Daily Report, unless waived by the Contracting Officer.

1.7.3.2 Deficiency Tracking.

Use the QC Daily Report Module to enter and track deficiencies. Deficiencies identified and entered into RMS by the Contractor or the Government will be sequentially numbered with a QC or QA prefix for tracking purposes. Enter each deficiency into RMS the same day that the deficiency is identified. Monitor, track and resolve all QC and QA entered deficiencies. A deficiency is not considered to be corrected until the Government indicates concurrence in RMS.

1.7.3.3 Three-Phase Control Meetings

Maintain scheduled and actual dates and times of preparatory and initial control meetings in RMS.

Worksheets for the three-phase control meetings are generated within RMS.

SECTION 01 45 00.15 10 Page 7

1.7.3.4 Labor and Equipment Hours

Enter labor and equipment exposure hours on a daily basis. Roll up the labor and equipment exposure data into a monthly exposure report.

1.7.3.5 Accident/Safety Reporting

Both the Contractor and the Government enter safety related comments in RMS as a deficiency.

The Contractor must monitor, track and show resolution for safety issues in the QC Daily Report area of the RMS QC Module. In addition, follow all reporting requirements for accidents and incidents as required in EM 385-1-1, Section 01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS and as required by any other applicable Federal, State or local agencies.

1.7.3.6 Definable Features of Work

Enter each feature of work, as defined in the approved CQC Plan, into the RMS QC Module. A feature of work may be associated with a single or multiple pay activities, however a pay activity is only to be linked to a single feature of work.

1.7.3.7 Activity Hazard Analysis

Import activity hazard analysis electronic document files into the RMS QC Module utilizing the document package manager.

1.7.4 Submittal Management

Enter all current submittal register data and information into RMS within 7 calendar days of receiving access to the contract in RMS. The information shown on the submittal register following the specification Section 01 33 00 SUBMITTAL PROCEDURES will already be entered into the RMS database when access is granted. Group electronic submittal documents into transmittal packages to send to the Government, except very large electronic files, samples, spare parts, mock ups, color boards, or where hard copies are specifically required. Track transmittals and update the submittal register in RMS on a daily basis throughout the duration of the contract. Submit hard copies of all submittals unless waived by the Contracting Officer.

1.7.5 Schedule

Enter and update the contract project schedule in RMS by either manually entering all schedule data or by importing the Standard Data Exchange Format (SDEF) file, based on the requirements in Section 01 32 01.00 13 PROJECT SCHEDULE.

1.7.6 Closeout

Closeout documents, processes and forms are managed and tracked in RMS by both the Contractor and the Government. Ensure that all closeout documents are entered, completed and documented within RMS.

1.8 IMPLEMENTATION

Use of RMS as described in the preceding paragraphs is mandatory. Ensure that sufficient resources are available to maintain contract data within the RMS system. RMS is an integral part of the Contractor's required management of quality control.

1.9 NOTIFICATION OF NONCOMPLIANCE

SECTION 01 45 00.15 10 Page 8

Take corrective action within 7 calendar days after receipt of notice of RMS non-compliance by the Contracting Officer.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

-- End of Section --

Mississippi River and Harbors Contract (Mile 48 UMR) to Mississippi (mile

537 AHP)

SECTION 35 20 23.33 Page 3

SECTION 35 20 23.33

NATIONAL DREDGING QUALITY MANAGEMENT PROGRAM

PART 1 GENERAL

1.1 DESCRIPTION

The work under this contract requires use of the US Army Corps of Engineers

(USACE) National Dredging Quality Management Program (DQM) to monitor the dredge's status at all times during the contract duration and manage data history. This performance-based specification section identifies the minimum required output as well as the precision and instrumentation requirements. The requirements may be satisfied using equipment and technical procedures selected by the Contractor.

1.2 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office responsible for review of the submittal for the Government. The following shall be submitted in accordance with Section 01 33 00, "Submittal

Procedures":

SD-01, Preconstruction Submittals

Dredge Plant Instrumentation Plan Revisions; G, OM

SD-07, Certificates

Letter of National Dredging Quality Management Program

Certification; G, EDC

1.3 MEASUREMENT AND PAYMENT

No separate measurement or payment will be made for the installation, operation, and maintenance of the DQM-certified system as specified herein for the duration of the dredging operations. All costs in connection therewith shall be considered a subsidiary obligation of the Contractor and shall be included in the applicable contract price for Dredging.

1.4 NATIONAL DREDGING QUALITY MANAGEMENT PROGRAM CERTIFICATION

The Contractor shall have a current certification from the DQM Program for the cutter/suction head hydraulic dredge instrumentation system to be used under this contract. Standard Operating Procedures (SOP) and criteria for certification are presented on the DQM website at https://dqm.usace.army.mil.

SECTION 35 20 23.33 Page 4

1.5 DREDGE PLANT INSTRUMENTATION PLAN (DPIP)

The Contractor shall have a digital copy of the Dredge Plant

Instrumentation Plan (DPIP) on file with the DQM Support Center. While working on site, the Contractor shall also maintain on the dredge a copy of the DPIP, which is easily accessible to Government personnel at all times.

This document shall accurately describe the sensors used, the configuration of the system, how sensor data will be collected, how quality control on the data will be performed, and how the sensors/data-reporting equipment will be calibrated and repaired if it fails. A description of the computed dredge-specific data and how the sensor data will be transmitted to the DQM database shall also be included. Prior to the start of work, the Contractor shall submit to the DQM Support Center any addendum or modifications made to the plan subsequent to its original submission. Requirements and a template for the DPIP are available on the DQM website at https://dqm.usace.army.mil.

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION

3.1 REQUIREMENTS FOR REPORTED DATA

The Contractor shall provide, operate, and maintain all hardware and software to meet these specifications. The Contractor shall also be responsible for the replacement, repair, and calibration of the sensors and other necessary data acquisition equipment needed to supply the required data.

The procedure to complete a repair shall be documented and completed as soon as practical. If repair is not possible within two business days of any sensor failure, a plan and timeline to complete the repair shall be submitted. Upon completion of a repair, replacement, installation, modification, or calibration, the Contractor shall notify the Contracting

Officer's Representative (COR). The COR may request recalibration of the sensors or other hardware components at any time during the contract as deemed necessary.

The Contractor shall keep a log of sensor repair, replacement, installation, modification, and calibration in the dredge's onboard copy of the DPIP. The log shall contain a three-year history of sensor maintenance, including the time of the sensor failures (and subsequent repairs), the time and results of sensor calibrations, the time of sensor replacements, and the time that backup sensor systems were initiated to provide the required data. It shall also contain the name of the person responsible for the sensor work.

Sensors installed shall be capable of collecting parameters within the specified accuracies and resolutions indicated in the following subparagraphs and transmit these parameters to the DQM database. All data shall be transmitted in JSON message bundles. Each bundle can contain multiple message types. Sensor data shall be transmitted as work event messages, and data which relates to the operational state of the dredge or its sensors shall be transmitted as state event messages. See paragraph entitled "Parameter Transmission to the Web Service".

3.1.1 Message Bundle Data

Every message bundle shall contain descriptive data that relates the

SECTION 35 20 23.33 Page 5 message to a given dredge plant and date/time. The start of a message bundle shall be identified by the tag "DQM_data".

3.1.1.1 Messages

Messages contain operational data that populates the DQM database for a dredge plant. A message shall consist of an event type and its associated data (as defined in paragraph entitled "Dredge Events"), a date/time stamp indicating when the event occurred or started, and a comment providing clarification or metadata about the situation. There are multiple event types, but they all fall into one of two categories - work events and state events.

3.1.1.1.1 Message Time

In a work event message, message time is the date and time that the data is collected from the sensors; in a state event message, message time is the date and time that the state event begins. The message time shall be reported to the nearest second and referenced to Coordinated Universal Time

(UTC) time based on a 24-hour format (YYYY-MM-DD HH:MM:SS). In order to ensure accuracy and reliability, the time stamp shall be synchronized to

UTC format from an accurate, unchangeable source (for example, a GPS

National Marine Electronics Association [NMEA] datastring). Message time shall be identified by the tag "msg_time".

3.1.1.1.2 Comment

Comments concerning the work event or state event messages being transmitted provide descriptive information that relates to the data. An example of a comment for work event data is information about a sensor issue; an example of a comment for state event data is a description of operations. A comment shall be identified by the introductory tag

"comment", and the comment shall consist of no more than 250 characters.

3.1.1.2 Dredge Events - Work Event

There are two types of dredge event messages - work event messages and state event messages. Work event messages contain data that are instantaneously collected or calculated from sensors and are logged as a series of events. Work events are triggered by a time interval change (as described in paragraph entitled "Work Event Messages"). All work event messages shall be initiated by the header tag "work_event".

3.1.1.2.1 Vertical Correction

The variation of the water level from the vertical datum for the river stage or tidal gage described in the state events shall be obtained using appropriate equipment to give the water level with an accuracy of +/- 0.1

ft. Vertical correction values above project datum described in the dredging specification shall be entered with a positive sign and those below with a negative sign. The tag for vertical correction shall be

"vert_correction".

3.1.1.2.2 Cutter/Suction Head Location and Movement

The X, Y, and Z components of the cutter/suction head location shall be monitored. Additional calculations made from the observed values determine the rates of movement to track the progress of the dredge.

SECTION 35 20 23.33 Page 6

3.1.1.2.2.1 Cutter/Suction Head Horizontal Position

The forwardmost point of the cutter/suction head shall be obtained using a positioning system operating with a minimum accuracy level of 3-10 feet horizontal Circular Error Probable (CEP). It shall be reported as

Latitude/Longitude WGS 84 in decimal degrees with West Longitude and South

Latitude values reported as negative. Position values shall be identified by the tags "ch_latitude" and "ch_longitude".

3.1.1.2.2.2 Cutter/Suction Invert Depth

Cutter/suction invert depth is the depth of the invert of the suction mouth relative to the surface of the water. Instrumentation shall be capable of reporting to an accuracy of +/- 0.5 foot and a resolution to the nearest

0.1 foot with no tidal adjustments. Minimum accuracies are conditional to relatively calm water. The tag "ch_depth" shall be used to identify the cutter/suction head depth.

3.1.1.2.2.3 Cutter/Suction Head Heading

The cutter/suction head heading is the angle of the centerline of the cutter/suction head and dredge ladder measured relative to true north. All headings shall be provided using industry-standard equipment. The heading shall be accurate to within 5 degrees and reported to the nearest whole degree with values from 000 (true north) to 359 degrees referenced to a clockwise positive direction convention. The tag "ch_heading" shall be used to identify the cutter/suction head heading.

3.1.1.2.3 Dredge Activity

Dredge activity shall be monitored using a combination of the following parameters.

3.1.1.2.3.1 Slurry Velocity

A flow-metering device, calibrated according to the manufacturer's specifications, shall be used to record the slurry velocity to the nearest

0.01 fps with an accuracy of plus 0.1 fps. If the manufacturer does not specify a frequency of recalibration, calibration shall be conducted prior to the commencement of work. The slurry velocity shall be measured for the same pipeline inside diameter as that used for the slurry density measurement. The tag "slurry_velocity" shall be associated with this value.

3.1.1.2.3.2 Slurry Density

A density-metering device, calibrated according to the manufacturer's specifications, shall be used to record the slurry density to the nearest

0.01 g/cc. It is understood that the accuracy of this sensor can vary based on several factors, including the type of material, the magnitude of the cut, and the length of time since calibration. If the manufacturer does not specify a frequency of recalibration, calibration shall be conducted prior to the commencement of work. Continuous monitoring of this sensor ensures that drift and other factors inherent in the dredging process can be accounted for in monitoring dredge activity. The tag "slurry_density" shall be associated with this value.

3.1.1.2.3.3 Pump RPM

The pump rpm is the number of revolutions per minute measured for the

SECTION 35 20 23.33 Page 7 slurry pump shaft. The shaft revolution rate (rev/min) shall be measured with the highest level of accuracy that is standard on the vessel's operational displays either at the bridge or in the engine room. This value shall be identified by the tag "rpm".

3.1.1.2.3.4 Pump Vacuum

The vacuum pressure of the dredge pump(s) (inches of mercury) shall be measured as near to the eye as practicable in the pump's suction pipe with the highest level of accuracy that is standard on the vessel's operational displays either at the leverman's controls or in the engine room. Vacuum pressure shall be identified by the tag "vacuum".

3.1.1.2.3.5 Pump Outlet Pressure

The pump outlet pressure shall be measured in the discharge line on the pump side of the flap valve in terms of pounds per square inch (psi) on a gauge. Pump outlet pressure shall be identified by the tag "outlet_psi".

3.1.1.2.4 Outfall Information (Open Water/Spill Barge Disposal)

The X and Y position of the terminal end of the outfall pipe shall be monitored continuously and the position reported as part of the work event string.

3.1.1.2.4.1 Discharge Horizontal Position

The horizontal position of the outfall end of the discharge pipe shall be obtained using a positioning system operating with a minimum accuracy level of 3-10 feet horizontal Circular Error Probable (CEP). It shall be reported as Latitude/Longitude WGS 84 in decimal degrees with West Longitude and

South Latitude values being reported as negative. Position values shall be identified by the tags "outfall_latitude" and "outfall_longitude".

3.1.1.3 Dredge Events - State Event

There are two types of dredge event messages - work event messages and state event messages. State event messages provide information about the current state of the dredge equipment or operations. They are created and sent only when a state changes. Since state events often cannot be collected in real time, state events are tagged with a date time stamp

(referenced to Coordinated Universal Time [UTC]) that indicates when the state change happened relative to the work event message tag. This data is considered to be "true" until another state event tag is received. Each type of state event message shall be indicated by a specific header tag as enumerated in the following subparagraphs. State events can be transmitted along with work event message bundles directly by the contractor using the indicated format, or they can be entered on the "State" tab in the

DQM-provided software.

3.1.1.3.1 Message Time

The state event time is the date and time that the event starts. The leverman's time shall be entered to the nearest second as local time and automatically converted to and reported in UTC based on a 24-hour format

(YYYY-MM-DD HH:MM:SS). Message time shall be identified by the tag

"msg_time".

SECTION 35 20 23.33 Page 8

3.1.1.3.2 Contract Event

Information concerning the contract under which dredging is being performed shall be reported at the start and completion of each contract using the header tag "contract_event".

3.1.1.3.2.1 Contract Number

The USACE-assigned contract number for the project shall be reported using the tag "contract_number".

3.1.1.3.2.2 Contract Start and End

The start and end of a contract shall be reported using the tag

"event_type" with the appropriate value of "start" or "end".

3.1.1.3.3 Tide Station/River Stage Gage Event

Properties associated with the vertical correction (see paragraph entitled

"Vertical Correction") for the tide station/river stage gage shall be grouped together under the header tag "station_event". This information shall be sent at the start of the contract and each time the dredge has moved enough to change the station being used.

3.1.1.3.3.1 Station Name

The station name is a concise name defining the tide station/river stage gage begin referred to. It shall be introduced by the tag "station_name", and it shall consist of a descriptor of no more than 25 characters.

3.1.1.3.4 Length of Pipe Event

The leverman's estimate of the length of pipe downflow from the dredge pump, measured to the nearest whole foot, shall be reported under the header tag "pipe_length_event". This information shall be sent at the start of the contract and at the completion of each 24-hour period ending at midnight local time.

3.1.1.3.4.1 Floating Pipe

The total length of floating pipe shall be reported with the tag

"length_floating".

3.1.1.3.4.2 Submerged Pipe

The total length of floating pipe shall be reported with the tag

"length_submerged".

3.1.1.3.4.3 Shore Pipe

The total length of shore pipe shall be reported with the tag "length_land".

3.1.1.3.5 Booster Pump Event

Information concerning the booster pumps being used shall be included under the header tag "booster_pump_event". A message shall be sent to indicate any change in the status of the booster pumps being used.

SECTION 35 20 23.33 Page 9

3.1.1.3.5.1 Number of Booster Pumps

Upon the addition or removal of a booster pump, the total number of booster pumps being used shall be reported with the tag "booster_total".

3.1.1.3.6 Dredge Advance

The dredge advance, the total forward progress of the dredge relative to the centerline of the cut, shall be measured to the nearest whole foot and cumulatively calculated over a 24-hour period from midnight to midnight local time. It shall be identified by the tag "advance_daily". The msg_time associated with this tag shall be reported as the first timestamp of the following 24-hour period (based on the local time) rather than as midnight of the day for which the value was calculated, and it shall be reported in

Greenwich Mean Time (GMT). The type of dredge advance mechanism shall be recorded, (i.e. spud carriage, walking spud or is moving on wires.

3.1.1.3.7 Outfall Information

The X and Y position of the terminal end of the outfall pipe shall be monitored and sent at the start of the contract and thereafter according to the following table. Discharge Heading and Pipe Elevation may be omitted if the dredge is not discharging into an upland disposal site. For beach nourishment, the horizontal X and Y position of the outfall shall be sent at the start of the contract and at the completion of each 24-hour period ending at midnight local time.

Discharge

Location

Horizontal

Position

Discharge Pipe

Elevation

Discharge Outfall

Heading

Open Water Continuous Work

Event

N/A N/A

Scow Upon Change N/A N/A

Beach Every 24 Hours N/A N/A

Upland Upon Change Upon Change Upon Change

3.1.1.3.7.1 Discharge Location

Information on where the slurry is being discharged shall be reported with the tag "outfall_location". Acceptable values include "upland", "open water", "beach", and "scow".

3.1.1.3.7.2 Discharge Horizontal Position

The horizontal position of the outfall end of the discharge pipe shall be obtained using a positioning system operating with a minimum accuracy level of 3-10 feet horizontal Circular Error Probable (CEP). It shall be reported as Latitude/Longitude WGS 84 in decimal degrees with West Longitude and

South Latitude values being reported as negative. Position values shall be identified by the tags "outfall_latitude" and "outfall_longitude".

3.1.1.3.7.3 Discharge Outfall Heading

The discharge outfall heading is the angle relative to true north measured from the centerline of the pipe in the direction of discharge. All headings

SECTION 35 20 23.33 Page 10 shall be provided using industry-standard equipment. They shall be accurate to within 5 degrees and reported to the nearest whole degree with values from 000 (true north) to 359 degrees referenced to a clockwise positive direction convention. The discharge heading shall be identified by the tag

"outfall_heading".

3.1.1.3.7.4 Discharge Pipe Elevation

The discharge pipe elevation is the height of the outfall measured in feet and tenths of a foot relative to the project datum. The required accuracy is contingent upon contract requirements. The tag "outfall_elevation" shall be used to identify this elevation.

3.1.1.3.8 Non-effective Work Event

Delays and dredge downtime shall be reported at the conclusion of the event. The reason for the non-effective work time shall be submitted under the header tag "non_eff_event" within 24 hours of the event.

3.1.1.3.8.1 Non-effective Work Interval

The start and end times for the non-effective work event shall be reported using the tags "msg_start_time" and "msg_end_time".

3.1.1.3.8.2 Dredge Function Code

The dredge operator indication of production delays, as listed on Form

4267, shall be transmitted at the end of the non-effective interval. Dredge function event messages shall be identified by the tag "function_code" and shall consist of one of the following standardized entries to indicate the operation:

AGV Assisting Grounded Vessels

CCH Change Cutterhead

CCSH Clear Cutter Suction

CLPJ Change Location Bar

COLL Collision

CPPL Clear Pump Pipeline

CPR Change Impeller

DR Dike Repair

FBD Fire Boat Drills

HPL Handling Pipe Line

HSL Handling Swing Line

HSP Handling Shore Pipe

LDNE Loss Due to Natural Elements

LDPV Loss Due to Passing Vessel

LNL Transfer to New Location

MISC Miscellaneous

MOB Mobilization & Demobilization

MSC Miscellaneous/Non-pay

OC Out of Commission

OR Operating Repairs

P Preparation

PREP Preparation & Making Up Tow

RPL Repair Pipeline

SB Sounding & Buoying

SBT Stand-By Time as Directed

SH Sundays-Holidays

TFS Taking on Fuel & Supplies

SECTION 35 20 23.33 Page 11

TOW Time on Tow

WAP Waiting Attendant Plant

3.1.1.3.8.3 Additional Comments

The "comment" tag shall be used to provide additional explanation for the noted delays or downtimes. For example, when the code "LDPV" (Loss Due to

Passing Vessel) is indicated, the name of the vessel and the number of tows shall be listed with the "comment" tag.

3.2 NATIONAL DREDGING QUALITY MANAGEMENT PROGRAM SYSTEM REQUIREMENTS

The Contractor's DQM system shall be capable of collecting and transmitting information to the DQM onboard computer. The applicable parameters from paragraph entitled "Requirements for Reported Data" shall be recorded as events locally and continuously transmitted to the DQM database anytime an

Internet connection is available. The dredge shall be equipped with a DQM computer system consisting of a computer, monitor, keyboard, mouse, data modem, Universal Power Supply (UPS), and network hub. The computer system shall be a standalone system, exclusive to the DQM monitoring system, and shall have USACE DQM software installed on it. If a hardware problem occurs, or if a part of the system is physically damaged, then the

Contractor shall be responsible for repairing it within two business days of the determination of the condition or submitting a plan and timeline to the DQM Data Acquisition and Analysis Team for repair if the repair will take more than two business days.

3.2.1 Computer Requirements

The Contractor shall provide a dedicated onboard computer for use by the

Dredging Quality Management system. This computer shall run the USACE DQM software and receive data from the Contractor's data-reporting interface.

This computer must meet or exceed the following performance specifications:

CPU Intel or AMD processor with a (non-overclocked) clock speed of at least 1.8 gigahertz (GHz)

Hard drive 250 gigabytes (GB); internal

RAM 4 gigabytes (GB)

Ethernet adapter 10 or 100 megabit (Mbit) internal network card with an RJ 45 connector

Video adapter Must support a resolution of 1024x768 at 16-bit color depth

Keyboard Standard 101-key keyboard

Mouse Standard 2-button mouse

Monitor Must support a resolution of 1024x768 at 16-bit color depth

Ports 2 free serial ports with standard 9-pin connectors; 1 free USB port

SECTION 35 20 23.33 Page 12

Other hardware Category 5 (Cat-5) cable with standard RJ-45 plugs connecting the network adapter to the network hub; one spare cable

The Contractor shall install a fully licensed copy of Windows 7

Professional Operating System on the computer specified above. The

Contractor shall also install any necessary manufacturer-provided drivers for the installed hardware.

This computer shall be located and oriented to allow data entry and data viewing as well as to provide access to data ports for connection of external hardware.

3.2.2 Software

The DQM computer's primary function is to transmit data to the DQM shoreside database. No other software which conflicts with this function shall be installed on it. The DQM computer shall also have the

USACE-provided Dredging Quality Management Onboard Software (DQMOBS) installed on it by DQM personnel.

3.2.3 UPS

The Contractor shall supply an Uninterruptible Power Supply (UPS) for the computer and networking equipment. It shall interface with the DQM computer to communicate UPS status, and it shall provide backup power at 1 kVA for a minimum of 10 minutes. The Contractor shall ensure that sufficient power outlets are available to run all specified equipment.

3.2.4 Internet Access

The Contractor shall maintain an Internet connection capable of transmitting real-time data to the DQM server as well as enough additional bandwidth to clear historically queued data when a connection is re-established. The telemetry system shall always be available and have connectivity in the contract area. If connectivity is lost, unsent data shall be queued and transmitted upon restoration of connectivity. The

Contractor shall acquire and install all necessary hardware and software to make the Internet connection available for data transmission to the DQM web service. The hardware and software shall be configured to allow the DQM

Support Center remote access to this computer, and the telemetry system shall be capable of meeting these minimum reporting requirements in all operating conditions.

In areas with an unreliable Internet connection and at the Contracting

Officers discretion, it may be required to manually download the data on a daily basis using the protocol for retrieving and submitting backup files provided by the DQM Support Center. This method of data transmission should be used only if Internet connectivity is unavailable at the dredging site, and it should be considered a temporary measure. If data must be manually downloaded, it shall be submitted to the DQM Data Acquisition and Analysis

Team within 48 hours of the date it was collected.

3.2.5 Data Routing Requirements

Onboard sensors continually monitor dredge conditions, operations, and efficiency and route this information to the shipboard dredge-specific system (DSS) computer to assist in guiding dredge operations. Portions of this Contractor-collected information, as described in this specification, SECTION 35 20 23.33 Page 13 shall be routed to the DQM computer on a real-time basis. Standard sensor data shall be sent to the DQM computer via an RS-232 serial interface with a baud rate of 9600 or 19200 bps. The serial interface shall be configured as 8 bits, no parity, and no flow control

Information regarding changes in the state of the dredge shall be digitally logged and transmitted as close to the time of the occurrence as possible.

These events can either be included in a separate message bundle going to the DQM onboard computer, or they can be entered on the "State" tab in the

DQM Pipeline Software

3.3 DREDGE MONITORING DATA

3.3.1 General

Onboard sensors continuously collect dredging data in support of the dredge

Contractor's operations. Portions of this Contractor-collected information, as described in this specification, and calculations based on them shall be stored and transmitted to the DQM database on a near real-time basis.

Additionally, information regarding the state of the dredge shall be digitally logged and transmitted.

3.3.2 Data Measurement Frequency

The frequency of data transmission is dependent on the type of message being sent. Work Event messages contain data that are instantaneously collected or calculated from sensors and are logged as a series of events.

State event messages are activated by a change in the dredge state.

3.3.2.1 Work Event Messages

Data shall be logged as a series of events. Each event shall consist of a dataset containing dredge information (as defined in paragraph entitled

"Requirements for Reported Data"). Each set of measurements (for example, time and position) shall be considered an event, and there shall be a 6-12 second interval between work events. This interval shall remain consistent across event types for the dredge plant.

A standard data string shall be recorded within one second of an event trigger with the time stamp and all parameters reflecting when the event happened.

3.3.2.2 State Event Messages

A set of descriptive information (event name, time, description, comment) shall be considered a state event. These events shall be recorded within 24 hours of a change in state with the time stamp reflecting when the event happened.

3.3.3 Parameter Transmission to the Web Service

The data shall be formatted as JSON (JavaScript Object Notation, as defined at http://www.json.org) strings of arbitrary length. These JSON strings represent a hierarchical data structure consisting of a message bundle which may contain 0-3 automatic data messages and any number of manual data messages.

A tag/parameter is reported only when it contains a value. No "Null" value strings shall be included in a message bundle.

SECTION 35 20 23.33 Page 14

Message bundle

"DQM_Data": {

"messages": [

"work_event": {

"msg_time": <24-hour UTC time YYYY-MM-DD HH:MM:SS>, "vert_correction": <floating point 100th decimal place>, "ch_latitude": <decimal to 6 decimal places>, "ch_longitude": <decimal to 6 decimal places>, "ch_depth": <floating point 100th decimal place>, "ch_heading": <integer value 000-359>, "slurry_velocity": <floating point 100th decimal place>, "slurry_density": <floating point 100th decimal place>, "pump_rpm": <integer>, "vacuum": <floating point 100th decimal place>, "outlet_psi": <floating point 100th decimal place>, "comment": <string>}, "contract_event": {

"msg_time": <24-hour UTC time YYYY-MM-DD HH:MM:SS>, "contract_number": <string>, "event_type": <string - "start" or "end">, "comment": <string>

"station_event": {

"msg_time": <24-hour UTC time YYYY-MM-DD HH:MM:SS>, "station_name": <string>, "comment": <string>

"pipe_length_event": {

"msg_time": <24-hour UTC time YYYY-MM-DD HH:MM:SS>, "length_floating": <integer>, "length_submerged": <integer>, "length_land": <integer>, "comment": <string>

"booster_pump_event": {

"msg_time": <24-hour UTC time YYYY-MM-DDHH:MM:SS>, "booster_total": <integer>, "comment": <string>

"advance_Event": {

"msg_time": <24-hour UTC time YYYY-MM-DD HH:MM:SS>, "advance_daily": <integer>, SECTION 35 20 23.33 Page 15

"comment": <string> water">

"outfall_position": {

"msg_time": <24-hour UTC time YYYY-MM-DD HH:MM:SS>, "outfall_location": <string-"upland", "beach", "scow", "open

"outfall_latitude": <decimal to 6 decimal places>, "outfall_longitude": <decimal to 6 decimal places>, "outfall_heading": <integer value 000-359>, "outfall_elevation": <floating point 10th decimal place>, "comment": <string>

"non_eff_event": {

"msg_start_time": <24-hour UTC time YYYY-MM-DD HH:MM:SS>, "msg_end_time": <24-hour UTC time YYYY-MM-DD HH:MM:SS>, "function_code": <string - 1 to 4 characters>, "comment": <string>

3.3.4 Contractor Data Backup

The Contractor shall maintain an archive of all data sent to the DQM computer during the dredging contract. The COR may require, at no increase in the contract price, that the Contractor provide a copy of these data covering specified time periods. The data shall be provided in the same

JSON format as would have been transmitted to the DQM computer. There shall be no line breaks between the parameters, and each record string shall be on separate line. The naming convention for the files shall be <dredgename

>_<StartYYYYMMddhhmmss>_<EndYYYYMMddhhmmss>.txt.

Data submission shall be via a storage medium acceptable to the COR.

At the end of the dredging contact, the Contractor shall call the National

DQM Support Center prior to discarding the data to ensure that it has been appropriately archived. The Contractor shall record the following information in a separate section at the end of the dredge's onboard copy of the DPIP:

- Person who called the National DQM Support Center

- Date of the call

- DQM representative who gave permission to discard the data

On the same day that the call is made, but prior to discarding the data, the Contractor shall submit a "Data Appropriately Archived" email to the local USACE District's COR with the above information and cc: the DQM

Support Center representative who granted the permission. In addition to the above information, the following shall also be included in the email:

- Project name and contract number

- Dredge start and end dates

- Name of the dredge

SECTION 35 20 23.33 Page 16

3.4 PERFORMANCE REQUIREMENTS

The Contractor's National Dredging Quality Management Program's data transmission shall be fully operational at the start of dredging operations. To meet contract requirements for operability, the Contractor's system shall provide an accurate data string return and be compliant with hardware requirements. Data string return is defined as the number of quality records within an event or state tag sent by the contractor's system to the DQM database. Quality data strings are considered to be those providing accurate values for all parameters reported when operating according to the specification. Repairs necessary to restore data return compliance shall be made within two business days, or a plan and timeline for repair shall be submitted to the DQM Data Acquisition and Analysis Team if the repair will take more than two business days. Failure by the

Contractor to report quality data within the specified time window for dredge measurements as stated in the specifications (see paragraphs entitled "Internet Access", "Data Measurement Frequency" and "Parameter

Transmission to the Web Service") will result in withholding of up to 10% of the contract progress payment in accordance to the 00700 Contract Clause entitled PAYMENTS UNDER FIXED-PRICE CONSTRUCTION CONTRACTS, FAR 52.232-5.

3.5 QUALITY ASSURANCE CHECKS

Quality assurance (QA) checks are a part of the DQM dredge certification procedure. They are required prior to the commencement of dredging and, at the discretion of the COR, periodically throughout the duration of the contract. The SOP and criteria for QA checks are presented on the DQM website at https://dqm.usace.army.mil.

3.6 CONTRACTOR QUALITY CONTROL

The Contractor shall designate a quality control systems manager (QCSM), who shall develop and maintain daily procedures to ensure quality control

(QC) of the dredge's DQM system. These methods shall include the procedure by which data being collected is checked against known values, and verification that the telemetry is functioning. These procedures shall be outlined in the DPIP and submitted prior to the Notice to Proceed. In the event a Contractor Quality Control (CQC) Report is required, daily annotations shall be made in the Daily CQC Report, documenting all actions taken on each day of work, including all deficiencies found and the corrective actions taken.

3.7 LIST OF ITEMS PROVIDED BY THE CONTRACTOR

- DPIP Paragraph entitled "Dredge Plant Instrumentation Plan (DPIP)"

- DQM System Paragraph entitled "National Dredging Quality Management

Program System Requirements"

- Dredge Data Paragraph entitled "Dredge Monitoring Data"

Section 01025-Table of Contents Page 1

DIVISION 1 - GENERAL REQUIREMENTS

SECTION 01025

MEASUREMENT AND PAYMENT

TABLE OF CONTENTS

PART 1 GENERAL

1.1 JOB SUM PAYMENT ITEMS

1.1.1 General

1.1.2 Job Sum Items

1.2 UNIT PRICE PAYMENT ITEMS

1.2.1 General

1.2.2 Unit Price Items

PART 2 PRODUCTS (NOT USED)

PART 3 EXECUTION (NOT USED)

-End of Section Table of Contents-

Section 01025 Page 1

SECTION 01025

MEASUREMENT AND PAYMENT

PART 1 GENERAL

1.1 JOB SUM PAYMENT ITEMS

1.1.1 GENERAL Payment items for the work of this contract for which lump sum payments will be made are listed in the Bidding Schedule item # (0005, 0010, 0015) and are described below. All costs for items of work, which are not specifically mentioned to be included in a particular lump sum payment item, shall be included in the listed lump sum item most closely associated with the work involved. The lump sum price and payment made for each item listed shall constitute full compensation for furnishing all plant, labor, materials, and equipment, and performing any associated Contractor Quality Control, meeting safety and environmental requirements, tests and reports, and for performing all work required for which separate payment is not otherwise provided.

1.1.2 JOB SUM ITEMS

(1) Mobilization and Demobilization

a. Payment will be made for all costs associated with operations necessary for mobilization and demobilization as specified in Section 00800. The 60% of this payment will be made once dredge and attendant plant are on site ready to pump with all pipelines in place at first assigned dredging location. The 40% Demobilization will be paid on the completion of the last dredging location.

b. Unit of measure, job sum: JS.

1.2 UNIT PRICE PAYMENT ITEMS

1.2.1 GENERAL Payment items for the work under this contract on which the contract progress payments will be based are listed in the Bidding Schedule Item # (0001,0002, 0003 and 0004 ; 0006, 0007, 0008 and 0009; 0011, 0012, 0013, and 0014) are described below. All costs for items of work, which are not specifically mentioned to be included in a particular unit price payment item, shall be included in the listed unit price item most closely associated with the work involved.