09B0014_0001.pdf

W26GLG91627655

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

MAINTENANCE DREDGING, PAGAN RIVER, HAMPTON CREEK, AND HERBERTS CREEK

1. CONTRACT ID CODE PAGE OF PAGES

J 1 2

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

16C. DATE SIGNED

BY 24-Jun-2009

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 W91236-09-B-0014

X 9B. DATED (SEE ITEM 11)

22-Jun-2009

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. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

24-Jun-2009

CODE

USA ENGINEER DISTRICT, NORFOLK

CONTRACTING OFFICE

803 FRONT STREET

NORFOLK VA 23510-1096

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W91236-09-B-0014

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

AMENDMENT – 0001

1. Technical Specifications, DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION for both Part 1 Maintenance Dredging Pagan River and Part 2 Part 2, Maintenance Dredging Hampton Creek and Herberts Creek, delete SECTION 35 20 30 in its entirety and replace with the attached new SECTION 35 20 30, Attachment.

2. Contractors are strongly advised to bid the solicitation, specifications, and plans as posted unless changed via an Amendment.

3. Contracting Point of Contact:

Tracey J. Hughes 803 Front Street Norfolk, VA 23510 757-201-7131

FAX 757-201-7183

SECTION 35 20 30

SILENT INSPECTOR FOR BARGES AND SCOWS

06/09

PART 1 GENERAL

1.1 DESCRIPTION

The work under this contract requires use of the Silent Inspector System to monitor the trip number, the time-position history for the scow, course over ground, speed and the hull status. This performance-based specifications section identifies the minimum required output and 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; G, SAM-OP-J

SD-07 Certificates

Letter of Silent Inspector Certification; G, OP

1.3 PAYMENT

No separate payment will be made for the installation, operation and maintenance of the SI system as specified herein for the duration of the dredging operations; all costs in connection therewith will be considered a subsidiary obligation of the Contractor and covered under the contract unit prices for dredging in the bidding schedule.

1.4 SILENT INSPECTOR CERTIFICATION

The Contractor is required to have a current Silent Inspector Certification for the scow instrumentation system to be used under this contract not later than ten working days after issuance of the Notice to Proceed. Certification shall be based on an on-site scow inspection conducted by Silent Inspector Support Center personnel.

An Inspection Shall Include:

• A series of data quality checks as described in paragraph 3.4 “Compliance Inspection and Quality Assurance Checks”,

• Verification of data acquisition and transfer (Paragraph 3.2),

• Review of the Dredge Plant Instrumentation Plan (DPIP) as described in

Paragraph 1.5.

A Silent Inspector Certification is valid for one year from the date of certification if the system is not turned off, disconnected or removed from the scow. The owner or operator of the scow should contact the SI Support Center on an annual basis at 1-877-840-8024 to schedule re-inspection, allowing ample time for recertification, and coordinate this with all local authorities. The Contractor shall have personnel, who are familiar with the SI system instrumentation and who have the ability to recalibrate the sensors, on site during the inspection. Re-inspection is required for any changes in sensor type or location; these changes will be reported in the sensor log section of the DPIP.

1.5 DREDGE PLANT INSTRUMENTATION PLAN (DPIP)

The Contractor shall have a DPIP on file with the National SI Support Center.

The Contractor shall also maintain a copy of the DPIP on a working dredge on site which is readily accessible to Government personnel at all times. This document shall describe how sensor data will be collected, how quality control on the data will be performed, and how sensors/data reporting equipment will be calibrated and repaired if they fail. A description of computed scow specific data and how the sensor data will be transmitted to the Silent Inspector Database shall also be included. The Contractor shall submit to the SI Support Center any addendum or modifications made to the plan, subsequent to its original submission, prior to Notice to Proceed.

The DPIP shall include the following as a minimum:

(DPIP must have table of content in the following order)

Dredging Company

• Dredge Point of Contact

• Phone Number

Scow Monitoring System Provider

• Scow Monitoring System Point of Contact

• Telephone Number

Scow ID Sensor repair, replacement, installation, modification or calibration methods Data reporting equipment

Procedure for providing sensor data/computed data to SI Database via e-mail

System Power Supply System Battery Charge Method If the system is left in place past the end of the contract, how will the contract number be changed System telemetry Dimensioned Drawings of the Scow

• A typical plan and profile view of the scow showing:

o Locations of required sensors referenced to:

fore and aft perpendicular each other o overall scow dimensions Criteria and method used to increment trip number Description of how the UTC time stamp is collected Positioning system

• brand name and specifications

• sampling rates for data acquisition (standard vs. dump)

• instrument used to calculate COG

• any calculation done external to the instrumentation

• certificates of calibration and/or manufacturer certificates of compliance

• A description of how scow speed is determined

Hull status

• Instrumentation brand name and specifications

• Certificates of calibration and/or manufacturer certificates of compliance

• Any calculation done external to the instrumentation

• Criteria for determining hull open/closed

Bin status criteria used to determine open/closed measurements of bin status

Contractor Data

• Backup frequency

• Backup method

• post processing

Archive capability Documentation of :

• test methods used by the Contractor to provide quality control of data

• verification that the reported values are applicable for the sensor and application

Log of sensor performance and modifications

Any changes to the computation methods during the contract shall be approved by the Silent Inspector Support Center prior to their implementation.

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 the specifications. The Contractor shall be responsible for replacement, repair and calibration of sensors and other necessary data acquisition equipment needed to supply the required data.

Repairs shall be completed within 48 hours after any sensor failure occurs. Upon completion of a repair, replacement, installation, modification or calibration the Contractor shall notify the Contracting Office’s Representative. The Contracting Office’s Representative may request re-calibration of sensors or other hardware components at any time during contract execution 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 to include: the time of sensor failure (and its subsequent repair), the time and results of sensor calibrations, the time of sensor replacements, and the time when backup sensor systems are initiated to provide required data. It shall also contain the name of the person responsible for the sensor work. Only sensors that affect the data reported in paragraph 3.2.6, “Reporting Data Metadata”, are affected by this logging requirement.

3.1.1 Scow Name

Each scow shall be assigned a unique name that will remain constant from one dredge operation to the next.

3.1.2 Trip Number

A trip number shall be reported for each dump run. The trip number will be incremented at the completion of each dump/emptying of the scow. Each scow shall maintain a separate trip numbering sequence – i.e. each scow will start with a trip number of 1, that will be incremented by 1 each time that scow completes a dump.

3.1.3 Horizontal Positioning

Horizontal positioning of the antenna location or center of scow shall be obtained using a Positioning System operating with a minimum accuracy level of 1 to 3 meters horizontal Circular Error Probable (CEP). Positions shall be reported as Latitude/Longitude WGS 84.

3.1.4 Date and Time

The date and time shall be reported to the nearest second and referenced to UTC time based on a 24 hour format.

3.1.5 Hull Status

Open/closed status of the bin, corresponding to the split/non-split condition of a split hull scow shall be monitored. An “OPEN” value shall indicate the hull is split. A “CLOSED” value shall indicate the hull is not split. For non-dump scows, the “OPEN” value shall indicate that the bin is in the process of being unloaded, either by pumping or mechanical means.

3.1.6 Scow Course

Scow course-over-ground shall be provided using industry standard equipment.

The Contractor shall provide scow course over ground (to the nearest whole degree) with values from 000 (true north) to 359 degrees referenced to a clockwise positive direction convention.

3.1.7 Scow Speed

Scow speed-over-ground shall be provided in knots using industry standard equipment with a minimum accuracy of 1.0 knots and resolution to the nearest 0.1 knot.

3.2 DATA REPORTING REQUIREMENTS

Contractor collected information shall be transmitted to the SI Database. The parameters which shall be reported to the SI Database include: trip number, date and time, hull status, scow course, scow speed.

3.2.1 Data Reporting Interface

The Contractor may select any commercial satellite, cellular phone, or other data communications systems available to transmit the data to the SI Database via the Internet in the required mail message format. The data transition process from the scow to the SI database must be automated. The data may be sent from the scow directly to the SI database or to a shore based computer. Data transmitted to the SI Database shall be raw data; any processing of the data conducted shore side shall be done using an automated software or programming routine. A description of this process shall be included in the DPIP.

3.2.2 Data Measurement Frequency

Data shall be logged as a series of events. Each set of measurements (e.g. time, position, etc…) will be considered an event. Data shall be measured with sufficient frequency by the scow system to resolve the events to the accuracy specified in the following table.

Event Type

Scow Status Event Description Event Time Resolution

Event Position Resolution

1 Stationary/loading with hull status

“CLOSED”

An elapsed time of 1 hour since the last event

1 minute NA

2 Moving with hull status “CLOSED”

Distance from the last event position equals or exceeds 0.5 nautical miles

1 second +/- 10 ft

3 Hull status “OPEN” A position must be recorded within 1 second of the hull status going from CLOSED to OPEN – distance from the last event position equals or exceeds 30 feet

1 second +/- 10 ft

The system shall have the capability of storing at least the previous 1000 events.

A time trigger may be used for event types 2 and 3 at the discretion of the SI Support Center, if it can be demonstrated that the data density will be consistent with the above logic.

3.2.3 Data Reporting

The system shall report the event history via Simple Mail Transport Protocol (SMTP) e-mail message to the SI Database Server. For this contract data will be reported on an event basis (sebt as dats is collected). All data for an event shall be transmitted to the SI Database no later than 24 hours after the event’s occurrence.

If the scow has a certified system aboard, it shall transmit data continuously to the SI Database from mobilization until the final USACE post-dredging survey has been accepted. If the scow does not have a certified system at the time of issuance of the Notice to Proceed, it shall begin transmitting data at the time it is certified prior to the start of dredging operations, and continue until acceptance of the final USACE dredging survey. In the event of sensor failure, a manual dump log shall be maintained and submitted on a daily basis to the Contracting Officer’s Representative.

3.2.4 Mail Message Format

The Simple Mail Transport Protocol, SMTP, (Internet FRC 2821) shall be used to report data to the SI Database. Mail messages shall have the following contents (Internet RFC 2822):

To: sidatatransfer@usace.army.mil From: contractor’s email address Subject: SISDATA Transfer Attachment: SI SDATA html file

Mail message start of body

SISDATA

SI Scow Data Transfer Blank line

Optional additional annotations from the Contractor – all data after the blank line are ignored.

End of message

3.2.5 Mail Attachment File Format

The attached data file shall be a MIME encoded (Internet RFC 2045) Extensible HyperText Markup Language (W3C standard XHTML 1.1) document. Any length of data may be included, but the file attachment size should not exceed six Megabytes. Only the html, table, tr, th, td, h2, h3 and body tags are permissible.

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="eng"> <body>

<h2 class = “contract”>contract number</h2>

<h3 class = “vessel_name”>scow name</h3>

<table class = “SISDATA”> <tr> <th>TRIP_NUMBER</th> <th coord_type = “(LL)”>X_POSITION</th> <th coord_type = “(LL)”>Y_POSITION</th> <th>DATE_TIME</th> <th>HULL_STATUS</th> <th>SCOW_COURSE</th> <th>SCOW_SPEED</th> </tr> <tr> <td>trip number value</td> <td>x position value</td> <td>y position value</td> <td>date time value</td> <td>hull status value</td> <td>scow course value</td> <td>scow speed value</td>

</tr> <tr> … repeated for additional data records </tr> </table> </html> </body>

3.2.6 Reporting Data Metadata

Data shall be reported to the SI database using the tags and criteria specified in the following table:

Header Tag Tag Notes vessel_name The name of the scow contract The USACE contract number under which the work is being performed, or the applicable permit number.

TRIP_NUMBER Trip numbers shall start at 1 at the beginning of work for each contract or permit. Trip numbers are incremented at the completion of the disposal/placement part of the scow cycle. Each scow maintains a unique set of trip numbers.

X_POSITION Longitude in decimal degrees. West Longitude values are reported as negative.

Y_POSITION Latitude in decimal degrees. North Latitude values are reported as positive.

Header Tag Tag Notes DATE_TIME mm/dd/yyyy hh:mm:ss defined as UTC time in 24hr format.

HULL_STATUS OPEN or CLOSED are the only permissible values.

SCOW_COURSE The scow course over ground reported from 0 to 359 degrees.

SCOW_SPEED The scow speed measured in knots at the reported time.

3.2.7 Contractor Data Backup

The Contractor shall maintain an archive of all data sent via SMTP to the SI Database. The Contracting Officer’s Representative 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 on PC format USB flash drive, CD-ROM, file transfer protocol (ftp) upload, or other storage medium acceptable to the Contracting Officer’s Representative. At the end of the dredging contract the Contractor is responsible for contacting the national SI Support Center prior to discarding the data to ensure all data have been appropriately archived. The person who made the call, the date of the call, and the representative who gave permission to discard the data should be recorded in a separate section at the end of the Contractor’s copy of the DPIP.

3.2.8 Data Reporting Example

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="eng"> <body> <h2 class = “contract”>DACW01-05-C-0001</h2> <h3 class = “vessel_name”>COE Scow 1</h3> <table class = “SISDATA”> <tr> <th>TRIP_NUMBER</th> <th coord_type = “LL">X_POSITION</th> <th coord_type = “LL">Y_POSITION</th> <th>DATE_TIME</th> <th>HULL_STATUS</th> <th>SCOW_COURSE</th> <th>SCOW_SPEED</th> </tr> <tr> <td>21</td> <td>1777345.1</td> <td>893256.8</td> <td>04/11/2004 12:01:55</td> <td>CLOSED</td>

<td>111</td> </tr> </table> </body> </html>

3.3 PERFORMANCE REQUIREMENTS

The Contractor’s Silent Inspector system shall be fully operational at the start of dredging operations. To meet contract requirements for operability, the Contractor’s system shall provide a minimum 95 percent data return and be 95 percent compliant with DPIP requirements. Data return percentage is defined as the total number of quality records sent, divided by the total possible number of records that could be sent by a system in good working order. Quality data strings are considered to be those providing accurate values for at least 6 of the 7 data parameters reported. DPIP compliance is determined by percent of items listed in Paragraph 1.5 to be at minimum compliance. After fifty percent project completion, combined percentage of data return and DPIP compliance should equal 95 percent or greater. If repairs necessary to restore 95 percent data return are not made within 48 hours, or if the Contractor fails to report required data within the specified time window for scow measurements (see paragraph 3.2.2 “Data Measurement Frequency” and 3.2.3 “Data Reporting”); the system will be declared not fully operational, and the Contractor will be assessed liquidated damages equivalent to the additional oversight hours that would be required for Corps personnel to be on site from the first full day after the system is deemed not fully operational through to the time when the system is returned to operational status. For this contract, the liquidated damages shall be $400.00 per day.

3.4 COMPLIANCE INSPECTION AND QUALITY ASSURANCE CHECKS

The Contractor shall submit a test data package to the SI Database from the system on each scow and have it accepted by the SI Support Center prior to scow compliance inspection.

Quality assurance checks are required prior to the commencement of dredging, and at the discretion of a Contracting Officer’s Representative, periodically throughout the duration of the contract. As part of the testing requirements, the Contractor shall provide the Contracting Officer’s Representative a visual display of measurements from the scow monitoring system in the same units that are submitted to the SI database. These measurements shall be provided in real-time on the scow or near real-time on location. The Contractor shall also submit data collected during the inspection from the scow monitoring system to the SI database at completion of inspection.

3.4.1 Position Check

During certification inspections, both the static position of the scow and a track of movement to and from the dump area will be monitored by an independent GPS unit and compared to the SI collected data. A contractor furnished tug will be required to transport the scow during this check, which will monitor time position of the scow, and verify that data collection intervals change as the scow enters and leaves the disposal area. Throughout the contract, the Contracting Officer’s Representative will periodically verify reported positions by independently measuring with other equipment to verify locations.

3.4.2 Hull Status Check

The Contracting Officer’s Representative will document the angle at which the hull status sensor registers “OPEN” and “CLOSED”.

3.5 LIST OF ITEMS TO BE PROVIDED BY THE CONTRACTOR

DPIP Sec 1.5 Dredge Plant Instrumentation Plan

SI SYSTEM

Sensor Instrumentation Sec. 3.1 Specifications for Reported Data

SCOW DATA

Event documentation Sec. 3.2.2 Data Measurement Frequency Data reports Sec. 3.2.3 Data Reporting