Attachment 1 - Software Sustainmment 20 September 2023.pdf

PERFORMANCE WORK STATEMENT

RAPID AIRFIELD DAMAGE ASSESSMENT SYSTEM (RADAS):

SOFTWARE SUSTAIMENT

Contract Number:

FA805123C00XX

Air Force Civil Engineer Center

20 September 2023 i

Table of Contents

1. Introduction

2. Background

3. Qualifications

4. Description of Services

5. Contract Data Requirements List (CDRLs)

6. Terms and Conditions

APPENDIX A SOFTWARE SUSTAINMENT

APPENDIX B SOFTWARE SUSTAINMENT – WORKLOAD ESTIMATES

Amendment 03 - Summary of Changes

All Performance Work Statement updates associated with amendment 03 are highlighted below. Most updates are administrative in nature with the exception of the addition of CDRL A004 Travel and the Services Summary Section 6.

1. Introduction. This document defines the effort associated with the sustainment, maintenance, and upgrade of government owned software supporting Civil Engineer’s expeditionary engineering efforts. It includes programming actions, creating and maintaining documentation to support accreditation and training, and conducting on-site training.

2. Background.

2.1. The Air Force Civil Engineer Center Readiness Directorate, Expeditionary Engineering

Division (AFCEC/CXX) provides optimized deployed force structure plans, relevant training products, current publications, and modern equipment to ensure Air Force expeditionary engineers possess the core competencies and capabilities to execute global contingency missions. Several software applications have been developed to execute, manage, and train the various aspects of AFCEC/CXX. The following applications are currently fielded and will be maintained by the terms of this performance work statement:

• Airfield Damage Repair (ADR) Client

• Command and Control (C2) Simulator/Virtual Sand Table (VST)

• GeoExPT ADR Synchronization (GAS)

• GeoExPT Mobile

• Geospatial Expeditionary Planning Tool (GeoExPT)

• Installation Recovery After Attack (IRAA)

• IRAA Mobile

2.2. The Expeditionary Engineering Division of AFCEC (AFCEC/CXX) and Explosive Ordnance Disposal Division (AFCEC/CXD) are the primary sources of expert guidance for functional requirements, issues, and concerns for the applications/software covered by this performance work statement. CXD/CXX determines the functional requirements, fielding, and sustainment of ADR supporting technologies. They also determine the manpower and training requirements to operationally field and sustain their respective technologies.

2.3. AFCEC maintains a robust Research, Development, Test and Evaluation (RDT&E) program.

This program will yield recommendations for application updates and new applications.

During the life of this contract, hardware and software may be updated and/or replaced. The Contractor will be provided adequate notice (up to at least six months) prior to the requirement to support any of these changes or new software packages requiring sustainment.

3. Qualifications.

3.1. Contractor shall have personnel with experience related civil engineering geospatial and enhanced visualization.

3.2. Contractor personnel shall have knowledge of the Airfield Damage Repair (ADR) business process. This includes an intimate knowledge of the following documents:

• AFI 32-2001, Fire Emergency Services (FES) Program

• AFMAN 32-3001, Explosive Ordnance Disposal (EOD) Program

• AFMAN 32-1007, Readiness and Emergency Management Flight Operations

• DAFMAN 91-201, Explosives Safety Standards

• AFPAM 10-219, v1, Contingency and Disaster Planning

• AFPAM 10-219, v2, CE Contingency and Response Recovery Procedures

• AFPAM 10-219, v3, CE Contingency and Response Recovery Procedures

• AFPAM 10-219, v4, Airfield Damage Repair Operations

• AFTTP 3-4, Airman’s Manual

• AFTTP 3-32.11, Airfield Damage Assessment After Attack

• AFTTP 3-32.12, Minimum Airfield Operating Surface (MAOS) Selection and Repair

Quality Criteria (RQC)

• AFTTP 3-32.13, Airfield Marking and Striping After Major Attack

• AFTTP 3-32.14, Alternate Installation Sequence for Emergency Airfield Lighting System after Major Attack

• AFTTP 3-32.15, Rapid Setback Installation of Mobile Arresting Gear System

• Draft ADR Tactics, Techniques, and Procedures (TTPs)

• NFPA 1, Fire Code, Current Edition

• NFPA 412, Standard for Evaluating Aircraft Rescue and Fire-Fighting Foam Equipment, Current Edition

• NFPA 472, Standard for Competence of Responders to Hazardous Materials/Weapons of

Mass Destruction Incidents, Current Edition

• UFC 3-270-07, O&M, Airfield Damage Repair

3.3. The following personnel are identified as Key Personnel. Below are the minimum educational and experience requirements.

• Principal Software Engineer. The engineer develops software solutions by studying information needs; conferring with users; studying systems flow, data usage, and work processes; investigating problem areas; following the software development lifecycle. The qualifications are:

o B.S. degree in Computer Science or similar technical degree or five (5) years of related experience/training.

o Must be familiar with the programming languages most often used are C#, C, C++, and

Java.

o Proficient with the development software and Microsoft Office Suite.

• Senior Software Engineer. The engineer develops software solutions by studying information needs; conferring with users; studying systems flow, data usage, and work processes; investigating problem areas; following the software development lifecycle. The qualifications are:

o Bachelor's Degree from four-year college or university and five (5) years of related experience/training.

o Current certificates, licenses and registrations: (Scrum.org) PSD 1, PSM I(Scrum

Alliance) CSP, CSD(SAFe) SDP, ST, ASE(Microsoft) MTA, MCP, MCSA, MCSD o Must be proficient with programming languages (C#, C, C++, and Java) o Must be familiar with the programming languages most often used are C#, C, C++, and

Java.

• Program Manager. The Program Manager directs and coordinates activities of one or more departments, such as engineering, operations, or sales and aids executives in formulating and administering organization policies personally or through subordinate managers. The qualifications are:

o Bachelor's Degree (BA) from four-year college or university and five (5) years of related experience and/or training, or equivalent combination of education and experience.

o Project Management Professional (PMP) o Must be familiar with Accounting Software, Contract Management Systems, Development Software, Microsoft Office Suite, and Project Management Software

• Project Manager. The Project Manager is responsible for the successful initiation, planning, design, execution, monitoring, controlling, and closure of a project. The qualifications are:

o Bachelor's Degree (BA) from four-year college or university, or five (5) years of related experience and/or training, or equivalent combination of education and experience.

o Recommended computer skills: Development Software; Microsoft Office Suite.

• Test Engineer. The test engineer designs test suites and understands usability issues.

Responsible for conducting testing, analyze results and submit observations to the development team. Interact with clients to better understand product requirements or in case the design requires any kind of modifications.

o Bachelor's Degree from four-year college or university, or five (5) of related experience and/or training, or equivalent combination of education and experience.

o Recommend certificates, licenses and registrations recommended: CTFL-BA, CTAL-

TAE, CTAL-ST

o Recommend computer skills required: Development Software; Microsoft Office Suite

4. Description of Services.

4.1. Management.

4.1.1 The Contractor shall utilize an agile software development process similar to the SCRUM method. This provides an iterative and incremental path enabling more interaction between the development staff and the Government between defined software release candidates.

4.1.2 The Contractor shall actively use, Application Lifecycle Management (ALM) tools for software development to provide the following capabilities:

• Software configuration management database to maintain source code and configuration management.

• Software requirements management database to document the system requirements and change requests.

• Software test case management database to document test cases, defects, and issues.

• Provide access to requirements and defect tracking management systems, via Internet, to the Government Project Manager as required.

• The Contractor shall track all software development tasks as user requests for future development, a defect, or a bug. Defects and bugs shall further be listed with the severity (low, minor, major, or critical) and priority (low, medium, high, immediate).

4.1.3 The Contractor shall evaluate upgrades/changes to related Application programming interfaces (APIs), Software Development Kits (SDKs), Commercial- off-the-Shelf (COTS)/Government-off-the-Shelf (GOTS) software, and software licenses supporting the software covered by the PWS (CDRL A001).

4.1.4 The Contractor shall, throughout the life of the contract, review the supporting applications for functionality, versioning, and applicability to AFCEC/CXX requirements. The current supporting software are:

• Autodesk AutoCAD Civil 3D

• Autodesk AutoCAD Map 3D

• Android Team Awareness Kit (ATAK)

• Microsoft Office

• MS SQLite

• MS SQL Server

• Aircraft Control

• Unity

• Windows Server.

4.1.5 The Contractor shall provide support for four Program Management Review (PMR) meeting per year; hosted at their facility. The topics include status, progress, performance, funding, schedule, personnel, security, assumptions, risks and other pertinent data. The Contractor shall provide meeting agenda notification no later than seven (7) calendar days prior to the scheduled meeting. The Contractor shall provide meeting minutes/notes no later than seven (7) calendar days after the meeting (CDRL A001).

4.2. Technical Data. The contractor shall produce and maintain documentation to support all supported software. Documents include,:

4.2.1 Software Design Document (SDD). The Contractor shall create and maintain SDDs to support all software maintenance efforts. The SDD is used to describe the software architecture and shall include the purpose of the application, the design considerations and constraints, the system design, and the data structures (CDRL A003 and CDRL A001).

4.2.2 Software Requirements Specification (SRS). The Contractor shall create and maintain SRSs to support all software maintenance efforts. The SRS is used to describe the functional and non-functional requirement as the user interacts with the application. The SRS shall also be utilized to produce use cases for testing protocols (CDRL A001).

4.2.3 Department of Defense Architecture Framework (DoDAF). The Contractor shall provide applicable Department of Defense Architecture Framework (DoDAF) documents. DoDAFs provide visualization infrastructure for specific stakeholders concerns through viewpoints organized by various views. These views are artifacts for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through tabular, structural, behavioral, ontological, pictorial, temporal, graphical, probabilistic, or alternative conceptual means (CDRL A001).

4.2.4 Interface Control Documents (ICDs). The Contractor shall provide ICDs for all supported software. The ICDs shall document both interfaces with the software specifically listed in this PWS and other software routinely utilized by AFCEC/CXXM such as the Joint Construction Management System (JCMS) (CDRL A001).

4.2.5 Risk Management Framework (RMF). The Contractor shall support the development of RMF documents to support Certification and Accreditation (C&A) activities. This includes support for establishing Authorities to Operate (ATO), Authorities to Connect (ATC), and inclusion on the AF Evaluated/Approved Software (AF E/APL) (CDRL A001).

4.2.6 Software license agreements. All software licensing shall be between the vendor and

AFCEC/CXX (CDRL A002).

4.2.7 User Manuals. The Contractor shall develop and maintain user manuals for support software. The manuals shall include, software overview, minimum hardware recommendations, installation procedures, descriptions of all tools and dialog boxes, common troubleshooting procedures. The User Manuals can be embedded within the software or a sperate standalone document, it shall not be solely accessible via an internet connection. All user Manuals shall be key word searchable (CDRL A001).

4.2.8 Training Products. The Contractor shall develop training materials to include, Points of Instruction (POIs), lesson plans, PowerPoint slideshows, workbooks, checklists, simulators, emulators, data, and computer- based training products. The Government shall retain all intellectual property rights to publish, copy, and distribute within the U.S. Department of Defense (DoD) (CDRL A001).

4.3. Government Furnished Equipment (GFE) / Government Furnished Materials (GFM). The Government is not providing an GFE/GFM.

4.4. Access to Computer Systems.

4.4.1 Request a User ID (and/or CAC) and Password from the designated Government representative. The request shall include the contract number, identification of the employee, including social security number. The request shall include the employee's signature and a statement that the employee understands and accepts.

the requirement to personally protect any password (and/or CAC) assigned to him or her as a result of the computer access request.

4.4.2 Ensure employees do not reveal their passwords to anyone. The obligation to enforce this requirement is a material element of the security requirement herein.

4.4.3 Notify the designated Government representative immediately of an employee’s termination from work on this effort.

4.5. Physical Security

4.5.1 Safeguard all Government property provided. Ensure that all Government facilities, equipment, and materials are secured. Follow regulatory guidance concerning maintenance, use, and safety of Government facilities at operating locations.

4.5.2 For Performance of Services during Emergency Conditions, local procedures shall be followed.

4.6. Personnel Security. Manage all aspects of security associated with performance to include personnel security access, security clearance information preparation, and liaison with Government POCs for security related items. Capture and maintain information regarding all contract personnel and security related data. The personnel information maintained and provided to the COR shall include a list of all personnel performing under the contract, security clearance levels, sponsors, dates for performance, and government identification materials (i.e.

Common Access Cards (CACs)). Provide information supporting visit requests, CACs, personnel clearance, and other security related activities.

4.7. Delivery

4.7.1 The Contractor shall deliver all software developed, modified or enhanced under this effort as source and object (executable) code, API, SDK, and developer documentation including commented source code as prescribed by the Government. Ensure all deliverables involving source code contains sufficient information for the Government to recreate the build environments to include: the compiler, environment variables, Operating System (OS), OS patches, all run-time libraries, middleware, make files, as well as test code (i.e. stubs and scaffolding) and any other dependencies to assure a successful build upon delivery. Commercial tools for which the Government does not own a license need not be included. Source code shall not be delivered outside AFCEC/CXXM without written permission of the COR. Forward requests for source code releases to the COR (CDRL A001).

4.7.2 Developed, modified and enhanced software under this effort is to be completely maintainable and modifiable with no reliance on any non-delivered computer programs or documentation.

4.7.3 All products shall be delivered digitally via email, DoD SAFE, and/or CD/DVD.

4.7.4 If material is subject to export-control restrictions, it may not be submitted via unsecured or unencrypted email.

4.7.5 All software shall be packaged as a single executable package utilizing Windows

Installer. The Government will identify software packages that do or do not require administrative privileges for installation.

4.8. Software Sustainment.

4.8.1 All software and systems are irritative in nature, thus are developed and fielded in capability spirals. The Contractor shall develop a methodology for establishing both developmental and fielding strategies to identify and track these spirals. This includes, but is not limited to, naming conventions, versioning, and configuration management.

4.8.2 All software shall be delivered as complete and usable products and shall not utilize updates or patches.

4.8.3 The Contractor shall determine the naming convention to track developmental and potential release candidates. The Government will provide the fielded naming convention and/or version number.

4.8.4 The Contractor shall perform the tasks below for all the application named in Appendix A.:

• Create/document use cases to sufficiently capture programming requirements. This includes, but is not limited to, user interface requirements, tool behavior, data requirements, data schemas, alignment with policy and guidance, and report generation.

• Perform Bug Fixes. A bug is considered an error or fault in the design, development, or operations of the software that cause incorrect or unexpected behavior. The Contractor shall classify bugs as low, medium, high, or critical.

• Product Backlog Items (PBIs). A PBI is a backlog of user requested changes. This PWS only address PBIs supporting existing capabilities and not the development of a new capability. This includes, but is not limited to, modification of the User Interface (US), changes required by the underlying software (i.e., Autodesk or SQL), data updates, wizard creation, process optimization, reports and maps, import/export protocols, and/or security updates. PBIs shall be classified by the Product Value (determined by the Government) and Level of Effort (determined by the Contractor).

• Conduct Software Testing.

o Functional testing such as unit, integration, interoperability, end-to-end, and regression.

o Non-functional testing such as performance, load, reliability, and usability o Compliance with all applicable Security Technical Implementation Guides

(STIGs) are applied.

o Other testing required to maintain accreditation and certification and inclusion on the AF E/APL.

o Testing shall be conducted on hardware with and without the USAF Standard

Desktop Configuration (SDC). When conflicts arise, governance of the SDC shall take precedence.

o The Contractor shall work with the Government to ensure proper chain of custody is maintained during all appropriate testing phases.

• Develop system images utilizing Microsoft Deployment Toolkit. The image shall contain all applications, software, device drivers, data, licenses, and user/training manuals required for full system operation.

• Develop specialized scripting to configure software/systems after image implementation. The intent is to customize the software/system to a specific operating location. This includes, but is not limited to, application configuration, loading of geospatial data, device and driver settings, data and file configurations, and naming conventions.

4.8.5 Data Deployment. The Contractor shall create and deploy customizable machine images for all laptops and servers that contains associated software and specifications for each configuration within the Rapid Airfield Damage Assessment (RADAS) system (CDRL 1).

• Laptop configurations for sUAS pilot control.

• Laptop configurations for Ground Control Station (GCS) Data Processing.

• Laptop configurations for Silver Flag Training Site (SFTS) laboratory computers

• Server configuration for data transmission, processing, and storage.

4.8.6 Data Archiving. The Contractor shall develop custom scripting to archive all collected and associated mission data. The script shall produce a single compressed file (i.e., .zip file) containing all collected photos and videos, aircraft log data, and all application log data. The name of the archive file shall include the name of the installation, date, and time.

4.8.7 The Contractor shall not utilize any Freeware in the creation, maintenance, or sustainment of any government owned software.

4.8.8 The Contractor shall coordinate with AFCEC/CXXM prior to implementing any passwords, access card enablement, or roles and permission within any application. If required, the Government shall provide all passwords.

4.9. Data Generation. The Contractor shall develop data sets to support training and operational use of the various software packages. This data includes,:

4.9.1 Geospatial data. This includes raster and vector data in various data formats (i.e., Mr.

Sid, .tff, .dwgs, shapefiles, geodatabases, tabular data) and various data schemas (i.e., Spatial Data for Facilities, Infrastructure, and Environment (SDSFIE), Tri-Service Standards, and Architecture/Engineering/Construction (A/E/C)) (CDRL A001).

4.9.2 Computed Aided Design (CAD) data. This includes two- and three-dimensional data

(CDRL A0011).

4.9.3 Building Information Model (BIM) data (CDRL A001).

4.9.4 Data to support development of virtual reality environment such as geographic, facility, equipment, personnel, and vehicle modeling (CDRL A001).

4.9.5 Synthetic (deep fake) data to support modeling and simulation and augmented/virtual reality (AR/VR) technologies (CDRL A001).

4.9.6 Small Unmanned Aircraft System (sUAS) Flight plans. The contractor shall develop installation specific flight plans, key planning considerations include, number of available aircraft, centralizing location of the launch and recovery zone (LRZ), primary wind direction at the installation, coverage of all the airfield operating surfaces, normalizing the flight time between flight sectors, and prescribed mission profiles (i.e., mission altitudes, mission flight speed, sensor performance). The Contractor shall also convert the flight plans to shapefiles for visualization with GeoExPT. These data may be GFE (CDRL A001).

4.9.7 Ground Control Station (GCS) data. The Contractor shall provide schematic drawings of the layout of the LRZ, the placement and alignment of the radio antenna tripod, and the alignment of each radio enclosure (CDRL A001).

4.9.8 GeoExPT Scenarios. The Contractor shall develop installation specific GeoExPT scenarios. At a minimum the data shall include grids, airfield operating surfaces, aircraft parking areas, RADAS assessment zones (CDRL A001).

4.9.9 IRAA scenarios (CDRL A001).

4.10. Training. The Contractor shall provide direct support for AFCEC sponsored training products and locations.

4.10.1 The Contractor shall develop, maintain, and publish an electronic-based instruction manual detailing all operational capabilities and general maintenance procedures of the supported software and systems.

4.10.2 The Contractor shall produce training support products listed in Appendix A of this

PWS.

4.10.3 The Contractor shall deliver on-site training for all supported software. The training shall be geared towards train-the-trainer. Training locations can be CONUS or OCONUS (as listed below). Class sizes will be limited to 10 students per offering. It is anticipated to conduct one two (2) CONUS and one (1) OCONUS classes per year.

• CONUS

o Dobbins ARB, GA o Fargo ANGB, ND o For Indiantown Gap ANGB, PA o Fort Smith ANGB, AK o Holloman AFB, NM o March ARB, CA o Mountain Home AFB, ID o Nellis AFB, NV o New London ANG, NC o Niceville, FL (Contractor’s location) o Tyndall AFB, FL

• OCONUS

o Andersen AFB, Guam o Joint Base Elmendorf/Richardson (JBER), AK o Osan AF, Korea o Ramstein AFB, Germany o RAF Feltwell/Camp Liberty, UK

4.11. Software Support

4.11.1 Items under this contract shall be free from defects in material and workmanship for one (1) year from the date of acceptance. If a discrepancy is found, the Contractor shall be notified in writing and fixed at no cost to the Government. This warranty applies only to work provided by the Contractor, not as a result of using supporting software.

4.11.2 Contractor shall provide documentation, software, firmware, and hardware support and upgrades necessary to sustain the software during this one (1) year period. This does not apply to any of the supporting software. Software and firmware release candidates will be reviewed by the government prior to implementation (validate scope, categorize, and prioritize solutions) (CDRL A001).

4.12. Data Ownership. All Government data, Government-related data, and metadata is and shall remain the exclusive property of the U.S. Government.

4.13. The Contractor shall provide quarterly work plan, inspected and validated with the Government on a monthly basis via virtual or in person meeting. (CDRL A001, A002, A003).

5. Contract Data Requirements List (CDRLs). The contractor shall prepare and submit the following reports, IAW the DD 1423-1, CDRLs:

5.1. CDRL A001: Software Evaluation

5.2. CDRL A002: Licenses

5.3. CDRL A003: Quality Control Plan (QCP)

5.4. CRDL A004: Travel

6. Services Summary (SS). The following service summary reflects the objectives and thresholds used to track contractor performance for this task order. Government surveillance of tasks not listed in the service summary or by methods other than those listed in the service summary (such as provided in the inspection clause) may occur during the performance period of this contract.

Such surveillance will be done according to standard inspection procedures or other contract provisions. Any action taken by the CO as a result of surveillance will be according to the terms of the contract.

Performance

Objective Reference

Performance Threshold Surveillance Method

PO1. Timeliness of performing requirements.

4.1, 4.9, 4.10, 4.11

Requirements are successfully completed by the first business day of each month as defined in the Performance Work Description(s) and Work Plan(s).

Requirements include, but not limited to:

Requirements Management, WP Implementation, Software Development, Training, Testing, Configuration

Monthly Inspection

Performance Objective

Reference Performance Threshold/ Standard Surveillance

Method PO2. Quality of documentation & deliverable(s).

4.2 All documentation/deliverables are complete, accurate, and IAW the CDRLs.

Documentation fulfills its intended use, meets standards and purpose.

100% Inspection

P O 3 : Completeness of software deliverables and sustainment

4.7, 4.8 Not less than 100% of all software delivered.

These deliverables are IAW the order Work Plan(s), and Performance Work Descriptions(s).

Monthly Inspection

6.1. Quality of Performance. The PM will document all defects and notify the CS/CO. The CS/CO will notify the contractor in writing and request a written response. The contractor’s response will address the accuracy and validity of the defect, planned corrective action, and actions to prevent reoccurrence. The information may be used in the contractor’s annual assessment report

(CPARS).

6.2. Quality Control. The contractor shall implement quality control procedures to ensure the timeliness, completeness, and quality of technical work, reports and publications. Procedures should facilitate early identification of problems or issues affecting technical or contractual performance. Problems or issues requiring government attention shall be communicated in a timely manner. The contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all contractor personnel. The contractor shall convey similar quality control requirements to subcontractors.

6.3. Quality Control Plan.

6.3.1 The contractor shall provide and maintain a Quality Control Plan (QCP) that contains, as a minimum, the items listed below to the PM for acceptance. The PM will notify the contractor of acceptance or required modifications to the plan. The Contractor shall make appropriate modifications and obtain acceptance of the plan

(CDRL A003).

6.3.2 The Government may find the QCP "unacceptable" whenever the Contractor's procedures do not accomplish quality control objective(s). The Contractor shall revise the QCP within ten (10) working days from receipt of notice that QCP is found "unacceptable."

6.3.3 The Contractor shall develop and implement procedures to identify, prevent, and ensure non- recurrence of defective services. The Contractor's QCP is the means by which it assures that work complies with the requirements of the task order.

6.3.4 The CO may notify the Contractor of required modifications to the plan during the POP.

Within ten (10) working days, the Contractor then shall coordinate suggested modifications and obtain acceptance of the plan by the CO.

6.3.5 Any modifications to the QCP during the POP shall be provided to the CO for review no later than ten working days prior to effective date of the change.

6.3.6 The QCP shall include the following minimum requirements:

• A description of the inspection system to cover all major services and deliverables.

The description shall include specifics as to the areas to be inspected on both a scheduled and unscheduled basis, frequency of inspections, and the title of inspectors.

• A description of the methods to be used for identifying and preventing defects in the quality of service performed.

• A description of the records to be kept to document inspections and corrective or preventative actions taken.

• All records of inspections performed shall be retained and made available to the Government upon request throughout the performance period, and for the period after completion, until final settlement of any claims.

6.4. Quality Assurance. The Government will evaluate the contractor’s performance of this contract on a regular basis for the POs listed in the Services Summary. The PM or other designated evaluator will follow the method of surveillance specified in Services Summary.

The Government will conduct informal and formal discussions with the contractor to ensure technical quality remains as high as possible. The Government will review written material that is intended for publication for quality and will provide feedback to the contractor.

Technical documents submitted to the PM for review are expected to be of a high quality requiring minimal modifications or corrections prior to publication. Unacceptable documents will be returned for corrections and resubmission. The PM will coordinate with the contractor if minor corrections are required. If major deficiencies occur and are not corrected or if deficiencies are delivered on a routine basis, the PM will provide written notification of unsatisfactory performance to the CO. The CO will review the circumstances of the PM’s findings and determine if the contractor is conforming to the terms of the contract and if a corrective action plan is required to return performance to an acceptable quality.

7. Additional Information

7.1. Travel.

7.1.1 Travel to both CONUS and OCONUS locations may be required in support of the requirements identified in this PWS. Travel is to be reimbursed in accordance with the Federal Travel Regulations and/or Joint Forces Travel Regulations. All travel must be approved by the PM and CO in advance.

7.1.2 Travel Note: Contractor travel shall include travel to Air Force Bases and other locations, worldwide, but not to locations designated as unduly hazardous for travel by the Department of State (DOS). It is the responsibility of the Contractor to have the necessary credentials prior to traveling and comply with all Government foreign travel requirements as specified by this task order and by the DOS passport regulations.

Additional information and/or training maybe required on a country by country basis.

7.1.3 Specific locations and the duration of travel cannot be established at this time so a travel budget is estimated as follows:

• Year 1: $2,500

• Year 2: $2,500

• Year 3: $2,500

• Year 4: $2,500

• Year 5: $2,500

7.1.4 All travel costs directly billed to the government shall be reported to the PM the month following settlement of the employee’s travel voucher. Supporting documentation will be provided with the contractor’s invoice. The contractor shall ensure the requested travel costs will not exceed what has been authorized in the task order (CDRL A004).

7.2. Freedom of Information Act (FOIA) Program. Contractor shall comply with DoDM 5400.7_ AFMAN 33-302, DoD Freedom of Information Act Program requirements. The regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding Controlled Unclassified Information (CUI) material.

Contractors who are functional OPRs for official government records are not authorized to make the decision to disclose government records.

7.3. Privacy Act (PA) Program. Contractor shall comply with DoDI 5400.11, DoD Privacy Program, requirements and AFI 33-332, AF Privacy and Civil Liberties Program. The regulation sets mandatory guidelines for collecting, safeguarding, maintaining, using, accessing, amending, and disseminating personal information kept in systems of records to comply with the Privacy Act, Title 5, United States Code (U.S.C.), Section 552a.

7.4. Controlled Unclassified Information (CUI). Contractor shall create and maintain CUI material IAW DoDD 5400.07, DoD Freedom of Information Act Program; AFI 17-101 Force Risk Management Framework for Department of the Air Force Information Technology; and AFI 17-130, Cyber Security Program Management. Mark all documents meeting the requirements identified in DoDM 5400.07_AFMAN 33-302, as “Controlled Unclassified Information”. Safeguard all sensitive data IAW DoDM 5400.07_AFMAN 33-302. When documents containing CUI material are authorized for destruction, shred the records in an approved shredder fit for the classification. Degauss or overwrite magnetic tapes or other magnetic media.

7.5. Records Management. Records management at the functional level is life-cycle management (creation, maintenance, storage, use, and disposition) of information as a government record, regardless of media. All data created for government use and delivered to, or fall under the legal control of the government, are federal records and shall be managed IAW DoD and AF directives. These records include information for official use only or information subject to the Privacy Act of 1974. AFI 33-322, Records Management and Information Governance Program, gives details on records management, and provides procedures and responsibilities for contractor’s records. AF WEB-RIMS RDS located at https://webrims.amc.af.mil/rds/index.cfm provides records disposition guidance.

7.6. Contractor Identification. Each person shall identify themselves as contractor employees in all written correspondence (physical and e-mail) and telephone conversations.

APPENDIX A

SOFTWARE SUSTAINMENT

This appendix describes the sustainment tasks for each associated software package. Each of the listed tasks may not be required each update/maintenance cycle. Development cycles shall be scheduled to provide a potential release candidate at ninety-day intervals.

1. ADR Client.

1.1. Description. Application that provides clients with basic GAS functionality (chat, tasking, and media) and tools for sensor management.

1.2. Key Maintenance tasks.

1.2.1. Alignment with remote/robotic platforms.

1.2.2. Alignment with control software for platforms.

1.2.3. Alignment with sensors.

1.2.4. Alignment with GAS updates.

1.2.5. Alignment of application with STIGs.

1.2.6. Updating application documentation.

1.2.7. Updating DoDAFs.

1.2.8. Fixing user identified bugs.

2. Command and Control (C2) Simulator/Virtual Sand Table (VST).

2.1. Description. A virtual reality simulator to provide an immersive training environment for the training and management of the airfield recovery activities. It is built atop Unity.

2.2. Key Maintenance tasks.

2.2.1. Alignment of the application with Unity.

2.2.2. Alignment of the application with ADR Client and GAS.

2.2.3. Alignment of application with STIGs.

2.2.4. Updating algorithms/logic based on DoD or USAF policy or directive guidance documents (e.g., AF Tactics, Techniques, and Procedures (TTPs)).

2.2.5. Updating virtual installation data and models.

2.2.6. Updating common engines (i.e., physics and timing).

2.2.7. Updating symbology and style templates.

2.2.8. Updating reports.

2.2.9. Updating task assignment and management.

2.2.10. Updating application documentation.

2.2.11. Updating DoDAFs.

2.2.12. Fixing user identified bugs,

3. GeoExPT ADR Synchronization (GAS).

3.1. Description. A tool for exchanging data between the different systems and software within the airfield damage Family of Systems. It is bult atop SQL Server. It includes a Software Development Kit (SDK).

3.2. Key Maintenance tasks.

3.2.1. Maintenance of SDK.

3.2.2. Maintenance of stored scenarios.

3.2.3. Maintenance of test client for vendors.

3.2.4. Alignment with SQL server.

3.2.5. Alignment of application with STIGs.

3.2.6. Maintain tasking system.

3.2.7. Updating common engines (i.e., physics and timing).

3.2.8. Updating application documentation.

3.2.9. Updating DoDAFs.

3.2.10. Fixing user identified bugs.

4. GeoExPT Mobile (Android Team Awareness Kit (ATAK)).

4.1. Description. A tool to visualize and manipulate data on an airfield. The GeoExPT Mobile Plugin has multi-user support to create a common set of data for each connected client. The built-in GPS and map functionality of ATAK is utilized in the GeoExPT Mobile Plugin to give the user a real-time view of mitigation and repair operations on the airfield.

4.2. Key Maintenance tasks.

4.2.1. Alignment of the application with ATAK.

4.2.2. Alignment of the application with ADR Client and GAS.

4.2.3. Alignment of application with STIGs.

4.2.4. Updating algorithms/logic based on DoD or USAF policy or directive guidance documents (e.g., AF Tactics, Techniques, and Procedures (TTPs)).

4.2.5. Updating task assignment and management.

4.2.6. Updating application documentation.

4.2.7. Updating DoDAFs.

4.2.8. Fixing user identified bugs.

5. Geospatial Expeditionary Planning Tool (GeoExPT).

5.1. Description. A decision support tool for planners providing the ability to build contingency beddown plans, aircraft parking plans, manage airfield damage, and select Minimum Airfield Operating Surfaces (MAOS) in accordance with USAF standards. GeoExPT includes templates, advanced placement and layout tools, constraints analysis, predefined units, sets, components, aircraft, and reports. It is built as a plugin to Autodesk’s AutoCAD Civil 3D and Map 3D.

5.2. Key Maintenance tasks. The maintenance tasks include:

5.2.1. Alignment of the application with the Civil 3D and Map 3D.

5.2.2. Alignment of the application with ADR Client and GAS.

5.2.3. Alignment of application with STIGs.

5.2.4. Updating algorithms/logic based on DoD or USAF policy or directive guidance documents (e.g., AF Tactics, Techniques, and Procedures (TTPs)).

5.2.5. Updating the asset and vehicle data.

5.2.6. Updating symbology and style templates.

5.2.7. Updating reports.

5.2.8. Updating task assignment and management.

5.2.9. Updating beddown and parking templates.

5.2.10. Updating import/export routines and templates.

5.2.11. Updating application documentation.

5.2.12. Updating DoDAFs.

5.2.13. Fixing user identified bugs.

6. Installation Recovery After Attack (IRAA).

6.1. Description. A tool to manage equipment, manpower, materials, and vehicles associated with recovering an airfield after attack. It automates many of the Command and Control

(C2) functions performed in the Civil Engineer (CE) Unit Control Center (CE-UCC), replacing non-standard databases, spreadsheets, and wall-mounted status boards. It is built atop SQLite.

6.2. Key Maintenance tasks.

6.2.1. Alignment of the application if SQLite.

6.2.2. Alignment of the application with ADR Client and GAS.

6.2.3. Alignment of application with STIGs.

6.2.4. Updating algorithms/logic based on DoD or USAF policy or directive guidance documents (e.g., AF Tactics, Techniques, and Procedures (TTPs)).

6.2.5. Updating the domain data.

6.2.6. Updating reports.

6.2.7. Updating task assignment and management.

6.2.8. Updating import/export routines and templates.

6.2.9. Updating application documentation.

6.2.10. Updating DoDAFs.

6.2.11. Fixing user identified bugs.

7. IRAA Mobile.

7.1. Description. A tool to enable field personnel to manage team and crew resources and taskings associated with airfield recovery. It is built utilizing the Android Software Development Kit

(SDK).

7.2. Key Maintenance tasks.

7.2.1. Alignment of the application with Android SDK.

7.2.2. Alignment of the application with ADR Client and GAS.

7.2.3. Alignment of application with STIGs.

7.2.4. Updating algorithms/logic based on DoD or USAF policy or directive guidance documents (e.g., AF Tactics, Techniques, and Procedures (TTPs)).

7.2.5. Updating task assignment and management.

7.2.6. Updating application documentation.

7.2.7. Updating DoDAFs.

7.2.8. Fixing user identified bugs.

8. Aircraft Control Software.

8.1. Description. Software developed by aircraft manufacturer. It includes all the tools to perform preflight/mission planning, operate the aircraft, download and process and media, and perform post flight actions. It also includes a Payload Development Kit (PDK).

8.2. Key Maintenance tasks.

8.2.1. Alignment of the application with vendor’s SDK.

8.2.2. Alignment of the application with ADR Client and GAS.

8.2.3. Alignment of application with STIGs.

8.2.4. Updating DoDAFs.

APPENDIX B

SOFTWARE SUSTAINMENT – WORKLOAD ESTIMATES

Each of the listed tasks may not be required each update/maintenance cycle.

Software Level of Effort Percentage Bug Fixes Product Backlog Item

ADR Client 3% 2 5 C2Sim/VST 10% 4 8

GAS 10% 4 8

GeoExPT 30% 6 20 GeoExPT Mobile 5% 4 6

IRAA 30% 6 20

IRAA Mobile 10% 4 8 Aircraft Control Software

2% 2 2

TOTAL 100% 32 77

Labor Categories Estimated Yearly Hours Principal Software Engineer (Level II) 2040 Senior Software Engineer (Level III) 1500 Program Manager 120 Project Manager 420 Technical Writer 120