Amendment 0001.pdf

OM-20-276

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The above numbered solicitation for Mississippi River, Baton Rouge to Gulf of Mexico, Southw est Pass Maintenance Dredging, Non-Continuous Mile 6.0 AHP to Mile 19.5 BHP, Cutterhead Dredge Rental No. 2-2020. Specif ication Nos. OM-20-276. has been amended to:

1. Update Davis Bacon Wage Rate Determination

2. Make changes to the solicitation as detailed in the follow ing pages.

Please note: A second amendment will be issued to set the bid opening date.

For any questions, please contact the Contracting Officer - Veronica Garner=Flint, (504) 862-1515 or the Contract Specialist - Cori Caimi, (504) 862-1352.

1. CONTRACT ID CODE PAGE OF PAGES

1 39

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street , County, State and Zip Code) X W912P820B0015

X 9B. DATED (SEE ITEM 11)

14-Nov-2019

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO.

AM0001

5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

25-Jun-2020

CODE

USACE, CONTRACTING DIVISION

ATTN: CEMVN-CT, ROOM 172

7400 LEAKE AVE.

NEW ORLEANS LA 70118-3651

W912P8 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W912P820B0015

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION 00010 - BIDDING SCHEDULE

The following have been added by full text:

AMENDMENT 0001

1. General Comment: This solicitation will be used to dredge the channel for both maintenance and new construction. The new construction dimensions of the channel are -50.0 ft MLLW by 750 ft bottom width from Mile 6.0 AHP to Mile 17.5 BHP, then narrowing to 600 ft wide through the jetty channel and bar channel. The specified elevation in the dredging assignment will not exceed -56.0 ft MLLW. Previously, the specified elevation in dredging assignments did not exceed -54.5 ft MLLW.

2. General Comment: Delete all references within the specifications to Edward Creef and replace with the following point of contact: Jeff Corbino, phone: (504) 862-1958, email: Jeffrey.M.Corbino@usace.army.mil.

3. General Comment: For all project titles, delete the word “rental”.

4. Project Table of Contents: Under Division 35, add Section 35 20 23.33 entitled “National Dredging Quality Management Program Pipeline Hydraulic Dredge”.

5. Section 00010, paragraph 1.1 “Bidding Schedule”: Delete this paragraph in its entirety and replace with the attached paragraph 1.1 entitled “Bidding Schedule”.

6. Section 00010, paragraph 1.3 “Evaluation of Bids”, subparagraph d: In the second sentence, delete “dredge rental” and replace with “contract duration”.

7. Section 00010, paragraph 1.4 “Conditions of Contract Award”, subparagraph c: In the first sentence, delete “of rental time”.

8. Section 00010, paragraph 1.4 “Conditions of Contract Award”, subparagraph c: Delete the “Approximate Cutterhead Dredge Contract Duration (Base Plus Option)” table and replace with the following table:

APPROXIMATE CUTTERHEAD DREDGE

CONTRACT DURATION

(BASE PLUS OPTION)

Pump Discharge ID (Inches)

Submerged Pump

Approximate Number of Contract Days

30 or greater Yes 237

9. Section 00700, FAR Clause 52.211-10 “Commencement, Prosecution, and Completion of Work (Apr 1984)”: In subparagraph c, delete “complete the entire work ready for use not later than the days specified by bid lot in Section 00010-1.4 of the bidding schedule, after the date of receipt by Contractor of notice to proceed” and replace with “complete the entire work ready for use not later than 237 calendar days after issuance of the Notice to Proceed”.

10. Section 00800, paragraph 3.2 “Prosecution, Option and Completion”: In the first sentence, delete “option rental hours” and replace with “option hours”.

11. Section 00800, paragraph 3.4 “Equipment Ownership and Operating Expense Schedule (UAI 5152.231- 9000 –MAR 1995)”: Delete this paragraph in its entirety and replace with the following paragraph:

3.4 CONSTRUCTION AND ARCHITECT-ENGINEER (A-E) CONTRACTS (UAI 5131.105)

(d)(2)(i)(B) For the predetermined schedule of construction equipment use rates, use Engineer Pamphlet (EP) 1110-1-8, Construction Equipment Ownership and Operating Expense Schedule.

(End of special contract requirement)

Note 1: Reference "Construction and Architect-Engineer Contracts" (FAR 31.105). Costs for repairs or overhauling are not allowed.

Note 2: A copy of the "EQUIPMENT OWNERSHIP AND OPERATING EXPENSE SCHEDULE" (Region III) can be obtained from the following website:

https://www.publications.usace.army.mil/Portals/76/Users/182/86/2486/EP%201110-1- 8%20Vo3%20.pdf?ver=2019-12-02-104221-527.

12. Section 01 30 00, paragraph 1.14 “Suspicious Activity Reporting Training”: Delete this paragraph in its entirety.

13. Section 01 33 00 Attachment: Delete the Submittal Register in its entirety and replace with the attached Submittal Register.

14. Section 35 01 50.73, Part 2 “Products”: In the first sentence, delete “due to the fact that the services of the equipment are leased by the Government,”.

15. Section 35 20 23.23, paragraph 1.2.2 “Dredging and Option Dredging Items”, subparagraph j: Delete “rental rate” and replace with “rate”.

16. Section 35 20 23.23, paragraph 1.2.5 “Work for Others”: Add the following as subparagraph d:

d. If the dredge returns to an assignment in another dredging region and the dredge in tow never enters the route that would have been taken had the dredge not been released, when dredged material starts flowing through the discharge pipeline.

17. Section 35 20 23.23, Part 2 “Products”: In the first sentence, delete “due to the fact that the services of the equipment are leased by the Government,”.

18. Section 35 20 23.23, paragraph 3.2.2 “Government Actions for Failed Production”, item (4): Delete “rental rate” and replace with “rate”.

19. Section 35 20 23.23, paragraph 3.1.3.1 “Dredging in Secondary Regions”: In the last sentence, delete “any additional costs not covered within the specification payment clauses”.

20. Section 35 20 23.23, paragraph 3.5 “Cutterhead Dredge and Attendant Plant Sheet”: Change Item 1.(l) to the following:

(l) Length of digging spud to trunnion:

With an idler barge: ________________, Without an idler barge: ________________

21. Section 35 20 23.23 Attachment: Delete MVN Form 4267 in its entirety and replace with the attached MVN Form 4267 (Version: June 2020).

22. Section 35 20 23.23 12, paragraph 1.3 “Existing Structures or Utilities”: For the 8” Hilcorp/Harvest Pipeline at approx. Station 534+13, change the email address for Mark Bordelon to “mbordelon@harvestmidstream.com”.

23. Section 35 20 23.23 12, Part 2 “Products”: In the first sentence, delete “due to the fact that the services of the equipment are leased by the Government,”.

24. Section 35 20 23.23 12, paragraph 3.1.1.1 “Mississippi River, Southwest Pass”: Delete subparagraph a in its entirety and replace with the following:

a. The new construction dimensions of the channel are -50.0 ft MLLW by 750 ft bottom width from Mile 6.0 AHP to Mile 17.5 BHP, then narrowing to 600 ft wide through the jetty channel and bar channel. The Contracting Officer or his/her authorized representative may issue dredging assignments for all or portions of this dredging region. Each dredging assignment will define the dredging template to be dredged by the contractor. The dredging template will include the swing width, the specified elevation, and the total length. The specified elevation in the dredging assignment will not exceed 6 feet below the new construction elevation. The required side slope is 1V on 3H. Disposal areas are shown on the contract plates (20-1R through 20-10R) attached at the end of this section. Should dike construction be necessary, an equitable adjustment in the contract price will be made.

25. Section 35 20 23.23 12, paragraph 3.1.4 “Location of Dredge Plant and Equipment”: Add the following to the end of this paragraph: “Upon completion of an assignment, the Contractor shall immediately remove all discharge pipeline within the channel and any charted marine vessel anchorage areas.”

26. Section 35 20 23.23 12, paragraph 3.3 “Rights of Way”: In subparagraph b(1), delete “August 31, 2020” and replace with “December 31, 2020”.

27. Section 35 20 23.23 12, paragraph 3.3 “Rights of Way”: Add the following as subparagraph c:

c. Special Permit Conditions – The United States Department of Interior, United States Fish and Wildlife Services has granted Right of Entry, including ingress and egress, to perform dredging, disposal, and dike construction within the Delta National Wildlife Refuge Area (DNWR). All work must be completed in accordance with the contract plates and specifications, including all special permit conditions. The Contractor shall comply with the following special permit conditions:

(1) The Right of Entry is valid through May 1, 2021.

(2) The use of airboats is prohibited from 1 November through 31 January.

(3) USACE will schedule a pre-construction meeting and site visit with DNWR 30 days prior to beginning work in DNWR.

(4) USACE will notify DNWR 48 hours prior to the beginning of work by notifying Barret Fortier at barret_fortier@fws.gov or (985) 882-2011 or Jimmy Laurent at laurent_jimmy@fws.gov.

28. Section 35 20 23.23 12 Attachment: Delete Plates 20-1 thru 20-10 and replaced with the attached plates (Plate 20-1R thru 20-10R).

29. After Section 35 20 23.23 12, add the attached Section 35 20 23.33 entitled “National Dredging Quality Management Program Pipeline Hydraulic Dredge”.

30. A second amendment request will be sent to set the bid opening date.

Section 00010, paragraph 1.1 “Bidding Schedule”

1.1 Bidding Schedule

SECTION 00010 – BIDDING SCHEDULE

MISSISSIPPI RIVER, BATON ROUGE TO GULF OF MEXICO

SOUTHWEST PASS MAINTENANCE DREDGING NON-CONTINUOUS

MILE 6.0 AHP TO MILE 19.5 BHP

CUTTERHEAD DREDGE NO. 2-2020

PLAQUEMINES PARISH, LOUISIANA

SOLICITATION NO. W912P820B0015

30 INCHES OR GREATER INSIDE DIAMETER (ID) PUMP DISCHARGE WITH SUBMERGED PUMP

Bid Item DESCRIPTION Estimated Quantity

Unit Unit Price

Total Price

0001 MOBILIZATION AND

DEMOBILIZATION

1 JOB

0002 DREDGING: Operation of one fully operated cutterhead dredge with 30 inches or greater ID pump discharge with a submerged pump, attendant plant and discharge pipeline as specified.

2880 HOUR

Option

OPTION DREDGING - Same plant as listed in Item No. 0002 of this bid lot.

1440 HOUR XXXXXX

0004 DREDGE TOWING SERVICE 15 MILE

Option

OPTION DREDGE TOWING

SERVICE

30 MILE XXXXXX

Option

BIRD NESTING PREVENTION

AND AVOIDANCE MEASURES

100 DAY

TOTAL:

*SEE BID FORM NOTES

SUBMITTAL REGISTER CONTRACT NO.

(ER 415-1-10)

CONTRACTOR SPECIFICATION SECTION

CONTRACTOR

TYPE OF SUBMITTAL ACTION

A C T I V I T Y

N O

TRANS-

MITTAL

NO

I T E M

N O

SPECIFICATION

SECTION

NUMBER

DESCRIPTION OF

ITEM SUBMITTED

D A T A

D R A W I N G S

I N S T R U C T I O N S

S C H E D U L E S

S T A T E M E N T S

R E P O R T S

C E R T I F I C A T E S

S A M P L E S

R E C O R D S

O M

M A N U A L S

I N F O R M A T I O N

O N L Y

G O V E R N M E N T

A P P R O V E D

R E V I E W E R

SUBMIT

APPROVAL

NEEDED

BY

MATERIAL

NEEDED

BY

C O D E

DATE

SUBMIT TO

GOVERN-

MENT

C O D E

DATE REMARKS

a. b. c. d. e. f. g. h. i. j. k. l. m. n. o. p. q. r. s. t. u. v. w. x. y. z. aa.

1 01 30 00 As-Built Drawings X X NOAO & ODT-D

2 01 35 26 Accident Prevention Program X SS

3 01 57 20.00 10 Environmental Protection Plan X X ODT-E

4 01 57 20.00 10 Bird Nesting Prevention Plan X X ODT-E

5 35 01 50.73 Calibration of Fathometer X X NOAO & ODT-C

6 35 01 50.73 Calibration of Horizontal Positioning Equipment

X X NOAO & ODT-C

7 35 01 50.73 Disposal Area Surveys X X X NOAO

8 35 01 50.73 Before and After Dredging Cross Sections

X X X NOAO

9 35 20 23.23 Pump curve(s) X X ODT-D

10 35 20 23.23 Plant Data Sheet X X ODT-D

11 35 20 23.23 Plan of Operations for Utility Crossing X X NOAO

12 35 20 23.23 Utility As-builts and Surveys Received from the Owners

X X X ODT-D

13 35 20 23.23 Aerial Photography Documentation X ODT-D

14 35 20 23.33 Letter of National Dredging Quality Management Program Certification

X X ODT-D

ENG FORM 4288-R, JAN 97 EDITION OF MAR 95 IS OBSOLETE. PAGE _1_ OF _1_ PAGES (PROPONENT: CEMP-CE)

NOTE: THIS REGISTER IS NOT NECESSARILY COMPLETE. THE CONTRACTOR SHALL BE RESPONSIBLE FOR DEVELOPING A COMPREHENSIVE REGISTER.

ACTION

TITLE AND LOCATION

Mississippi River Southwest Pass Cutterhead Dredge No. 2-2020. Solicitation No. W912P820B0015.

CLASSI-

FICATION

GOVERNMENT CONTRACTOR

SCHEDULE DATES

Section 01 33 00 - ATTACHMENT

NAME AND TYPE PIPELINE

OTHER TOTAL SHIFTS PER DAY

AUTH.

DIMENSIONS

C/L STATIONS >

GMS/liter GMS/liter

TYPE

TYPE

MM TYPE

AMOUNT

AVERAGE WIDTH OF CUT (SWING) FEET

TOTAL ADVANCE THIS PERIOD FEET

TOTAL ADV. PREVIOUS TO THIS PERIOD FEET BOOSTER (in line) :

TOTAL ADVANCE TO DATE FEET

TOTAL LENGTH OF DISCHARGE PIPE: *SEE REVERSE SIDE HANDLING PIPE LINES HPL

AVERAGE LIFT FEET HANDLING ANCHOR LINES HAL

AVERAGE PUMP SPEED R.P.M. CLEARING PUMP AND PIPE LINE CPPL

AVERAGE GROSS CY'S DREDGED / PER PUMP HRS. CU. YDS. CLEARING CUTTER OR SUCTION HEAD CCSH

SCOWS LOADED NUMBER WAITING FOR SCOWS WFS

CU. YDS. TO AND FROM WHARF OR ANCHORAGE TFWA

CHANGING LOCATION OF PLANT ON JOB CLPJ

CUBIC YARDS REMOVED LOSS DUE TO OPPOSING NATURAL ELEMENTS LDNE

LOSS DUE TO PASSING VESSELS WVP

(1) CREDITED (pay place) SHORE LINE AND SHORE WORK SLSW

(2) GROSS (computed amount) WAITING FOR BOOSTER WFB

MINOR OPER. REPAIRS (explain in remarks) MOR

(1) CREDITED (pay place) WAITING FOR ATTENDANT PLANT WAP

(2) GROSS (computed amount) PREPARATION AND MAKING UP TOW PMUT

TRANSFERRING PLANT BETWEEN WORKS TPBW

(1) CREDITED (pay place) LAY TIME OFF SHIFT AND SATURDAYS LTOSS

(2) GROSS (computed amount) SUNDAYS AND HOLIDAYS SH

FIRE DRILL FD

MISCELLANEOUS (explain in remarks) MISC

TOTAL NON-EFFECTIVE WORKING TIME

DREDGE

TENDER #1

TENDER #2

SKIFF

CREW PCT OF TOTAL TIME IN PERIOD

SURVEY

BARGES

CRANE BARGE MAJOR REPAIRS AND ALTERATIONS

IDLER BARGE CESSATION

CUTTER-TYPE COLLISIONS

SPUD LENGTH MISCELLANEOUS (explain in remarks)

NUMBER OF TOTAL LOST TIME

INSPECTIONS PERCENTAGE OF TOTAL TIME

( ) NO

TOTAL TIME IN PERIOD 00:00

( ) YES

Version: June 2020

SIZE

DREDGE ADVANCE MECHANISM

NO. OF TIMES AMOUNT

THRU: TO:

inch dia.

disch.

PROPULSION

REPORT NO.

SHOREDREDGE

WORK

SCHEDULE

FROM:

DIPPER OR BUCKET

DATE OR

PERIOD

cu. yds. cap.

COMPLETION

PROJECT

AND

BAR

DEPTHWIDTH

SUCTION PIPE JETDREDGE PUMP

RANGES - RT, CL, LT

RANGES - RT, CL, LT

WIDTH OF

SWING:

RANGES - RT, CL, LTLOCATION

(INCLUDE STATIONS

NUMBERS)

CHARACTER

OF

MATERIAL

(chargeable to cost of work)

CONTRACT OR

ORDER NUMBER

WEATHER

CONDITION miles

AVERAGE

DEPTH

RIVER

STAGE

MM

NUMBER

BEFORE DREDGING

GEOLOGICAL

CLASSIFICATION

CHANNEL

CONDITION

ABSOLUTE DENSITY VOIDS RATIOIN PLACE DENSITY

ITEM

MVN FORM 4267

AVERAGE LOAD PER SCOW

CONTRACT USE

ONLY

TOTAL EFFECTIVE AND NON-EFFECTIVE

ITEM

BY DIV & OCE

PERSONNEL

ATTENDANT PLANT

HOURS

(If "YES", explain under remarks on back)

BY DISTRICT

PERSONNEL

HAS ANYTHING DEVELOPED WHICH MIGHT

LEAD TO A CHANGE ORDER OR CLAIM?

TIME

(Signature and Remarks Required on reverse side)

NAME OR NUMBER

AMOUNT PREVIOUSLY REPORTED:

TOTAL AMOUNT DREDGED TO DATE:

PCT. OF NON-EFFECTIVE TIME

REPORTS CONTROL SYMBOL

ENGCW-0-13

DAYS PER WEEK

CUTTER OR BUCKET

REPORT OF OPERATIONS -- PIPELINE, DIPPER OR BUCKET DREDGES

HORSEPOWER

OF

DAILY[ ] [ ] [ ]NEW

WORK

MAINTE-

NANCE [ ] [ ] ANNUAL

CHARACTER OF

REPORT

DREDGE

OVERDEPTH

EFFECTIVE WORKING TIME

NON-EFFECTIVE WORKING TIME

NUMBER OF

CREWMEMBERS

TIMETIME

(chargeable to cost of work)

HIRED LABOR

TOTAL NUMBER OF DAYS

ON WHICH WORK WAS

DONE:

(clear, cloudy, rain, snow, and fog)

PUMPING OR DREDGING

PCT. OF EFFECTIVE TIME

AFTER DREDGING

VISIBILITY

UNIT QUANTITY

FULL WIDTH

FULL WIDTH

FULL WIDTH

(chargeable to cost of work)

LOST TIME

(not chargeable to cost of work)

AMOUNT DREDGED THIS PERIOD:

DISTRIBUTION OF TIMEWORK PERFORMED

GRAIN SIZE

WIND (maximum velocity & direction)

BEFORE DREDGING

CONTRACTOR

AFTER DREDGING

MINIMUM

GAGE LOCATION

MAXIMUM

MINIMUM

SOUNDING

FLOATING Marsh Trackhoes-30' SKIDDER Barges

PONTOONS Marsh Trackhoes-60'

Metal Metal Metal Marsh Buggies Breast

PVC PVC PVC Dozers Head

Flexifloat Other Other Total FEET in LINE Front End Loaders Line

TOTAL LF Air Boats Other

ATV's

ELBOWS Y-Valves

Stiff Spreaders

Swivel

MATERIAL

SHORE CONNECTION START FINISH TOTAL CY TOTAL ACRES CLASSIFICATION

100% 70% 35% 0% TOTAL

BASE HOURS 00:00

OPTION HRS 00:00

OPERATING SUPPLIES

COMMODITIES UNIT QUANTITY QUANTITY VALUE

FUEL (oil) GAL.

TOTAL COST OF PLANT

LUBRICANT GAL.

(oil)

LUBRICANT LBS.

(grease)

WATER GAL.

SUBSISTENCE SUPPLIES ……………………………………… $

MISCELLANEOUS SUPPLIES…………………………………

TOTAL……………………………………………………. $ $

NAME: NAME: NAME:

TITLE: TITLE: TITLE:

Version: June 2020

SUMMARY OF DREDGE DISCHARGE PIPELINE, DISPOSAL AREAS and TIME BREAKDOWN

PLANT OWNERSHIP COSTS

(Actual for F.Y. reporting period):

DEPRECIATION………………

REPAIRS (Adjusted) …………

BOOK VALUE

(End of F.Y. reporting period)………………

BALANCE IN PLANT ACCOUNT

(End of F.Y. reporting period)………………

CESSATION OF WORK ……

SUBMITTEDED BY (Name, title, and signature)

REMARKS:

(End of F.Y. reporting period)………………

AMOUNT SHORE AMOUNT

SMALL TOOLS, ETC…………

TOTAL……………………………

RECOMMENDED BY (Name, title, and signature) APPROVED BY (Name, title, and signature)

ATTENDANT PLANT

DREDGE DISCHARGE PIPELINE DISPOSAL AREA EQUIPMENT ANCHORING SYSTEMS

(complete when submitting Annual report)

ANNUAL REPORT DATA

CONSUMED INVENTORY

COSTS PER MINUTE

(Based on total operating costs)……………

SUBMERGEDAMOUNT

MVN FORM 4267

ANCHORS

DISPOSAL AREA SUMMARY

LOCATION

TIME BREAKDOWN

REMARKS

B2ODTSC9

Rectangle

SECTION TABLE OF CONTENTS

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

SECTION 35 20 23.33

NATIONAL DREDGING QUALITY MANAGEMENT PROGRAM PIPELINE HYDRAULIC DREDGE

PART 1 GENERAL

1.1 DESCRIPTION

1.2 MEASUREMENT AND PAYMENT

1.3 NATIONAL DREDGING QUALITY MANAGEMENT PROGRAM CERTIFICATION

1.4 DREDGE PLANT INSTRUMENTATION PLAN (DPIP)

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION

3.1 REQUIREMENTS FOR REPORTED DATA

3.1.1 Message Bundle Data

3.1.1.1 Messages

3.1.1.1.1 Message Time

3.1.1.1.2 Comment

3.1.1.2 Dredge Events - Work Event

3.1.1.2.1 Vertical Correction

3.1.1.2.2 Cutter/Suction Head Location and Movement

3.1.1.2.2.1 Cutter/Suction Head Horizontal Position

3.1.1.2.2.2 Cutter/Suction Invert Depth

3.1.1.2.2.3 Cutter/Suction Head Heading

3.1.1.2.3 Dredge Activity

3.1.1.2.3.1 Slurry Velocity

3.1.1.2.3.2 Slurry Density

3.1.1.2.3.3 Pump RPM

3.1.1.2.3.4 Pump Vacuum

3.1.1.2.3.5 Pump Outlet Pressure

3.1.1.2.4 Outfall Information (Open Water/Spill Barge Disposal)

3.1.1.2.4.1 Discharge Horizontal Position

3.1.1.3 Dredge Events - State Event

3.1.1.3.1 Message Time

3.1.1.3.2 Contract Event

3.1.1.3.2.1 Contract Number

3.1.1.3.2.2 Contract Start and End

3.1.1.3.3 Tide Station/River Stage Gage Event

3.1.1.3.3.1 Station Name

3.1.1.3.4 Length of Pipe Event

3.1.1.3.4.1 Floating Pipe

3.1.1.3.4.2 Submerged Pipe

3.1.1.3.4.3 Shore Pipe

3.1.1.3.5 Booster Pump Event

3.1.1.3.5.1 Number of Booster Pumps

3.1.1.3.6 Dredge Advance

3.1.1.3.7 Outfall Information

3.1.1.3.7.1 Discharge Location

3.1.1.3.7.2 Discharge Horizontal Position

SECTION 35 20 23.33 Page 1

3.1.1.3.7.3 Discharge Outfall Heading

3.1.1.3.7.4 Discharge Pipe Elevation

3.1.1.3.8 Non-effective Work Event

3.1.1.3.8.1 Non-effective Work Interval

3.1.1.3.8.2 Dredge Function Code

3.1.1.3.8.3 Additional Comments

3.2 NATIONAL DREDGING QUALITY MANAGEMENT PROGRAM SYSTEM REQUIREMENTS

3.2.1 Computer Requirements

3.2.2 Software

3.2.3 UPS

3.2.4 Internet Access

3.2.5 Data Routing Requirements

3.3 DREDGE MONITORING DATA

3.3.1 General

3.3.2 Data Measurement Frequency

3.3.2.1 Work Event Messages

3.3.2.2 State Event Messages

3.3.3 Parameter Transmission to the Web Service

3.3.4 Contractor Data Backup

3.4 PERFORMANCE REQUIREMENTS

3.5 QUALITY ASSURANCE CHECKS

3.6 CONTRACTOR QUALITY CONTROL

3.7 LIST OF ITEMS PROVIDED BY THE CONTRACTOR

-- End of Section Table of Contents --

SECTION 35 20 23.33 Page 2

SECTION 35 20 23.33

NATIONAL DREDGING QUALITY MANAGEMENT PROGRAM

PIPELINE HYDRAULIC DREDGE

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 MEASUREMENT AND PAYMENT

No separate measurement or payment shall 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 the contract unit price per hour for "Dredging" and "Option Dredging".

1.3 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.

1.4 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.

SECTION 35 20 23.33 Page 3

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 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

SECTION 35 20 23.33 Page 4 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.

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.

SECTION 35 20 23.33 Page 5

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 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

SECTION 35 20 23.33 Page 6 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".

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".

SECTION 35 20 23.33 Page 7

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.

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).

SECTION 35 20 23.33 Page 8

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 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

SECTION 35 20 23.33 Page 9 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 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

SECTION 35 20 23.33 Page 10

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 l east 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 connec tor

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

Other hardware Category 5 (Cat-5) cable with standard RJ-45 plugs connecting the n etwork 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.

SECTION 35 20 23.33 Page 11

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 local District's 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, 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.

SECTION 35 20 23.33 Page 12

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.

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>, SECTION 35 20 23.33 Page 13

"comment": }, "contract_event": { "msg_time": , "contract_number": , "event_type": ,…