Attachment 6 - Campaign Analytic Support PWS V1.0.DOC

Attachment 1

FA5000‐XX-X-XXXX

Solicitation FA7014-23-R-0031 Contract FA7014-24-D-xxxx

PERFORMANCE WORK STATEMENT

FOR

CAMPAIGN ANALYSIS SUPPORT

AT

PENTAGON, ARLINGTON, VIRGINIA

24 AUGUST 2023

VERSION 1.0.4

Controlled by: AFDW/PK Distribution/Dissemination Controls: FEDCON AFTER AWARD POC: Shannon Weston (801-710-8856)

Contents

SECTION I: DESCRIPTION OF SERVICES

1.1 GENERAL

The mission of the Secretary Air Force Office of Studies and Analysis (SAF/SA) is to provide timely, credible, and innovative analyses in support of decisions by the Secretary and Undersecretary of the Air Force, the Chief and Vice Chief of Staff of the Air Force, and the Chief and Vice Chief of Space Operations. To carry out its mission, SAF/SA conducts mission and campaign level analyses to support force structure decisions; assess potential force employment options; and evaluate the contribution of various weapon systems to the outcome of key objectives in theater-level conflicts. These analyses demand accurate and timely representation of air, space, ground, maritime, and cyberspace domains and their relationship to actions by other services or coalition forces. To meet these analytic requirements, SAF/SA uses the Synthetic Theater Operations Research Model (STORM). STORM has been the United States Air Force’s simulation of record for campaign-level Air Force analysis for over a decade. Through continuous capability development, STORM has emerged as the campaign-level analysis model for the Joint Analysis community with over 100 users across 20 different service organizations and 4 international user groups.

1.2 SCOPE

The Contractor shall provide tools, equipment, personnel, and project supervision necessary to support the SAF/SA campaign analysis effort to inform senior leaders of the Department of Air Force. The Contractor shall provide technical, analytical, and subject matter expertise in running, calibrating, modifying, updating, and integrating STORM and its data to support SAF/SA analytic studies at various classification levels. The Contractor shall provide software engineering to maintain the STORM software and its simulation capabilities to represent theater-level military operations in a joint war fighting context. The Contractor shall provide required support and training to STORM user community.

1.3 BACKGROUND

To ensure that the SAF/SA continues to provide timely, credible, and innovative analyses to senior leaders of the Department of Air Force, the SAF/SA must maintain its capability to conduct campaign level analyses at various classification levels and modify STORM software and its simulation capabilities to accurately represent an ever-evolving joint warfighting environment. To meet these requirements, the Contractor shall provide tools, equipment, personnel, and project supervision necessary for Campaign Analysis Support, STORM Software Engineering Support, Analysis Toolkit Software Engineering Support, and User Community Support services.

SECTION II: TASK DESCRIPTION

2.1 GENERAL

2.1.1 OVERVIEW

SECTION II provides detailed task descriptions organized into five service categories: Campaign Analysis Support, STORM Software Engineering Support, Analysis Toolkit Software Engineering Support, User Community Support, and General Support. The section also contains a list of key personnel required for both on-site and off-site support. Those providing off-site support shall be at an off-site facility within approximately an hour response time to the Pentagon, Washington DC to ensure prompt response. The Contractor shall provide all tools, equipment, personnel, and project supervision required in connection with this Performance Work Statement (PWS).

2.1.2 GOVERNMENT COORDINATION REQUIREMENT

The tasks described in SECTION II require extensive coordination with SAF/SA and other Department of Defense (DoD) organizations. To ensure that the Government is fully informed on activities performed under this contract, the Contractor shall include at least one Government representative from the list below while coordinating with the Government organizations. At the request of the Government, the Contractor shall provide status updates on activities.

· STORM Contracting Officer’s Representative (COR): a government individual designated in writing by SAF/SA who “develop proper requirements and ensure during contract administration the Contractor meet the commitments of their contract.” (General Service Acquisition Manual (GSAM) 501.604 Contracting Officer’s Representative (COR))

· STORM Model Manager: a government individual designated by SAF/SA to act as the program manager for a model. The Model Manager is responsible for all technical aspects of the model and ensuring the PWS encompasses the requirements of SAF/SA and the User community.

· Study Lead: a government individual or contractor designated by SAF/SA leading an analytic study in support of SAF/SA Campaign Analysis and Sustainment effort.

2.1.3 SECURITY CLEARANCE REQUIREMENT

The tasks described in SECTION II may require personnel to access classified information. All campaign analysis support personnel assigned to PWS Section 2.2 tasks shall be able to obtain and retain a minimum of SECRET clearance. On-site campaign analysis support personnel assigned to PWS Sections 2.2 and 2.8.1 tasks shall be able to obtain and retain TOP SECRET (TS) security clearance with access to Sensitive Compartmented Information (SCI) and Program Specific information and shall be eligible to meet Special Access Required (SAR) requirements. Additional contractor positions requiring a TS/SCI and/or TS/SAR clearance shall be specified in the task order request. All on-site campaign analysis personnel with clearances shall be able to obtain and retain NATO SECRET and shall conform to all SAF/SA security policies. Off-site campaign analysis support personnel assigned to PWS Sections 2.2 and 2.8.1 tasks shall be able to obtain and retain SECRET clearance. Off-site software engineering and user support personnel assigned to PWS Sections 2.3, 2.4, and 2.5 tasks to obtain and retain SECRET clearance if required by the Government. The Contractor shall ensure that any International Traffic in Arms Regulations (ITAR) information is protected in accordance with Government rules and regulations related to protecting the ITAR information. The contractor shall adhere to DD Form 254, Contract Security Classification Specification, which shall be incorporated at time of award. The contractor is required to ensure that security clearances of personnel performing under this PWS are available to the SAF/SA security officer and/or to the supported organization’s security officer through the Defense Information System for Security (DISS). The SAF/SA Security Officer and the COR shall be identified as the Point of Contact on all Visit Requests.

2.1.4 SERVICE CONTINUITY REQUIREMENT

The tasks described in SECTION II may require maintaining a consistent level of performance during transition and throughout the contract’s period of performance. The Contractor shall ensure that personnel assigned to such tasks are able to perform without additional training and guidance from government personnel.

2.2 CAMPAIGN ANALYSIS SUPPORT

The Contractor shall provide technical, analytical, and subject matter expertise to support SAF/ SA study efforts. The scope of this service may include developing concepts of operations and mission scenario for credible to DAF analyses; integrating joint warfare involving air, space, maritime, ground, and cyberspace domains into joint campaign scenarios; assisting with functional capability analyses. The Contractor shall ensure that on-site personnel assigned to Sections 2.2 tasks are able to obtain and retain TS security clearance with access to SCI and Program Specific information and shall be eligible to meet SAR requirements.

It is essential for the SAF/SA to maintain its ability to provide timely, credible, and innovative analyses to senior leaders of the Department of Air Force during transition and throughout the contract’s period of performance. To meet this requirement, the Contractor shall ensure that personnel assigned to Sections 2.2 tasks are able to provide campaign analysis support using STORM without additional training and guidance from government personnel.

The Contractor shall act in coordination with SAF/SA study teams to accomplish the tasks outlined in the following subsections, which are required to successfully support campaign analysis. The Model Manager will maintain correspondence with relevant study leads to manage allocation of work and ensure daily task requirements are being met. The Model Manager will inform the COR of any issues. The Contractor shall document activities performed under this service category in the Monthly Progress Report (CDRL A007).

2.2.1 ANALYTIC STUDY PLANNING

The Contractor, in conjunction with the Model Manager, shall provide support to investigate and implement appropriate methodologies for analytic studies. The Contractor shall assist study teams to prepare study plans, develop methodologies and model enhancements, maintain data configuration control, and gather analytic data. The Model Manager will maintain correspondence with relevant study leads to manage allocation of work and ensure task requirements are being met.

2.2.2 MODEL DATABASE DEVELOPMENT SUPPORT

The Contractor shall provide support to develop, modify, update, debug, and maintain STORM databases. The task may include data transfer and calibration of data to/from the SAF/SA suite of models, such as Brawler, the Weapons Effects Analysis and Probability Software (WEAPS), and the Advanced Framework for Simulation, Integration and Modeling (AFSIM). The Contractor shall provide support to develop and administer the repository of supporting model databases as required by the Government. The Contractor shall work with managers of external models to ensure that relevant data from those models are in a format compatible with STORM. When native compatibility from external models is not possible, the Contractor shall adapt the format of the data to ensure its usability in STORM.

2.2.3 SCENARIO DATABASE DEVELOPMENT SUPPORT

The Contractor shall provide on-site/off-site support to develop, modify, update, debug, and maintain STORM scenario databases. The task may include supporting Concept of Operations (CONOPS) development, integrating Intelligence Community (IC) assessments, and modeling service Tactics, Techniques, and Procedures (TTP) and joint operations. The Contractor shall integrate inputs from other government organizations and verify that the database is operational for analyses. The Contractor shall validate that the database accurately represents the scenario and associated CONOPS. The Contractor shall maintain the repository of STORM scenario databases at multiple classification levels. The Contractor shall assist the Government and provide to facilitate coordination with other government organizations.

2.2.4 STORM ANALYSIS SUPPORT

The Contractor shall provide on-site/off-site support to execute the STORM software to produce model runs accurately portraying the given scenario(s). The task may include providing pre-production, production, post-production model runs and conducting analytic post processing to support studies as required by the Government. The Contractor shall make software modifications to source code, scripts and databases as required to complete studies. This task differs from the task described in Section 2.3.6 in that the scope of these changes shall be limited to elimination of bugs and errors or modifications to existing functionality, required to support on-going studies and analyses. These maintenance and modification actions shall be documented in a format agreed to by the Government and shall be placed under configuration control as candidates for inclusion into the baseline.

2.2.5 STUDY AND ANALYSIS REPORTING SUPPORT

The Contractor shall provide on-site/off-site support to post-process model output data utilizing existing model functionality, data reduction programs, scripts, database queries, and analyses tools either developed by the Contractor or provided by the Government. The Contractor shall assist the production of output reports and/or briefings to address study/analyses findings in a format requested by the Government.

2.2.6 SOFTWARE AND DATABASE INSTALLATION SUPPORT

The Contractor shall provide on-site/off-site support to install individualized STORM code updates and databases when available. The Contractor shall ensure that the modeling environment at SAF/SA is configured with the most relevant model source codes and databases. At the request of the Government, the Contractor shall provide similar installation support to additional organizations.

2.2.7 CONFLICT SIMULATION SUPPORT

The Contractor shall provide on-site/off-site support to assist the conflict simulation community through scenario and database development, analytic results briefing, and definition and improvement of processes involved in executing conflict simulation. The Contractor shall perform model setup and operation during rehearsal and actual war games supported by SAF/SA. At the request of the Government, the Contractor shall travel in support of war games. Travel shall include conflict simulation planning meetings, rehearsals, conflict simulation activities, and post-simulation analysis briefings. All travel shall be done in accordance with Section 6.11.

2.3 STORM SOFTWARE ENGINEERING SUPPORT

The Government will continue to enhance STORM capabilities by identifying, proposing, and evaluating improvements to the methodologies, model algorithms and code, databases, and graphical user interfaces. The Contractor shall provide software engineering support to modify, test, and maintain STORM software. The scope of this service may include implementing code modifications to STORM in accordance with design concepts approved by the STORM Configuration Control Board (CCB) consisting of DoD representatives; reviewing code modifications to assess their impact on operations, database requirements, and run-time environments of the model; and ensuring compliance to the latest DoD cybersecurity policy and guidance. The Contractor shall provide a Help Desk representative, Chief Model Architect and Chief Software Engineer as supporting members of the CCB. Although the STORM software engineering support is primarily performed at the off-site Contractor location, the Contractor shall provide on-site support at the request of the Government. The Contractor shall ensure that off-site personnel assigned to Sections 2.3 tasks are able to obtain and retain required SECRET security clearance if required by the Government.

2.3.1 SOFTWARE DEVELOPMENT

The Contractor shall accomplish necessary model code/software modifications for supporting SAF/SA required analysis or for integrating with other Agency models. The Contractor shall coordinate all code/software changes with the appropriate SAF/SA Model Manager and CCB prior to making any change. Once the CCB approves a concept, the Government will award design and implementation to the Contractor under this task. The Contractor shall provide support to accomplish necessary code/software modification for other Agency models federated or associated with assigned models, including possible integration with other Common Analytic Simulation Architecture (CASA) based models. The Contractor shall provide software engineering for the development and maintenance of computer applications to support analysis using these models. The Contractor will document code modifications, technical analysis, database development, and administrative activities in support of SAF/SA required analysis in the Monthly Progress Report (CDRL A007). The Contractor shall turn all code changes over to the configuration management process for incorporation into the next baseline version.

2.3.2 STORM MODIFICATION PROPOSAL DEVELOPMENT

The Contractor shall assist the Government to define enhancement requirements. The Contractor shall provide a written report, known as “White Paper,” that includes a recommended course of action, draft design, and estimate for required effort. Once approved by the Government, the Contractor shall coordinate with the Government to create a modification proposal for submission to the CCB. The Contractor is not required to develop a modification proposal for an effort initiated outside of SAF/SA or outside the scope of this PWS as determined by the Government. The Contractor may be asked to review outside agency STORM proposals for viability and feasibility.

2.3.3 STORM MODIFICATION PROPOSAL REVIEW

The Contractor shall support the Government to review all proposed model modifications and assess their impact on the underlying assumptions, operations, database requirements, source code, and run-time environments of the model. The Contractor may recommend approvals or changes to the proposed designs back to the Government. The Contractor shall provide services described in this section throughout the iterative review process of model modifications.

2.3.4 STORM MODIFICATIONS REQUEST DOCUMENTATION

The Contractor shall maintain a database of all software modification requests that include who required the change, background information on the change and the status of any action taken to implement or discard the change. The Contractor shall provide the database to the Model Manager upon as requested by the Government.

2.3.5 STORM MODIFICATION DESIGN DEVELOPMENT

It is at the discretion of the Government to endorse and fund contract modifications approved by the CCB, however there is no requirement that a resulting design document will be funded upon receipt. Upon authorization from SAF/SA, the Contractor shall research modifications and provide a software specification document to the Government. This document shall contain the following: a) a detailed design of the methodology, data structures, and algorithms to be implemented; b) a test plan outlining proposed implementation approach, test cases, and test plan; and c) an assessment of the impact the software modifications will have on the underlying assumptions, operations, database requirements and sources, and run-time environment of STORM. The Contractor shall submit the completed software specification document to the Government for approval before starting the implementation of the modification. After design review, the Contractor shall update the design and the software specification document to incorporate recommendations made by the Government. The Contractor shall resubmit revised design for review until the design and software specification documents are approved for implementation by the Government. The Contractor shall submit software specification documents containing requirements or design methods diverging from the CCB approved modification proposal to the CCB as an addendum to the original proposal, at no additional cost to the government.

2.3.6 STORM MODIFICATION IMPLEMENTATION

The Contractor shall implement code modifications according to the software specification document, integrate them into a baseline configuration-controlled version of STORM, and test the version. The Contractor shall integrate all approved software and data changes, including those developed outside of this contract, into the baseline version. The Contractor shall ensure that all code modifications are approved by the CCB prior to implementation. The Contractor shall release the STORM updates either as interim updates or as version releases by following a versioning schema agreed upon by the Government.

2.3.7 STORM SOFTWARE SECURITY REVIEW

The Contractor shall apply industry accepted software engineering practices and tool(s) to identify STORM software vulnerabilities and implement measures to mitigate them, including code modifications and/or operating procedure changes. The Contractor shall ensure that the mitigation measures are adequate to complete an applicable checklist, such as Security Technical Implementation Guides (STIGs) checklist, in support of a Risk Management Framework (RMF) process. The Contractor shall generate a written report(s) describing software vulnerability findings, implemented mitigation measures, and recommendation(s) on addressing any unresolved software vulnerabilities.

2.3.8 STORM RISK MANAGEMENT IMPLEMENTATION

The Contractor shall establish a risk management process in accordance with the Air Force Instruction (AFI) 17-101 Risk Management Framework (RMF) for Air Force Information Technology (IT) for compliance with the Department of Defense Instruction (DoDI) 8510.01 Risk Management Framework for DoD Systems. The Contractor shall apply industry accepted practices and their knowledge in the STORM software development and operation to implement a RMF process for STORM. The Contractor shall provide artifacts and documentation required to ensure compliance to the RMF process. The required items include, but are not limited to, checklist report(s) importable to a cybersecurity management system, such as the Enterprise Mission Assurance Support Service (eMASS); report(s) generated as part of requirements in Section 2.3.7; and updates to installation guide(s) and user manual(s).

2.3.9 STORM INTERIM CODE RELEASES

The Contractor shall release interim updates necessary to support current analytic efforts of the STORM community. The updates may include code modification(s) that add new functionality to the model or resolve bugs found in the current supported baseline versions. Updates are either directly requested by the Government or required for resolving issues reported to the Help Desk (Section 2.5.1, 2.5.3, and 2.5.4). To resolve immediate problems in timely manner, the Contractor may provide a simplified version of model documentation and design specifications. The Contractor shall ensure that interim versions are compliant to the RMF process and report to the Model Manager if the compliance cannot be accomplished before the release. To minimize disruption to the efforts of the overall community, the Contractor shall ensure that all interim updates affecting the STORM functionality must be explicitly employed by the user. If the interim updates cannot be enabled without impacting the baseline STORM functionality, the Contractor shall receive an approval from the Model Manager before releasing them. The Contractor shall deliver the interim code release to the Government by a physical disc or by a secured electronic file transfer system on a date specified by the Government.

2.3.10 STORM VERSION RELEASES

The Contractor shall coordinate with the Model Manager to determine the dates for interim and version releases to the STORM user community. The releases include, but are not limited to, modifications impacting core functionality of the model. The Contractor shall deliver an alpha version to the Model Manager no later than 60 days prior to the determined release date. The Contractor shall conduct a test on the alpha version, resolve discrepancies, and implement corrections for integration into a beta version. The Contractor shall deliver the beta version no less than 30 days prior to the determined version release date. The Contractor shall conduct a final test on the beta version, identify remaining bugs, and make corrections prior to final version release. For each STORM version release, the Contractor shall ensure that the release is compliant to the established RMF process, revise documentation to account for changes, and place all final code and documentation changes under configuration control. Documentation may include, but is not limited to, an Analyst’s Manual, Programmer’s Manual, RMF Compliance Report, and User’s Guide. The Contractor shall ensure that a release package contains the software version with an automated installation process and updated documentation. The Contractor shall deliver the release package to the Government on a physical disc on the schedule agreed upon by the Government.

2.3.11 STORM SOFTWARE VERSION REPOSITORY

The Contractor shall maintain a configuration-controlled version of software and documentation for all version releases. This repository shall include a configuration control log that details all changes made in either interim or version releases and be presented to the Government upon request.

2.3.12 STORM CODE DEVELOPMENT TESTING

Solicitation FA7014-23-R-0031 Contract FA7014-24-D-xxxx

At the request of the Government, the Contractor shall perform on/off-site testing of interim STORM versions on SAF/SA collateral databases prior to release. The tests shall examine the interim STORM versions against a robust set of databases to test different areas of the model, isolate hard breaks in the code, and identify possible errors in the database. Upon testing completion, the Contractor shall include a final report describing all discovered breaks and responsive fixes to be included during the alpha, beta, or final code release in the Final Version Release Software (CDRL A003).

2.4 ANALYSIS TOOLKIT SOFTWARE ENGINEERING SUPPORT

The Contractor shall provide software engineering support to develop, modify, and maintain campaign analysis toolkits in support of SAF/SA analyses. The scope of this service may include, but is not limited to, updating setup scripts to configure the latest STORM version’s runtime environment, developing pre-processing toolkits to refine STORM inputs, and post-processing toolkits to evaluate output data. Although the analysis toolkit software engineering support is primarily performed at the off-site Contractor location, the Contractor shall provide on-site support at the request of the Government. The Contractor shall ensure that off-site personnel assigned to Sections 2.4 tasks are able to obtain and retain required SECRET security clearance if required by the Government.

2.4.1 ANALYSIS TOOLKIT MODIFICATION PROPOSAL DEVELOPMENT

The Contractor shall assist the Government to define requirements for upgrading analysis toolkits. The Contractor shall provide a written report, known as “White Paper,” that includes a recommended course of action, draft design, and estimate for required effort. Once approved by the Government, the Contractor shall coordinate with the Government to create a modification proposal for submission to the CCB. The Contractor is not required to develop a modification proposal for an effort initiated outside of SAF/SA or outside the scope of this PWS as determined by the Government. However, the Contractor may be asked to review outside agency STORM proposals for viability and feasibility, during the CCB review of the submitted proposal.

2.4.2 ANALYSIS TOOLKIT PROPOSALS REVIEW

The Contractor shall support the Government to review all proposed analysis toolkit modifications and assess their impact on the underlying assumptions, operations, database requirements, source code, and run-time environments of STORM. The Contractor shall recommend approvals or changes to the proposed designs back to the Government. The Contractor shall provide services described in this section throughout the iterative review process of model modifications.

2.4.3 ANALYSIS TOOLKIT MODIFICATIONS REQUEST DOCUMENTATION

The Contractor shall maintain a database of all analysis toolkit modification requests that include who required the change, background information on the change and the status of any action taken to implement or discard the change. The Contractor shall provide the database to the Model Manager upon as requested by the Government.

2.4.4 ANALYSIS TOOLKIT DESIGN DEVELOPMENT

Upon authorization from SAF/SA, the Contractor shall research modifications and provide a software specification document to the Government. This document shall contain the following: a) a detailed design of the methodology, data structures, and algorithms to be implemented; b) a test plan outlining proposed implementation approach, test cases, and test plan; c) an assessment of the impact of software modifications will have on the underlying assumptions, operations, database requirements and sources, and run-time environment of STORM. The Contractor shall submit the completed software specification document to the Government for approval before starting the implementation of the modification. After design review, the Contractor shall update the design and the software specification document to incorporate recommendations made by the Government. The Contractor shall resubmit revised design for review until the design and software specification documents are approved for implementation by the Government. The Contractor shall submit provide software specification documents containing requirements or design methods diverging from the CCB approved modification proposal to the CCB as an addendum to the original proposal at no additional cost to the government.

2.4.5 ANALYSIS TOOLKIT MODIFICATION IMPLEMENTATION

The Contractor shall implement code modifications according to the software specification document, integrate them into a baseline configuration-controlled version of analysis toolkit, and test the version. The Contractor shall include all approved software and data changes, including those developed outside of this contract, into the baseline version. The Contractor shall ensure that all code modifications are approved by the CCB prior to implementation. The Contractor shall release updated analysis toolkit either as interim updates or as a part of STORM version releases by following a versioning schema agreed upon by the Government.

2.4.6 ANALYSIS TOOLKIT SECURITY REVIEW

If an analysis toolkit requires independent security review outside of PWS Section 2.3.7, the Contractor shall apply industry accepted software engineering practice(s) and tool(s) to identify the analysis toolkit software vulnerabilities and implement measures, including code modifications and/or operating procedure changes to mitigate vulnerabilities. The Contractor shall ensure that the mitigation measures are adequate to complete an applicable checklist, such as Security Technical Implementation Guides (STIGs) checklist, in support of a Risk Management Framework (RMF) process. The Contractor shall generate a written report(s) describing software vulnerability findings; mitigation measures implemented; and recommendations on addressing any unresolved software vulnerability.

2.4.7 ANALYSIS TOOLKIT RISK MANAGEMENT IMPLEMENTATION

If an analysis toolkit requires an independent RMF process outside of STORM RMF process scope, the Contractor shall apply industry accepted practices and their knowledge in the analysis toolkit development and operation to implement a RMF process. The Contractor shall establish the process in accordance with the Air Force Instruction (AFI) 17-101 Risk Management Framework (RMF) for Air Force Information Technology (IT) for compliance with the Department of Defense Instruction (DoDI) 8510.01 Risk Management Framework for DoD Systems. The Contractor shall provide artifacts and documentation required to ensure compliance to the RMF process. The required items include, but are not limited to, checklist report(s) importable to a cybersecurity management system, such as the Enterprise Mission Assurance Support Service (eMASS); report(s) generated as part of requirements in PWS Section 2.4.6; and updates to installation guide(s) and user manual(s).

2.4.8 ANALYSIS TOOLKIT INTERIM CODE RELEASES

The Contractor shall release interim updates necessary to support current analytic efforts of the STORM community. The updates include, but are not limited to, code modifications that add new functionality to an analytic toolkit or resolve bugs found in the current supported baseline versions. Updates are either directly requested by the Government or required for resolving issues reported to the Help Desk (PWS Sections 2.5.2, 2.5.3, and 2.5.4). To resolve immediate problems in timely manner, the Contractor may provide a simplified version of model documentation and design specifications. If the analytic toolkit requires an independent RMF process outside of STORM RMF process scope, the Contractor shall ensure that interim versions are compliant to the RMF process and report to the Model Manager if the compliance cannot be accomplished before the release. To minimize disruption to the efforts of the overall community, the Contractor shall ensure that all interim updates affecting the toolkit functionality must be explicitly employed by the user. If the interim updates cannot be enabled without impacting the baseline toolkit functionality, the Contractor shall receive an approval from the Model Manager before releasing them. The Contractor shall deliver an interim code release to the Government by a physical disc or by a secured electronic file transfer system on a date specified by the Government.

2.4.9 ANALYSIS TOOLKIT VERSION RELEASES

The Contractor shall coordinate with the Model Manager to determine the interim and version release dates of the analysis toolkit. The releases include, but are not limited to, modifications impacting core functionality of the toolkit. Unless it is waived by the Government, the Contractor shall deliver an alpha version to the Model Manager no later than 60 days prior to the determined release date. The Contractor shall conduct a test on the alpha version, resolve discrepancies, and implement corrections for integration into a beta version. Unless it is waived by the Government, the Contractor shall deliver the beta version no less than 30 days prior to the determined version release date. The Contractor shall conduct a test to identify remaining bugs and make corrections prior to final version release of the toolkit. For each toolkit version release, if the analytic toolkit requires an independent RMF process outside of STORM RMF process scope, the Contractor shall ensure that the release is compliant to the established RMF process, revise documentation to account for changes, and place all final code and documentation changes under configuration control. Documentation may include, but is not limited to, an Analyst’s Manual, Programmer’s Manual, RMF Compliance Report, and User’s Guide. The Contractor shall ensure that a release package contains the software version with an automated installation process and updated documentation. The Contractor shall deliver the release package to the Government by a physical disc or by a secured electronic file transfer system on the schedule agreed upon by the Government.

2.4.10 ANALYSIS TOOLKIT SOFTWARE VERSION REPOSITORY

The Contractor shall maintain a configuration-controlled version of software and documentation for all version releases. This repository shall include a configuration control log that details all changes made in either interim or version releases and be presented to the Government upon request.

2.4.11 ANALYSIS TOOLKIT CODE DEVELOPMENT TESTING

At the request of the Government, the Contractor shall perform on/off-site testing of an interim version of an analysis toolkit on SAF/SA collateral databases prior to release. The tests shall apply the interim version of the toolkit against a robust set of databases to apply different areas of the STORM model, isolate hard breaks in the code, and identify possible errors in the toolkit. Upon testing completion, the Contractor shall provide a final report describing all discovered breaks and fixes to be included in the alpha, beta, or final code release as requested the Government.

2.4.12 ADDITIONAL ON-SITE ANALYSIS TOOLKIT DEVELOPMENT SUPPORT

At the request of the Government, the Contractor shall provide additional on-site analysis toolkit development support to improve data inputs to STORM and utilize and evaluate outputs of STORM in support of SAF/SA studies. If executed, the Contractor shall document activities performed in the Monthly Progress Report.

2.4.13 ADDITIONAL OFF-SITE ANALYSIS TOOLKIT DEVELOPMENT SUPPORT

At the request and guidance of the Government, the Contractor shall provide analysis toolkit development support. Whereas the STORM support of analysis under requirements in PWS Section 2.2 entails the contribution to Government-led efforts, the development support under this requirement shall be conducted under Government supervision off-site and reported to the Government in a format and at a periodicity agreed to by the Government. The Contractor shall provide to the Government all tools and utilities developed during the development effort. If executed, the Contractor shall document activities performed in the Monthly Progress Report.

2.5 USER COMMUNITY SUPPORT

The Contractor shall provide technical and analytical support for the STORM software suite to the STORM user community. The STORM software suite includes the STORM software and associated Analysis Toolkits. The scope of this service may include such tasks as providing Help Desk support; organizing and conducting User Group Meeting; and developing instructional materials and hosting on-site STORM introductory training sessions. The user community support is primarily performed at the off-site Contractor location, the Contractor shall provide on-site support at the request of the Government. The Contractor shall ensure that off-site personnel assigned to Sections 2.5 tasks are able to obtain and retain required SECRET security clearance if required by the Government.

2.5.1 STORM SOFTWARE SUITE HELP DESK ADMINISTRATION

The Contractor shall provide a Help Desk service that performs as the primary point of contact for STORM users to submit requests for resolving technical issues with the STORM software suite. The Contractor shall provide technical support functions to the STORM users approved by the Government. The manning of the Help Desk service is as required and shall not be a full-time effort.

2.5.2 OFF-SITE HELP DESK SUPPORT

The Contractor shall provide an off-site Help Desk for the STORM user community, to identify, isolate, and correct problems with the STORM software suite. The user experiencing a problem will be expected to identify the problem, characterize the domain of the problem (e.g., model version, data used, operating system, etc.) and to provide this information to the Contractor-staffed Help Desk. The Contractor is not required to maintain a full-time answering service; however, the Help Desk shall be reachable by telephone or email during normal duty hours (0830 – 1630 EST). If required, the Contractor will work with the user to duplicate the issue on the required classification systems per classification guidance. The Contractor shall maintain a log documenting trouble calls (tickets) received in consecutive order to include the following: tracking number, the date trouble ticket was opened, originator and their contact information, the nature of the problem, the solution provided (if any), the status of any open trouble calls, date closed, and follow-up summary of any/all actions taken to close. Open tickets over 30 days old will be highlighted in the Monthly Progress Report (CDRL A007) and will include all appropriate information as to why no resolution has been made and the expected resolution date. The Contractor shall include a list of all monthly trouble call logs and the status of each call log in the Monthly Progress Report (CDRL A007).

2.5.3 STORM USER GROUP WEBSITE

The Contractor shall maintain a STORM User Group webpage that facilitates community support. The website shall serve as a repository for Release Candidates and Code Updates and provide points of contact for various user support elements. The user support elements may include information requests, bug reports, Help Desk support, unfunded modification descriptions, model enhancement white papers, and Frequently Asked Questions (FAQ) section. The Contractor shall implement an access control to the website to limit any user not approved by the Government from accessing information on the website. The Contractor shall ensure that any ITAR information is protected in accordance with Government rules and regulations related to protecting the ITAR information.

2.5.4 STORM SOFTWARE SUITE BUG REPORT

The Contractor shall investigate a software bug reported by a STORM user and determine an approach or methodology for resolution. With an approval from the Model Manager, the Contractor shall implement a minor software modification or database change to fix the bug related to the model, data, or analysis and graphics tools. The software modification implemented under the scope of the Help Desk is aimed to resolve the reported bug quickly and does not require stringent design and documentation standards. The Contractor shall document all modification and maintenance actions and provide to the Model Manager in the Monthly Status Report (CDRL A007). The Contractor shall include the software modifications into the next STORM and Analysis Toolkit baseline releases at the discretion of the Model Manager.

2.5.5 USER GROUP MEETING ORGANIZATION AND HOSTING

The Contractor shall organize and administer User Group meetings on a schedule approved by the COR. The location and agenda shall be provided and agreed to by the Government, no later than 90 days prior to the meeting. The Contractor shall announce the meeting to all members of the User Group no less than 60 days prior to the event. The Contractor shall provide a meeting plan to the Model Manager with provisional logistics and agendas 90 days prior to the meeting and thereafter on a biweekly basis. The Contractor shall incorporate all feedback from the Model Manager into the meeting plan until all details are finalized. The Contractor shall record and distribute minutes and actions associated with the annual User Group meeting to all members of the User Group, no later than 30 days after the meeting. The meeting minutes will also be included in the Monthly Progress Report (CDRL A007) for that period.

2.5.6 VERSION DISTRIBUTION

The Contractor shall provide appropriately labeled copies of all configuration-controlled STORM software versions on physical discs to the Model Manager for dissemination to the STORM user community. The COR shall inform the Contractor of the number of copies needed two weeks prior to the version release date. All copies should be provided to the Model Manager within 1 week of the version release.

2.5.7 TRAINING DEVELOPMENT AND INSTRUCTION REQUIREMENTS

The Contractor shall develop a training course covering topics related to STORM release version and applicable Analysis Toolkit release version. The training course topics will be coordinated with the Model Manager prior to the development of course materials. The Contractor shall review and update the course modules as necessary to incorporate any new analysis tools, methodologies or hardware/software system changes adopted by SAF/SA. The Contractor shall provide one copy of all training material as the baseline for reference to the Government facility. The Contractor shall provide the training location at no additional cost to the Government.

2.5.8 COURSE PLANNING AND SCHEDULING

The Contractor shall organize all required training to include the following: arranging a location, disseminating course information, setting up all necessary equipment and printing training materials for each expected student. The Contractor shall coordinate dates for courses with the Model Manager and the Contractor no less than 60 days in advance. The Model Manager will provide the course roster to the Contractor no later than 2 weeks prior to the course. The Contractor shall provide the Model Manager and COR a course plan for review and approval 60 days prior to presenting any course and associated materials. The course plan shall include a content outline highlighting changes to previous course content as well as logistical details for the upcoming training. The first monthly report shall include the initial schedule, any subsequent modifications, and a post training report which will be included in the Monthly Status Report.

2.5.9 INTRODUCTORY COURSE DEVELOPMENT

The Contractor shall develop, modify, and maintain an introductory STORM training course with course materials.