AddendumWCMDCMBRESLEPMAPEffort.pdf

Addendum 1

For

Common Munitions BIT/Reprogramming Equipment (CMBRE) Service Life Extension Program

(SLEP), Munitions Application Program (MAP) Common Code Development for Wind

Corrected Munitions Dispenser (WCMD)

May 20, 2020

1. GENERAL INFORMATION

1.1. Purpose

This Addendum outlines the efforts required to support the Common Munitions BIT/Reprogramming Equipment (CMBRE) Service Life Extension Program (SLEP), Munitions Application Program (MAP) common code library development and deployment of a complete CMBRE SLEP MAP for the Wind Corrected Munition Dispenser (WCMD).

1.2. Background

The CMBRE Program Office is addressing obsolescence, cybersecurity, and vendor lock issues currently associated with fielded CMBRE(s). Addressing the issues described, the CMBRE Program Office, AFLCMC/WNA Robins AFB, collaborated with the 520 SWES, Hill AFB, to develop and design a modernized Government owned Digital Computer System Assembly (DCSA) to address the obsolescence and vendor lock issues in hardware, software, firmware, and operating system. Therefore, currently fielded MAPs will not function with the CMBRE SLEP DCSA and will need to be re-hosted to a Linux CentOS environment.

1.3. Scope

The contractor’s responsibilities shall include the effective administration, management, execution, and performance of duties necessary to develop and deliver a field capable, Linux CentOS-based MAP that functions with the CMBRE SLEP system and the CBU-103, CBU-104, CBU-105, CBU-107, CBU-118 WCMD variants. The activities described within this Addendum will be performed at the contractor’s facility unless otherwise specified by the Government in individually defined objectives/tasks stated herein. In cases where this Addendum reveals ambiguities, the PWS takes precedence to include services and quality measurement thresholds.

1.4. Applicable Documents:

In the event of conflict between the text of this Addendum and the references cited herein, the text of this Addendum shall take precedence:

a) WCMD CMBRE Application Software (WCAS) Interface Control Document (ICD)

For WCMD

b) WCMD CMBRE Application Software (WCAS) System Requirements Specification

(SRS)

c) WCMD CMBRE Application Software (WCAS) for the WCMD MAINTENANCE

LOG FILE DESCRIPTION

d) CMBRE SLEP Programmer’s Manual for Munition Application Program (MAP)

Developers Guide w/ periodic updates will be required.

2. GENERAL REQUIREMENTS

2.1. Program/Project Management

The contractor shall identify, by name, to the Government a single point of contact (Program/Project Manager) for all matters under this contract. The Program/Project Manager and team shall be responsible for the planning, coordinating, implementing, monitoring, reporting, and ensuring Software Development Teams are adequately staffed, and readily available, as required to meet the objectives stated herein.

2.2. Logistics Management Support

The contractor shall provide direction and support to manage WCMD activities that include maintaining WCMD Technical Order source data and WCMD CMBRE software to include evaluation and verification support of system changes, training updates, field/user support, and transportation and delivery to meet the objectives stated herein.

2.3. Engineering Management Support

The contractor shall provide appropriate Engineering resources (Chief Engineers, Integrated Product Team (IPT) leads, Responsible Engineering Authorities (REAs), Systems Engineering, Software Engineering, and Subject Matter Experts) to support the execution of the objectives and requirements stated herein.

2.4. Cybersecurity

2.4.1. Software Cybersecurity: All software/firmware created, modified, delivered, and installed as part of this effort must utilize non-repudiation techniques to guarantee the integrity and origin of the MAP software/firmware throughout the software/firmware lifecycle. The contractor must incorporate peer review and static code analysis in all software/firmware created, modified, delivered, and installed.

2.4.2. Cybersecurity Controls: The contractor must ensure that familiarization materials, technical manuals, and other technical data developed as part of this effort address any cybersecurity controls (e.g., administrative, procedural, inherited) or requirements that affect system operation, maintenance, repair or other support activities.

2.4.3. Cybersecurity Analysis: The contractor must conduct analysis for any Commercial-Off- The-Shelf (COTS) and/or non-developmental items to ensure that they are appropriately configured, software/hardware/firmware is controlled, and any unique risks they pose are mitigated.

2.4.4. Cyber-Secure Development Environment: The contractor must maintain a cyber-secure development environment that reduces and manages risk by implementing, at a minimum, the following select controls from CNSSI 1253 as defined in NIST SP 800-53r4: SA-10, SA-15, and AT-2 .

3. DETAILED REQUIREMENTS

Program/Project Management Support

3.1. Program/Project Management (PM)

3.1.1. The PM shall submit Monthly Status Reports (MSRs) documenting the activities and progress of the previous month, also identifying planned activities for the following month.

For the duration of this effort, the MSR shall be submitted monthly, with the initial report due NLT than five (5) business days after the first full month from the contract award date. The status reports must be delivered to the Government Contracting Officer Representative (COR) or appropriate Manager/Lead from the System Program Office (SPO) [CDRL A003, DI- MGMT-80227, Contractor’s Progress, Status and Management Report].

3.1.2. The contractor must support and participate in scheduled WCMD Program Management Reviews (PMRs) and prepare briefing materials, reports, and other documentation necessary to discuss project status, problems, and issues [CDRL A003, DI- MGMT-80227, Contractor’s Progress, Status and Management Report].

3.1.3. The contractor shall host Quarterly Working Groups and Technical Interchange Meetings (TIMs) between the Government CMBRE SLEP Team and partners as necessary to support project objectives and requirements. Additionally, the contractor shall be prepared to travel to Eglin AFB to support semi-annual CMBRE PMRs. In support of working groups and meetings, the contractor shall develop meeting materials and minutes, and be prepared to support opportunistic demonstrations/evaluations of software with assets provided by the 520 SWES [CDRL A005, DI-ADMN-81373, Presentation Materials].

Logistics and Engineering

3.2. Logistics Support. The contractor shall provide logistics support for those activities required to support the efforts described herein. This effort shall include, but are not limited to the following:

3.2.1. Provide Government Furnished Equipment (GFE)/Government Furnished Property (GFP) asset management to comply with FAR/DFAR/PGI requirements, and support Financial Improvement Audit Readiness (FIAR).

3.2.2. Provide Packaging Handling Storage and Transportation (PHS&T) support where:

a) The contractor must package and mark material in accordance with the contract/order Air Force Materiel Command (AFMC) Form 158, Packaging Requirements, and applicable Government regulations to include MIL-STD- 129P(4), Department of Defense Standard Practice/Military Marking for Shipment and Storage; MIL-STD-130N, Department of Defense Standard Practice/Identification Marking of U.S. Military Property; MIL-STD-2073-1D, Standard Practice for Military Packaging; and/or other applicable U.S.

Government packaging requirements. Unsuitable shipping containers must be disposed of and replaced with new containers that meet the requirements of the AFMC Form 158. The contractor must ensure that classified material is packaged, marked and delivered IAW DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM).

b) The contractor shall be responsible for shipping all material and/or test equipment required under this effort to and from the contractor’s location, Original Equipment Manufacturer (OEM) facility, or Military installation (i.e., Hill AFB, UT and Eglin AFB, FL). The contractor must provide either a shipping document or shipping account information to the Government when shipping is required to the contractor’s facility. Prospective shipments will include:

3.2.2.b.1. Four (4) shipping occurrences of one (1) DCSA & one (1) PCMCIA Reader.

3.2.2.b.2. One (1) shipping occurrence of one (1) Development Kit.

3.2.2.b.3. Two (2) miscellaneous shipping occurrences annually for small shipments i.e., software packages, items less than 10 lbs., etc.

c) The contractor must use a commercial shipping method that provides a shipment tracking function for each shipment and provide the shipment tracking number to the Government when shipment occurs. Preservation and packaging of all items must provide adequate physical and environmental protection for the identified mode of shipping, handling, and storage conditions. Container markings must include information for easy item identification and must be compatible with existing Government methods of receiving, shipping, storage, and inventory control. The contractor must coordinate any transportation issues with the Government.

3.2.3. Support WCMD compatibility testing with the CMBRE Plus TAU interface, the CMBRE SLEP TAU interface, and multiple DCSA configurations to substantiate system and MAP compatibility and functionality.

3.3. Software (SW) Development Support. The contractor shall provide full-time Software Development Support that is adequately staffed, stable, and capable of supporting the CMBRE SLEP WCMD MAP development and common code effort. The team of SW Developers shall be responsible for designing, developing, integrating and testing, verifying and validating, and deploying software that:

3.3.1. Satisfies all WCMD CMBRE Application Software (MCAS) System Requirements Specifications.

3.3.2. Satisfies all MCAS Interface Control Document requirements for WCMD.

3.3.3. Adheres to all CMBRE SLEP MAP Writers Guide code format, software/library calls and interface requirements.

3.3.4. Ensures interoperability with the CMBRE plus TAU interface, the CMBRE SLEP TAU interface, and corresponding DCSA configurations.

In addition to the objectives referenced above, the contractor’s SW Development Team shall:

3.3.5. Develop a reusable common MAP software framework with associated common requirements and documentation that supports a fully functional WCMD MAP.

3.3.6. Perform special duties as requested by the Government (e.g. Maintain operation logs to support CMBRE SLEP reliability calculations). Operation logs shall be included as an appendix in the MSR (Ref. para. 3.1.1).

3.3.7. Provide common MAP software framework test reports of the WCMD MAP to the 520SWES that are generated utilizing a DevOps Automated Test Pipeline. Subject reports shall be incorporated in to the MSR as an appendix (Ref. para. 3.1.1)

3.3.8. Develop Functional Qualification Test (FQT) plan(s) as required to assess the interoperability of software, data link, formats, timing – and any other pertinent interactions with the CBU-103, CBU-104, CBU-105, CBU-107, CBU-118 WCMD variants.

3.3.9. Travel to Eglin AFB, FL or otherwise specified location – Guidance Weapons Evaluation Facility (GWEF) to support and perform FQT activities as required to qualify the CMBRE MAP software against the CMBRE SLEP system components.

3.3.10. Update current documentation as required for the CMBRE MAP software to include the:

a) Software Version Description (SVD) [CDRL A002, DI-IPSC-81442A, Software Version Description].

b) Contractor’s Progress, Status and Management Report [CDRL A003, DI- MGMT-80227, Contractor’s Progress, Status and Management Report].

c) Interface Control Document (ICD) [CDRL A004, DI-SESS-81248B, Interface Control Document].

d) Presentation Material [CDRL A005, DI-ADMN-81373, Presentation Material].

e) Computer Software Product End items [CDRL A006, DI-MCCR- 80700A, Computer Software Product End items].

3.3.11. Deliver a fully functional field representative WCMD MAP (CDRL A006, DI- MCCR-80700A, Computer Software Product End Items).