Attachment_III_-_Statement_of_Work_(A00004).pdf

Statement of Work

Machinery Plant Control & Monitoring System Upgrade

VER: 18 August 2014

Contents

1.0 General

2.0 Definitions and References

3.0 Performance Tasks

4.0 Verification

5.0 Deliverables

6.0 Contract Line Item Deliverables (CLIN)

1. General

1.1 Background:

1.2 Scope: The Contractor shall provide all management, supervision, personnel, labor, materials, and equipment required to remove, modify, install, test, calibrate, certify, and provide training required to upgrade the Machinery Plant Control & Monitoring System

(MPCMS) installed on U.S.C.G. 225’ WLB Cutters listed in paragraph 2.21 and in accordance with this Statement of Work.

1.3 Personnel Qualification Standards

1.3.1 Program Manager: The Contractor shall provide qualified personnel to perform all of the services for this Statement of Work (SOW). This list shall include a single point of contact (POC), designated as the Coast Guard Liaison.

The services required by this SOW shall not be subcontracted to or performed by persons other than the Contractor without prior consent of the Contracting Officer (KO).

The Contractor shall provide a list of personnel that will be performing the services described herein. The Contractor shall notify the KO and Contracting Officer’s

Representative (COR) in writing of changes to personnel working on this contract.

1.3.2 Security Clearance: A security clearance is not required to perform this work; however, all contractor personnel working on or visiting Government installations are required to be U.S. citizens and have valid U.S. Government identification (Social Security

Numbers, driver license, passport, etc.).

1.4 Period of Performance: All work covered by this Statement of Work shall be completed within 3 years of Contract Award.

1.5 Schedule of delivery: The items marked TBD in the schedule depend on cutter availability.

It is the intent of the Government to install this upgrade as quickly as possible, but as of the date of the request for bid the installation dates for any specific cutter are not known.

1.6 Bid Process: The Contractor shall provide two schedules with costs in a Gantt chart format that addresses the resources required to accomplish the contract tasks. Schedule one shall focus on providing a time line that represents best cost to accomplish the tasks in the contract. Schedule two shall focus on providing a time line that represents fastest means to accomplish the tasks in the contract.

2. Definitions and References

2.1. U.S. Coast Guard Technical Publication: TP – 3505 A & B MACHINERY PLANT

CONTROL & MONITORING SYSTEM OPERATING MANUAL (MPCMSOM)

2.2. U.S. Coast Guard Technical Publication: TP – 3585 A& B MACHINERY PLANT

CONTROL & MONITORING SYSTEM OPERATING MANUAL (MPCMSOM)

2.3. U.S. Coast Guard Technical Publication: TP – 3932 MPCMS DATA LOGGING SYSTEM

2.4. U.S. Coast Guard Technical Publication: TP – 3589 MPCMS COMPUTER SYSTEM

MANUAL

2.5. U.S. Coast Guard Technical Publication: TP – 3507A MPCMS COMPUTER SYSTEM

OPERATING MANUAL (CSOM)

2.6. U.S. Coast Guard Technical Publication: TP – 3508A MPCMS COMPUTER SYSTEM

DIAGNOSTIC MANUAL (CSDM)

2.7. U.S. Coast Guard Technical Publication: TP – 3509A MPCMS SOFTWARE USER'S

MANUAL (SUM)

2.8. USCG 202 Drawing: 225-WLB_202_1, Rev F, MPCMS CABLING DIAGRAM

2.9. USCG 202 Drawing: 225-WLB_202_2, Rev G, MPCMS COED

2.10. USCG 202 Drawing: 225B-WLB_202_2, Rev D, MPCMS CONNECTION TABLE

2.11. USCG 202 Drawing: 225B-WLB_202_1, Rev G, MPCMS CABLING DIAGRAM

2.12. USCGC JUNIPER INSTRUCTION 3540.1B – WLB Casualty Control Manual (CCM)

2.13. American Bureau of Shipping, Steel Vessel Rules (ABS SVR), 1998, Part 4, Section 11

(Shipboard Automatic or Remote Control and Monitoring Systems) with propulsion class symbol

ACC

2.14. Institute of Electrical and Electronics Engineers (IEEE) Std 45-1998 Recommended

Practice for Electric Installations on Shipboard

2.15. Institute of Electrical and Electronics Engineers (IEEE) Std 829-2008, Standard for

Software and System Test Documentation

2.16. 46CFR 62 (1998) Code of Federal Regulations, subchapter F

2.17. MIL – STD – 1399 Interface Standards for Shipboard Systems, Section 300B, Electric

Power, Alternating Current.

2.18. MIL-DTL-24643C, Cables, Electrical, Low Smoke Halogen-Free, For Shipboard Use, General Specification for

2.19. National Electrical Manufacturers Association (NEMA) 250-2008, Enclosures for

Electrical Equipment (1000 Volts Maximum)

2.20. National Marine Electronics Association (NMEA) 0183, v 4.10, Standard for Interfacing

Marine Electronic Devices

2.21. List of Applicable Cutters and their homeports.

2.21.1 USCGC JUNIPER (WLB-201), Newport, RI

2.21.2 USCGC WILLOW (WLB-202), Newport, RI

2.21.3 USCGC KUKUI (WLB-203), Honolulu, HI

2.21.4 USCGC ELM (WLB-204), Atlantic Beach, NC

2.21.5 USCGC WALNUT (WLB-205), Honolulu, HI

2.21.6 USCGC SPAR (WLB-206), Kodiak, AK

2.21.7 USCGC MAPLE (WLB-207), Seward, AK

2.21.8 USCGC ASPEN (WLB-208), San Francisco, CA

2.21.9 USCGC SYCAMORE (WLB-209), Cordova, AK

2.21.10 USCGC CYPRESS (WLB-210), Pensacola, FL

2.21.11 USCGC OAK (WLB-211), Charleston, SC

2.21.21 USCGC HICKORY (WLB-212), Homer, AK

2.21.13 USCGC FIR (WLB-213), Astoria, OR

2.21.14 USCGC HOLLYHOCK (WLB-214), Port Huron, MI

2.21.15 USCGC SEQUOIA (WLB-215), FPO AP, Guam 96678

2.21.16 USCGC ALDER (WLB-216), Duluth, MN

2.22. USCG Surface Forces Logistics Center (SFLC) Documents

2.22.1. COMDTINST M9085.1C, Naval Engineering Computer Aided Design

Standards

2.22.2. D-086-0508, Technical Documentation Specifications (Tech Publications

& Drawings)

2.22.3. SFLC Std Spec 3042, 2012, Shipboard Electrical Cable Removal, Relocation, Splice, Repair, and Installation

3. Performance Tasks

3.1. The Contractor shall provide all resources and materials required to complete the following tasks in accordance with the schedule of deliverables in Section 5.0 Deliverables.

3.2. Host a project kickoff meeting at the Contractor’s facility to review the contract documents including the performance tasks and deliverables (CLIN 1.1). The Contractor shall provide the following at the kickoff meeting:

3.2.1. System block diagrams of the existing and proposed system upgrades.

3.2.2. Operator and maintainer training requirements.

3.2.3. A list of components to be removed and installed.

3.2.4. A list of developmental software to be used.

3.2.5. A list of personnel working on the project and their qualifications.

3.2.6. Record and provide meeting minutes.

3.3. The Contractor shall provide a Plan of Action and Milestones (POA&M) (CLIN 1.2) that includes the following:

3.3.1. The performance tasks, including sequencing logic and contractor resources for each item, required to develop the system (CLIN 1and CLIN 2).

3.3.2. The notional deployment schedule.

3.3.3. Mitigation strategies for schedule, technical, and cost risks.

3.3.4. Development start and completion dates for each software module, piece of hardware, test procedure, and draft engineering document.

3.3.5. Bi-weekly progress report to update the developmental schedule, problems encountered, and achieved milestones (CLIN 1.3); however, issues requiring immediate actions shall be conveyed verbally and via email to both the Contracting Officer (KO) and the Contract Officer’s Representative(s)

(COR).

3.4. The Contractor shall provide bi-weekly progress reports which shall be provided to the

Government for review and comment/approval as required (CLIN 1.3). Issues requiring immediate actions shall be conveyed verbally and via email to both the KO and the COR(s). The contractor shall conduct all communications with only the KO or the assigned COR(s). Bi weekly progress reports shall include the following:

3.4.1. Updates to the POA&M

3.4.2. HMI screen updates for review, comment and approval as completed.

3.4.3. Schedule issues, risks and the steps taken to manage them.

3.4.4. Project performance issues and risks, including technical and engineering problems, and the steps taken to correct.

3.4.5. An Email or verbal means to discuss, review and document emergent concerns.

3.4.6. Completed milestones.

3.5. The Contractor shall upgrade the MPCMS VME Subsystem to replace the obsolete VME computers and associated equipment as per the SOW. The upgraded system shall retain all of the current capabilities of the existing system as stated in references 2.1-2.7 and meet the requirements of paragraph 2.13 (ABS SVR ACC), paragraph 2.14 (IEEE – STD- 45), and paragraph 2.16 (46CFR 62).

3.5.1. The contractor shall replace the existing system hardware and associated

ADA software with commercial off the shelf hardware and software. The applications shall have two levels of password protected user access.

3.5.1.1. Level 1 (highest level of access and modification permissions and shall include Level 2 security permissions and administrative privileges).

3.5.1.2. Level 2 (this level provides the ability to change set points, alarm delays, Level 2 password changes, and logging functions).

3.5.1.3. Default factory passwords shall be provided to the COR.

3.5.2. The MPCMS shall have a hardened network to include the following security measures:

3.5.2.1. Hardened operating system protected from modification and the prevention of new user creation by Level 2 users.

3.5.2.2. Removal of any unnecessary programs (i.e. games, or household applications)

3.5.2.3. Closure of any unused network ports

3.5.2.4. Prevention of access to MPCMS from any unauthorized

computers, switches or other networking devices.

3.5.2.5. Prevention of USB access to the MPCMS system from

unauthorized devices

3.5.3. Cable and wire markings and identification shall comply with the style and nomenclature used in the existing system and found in references 2.1 through

2.11. The contractor shall provide and install new or reroute existing cable, as necessary, in accordance with paragraph 2.22.4 (SFLC Std Spec 3042).

3.5.4. The Contractor shall remove cables, wire, and components no longer used in the MPCMS as a result of the upgrade.

3.5.5. The Contractor shall set aside circuit cards and computer components, displays, keyboards, and power supplies in a location designated by the cutter’s representative.

3.5.5.1. Areas of concern include Port and Starboard Quarterdecks, Engineering Log Office, EO’s Stateroom, the Bridge, and the Engineering

Control Center. The Contractor shall ensure that fire-tight and watertight boundaries are maintained after installation.

3.5.5.2. The cutter’s representative will contact the IBCT product line for equipment disposition instructions. All other materials shall be disposed of by the Contractor.

3.6. The system shall retain or improve upon all of the current capabilities in terms of redundancy, speed, operation, control and monitoring, and graphics. System design shall also include the following changes:

3.6.1. Provide a new direct communications path between DPS and MPCMS that is serial and NMEA 0183 based, independent of the DDS LAN network. The

Contractor shall coordinate this upgrade with the DPS OEM, L-3

Communications Dynamic Positioning and Controls.

3.6.2. Remove the ECDIS interface including alarm exchange and monitoring and the

SMG and COG messages found on the WLB B class cutters; however, the

MPCMS shall continue to provide the NMEA 0183 $PTAN message that provides propulsion information to the ECDIS. This shall be done via separate one way communications to the DDS LAN.

3.6.3. Provide the means to manually enter the system date and time from any ECC workstation.

3.6.3.1. Date time information shall be retained upon loss of power for 48 hours.

3.6.3.2. Software shall be able to detect whether the date and time requires updating upon restoration from a loss of power.

3.6.3.3. Updating system date and time at a MPMCS HMI computer in the

Engineering Control Center shall update all computers.

3.6.4. Provide graphical pages with modern mimics and appropriate use of color, similar to those found in industry, to better associate displayed data with the equipment to which it pertains.

3.6.4.1. The graphics shall provide the user an interface to implement the additional features herein. Improved graphics are desired and will be reviewed during HMI progress reviews.

3.6.4.2. Provide a propulsion system graphic user interface that allows the operator to use a mouse to select an item from a system level arrangement. The selected item shall link to detailed equipment page which includes operating parameters and alarms.

3.6.4.3. When navigating between pages on HMI computers, the new screen shall refresh in less than 1 second, and changing screens shall happen in less than 1 second.

3.6.5. Provide monitoring of communication traffic between MPCMS and DPS. The system shall log, alarm and timestamp data that is not properly formatted or contains checksum errors. This information shall also display on an alarm page and on a new communications monitoring page.

3.6.5.1. The communications monitoring page shall continuously update to provide twelve messages of data between the DPS and MPCMS.

3.6.5.2. The data shall be provided in a text box.

3.6.5.3. The system shall provide the ability to freeze and resume the message updates in the text box.

3.6.6. Provide data logging recording capability to replace the obsolete data recorder with the additional provisions as follows:

3.6.6.1. Continue to provide the capability of storing 3 years worth of logged data and provide the means to move the data to an exportable media.

3.6.6.2. Provide the capability to log 25 user selectable analog points at a rate of 1 per second. This capability shall provide a log that stores data for

1 month and overwrites data that is more than one month old.

3.6.6.3. Provide an alarm set point change log and display graphic that provides a list of set point changes from the default.

3.6.6.4. Provide a means to export log data in comma separated value

(CSV) format to DVD/RW.

3.6.6.5. Modify the Machinery Plant Status Log Interval to have a logging period from 1 to 4 hours in 1 hour increments. This represents a change by removing the capability to secure Machinery Plant Status Logging and to limit the logging period to once every 4 hours as a maximum.

3.6.6.6. Provide the capability for an operator to print the Machinery Plant

Status Log directly to the data logger on demand via keyboard input. This capability shall be available to the operator at least once per minute and shall not impact the performance of the MPCMS.

3.6.7. Remove the 75% thrust limit for the bow and stern thruster and restore the original thruster range of 100% thrust. The Contractor shall provide additional testing on prototype vessels to ensure proper system operation and that the new thruster limits work well.

3.6.8. Provide a laptop computer with for quarterdeck operation, OBT, and the following:

3.6.8.1. Provide a connection port and cables for use on the bridge.

3.6.8.2. Provide a connection port and cables for use on the port and starboard quarterdecks.

3.6.8.3. Provide a connection port and cables for use in the Engineering

Control Center for the future implementation of onboard training.

3.6.8.4. Provide the future capability to use as the instructor station for the onboard trainer.

3.6.8.5. The laptop computer shall meet the vibration and environmental requirements for shipboard operation. Shipboard operation for laptop computers is defined as in an environmental protected against the outdoors, while meeting the vibration requirements of ABS.

3.6.8.6. The Contractor shall provide 3 laptops in their quote.

3.6.9. The Contractor shall provide an Onboard Trainer (OBT) as follows:

3.6.9.1. The OBT module of the MPCMS upgrade shall remain separate and independent of the core MPCMS during development. The OBT module shall be integrated into the core MPCMS software per paragraph for testing per paragraphs 4.18, 4.19, and 4.20. OBT shall not negatively affect MPCMS operation or the mission of the core application.

3.6.9.2. The MPCMS OBT shall be incorporated into future MPCMS cutter installations upon successful prototype evaluation CLINs 5.4 and 5.5.

3.6.9.3. Provide the function to allow HMI Panel C5 (outboard starboard bay) of the Engineering Control Center Console to login as an OBT student workstation. Distinctive banners shall be displayed on HMI screens that are in training mode to alert the operator when a simulation is running on the console. While in the training mode, operation of the workstation peripherals (keyboard and trackball) will have no effect on actual machinery or equipment, but will be evaluated by the simulation routine to progress the scenario. Displayed status pages and mimics shall update to simulate expected conditions and maintain a sense of realism during each exercise.

3.6.9.4. Develop MPCMS initial conditions and casualty indicators that reflect the WLB Casualty Control Manual (CCM) (reference paragraph

2.12) found in chapter 2 of the manual.

3.6.9.5. Provide a preliminary MPCMS OBT Technical Manual (CLIN 5.12)

3.6.9.5.1. The manual shall provide instructions on how to configure the system for OBT and how to return the system to regular operation.

3.6.9.5.2. The manual shall provide instructions on how to use the OBT instructors and student station.

3.6.9.5.3. The manual shall provide instructions on how to use the system to start, modify conditions, and stop each exercise.

3.6.9.5.4. The manual shall provide graphics and illustrations to aid the instructor on using the OBT system.

3.6.9.6. The Government’s intent for OBT is to have an instructor station

(quarterdeck laptop computer) provide conditions to the student station, HMI computer C5. Both computers shall be placed in training mode. The instructor station shall be capable of sending plant status information to the student station. At a minimum this shall include MDE On/Off, Clutch

On/Off, Engine Speed and Propeller Speed, SSDG and EDG status

On/Off, Bus Status, thruster status, propulsion status (maneuvering mode/transit mode). The instructor station shall be capable of changing the plant status with a series of check boxes and entering analog data manually for display on the student station. The instructor station shall also be able to cause alarms and malfunctions to display on the student station as found in the CCM with the same method as initiating plant status.

3.6.9.7. Actions that affect the plant status will be carried on the active part of the MPCMS such as reducing speed, lighting off fire pumps, shutting down engines, etc. However, the instructor shall be able to mimic changes to the plant via the instructor station.

3.6.9.7.1. Basic Engineering Casualty Control Exercises (BECCE) found in chapter 2 of the CCM. At a minimum, the on board trainer shall be capable of realistically simulating underway and dockside conditions including the following engineering casualty scenarios:

3.6.9.7.1.1. CG-ENG-03, Loss of MPCMS

3.6.9.7.1.2. CG-ENG-04, Major Fuel Oil Leak

3.6.9.7.1.3. CG-ENG-05, Loss of Control Air Pressure

3.6.9.7.1.4. CG-ENG-07, Hot Bearing Reduction Gear/Line Shaft

Bearing

3.6.9.7.1.5. CG-ENG-12, Loss of CPP Pitch Control

3.6.9.7.1.6. CG-ENG-13, Overheating Diesel Engine MDE or SSDG

3.6.9.7.1.7. CG-ENG-18, MDE Loss of Lube Oil Pressure

3.6.9.7.1.8. CG-ENG-20, MDE Loss of Fuel Oil Pressure

3.6.9.7.1.9. CG-ENG-24 Loss of Clutch Air Pressure

3.6.9.8. Provide an OBT Factory Acceptance Test (CLIN 5.2) for

Government review and approval.

3.6.9.8.1. The Contractor shall provide a pre meeting/discussion test and an after meeting discussion.

3.6.9.8.2. The Contractor shall incorporate comments as directed by the

COR that are within the scope of work, and provide a FAT acceptance certificate at the conclusion of testing for signature.

3.6.9.8.3. The Contractor shall provide a test and operational results document.

3.6.9.8.4. The FAT shall demonstrate the following:

3.6.9.8.4.1. BECCE screen look and operation.

3.6.9.8.4.2. Placing the MPMCS into OBT mode and restoring to normal operation.

3.6.9.8.4.3. Perform each BECCE listed in paragraph 3.6.9.7.1 demonstrating OBT operation.

3.6.9.9. Install OBT for Integration testing and training at C3CEN. (CLIN

5.3).

3.6.9.9.1. Integration testing and training shall include the following:

3.6.9.9.1.1. After the OBT upgrade is installed, the Integrated Ships

Control System (ISCS) shall be run in DPS follow track mode for

48 hours without fault.

3.6.9.9.1.2. OBT training shall be provided to Government Personnel for 5 days, while the ISCS is running while simulating different operating conditions without fault.

3.6.9.9.1.2.1. OBT training shall include the BECCEs from

paragraph 3.6.9.7.1.

3.6.9.9.1.2.2. OBT training shall include starting and stopping the training session and placing the system into and out of training mode.

3.6.9.9.1.2.3. OBT training shall follow the preliminary OBT

training manual provided to verify contents.

3.6.9.10. Provide OBT Prototype installation, testing, testing, and training to

WLB A Class Cutter.(CLIN 5.4)

3.6.9.10.1. OBT shall be installed during the 60 day prototype evaluation period of CLIN 3.2.

3.6.9.10.1.1. The Government will make the MPCMS Prototype cutter available 30 days after the prototype evaluation period begins to install and provide training of the OBT to the cutter.

3.6.9.10.1.2. The Government will continue to perform prototype evaluation of the system as a whole for an additional 30 days.

3.6.9.11. Provide OBT Prototype installation, testing, testing, and training to

WLB B Class Cutter CLIN (5.5)

3.6.9.11.1. OBT shall be installed during the 60 day prototype evaluation period of CLIN 3.3.

3.6.9.11.1.1. The Government will make the MPCMS Prototype cutter available 30 days after the prototype evaluation period begins to install and provide training of the OBT to the cutter.

3.6.9.11.2. The Government will continue to perform prototype evaluation of the system as a whole for an additional 30 days.

3.6.9.12. Provide an update to the updated Engineering Package and

Installation booklet with OBT, and final OBT technical manual for

Government review and approval. (CLIN 5.6)

3.7. The Contractor shall provide a Factory Acceptance Test (CLIN 1.4) for Government review and approval.

3.7.1. The Contractor shall record test results and meeting minutes. The

Contractor shall provide a pre meeting/discussion test and a post meeting/discussion.

3.7.2. The Contractor shall incorporate comments and take action as directed by the COR that are within the scope of work.

3.7.3. The FAT shall demonstrate the following:

3.7.3.1. Computer and network system redundancy.

3.7.3.2. HMI graphical user screen look and feel

3.7.3.3. HMI station operation and navigation

3.7.3.4. HMI integration and redundancy

3.7.3.5. Date and Time entry and display

3.7.3.6. Data logging functions and ability

3.7.3.7. TANONET RTU integration

3.7.3.8. Alarm detection, announcing, and display functions

3.7.3.9. Control functions of the plant

3.7.3.10. System malfunction detection BITE and BIT

3.7.3.11. DDS LAN integration changes

3.8. Preliminary Engineering Documentation. The Contractor shall develop and provide preliminary engineering documentation (CLIN 1.5) for Government review and approval as follows:

3.8.1. Draft system rip-out and installation table providing a list of cables and equipment to be removed and installed.

3.8.2. Draft conditions found test procedures and conditions found reports.

3.8.3. Draft commissioning test procedures, in accordance with IEEE – STD –

829 or equal, sufficient to validate MPCMS system performance integration and operation. The test plan shall include the following:

3.8.3.1. Level Test Plan Clause 9

3.8.3.2. The Level Test Cases Clause 10, Level Test Procedures Clause

11, and Level Test Logs Clause 12, which may be combined.

3.8.3.3. Anomaly report Clause 14

3.8.3.4. Level Test Report Clause 16

3.8.3.5. Signature/Acceptance block for Government Witness and COR.

3.8.4. Software flowcharts.

3.8.5. Draft Conditions Found report

3.8.6. Draft MPCMS upgrade booklet

3.8.7. Redundancy and error checking flowcharts, including database synchronization.

3.8.8. Serial data flowcharts, including baud rates and polling intervals.

3.8.9. Operating system for installed computers.

3.8.10. Software loading and update instructions for MPMCS computers.

3.8.11. Provide an Interface Design Document (IDD) in the same format as found within the current data logging software “WLB MPMCS.MDB”. The IDD shall include modifications to the base software as modified by this specification.

3.8.12. Provide an IDD for communications between MPCMS and DPS.

3.9. Final Engineering Documentation. The Contractor shall develop and provide final engineering documentation (CLIN 2.3) for Government review and approval as follows:

3.9.1. System rip-out and installation drawings, with corresponding written instructions and quality control steps for the technicians performing the work.

3.9.2. Conditions Found Report Format:

3.9.3. Draft commissioning test procedures, in accordance with IEEE – STD –

829 or equal, sufficient to validate MPCMS system performance integration and operation. The test plan shall include the following:

3.9.3.1. Level Test Plan Clause 9

3.9.3.2. The Level Test Cases Clause 10, Level Test Procedures Clause

11, and Level Test Logs Clause 12, which may be combined.

3.9.3.3. Anomaly report Clause 14

3.9.3.4. Level Test Report Clause 16

3.9.3.5. Signature/Acceptance block for Government Witness and COR.

3.9.4. Software flowcharts.

3.9.5. Redundancy and error checking flowcharts, including database synchronization.

3.9.6. Serial data flowcharts, including baud rates and polling intervals.

3.9.7. Software loading and update instructions for MPMCS computers

3.9.8. Operating system for installed computers.

3.9.9. Load analysis to show the expected and maximum power consumed and delivered by each power supply, as well as the maximum demand on the

MPCMS uninterruptable power supply (UPS)

3.9.10. Provide an Interface Design Document (IDD) in the same format as found within the current data logging software “WLB MPMCS.MDB”. The IDD shall include modifications to the base software as modified by this specification.

3.9.11. Provide an IDD for communications between MPCMS and DPS.

3.9.12. A complete set of MPCMS screen layouts.

3.9.13. A Copy of all source code developed for the benefit of the Government.

3.9.14. A Copy of all compiled software and executable files.

3.9.15. A Copy of all configuration files, including default or baseline settings.

3.9.16. Original media and licenses for all software.

3.9.17. A Complete revision of all MPCMS technical documentation, reflecting the as built system.

3.9.18. A MPCMS system upgrade booklet (Paragraph 3.10)

3.10. MPCMS System Upgrade Booklet. The Contractor shall develop and provide a system upgrade booklet that contains all of the information required to install and commission the

MPCMS for Government review and approval as follows:

3.10.1. The booklet shall be submitted to the Government for review and approval.

3.10.2. The booklet shall be divided into sections for each stage of the upgrade, and shall be in a format that flows with the installation.

3.10.3. The booklet shall provide onsite storage, and space requirements for equipment received for cutter installations.

3.10.4. The booklet shall include an installation time line and names and number of Contractor personnel that will be performing the each stage of work. This information shall be updated prior to each installation.

3.10.5. The booklet shall include instructions on coordinating the upgrade with the DPS OEM, and shall be upgraded to reflect the DPS OEM schedule and level of effort.

3.10.6. The booklet shall include instructions to conduct an in-brief with the cutters Command prior to commencing work that provides an outline of the work to be accomplished and include the following:

3.10.6.1. The Command designation of a Point of Contact(s) (POC) for the

Contractor to communicate updates.

3.10.6.2. The Contractor shall coordinate work schedules for each phase of system installation and testing with the POC.

3.10.6.3. The Contractor shall coordinate and work with the POC during each testing phase and each test.

3.10.7. The booklet shall include a pre-installation test plan with a condition found report (CFR) that documents the condition of the MPMCS and the equipment/systems that the MPMCS communicates, controls, and monitors.

3.10.7.1. The report shall be signed by Contractor personnel conducting the testing

3.10.7.2. The report shall provide a signature block for a Government witness to sign.

3.10.7.3. The report shall include instructions to forward the signed CFR to the COR and KO upon completion to allow the Government time to arrange repairs as required.

3.10.7.3.1. The receipt. Conditions that have been identified as “no go” by the Contractor will be repaired by the Government under a separate

Contract.

3.10.7.3.2. When a condition is identified that will prevent the installation of the upgrade the Government may cancel and reschedule the upgrade at the Government’s expense.

3.10.8. The booklet shall include a Bill of Materials (BOM) for equipment and cables to be installed. The BOM shall include signature blocks for the

Contractor and the POC to sign verifying that all materials are onsite prior to installation.

3.10.9. The booklet shall include equipment and cable removal instructions, drawings, and photos.

3.10.10. The booklet shall include equipment and cable installation instructions, drawings, and photos.

3.10.11. The booklet shall include test procedures for dockside system startup, integration, functional and operational testing.

3.10.11.1. Tests shall be performed in the company of a Government witness.

3.10.11.2. The test procedures shall provide a signature block for a

Government witness to sign.

3.10.11.3. Tests shall include DPS integration testing.

3.10.11.4. The report shall be signed by Contractor personnel conducting the testing

3.10.12. The booklet shall include test procedures for conducting underway testing. Underway testing shall include operational testing that demonstrates the system is free of errors and that the system as a whole is working error free.

3.10.12.1. The underway test plan shall be developed starting with the tests performed in paragraph 3.13 but reducing the scope of the test to three days.

3.10.12.2. Tests shall include DPS integration testing and DPS operational testing.

3.10.12.3. Tests shall be performed in the company of a Government witness.

3.10.12.4. The test procedures shall provide a signature block for a

Government witness to sign.

3.10.12.5. The test procedures shall be signed by Contractor personnel conducting the testing.

3.10.13. The booklet shall include a section that provides changes made during system installation and commissioning that were required during installations.

3.10.13.1. Changes to equipment and cabling shall be documented as red-line edits to the new drawings. Photos shall also be provided to document differences between expected instructions and actual instructions and forwarded to the KO and COR.

3.10.13.2. Changes made to software shall be documented and forwarded to the KO and COR for review and approval.

3.10.14. The Contractor shall update the booklet based on recommendations provided during the execution of this document. New revisions shall be provided to the KO and COR for review and approval.

3.10.15. The booklet shall include a training outline and procedures for system operators and maintainers.

3.10.15.1. Training shall be provided to groups of no more than 4 persons at a time.

3.10.15.2. Training shall be provided dockside and underway.

3.10.15.3. Training shall provide system operators and maintainers verbal and hands-on instruction on the use and maintenance of the MPCMS.

3.10.15.4. Training shall provide explanation of the new system functionality to the system operators and maintainers (i.e. examples of system operation before and after installation).

3.10.15.5. Training shall be provided separately for bridge and engineering control center crewmembers.

3.10.15.6. A training check off sheet shall be provided to be signed by a

Government witness.

3.10.16. The booklet shall include instructions to conduct an out-brief with the command after all work is complete that provides an outline of the work performed and an opportunity for the command to provide positive or negative feedback, and recommendations for future installs.

3.10.17. The booklet shall include a certificate of acceptance to be provided to the

COR after each successful install for review and signature.

3.11. Technical Data (TD). This section defines the requirements for the Contractor to provide

TD necessary to integrate the Contractor’s equipment into the design of Coast Guard Cutters and to begin logistical support documentation. (CLIN 2.1) The Contractor’s TD shall include as applicable:

3.11.1. Equipment technical/performance data for all major components including control unit parts, detectors, alarming devices, and any relevant accessories.

3.11.2. A generic system layout showing how the proposed system components form a complete system and how the system is capable of meeting the requirements of this specification.

3.11.3. A unique assembly part number, nomenclature, and original equipment manufacturer (OEM) Commercial and Government Entity Code (CAGE) Code.

3.11.4. General arrangement drawings detailing overall dimensions; required maintenance area dimensions; locations, size and type of all mechanical, electrical, electronic, and other shipboard installation and operating interface requirements.

3.11.5. Overall component and system weights, including an accounting of the change in weight as a result of old equipment removal and new hardware installation.

3.11.6. Equipment heat rejection values, BTU/hr or kW.

3.11.7. Manual, technical publication, and/or catalogue data detailing the installation requirements for each piece of equipment.

3.11.8. The Contractor’s TD shall include as applicable: The TD identified herein shall be provided within forty-five (45) days after activation of (CLIN-2).

3.11.9. Where system designs differ between A Class and B Class cutters, the following separate TD shall be submitted noting which class it is applicable to.

If tech data is identical, duplicate TD need not be submitted for each cutter class. Drawings shall be in accordance with reference 2.22.1.

3.11.10. System layout drawings identifying each piece of equipment, the location of each piece of equipment and the zone (where applicable) of each piece of equipment. Equipment shall be shown on ship layout drawings. Layout drawings shall identify and include the quantity of each identifiable component shown on the drawings. Drawings shall be based on general ship arrangements (references 2.8 and 2.11).

3.11.11. System block wiring diagram detailing the equipment single line connections, cable types and zone identification.

3.12. Data for Provisioning (DFP). The Contractor shall provide DFP for all components being supplied. DFP shall be provided after contract award as defined herein. DFP includes drawings, technical manuals, catalog data and product specification sheets to allow the provisioning of a system or piece of equipment. The DFP for the base year end item shall include all items listed below. (CLIN 2.1) The Contractor shall provide addendums to the

DFP for each item during the option years as required.

3.12.1. The Contractor shall put provisions in his lower-tier subcontracts and supply agreements requiring compliance with this Specification. The DFP that the Coast Guard requires from the Contractor’s subcontractors shall be provided by the Contractor.

3.12.2. DFP supplied shall include as a minimum:

3.12.2.1. A hierarchical listing of all components which can be assembled, re-assembled, and/or replaced. The listing shall identify primary components and all supporting components/parts. Figure 1 provides an example of how to list information.

Figure 1Example submission of DFP data for component hierarchy.

3.12.2.2. General arrangement and system diagrams.

3.12.3. The contractor shall update all Technical Manuals/Publications to completely describe the end item, end item’s equipment and/or piece parts;

material, mechanical, electrical, dimensional characteristics, location, and their function within the assembly. The technical publications shall include theory of operation, equipment and component set points and related technical

Hierarchy # Major Components Quantity OEM OEM CAGE Part # Estimated Retail Cost Description

Number identifying the hierarchy of the components and sub-components.

Name of major components of the system. Should include at a minimum the items outlined in Spec Section 3.2 but may include additional items per your design. Should not include items such as valves, foundations, hardware, etc. Sub-components should be listed beneath and indented from their main assembly.

Number of each component.

Original Equipment

Manufacturer that

USCG would contact to purchase a direct replacement part.

The Commercial and

Government Entity (CAGE)

Code of the OEM.

Identifying number used by the vendor.

Estimated Retail Cost for purposes of planning maintenance and repairs.

Brief description of the component including purpose, interfaces and other information to assist with understanding the configuration of the system

Service Filter Assembly 2 Company X K1234 12345-AB-6 $17,000 Main assembly that filters the fuel service system.

1.1 Filter Separator 1 1 Company Y B5432 12345-AB-7A $4,300

One of two separators used in parallel as part of the service filter assembly

1.2 Filter Separator 2 1 Company Y B5432 12345-AB-7B $4,300

One of two separators used in parallel as part of the service filter assembly information, disassembly procedures, recommended maintenance, maintenance and lay-up procedures, component repair and maintenance instructions, trouble shooting guide, parts schematic/line diagrams, and complete drawings and diagrams.

3.12.4. The contractor shall combine the following technical publications referenced in paragraphs 2.5, 2.6, and 2.7 for the WLB A Class shall be combined into one manual in the same fashion as found in reference 2.4, which is used on the WLB B class cutters. The contractor may further combine the

WLB A and WLB B class manuals referenced in this paragraph into one manual for both classes.

3.12.5. Illustrated Parts Breakdown- Identify parts associated with the equipment.

An exploded illustrated parts breakdown shall show the location of the parts.

The parts list shall identify the piece part of the illustration, quantity installed, nomenclature, designation, original manufacturer and manufacturer’s part number. Part numbers are not required for common hardware available from multiple sources, if adequate descriptive data is provided. Parts data listed in the technical manual shall be the same as listed on the hierarchical listing. If metric system components are provided, they shall be so noted.

3.12.6. All special tools and test equipment required to maintain the end item.

3.12.7. A list of all software/licenses needed to accomplish diagnostic testing.

3.12.8. Delivery of preliminary DFP shall be no later than one hundred and eighty

(180) days after activation of (CLIN - 2). The Coast Guard requires thirty (30) days to review DFP. The Contracting Officer, or his representative, will provide written approval or recommendations for improvement. The Contractor shall have thirty (30) days to correct and resubmit if the initial delivery is disapproved.

3.12.9. Delivery of final DFP shall be no later than 30 days per the schedule of deliverables.

3.12.10. Data Submission Format. Data files shall be delivered on CD-ROM or

DVD-ROM. A copy of all source documents used to prepare the PDF shall also be provided in their native editable format compatible with Microsoft Office 2007

(DOC, XLS, or MDB) or AutoCAD 2012 (DWG) applications. Where electronic media is submitted, it shall be with the manufacturer’s permission to use the data on Coast Guard drawings. Documentation supplied as electronic media shall be one (1) copy.

3.13. Integration installation and testing at C3CEN WLB Integrated Ships Control System

(ISCS) training facility (CLIN 3.1). The Contractor shall install and test the MPCMS upgrade as follows:

3.13.1. The Contractor shall coordinate work schedules for each phase of system installation and testing with the COR.

3.13.2. The Contractor shall execute verify and the Preliminary Engineering

Documentation (Paragraph 3.8).

3.13.3. The Contractor shall use this opportunity to develop the Final Engineering

Documentation (Paragraph 3.9).

3.13.4. The Contractor shall coordinate system installation and testing with the

DPS OEM.

3.13.5. The Contractor shall enable data logging to verify correct operation during testing.

3.13.5.1. The contactor shall enable 25 analog data points for 1 second recording for the duration of the test.

3.13.5.1.1. The Contractor shall demonstrate the operation of exporting logs upon completion of integration testing.

3.13.6. The Contractor shall take progress photos of before, during and after installation of equipment.

3.13.7. The Contractor shall coordinate ECDIS testing with the COR.

3.13.8. The Contractor shall maintain a test and change log documents

3.13.8.1. The test and change logs shall record the results from all tests and/or changes to technical documentation, hardware and software required to conduct successful functional testing.

3.13.8.2. The Contractor shall submit these documents for Government review and comment and approval.

3.13.9. The Contractor shall conduct functional and operational testing, and integration testing in accordance with the preliminary test procedures as outlined in 3.8.

3.13.10. The Contractor shall conduct functional and operational testing of the

MPCMS prior to system integration testing.

3.13.11. The Contractor shall rerun testing from the start upon failure of a test or upon making changes to software or hardware.

3.13.12. The MPCMS shall run for 4 hours prior to the start of functional and operational testing. Upon completion of functional and operational testing, the

MPCMS shall run for an additional 24 hours without failure.

3.13.13. System integration testing shall include operating the MPCMS in all modes with the DPS and the entire suite of ISCS systems and equipments online.

3.13.14. System integration testing shall include tests where the Contractor injects bad and malformed data to test DPS communication monitoring and alarm functions.

3.13.15. System integration testing shall include the additional scenarios as follows:

3.13.15.1.1. Testing shall include exercising the computer failover function in each test scenario found in paragraphs 3.13.15.1.2 through 3.13.15.1.6

3.13.15.1.2. 2 hours of MPCMS operation in transit mode followed by failing the active computer to ensure that the system redundancy functions correctly followed by 2 hours of operation on the backup computer.

3.13.15.1.3. 2 hours of DPS hold position mode operation followed by 1 hour of MPCMS throttle, tiller, and thruster testing in maneuvering mode. This test shall be rerun 2 additional times consecutively. A

DPS follow track mode test shall immediately follow this test.

3.13.15.1.4. 6 hours of DPS follow track mode testing followed by 2 hours DPS hold position mode. The test shall demonstrate that DPS integration is functioning. This test shall be rerun two additional times.

3.13.15.1.5. 1 hour of MPCMS operation in transit mode followed by 2 hours of DPS joystick operation in maneuvering mode followed by 1 hour of DPS joystick operation in transit mode followed by 2 hours of

DPS hold position mode. A DPS follow track mode test shall immediately follow this test for a minimum of two hours.

3.13.15.1.6. 8 hours of testing where alarms and faults and plant configurations are changed to ensure proper operation and stability of the system. Followed by 48 hours of continuous operational testing. This scenario shall include shutting down both MPCMS computers simultaneously followed by a restore to observe system operation.

3.13.16. The Contractor shall provide training to the WLB ISCS courseware developers and training personnel for operators and maintainers.

3.13.16.1. Training shall include instruction and demonstration on how to load software in the MPCMS.

3.13.17. The Contractor shall provide an acceptance certificate of compliance for signature by the COR.

3.13.18. Progress to CLIN 3 will not begin until Government Acceptance of CLIN 2

3.14. MPCMS prototype installs on one WLB A Class Cutter (CLIN 3.2) and one WLB

B Class Cutter (CLIN 3.3).

3.14.1. The Contractor is responsible for providing the required materials, test equipment, labor, and consumable items for each MPMCS install. The

Contractor shall ship all of these items for arrival prior to beginning the installation of the MPCMS upgrade.

3.14.2. The Contractor shall install and commission the MPCMS upgrade in accordance with the MPCMS System Upgrade Booklet (Paragraph 3.10) on each cutter.

3.14.3. The Contractor shall provide an additional 24 hours of dockside operational testing for the prototype installations.

3.14.4. The Contractor shall provide an additional 48 hours of underway operational testing.

3.14.5. The Government will provide 60 days notice prior to the start of an installation and coordinate site requirements to work on the cutter. The

Government will select prototype cutters based in the continental United States.

3.14.6. The Government will provide notice of installation schedule changes due to Cutter operational requirements.

3.14.7. After successful installation and commissioning the Government will evaluate the prototype for 60 days.

3.14.7.1. During this time the contractor shall provide system upgrades to hardware and software to correct deficiencies that may be reported by the

Government. Modifications made during this period shall be submitted to the Government for review and approval.

3.14.7.2. After the prototype evaluation period the Contractor shall provide a certificate of acceptance to the Government for review and signature.

3.15. MPCMS installs on remaining 225 WLB Class Cutters at the cutters homeport per reference 2.21.

3.15.1. The Contractor shall install the MPCMS upgrade as directed by the COR on WLB A Class Cutters and WLB B Class Cutters.

3.15.2. The Contractor is responsible for providing the required materials, test equipment, labor, and consumable items for each MPMCS install. The

Contractor shall ship all of these items for arrival prior to beginning the installation of the MPCMS upgrade.

3.15.2.1. Note: Shipping MPCMS upgrade to units in Hawaii, Alaska, and

Guam may take up to 30 days to arrive on-site.

3.15.3. The Contractor shall install and commission the MPCMS upgrade in accordance with the MPCMS System Upgrade Booklet (Paragraph 3.11) on each cutter.

3.15.4. The Government will provide 60 days notice prior to the start of an installation and coordinate site requirements to work on the cutter.

3.15.5. The Government will provide notice of installation schedule changes due to Cutter operational requirements.

4. Verification

4.1. The Contractor shall provide the materials from the kickoff In Accordance With (I.A.W.)

the requirements in paragraph 3.2, and per the deliverable schedule item 5.1 for

Government review and comment. The Government will review and provide comments to the Contractor within 5 days

4.2. The Contractor shall provide the POA&M I.A.W. the requirements of paragraph 3.3, and per the deliverable schedule item 5.2 for Government review and approval.

4.2.1. The Government will review the POA&M for 5 days and provide comments for incorporation into the POA&M.

4.2.2. The Contractor shall incorporate comments within 5 days and resubmit to the Government for approval.

4.2.3. The Government will review for 5 days.

4.3. The Contractor shall provide progress reports I.A.W. the requirements of paragraph 3.4 and per the deliverable schedule item 5.3 for Government review, comment and/approval.

4.3.1. Items requesting action by the Government will be addressed within 2 days of receipt.

4.3.2. The Contractor shall incorporate Government comments into HMI screens and resubmit for review and approval. Recommendations perceived as outside of the scope of work shall be jointly discussed and adjudicated.

4.4. The contractor shall conduct a Factory Test I.A.W. the paragraph 3.7 and per the deliverable schedule item 5.4.

4.4.1. The Contractor shall plan to receive up to 5 Government representatives for the Factory test.

4.4.2. The Contractor shall provide a copy of the test results and meeting minutes for Government review and comment.

4.4.3. The Contractor shall incorporate Government comments and resubmit for review and approval.

4.5. The Contractor shall provide the Preliminary Engineering Documentation package I.A.W.

paragraph 3.8 and per the deliverable schedule item 5.5.

4.5.1. The Government will review this document for 14 days and provide comments or approval.

4.5.2. The Contractor shall incorporate Government comments and resubmit for review and approval with 14 days of receipt.

4.6. The Contractor shall not proceed to CLIN 2 until Government reviews and approves the deliverables from CLIN 1.1, 1.2, and approves funding.

4.7. The Contractor shall provide the Preliminary Engineering Documentation package I.A.W.

paragraph 3.11 and 3.12 and per the deliverable schedule item 5.6.

4.7.1. The Government will review this documentation for 14 days for comments or approval.

4.7.2. The Contractor shall incorporate Government Comments for review and approval.

4.8. The Contractor shall install the MPCMS upgrade at the C3CEN ISCS training facility for integration testing. I.A.W. paragraph 3.13 and per the deliverable schedule item 5.9.

4.8.1. The Contractor shall provide test and change logs to the Government for review/comment/approval. The Contractor shall participate in this review on site at C3CEN. Comments shall be incorporated during the review.

4.8.2. The final document shall be provided to the Government for review and approval.

4.8.3. The Contractor shall provide an acceptance certificate of compliance for signature by the COR upon successful installation and testing of the MPCMS upgrade.

4.9. The Contractor shall provide the Final…