APPENDIX_VI_-_CSSC_DELIVERABLES.pdf
PDF 107 KB Posted
- Solicitation number
- HC1013-14-R-0004
- Issued by
-
Defense Information Systems Agency
About this file
PWS Appendix VI - CSSC Deliverables
View the file
Other files
Show all 33
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
CSSC Deliverables
Delive rable
ID
PWS Task# Deliverable Title Format Due Date Frequency and Remarks
D1 6.3.6.2 Installation Design Plan (IDP) and As-Built Drawing Packages
As-Built Drawing Packages
AutoCAD 2011 or above and latest Shore Installation Process Handbook (SIPH) Commander Space and Naval Warfare Systems Command
(COMSPAWAR) M-
4720.1
Final As-Built Drawings shall be delivered 45 calendar days from installation completion.
Required after installation of a specific section of the terrestrial architecture to be driven by the terrestrial architecture stand up plan schedule.
D2 6.3.6.2 Installation Design Plan (IDP) and As-Built Drawing Packages
IDP AutoCAD 2011 or above and latest SIPH
COMSPAWAR M-
4720.1
IDP shall be delivered within 21 calendar days of task order award.
Required prior to installation at all Navy Designated Point of Presence (NDPs).
D3 6.2.8.2 Beam Shaping Beam Shaping Plan
Contractor Format Response Times:
Routine (new beams) - 72 hours
Emergent (new beams) - 48 hours
Emergent (pre-planned beams) - 2 hours
Response is the time allotted to execute the shaping action and begins upon initial notification.
D4 6.2.8.3 Beam Steering Beam Steering Plan
Contractor Format Response Times:
Routine (new beams) - 24 hours
Emergent (new beams) - 8 hours
Emergent (pre-planned beams) - 2 hours
Response is the time allotted to execute the action steering action and begins upon initial notification.
ID
PWS Task# Deliverable Title Format Due Date Frequency and Remarks
D5 6.3.6.1 Configuration Management
Configuration Management Documentation/ Integrated Logistics Support (ILS) Plan
SIPH COMSPAWAR M-
4720.1
For all contractor furnished equipment located at the NDPs, the contractor shall provide, within 14 calendar days after task order award, configuration management documentation which includes ILS Plan. Upon Government acceptance of the network architecture, the contractor shall provide configuration management documentation in accordance with the SIPH COMSPAWAR M- 4720.1.
Upon execution of a new task order
D6 6.4.1 Subtask 1 – Transition Support Plan
Transition Support Plan
Contractor Format The contractor shall develop and present a Transition Support Plan 14 calendar days after contract award for transition discussions at the Kick-Off Meeting.
After basic contract award.
The Transition Plan shall include stand-up of the terrestrial network and commercial teleport (CT) facilities to support the CSSC solution, performance and acceptance testing, performance and acceptance reporting, cutover of end user terminals onto the CSSC architecture, and dual illumination of the space segment when applicable
D7 6.4.3 Subtask 3 – Final Acceptance Test
System Operational Verification Test (SOVT) document
SOVT Preparation and Execution Guide SPAWAR Instruction 3084.1
The contractor shall develop and deliver a SOVT document shall be delivered within 21 calendar days after task order award that will be used for the post-installation and transition testing of the end-to-end service.
The completed SOVT shall be delivered within 180 calendar days after task order award.
After task order award.
For final acceptance testing at each
NDP.
ID
PWS Task# Deliverable Title Format Due Date Frequency and Remarks
D8 6.5.3 Subtask 3 – Operations Guide
Operations Guide for
CSSC
Operations
Contractor Format Draft Operations Guide is due within 30 calendar days after task order award.
Final Operations Guide is due no later than 90 calendar days after award.
Required after task order award.
Required for communications and procedures/protocols for handling issues/concerns between customers and the vendor.
D9 6.6.2 Subtask 2 – Web Tool
Web Tool Contractor Format The Web Tool shall be accessible on-line and ready for use within 120 calendar days after task order award
Includes all deliverables listed in Section 6.6.2 of the PWS.
D10 6.6.2.3.4 Utilization Information Performance
Utilization Information Performance Report
Contractor Format Weekly due each Tuesday for the preceding week, 6.6.2.3.4.1.1
Monthly due 1st Friday for preceding month. 6.6.2.3.4.1.2
Annual due on each anniversary of task order award 6.6.2.3.4.1.3
The Web Tool shall provide utilization performance information that includes utilization by capacity for the space segment, CT services, and terrestrial backhauls by contract, task order, mission number, and operating areas.
D11 6.6.2.5 Web Tool Historical Database
Web Tool Historical Database
All statistical information provided to the Web Tool in an Extensible Markup Language (XML) format
This database shall be exported in its entirety and delivered to the Government at the conclusion of the contract.
The contractor shall archive and maintain a database of all operational historical information and statistical information for the life of the contract.
This information shall also be available for display on the Web Tool.
ID
PWS Task# Deliverable Title Format Due Date Frequency and Remarks
D12 6.7.4.2 Program Management Reviews (PMRs)
PMR Brief Contractor Developed Format
Every quarter throughout the life of the contract
Two PMRs shall be held via teleconference and two PMRs shall be held in person per contract year. The contractor shall prepare and deliver a PMR Brief at each PMR that covers, at a minimum, the status of: the system architecture, current and ongoing efforts, task orders, performance trends, program and technical risks, as well as status of Information Assurance (IA) requirements detailed in Instruction (DoDI) 8510.01.
D13 6.6.2.7 Web Tool User Manual
Web Tool User Manual
Microsoft (MS) Word 2007 or later
Within 90 calendar days after task order award
Required after task order award
Maintain the User Manual throughout the life of the contract.
D14 6.6.2.8 Web Tool Training
Web Tool Training Curriculum
Contractor Developed Format
The contractor shall develop a curriculum for Web Tool user training. The curriculum shall be delivered within 90 calendar days after task order award.
Required after task order award.
The contractor shall provide up to four training sessions per NDP to accommodate shift work. Training sessions will be scheduled after the Web Tool and training curriculum have been delivered to the Government. The training schedule will be approved by the Government at least 30 calendar days in advance of each training session.
ID
PWS Task# Deliverable Title Format Due Date Frequency and Remarks
D15 6.7.1 Subtask 1 – Project Management Plan
(PMP)
Project Management Plan (PMP)
Contractor Format/Schedule in MS Project 2010
The contractor shall deliver the PMP within 14 calendar days after task order award at the Kick-Off Meeting.
The contractor shall maintain a detailed PMP. It shall detail the standup of the terrestrial segment capability and bandwidth services.
The contractor shall establish and define clear lines of authority and responsibility between all organizational elements. The PMP shall include a Risk Management Plan and a Quality Control Plan (QCP) and be delivered within 14 calendar days of task order award at the Kick-Off Meeting.
D16 6.7.3.3 Daily Service Report
Daily Service Report
E-mail Notification and on Web Tool
On the Web Tool no later than 0600 Eastern Time the following day.
The contractor shall provide a Daily Service Report detailing the current status of each end-to-end circuit
Information in the Daily Service Report shall include requirements of 6.7.3.3 and 6.6.2.3.3
D17 6.7.3.1 Outage Report Outage Report E-mail Notification and on Web Tool
The contractor shall generate real time reports whenever outages are experienced. Prior to Web Tool implementation, the contractor shall provide the reports daily via email to standard distribution.
Event Driven
D18 6.7.3.2 Change of Mission Status Report
Change of Mission Status Report
Contractor Format posted on Web Tool
Immediately upon status change Event Driven
ID
PWS Task# Deliverable Title Format Due Date Frequency and Remarks
D19 6.7.3.4 Monthly Service Report
Monthly Service Report
Contractor Format E-mail Notification and on Web Tool
Due every month no later than 5 business days after the end of the previous month
The contractor shall provide a Monthly Service Report that includes the time and duration of any service outages. If service outages are identified in the report, the contractor shall provide a failure analysis detailing the root cause of the service failure, number of circuits affected, as well as any future steps required to avoid that service failure. Prior to implementation of the Web Tool, the contractor shall submit the reports via email to the standard distribution. After Web Tool implementation, the contractor shall provide a monthly notification via email to the standard distribution stating that the report can be found on the Web Tool.
Includes Outage Summary Report 6.1.2
D20 6.7.3.5 Monthly Contract Progress Status Management Report
Monthly Contract Progress Status Management Report
Contractor Format Due every month no later than 5 business days after the end of the previous month
The reports address the progress of the contract and individual task order efforts, status of any problem resolution, identification of new problems, summary of safety-related actions, significant events, updated contract schedule, and other data required to be included by other paragraphs within the PWS. The monthly report also addresses delivery schedules, delivery order status and number, lease start and stop dates, and funding
ID
PWS Task# Deliverable Title Format Due Date Frequency and Remarks
D21 6.7.4.4 Installation Readiness Review (IRR)
Agenda and Presentation Materials for
IRR
Contractor Format 30 days prior to start of terrestrial installation
IRR Package shall consist of design packages, all component, subsystem, system test results, work/job plans, and staff assigned to the installation and installation schedule.
D22 6.8.1 Subtask 1 – Pre- Installation Testing
Pre-Installation Testing Report
Contractor Developed Format
21 days after task order award The contractor shall provide a pre-installation test report that validates system design, configuration and performance.
D23 6.8.2 Subtask 2 – Post- Installation SOVT
Post Installation SOVT Report
Contractor Developed Format
120 days after task order award The contractor shall conduct post-installation testing on leased lines between CT and the NDP in accordance with the SOVT.
D24
6.10 Task 10 –
Electromagnetic Interference (EMI)/Radio Frequency Interference (RFI) Identification, Characterization, and Geo-Location
EMI/RFI
identification, characterization , and geo-location
United States Strategic Command
(USSTRATCOM)
Format
The contractor (and/or subcontractors) shall provide initial acknowledgement of EMI/RFI to the RSSC-WEST by telephone within 10 minutes. Best effort geo-location of the interfering signal source, spectrum analyzer screenshots, and characterization in accordance with USSTRATCOM guidance (as described in the USSTRATCOM EMI/RFI Reporting Checklist) shall be provided within 30 minutes of contractor EMI/RFI detection or Government request if events are detected by the Government. Updates of such information shall be provided to the Government upon change, upon request, or every two hours from initial report, until incident resolution.
Event-driven.
ID
PWS Task# Deliverable Title Format Due Date Frequency and Remarks
D25 6.10 Task 10 – Electromagnetic Interference (EMI)/Radio Frequency Interference (RFI) Identification, Characterization, and Geo-Location
Summary of Action Report
USSTRATCOM Format 24 hours after resolution of EMI/RFI Incident
Event-driven.
D26 6.11.1 Subtask 1 – Fault Reporting & 6.7.3.3.13 Open Trouble Tickets
Trouble Ticket Contractor Format Trouble tickets shall be updated daily regardless of change in status and hourly for serious issues until they are corrected.
Event driven- at detection, identification, and isolation of faults; 2) initiation, tracking, and completion of corrective actions;
and 3) fault reporting
The contractor shall electronically report fault information with the associated signal parameters for out-of-tolerance alarms and carrier-related alarms via trouble tickets to the Navy Network Warfare Command (NNWC), the appropriate Joint Fleet Telecommunications Operations Center (JFTOC) and the CSSC Technical Advisor (TA) as well as provide a summary of fault trends and detailed statistics in its monthly status report.
ID
PWS Task# Deliverable Title Format Due Date Frequency and Remarks
D27 6.11.2 Subtask 2 – Service Outage and Restoration
Service Interruption and Restoration Reporting
On Web Tool and Trouble Ticket
Initial reports shall be provided by phone to NNWC, the appropriate JFTOC and the CSSC TA within 10 minutes of incident.
For service outages, the contractor shall provide verbal and written status reports to NNWC, the appropriate JFTOC and the CSSC TA. These reports are in addition to all electronic reports and monthly reports. These reports shall identify the circuits involved, the cause of outage if known and the actions already taken and planned to correct the outage.
Initial trouble tickets shall be submitted to NNWC, the appropriate JFTOC and the CSSC TA within 30 minutes and updated hourly thereafter until service is restored. For outages lasting 120 minutes or more, the contractor’s Program Manager shall participate in any requested conference calls and for outages lasting 240 minutes or more the contractor’s senior management shall participate in any requested conference calls.
ID
PWS Task# Deliverable Title Format Due Date Frequency and Remarks
D28 6.13.2 Subtask 2 – Frequency Matrix
Frequency Matrix
Navy Template The contractor shall provide a Frequency Matrix to the Navy concurrently with each transmission plan. The Frequency Matrix is a summation of the transmission plan that focuses primarily on operator level settings. This information is used to provide users at the Government furnished equipment terminals frequency, modulation, and encoding parameters specific to their operations at the terminal operators’ location. Appendix V provides a template for the Frequency Matrix to be provided.
Same time as Transmission Plan is submitted
D29 6.15 Task 15 – Semi- Annual Sun Transit Reporting.
Semi-Annual Sun Transit Reporting.
Contractor Format The contractor shall provide semi-annual sun transit reports at least 14 calendar days prior to each seasonal eclipse event to the Contracting Officer’s Representative, NNWC, and the
CSSC TA.
Semi-annual; based on Spring and Fall seasonal eclipse.
D30 6.13.1 Subtask 1 – Transmission Plan
Transmission Plan
Excel spreadsheet and XML format
Five days or less after task order award; at least 24 hours before start date
Updated Transmission Plans are due within 3 calendar days from receipt of written request from the Government.
Required after award and for every change in configuration or PoP thereafter.
ID
PWS Task# Deliverable Title Format Due Date Frequency and Remarks
D31 6.12 Task 12 – Support for CSSC Security and Information Assurance (IA) Requirements
IA Compliance Matrix Updates
IA Compliance Matrix in Microsoft Excel workbook format as provided by the Government in the RFP.
At issuance of a new task order.
Any Engineering Change Proposal (ECP) submitted which changes any of these elements during the life of this contract shall include an updated IA Compliance Matrix and is subject to Designated Accrediting Authority (DAA) approval and acceptance.
At issuance of new task orders and ECPs to the task orders.
The contractor shall ensure that provisioned service meets specified IA requirements including DoDI 8581.01, DoD
8500.2 and Minimum Security Controls listed in the IA Compliance Matrix. The contractor shall continually monitor and verify IA compliance in accordance with the IA Compliance Matrix so long as the task order is in effect.
ID
PWS Task# Deliverable Title Format Due Date Frequency and Remarks
D32 6.12.5 Subtask 5 –
DIACAP
DIACAP
package to support the Certification and Accreditation (C&A)
The DIACAP package shall be in accordance with DoD and Department of Navy templates found at https://emass-navy.csd.disa.mil.
The contractor shall submit a DIACAP package within 30 calendar days after task order award.
The Navy’s Office of Operational Designated Accrediting Authority is responsible for the security of the terrestrial segment of the CSSC from the CT back to the NDP. All terrestrial segment equipment that is part of the CBSP architecture must meet local DAA accreditation. The contractor shall support the Government in making MAC classification and Sensitivity Level determination consistent with DoDI 8500.01. The contractor shall prepare and deliver the DIACAP package to support the C&A of the CSSC capability consistent with DIACAP DoDI 8510.01. The contractor shall continually monitor, verify and maintain IA compliance throughout the life of the contract. The contractor shall support the Government in transition from DIACAP to the Risk Management Framework as directed.
All deliverables shall be delivered electronically unless otherwise specified.
All deliverables in this document as well as those listed in the CSSC PWS, are requirements of the Government and shall be provided by the Contractor.
https://emass-navy.csd.disa.mil/ https://emass-navy.csd.disa.mil/
File details come from the government source that posted it. Updated .