Attachment A - SOW.pdf

287 KB Posted

Attached to
U. S. Coast Guard Communication Management System (CMS)
Solicitation number
70Z02320RAPB02300
Issued by

About this file

Written by GovTribe AI ·

This statement of work outlines requirements for a communication management system to support the U.S. Coast Guard's Polar Security Cutter program. The contractor will design, test, and deliver up to three systems over five years, with each system including a red and black switching system, common end-user terminals, communication management software, and exterior communication system radio management. Key activities include kickoff and design reviews at the contractor's facility, final testing at the government's integration site, and travel support for integration. Optional line items allow the government to procure up to three total systems in years one through five. The system must meet requirements in the technical specification and interface with government-furnished radios, networks, and equipment.

View the file

Other files

File Type Posted
Repsonses to Questions 98 to 127.pdf PDF
Attachment M - NIST SP 800-53 rev4.pdf PDF
Attachment I - DoN CIO IA Pub 5239-31.pdf PDF
Attachment H - COMDTINST M5530.1C.pdf PDF
Attachment B - Technical Specification Amend 003.pdf PDF
Repsonses to Questions 59 to 78.pdf PDF
Attachment E - GFI Schedule Amend 003.pdf PDF
Attachment C - Pricing Worksheet - Amend 003.xls XLS spreadsheet
Attachment F - Compliance Matrix Amend 003.xlsx XLSX spreadsheet
Attachment N - DoDI 8540.01.pdf PDF
Attachment K - DoDI 8510.01.pdf PDF
Attachment A - SOW Amend 003.pdf PDF
Responses to Questions 128 to 162.pdf PDF
Attachment L - DOD 5200.08-R.pdf PDF
Attachment G - Sample Comms Plan.doc DOC document
Attachment J - CNSSAM 0113..pdf PDF
70Z02320RAPB02300 A003.pdf PDF
Repsonses to Questions 79 to 97.pdf PDF
70Z02320RAPB02300 QA2.pdf PDF
Attachment D - CDRL List A002.pdf PDF
Attachment E - GFI Schedule A002.pdf PDF
70Z02320RAPB02300 A002.pdf PDF
70Z02320RAPB02300 QA1.pdf PDF
Attachment F - Compliance Matrix.xlsx XLSX spreadsheet
Attachment B - Technical Specification.pdf PDF
Attachment E - GFI Schedule.pdf PDF
Attachment D - CDRL List.pdf PDF
SF 1449 CMS.pdf PDF
Attachment C - Pricing Worksheet.xls XLS spreadsheet
70Z02320RAPB02300 CMS.pdf PDF
Show all 30

On GovTribe

Work with this file

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

Text version

The file's text, extracted by GovTribe without its formatting.

Statement of Work

70Z02320RAPB02300 1

1. General Information

1.1. Scope. The scope of this Statement of Work (SOW) is to provide a Communication

Management System (CMS) to include; a Red (classified) Switching System, a Black

(unclassified) Switching System, Common End-User Terminals (CEUTs), and

Communication Management Software for the U.S. Coast Guard (USCG) Polar

Security Cutter (PSC) Program. Combined, they provide point-to-point connections for information flow between radios, modems, cryptographic, classified communication capable user terminals, recording devices and Internal Voice Network (IVN) equipment.

The CMS also provides management of Exterior Communication System (XCS) radios.

1.2. Period of Performance: Five years from date of award.

2. References

2.1. Reserved

3. CLIN 0001 – Design and Testing of CMS

3.1. Kick Off Meeting

3.1.1. The Contractor shall conduct a Kick off meeting at its facility within 2 weeks after contract award.

3.1.2. The Contractor shall accommodate up to 5 Government attendees.

3.1.3. The Contractor shall provide a Project Plan and Schedule. [DI-018]1

3.1.4. The Contractor shall provide a Quality Assurance Plan. [DI-013]

3.1.5. The Contractor shall identify schedule and technical risks.

3.2. Preliminary Design

3.2.1. The Contractor shall provide a Network Architecture Report. [DI-011]

3.2.2. The Contractor shall provide a Schematic Block Diagram. [DI-002]

3.2.3. The Contractor shall provide Electronic System Elementary Wiring Diagrams.

[DI-003]

3.2.4. The Contractor shall provide a Test and Evaluation Program Plan. [DI-012]

3.2.5. The Contractor shall provide Interface Requirements Specifications. [DI-019]

3.3. Formal Design Review (FDR) The Contractor shall conduct a Formal Design Review with Government representatives in attendance.

3.3.1. FDR shall be at the Contractor’s facility.

3.3.2. The Contractor shall accommodate up to 5 Government attendees.

3.3.3. The Contractor shall conduct FDR when the CMS design:

3.3.3.1. Is technically feasible of complying with Attachment A.

3.3.3.2. Is balanced with internally consistent and convergent design characteristics from a single integrated design for the entire system.

3.3.3.3. Accurately captures all integration and interfaces between the CMS, Government furnished systems (e.g., data networks, internal voice networks, radios) as defined in the GFI.

3.3.3.4. Demonstrates complete representation of all interfaces defined in the CMS

Specification and GFI.

1Refers to Contract Data Requirements List (CDRL).

70Z02320RAPB02300 2

3.3.4. The Contractor shall conduct the FDR within 2 weeks after Government acceptance of the following Preliminary Design data items (3.2 above).

3.3.5. During FDR, the Contractor shall provide data and narrative in sufficient detail for the Government to verify:

3.3.5.1. The design is producible per the Contractor’s build strategy.

3.3.5.2. The design incorporates proven technology reflecting a high level of maturity with demonstrated functional performance.

3.3.5.3. The Requirements Traceability and Verification Matrix. [DI-019]

3.3.5.4. The Contractor’s Configuration Status Accounting (CSA).[DI-017]

3.3.5.4.1. The CSA shall establish the configuration baseline that uniquely identifies end items, repairable components, replaceable components, software items, and firmware items.

3.3.5.4.2. CSA shall include all components valued at $3,000 or greater.

3.3.5.4.3. The CSA shall include serialized items even if they are valued under

$3,000

3.3.5.5. The design satisfies contract requirements.

3.3.5.6. System and component material selections meet contract performance requirements.

3.3.5.7. Software development processes are fully defined and accepted as appropriate for coding and test.

3.3.5.8. Interfaces between all configuration items both internal and external to the system are defined and stable.

3.3.5.9. Software user interfaces are identified, including critical formats and interactions.

3.4. Final Design and Test

3.4.1. The Contractor shall ensure that its CMS meets each technical requirement in the Technical Specification, Attachment A.

3.4.2. The Contractor shall provide a Test Plan. [DI-014]

3.4.3. The Contractor shall provide Test Procedures. [DI-015]

3.4.4. The Contractor shall provide Test Reports. [DI-020]

3.4.5. Test Administration and Testing

3.4.5.1. Test Dates and Details. The Contractor shall schedule testing to occur within 2 weeks after approval of Test Procedures. [DI-016].

3.4.5.2. The Contractor shall perform the tests necessary to demonstrate compliance with the requirements of Attachment A.

3.4.5.3. The Contractor shall execute approved test procedures in the presence the Government.

3.4.5.4. The Contractor shall start tests only with permission of the Government.

3.4.5.5. The Contractor shall perform each test using the current approved or accepted test procedure.

3.4.5.6. While conducting tests, the Contractor shall not align or adjust the equipment being tested except as required by the test procedure.

3.4.5.7. The Contractor shall perform tests at its facility.

3.4.5.8. The Contractor shall accommodate up to 5 Government attendees.

70Z02320RAPB02300 3

3.4.6. Configuration Management. The Contractor shall perform configuration management functions to ensure that no changes or deviations to the system design, components, or software occur without prior Government approval.

3.4.6.1. The Contractor shall submit an Engineering Change Proposal (ECP), for approval before changing the configuration baseline. [DI-016]

3.4.6.2. The Contractor shall maintain configuring control of everything in the configuration baseline from FDR to delivery.

3.4.6.3. The Contractor shall place software under configuration control immediately following unit test.

3.4.6.4. The Contractor shall provide a Software Version Description [DI-006].

3.4.7. The Contractor shall provide fully paid, non-expiring software licenses, for all software items necessary for the operation, use, and maintenance of contractor furnished equipment.

3.4.8. Reserved

3.4.9. Reserved

3.4.10. The Contractor shall provide Installation Control Drawings. [DI-004]

3.4.11. The Contractor shall provide Software User Manuals. [DI-005]

4. CLIN 1001 – Communications Management System for PSC #1 (OPTION)

If the Government exercises this option, it will be in year 1 of the period of performance.

4.1. The Contractor shall provide one complete CMS.

4.2. The Contractor shall provide an Information Assurance Plan. [DI-009]

4.3. The Contractor shall provide an Information Assurance Design Review Information

Package. [DI-010]

4.4. The Contractor shall provide a Bill of Materials. [DI-001]

4.5. The Contractor shall provide Technical Manuals. [DI-007]

4.6. The Contractor shall provide a Software Product Specifications [DI-008].

4.7. The Contractor shall provide systems engineering and technical assistance to support configuration, installation, and integration of the CMS at the Government XCS Test &

Integration Facility in Patuxent River, MD.

5. CLIN 10002 – Travel (OPTION)

If the Government exercises this option, it will be in year 1 of the period of performance.

5.1. The Government shall reimburse the Contractor for costs for one technical specialist to travel to the Test & Integration Facility in Patuxent River, MD to provide all engineering and technical assistance referenced at CLIN 10001: 4.7.

6. CLIN 2001 – Communications Management System for PSC #2 (OPTION)

If the Government exercises this option, it will be in year 2 or 3 of the period of performance.

6.1. The Contractor shall deliver one complete CMS.

7. CLIN 3001 – Communications Management System for PSC #3 (OPTION)

If the Government exercises this option, it will be in year 4 or 5 of the period of performance.

7.1. The Contractor shall deliver one complete CMS.

File details come from the government source that posted it. Updated .