Section_J _Attachment_17 _C2SES_III_System_Sustainment_TO_0001_PWSs.doc
DOC document 779 KB Posted
- Attached to
- C2SESIII Award
- Solicitation number
- FA4600-16-R-0007
About this file
C2SESIII RFP - Section J Attachment 17 System Sustainment TO0001 PWS
View the file
Other files
Show all 37
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
FA4600-XX-X-XXXX-XXXX
PERFORMANCE WORK STATEMENT
SHAPE \* MERGEFORMAT
C2 Software Sustainment
FA4600-XX-X-XXXX-0001
14-Oct-16 11.
Description of Service/General Information
11.1.
Description of Services
11.2.
Background
11.3.
Scope of Work
11.4.
Period of Performance
22.
Requirements
22.1.
Description of requirements
22.2.
Deliverables
22.2.1.
Documents/reports/studies/software
22.2.2.
Milestones/reviews
22.3.
Travel
22.4.
Mission Essential Service
33.
Government Furnished Property and Services
33.1.
Government Furnished Property
33.1.1.
Government-Furnished Materials/Equipment:
33.1.2.
Facilities
33.1.3.
Supplies
33.1.4.
Contractor Acquired Equipment
44.
Applicable Documents
44.1.
Government Documents
44.2.
Non-Government Documents
44.3.
Standards
44.4.
Contracting
55.
Acronyms
1. Description of Service/General Information
1.1. Description of Services
The purpose of this Command and Control System Engineering Support III (C2SES III) effort is to utilize contractor expertise to ensure the proper development, testing, delivery, installation, and sustainment of C2SES III capability. The office of primary functional responsibility for C2SES III activities, AFLCMC/HBCN, oversees all activity related to this Performance Work Statement (PWS).
1.2. Background
USSTRATCOM requires software maintenance and system engineering support to perform the specific tasks identified in this PWS to meet the mission requirements as identified in the Joint Strategic Capabilities Plan (JSCP), CJCSI 3110.04A (Nuclear Supplement to JSCP), Emergency Action Procedures (EAP)-CJCS Vols IR, VII, & VIII, the C2 Modernization ORD, the NPES ORD, and the USSTRATCOM UCP, none of which are releasable to the contractor.
1.3. Scope of Work
This task order establishes the performance for providing software and system engineering support for the following systems/applications included in C2SES III:
· Force Status and Readiness (FSR)
· Force Survivability, Analysis, and Management (FSAM)
· Global Information Grid (GIG)/ Area of Responsibility (AOR) Decision Support System (GADSS)
· Nuclear Planning and Execution System (NPES)
· NPES Strategic Data Loader (NSDL)
· Low to High (L2H)
The contractor shall provide the requirements outlined in this PWS in accordance with (IAW) the C2SESIII PWS. NPES and NSDL support will be managed as separate WBSs under a combine CLIN within the overall task effort. FSR and L2H support will be managed as separate WBSs under a combine CLIN within the overall task effort. FSAM support will be managed as a separate WBS project, under a separate CLIN, within the overall task effort. GADSS support will be managed as a separate WBS project, under a separate CLIN, within the overall task effort.
1.4. Period of Performance
The contractor shall coincide with the base contract period of performance.
2. Requirements
2.1. Description of requirements
The Contractor shall:
a) Coordinate software change requests, deficiency reports, and projects into scheduled releases in coordination with the Government.
b) Support up to two major releases per year and up to four minor releases per year for each application/system.
c) Support patches as required to address issues identified in the field or to support security findings.
d) Provide system engineering and support services for all software releases as required and for requirements identified by the Government.
e) Maintain utilities and tools required to support the current suite of software.
f) Perform corrective, adaptive, perfective, and preventive maintenance, and provide associated documentation, as required.
g) Modify/enhance software to ensure a strong security posture and address Government security findings and Information Assurance Vulnerability Alert (IAVA), Information Assurance Vulnerability Bulletins (IAVB), technical advisories and Cyber Vulnerability Assessments.
h) Provide to the Government all developed, modified, or converted source modules, processes, programs, scripts, operating instructions, databases, system files, documentation, test files and test conditions, and deficiency reports (DRs) for each software release.
i) Analyze and recommend solutions to change requests (CRs) for Government prioritization and approval.
j) Track, manage, and status all stakeholder requests, software discrepancies, and change requests in a Government provided repository (e.g., JIRA).
k) Oversee all engineering activities and ensure the use of common system engineering processes, software tools, techniques, and where practicable, services/languages/libraries/code.
l) Support the analysis and design of systems and applications and their integration into the overarching enterprise architecture.
m) Participate in periodic Government management board meetings (e.g., IPTs and Requirements Review Boards (RRBs)).
n) Assess impacts to C2 systems/applications within the scope of this PWS for communication system/device modernization plans, technical upgrade/refresh, and connectivity changes. Impact assessment includes analysis, determining courses-of-action, and recommend changes or necessary enhancements to sustain the services/capabilities from other communication systems/devices required for C2 systems/applications.
o) Maintain and update communication system drawings, interface control documents, data flows, and connectivity diagrams necessary to maintain and troubleshoot C2 systems/application interfaces to communication systems/devices.
p) Develop and implement Configuration Management (CM) processes and procedures to support the activities described in this PWS in accordance with the J864 C2 Mission Portfolio Configuration Management Plan.
q) Maintain and control the product baseline (all artifacts associated with a release – software, documentation, version descriptions, test results, etc.)
r) As required, develop and deliver technical reports to document the results and recommendations of quality assurance analyses/process improvement recommendations.
s) Ensure all system deliverables comply with applicable DOD, NIST, CNSSI, AF, and USSTRATCOM Information Assurance (IA) Policy.
t) Perform database and data administration for NPES installations in the software support and test environment
u) Manage and maintain system software support and test environments to support the provisioning, installation/configuration, operation, and maintenance of hardware and software and related infrastructure for system software support and test activities.
v) Perform database design and data administration for installations in the software support and test environments.
w) Implement a comprehensive test program and provide test engineering support to ensure proper validation and verification of user requirements for capabilities delivered.
2.2. Deliverables
2.2.1. Documents/reports/studies/software
a) The contractor shall deliver all software documentation IAW the C2SES III PWS paragraph 3.1 and 3.4.
b) The contractor shall deliver all system engineering and support services documentation IAW the C2SES III PWS paragraph 4.
2.2.2. Milestones/reviews
The contractor shall identify all milestones and reviews for all software releases in the IMS for Government approval.
2.3. Travel
Travel will be conducted on a cost reimbursable basis IAW the Joint Federal Travel Regulations. The contractor shall provide all associated costs for conducting the travel.
2.4. Mission Essential Service
None
2.5. Transition Period
The Contractor shall provide a plan outlining their approach to accomplish a smooth transition without degradation of service.
The contractor shall:
a) Provide a schedule covering the duration of the transition period. It shall identify risks and mitigation measures associated with the transition period.
b) Identify key personnel and activities, along with a plan for ensuring appropriately cleared personnel are available by the end of the transition period.
c) Outline how the Contractor will communicate with USSTRATCOM, the offeror’s teaming partners/sub-contractors, and others working with the C2 programs.
3. Government Furnished Property and Services
3.1. Government Furnished Property
3.1.1. Government-Furnished Materials/Equipment:
No unique requirements.
3.1.2. Facilities
All work will be conducted as USSTRATCOM.
3.1.3. Supplies
None.
3.1.4. Contractor Acquired Equipment
None.
4. Applicable Documents The following documents shall form a part of this specification to the extent specified herein. In the event of conflict between the documents referenced and the contents of this specification, the contents of this specification shall be considered a superseding requirement.
4.1. Government Documents
Performance Work Statement for the USSTRATCOM Command and Control Software Engineering and Support III.
4.2. Non-Government Documents
No special guidance.
4.3. Standards
No special guidance.
4.4. Contracting
No special guidance.
5. Acronyms
CR
Change Requests
CM
Configuration Management
DR
Deficiency Reports
FSAM
Force Survivability, Analysis, and Management
FSR
Force Status and Readiness
GADSS
Global Information Grid (GIG)/ Area of Responsibility (AOR) Decision Support System
IA
Information Assurance
IAVA
Information Assurance Vulnerability Alert
IAVB
Information Assurance Vulnerability Bulletins
IAW
In Accordance With
L2H Low to High
TO
Task Order
NPES
Nuclear Planning and Execution System
NSDL
NPES Strategic Data Loader
PMO
Program Management Office
PWS
Performance Work Statement
RRB
Requirements Review Boards
USSTRATCOM
United States Strategic Command
Section J, Attachment 17
Task Order 0001 PWS
PAGE
File details come from the government source that posted it. Updated .