Attachment 18 - ISC2.0 PWS ATO1 MMIII DIRSUP.pdf

FA8207-20-R-0003 - ISC 2.0

Task Order 1: MMIII Directorate Support PWS

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

INTEGRATION SUPPORT CONTRACT (ISC) 2.0

TASK ORDER 1: MINUTEMAN III (MMIII) DIRECTORATE SUPPORT

PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

MMIII SYSTEM PROGRAM OFFICE (SPO)

14 OCTOBER 2020

CONTENTS

1.0 ISC – MMIII DIRECTORATE SUPPORT

2.0 GENERAL REQUIREMENTS

3.0 ENGINEERING

4.0 FINANCE

5.0 TRANSITION

6.0 PORTFOLIO MANAGEMENT

7.0 INFORMATION TECHNOLOGY (IT)/CYBERSECURITY

8.0 ICBM WARHEAD LEAD PROJECT OFFICE (LPO)

9.0 FORCE DEVELOPMENT EVALUATION (FDE)

10.0 SCHEDULING

11.0 MMIII DEMILITARIZATION (DEMIL) AND DISPOSAL

ACRONYM LIST ….……………….………………………….……………….………………38

1.0 ISC – MMIII DIRECTORATE SUPPORT

MMIII DIRECTORATE SUPPORT DESCRIPTION

The MMIII Directorate Support requirement consists of the functional support needed to provide policy, governance, organization, training, and other functional support to the MMIII SPO. This functional support provides an overarching perspective to senior leadership and assists in developing a clear understanding of the current status of the MMIII Weapon System (WS).

The MMIII Directorate Support PWS consists of requirements from the following functional areas:

• Engineering

• Finance

• Transition

• Portfolio Management

• Information Technology (IT)/Cybersecurity

• Lead Project Office (LPO)

• Force Development Evaluation (FDE)

• Scheduling

• MMIII Demilitarization (DEMIL) and Disposal

DATA DELIVERABLES (Contract Data Requirements Lists [CDRLs]) A master list of potential DoD Form 1423s (DD 1423s), Contract Data Requirements Lists, is provided as Section J Attachment 6, Contract Data Requirements Lists (CDRLs).

Due to the quantity and diversity of the programs in the ICBM Organization, the type and magnitude of required support is different for each program. Each program will employ the tasks in this PWS to the extent needed by that program. This also means that data deliverable needs will vary based on the program. To this end, CDRLs are not referenced in this PWS after every paragraph in which they may be required.

CDRLs specifically referenced in this PWS are to be delivered every time the task required by the referenced paragraph is performed (e.g. monthly status reports, training materials, engineering documentation, etc.).

If a program determines that a formal data deliverable is needed for a paragraph without a CDRL reference (e.g. advice, recommendations, analysis reports, etc.), the Government representative will select the appropriate CDRL from the master list and specify the delivery date/address and any other necessary instructions on the DD 1423. Any additional tailoring will also be documented on the DD 1423 at that time. The CDRL number will be incorporated into the associated task assignment (see paragraph 4.9 of the Basic PWS).

2.0 GENERAL REQUIREMENTS

2.1. All requirements in the Basic PWS of this contract apply to this Task Order.

2.2. All work shall be performed in coordination and cooperation with pertinent overseeing by

Government personnel. (The Government Program Manager (PM) and Engineer are responsible for meeting programs’ cost, schedule, technical, and performance objectives.

As the system integrator, the Government is the decision authority.)

2.3. All work shall be performed in coordination with Subsystem Support Contractors (if applicable) and other contracted personnel.

2.4. The Contractor shall collaborate with appropriate internal and external stakeholders as needed to accomplish requirements and tasks.

2.5. All work shall be performed in accordance with (IAW) applicable laws and regulations.

2.6. The Contractor shall NOT perform any Inherently Government Functions as defined in

Federal Acquisition Regulation (FAR) 7.503.

2.7. The Contractor shall recommend and incorporate process and resource efficiencies, including application of streamlined Program Management techniques and other industry best practices.

2.8. Meeting Support: Appropriate functional Contractor personnel shall participate in, contribute to, and provide technical and programmatic expertise for meetings, reviews, and boards as needed, IAW the Basic PWS paragraph 3.9. (CDRLs A002, A003, A004, A059- 73)

3.0 ENGINEERING

3.1. Knowledge Transfer (KT)

Description The goal of KT is to create a capable and competent Government workforce prepared to manage and perform the necessary functions in providing daily MMIII WS lifecycle support.

The objective of KT is to improve Air Force (AF) personnel’s MMIII life cycle support competencies. To this end, the MMIII SPO may identify areas where MMIII-specific training or courses of various technical depth, complexity, and duration are desired.

Requirements include developing training material and courses, providing all logistic support required for the training, tracking student attendance, etc.

3.1.1. The Contractor shall provide insight and assist the Government in developing an innovative solution that accomplishes KT.

3.1.2. The Contractor shall identify subject areas pertinent to MMIII WS support and where instruction would be beneficial to the AF.

3.1.3. The Contractor shall provide insight and assist the Government in developing a variety of training and classes as requested.

3.1.4. The Contractor shall develop lesson plans. (CDRL A008-4)

3.1.5. The Contractor shall provide instructors and logistic support to accomplish required training, ranging from standalone Computer Based Training Modules to multi-hour/day instructor lead courses, either in AF facilities or off-site.

3.1.6. The Contractor shall deliver all training plans and tests developed to the Government. (CDRL A008-4)

4.0 FINANCE

Financial Management (FM) Description MMIII FM is the office that manages the Planning, Programming, Budgeting and Execution (PPBE) process for the MMIII SPO. This includes financial reporting and ensuring the integrity of financial data within Government accounting and information systems.

FM support is technical and administrative in nature. FM support does NOT require the Contractor to perform any Inherently Government Functions, including making any decisions regarding funding obligation authorization, funds certification, etc. The nature of FM support requires the Contractor to adapt to changing standards, policies, and practices while performing the tasks within this section of the PWS.

4.1. General Requirements

4.1.1. The Contractor shall understand and ensure compliance with fiscal laws and funding policies.

4.1.2. The Contractor shall provide decision support and financial reporting to ICBM personnel, management and stakeholders.

4.1.3. The Contractor shall ensure the integrity of financial data within Government accounting and information systems.

4.2. Programming

4.2.1. The Contractor shall participate in and provide information for planning, writing, programming, documenting and justifying ICBM requirements IAW ICBM standards and regulatory guidance.

4.2.2. The Contractor shall participate in and provide information for preparation of the annual Program Objective Memorandum (POM) and related briefings.

4.2.3. The Contractor shall ensure all acquisition and sustainment program requirements are recorded, programmed, and phased correctly in applicable financial systems.

4.2.4. The Contractor shall review cost estimates (e.g. Program Office Estimates (POEs), POE annual updates, Independent Government Estimates (IGEs), etc.) to ensure requirements and budgets are accurately recorded in applicable financial systems across programs’ lifecycles.

4.2.5. The Contractor shall ensure funding requirements and budget levels are accounted for and balanced across all assigned financial systems and products.

4.3. Budgeting and Execution

4.3.1. The Contractor shall ensure compliance with fiscal laws and funding policies prior to Early Acquisition Strategy (EAS)/Early Strategy and Issues Session (ESIS) briefings and POM submissions.

4.3.2. The Contractor shall record program budgets in applicable financial systems.

4.3.3. The Contractor shall formulate, document and justify assigned budgets IAW ICBM standards and regulatory guidance.

4.3.4. The Contractor shall assist the Government with the preparation of assigned budget formulation efforts such as the Budget Estimate Submission (BES) and President’s Budget (PB), as well as budget adjustment activities such as realignments and reprogramming.

4.3.5. The Contractor shall prepare Target Loads according to Financial Improvement and Audit Readiness (FIAR) standards, while ensuring they are supported by Budget Authorization/Allocation or Operating Budget Authority documentation.

4.3.6. The Contractor shall assist the Government with management of budget overages and shortfalls, preparation of reprogramming/realignment requests that meet overall system priorities, and preparing responses to budget cut drills.

4.3.7. The Contractor shall analyze and provide solutions for how to meet Office of the Secretary of Defense (OSD) goals.

4.4. Forecasting

4.4.1. Obligation Forecasting

4.4.1.1. The Contractor shall create obligation forecasts for all funded requirements.

4.4.1.2. The Contractor shall ensure obligation forecast plans are submitted, coordinated, accounted for, and reported in required financial systems/products.

4.4.1.3. The Contractor shall verify all approved budgets are forecasted with relevant obligation activities.

4.4.1.4. The Contractor shall confirm obligation documentation is accounted for in assigned Government systems, imbalances with financial systems and financial documentation are identified and resolved, and issues are communicated as required to the Government.

4.4.2. Expenditure Forecasting

4.4.2.1. The Contractor shall create expenditure forecasts for all funded and unfunded requirements, as needed.

4.4.2.2. The Contractor shall ensure forecasted expenditure plans are submitted, coordinated, accounted for, and reported in required financial systems/ products.

4.4.2.3. The Contractor shall ensure all approved budgets are forecasted with relevant expenditure activities.

4.4.2.4. The Contractor shall ensure relevant invoice activities are accounted for in assigned Government systems, imbalances with financial systems are identified and resolved, and issues are communicated as required to the Government.

4.5. New Start Notification

4.5.1. The Contractor shall assist in reviews and coordination of New Start Notification(s) that conform to Air Force Instruction (AFI) 65-601, Budget Guidance and Procedures/Budget Management for Operations, and Department of Defense (DoD) Financial Management Regulation (FMR) 7000.14.

4.6. Execution of Current Year Funds

4.6.1. The Contractor shall ensure funds are executed properly and timely IAW all applicable laws and regulations.

4.7. Requirements, Funded, and Unfunded Activities

4.7.1. The Contractor shall ensure requirements documentation balances with assigned financial systems to actively track funding requirements through the Future Years Defense Plan (FYDP).

4.7.2. The Contractor shall ensure funded requirements, Unfunded Requirements (UFRs), and excess funding are recognized and properly supported in assigned financial systems.

4.7.3. The Contractor shall evaluate and analyze funds execution each month, identify potential funding sources, and notify the Government of funding disconnects.

4.8. Fiscal Year Closeout

4.8.1. The Contractor shall support the Government to ensure that funds are ultimately

100% obligated or in contingent liability prior to funds expiration, and notify the Government when not 100%.

4.8.2. The Contractor shall work with applicable Government leadership to ensure that requirements are represented in year-end spending lists and prioritized appropriately.

4.9. Expiring Year and Expired Funds Management

4.9.1. The Contractor shall support the Government in managing unobligated and/or unliquidated active funds that can be utilized prior to funds expiration.

4.9.2. The Contractor shall support the Government in managing expired funds that can be utilized prior to funds cancellation.

4.9.3. The Contractor shall provide advice on how to obligate or declare all unobligated expiring and expired funds as excess while funds are still available.

4.9.4. The Contractor shall assist the Government in control of obligation of expired fiscal year funds.

4.9.5. The Contractor shall ensure new obligations of expired funds are coordinated in financial and program management systems as Upward Obligation Adjustments (UOAs).

4.10. Accounting

4.10.1. The Contractor shall build funding Lines Of Accounting (LOA), perform

Comprehensive Cost and Requirement (CCaR) System reconciliations, validate LOA-build accuracy in Commanders Resource Integration System (CRIS), perform quarterly review of documents, research Open Document List (ODL) issues (such as dormant obligations, canceling year unliquidated obligations, fall-out/fall-in analysis, and accounting errors), ensure the quality of CCaR records, and reconcile and balance related systems (e.g. CCaR to General Accounting and Finance System (GAFS) daily, CCaR to Funded Requirements Management (FRM) and Project Management Resource Tool (PMRT) Enterprise Analytics (EA), and GAFS to Mechanization of Contract Administration Services (MOCAS)/Shared Data Warehouse and FM Suite) while working ODL issues.

4.10.2. The Contractor shall participate in preparation and presentation of a monthly ODL status report.

4.10.3. The Contractor shall coordinate with the assigned base Comptroller office and/or Defense Finance and Accounting Service (DFAS) to resolve and/or close any ODL issues.

4.10.4. The Contractor shall ensure the accuracy of month-end reports.

4.10.5. The Contractor shall review and update assigned program budgets and funds execution in the CCaR system as necessary.

4.11. Reconciliation

4.11.1. The Contractor shall provide advice and recommendations on monitoring the

PMRT financial system data (CCaRs, Monthly Acquisition Reports (MARs), etc.)

to support budget development, forecasting obligations and expenditure plans, while maintaining traceability of budget items to other program documentation.

4.11.2. The Contractor shall provide advice and recommendations on creating inputs necessary for all applicable budget exhibits or ICBM appropriations.

4.11.3. The Contractor shall provide advice and recommendations on forecasting and reconciliation efforts related to obligations and expenditure plans, contingent liabilities, and inconsistent or inappropriate billing.

4.11.4. The Contractor shall identify potential shortfalls and execution issues, and provide mitigation strategies for forward financing issues, excessive billing cycle lag, potential shortfalls and contingency liability sufficiency.

4.11.5. The Contractor shall document and present the results of the previous tasks to AFNWC Budget Chiefs or designees, and higher headquarters. (CDRL A003)

4.12. Decision Support and Reporting

4.12.1. The Contractor shall provide advice, assistance, and recommendations regarding financial status reports.

4.12.2. The Contractor shall produce financial status reports.

4.12.3. The Contractor shall develop a financial execution status briefing consisting of:

(CDRL A003)

• Execution plans and status

• Execution issues and obligated/unobligated funds

• Expenditure status

• Unfunded requirements and potential realignments after analyzing budget excesses and shortfalls

• Future events within the assigned organization’s battle rhythm as related to financial management and budget

• Major issues and risks with assigned funds

• Ways to achieve effective programming, budgeting, fund execution

• Ways to achieve effective internal control of division requirements and resources

• Viable alternatives and recommendations

4.12.4. The Contractor shall advise the Government on:

4.12.4.1. Managing funding requirements in relevant assigned ICBM systems

4.12.4.2. Producing the annual BES/PB submission

4.12.4.3. Budget execution

4.12.4.4. Extracting, preparing, and presenting the financial information required in acquisition and sustainment briefings and reports such as:

• MARs

• Selected Acquisition Reports (SARs)

• Defense Acquisition Executive Summary (DAES)

• Constrained/Unconstrained Budget Reports

• Long Range Defense Planning (LRDP)

• Financial Working Groups (FWGs)

• Program Management Reviews (PMRs)

• Etc.

4.12.4.5. Accuracy and probability of obligation and expenditure forecasts, obligation events, and program schedules

4.12.4.6. Assisting working groups/Integrated Product Teams (IPTs) with writing effective program and requirement description and impact narratives

4.12.4.7. Other finance-related issues as needed

4.12.5. The Contractor shall provide analysis, advice, and assistance with:

4.12.5.1. Improving internal financial processes and incorporating best practices

4.12.5.2. Financial impacts of changes to and interpretations of regulations and policies

4.12.5.3. Impacts of FYDP planning numbers, budget outlooks and Major

Command (MAJCOM)/Secretary of the Air Force (SAF) fiscal year guidance

4.12.5.4. Impacts of spending trends

4.12.5.5. Completing suspensed tasks

4.12.5.6. Preparing reports or minutes of meetings attended (CDRL A004)

4.12.5.7. Preparing for Centralized Asset Management (CAM) Advisory Councils

(ACs), FWG, Investment Financial Working Groups (IFWGs), Resource Management Boards (RMBs), Spring Program Reviews (SPRs), Fall Program Reviews (FPRs), Investment Budget Reviews (IBRs) and the Manager’s Internal Control Program (MICP)

4.12.5.8. Viable alternatives and recommendations

4.12.5.9. Other finance-related issues as needed

4.12.5.10. Stakeholder support

4.12.6. The Contractor shall advise and assist key ICBM stakeholders (e.g. AF Global Strike Command (AFGSC), AF Materiel Command (AFMC), AFNWC/FM, AF Portfolio Executive Officer/Strategic Systems (AFPEO/SS), United States Strategic Command (USSTRATCOM), Program Element Monitors (PEM) at SAF/AQ, etc.)

to advocate effectively for ICBM needs.

4.12.6.1. The Contractor shall respond to stakeholder questions and requests for information by suspense dates and times.

4.13. Funding Document Support

4.13.1. The Contractor shall review, track, and assist with building funding documents such as:

• AF Form 9 - Request for Purchase

• DoD Form (DD) 448 - Military Interdepartmental Purchase Request

• AF Form 185 - Project Order

• AF Form 4009 - Government Purchase Card Fund Cite Authorization

• AF Form 406 - Miscellaneous Obligation/Reimbursement Document

• AFMC Form 181 - Project Order

• AFMC Form 376 - Administrative Commitment Document

• Other funding documents as needed

4.13.2. The Contractor shall utilize and comply with the AFNWC Financial Management Records Management Plan to ensure ease of access to financial information and continuity of operations.

4.14. Systems

4.14.1. The Contractor will be provided access to and shall use Government accounting and information as required, in the following systems:

• FM Suite

• Defense Enterprise Accounting Management System (DEAMS)

• Automated Funds Management (AFM)

• Defense Transaction Interface Module Systems (DTIMS)

• CRIS

• Integrated Budget Documentation and Execution System (IDECS)

• Centralized Access for Data Exchange (CAFDEx)

• FRM

• Job Order Production Master System (JOPMS/G004L)

• Automated Project Order (APO/JO25A)

• Defense Industrial Financial Management System (DIFMS)

• Electronic Document Access (EDA)

• Automated Business Services System (ABSS)

• PMRT including CCaRS and EA

• Defense Travel System (DTS)

• Shared Data Warehouse (SDW)

• Wide Area Workflow (WAWF)

• MOCAS

• Other systems as required

4.15. Specific Qualifications

4.15.1. Contractor personnel assigned to FM shall have knowledge and experience in:

• Understanding, following, and managing PPBE concepts

• Using the Microsoft Office Suite and Government accounting and information systems to accomplish normal financial management functions within a SPO

• Producing accurate financial status reports and analyzing/interpreting data within financial status reports

• Developing specialized spreadsheets and improving existing models to achieve greater accuracy and efficiency

5.0 TRANSITION OFFICE

Transition Office Description The Transition Office manages the planning, integration, and synchronization of the MMIII SPO, Ground Based Strategic Deterrent (GBSD) SPO, and external stakeholders, including AFGSC and others, to plan, prepare and successfully execute AF mission re-alignment from the MMIII ICBM to the GBSD ICBM as the land-based leg of the nuclear strategic triad.

5.1. Transition Office Support

5.1.1. The Contractor shall provide recommendations of transition effort task prioritization to Transition Office leadership.

5.1.2. The Contractor shall develop, update and manage ICBM transition metrics.

5.1.3. The Contractor shall support the Transition IPT with administrative requirements.

5.1.4. The Contractor shall develop and manage the Transition schedule.

5.1.5. The Contractor shall integrate MMIII and GBSD programmatic schedule activities impacting ICBM transition/schedules/roadmaps.

5.2. ICBM Transition Logistics Support

5.2.1. The Contractor shall coordinate GBSD deployment between the Transition Office and GBSD SPO IPTs.

5.2.2. The Contractor shall coordinate MMIII deactivation between the MMIII SPO and

Enterprise stakeholders.

5.2.3. The Contractor shall assess and deconflict timelines and efforts of GBSD deployment and MMIII deactivation.

5.2.4. The Contractor shall develop transition planning guidance, including ISC manpower requirements, based upon ICBM transition timelines.

5.2.5. The Contractor shall analyze transition risks to MMIII deactivation and GBSD deployment, and develop Courses of Action (COAs) and mitigation strategies.

5.2.6. The Contractor shall communicate with MMIII stakeholders to relay questions, assumptions, constraints, and limitations to GBSD deployment.

5.2.7. The Contractor shall attend meetings as needed to integrate, synchronize and communicate ICBM transition requirements.

5.2.8. The Contractor shall analyze ICBM logistics processes and identify what MMIII

SPO efforts are necessary to minimize impact to GBSD deployment.

5.3. Transition Model Based System Engineering (MBSE) Support

5.3.1. The Contractor shall implement a predictive MBSE environment to inform all aspects (operational, programmatic, etc.) of ICBM transition.

5.3.2. The Contractor shall develop, build, implement, maintain, update, and operate

ICBM transition software modeler and build modeling/simulation software tools.

5.3.3. The modeling/simulation software tools shall employ predictive logic to:

5.3.3.1. Enable analysis of ICBM transition functions, i.e. variables and outcomes of changing factors of MMIII deactivation and GBSD deployment

5.3.3.2. Simulate ICBM factors, functions, and resource availability to identify constraints requiring mitigation

5.3.3.3. Offer process logic for all relevant Missile Wing and Depot support activities, as well as personnel and equipment availability

5.3.4. The Contractor shall continuously update model fidelity with real-time numbers provided by customers for specific asset availability.

5.3.5. The Contractor shall provide MMIII deactivation and GBSD deployment inputs to update transition models.

5.3.6. The Contractor shall perform data analytics of model outputs.

5.3.7. The Contractor shall maintain all iterations of the model and subsections including process alterations and process logic.

5.3.8. The Contractor shall maintain all software system updates relative to the model.

5.3.9. The Contractor shall perform transition model maintenance to include interface compatibility, troubleshooting, and updates to the modelling software.

5.3.10. The Contractor shall provide training and tutorials for the Transition Team to maintain their proficiency in using and explaining the model to extended stakeholders. (CDRL A107)

5.4. Specific Qualifications

5.4.1. Contractor personnel assigned to the Transition Office shall have:

• Modern programming language understanding (e.g. C++, JAVA, PYTHON) and knowledge of scripting languages (e.g. MATLAB) to customize/configure required software tools

• MBSE product knowledge and the ability to use software platforms (e.g.

CAMEO)

6.0 PORTFOLIO MANAGEMENT

6.1. Long-range Planning/Strategic Messaging

Strategic messaging should effectively communicate the status of the MMIII WS (including any ancillary equipment and systems), risks to effective operation of the WS, status of mitigation activities, gaps and operational impacts caused by resource limitations, and status of sustainment and acquisition efforts.

6.1.1. The Contractor shall assist the Government in developing strategic messaging themes to effectively communicate with internal and external stakeholders.

6.1.2. The Contractor shall provide support for quarterly conferences, including meeting planning, agendas, minutes, and action items. (CDRLs A002, A003, A004, A059- 73)

6.1.3. The Contractor shall create, update, and deliver an annual ICBM Roadmap report that informs stakeholders on ICBM requirements to support the MMIII WS. (CDRL A136)

6.1.4. The Contractor shall generate metrics in support of strategic messaging.

6.1.5. The Contractor shall perform individual tasks deemed appropriate by MMIII leadership.

7.0 INFORMATION TECHNOLOGY (IT)/CYBERSECURITY

IT/Cybersecurity The IT/Cybersecurity Office plans, acquires, deploys, sustains, authorizes, reports, and provides cybersecurity expertise for all IT requiring accountability and/or cybersecurity assessment and authorization. It provides programmatic oversight to the ICBM Integrated Data Environment (IDE) and assistance to Enterprise-level data management systems. The Office serves as the SPO-level support office for procurement of IT.

This effort is focused on cybersecurity, IT acquisition/sustainment support, and project management for ICBMs. IT/Cybersecurity support involves work in a wide range of functions, such as Program Management, Cybersecurity Analysis, Software Engineering, Information System Security Management, Technical Writing, Quality Assurance (QA), Configuration Management (CM), Process Controls, Administrative Support, etc.

7.1. General Requirements

7.1.1. The Contractor shall provide consulting and project management services.

7.1.2. The Contractor shall work on multiple projects simultaneously and recommend project priorities.

7.1.3. The Contractor shall create project plans and presentations.

7.1.4. The Contractor shall perform analysis and provide recommendations on strategic and tactical directions.

7.1.5. The Contractor shall propose and create Enterprise electronic communications systems for Government review and approval prior to release.

7.1.6. The Contractor shall support/facilitate/participate in meetings, including scheduling, arranging facilities, providing materials (e.g. charts, dashboards, other means of displaying information, etc.), documenting official decisions and actions assigned, etc. (CDRLs A002, A003, A004, A059-73)

7.1.7. The Contractor shall provide IT acquisition and cybersecurity training.

7.1.7.1. The Contractor shall perform training sessions according to user need.

7.1.7.2. The Contractor shall develop training materials (e.g. charts, diagrams, other instructional aides) for training performed and keep the materials current. (CDRL A107)

7.2. IT Support

IT Support Description DoD IT includes DoD owned/controlled information systems, IT products, hardware and software, IT services, Platform Information Technology (PIT) and PIT Systems.

IT support involves software deployment, software CM, and software deployment quality assessment and control activities. Services and support include Service Desk, documentation, training, Data Management (DM), CM, program/project management, QA, Software Engineering, and System Administration. Efforts include assessment of data and processes, troubleshooting defects, providing bug fixes and software patches, consultation and helpdesk services for software and systems, and integration and migration of data and processes in Government-Off-The-Shelf (GOTS) and Commercial-Off-The-Shelf (COTS) software applications supporting the ICBM IDE, such as Microsoft SharePoint, Atlassian JIRA, Oracle Primavera, Siemens Teamcenter, and similar software.

7.2.1. General IT Requirements

7.2.1.1. The Contractor shall provide senior design, development, deployment, integration, administration, sustainment, management, etc. services in support of automated collaboration, workflows, business processes, business-intelligence dashboards, web content, data, information, and knowledge management.

7.2.1.2. The Contractor shall assist with implementation of AF policies and procedures, IAW AF Manual (AFMAN) 17-1203, Information Technology (IT) Asset Management (ITAM).

7.2.1.3. The Contractor shall provide support, source data, and analysis for acquisition and sustainment of IT systems.

7.2.1.4. The Contractor shall ensure IT is acquired, documented, operated, used, maintained, and disposed of properly IAW AFI 17-101, Risk Management Framework (RMF) for Air Force Information Technology (IT).

7.2.1.5. The Contractor shall recommend custom application configuration specifications and provide associated product delivery timelines.

7.2.1.6. The Contractor shall participate in change management processes involving hardware and software (e.g. testing and evaluation support, etc.).

7.2.1.7. The Contractor shall develop and recommend implementation strategies, deployment schedules, and other artifacts.

7.2.1.8. The Contractor shall create architectural diagrams.

7.2.1.9. The Contractor shall perform software defect tracking and reporting.

7.2.1.10. The Contractor shall provide bug fix estimation (along with system data update estimated cost if applicable).

7.2.1.11. The Contractor shall ensure that software program risks are identified and managed as part of the overall program risk management process.

7.2.1.12. For Government-conducted assessments, the Contractor shall analyze data and provide recommendations for further action.

7.2.2. Integrated Data Environment (IDE)

The IDE used by the Government for data in support of ICBM WSs must be a common, long-term, consistent, and continuous data infrastructure.

7.2.2.1. The Contractor shall develop and recommend processes for the applications within the IDE, ensuring CM compliance.

7.2.2.2. IDE Health

7.2.2.2.1. The Contractor shall maintain the health of the IDE.

7.2.2.2.2. The Contractor shall identify, manage, and verify requirements for sustaining and modernizing the IDE.

7.2.2.2.3. The Contractor shall determine and perform the tasks necessary to maintain IDE health, such as:

• Monitoring application and system status for system availability

• Application installation, configuration, and patching

• Operating System (OS) installation, configuration, and patching

• Soliciting third-party support, identifying problems, and resolving incidents and problems

• Major version updates of major applications, plug-ins and any other software used in the IDE

• Recommending replacement of applications as new technology becomes available

• Other tasks as applicable

7.2.2.3. IDE Configuration

7.2.2.3.1. The Contractor shall create and/or assess software strategies, including which applications should be deployed in the IDE, validating Government software requirements, providing recommendations for improvements, etc.

7.2.2.3.2. The Contractor shall configure the applications within the IDE.

7.2.2.3.3. The Contractor shall meet with system users to assess and recommend configuration changes.

7.2.2.3.4. The Contractor shall recommend opportunities and

methodologies to revise, replace, or reconfigure Government processes to better align with industry standards and emerging technologies.

7.2.2.3.5. The Contractor shall create workflows and coordination paths within IDE applications.

7.2.2.3.6. The Contractor shall ensure proper software CM and QA procedures are followed prior to implementation of changes, IAW MIL-HDBK-61.

7.2.2.3.7. The Contractor shall perform QA to ensure CM of applications moving from development and into the production environment.

7.2.2.3.8. The Contractor shall perform data updates, data migration, and data maintenance activities.

7.2.2.3.9. The Contractor shall perform bug fixes, patching, and security updates.

7.2.2.3.10. The Contractor shall test new or enhanced software functionality and releases/patches.

7.2.2.3.11. The Contractor shall test all developed configurations in a development environment and provide proof of concept to the Government before implementing into the production environment.

7.2.2.4. IDE Hosting

The Government intends to securely host the IDE on Government infrastructure, whether off-site or on-premises.

7.2.2.4.1. If Government hosting becomes impractical, the Contractor shall provide recommendations for secure hosting alternatives, including commercial and Contractor-provided options.

7.2.2.4.2. Any off-site hosting service shall be transferable to the Government at no additional cost (beyond reasonable ongoing commercial hosting and licensing costs), with appropriate usage rights for any future Contractor that supports the ICBM Organization.

7.2.2.4.3. Once the Government selects an alternative, the Contractor shall provide analysis and support necessary to transition hosting infrastructure.

7.2.2.4.4. The Contractor shall ensure the ICBM IDE is consistent and continuous through any transition.

7.2.2.5. IDE Management Transition

7.2.2.5.1. Upon expiration of this contract, the Contractor shall provide full data transfer and migration support to the incoming Contractor, including full transfer of all software used in the management of data (both commercial and non-commercial).

7.2.2.5.2. Any development of custom software and/or modification to commercial software done in support of managing Government data shall be transferred in full, with unlimited rights IAW applicable CDRLs and this contract’s Government Rights in Data and Software (GRIDS).

7.2.2.6. Service Desk

7.2.2.6.1. The Contractor shall provide a service desk in support of the

IDE.

7.2.2.6.2. The Contractor shall provide courteous, friendly, and professional customer service.

7.2.2.6.3. The Contractor shall translate customer needs into requirement recommendations.

7.2.2.6.4. The Contractor shall provide the following services through the service desk:

• User account management – process DoD Form 2875, System

Authorization Access Request

• Rights and permissions management

• User assistance - phone (toll free and local number), email, tickets during regular hours

• Rights and permissions management

• Advanced troubleshooting and problem resolution

• Receive and record customer requests and attempt issue resolution

• Review customer feedback surveys, and develop and provide recommendations of opportunities for continual improvement

• Other service desk tasks as applicable

7.2.2.6.5. The Contractor shall employ a Government-approved helpdesk ticketing and project management system to track status and provide task updates.

7.2.2.7. Documentation

7.2.2.7.1. The Contractor shall develop documentation and procedures associated with the running, support and maintenance of software and systems.

7.2.2.7.2. The Contractor shall document any software controls (e.g.

administrative, procedural, inherited, etc.) or requirements that affect system operation, maintenance, repair, or other support activities.

7.2.2.7.3. The Contractor shall document their processes for developing configurations to software applications and how they are to be flowed through from the development environment to the production environment.

7.2.2.7.4. The Contractor shall develop software configuration documents for software application configurations which are part of the IDE, such as:

• System Architecture and Deployment Diagram – high level diagram of system components

• Software Component Diagram – high level logical diagram of software components

• Additional configuration, scripts, templates, packages and programs

• Other documents as required

7.2.2.7.5. The Contractor shall develop and maintain user guides and training materials for how each of the configured software applications functions for the Government instance, and present training as needed. (CDRLs A052, A107)

7.2.2.7.6. The Contractor shall ensure that all Contractor-developed IDE documentation is in compliance with MIL-HNDK-61.

7.3. Cybersecurity

Cybersecurity Support Description The purpose of cybersecurity is the prevention of damage to, protection of, and restoration of computers, electronic communications systems and services, wired or wireless communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation. Cybersecurity applies to all DoD IT that receive, process, store, display, or transmit DoD information.

This effort provides cybersecurity engineering and assessment for WS acquisition and sustainment activities, as well as acquisition and sustainment of ICBM IT systems. This includes addressing National Defense Authorization Act (NDAA), Clinger-Cohen Act (CCA), and other cybersecurity requirements for ICBM programs, IAW applicable laws, policy, regulations, guidance.

7.3.1. Cybersecurity General Requirements

7.3.1.1. The Contractor shall provide cybersecurity engineering and assessment for

ICBM WS acquisition and sustainment activities, as well as acquisition and sustainment of ICBM IT systems.

7.3.1.2. This support shall include:

• Evaluation and analysis of capabilities and systems

• Strategic planning

• Problem analysis

• Identification of alternative solutions

• Providing recommendations

• Writing reports

• Obtaining and sustaining system accreditation

• Identifying cybersecurity requirements to be included in system and subsystem specifications, including appropriate verification methods

• Other support tasks as necessary

7.3.1.3. The Contractor shall provide cybersecurity support to ensure networthiness is maintained for all required software (on the AF Evaluated Product List) for the IDE.

7.3.1.4. The Contractor shall assist in the establishment of a task management process that includes configuration control of IT system artifacts.

7.3.1.5. The Contractor shall provide monthly Contractor’s Progress, Status and Management Reports. (CDRL A140)

7.3.2. ICBM Cybersecurity Strategy and Program

7.3.2.1. The Contractor shall support the Cybersecurity Office in the development, implementation, and maintenance of the ICBM Organization’s Cybersecurity Strategy and Program to support ongoing ICBM acquisition and sustainment efforts.

7.3.2.2. The Contractor shall develop standards, processes, guidance, Operating Instructions (OIs), etc. IAW established procedures and applicable regulations.

7.3.3. Cybersecurity Program/Acquisition Management

7.3.3.1. The Contractor shall implement AF cybersecurity policies and procedures as identified in AFI 17-130, Cybersecurity Program Management and applicable specialized cybersecurity publications (e.g. COMSEC, COMPUSEC, TEMPEST, etc.).

7.3.3.2. The Contractor shall ensure IT is acquired, documented, operated, used, maintained, and disposed of properly and IAW the applicable security Authorization and Accreditation (A&A) documentation as prescribed by

AFI 17-101.

7.3.3.3. The Contractor shall provide support (source data, analysis, etc.) for acquisition and sustainment of IT systems IAW DoD Instruction (DoDI) 5000.02T, Operation of the Defense Acquisition System and other applicable regulations.

7.3.3.4. The Contractor shall provide support (source data, analysis, etc.) for obtaining A&A for systems IAW DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), and other applicable regulations.

7.3.3.5. The Contractor shall provide cybersecurity Risk Management Framework (RMF) activities and events for incorporation into the Enterprise Integrated Master Schedule (EIMS).

7.3.3.6. The Contractor shall ensure proper CM procedures are followed IAW AFI 17-130 and AFI 17-101.

7.3.3.7. The Contractor shall report cybersecurity incidents or vulnerabilities.

(CDRLs A071, A142)

7.3.3.8. The Contractor shall initiate protective or corrective measures when a cybersecurity incident or vulnerability is discovered.

7.3.3.9. The Contractor shall implement and maintain required cybersecurity (e.g.

COMSEC, COMPUSEC, TEMPEST, etc.) countermeasures and compliance measures.

7.3.3.10. The Contractor shall initiate requests for temporary and permanent exceptions/deviations/waivers to cybersecurity requirements/criteria IAW AFI 17-130 and applicable specialized cybersecurity publications.

7.3.3.11. The Contractor shall assist with assessments conducted by the Cybersecurity Program Office.

7.3.3.12. Contractor Subject Matter Experts (SMEs) shall analyze data and provide recommendations for further action.

7.3.4. Cybersecurity Systems Engineering

7.3.4.1. The Contractor shall identify, manage, and verify cybersecurity requirements for acquisition and sustainment efforts.

7.3.4.2. The Contractor shall assess proposed cybersecurity strategies and programs, including validating security critical requirements and proposed controls, and ensuring traceability between security controls and requirements.

7.3.4.3. The Contractor shall verify implementation of applicable cybersecurity controls by using Systems Engineering (SE) technical processes such as stakeholder requirements definition, requirements analysis, architecture design, implementation, integration, verification, validation, etc.

7.3.4.4. The Contractor shall ensure cybersecurity risks are identified, managed, and documented as required by the RMF as part of the overall program risk management process.

7.3.4.5. The Contractor shall ensure that their cyber risk management activity is consistent with guidance provided by the Cybersecurity Program Office.

7.3.4.6. The Contractor shall ensure their cybersecurity risk management activity reexamines threats, exposure, and vulnerabilities, and assesses changes to system architecture and design.

7.3.4.7. The Contractor shall validate cybersecurity controls, assess verification results, and provide results to the Government.

7.3.4.8. The Contractor shall recommend changes to cybersecurity controls for acquisition programs as part of Systems Engineering Technical Reviews (SETRs).

7.3.4.9. The Contractor shall ensure that all program documentation complements the program’s Cybersecurity Strategy and System Security Plan (SSP).

7.3.4.10. The Contractor shall assist with integration of Test and Evaluation (T&E) of cybersecurity requirements into the overall T&E process, including component-level testing performed by suppliers.

7.3.4.11. The Contractor shall identify vulnerabilities to Critical Program Information (CPI) and mission-critical functions and components.

7.3.4.12. The Contractor shall assist with integration of cybersecurity into Systems Security Engineering (as part of SE), Program Protection, anti-tamper, and design processes.

7.3.4.13. The Contractor shall ensure cybersecurity portions of overall system design are included in SE and design documents, test plans, procedures, and reports.

7.3.4.14. The Contractor shall ensure training materials, technical manuals, and other technical data developed, address cybersecurity controls or requirements that affect system operation, maintenance, repair, or other support activities.

7.3.4.15. The Contractor shall ensure cybersecurity boundaries (e.g. crypto boundary, certification boundary, classification boundary, etc.) are clearly and consistently identified in program documents and drawings.

7.3.5. Professional Certifications and/or Licenses Required for Contractor Personnel

7.3.5.1. The Contractor’s cybersecurity workforce shall maintain compliance with the cybersecurity Contractor training and certification requirements in DoD Directive (DoDD) 8140.01, Cyberspace Workforce Management, and DoD 8570.01-M, Information Assurance Workforce Improvement Program, and meet the investigative level requirements established in Enclosure 3 of DoDI 8500.01, Cybersecurity.

7.3.5.2. The Contractor shall comply with all applicable computer and network access requirements and instructions (including DoDD 8140.01) for the access level(s) required to accomplish the tasks of this contract.

7.3.5.3. The Contractor shall act as Information System Security Managers (ISSMs) (see AFI 17-101).

7.3.5.3.1. ISSMs shall provide independent assessments as primary cybersecurity technical advisors to the Authorizing Official (AO) for AF IT.

7.3.5.4. The Contractor shall act as Information System Security Officers (ISSOs).

(See AFI 17-101).

7.3.5.4.1. ISSOs shall ensure the appropriate operational security posture is maintained for AF IT under their purview, including activities related to maintaining situational awareness and initiating actions to improve or restore cybersecurity posture.

7.3.5.5. The Contractor shall act as Information System Security Engineers (ISSEs). (See AFI 17-101).

7.3.5.5.1. ISSEs shall conduct Information System Security Engineering activities.

8.0 ICBM WARHEAD LEAD PROJECT OFFICE (LPO)

LPO Description The ICBM Warhead LPO manages AF nuclear ICBM warhead sustainment and acquisition to provide safe, reliable, and certified ICBM nuclear warheads for 400 combat capable nuclear missiles.

8.1. Requirements

8.1.1. The Contractor shall perform technical services related to System Engineering &

Integration (SE&I) as directed by the Government.

8.1.2. The Contractor shall support the Government in the preparation and review of ICBM warhead Military Characteristic (MC) documents, Stockpile to Target Sequence (STS) documents, and Joint Operating Agreements (JOAs).

8.1.3. The Contractor shall provide support to the LPO to identify, validate, verify, revise, and control warhead interface requirements.

8.1.4. The Contractor shall identify and perform system-level trade-off studies and analyses associated with requirements, designs, program schedules, and lifecycle costs.

8.1.5. The Contractor shall support the Government in identifying the need for and evaluating trade studies performed by LPO interagency partners and subcontractors.

8.1.6. The Contractor shall provide support for and participate as a member of appropriate ICBM Warhead Project Officer Group (POG) sub-groups and associated working groups such as:

• W78/W87-0 POG:

o Systems Engineering & Integration Sub-Group (SE&ISG) o Requirements Sub-Group (RSG) o Safety, Surety & Reliability Sub-Group (SS&RSG) o Interface Control Sub-Group (ICSG) o Joint Test Sub-Group (JTSG) o Maintenance & Logistics Sub-Group (MLSG)

• W87-1 POG:

o SE&ISG o RSG o Safety, Surety Reliability & Cybersecurity Sub-Group (SSR&CSG) o ICSG o Planning and Assessment Sub-Group (PASG) o MLSG

8.1.7. The Contractor shall support recurring POG meetings and Executive POG (EPOG) meetings (and prepare and deliver POG meeting notes, when needed), as well as ad hoc Interagency Planning meetings and Technical Exchange Meetings (TEMs) as required by the Government to execute the LPO mission. (CDRLs A002, A003, A004, A059-73)

8.1.8. The Contractor shall conduct Technical Peer Reviews on appropriate deliverables such as documents, trade studies, requirements, presentations, and any other product delivered or formally presented to or by the Government.

8.1.9. The Contractor shall participate in the identification, planning, conduct, and review of technical design reviews.

8.1.10. The Contractor shall prepare and deliver to the Government a monthly status report of Contractor activities and deliverables. (CDRL A026-1)

8.2. Specific Qualifications

8.2.1. Contractor personnel assigned to the LPO shall have knowledge and experience in:

• Maintaining currency with the Department of Energy (DoE) nuclear weapons lifecycle phases and the Phase 6.x process

• DoD system lifecycle phases and associated SE processes

9.0 FORCE DEVELOPMENT EVALUATION (FDE)

FDE Description This is support for AFGSC. Headquarters (HQ) AFGSC functions as an “organize, train, and equip” Command. As a “train and equip” Command, AFGSC is responsible for conducting the Mission Area Assessment process to evaluate the ICBM force’s ability to accomplish AF missions in specific Mission Areas.

HQ AFGSC is responsible for conducting the ICBM FDE program for ICBM WSs. The basic objectives of this program are to:

1) Establish accuracy and reliability planning factors under operationally-representative test conditions

2) Detect changes in WS accuracy and reliability

3) Identify areas for WS modification or improvement

4) Verify operational effectiveness and suitability of the current system and new acquisitions

This includes activities such as support for Operational Test Launches (OTLs) and equity in test launches other than OTLs, which permit performance assessments of operationally-representative ICBM components under operationally-representative test conditions. HQ AFGSC is also responsible for overseeing MAJCOM operational testing for ICBM acquisition programs.

9.1. Test and Operations Support:

9.1.1. The Contractor shall provide mission analysis support to assist in defining test missions to meet current test objectives, range sensor and range safety constraints.

9.1.2. The Contractor shall perform mission design including accessibility, flight safety analysis and key state vector and sequence of event data.

9.1.3. The Contractor shall prepare briefing materials and participate in planning meetings. (CDRLs A002, A003, A004, A059-73)

9.1.4. The Contractor shall, with input from Subsystem Contractors, provide a Prelaunch

Processing Report and a Quick-Look Flight Performance Report.

9.1.5. The Contractor shall support MK12A/MK21/MK21A Joint Test Working Group

Meetings, Joint Test Subgroup Meetings and other related joint National Nuclear Security Administration (NNSA)-AF meetings as requested by AFGSC.

9.1.6. The Contractor shall attend special Test Planning and Technical Interchange Meetings (TIMs).

9.1.7. The Contractor shall support and participate in Integrated Test Team (ITT) meetings, IPT meetings, applicable working group meetings, and other similar meetings.

9…