FA4600-16-R-0007_Amend_2_C.docx

FA4600-16-R-0007

FA4600-16-R-0007

Section A - Solicitation/Contract Form

ADMINISTRATIVE DELEGATION

DELEGATED SELECTED ADMINISTRATIVE DUTIES TO DCMA IAW FAR 42.202 TO DCMA, TBD.

DCMA OFFICE TBD

Section B - Supplies or Services and Prices

C2SES III Technical Support

CPIF

The contractor shall provide services to complete the requirements IAW the C2SES III Performance Work Statement of the basic contract. Future unknown requirements To Be Negotiated (TBN) at the individual task order level.

ODCs and Travel shall be priced separately under CLIN(s) 0005 and 0006.

This CLIN is Government pre-populated not to exceed (NTE) the amount of $60.7 million. This CLIN will include the CPIF efforts in Task Order 0001, which shall be awarded with the award of the IDIQ.

Period of Performance: To be cited in each individual task order.

FOB: Destination

PROJECT: C2SES III

SIGNAL CODE: A

TARGET COST

TARGET FEE

TOTAL TGT COST + FEE

MINIMUM FEE

MAXIMUM FEE

SHARE RATIO ABOVE TARGET

SHARE RATIO BELOW TARGET

C2SES III Technical Support

CPFF

The contractor shall provide services to complete the requirements IAW the C2SES III Performance Work Statement of the basic contract. Future Unknown requirements To Be Negotiated (TBN) at the individual task order level.

ODCs and Travel shall be priced separately under CLIN(s) 0005 and 0006.

This CLIN is Government pre-populated not to exceed (NTE) the amount of $18 million.

The Fixed Fee is 8.0%

Period of Performance: To be cited in each individual task order.

FOB: Destination

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

Lot

C2SES III Technical Support

FFP

The contractor shall provide services to complete the requirements IAW the C2SES III Performance Work Statement of the basic contract. Future unknown requirements To Be Negotiated (TBN) at the individual task order level.

Pricing shall be priced IAW the pricing rate schedule attachment located in Section J, or pricing may be discounted at the task order level.

ODCs and Travel shall be priced separately under CLIN(s) 0005 and 0006.

This CLIN is Government pre-populated not to exceed (NTE) the amount of $11 million.

Period of Performance: To be cited in each individual task order.

FOB: Destination

MAX

NET AMT

Lot

C2SES III Technical Support

FFP-LOE

The contractor shall provide services to complete the requirements IAW the C2SES III Performance Work Statement of the basic contract. Future unknown requirements To Be Negotiated (TBN) at the individual task order level.

Pricing shall be priced IAW the pricing rate schedule attachment located in Section J, or pricing may be discounted at the task order level.

ODCs and Travel shall be priced separately under CLIN(s) 0005 and 0006.

This CLIN is Government pre-populated not to exceed (NTE) the amount of $3.3 million.

Period of Performance: To be cited in each individual task order.

FOB: Destination

MAX NET AMT

CEILING PRICE

C2SES III Travel

COST

All travel cost shall be in accordance with the Joint Travel Regulation and approved by the COR prior to travel. This is a cost reimbursable CLIN. Fee/profit will not be allowed on the costs of any Travel. However, this does not preclude the application of associated burden(s) (e.g. G&A, Material Handling, etc.) associated with those costs.

The Government has pre-populated the not to exceed (NTE) amount for this CLIN at $200,000. This amount includes the application of associated burden(s) (e.g. G&A, Material Handling Fee, etc.) associated with those costs.

This CLIN will support TO 0001 and all future TOs as needed.

FOB: Destination

MAX COST

C2SES III ODC

COST

All ODCs shall be approved by the COR prior to purchase. All items over the micro purchase threshold shall be approved by the Contracting Officer. In addition, contractor shall supply three quotes as proof of cost reasonableness to the Contracting Officer when required. Fee/profit will not be allowed on the costs of any ODCs. However, this does not preclude the application of associated burden(s) (e.g. G&A, Material Handling, etc.) associated with those costs. This CLIN will support TO 0001 and all future TOs as needed.

The Government has pre-populated the not to exceed (NTE) amount for this CLIN at $100,000. This amount includes the application of associated burden(s) (e.g. G&A, Material Handling Fee, etc.) associated with those costs.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination

MAX COST

Lot

Data

FFP

CDRL's in support of requirements identified in the C2SES III Contract PWS and/or future task order PWSs.

NOT SEPARATELY PRICED (NSP).

FOB: Destination

MAX

CPIF

IAW FAR Clause 52.217-8, Option to Extend Services (Nov 1999), the Government may require continued performance of any services within the limits and at the rates specified in the contract. These rates may be adjusted only as a result of revisions of prevailing labor rates provided by the Secretary of Labor. The option provision may be exercised more than once, but the total extension of performance hereunder shall not exceed 6 months.

If the option to extend services clause is exercised, the price for current option period will be pro-rated IAW FAR Clause 52.217-8 at the rates specified for that option period.

ODCs and Travel shall be priced separately under CLIN(s) 1005 and 1006.

This CLIN is Government pre-populated not to exceed (NTE) the amount of $3.5 million.

Period of Performance: To be cited in each individual task order.

FOB: Destination

TARGET COST

TARGET FEE

TOTAL TGT COST + FEE

MINIMUM FEE

MAXIMUM FEE

SHARE RATIO ABOVE TARGET

SHARE RATIO BELOW TARGET

CPFF

The contractor shall provide services to complete the requirements IAW the C2SES III Performance Work Statement of the basic contract. Future Unknown requirements To Be Negotiated (TBN) at the individual task order level.

ODCs and Travel shall be priced separately under CLIN(s) 0005 and 0006.

This CLIN is Government pre-populated not to exceed (NTE) the amount of $500,000.

The Fixed Fee is 8.0%

Period of Performance: To be cited in each individual task order.

FOB: Destination

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

Lot

FFP

IAW FAR Clause 52.217-8, Option to Extend Services (Nov 1999), the Government may require continued performance of any services within the limits and at the rates specified in the contract. These rates may be adjusted only as a result of revisions of prevailing labor rates provided by the Secretary of Labor. The option provision may be exercised more than once, but the total extension of performance hereunder shall not exceed 6 months.

If the option to extend services clause is exercised, the price for current option period will be pro-rated IAW FAR Clause 52.217-8 at the rates specified for that option period.

ODCs and Travel shall be priced separately under CLIN(s) 1005 and 1006.

This CLIN is Government pre-populated not to exceed (NTE) the amount of $500,000.

Period of Performance: To be cited in each individual task order.

FOB: Destination

MAX

Lot

FFP-LOE

IAW FAR Clause 52.217-8, Option to Extend Services (Nov 1999), the Government may require continued performance of any services within the limits and at the rates specified in the contract. These rates may be adjusted only as a result of revisions of prevailing labor rates provided by the Secretary of Labor. The option provision may be exercised more than once, but the total extension of performance hereunder shall not exceed 6 months.

If the option to extend services clause is exercised, the price for current option period will be pro-rated IAW FAR Clause 52.217-8 at the rates specified for that option period.

ODCs and Travel shall be priced separately under CLIN(s) 1005 and 1006.

This CLIN is Government pre-populated not to exceed (NTE) the amount of $170,000.

Period of Performance: To be cited in each individual task order.

FOB: Destination

MAX NET AMT

CEILING PRICE

COST

Six month extension IAW 52.217.8. All travel cost shall be in accordance with the Joint Travel Regulation and approved by the COR prior to travel. This is a cost reimbursable CLIN. Fee/profit will not be allowed on the costs of any Travel. However, this does not preclude the application of associated burden(s) (e.g. G&A, Material Handling, etc.) associated with those costs.

The Government has pre-populated the amount for this CLIN at $20,000. This amount includes the application of associated burden(s) (e.g. G&A, Material Handling Fee, etc.) associated with those costs.

FOB: Destination

MAX COST

COST

Six month extension IAW 52.217.8. All ODCs shall be approved by the COR prior to purchase. All items over the micro purchase threshold shall be approved by the Contracting Officer. In addition, contractor shall supply three quotes as proof of cost reasonableness to the Contracting Officer when required. Fee/profit will not be allowed on the costs of any ODCs. However, this does not preclude the application of associated burden(s) (e.g. G&A, Material Handling, etc.) associated with those costs.

The Government has pre-populated the amount for this CLIN at $10,000. This amount includes the application of associated burden(s) (e.g. G&A, Material Handling Fee, etc.) associated with those costs.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination

MAX COST

Lot

FFP

Six month extension IAW 52.217.8. CDRL's in support of requirements identified in the C2SES III Contract PWS and/or future task order PWSs.

NOT SEPARATELY PRICED (NSP).

FOB: Destination

MAX

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT

FOR

USSTRATCOM COMMAND AND CONTROL

SOFTWARE ENGINEERING AND SUPPORT III

(C2SES III)

1 September 2017

USSTRATCOM Command and Control Software Engineering and Support III (C2SES III) Performance Work Statement (PWS)

Name:

Organization:

Executive Summary The USSTRATCOM Command and Control Software Engineering and Support (C2SES) program provides Commander (CDR) USSTRATCOM, supported Combatant Commands, Component Commands, and other authorized users with modernized mission critical communications and computer systems utilizing common integrated information and decision toolsets, applications and capabilities in a fully synchronized, net-centric information environment, necessary to maintain deterrence and, if required, dominate in conflict. As the successor to C2SES II, C2SES III will continue to provide total lifecycle program management of these systems, applications, and toolsets.

USSTRATCOM C2SES III PWS.

Table of Contents

1. PURPOSE

The missions of United States Strategic Command (USSTRATCOM) are: to detect, deter, and prevent attacks on United States (US) vital interests, to ensure US freedom of action in space and cyberspace, to deliver integrated kinetic and non-kinetic effects to include nuclear and information operations in support of US Joint Force Commander operations, to synchronize global missile defense plans and operations, to synchronize regional combating weapons of mass destruction plans, to provide integrated surveillance and reconnaissance allocation recommendations to the Secretary of Defense (SECDEF), and to advocate for capabilities as assigned.

The USSTRATCOM C2SES program provides Commander (CDR) USSTRATCOM, supported Combatant Commands, Component Commands, and other authorized users with modernized mission critical communications and computer systems utilizing common integrated information and decision toolsets, applications and capabilities in a fully synchronized, net-centric information environment, necessary to maintain deterrence and, if required, dominate in conflict. As the successor to C2SES II, C2SES III will continue to provide total lifecycle program management of these systems, applications, and toolsets.

1. SCOPE

The C2SES III contractor shall assemble a cohesive team to effectively implement best practice processes to manage the execution and delivery of USSTRATCOM command and control (C2) software requirements. The contractor shall provide software engineering, system engineering, testing, integration, installation, security engineering, administrative and additional support tasks required to provide reliable, effective, and user-friendly net-centric capabilities contributing to the overall operations and maintenance of USSTRATCOM C2 capabilities. For NPES, development system management and system administrative support shall be provided by the C2SES III contractor. FSAM requires C2SES III support for Integrated Tactical Warning and Attack Assessment (ITW/AA) community testing with FSAM and the Processing and Display Subsystem – Migration (PDS-M), and the Subscriber Terminal Network Terminal (STNT) meeting support, scenario checkout, requirement verification, problem tracking, and initial software and communications problem analysis for FSAM and PDS-M are also required.

The Government seeks disciplined system engineering and software life cycle processes to provide software sustainment, enhancement, optimization, and testing of C2 systems, applications and tools supporting mission requirements and improve operator performance and capability.

The Government expects a contractor and Government partnership to provide the Government clear and constant visibility into all aspects of the program. The contractor shall be responsive to the continuing evolution of USSTRATCOM mission sets, able and willing to adjust as requirements, tasks, and priorities change. Contending contractors shall use this PWS as the basis for preparing proposals, to include a Work Breakdown Structure (WBS), for Government consideration.

The systems/applications included in C2SES III are:

· 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) and NPES Strategic Data Loader (NSDL)

· Low to High (L2H) Systems/applications details are provided in the documents available in the bidder’s library, and a summary is provided in the following sections.

1. Force Status Readiness (FSR) USSTRATCOM Force Status (FS) reporting capabilities are provided by the Force Status Readiness System. The system design is described in the Force Status Readiness (FSR) System/Subsystem Design Description (SSDD) provided in the bidder’s library. In addition, the Force Status Readiness (FSR) Software Design Description (SDD) identifies the software developed and maintained for FSR. The FSR software is deployed in two security domains. The FSR software interfaces with external systems and services including but not limited to databases, mail service, directory service, external web services, cross-domain solution (CDS), and network load balancer. The application environment (e.g., servers, storage, network, and workstations), services, and communication devices used in the software support, test, and production environments are located at Government facilities and are provided and supported by the Government thru other contracted resources.

The database services required by FSR are provided by the C2EDB. The database and data administration support required for the FSR software are provided by Government organizations and other contractors. The C2SES III contractor will recommend updates and coordinate changes to the database requirements with the Government for the FSR application. The scheduling of changes to FSR software must align to and support the applicable C2EDB version release and take into consideration any ITW/AA vertical changes required.

FSR software engineering and support includes addressing changes in the C2EDB schemas, external systems/applications interfacing FSR, functional enhancements, and system maintainability. Corrective changes include eliminating software deficiencies and errors, as well as adapting and updating software tools/technologies to better support user requirements. System and software requirement changes are driven by the user’s operational requirements and plans, the C2EDB and CDS designs and implementations, system utilities, tool set changes, and version upgrades to the commercial software required by FSR. The Government expects the contractor to continually monitor software and system performance, and the supportability and compatibility of all technologies included in the FSR application and environments. The contractor is expected to, based on direction and approval by the Government, address necessary updates and changes to the FSR software.

1. Force Survivability, Analysis, and Management (FSAM) USSTRATCOM Force Survival (FS) and Force Management (FM) capabilities are provided by the FSAM. The system design is described in the Force Survivability, Analysis, and Management (FSAM) System/Subsystem Design Description (SSDD) available in the bidder’s library. In addition, the Force Survivability, Analysis, and Management (FSAM) Software Design Description (SDD) identifies the software developed and maintained for FSAM.

FSAM software interfaces with external systems and services including but not limited to databases, directory service, cross-domain solution, and network load balancer. The application infrastructure (e.g., servers, storage, network, workstations) and communication devices used in the software support, test, and production environments are located at Government facilities and are provided and supported by the Government thru other contracted activities.

The database services required by FSAM are provided by the C2EDB. The database and data administration support required for the FSAM software are provided by Government organizations and contracted resources. The C2SES III contractor will recommend updates and coordinate changes to the database requirements with the Government for the FSAM application. The scheduling of changes to FSAM software must align to and support the applicable C2EDB version release.

FSAM software engineering and support includes addressing changes driven by C2EDB schema modifications and integration, external interfaced systems/applications, functional enhancements, and system maintainability. Corrective changes include eliminating software deficiencies and errors, as well as adapting and updating software tools/technologies to better support user requirements. System and software requirement changes are driven by the user’s operational requirements and plans, the C2EDB and CDS designs and implementations, algorithm and message changes applicable to Integrated Tactical Warning and Attack Assessment (ITW/AA) programs, system utilities, tool set changes, and version upgrades to commercial software required by FSAM. The Government expects the contractor to continually monitor software and system performance, and the supportability and compatibility of all technologies included in the FSAM application and environments. The contractor is expected to, based on direction and approval by the Government, address necessary updates and changes to the FSAM software. The scheduling of changes to FSAM software must align to and support the applicable ITW/AA version release.

1. Global Information Grid (GIG)/ Area of Responsibility (AOR) Decision Support System (GADSS) The GADSS software with the companion GADSS database provides capabilities to identify, analyze, track, and report GIG AOR events by the USSTRATCOM Network Operations (NetOps) C2 Watch Officer. The NetOps C2 Watch Officer can then, via GADSS’ collaborative and reporting capabilities pass operational mission impacts to the NetOps operational and maintenances teams. The system design is available in the Global Information Grid (GIG)/ Area of Responsibility (AOR) Decision Support System (GADSS) System/Subsystem Design Description (SSDD) provided in the bidder’s library.

The GADSS database design for GADSS will be provided by the C2SES III Contractor. The GADSS database administration support is provided by Government organizations and other contracted resources. The application infrastructure (e.g., servers, storage, network, workstations) used in the software support, test, and production environments are located at Government facilities and are provided and supported by the Government thru other contracted activities.

1. Nuclear Planning and Execution System (NPES) Capabilities The Nuclear Planning and Execution System (NPES) is a C2 information system providing data analysis and decision making information during peacetime and crises involving strategic nuclear operations. NPES provides information to the National Command Authorities (NCA) in the critical phases of nuclear conflict. NPES is installed at multiple locations both ground based and airborne. Each NPES installation receives updates and communicates with other NPES installed locations through several communication channels.

The application infrastructure (e.g., servers, storage, network, workstations) used in the software support and test are located at Government facilities and are provided by the Government but will be administered by the C2SES III Contractor. This includes the system administration and database administration services. These services are identified in C2SES III Support Services section of this PWS. The C2SES III Contractor will need to identify and perform system and database administration changes and updates as required by the NPES applications, infrastructure, and as affected by changes from external systems and data sources. The system and database administration will also provide support/assistance to the Government and other contractors in deployment and issue resolution at the NPES production and user testing locations.

3. NPES

The NPES software provides Force Management, Force Direction, Planning, Situational Awareness, and Execution capabilities. The system and software design documentation is provided in the bidder’s library location.

NPES software engineering and support includes addressing adaptive software changes driven by integrated Government off-the shelf (GOTS) and Commercial-off-the-shelf (COTS) software, external data sources including schema modifications and integration, external interface maintenance, functional enhancements, and system maintainability. Corrective changes include eliminating software deficiencies and errors, as well as adapting and updating software tools/technologies to better support user requirements. System and software requirement changes are driven by the user’s operational requirements and plans, the external data sources, changes to CDS designs and implementations, algorithm and message changes applicable to Integrated Tactical Warning and Attack Assessment (ITW/AA) programs, system utilities, tool set changes, and upgrades to both Government provided software and commercial software required by NPES. The Government expects the contractor to continually monitor software and system performance, and the supportability and compatibility of the entire set of technologies included in the NPES application and environments. The contractor is expected to, based on direction and approval by the Government, address necessary updates and changes to the NPES software. The scheduling of changes to NPES software must align to and support the applicable external data sources.

3. NPES Strategic Data Loader (NSDL) The NPES Strategic Data Load (NSDL) application is used to extract data from the Integrated Strategic Planning and Analysis Network (ISPAN) Enterprise Database (EDB) for input to NPES. The NSDL software pulls data from an ISPAN EDB and stores the extracted data in files. These files are then distributed for use to NPES locations through two modes. The first mode pulls NPES required data from the current plan, validates, and prepares the data for distribution (via CD, DVD, or electronic transfer). The second mode retrieves selected portion of data and prepares messages for transmission to NPES locations. The NSDL software engineering and support includes addressing application changes driven by the ISPAN EDB and changes to NPES. The EDB changes and cutovers are managed by the USSTRATCOM ISPAN program and are scheduled semiannually with potential interim cutovers as planning circumstances dictate. NSDL releases must align with both the EDB release schedules and NPES release schedules. The details for the NSDL application are provided in the bidder’s library. NSDL software engineering and support includes addressing adaptive software changes driven by external data sources including schema modifications, integration, and system maintainability. Corrective changes include eliminating software deficiencies and errors, as well as adapting and updating software tools/technologies to better support user requirements.

1. Low-to-High (L2H) Command and Control Enterprise Database (C2EDB) Data Synchronization (L2HCDS) USSTRATCOM Force Status (FS) database synchronization capabilities are provided by the L2HCDS system. The system design is described in the L2HCDS System/Subsystem Design Description (SSDD) provided in the bidder’s library. In addition, the L2HCDS Software Design Description (SDD) identifies the software developed and maintained for L2HCDS.

The L2HCDS software is deployed in two security domains. C2EDB data is replicated to the TS C2EDB via low-to-high cross security domain process using the Secure Message and Routing Terminal Next Generation (SMART.neXt) system. The SMART.neXt provides a two-way file exchange capability that the L2HCDS uses to transfer C2EDB data and process status message between the Secret and TS-C security domains.

The L2HCDS software interfaces with external systems and services including but not limited to databases, mail service, directory service, cross-domain solution (CDS), and network load balancer. The application environment (e.g., servers, storage, network, and workstations), services, and communication devices used in the software support, test, and production environments are located at Government facilities and are provided and supported by the Government thru other contracted resources.

The database services required by L2HCDS are provided by the C2EDB. The database and data administration support required for the L2HCDS software are provided by Government organizations and other contractors. The C2SES III contractor will recommend updates and coordinate changes to the database requirements with the Government for the L2HCDS application. The scheduling of changes to L2HCDS software must align to and support the applicable C2EDB version release and take into consideration any ITW/AA vertical changes required.

L2HCDS software engineering and support includes addressing changes in the C2EDB schemas, external systems/applications interfacing L2HCDS, functional enhancements, and system maintainability. Corrective changes include eliminating software deficiencies and errors, as well as adapting and updating software tools/technologies to better support user requirements. System and software requirement changes are driven by the user’s operational requirements and plans, the C2EDB and CDS designs and implementations, system utilities, tool set changes, and version upgrades to the commercial software required by L2HCDS. The Government expects the contractor to continually monitor software and system performance, and the supportability and compatibility of all technologies included in the L2HCDS application and environments. The contractor is expected to, based on direction and approval by the Government, address necessary updates and changes to the L2HCDS software.

1. Other Considerations The USSTRATCOM Chief Information Office (CIO) has directed the migration of mission systems to a Common Computing Environment (CCE) (see CCE Policy letter in bidder’s library). This direction affects the C2 systems, and requires a migration from a Solaris operating system on a SPARC-based architecture to a Linux operating system on x86-64 commodity hardware operating within VMWare virtual machines. The C2 portfolio has also made the decision to standardize the mid-tier technology to utilize the JBoss Application Server. The C2 systems described herein are all in the process of migrating to the CCE. All of the systems will be fully transitioned to the new environment prior to the start of this contract.

Early in the C2SES III contract, personnel and operations will transition to the new USSTRATCOM Headquarters (HQ) C2 Complex, currently under construction. The C2SES III contractor will support the transition of hardware and software to the new environment (installation and checkout, system testing, etc.). New building transition plans are still evolving, so it is unknown the extent of the impact on C2SES III activities.

1. REQUIREMENTS/DESCRIPTION OF SOFTWARE ENGINEERING SERVICES

The bidder’s library contains as-is documentation describing the system and software architectures, coding languages, size, complexity, etc., of the current system/software baselines for the systems identified in Section 2. The Contractor shall use this information to define the scope of effort required and ensure engineering staffing levels, skills, and experience levels are sufficient to successfully deliver the software engineering services describe herein. All software engineering services must comply with applicable documents and standards specified in Section 7 of this PWS.

2. Maintenance and Sustainment System/software maintenance and sustainment requirements as defined in this PWS will be applied as part of a software delivery specified in Section 3.4, Software Life Cycle Management. Software maintenance addresses corrective, preventive, adaptive, and perfective changes/updates to the applications identified in Section 2 of this PWS. Software sustainment includes documentation, deployment, security, configuration management, integration of GOTS and COTS software, and technology refreshes. As part of the on-going software maintenance and sustainment, the use of the Agile Software methodology is greatly encouraged, subject to Government approval. (CDRL A001, B001, C003) The Contractor shall:

1. Perform corrective, adaptive, perfective, and preventive maintenance, and provide associated documentation, as required.

1. 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.

1. Develop schedules and implementation plans, including dependencies and need dates, identification of technical approaches, and a description of anticipated expected results.

1. Design, develop, test and package software for release.

1. Maintain the current baselines of the systems and provide software changes and problem fixes to these baselines as required.

1. 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.

1. Ensure software engineering efforts are compatible with other C2 systems’ hardware, software, and architectures, including Integrated Strategic Planning and Analysis Network (ISPAN) Enterprise Database (EDB) and the C2EDB.

2. Major Enhancements Major system/software enhancements as defined in this PWS will be applied as part of a software delivery specified in Section 3.3, Software Life Cycle Management. Major system/software enhancements addresses major changes to the mission or communication capabilities to the applications identified in Section 2 of this PWS. Major system/software enhancements includes documentation, deployment, security, configuration management, integration of GOTS and COTS software, and technology refreshes. As part of the on-going system/software enhancement, the use of the Agile Software methodology is greatly encouraged, subject to Government approval. (CDRL A001, B001, C003)

The Contractor shall:

1. Conduct analysis of known and/or future identified enhancement capabilities to determine how the applications identified in Section 2 are impacted.

1. Develop schedules and implementation plans, including dependencies and need dates, identification of technical approaches, and a description of anticipated expected results.

1. Modify/enhance software to ensure a strong security posture is properly maintained.

1. Design, develop, test and package software for release.

1. Maintain the current baselines of the systems and provide software changes and problem fixes to these baselines as required.

1. 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.

1. Ensure software engineering efforts are compatible with other C2 systems’ hardware, software, and architectures, including Integrated Strategic Planning and Analysis Network (ISPAN) Enterprise Database (EDB) and the C2EDB.

2. Integration and Support Systems/software integration and support will be performed by the Contractor as part of a software delivery specified in Section 3.3 Life Cycle Management. Software designs and baseline include both GOTS and approved COTS software and tools delivered capabilities. (CDRL C004) The Contractor shall:

1. Perform system performance tuning and update software for compatibilities with technology changes (e.g., tech refresh), and integrate services as requested by the Government.

1. Perform the necessary software updates/changes to incorporate where applicable the integration with GOTS and approved COTS software.

2. Software Lifecycle Management Changes to system/application software may be required to reflect changes in national guidance and/or USSTRATCOM policy; implement Government prioritized, user-defined, functionality requirements; correct software deficiencies identified in the production environment; and incorporate compatibility upgrades resulting from changes in weapon systems, other C2 applications/databases, and supporting infrastructure. Based on user prioritization of requirements and C2 program management guidance, software changes will be delivered to the operational environment via scheduled releases. (CDRL A001, C003) The Contractor shall:

1. Coordinate software change requests, deficiency reports, and projects into scheduled releases in coordination with the Government.

1. Support major releases, minor releases, and security patch support for each application/system as defined in the task orders (TOs).

Major and minor releases are defined as follows:

1. A major release identifies a component or product delivered is incompatible with the previous major release, and indicates enhanced/new functionality is included in the software and/or product structure changes have been included. The duration of a major release is approximately 6-9 months, or longer.

1. A minor release indicates functional enhancements to the product. A minor release must be compatible with previous version of the same major release. A minor release does not necessarily require a re-install of the product, but can be overlaid on top of the existing installation. The duration of a minor release is approximately 3-6 months.

1. A security patch support addresses security issues for the program and may or may not be scheduled separately from directed software releases. A security patch release does not necessarily require a re-install of the product, but can be overlaid on top of the existing installation and easily removed if required. The duration of a security patch is approximately 30-90 days.

3. Release Scope The Government may reorder priorities and/or add other capabilities as mission requirements dictate. Delivery and implementation of software releases will be made upon completion of each item, following the test processes defined by the IPT and in accordance with (IAW) the requirements of paragraph 4.7 of this PWS. Updated product documentation, regression testing and performance testing will be required, incorporating all software changes for the release.

The Government, in coordination with the Contractor, will prioritize requirements for major and minor releases for each of the systems identified in section 2. The Contractor, in coordination with the Government, will prioritize requirements for security patch releases for each of the systems and make release schedule recommendations to the Government for approval for each of the systems identified in Section 2. The Government may decide to forgo one or both minor releases for a specific system, in which case the Contractor software engineering hours will be reallocated for a specific system. (CDRL A003, C004) The Contractor shall:

1. Analyze and recommend solutions to change requests (CRs) for Government prioritization and approval.

1. Incorporate prioritized user-defined mission requirement capabilities and adaptive, corrective, and perfective CRs into software support efforts for each version release.

1. Identify COTS software products and license requirements to be utilized in both support and operations of C2 applications.

1. Deliver modified software to operational units utilizing Government delivery resources or through remote capabilities.

The Contractor is responsible for determining the optimum skill mix based on software code complexity and current system/application architecture, as described in bidder’s library artifacts.

3. Major Release Documentation & Deliverables The Contractor shall provide updated documentation and other required deliverables IAW the type of release, CM Policy, C2 SEMP and C2 Test Process documents. Delivery and implementation of these releases will be made upon completion of each item.

The Contractor may use Agile Software methods for each release cycle, but the current set of system life cycle documentation or its equivalent must be maintained. The employment of Agile methods may drive changes to Government defined software lifecycle documentation to align to internal methods (e.g., iterative and incremental). Contractor proposed modifications to the documentation set delivered for each release, as listed below and defined in the C2 SEMP, are subject to Government approval. (CDRL C003, C004, C005) At a minimum, the Contractor shall update and deliver the documentation (or its equivalent) identified in Table 1 for each major release, including incorporation of any outstanding change pages from minor releases/patches.

Table 1 Major Release Documentation

X

Database Design Description (DBDD)

Interface Control Document (ICD)

X

Software User Manual (SUM)

X4

X6

X

Table 1 Notes

1. GADSS and FSAM maintain DDL for the GADSS and FSAM databases, but not a formal DBDD.

1. Description of the FSAM interface design is currently included in the SDD.

1. FSAM refers to this as “Software Installation Guide”.

1. FSAM refers to this as “User Operator Manual”.

1. Delivered as part of the SVD.

1. NPES Software User’s Manual maintained in online help (not a document delivery).

3. Minor Release Documentation & Deliverables For each minor release, the Contractor will develop and maintain document change pages for all system/software life cycle documentation, for incorporation into the updated/revised documentation at the next major release. (CDRL C003, C004, C005) In addition, and as a minimum, the Contractor shall deliver the documentation identified in Table 2 for each minor release.

Table 2 Minor Release Documentation

Table 2 Notes

1. FSAM refers to this as “Software Installation Guide”.

1. Delivered as part of SVD.

3. Patch Releases In order to comply with IA requirements or emergency changes driven by real-world operational needs, patch releases may be required to ensure delivered software meets warfighter needs.

The Contractor shall prepare and implement software patches IAW Government direction. The only documentation required for a patch release is the Software Test Report (STR) and the Software Version Description (SVD). Guidance for other documentation will be provided by the Government, driven by the nature and complexity of the patch, capability changes to the system, and the mission urgency for deployment. Hours expended in the analysis of software patches are included in the total number of software engineering hours available for a specific system. (CDRL C003, C004, C005)

2. Software Engineering Support and Test Environments The software engineering environments for evaluating, updating, testing, and maintaining software are provided by the Government and located at the Government location. The environments are supported by automated tools, manual procedures, or both. The Contractor may propose changes where they have the greatest impact and improvement on software quality and engineer productivity. The tools for managing system requirements, configurations and changes, acceptance testing, and verification and validation are provided by the Government. (CDRL A002, C004) The Contractor shall:

1. Perform all analyses and responses to stakeholder requests, software discrepancy reports (DRs), and software change request (CRs) on the Government specified network.

1. Track, manage, and provide status of all stakeholder requests, software discrepancies, and change requests in a Government provided repository (e.g., JIRA).

4. FSR and GADSS Environments The environment for FSR and GADSS software maintenance and acceptance test activities are provided by Government with administration of environment through other Contractors managed by the Government (i.e., not C2SES III). (CRDL C004) The Contractor shall:

1. Perform all FSR and GADSS software evaluations, updates, changes, and maintenance in the Government provided environments.

1. Coordinate all environment administration required for software engineering activities with Government Program Manager (PM).

1. Assist the Government PM in identifying and troubleshooting any issues with the software engineering environments.

1. As required, assist administration personnel in troubleshooting any system performance issues.

4. FSAM Environments The software engineering activities for FSAM will be accomplished in the Government specified environment. A dedicated environment is provided by the Government for the FSAM software engineering and support activities including all software changes. The environment for FSAM acceptance test activities is provided by the government with administration of the environment through other Contractors managed by the Government (i.e., not C2SES III). (CDRL C004) The Contractor shall:

1. Perform all FSAM software evaluations, updates, changes and maintenance in the dedicated FSAM development environment.

1. Coordinate all test environment administration required for software engineering activities with Government PM.

1. Assist the Government PM in identifying and troubleshooting any issues with the acceptance test environment.

1. As required, assist administration personnel in troubleshooting any system performance issues.

1. Coordinate all FSAM system and database administration required for software engineering activities with support teams provided as part of C2SES III.

1. Migrate the existing FSAM development support environment, where “development support environment” includes developmental tools (e.g. JIRA, Subversion, and Jenkins) and also migrate development application servers, to the USSTRATCOM C2LAN, maintain the existing FSAM development support environment and development applications servers and, where feasible, consolidate the hardware and software…