DRAFT STORM Performance Work Statement.docx

Attachment 1

FA5000‐XX-X-XXXX

CUI FA7014‐XX-X-XXXX

PERFORMANCE WORK STATEMENT

FOR

THE SYNTHETIC THEATER OPERATIONS RESEARCH MODEL (STORM)

AT

PENTAGON, ARLINGTON, VIRGINIA

05 JANUARY 2023

DRAFT VERSION 6.0

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

Contents

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General. The mission of the Air Force Office of Studies and Analysis (SAF/SA) is to conduct 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 uses modeling and simulation to support force structure decisions, analyze potential force employment options and evaluate the contribution of various weapon systems to the outcome of key objectives in theater-level conflicts. For analyses at this level of war, SAF/SA utilizes various tools to assess the air, space and cyberspace campaign’s impact on the overall joint campaign. These analyses demand accurate and timely representation of the many dimensions of air, space and cyberspace warfare and their relationship to actions by other services or coalition forces. To examine the military potential of proposed doctrinal changes or evolving weapon systems, SAF/SA uses flexible, state-of-the-art theater-level models.

1.1.1 Scope. The Synthetic Theater Operations Research Model (STORM) is the Air Force’s campaign model solution, integrating air, space, sea, land and cyberspace domains. STORM is a dynamic, complex analytic simulation representing theater-scale military operations in a joint war fighting context. It includes the following components:

· A graphical front end for model execution, control, and reporting (Study tool)

· Input tools (Orbit Tool, TBMTool, ATCALPhaseITool, A2SPKTool)

· Execution tools (multirun scripts, STORM code and algorithms, and integration with supported batch scheduler software)

· Output tools (MapTool, GraphTool, ReportTool)

· Relational database for input, execution and output

· Distribution package of select open-source software application and tools

· Documentation (Analysts, Programmers, Users manuals, Appendices, change notices and training course materials)

1.2 Background. All references to STORM apply to the STORM analytic simulation and components described above. SAF/SA developed, owns and controls access to and licensing of STORM and is responsible for its configuration management. SAF/SA intends to manage and maintain STORM under this Performance Work Statement (PWS). In addition, SAF/SA must maintain and sustain the core capability to run, calibrate, modify, update and integrate data and results amongst the entirety of its modeling and simulation toolkit in order to effectively perform studies and analyses of Air Force capabilities. As a result, maintenance and development of tools or user interfaces to support these models are also supported under this PWS.

SAF/SA also maintains a suite of modeling tools, which are provided by other DoD agencies or other SAF/SA contract vehicles, to support ongoing analysis. The SAF/SA modeling suite includes but is not limited to such models as Brawler, Combat Forces Assessment Model (CFAM), Sensor Platform Allocation Analysis Tool (SPAAT), Capability Based Logistics Planner (CBLP), Sortie Generation Rate Model (SGRM), Enhanced Surface-to-Air Simulation (ESAMS), Weapons Effects Analysis & Probability Software (WEAPS), Advanced Framework for Simulation, Integration and Modeling (AFSIM), Analysis of Mobility Platform (AMP) and Airbase Damage - Assessment and Resiliency Model (AD-ARM).

SECTION II

2.0 Task Descriptions

STORM is designed to support in-depth analysis of the campaign-level contributions of air, space, sea, land and cyberspace forces. As a result, STORM is also dependent upon an extensive collection of databases tailored for a combatant’s combat capability as well as force deployment, employment and geographic region characteristics. As STORM undergoes continuous updates in support of analytic studies, all components of STORM (databases, input, output and reporting tools, etc.) require review, modification and updating to ensure its viability as an analysis tool.

2.0.1 Key Personnel

2.0.1.1 The key personnel for the Contractor shall be located in the National Capital Region (NCR).

The key personnel are required to maintain an off-site facility within approximately an hour response time to the Pentagon, Washington DC to facilitate visits by the COR/Model Manager and AF Senior Leaders located in the Pentagon.

2.0.1.2 The Contractor shall develop, integrate, test, document, deliver and support all deliverables to meet the requirements as described in subsections: 2.2, 2.4 and 4.0.

2.0.1.3 The Government requires that the Contractor commits personnel that will meet the requirements of this contract for a minimum of the base year. The Contractor may prefer personnel that have other campaign model expertise (analytic and/or development) with an explanation of why this campaign modeling experience should be accepted as equivalent experience. Any deviation from the criteria listed below shall solely be determined by the Government.

2.0.1.3.1 Principal Analyst (paragraph 2.2 and 2.4)

2.0.1.3.2 Program Manager (paragraph 2.2, 2.3, and 2.4) (Not to exceed 376 hours annually)

2.0.1.3.3 Principal Configuration Architect (paragraph 2.3, and 2.4)

2.0.1.3.4 Help Desk (Junior Analyst/Developer/Software Engineer (paragraph 2.5, 2.6 and 2.7)

• Responsible for assisting the STORM user community debugging STORM code and database errors

2.1 Task 1: Technical Requirements for STORM

2.1.1 The contractor shall provide all remaining tools, equipment, personnel, and supervision necessary to support the SAF/SA Campaign Analysis Support and Sustainment effort in providing campaign level analysis, software maintenance, software development, configuration management, and user community support to Headquarters Air Force.

2.1.1.1 The contractor shall receive funding for Other Direct Costs (ODC) like licenses Maintenance and Warranties for both hardware and software, etc., that are required support this contract effort. The contractor shall support this effort as a study member, as required, under the study lead’s leadership or as members of development/enhancement teams under the SAF/SA model manager. They must be capable of providing all of the services specified in the task described.

2.1.2 The Contractor shall provide internal program management, at an off-site location, to ensure all requirements under this contract are accomplished to the Government’s satisfaction. The Contractor’s program manager shall interface with both the Model Manager (MM) and the Contracting Officer Representative (COR) regularly, at a frequency determined by the MM and COR, to ensure understanding, and compliance with government’s intent of the active requirements and/or to establish future requirements under this contract. SAF/SA supports a wide range of mission areas- from developing large mathematical models and methodologies to determining aircraft attrition-during a campaign-level effort. These requirements range in scope from short suspense tasking (24 hours – 1 week) to studies dealing with critical force management issues lasting 6-12 months or longer. These tasks require an extensive knowledge of the Department of the Air Force organizational structure, functional responsibilities, mission areas, and joint campaign analysis and data sources and will fall into the task descriptions that follow. Analysis support may be requested, on an as needed basis, to assist in the conduct of studies. SAF/SA may provide support under this PWS to all users of STORM products. Contractors who provide analysis support will be required to be proficient in one or more of the SAF/SA modeling tools and its associated application to the analysis task at hand. The contractor shall perform all analysis support and general support tasks at the Government’s facility, unless otherwise informed by the COR that work shall be conducted at the contractor’s facility.

2.1.3 The Contractor shall enhance and maintain STORM and support the community of STORM users, based upon the guidance of the SAF/SA Model Manager. This will require a steady-state ongoing effort throughout the period of performance. The level of effort may be increased as unscheduled improvements to STORM are required and funded. The Contractor personnel who support the model maintenance and user community support tasks shall be experts in the use and algorithms of STORM. Both the model maintenance and user community support tasks shall be accomplished off-site at the Contractor’s facility.

2.2 Task 2: Campaign Analysis Support

The Contractor shall provide technical, analytical and subject matter expertise to support SAF/ SA study efforts. This expertise may include, but is not limited to, such tasks as applying subject matter expertise and operational experience to concept of operations and mission scenario development in order to add credibility to DAF analyses; assist in developing integrated joint warfare, air, space, and cyberspace campaign scenarios; assist with functional capability analyses.

2.2.1 Core Campaign Analysis Support

The Contractor will act in concert with SAF/SA study teams to accomplish the tasks outlined in the following subsections. They represent the core tasks required to successfully deliver Campaign Analysis Support. 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 relate any issues to the COR. The Contractor will document activities performed under 2.2.1.1, 2.2.1.2, 2.2.1.3 and 2.2.1.4 in support of SAF/SA analysis in the Monthly Progress Report (Deliverables: Contract Data Requirement List (CDRL) 1 Deliverable 007 STORM Monthly Report).

2.2.1.1 Onsite Study/Analysis Planning

The Contractor, in conjunction with the Model Manager, will investigate and agree to implement appropriate methodologies to support studies and analyses. The Contractor will help with such tasks as study plan development, methodology and model enhancement and/or development, data configuration control, research and data gathering, as required, to support studies. The Model Manager will maintain correspondence with relevant study leads to manage allocation of work and ensure task requirements are being met.

2.2.1.2 Scenario Database Development Support

The Contractor shall develop, modify, update, debug, and maintain model databases. This database support includes data transfer and calibration of data to/from the SAF/SA suite of models, including but not limited to Brawler, the Weapons Effects Analysis and Probability Software (WEAPS) and the Enhanced Surface to Air Missile Simulation (ESAMS), and other modeling tools, as required. The Contractor shall provide support to develop and administer the repository of supporting model databases as required by the Government. Additionally, 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.1.3 STORM Support of Analysis

The Contractor shall provide operations systems support to studies by using STORM to produce model runs accurately portraying the given scenario(s) -- provide pre-production, production, post-production model runs and analytic post processing, i.e., run models as required 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 task 2.2.1.4 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.1.4 Study and Analysis Reporting Support

The Contractor shall 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 support the production of output reports and/or briefings to address study/analyses findings in a format agreed to by the Government.

2.2.1.5 On-Site Campaign Analysis Support

At the request of the Government, the Contractor shall be prepared to provide additional on-site analytic support similar in scope to the requirements in Sections 2.2.1.1, 2.2.1.2, 2.2.1.3, and 2.2.1.4 above. If executed, the Contractor will document activities performed in support of 2.2.1.4 in the Monthly Progress Report (Deliverables: Contract Data Requirement List (CDRL) 1 Deliverable 007 STORM Monthly Report).

2.2.1.6 Off-Site Campaign Analysis Support

At the request and guidance of the COR, the Contractor shall be prepared to provide additional off-site analysis and support. Whereas the STORM support of analysis under requirement and 2.2.1 entails the contribution to Government-led efforts, the analysis 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 COR. The Contractor shall provide to the Government all databases developed during the analysis. The Contractor shall produce output reports and/or briefings in a format agreed to by the COR to address study/analyses findings. If executed, the Contractor will document activities performed in support of 2.2.1.6 in the Monthly Progress Report (Deliverables: Contract Data Requirement List (CDRL) 1 Deliverable 007 STORM Monthly Report).

2.2.1.7 Software and Database Installation Support

As necessary, the Contractor shall support the installation of individualized STORM code updates and databases when they become available to ensure the modeling environment at SAF/SA is configured with the most relevant model source code and databases. At the request of SAF/SA, the Contractor will provide similar installation support to additional organizations within the NCR. If executed, the Contractor will document activities performed in support of 2.2.1.7 in the Monthly Progress Report (Deliverables: Contract Data Requirement List (CDRL) 1 Deliverable 007 STORM Monthly Report).

2.2.1.8 Conflict Simulation Support

At the request of the Government, the Contractor shall support 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. The Contractor may be required to travel in support of war games. Travel shall include conflict simulation planning meetings, rehearsals, conflict simulation activities, and post- simulation analysis briefings. All travel will be done in accordance with Section 6.9.1 of the PWS. If executed, the Contractor will document activities performed in support of 2.2.1.8 in the Monthly Progress Report (Deliverables: Contract Data Requirement List (CDRL) 1 Deliverable 007 STORM Monthly Report).

2.2.1.9 On-Site STORM Campaign Analysis Toolkit Development Support

At the request of the Government, the Contractor shall be prepared to provide additional on-site analytic support to develop tools to improve data inputs to STORM and utilize and evaluate outputs of STORM in support of SAF/SA Studies and Analyses. If executed, the Contractor will document activities performed in support of 2.2.1.9 in the Monthly Progress Report (Deliverables: Contract Data Requirement List (CDRL) 1 Deliverable 007 STORM Monthly Report).

2.2.1.10 Off-Site STORM Campaign Analysis Toolkit Development Support

At the request and guidance of the Government, the Contractor shall be prepared to provide additional off-site analyses and support. Whereas the STORM support of analysis under requirement 2.2.1.9 entails the contribution to Government-led efforts, the analysis 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 in the course of the development effort. If executed, the Contractor will document activities performed in support of 2.2.1.10 in the Monthly Progress Report (Deliverables: Contract Data Requirement List (CDRL) 1 Deliverable 007 STORM Monthly Report).

2.3 Task 3: STORM Campaign Analysis Toolkit

The contractor will support in accordance with Section 2.0, tools and user interfaces to support the Government use of STORM which may be created and maintained under this PWS. STORM Campaign Analysis Toolkit development will help members of the STORM analytic community refine and improve inputs to STORM and evaluate outputs from STORM through a suite of tools.

2.4 Task 4: STORM Maintenance and Modifications

2.4.1 The Government is responsible for the configuration of its models and will chair the model’s Configuration Control Board (CCB). The CCB works directly with users proposing model enhancements to develop design documents that meet requirements while ensuring model integrity. The Contractor shall support the Government’s configuration control and verification and validation processes. The Contractor shall provide a Help Desk representative, Chief Model Architect and Chief Software Engineer as supporting members of the CCB and support the Model Manager in maintaining a registry of all code/software changes (both approved and disapproved) as part of the CCB.

2.4.2 The Contractor shall accomplish necessary model code/software modifications required to support SAF/SA required analysis or integration with other Agency models. The Contractor shall be required to coordinate all code/software changes with the appropriate SAF/SA Model Manager and CCB before any changes are made. 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 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 (Deliverables: Contract Data Requirement List (CDRL) 1 Deliverable 007 STORM Monthly Report). The Contractor shall turn all code changes over to the configuration management process for incorporation into the next baseline version.

2.4.3 Modification Proposal Development

The Government will continually seek to enhance STORM capabilities by identifying, proposing and evaluating improvements to the methodologies, model algorithms and code, databases and graphical user interfaces. The Contractor and Government shall work in concert to thoroughly define enhancement requirements. The Contractor will provide to the Government recommended courses of action to include draft designs and an estimate of the level of required effort entailed, aka “White Papers”. If the decision is made by the Government to proceed with the suggested course of action, the Contractor will work with the Government to create a modification proposal for submission to the CCB. The Contractor is not required to develop modification proposals for efforts 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, prior to it being accepted as a required task under the configuration control board.

2.4.4 Software Model Modification Reviews

The Contractor shall support Government reviews of all proposed model modifications to include an assessment of the impact these changes will have on the underlying assumptions, operations, database requirements, source code, and run-time environments of the model. The Contractor shall recommend approval to implement the proposed design or propose design changes back to the Government. Modification proposals may evolve through the requirements definition and design processes, and thus may be submitted to the CCB multiple times for approval.

2.4.5 Document Requests for Software Modifications

The Contractor shall maintain a software change request database that provides, at a minimum, who required the change, background information on the change and the status of any action taken to implement or discard the change and provide the database to the Model Manager.

2.4.6 Design Development

It is at the discretion of the Government to endorse and fund under these 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 such 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 the software changes 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 Contractor hours are expended on the modification. Subsequent to design review, the Contractor shall modify the design and the software specification document to incorporate recommendations made by the Government. The revised design shall be re- submitted for review and the iterative review process will continue until the design and software specification document are approved for implementation by the Government. Software Specification Documents containing requirements or design methods diverging from the CCB approved modification proposal shall be submitted to the CCB as an addendum to the original proposal, at no additional costs to the government.

2.4.7 Software Modification Implementation

The Contractor shall, upon approval of the software specification document, code the software, integrate it into the baseline and test the implementation. The Contractor shall incorporate all approved software and data changes, including those developed outside of this contract, into a baseline configuration-controlled version of STORM. Responsive bug fixes (described in Section 2.6.3) are not required to undergo the CCB approval process. All other modifications must have been previously approved by the CCB before being incorporated into baseline STORM. STORM updates will be released either as interim updates or as version releases. Interim updates and version releases must follow a versioning schema agreed upon by the Government.

2.4.8 Interim Release Code

Interim updates, previously known as “Release Candidates”, shall be released by the Contractor as necessary to support current analytic efforts of the STORM community. These updates will include code changes that add immediate functionality to the model or resolve bugs found in the current supported baseline versions. Changes may be required directly from the Government or be required to resolve issues identified by the Help Desk (Section 2.6). Responsive fixes are geared toward resolving immediate problems in an expedient manner. As a result, less stringent model documentation and design specifications are acceptable for this type of modification. All documentation shall be provided to the Model Manager upon release of the interim update. In order to minimize disruption to the efforts of the overall community, the Contractor shall ensure all modifications affect STORM functionality only if explicitly employed by the user. Cases where immediate changes cannot be accomplished without impacting baseline STORM functionality require Model Manager approval before being released. The Government may request interim updates to be delivered on specified dates but will generally not set the schedule for delivery. The Contractor shall deliver interim code releases to the Government either physically on CDs or DVDs or by other established means of electronic data transfer.

2.4.9 Version Releases

Version releases often include, but are not limited to, modifications impacting core functionality of the model. Dates for which baseline versions of STORM are completed and released to the community will be coordinated with the Model Manager. No later than 60 days prior to the determined release date, the Contractor shall deliver an alpha version to the Model Manager. Testing shall be done in the alpha version, discrepancies shall be resolved, and corrections shall be implemented into a beta version to be delivered to the Model Manager no less than 30 days prior to the determined version release date. A final phase of testing shall be performed on the beta version to identify remaining bugs. Corrections shall be implemented and tested prior to final version release. For each software version release, the Contractor shall 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, and User’s Guide. The Contractor shall deliver integrated software version releases with an automated installation process and updated documentation on CDs or DVDs on the schedule agreed upon by the Government.

2.4.10 Maintain 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 Code Development Testing

At the request of the government, prior to the release of interim STORM code, the Contractor shall perform off-site testing of interim code on SAF/SA collateral databases. These tests will examine the STORM code against robust databases that stress different areas of the model to isolate hard breaks in the code and identify possible errors in the database. Upon testing completion, the Contractor shall provide a final report describing all discovered breaks and responsive fixes to be included with the Alpha, Beta or Final code release, as applicable.

2.5 Task 5: User Community Support

2.5.1 SAF/SA shall be the sole authority responsible for defining the User Group membership roster, and subsequently determining each user’s specific eligibility for STORM support. SAF/SA shall provide the approved User Group roster to the Contractor when changes occur and provide an updated roster annually, even if no changes have occurred. Upon receipt, the Contractor shall use the roster to validate support requests, ensuring that only authorized members are supported. Each individual request for support received from non-approved sources shall be reported to the government Model Manager as soon as possible.

2.5.2 STORM Campaign Analysis Toolkit Modification Proposal Development

The Government will continually seek to enhance STORM capabilities within the Campaign Analysis Toolkit by identifying, proposing and evaluating improvements to the methodologies, model algorithms and code, databases and graphical user interfaces. The Contractor and Government shall work in concert to thoroughly define enhancement requirements. The Contractor will provide to the Government recommended courses of action to include draft designs and an estimate of the level of required effort entailed, aka “White Papers”. If the decision is made by the Government to proceed with the suggested course of action, the Contractor will work with the Government to create a modification proposal for submission to the CCB. The Contractor is not required to develop modification proposals for efforts initiated outside of SAF/SA or outside the scope of this PWS as determined by the Government. However, the Contractor shall review outside agency proposals for viability and feasibility as a required task under configuration control.

2.5.3 Campaign Analysis Toolkit Review of Modification Proposals

The Contractor shall support Government reviews of all proposed model modifications to include an assessment of the impact these changes will have on the underlying assumptions, operations, database requirements, source code, and run-time environments of the model. The Contractor shall either recommend approval to implement the proposed design or propose design changes back to the Government. Modification proposals may evolve through the requirements definition and design processes, and thus may be submitted to the CCB multiple times for approval.

2.5.4 Document Requests for STORM Campaign Analysis Toolkit Software Modifications

The Contractor shall maintain a software change request database that provides, at a minimum, who required the change, background information on the change and the status of any action taken to implement or discard the change and provide the database to the Model Manager who will maintain it.

2.5.5 STORM Campaign Analysis Toolkit Design Development

It is at the discretion of the Government to endorse and fund under this 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 such 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 the software changes will have on the underlying assumptions, operations, database requirements and sources, and run-time environment of the STORM Campaign Analysis Toolkit. The Contractor will submit the completed software specification document to the Government for approval before Contractor hours are expended on the modification. Subsequent to design review, the Contractor shall modify the design and the software specification document to incorporate recommendations made by the Government. The revised design shall be re-submitted for review and the iterative review process will continue until the design and software specification document are approved for implementation by the Government. Software Specification Documents containing requirements or design methods diverging from the CCB approved modification proposal shall be submitted to the CCB as an addendum to the original proposal.

2.5.6 STORM Campaign Analysis Toolkit Software Modification Implementation

The Contractor shall, upon approval of the software specification document, code the software, integrate it into the baseline and test the implementation. The Contractor shall incorporate all approved software and data changes, including those developed outside of this contract, into a baseline configuration-controlled version of STORM. Responsive bug fixes (described in Section 2.6.3) are not required to undergo the CCB approval process. All other modifications must have been previously approved by the CCB before being incorporated into baseline STORM. STORM updates will be released either as interim updates or as version releases. Interim updates and version releases must follow a versioning schema agreed upon by the Government.

2.5.7 STORM Campaign Analysis Toolkit Interim Release Code

Interim updates, previously known as “Release Candidates”, shall be released by the Contractor as necessary to support current analytic efforts of the STORM community. These updates will include code changes that add immediate functionality to the model or resolve bugs found in the current supported baseline versions. Changes may be required directly from the Government or be required to resolve issues identified by the Help Desk, Section 2.6.4. Responsive fixes are geared toward resolving immediate problems in an expedient manner. As a result, less stringent model documentation and design specifications are acceptable for this type of modification. All documentation shall be provided to the Model Manager upon release of the interim update. In order to minimize disruption to the efforts of the overall community, the Contractor shall ensure all modifications effect STORM functionality only if explicitly employed by the user. Cases where immediate changes cannot be accomplished without impacting baseline STORM functionality require Model Manager approval before being released. The Government may request interim updates to be delivered on specified dates but will generally not set the schedule for delivery to the Government. The Contractor shall deliver interim code releases to the Government either physically on CDs or DVDs or by other established means of electronic data transfer.

2.5.8 STORM Campaign Analysis Toolkit Version Releases

Version releases often include, but are not limited to, modifications impacting core functionality of the model. Dates for which baseline versions of STORM are completed and released to the community will be coordinated with the Model Manager. No later than 60 days prior to the determined release date, the Contractor shall deliver an alpha version to the Model Manager. Testing shall be done in the alpha version, discrepancies shall be resolved, and corrections shall be implemented into a beta version to be delivered to the Model Manager no less than 30 days prior to the determined version release date. A final phase of testing shall be performed on the beta version to identify remaining bugs. Corrections shall be implemented and tested prior to final version release. For each software version release, the Contractor shall 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, and User’s Guide. The Contractor shall deliver integrated software version releases with an automated installation process and updated documentation on CDs or DVDs with the agreed upon schedule. (Deliverables: Contract Data Requirement List (CDRL) 1 Deliverable 001 STORM Campaign Alpha Developmental Release, CDRL 2 Deliverable 002 STORM Campaign Analysis Toolkit Beta Developmental Release, and CDRL 3 Deliverable 003 STORM Analysis Toolkit Final Version Release.)

2.5.9 Maintain STORM Campaign 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.5.10 STORM Campaign Analysis Toolkit Code Development Testing

At the request of the government, prior to the release of interim STORM Campaign Analysis Toolkit code, the Contractor shall perform off-site testing of interim code on SAF/SA collateral databases. These tests will examine the STORM Campaign Analysis Toolkit code against robust databases that stress different areas of the model in an effort to isolate hard breaks in the code and identify possible errors in the database. Upon testing completion, the Contractor shall provide a final report describing all discovered breaks and responsive fixes to be included with the Toolkit Alpha, Beta or Final code release, as applicable.

2.6 Task 6: Help Desk Requirements & Administration

2.6.1 The Contractor’s STORM Help Desk shall serve as the first point of contact for members of the User Group with technical issues involving the model. The Contractor shall provide technical support functions to the Government’s approved users of STORM. The Government’s maximum expected level of effort for this task is less than a full man year. The manning of the Help Desk is as required and shall not be a full-time effort.

2.6.2 The Contractor shall provide an off-site Help Desk for the STORM user community, to identify, isolate, and correct problems with the model. 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 hrs). 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 current 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 (Deliverables: Contract Data Requirement List (CDRL) 1 Deliverable 007 STORM Monthly Report) 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 (Deliverables: Contract Data Requirement List (CDRL) 1 Deliverable 007 STORM Monthly Report), due on the 5th business day of the month, to the Contracting Officer Technical Representative (COR).

2.6.3 STORM Campaign Analysis Toolkit Help Desk Administration

The Contractor’s STORM Campaign Analysis Toolkit Help Desk shall serve as the first point of contact for members of the STORM Campaign Analysis Toolkit Users Group with technical issues involving the tools developed under Section 2.3. The Contractor shall provide technical support functions to the Government’s approved users of STORM. The Governments maximum expected level of effort for this task is less than a man year. The manning of the Help Desk is as required and shall not be a full-time effort.

2.6.4 Help Desk Process

The Contractor shall provide an off-site Help Desk for the STORM Campaign Analysis Toolkit user community, to identify, isolate, and correct problems with the tool, in question. 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. 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 current 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 (Deliverables: Contract Data Requirement List (CDRL) 1 Deliverable 007 STORM Monthly Report) and will include all appropriate information as to why no resolution has been made and the expected resolution date. The Contractor will submit monthly trouble call logs in the Monthly Progress Report (Deliverables: Contract Data Requirement List (CDRL) 1 Deliverable 007 STORM Monthly Report) to the Contracting Officer Technical Representative (COR) due by the 5th business day of each month.

2.6.5 Responsive Modifications to STORM

The Contractor shall investigate the problems and determine an approach or methodology for resolution. With the agreement of the Model Manager, the Contractor will make/direct minor software or database changes to correct immediate problems related to the model, data, or analysis and graphics tools. The scope of Help Desk software changes shall be geared toward getting the user through the immediate problem in an expedient manner. As such, these modifications may not be permanent in nature and have less stringent design and documentation standards. These maintenance and modification actions shall be documented and provided to the Model Manager in the Monthly Status Report. Modifications will be implemented into the next model baseline at the discretion of the Model Manager.

2.6.6 Software Installation Support

As necessary, and at the request of the Government, the Contractor shall be prepared to provide installation support of all new software modifications within the NCR. Additionally, the Contractor shall provide the necessary technical guidance to support the installation of any additional software tools or utilities that might be required for on-site debugging, such as gprof and Valgrind. Gprof is a performance analysis tool used in STORM to discover the program's behavior as it executes and is used to assess which sections of the code to optimize. Valgrind is a utility within STORM’s toolkit that performs memory integrity tests and diagnoses various memory related errors.

2.7 Task 7: Users Group Management and Administration

2.7.1 Organize and Conduct User Group Meeting

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 (Deliverables: Contract Data Requirement List (CDRL) 1 Deliverable 007 STORM Monthly Report) for that period to the COR.

2.7.2 Facilitate Distribution of Version Releases

The Contractor shall provide appropriately labeled copies of all configuration-controlled STORM software versions on CDs or DVDs to the Model Manager for dissemination. 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.7.3 User Group Website

The Contractor shall maintain a User Group webpage that facilitates community support. The website will serve as a repository for Release Candidates and Code Updates. Furthermore, the website will provide points of contact for various activities: information requests, bug reports, Help Desk support, unfunded modification descriptions, model enhancement white papers, Frequently Asked Questions (FAQ) Section, etc. Access controls should be used to limit indiscriminate surfing by the public on the Contractor’s server and appropriately protect ITAR info.

2.8 Task 8: Training Development and Instruction Requirements

The Contractor must develop or modify all courses required under this PWS and be prepared to develop those required as optional requirements. All topics to be covered in any training shall be coordinated with the Model Manager prior development. 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 advanced training material as the baseline for reference in the Government facility. The Contractor shall provide the training location at no additional cost to the Government.

2.8.1 Introductory Course Development

The Contractor shall develop, modify and maintain an introductory STORM training course with course materials. The course shall consist of training on the various aspects of the model to include the following: how to run the model; STORM methodologies, capabilities, assumptions and limitations; required input data format and content; understanding the output and how to control it, and the utilization of associated STORM Tools. The Contractor shall ensure the course and corresponding materials include adequate hands-on training to give the new student a good understanding of fundamental model usage. The Contractor shall deliver updated course materials to the Government either physically on CDs or DVDs or by other established means of electronic data transfer.

2.8.2 Advanced Course Development

The Contractor shall develop, modify and maintain an advanced STORM training course with course materials for experienced users. The course shall include advanced topic modules that can be combined to form a course tailored to the specific needs and backgrounds of the attendees. The modules should include discussions and demonstration of STORM unique modeling and analysis techniques as well as presentation of some of the more obscure and less understood STORM options and switches. The Contractor shall deliver updated course materials to the Government either physically on CDs or DVDs or by other established means of electronic data transfer.

2.8.3 Course Planning and Scheduling

Dates for courses will be coordinated between the Model Manager and the Contractor no less than 60 days in advance. The Model Manager will establish the course roster and provide it to the Contractor no later than 2 weeks prior to the course. 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 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.8.4 Conduct Introductory Training

The Contractor shall present introductory training as a seminar course lasting five days with up to 15 students in attendance twice per contract year.

2.8.5 Conduct Advanced Training

Th…