S1.1c_225_175_MPCMS_Support_PWS_2014-19_bridge.docx

DOCX document 45 KB Posted

Attached to
MPCMS WLB-225 AND WLM-175
Solicitation number
70Z085-19-Q-P4535200
Issued by

About this file

Performance Work Statement

View the file

Other files

File Type Posted
Amendment_0002_MPCMS_WLB_WLM.pdf PDF
Amendment_0001_MPCMS_WLB_WLM.pdf PDF
Solicitation_WLB_WLM_MPCMS.docx DOCX document
Past_Performance_Questionnaire.doc DOC document
S1.4d_JA_WLM_WLB_SUPPORT_BRIDGE_RAD_Signed_Redacted.pdf PDF
OMBUDSMAN_PROGRAM_LETTER.docx DOCX document
S1.1b_BLANK_IGE_WLB_WLM_MPCMS_Support_20190724_1yr_bridge.xlsx XLSX spreadsheet
Solicitation_WLB_WLM_MPCMS.docx DOCX document
Request_for_Clarification_doc.docx DOCX document

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

ATTACHMENT 1

PERFORMANCE WORK STATEMENT

1 GENERAL

Provide repair and maintenance of the Machinery Plant Control and Monitoring System (MPCMS) and related subsystems onboard the WLB-225 A class, WLB-225 B class, and WLM-175 class vessels involving the equipment and processes below. See section 2 below for applicable references. These services include conducting appraisals, inspections, reports, repairs, and tests on a recurring basis throughout the contract period and any option years exercised under the contract. Required services will include shipboard performance, onsite service(s) during sea trials and in-shop engineering support to include software. The service representative(s) and engineer(s) will be required to provide all parts and perform all labor to complete appraisals, inspections, reports, repairs, and tests.

At a minimum, the Government will require four (4) grooms onboard cutters, with associated circuit card repairs, remote troubleshooting telephone support and associated reports as outlined below. Additional hours of technical on-site troubleshooting and engineering services may also be required. These services will be determined by the Contracting Officer’s Representative (COR) and approved by the Contracting Officer (KO) based upon the nature of the casualty. Troubleshooting MPCMS problems beyond the scope of the groom will be handled as an optional item. The KO and COR may choose to activate any combination of optional items as necessary to troubleshoot and repair casualties or provide MPMCS support.

Materials and parts not connected to services may be procured under this contract.

When the system is altered, provide updates to technical manuals and drawings to document the changes. The quality of such changes shall be no less than that of the affected technical manual or drawing before the update.

Generally, most required service will be performed aboard the vessel at a Government mooring. In some instances, work aboard the vessel will be necessary while it is moored or dry-docked at a commercial facility, such as a shipyard. Repair or work on the following onboard equipment (hardware and associated software) may be required:

· Engineering Control Center Console (ECCC)

· Main Ship Control Console (MSCC)

· Port and Starboard Secondary Conning Stations (SCS)

· The TANO Network (TANOnet)

· Remote Terminal Units (RTU)

· MPCMS Data Logger System

· Uninterruptable power supply (UPS) and feeder supplying the MPCMS

· Operator workstations

1.1 Required Standard of Workmanship

Unless otherwise specifically required for within this contract, the quality of all services rendered hereunder shall conform to the highest standards of the relevant profession, trade, and/or field of endeavor. All services shall be rendered by individuals fully qualified in the relevant profession, trade, or field. The required obtainment and maintenance of any licenses required by law are also required by the terms of this contract.

1.2 Prior Written Permission Required for Subcontracts

None of the services required by this contract shall be subcontracted to or performed by persons other than the contractor or the contractor’s employees without the prior written consent and authorization of the KO.

1.3 Source Code

The MPCMS source code is written in ADA 95. The firmware which runs on the RTUs is proprietary and the Government does not have access to the source code.

1.4 Serial Data Encoding

Data transmitted over RS-422 serial networks between RTUs and the VME processors is encoded in a proprietary binary format. Data transmitted over RS-485 serial lines within each RTU and console is also encoded. The Government does not have access to the coding schemes and the decoding algorithms.

2 REFERENCES

2.1 Coast Guard Drawings

· Coast Guard Drawing 175-WLM 202-1, Rev J, MPCMS Cabling Diagram

· Coast Guard Drawing 175-WLM 202-2, Rev F, MPCMS Cabling Diagram COED

· Coast Guard Drawing 175-WLM 202-6, Rev B, MPCMS Wiring Modifications to Main & Secondary Consoles (551-559)

· Coast Guard Drawing 175-WLM 202-7, Rev C, MPCMS Wiring Data Modifications to Consoles (COED), Hulls 551-559

· Coast Guard Drawing 175-WLM-202-201, Rev Q, MPCMS

· Coast Guard Drawing 225-WLB 202-1, Rev F, MPCMS Cabling Diagram

· Coast Guard Drawing 225-WLB 202-2, Rev G, MPCMS COED

· Coast Guard Drawing 225B-WLB 202-2, Rev D, MPCMS Connection Table

· Coast Guard Drawing 225B-WLB 202-1, Rev G, MPCMS Cabling Diagram

2.2 Coast Guard Publications

· Coast Guard Technical Publication (TP) 3605 A & B Machinery Plant Control & Monitoring System Operating Manual (MPCMSOM)

· Coast Guard Technical Publication (TP) 3607 MPCMS Computer System Operating Manual (CSOM)

· Coast Guard Technical Publication (TP) 3608 MPCMS Computer System Diagnostic Manual (CSDM)

· Coast Guard Technical Publication (TP) 3509 MPCMS Software User's Manual (SUM)

· Coast Guard Technical Publication (TP) 3505 A & B Machinery Plant Control & Monitoring System Operating Manual (MPCMSOM)

· Coast Guard Technical Publication (TP) 3585 A& B Machinery Plant Control & Monitoring System Operating Manual (MPCMSOM)

· Coast Guard Technical Publication (TP) 3932 MPCMS Data Logging System

· Coast Guard Technical Publication (TP) 3589 MPCMS Computer System Manual

· Coast Guard Technical Publication (TP) 3507 MPCMS Computer System Operating Manual (CSOM)

· Coast Guard Technical Publication (TP) 3508 MPCMS Computer System Diagnostic Manual (CSDM)

· Coast Guard Technical Publication (TP) 3509 MPCMS Software User's Manual (SUM)

· SFLC Technical Standard 086, June 2013, Technical Publications (TP)

· COMDTINST M9085.1, Rev C, Naval Engineering Computer Aided Design Standards

· CGTO PG-85-00-230-S, August 2013, Planned Maintenance System Development Process Guide 3 MAINTENANCE FOR WLB A and B, WLM CLASS VESSELS Each maintenance visit may include any or all of the tasks listed below as determined by the COR on a ship-by-ship basis in support of MPCMS. Submit a Condition Found Report (CFR) to the COR for any discrepancies found during performance of this contract within 24 hours of discovery.

3.1 Grooms

3.1.1 Procedure. Develop and submit a written procedure to groom the system. Prepare a test plan delineating all tests to be performed on core system components and functions to be assessed during performance of the shipboard groom. Provide a detailed written test procedure for each item on the test plan, including pass/fail criteria and a list of parts to be expended. Additional parts may be added to the list after initial submittal based on upgrade/changes, either by choice of the manufacturer or due to obsolesce of the parts.

3.1.2 Test sequence. Prepare a test sequence Gantt chart that shows the inspections, calibrations, maintenance actions, and pre-operational tests to be performed on shipboard equipment while dockside, as well as the post-groom operational tests to be performed during dock trials or sea trials. Include the expected duration of each task, show any task interdependencies or sequencing, and note where coordination with grooms of other systems outside the scope of this work item is required. List any other additional data or documentation required for the groom.

3.1.3 Performance. During each shipboard groom visit, test, calibrate, and validate system and component performance as outlined in the Groom Test Sequence and detailed in the Groom Performance Test Plan. The technical representative shall arrive at the cutter to perform the groom as scheduled by the COR. At least 14 days (21 days if the cutter will not be located within the continental United States, Alaska, Hawaii, or Puerto Rico during the visit) of advance notice will be provided. For such testing, Coast Guard personnel will operate cutter equipment under the guidance of the Contractor. The Contractor shall be responsible for all equipment adjustments and calibrations during the groom visit, but shall actively engage Coast Guard personnel while performing these tasks for their familiarization benefit. If disagreement arises over the extent of Coast Guard participation in the groom, immediately notify the COR and request resolution.

3.1.4 Accountability. Provide a single on-site point of contact for the duration of the groom who will be responsible for all employees and subcontractors.

3.1.5 Additional work. Submit a CFR for any additional tasking that may be required to correct any MPCMS equipment deficiencies that fall outside of the scope of the groom. Provide a separately priced proposal describing the tasking, required labor, and associated costs to correct the deficiency. This separately price proposal may or may not be accepted by the Coast Guard, negotiated, and executed at time of the groom.

3.1.6 Tasks. When authorized by the COR, perform the groom procedure over a period of no more than three (3) days with two (2) additional days for testing and validation. In the service report or CFR, provide detailed observations and describe the corrective actions taken about all asterisked (*) tasks below:

3.1.6.1 Groom the ECC Console and all contained subsystems and components, including:

· VME printed circuit cards and frames

· Individually mounted printed circuit cards

· Data logger

· Power supplies, filters, relays, sockets, connectors, and fuse blocks

· Power supply auctioneering and relay coil discharge diodes

· Watch dog timer

· Vital alarm system

· Video monitors

· Keyboards, buzzers, fans, and trackballs

· Indicators, switches, and meters

· Engine order telegraph

· Terminal boards and internal wiring

· RS-232, RS-422, and RS-485 serial communication channels

3.1.6.2 Check the MPCMS software revision and load with the most current version.*

3.1.6.3 Document the firmware revision loaded on each printed circuit card with a processor. Install the most current firmware version on each card if not already loaded.*

3.1.6.4 Replace all old and significantly discharged batteries installed on processor and memory cards.*

3.1.6.5 Groom all RTUs and remote consoles, including any interfaces to external equipment such as the thrusters.*

3.1.6.6 Test all direct current power supplies individually and renew any that fail to carry normal load.*

3.1.6.7 Inspect all 5 VDC power supply input power isolation relays and sockets. Renew any with cracks or visible deterioration.*

3.1.6.8 Check the tightness of all internal and external cable terminations, including screw terminals which may vibrate loose over time. Check all circuit board connectors for tightness and adjust contact gripping force as needed to improve continuity.*

3.1.6.9 Validate that the system is operating within the manufacturer’s specifications.

3.1.6.10 Verify that all system instrumentation, controls, sensors, data acquisition modules, optical isolators, and communication channels are properly operating.*

3.1.6.11 Confirm that the system is fully interoperable with other systems with which it interfaces. This will include review of in-line data collection devices that may be installed.

3.1.6.12 Repair, renew, adjust, calibrate, and test improperly functioning system components. A CFR is required documenting arrival conditions as well as results. This includes serial numbers and installation dates of equipment. If no emergency issues, this shall be documented in the final report as per section 5.

3.1.6.13 Perform component and system planned maintenance tasks that have been approved by the Coast Guard.

3.1.7 Serial data port monitoring. As directed by the COR, install equipment to monitor serial communication traffic and interrupt requests through the VME backplane. Log all anomalies, including excessive message lengths, corrupt data, and multiple retransmissions to build a reliability history.

3.1.8 Operational testing. Conduct operational testing, including 1 day of underway testing, after completion of all in port tasks. Such underway testing should be considered to be part of every groom; however, this requirement may be waived by the COR.

3.2 Circuit Card Services

Provide in-shop inspection, testing, and repair of MPCMS and other TANO system cards. Submit a monthly report and an annual report of all system cards in inventory to include condition and availability. Provide an expedited shipping option for parts upon COR request.

3.3 Engineering Services

As directed by the COR, provide engineering services for both hardware and software to Product Line key personnel. Such services may be requested to develop and refine the recommended scope of work for casualty repair (CASREP), prepare training, provide technical guidance on the system, describe component theory and operation, implement performance monitoring programs, or analyze casualties.

3.4 Inspection, Survey, Airfare, Per Diem, Ground Transportation, and Travel Contractor personnel are required to perform the work under a resultant task or delivery order at various locations around the world. Contractor’s quoted price should include the possibility that work may be performed during Saturdays, Sundays and holidays. Compensation for underway periods will not exceed 12 hours per day unless the actual time actively spent working is greater. Price quotes for airfare, per diem, ground transportation and travel will be made in accordance with Joint Travel Regulations (JTR), as amended. Of note, the contractor will be required to hold a valid U.S. Passport and area clearance to visit designated vessel if located overseas.

3.5 On-Site Troubleshooting Support

Provide onsite troubleshooting service of the MPCMS and associated systems. Such may include participation in dockside or underway performance testing, evaluation, and validation. Document all efforts and changes effected.

3.5.1 Responsiveness. If the ship is at home port, the technical representative shall arrive at the cutter within 24 hours of receiving authorization from the COR. If the ship is away from home port, initiate travel within 48 hours of receiving authorization from the COR; the technical representative shall arrive at the cutter or designated embarkation point no longer than 24 hours later.

3.5.2 Performance test. When ordered by the COR, the MPCMS performance test shall include the following elements (note that the system may be modified over the life of this contract to perform some functions listed below which are not presently possible):

· Observation that commands originated from MPCMS are promptly transmitted to and received by interfacing systems.

· Observation that human-machine interface (HMI) screens are updated in near real time in response to status changes, alarms, and monitored parameter variations in interfacing systems.

· Observation of the alarm stack to ensure that alarms occurring nearly simultaneously are all captured.

· Observation that uncommanded state changes are detected and displayed when interfacing machinery systems are operated using a local control mode or are tripped by an independent safety system.

· Analysis of any command failures to determine the cause and isolate the problem to MPCMS or the interfacing machinery system.

· Review of the alarm log to verify that all logged alarms were legitimate and that no alarms transmitted by interfacing systems were delayed or never displayed.

· Review of the event log to verify that all logged events were legitimate and that no events transmitted by interfacing systems were delayed or never captured.

· Review of the network and communications logs to verify that no anomalies occurred on the network or communication channels during interfacing system operation.

· Audit of the data logger to ensure that a representative sample of logged machinery operating parameters was being accurately recorded at the proper scan rate.

3.6 Remote Troubleshooting Support

3.6.1 Call center. Provide remote troubleshooting support via telephone line to individual cutter crews and support staff. The telephone line shall be maintained at all times. Document all calls to include time, date, caller, and a summary of troubleshooting services provide. If a problem is not resolved within 4 hours of an initial call, electronically notify the COR immediately. A report of calls and resulting recommendations shall be provided to the COR monthly. A consolidated annual report of all calls and recommendations shall be provided to the COR.

3.6.2 Responsiveness. During regular working hours, acknowledge all requests within 1 hour and provide initial technical action for the crew no later than 2 hours after acknowledgement. At all other times, acknowledge each request within 4 hours and provide initial technical action for the crew no later than 4 hours after acknowledgement. If this time frame cannot be met, then notify the COR or KO within 4 hours after acknowledgement and provide a plan for responding.

4 DEFINITION OF STRAIGHT (REGULAR) TIME, OVERTIME, AND PREMIUM TIME

4.1 Straight Time

Normal work of eight (8) hours per day, five (5) days per week, Monday through Friday.

4.2 Overtime

Any work in excess of eight (8) hours per day or any work performed on Saturdays.

4.3 Premium Time

Any work performed on Sundays or holidays. The holidays applicable to this contract are as follows:

New Year’s Day
1 January
Martin Luther King Day
Third Monday in January
President’s Day
Third Monday in February
Memorial Day
Last Monday in May
Independence Day
4 July
Labor Day
First Monday in September
Columbus Day
Second Monday in October
Veteran’s Day
11 November
Thanksgiving Day
Fourth Thursday in November
Christmas Day
25 December

5 LOGISTICS SUPPORT REQUIREMENTS (Applies to new equipment only) Logistics support requirements are necessary to establish and maintain life cycle support for equipment procured by the Government. The logistics documentation required by the contract is in the form of an equipment technical manual, technical support data, repair parts support, and parts usage data associated with equipment repairs performed by contractors. The United States Coast Guard Surface Forces Logistics Center is designated as the technical office for all issues relating to logistics support requirements. All reports and deliverables identified in this section shall be submitted in the English language only within 30 business days to the COR and KO.

5.1 Technical Manual Requirements

Content for technical documentation (technical publications and drawings) to be provided shall be as defined herein and as in SFLC Technical Standard 086 (available upon request via the COR or KO). Provide data rights documentation that allows publication on the Coast Guard Intranet and distribution to the Fleet. Quantities shall be provided as specified herein. Additional requirements for the content of technical documentation shall be as identified in Engineering Data for Provisioning (EDFP).

5.1.1 Technical Publications. Develop and provide a Technical Publication for the installation, operation and maintenance of any new components or system. Technical Publications shall be delivered on CD-ROM or DVD-ROM in unlocked and unencrypted Adobe Acrobat PDF format. Chapters, sections, major paragraphs, parts lists, drawings, figures, and appendices shall be hierarchically indexed with bookmarks. Text on all sheets, except drawings and photographs, shall be searchable when practicable. A copy of all source documents used to prepare the PDF shall also be provided in their native editable format, such as Microsoft Office (DOC, XLS, or MDB), or AutoCAD DWG. Technical publications should include (as applicable):

· Cover and title page

· Manufacturer’s name and address

· Equipment name and application

· Table of contents (including a list of drawings and tables)

· Safety precautions (cautions, warnings, and notes)

· General theory of operation

· Complete functional description of equipment based on a block diagram

· Complete explanation of mechanical features using block diagrams or cutaway drawings

· Major assemblies broken into individual circuits, accompanied by complete circuit analysis keyed to a simplified schematic

· Brief descriptions of complex and unusual circuits

· Voltage waveforms at significant points in the circuit

· Memory maps and a description of microprocessor functions

· Preparation for use, installation, and initial adjustment instructions

· Operational instructions

· Maintenance instructions (preventive and corrective)

· Cleaning and lubrication instructions

· Performance verification and test features

· Frequency of adjustment, including required test equipment

· Trouble shooting instructions

· Disassembly, repair, replacement and reassembly instructions

· Installation instructions diagrams, illustrations, and schematics

· Parts list data – the parts list will identify all components and assemblies necessary to generate a complete bill of material. The following requirements apply to the parts list:

· Original equipment manufacturer (OEM) part number, OEM commercial and government entity (CAGE) code, if available, or OEM description, address and telephone number.

· All parts shall be keyed (using index numbers) to exploded view drawings.

· Parts in the listings shall be grouped by assemblies, subassemblies, and modules. Parts shall be identified in the assembly in which they are components.

· Parts listed in the technical manual will match the technical support data parts list as required by section 5.2 below.

5.1.1.1 Draft Deliverable – One (1) paper and one (1) electronic draft copy of the Technical Publication shall be submitted to the COR for review and approval. Comments will be returned along with the assignment of a Coast Guard Document number.

5.1.1.2 Final Deliverable – One (1) paper and one (1) electronic copy of the Coast Guard approved Technical Publication shall be provided to the COR for each affected cutter. One additional copy of the electronic files shall be provide for the Government’s technical library and shall include all source files used to produce the Technical Publication. Upon direction from the KO, vendor should be capable of providing printed copies of each technical manual for each affected vessel. Printed manuals shall be permanently imprinted by mechanical means and the cover shall be durable to withstand frequent handling and exposure to oil and water. The binding shall permit adding and removing pages.

5.1.1.3 Drawings. Develop and provide system and component drawings and diagrams in AutoCAD version 2012 in accordance with COMDTINST M9085.1. Standard Coast Guard drawing border templates are available via the internet at: http://www.uscg.mil/SFLC/drawings.asp or upon request via the COR or KO.

5.2 Integrated Logistics Support

Provide the following logistical support and information for any new equipment proposed and/or installed on the MPCMS. Modifications made to the equipment provided during the term of the contract must be accompanied by updates of all the following that relate to those changes.

5.2.1 Engineering Data for Provisioning (EDFP). Provide Engineering Data for Provisioning (EDFP). Include a parts list containing all of the installed parts, along with the original equipment manufacturer (OEM), OEM part or assembly numbers, the OEM’s name and address, the OEM’s cage code, and quantity used in each equipment, keyed to the provided drawings. All spare parts necessary for overhaul of a unit shall be identified in the printed technical documents supplied.

5.2.2 Recommended Spare Parts Lists. Provide with the EDFP/PTD a recommended spare parts list for onboard repair parts (OBRP) and stock system parts. The spare parts list shall list applicable manufacturer’s maintenance tasks for each line item (both preventive and corrective). Refer to section 5.4 for additional information.

5.2.2.1 Onboard spare parts – Onboard spare parts are items that unit personnel can replace without additional special tools or technical support.

5.2.2.2 System Stock – System stock shall be the long lead time materials (materials with lead times over 90 days) and manufacturer designated critical items.

5.2.3 OEM Maintenance Requirements. Provide OEM maintenance recommendations, in addition to the maintenance recommendations in the Technical Publication, to allow for Government development of Maintenance Procedure Cards. Guidance for providing this information can be found in Chapter 7 of CGTO PG-85-00-230-S (available upon request via the COR or KO). Identify at least the following line items:

· Applicable maintenance task code

· Maintenance procedure title

· Maintenance procedure interval

· Maintenance procedure description

· Maintenance procedure sequenced tasks

· Maintenance procedure

· Maintenance procedure task type

· Associated parts name and number

· Quantity of parts per maintenance task

· Associated parts unit of issue

· Associated parts shelf life

· Associated parts unit price

· Special tools and equipment nomenclature

· Special tools and equipment CAGE and part number or National Stock Number

· Task descriptions

5.3 Technical Support Data (TSD)

Provide complete and accurate data with delivery of the equipment. Submit a revision whenever engineering changes and/or modifications occur which add to, delete from, or modify previously submitted Technical Support Data (including changes to manufacturer’s part numbers). When TSD documents are prepared by other than the OEM, the preparer shall be identified by their company’s name, an address, telephone number and point of contact.

5.3.1 Contents of Technical Support Data

5.3.1.1 The TSD documentation consists of an illustrated parts breakdown along with the following:

· Bill of materials or list of all repair parts

· List of assemblies and subassemblies

· Special tools and test equipment required to maintain, repair or overhaul the equipment and components

5.3.1.2 The documentation shall include, at a minimum, the following technical data for each individual part, assembly and subassembly:

· OEM’s part number

· OEM’s commercial and government entity (CAGE) code (if no CAGE is available, provide OEM address, description and the telephone number)

· OEM’s drawing that identifies the part (illustrated parts breakdown)

· Characteristic/name plate data/certification data for the end item and all equipment

· Item name

· Reference symbol number (for electronic provisioning only)

· Production leads time (if known)

· Unit of issue

· Unit price

· Unit of measure

5.3.2 Alternate submission of technical support data. TSD documentation may be replaced with an equipment technical manual meeting the requirements of section 5.1 above, providing the technical manual contains the minimum data requirements set forth in section 5.2.1 above. Provide any additional TSD documentation not contained in the technical manual in order to meet the minimum requirements of section 5.2.1 above.

5.4 Repair Parts Support

Provide the Government with a pre-priced recommended list of spare parts with delivery of equipment. The recommended spares list shall be of sufficient range and depth to provide one year of preventive maintenance and up to 10 years of corrective maintenance support for equipment specified in the contract broken out by year based upon life cycle of components. The Government may exercise the option to purchase any or all parts so recommended. In determining the necessary spares support, consider the equipment’s maintenance requirements (preventive and corrective), component criticality and historic failure rates. The recommended spares list shall include as a minimum:

· Part number, nomenclature and description

· Part quantity per component

· Recommended quantity

· Unit of issue

· Unit price

· Total price

5.5 Repair Parts Usage Data

Provide parts usage data associated with all equipment repairs made under this contract. The documentation shall include the following information (by each piece of equipment repaired):

5.5.1 Nomenclature and model number of equipment repaired (end item)

· Part nomenclature

· Part number

· Part quantity used

· Part manufacturer

5.5.2 Data shall be submitted electronically within 14 days of completion of work.

6 FIELD SERVICE REPORTS

Provide a field service report at the conclusion of each task order, describing the work performed, including details of any corrective actions taken. Reports shall be submitted within 10 business days to the COR and KO.

File details come from the government source that posted it.