v12_PWS_GLADS_UDOP.pdf

PDF 210 KB Posted Aug 2, 2019

Attached to: Award Notice: Global Awareness and Decision Support (GLADS)
Solicitation number: AFICCFA4452-19-R-A007
Issued by: Department of the Air Force Air Mobility Command

About this file

From the source

Attachment 1: Performance Work Statement (PWS)

View the file

Other files

File	Type	Posted
GLADS_JA_Redacted_10_Oct.pdf	PDF	Oct 10, 2019
DD254_GLADS_UDOP_2019_(003).pdf	PDF	Aug 2, 2019
QASP_GLADS.pdf	PDF	Aug 2, 2019
Mission_Essential_Letter_Signed.pdf	PDF	Aug 2, 2019
GLADS_Solicitation_-_FA445219RA007.pdf	PDF	Aug 2, 2019
Task_Order_1_RFP.pdf	PDF	Aug 2, 2019
CDRLs_FA4452-19-R-A007.pdf	PDF	Aug 2, 2019

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Air Mobility Command (AMC) 618th Air Operations Center (Tanker Airlift Control Center)

(618 AOC (TACC))

Requirements Contract Level Performance Work Statement (PWS)

Mobility Air Forces User Defined Operational Picture (MAF UDOP) – Global Awareness and Decision Support (GLADS)

1 Aug 2019

UNCLASSIFIED

TABLE OF CONTENTS

1.0 Background and Scope

1.1 Background

1.2 Scope

2.0 Scope of Work - Technical Tasks

2.1 Task 1: MAF UDOP -GLADS Integration Support

2.2 Task 2: Acceptance and User Testing

2.3 Task 3: Training and Demonstration

3.0 Deliverables

4.0 Service Summary

5.0 Place of Performance

6.0 Contractor Manpower Reporting

7.0 General Requirements

7.1 Contractor Personnel

7.2 Contractor Consent to Background Checks

7.3 Security

7.4 Confidentiality and Non-Disclosure Agreements

7.5 Facilities, Communications, Hardware and Software

7.6 PWS Change Process

7.7 Common Access Card and Restricted Area Badge

7.8 Non-Personal Services

7.9 Access to Installation During Force Protection Conditions (FPCONs)

7.10 Safeguarding Classified or Unclassified Information

7.11 Protection of Information

7.12 Release of Information

7.13 Information Assurance (IA) Workforce Training

7.14Privacy Act

7.15 Safety

7.16 Personnel Security

7.17 Transmission of Classified Material

UNCLASSIFIED

7.18 Protection of System Data

7.19 System and Network Authorization Access Requests

7.20 Antiterrorism Force Protection Level I Training

7.21 Contractors Working in Controlled or Restricted Areas

7.22 Property Protection

8.0 Technical Points of Contact

9.0 Deliverable Rights

9.1 Commercial Software Ownership and Rights

10.0 Software

10.1 Software License Coverage

11.0 GLADS Notional Phase VI-X Milestones

12.0 Travel

13.0 Annex 1

14.0 Annex 2

15.0 Annex 3

16.0 Appendix 1

1.0 BACKGROUND AND SCOPE

1.1 Background:

The Air Mobility Command (AMC) required Systems Tool Kit (STK) Commercial Off-the-Shelf (COTS) software and associated Global Awareness and Decision Support (GLADS) capability was purchased and installed in 2014 as a workstation/client license capability. Experience with the capability led to the government decision to transition from a workstation/client license based Thick Client capability, to a web application server environment based capability to complete Phase V of the GLADS integration effort. Phase III through V provided a phased approach to achieving Initial Operating Capability (IOC) of the web-enabled GLADS capability on both the Secret Internet Protocol Router Network (SIPR) and the Non-classified Internet Protocol Router Network (NIPR). Phase III through V also added critical decision support tools, connections to other authoritative data sources, and increased functionality. Notional phase VI through X will add integration of NIPR and SIPR Authoritative Data Sources (ADS) and Decision Support Tools (DST) and capabilities to address mission critical materiel solution gaps and shortfalls documented in the 618 AOC Capabilities Based Assessment (CBA) and Initial Capability Document and associated Requirements Definition (ISRD). Notional phase VI through X will also allow United States Transportation Command (USTC) to explore/exploit/field this capability to meet their specific COCOM requirements.

The logistics support workflows of AMC in the areas of data management, data access, data visualization and data analysis are spread across multiple networks and a multitude of disparate data sources. AMC 618 Air and Space Operations Center (Tanker Airlift Control Center) (618 AOC (TACC)) staff now has achieved IOC of a single web enabled User Defined Operational Picture (UDOP) for their airborne assets, weather, Intel and logistical support information such as airfields.

The Mobility Air Forces (MAF) UDOP - GLADS was generated by leveraging the United States Strategic Command (USSTRATCOM) requirements. MAF UDOP- GLADS supports different user communities by collecting information from disparate sources and providing an aggregated set of Situational Awareness (SA) products in the form of a UDOP. Also, the use of web-based technologies vice client-based greatly increases the ability to share this information with other mission partners and organizations. The purpose of MAF UDOP-GLADS is to provide an easy, effective, and customizable (e.g., user definable) capability to access, display and use a variety of information supporting strategic and tactical use cases throughout the DoD. The current contract leverages the operationally proven Global Awareness and Presentation Services (GAPS) system and expertise of the GLADS contractor to integrate these services and capabilities with 618 AOC (TACC) information sources

UNCLASSIFIED

in order to provide automation, visualization, workflow support and situational awareness through one or more 618 AOC (TACC) and, as applicable, USTC UDOPs.

The effort outlined in this PWS adds additional decision support tools, connections to other authoritative data sources and increased functionality as specified in the attached Annex A and B, which contains descriptions of the notional phased requirements and results in a sustainable solution that provides web-based access to a variety of information sources and SA products to support workflows and collaboration. The primary areas of work include integration of authoritative data and services with data sources, testing and integration into a web-based environment supporting 618 AOC (TACC) use cases on both SIPRNET (GLADS) (classified) and NIPRNET (GLADS) (unclassified network). As a result of experience gained during Phase I through V, the need for additional decision support tools, connection to other authoritative data sources and functionality tailoring has been identified and a notional phased approach laid out to integrate AFRL provided technologies, additional authoritative data sources, as well as complete any additional upgrades to GLADS based on capabilities not planned to be delivered in GLADS Phase I - V.

This is a requirements contract type where the subtasks listed in Annex 1 and 2 will be ordered as needed IAW AMC & 763 SCONS Standard Procedures.

1.2 Scope:

The Government requires the GLADS contractor to integrate GLADS capabilities and services with AMC, MAF, United States Transportation Command, and other authoritative data sources to support daily operations by adding additional decision support tools to the existing UDOP capability via the GLADS UDOP. This includes obtaining for the purpose of UDOP display, the most up-to-date and/or real-time data available. The contractor shall tailor COTS/GOTS software to provide meaningful outputs, onsite and remote user support, testing, training: documentation of all tools, techniques, and training.

This PWS defines the requirements for the contractor to engineer, install and test (EI&T) an integrated solution to provide daily operations during the period of performance.

The contractor shall provide and tailor its standard software as identified in Section 10 to integrate with existing Air Force systems and networks and in accordance with the GLADS milestones listed in Section 11. The tailored software solution shall provide meaningful outputs, on-site and remote user support, testing, documenting all tools and techniques utilized during testing. The contractor shall coordinate all testing & cutover plans with Air Force personnel for acceptance prior to cutover.

UNCLASSIFIED

The contractor shall provide both on-site and remote site support during normal duty hours; except as stated in Task 3.

The contractor shall provide on-site training within the 618 AOC (TACC). This includes training material, both paper and electronic tools as required to meet the performance objectives and thresholds.

2.0 SCOPE OF WORK – TECHNICAL TASKS

Contractor shall draw upon expertise gained from previous GLADS development efforts and interactions with 618 AOC (TACC) stakeholders. Contractor shall gain specific customer domain knowledge with 618 AOC (TACC) stakeholders. This knowledge and information will be used to tailor and test the functional capabilities of GLADS to help support 618 AOC (TACC) and USTC operations (as required).

Contractor shall propose and deliver draft Task Work Plan and Schedule inputs for AMC to approve and finalize in accordance with CDRL A005. Approval authority is the Contracting Officer Representative (COR). The Task Work Plan and Schedule shall provide the taskings to accomplish the requirements of each Task Order listed as an attachment to the request for proposal (RFP).

Contractor shall produce and deliver Monthly Status Reports with Addenda, and Program Management Review (PMR) slides in accordance with (IAW) performance objectives and thresholds specified in Sections 3 and 4, Deliverables and Services Summary of this PWS.

2.1 Task 1: MAF UDOP – GLADS Integration Support

Contractor shall provide on-site and remote support to help identify and understand user needs, requirements, Concept of Operations (CONOPs) and use cases as well as facilitate installation, integration, tailoring, and validating of software capabilities.

For this period of performance, on-site MAF UDOP-GLADS assistance will be provided for 618 AOC (TACC), and USTC (as applicable) personnel creating UDOPs that are outlined in the UDOP Information Systems ISRD using existing software.

The ISRD is maintained and will be made available from AMC/A3CG.

Contractor shall work with stakeholders, 18 AOC (TACC), and USTC (as applicable) staff to integrate sources of data and information supporting 618 AOC (TACC) operations such as aircraft tracking, weather data, intelligence sources, infrastructure information and additional information sources needed to support 618 AOC (TACC) activities and SA. To obtain the appropriate data, the contractor will require access to the 618 AOC Data and Web Services (DAWS) for hosting and access to GDSS data, AMC Mobility Enterprise Information System (MEIS), and other methods to access identified authoritative data sources.

UNCLASSIFIED

Contractor shall develop a series of 618 AOC (TACC) and USTC (as applicable) UDOPs and decision support tools that provide information views based upon required sources. Contractor shall provide software and UDOPs to support both unclassified operations and SIPRNET operations.

Contractor shall work with stakeholders and users to automate workflows including accessing information, merging of information from multiple sources and producing output reports and products.

Contractor shall provide 618 AOC (TACC) and USTC (as applicable) users with access to information and MAF UDOP-GLADS related to 618 AOC (TACC) and USTC (as applicable) operations and activities.

Contractor shall develop training material to support 618 AOC (TACC) workflows involving MAF UDOP-GLADS software. Contractor shall develop training material for the Government to use the available tools and techniques to manage emerging MAF UDOP-GLADS needs.

The Government is responsible for identifying, securing and financing a GLADS hosting environment that meets the criticality, reliability and system availability requirements imposed on the GLADS UDOP solution. Contractor shall develop a hardware (server) hosting deployment plan, if required. This plan shall outline steps for a local server as well as a server hosted outside the 618 AOC (TACC).

Contractor shall support 618 AOC (TACC) and USTC (as applicable) with subject matter expertise (SME) as changes occur in the hosting environment and programs impact access to authoritative data sources and/or other UDOP capabilities. SME areas include net-centric operations, software development, domain specific knowledge in C4ISR, Logistical support, and other DoD-related domains.

Contractor shall provide a technical roadmap that describes requirements for related capabilities beyond the Period of Performance of the effort outlined in this PWS.

Contractor shall provide on-site technical support during business hours and provide up to 24 discontinuous hours of “on-call” weekend or night support to address critical issues occurring outside of normal duty hours at 618 AOC (TACC) and USTC (as applicable), Scott AFB, IL.

2.2 Task 2: Acceptance and User Testing

Contractor shall write a capabilities validation plan.

Contractor shall perform and facilitate user validation of information outputs from GLADS software.

UNCLASSIFIED

Contractor shall provide software integration testing, operational evaluations, software defect identification and resolution.

2.3 Task 3: Training and Demonstration

Contractor shall provide MAF UDOP-GLADS training for Government users and managers at the 618 AOC (TACC) and USTC (as applicable) at Scott AFB, IL.

Contractor shall provide MAF UDOP-GLADS User Guides, and user guide content shall be refreshed as appropriate in each GLADS release to reflect significant new or modified capabilities associated with that release.

Contractor shall demonstrate capabilities to users and 618 AOC (TACC) stakeholders and USTC (as applicable) at Scott AFB, IL.

Contractor shall provide demonstration and experimentation support at key program events and venues that support 618 AOC (TACC) and USTC (as applicable) program objectives.

Contractor shall provide support to program events: program reviews, technical interchange meetings, demonstrations, workshops, exercise events and conferences as required.

Contractor shall provide demonstration of Access/Availability of GAPS authoritative data source information for classified and unclassified networks.

3.0 DELIVERABLES

The document deliverables will be delivered to the COR via electronic means.

Table 3: Contract Data Requirements List (CDRL) Data Deliverables

CDRL Deliverable Title PWS Para.

A001 Monthly Status Report 2.0 A002 Quarterly PMR Slide Submittal 2.0 A003 Capabilities Validation Plan 2.2 A004 MAF UDOP-GLADS User Guides 2.3 A005 Task Work Plan and Schedule 2.0

4.0 SERVICES SUMMARY

Performance Objective PWS Paragraph

Performance Threshold

Provide documentation support necessary to accomplish the Contract in a responsive, satisfactory, and timely manner. 2.0

Performance is acceptable when:

-All data deliverables are in accordance with

2.0 and corresponding CDRLs.

-No more than one late Monthly Status Report with Addendum annually.

-No more than 1 PMR coordinated slides late annually.

Provide a task work plan and schedule for AMC approval.

2.0

Performance is acceptable when:

-Delivery to COR is not later than fifteen (15) days after award of the contract.

5.0 PLACE OF PERFORMANCE

The primary place of work for performance of this effort shall be at the 618 AOC (TACC) and USTC (as applicable) at Scott AFB. Additional work that is required for UDOP tailoring shall be performed at the contractor facilities when other support (reach back) is required.

6.0 CONTRACTOR MANPOWER REPORTING

The contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for AMC/A6 via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil. Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 01 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year. Contractors may direct questions to the Contractor Manpower Reporting Application (CMRA) help desk.

*Reporting Period: Contractors are required to input data by 31 October of each year.

Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with http://www.ecmra.mil/

UNCLASSIFIED

the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

User Manuals: Data for Air Force service requirements must be input at the Air Force CMRA link. However, user manuals for Government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil.

7.0 GENERAL REQUIREMENTS

7.1 Contractor Personnel

The Contractor shall provide personnel who have experience with STK software.

7.2 Contractor Consent to Background Checks

The contractor shall not employ persons to perform under this contract if such employee is deemed or identified by Scott AFB as a potential threat to the health, safety, security, general well-being or operational mission of the installation and its population, nor shall the contractor or subcontractor employ persons under this contract who have an outstanding criminal warrant as identified by Law Enforcement Agency Data System (LEADS) through the National Crime Information Center.

LEADS checks will verify if a person is wanted by local, state, and federal agencies.

All Contractor and subcontractor personnel must consent to LEADS background checks, before being granted access to installation. Contractor and subcontractor personnel who do not consent to a LEADS check will be denied access to the installation. Information required to conduct a LEADS check includes: full name, driver’s license number, and/or social security number, date of birth of the person entering the installation, and completion of a background check questionnaire. The contractor must have this information ready to provide to the installation’s Visitor Control Center, if requested.

Contractors must ensure their employees and those of their subcontracts have the proper credentials allowing them to work in the United States. Persons later found to be undocumented or illegal aliens will be remanded to the proper authorities.

The contractor shall not be entitled to any compensation for delays or expenses associated with complying with the provisions of this clause. Furthermore, nothing in this clause shall excuse the contractor from proceeding with the contract as required.

7.3 Security

http://www.ecmra.mil/

UNCLASSIFIED

The contractor shall ensure all data is appropriately protected and is accessible only to those individuals with appropriate accesses and an authorized “need-to-know”. The contractor shall ensure all personnel are cleared at the appropriate level in accordance with 618 AOC (TACC) security policies. Technical, programmatic and schedule materials shall be stored on appropriately approved computer systems provided by the Government.

7.4 Confidentiality and Non-Disclosure Agreements

Contractor personnel shall sign appropriate Organizational Conflict of Interest (OCI) and Non-disclosure agreements (NDA) as required.

Due to the sensitive nature of the data and information being worked with on a daily basis, the contractor shall require contractor personnel to sign a non-disclosure statement to protect non-public information of the Government. All contractor personnel assigned to the contract shall complete and return a Government-provided non-disclosure statement within 15 calendar days after award to protect unauthorized disclosure of sensitive or proprietary information. Copies of signed non-disclosure statements shall be provided to the COR.

As required, all contractor personnel assigned to the contract may be required to complete additional non-disclosure statements prior to technical interchanges to ensure information that is considered sensitive or proprietary by other companies, corporations, or businesses is not compromised. Signed non-disclosure statements shall be provided to the COR for distribution.

7.5 Facilities, Communications, Hardware and Software

The Government will provide a standard Air Force office workspace with furniture, personal computer with network access (remote access is authorized) and standard services (email, print, applications, etc.), telephone access, and access to office equipment for official business.

The Government will provide Camtasia or other similar software onsite to support the recording of the videos, but the contractor personnel shall perform video production functions.

Except for the software licenses provided as part of the PWS, contractor is not expected to purchase hardware or software for use in executing this task.

7.6 PWS Change Process

UNCLASSIFIED

Changes to the scope of this PWS may only be made by the Contracting Officer. The Contracting Officer is the ultimate authority on all changes to the PWS.

7.7 Common Access Card and Restricted Area Badge

Photo identification, such as Common Access Card (CAC) and Restricted Area Badge as required. The contractor shall comply with all DoD, AF and installation requirements as necessary to obtain a CAC and Restricted Area Badge for each employee.

The contractor is required to provide identification badges for their employees. All contractor personnel shall wear these badges while on duty on the Government site.

Badges are required to identify the individual, company name, and be clearly and distinctly marked as contractor. Size, color, style, etc. are to be mutually agreed to by contractor and Government. The contractor’s identification badge will not be used as an entry requirement for installation entry or into any Government designated controlled or restricted area.

7.8 Non-Personal Services

The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the contractor feels that any actions constitute, or are perceived to constitute personal services, it shall be the contractor’s responsibility to notify the Contracting Officer immediately. These services shall not be used to perform work of a policy/decision making or management nature, i.e., inherently Governmental functions. All decisions relative to programs supported by the contractor shall be the sole responsibility of the Government. These operating procedures may be superseded by Theater Commander’s direction during deployments.

7.9 Access to Installation During Force Protection Conditions (FPCONs)

Contractor will be assigned a mission essential designation IAW requirements contained in the installation’s Integrated Defense Plan or the Installation Antiterrorism Plan. Only the installation commander or the unit commander requesting contract support will assign the mission essential designation.

7.10 Safeguarding Classified or Unclassified Information

UNCLASSIFIED

The contractor shall meet Air Force standards for storing, processing, and handling classified information and systems. Additionally, all resources (e.g. maps, publication/instructions, photos) provided by the Government to assist the contractor in the performance of their contract will be surrendered upon termination of the contractor’s involvement in the project or the end of the contract performance period.

7.11 Protection of Information

In performance of this contract, the contractor may obtain access to sensitive, nonpublic information. The contractor agrees (a) to use and protect such information from unauthorized disclosure IAW Federal Acquisition Regulations (FAR); (b) to use and disclose such information only for the purpose of performing this contract and to not use or disclose such information for any personal or commercial purpose; (c) to obtain permission of the government COR before disclosing or discussing such information with a third party; (d) to return, upon government request, any non-public, sensitive information no longer required for contractor performance; and (e) to advise the government representative of any unauthorized release of such information.

7.12 Release of Information

The contractor shall not hold any discussions or release any information relating to this contract to anyone not having a direct interest in performance of this contract, without written consent of the CO or designated representative of the CO. This restriction applies to all news releases of information to the public, industry or government agencies, except as follows: information for actual or potential subcontractors or other individuals necessary for the contractor’s performance of this contract.

The contractor shall not issue advertisements about projects performed under this contract without Government review and approval. For the purposes of this paragraph, advertisement is considered to be contractor-funded promotional brochures, posters, tradeshow handouts, World-Wide-Web pages, magazines, or any other similar type promotions.

7.13 Information Assurance (IA) Workforce Training

IAW Defense Federal Acquisition Regulations (DFARS) clause 252.239-7001, The Contractor personnel shall comply with all AMC or respective MAJCOM security requirements pursuant to DODD 5200.2, DOD Personnel Security Program, which requires DOD military, and civilian personnel, as well as DOD consultant and Contractor personnel who perform work on sensitive automated information systems (AIS) to be assigned to positions which are designated sensitive. All personnel must

UNCLASSIFIED

complete Annual Information Assurance training by on line computer based training (CBT). All personnel must comply with DoD 8570.01-M, Information Assurance Workforce Improvement Program, as required in this PWS, and must provide certifications within 15 days of performance start date.

7.14 Privacy Act

Work on this project requires that personnel have access to Privacy Information.

Personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations.

7.15 Safety

The Contractor shall comply with all safety provisions, e.g., technical specifications, technical publications, Federal Occupational Safety and Health Standards (Title 29 CFR Part 1910). If there is no applicable Occupational Safety and Health Administration (OSHA) standard, the Contractor shall use other applicable national, state or locally recognized sources of safety, health, fire prevention, and airfield operations standards.

7.16 Personnel Security

Individuals performing work under this contract shall comply with applicable program security requirements as stated in the task order. GLADS will support the following levels of security: Unclassified; Unclassified, But Sensitive; Secret (S) and Top Secret (TS).

The PWS requires personnel utilizing TACC as their primary work location to possess or obtain a TOP SECRET clearance. The PWS requires personnel visiting 618 AOC (TACC) possess or obtain a SECRET clearance. The security clearance requirements will depend on the security level required by the proposed task order.

Contractors who require SECRET clearance shall be able to obtain adequate security clearances prior to performing services under the contract. The Contract Security Classification Specification (DD Form 254) will be at the basic contract and task order level and will encompass all security requirements. All contractors located on military installations shall also comply with Operations Security (OPSEC) requirements as set forth in DoD Directive 5205.02, Operations Security Program and AFI 10-701, Operations Security. IAW DoD 5200.2-R, Personnel Security Program (Jan 87), DoD military, civilian, consultants, and contractor personnel using unclassified automated information systems, including e-mail, shall have, at a minimum, a completed favorable National Agency Check plus Written Inquiries (NACI). A DD254, Contract Security Classification Specification, shall provide the

UNCLASSIFIED

Security Requirements. Additionally, a Visitor Group Security Agreement (VGSA) will be executed upon work start. If multiple locations are listed in Block 8a of the DD 254, separate VGSAs will be used for each location.

The types of Personnel Security Investigations (PSI) required for the contractor vary in scope of investigative effort depending upon requirements of the Government and/or conditions of the contract. In cases where access to systems such as e-mail is a requirement of the Government, application/cost for the PSI shall be the responsibility of the Government. In cases where access to systems is a condition of the contract, application/cost for the appropriate PSI shall be the responsibility of the contractor. In such instances, the contractor shall diligently pursue obtaining the appropriate PSI for its employees prior to assigning them to work any active task order. Acquisition planning must consider Anti-Terrorism (AT) measures when the effort to be contracted could affect the security of operating forces (particularly in-transit forces), information systems and communications systems IAW DoD Instructions 2000.16 Anti-Terrorism Standards.

7.17 Transmission of Classified Material

The contractor shall transmit and deliver classified material/reports IAW the National Industrial Security Program Operating Manual (DoD 5220.22-M). These requirements shall be accomplished as specified in this task order.

7.18 Protection of System Data

Unless otherwise stated in the task order, the contractor shall protect system design-related documents and operational data whether in written form or in electronic form via a network IAW all applicable policies and procedures for such data, including DoD Regulation 5400.7-R and DoD Manual 5200.01(v1-v4) to include latest changes, and applicable service/agency/ combatant command policies and procedures. The contractor shall protect system design related documents and operational data at least to the level provided by Secure Sockets Layer (SSL)/Transport Security Layer (TSL)-protected web site connections with certificate and or user ID/password-based access controls. In either case, the certificates used by the Contractor for these protections shall be DoD or IC approved Public Key Infrastructure (PKI) certificates issued by a DoD or IC approved External Certification Authority (ECA) and shall make use of at least 128-bit encryption.

7.19 System and Network Authorization Access Requests

For Contractor personnel who require access to DoD, Defense Information Systems Agency (DISA), or Air Force computing equipment or networks, the Contractor shall

UNCLASSIFIED

have the employee, prime or subcontracted, sign and submit a System Authorization Access Report (SAAR), DD Form 2875.

7.20 Antiterrorism Force Protection Level I Training

Within 30 calendar days after contract start; all contractor personnel shall complete Antiterrorism Level I Training, as required by DODI 2000.16. Newly hired personnel shall complete the Antiterrorism Level I Training within the first 30 calendar days of their employment. Refresher Antiterrorism Level I Training shall be completed and documented annually thereafter. The training is provided at https://atlevel1.dtic.mil/at/ and also available through Advanced Distributed Learning Services, Force Protection Course (ZZ133079) at https://golearn.csd.disa.mil/kc/main/kc_frame.asp for AF Portal access or https://golearn.csd.disa.mil/kc/login/login.asp for non-portal login.

7.21 Contractors Working in Controlled or Restricted Areas

In the unlikely event that a Contractor requires access to the controlled or restricted area and does not have the proper security clearance, the Government will ensure escort(s) are provided for the contractor at all times when within a controlled or restricted area. The contractor must have an issued AF Form 1199; work on base a minimum of 4 days a week (must have an assigned workspace on base). The contractor is only allowed to escort visitors from the same company for which he/she works and all visits must be for official business. In addition, Contractors must fulfill, maintain, and comply with all security requirements IAW AFI 31-101, Integrated Defense, and command/local directives.

7.22 Property Protection

Property protection for facility where the contractors’ primary work center is located will be the responsibility of the local facility manager and local Government Security Manager, or their duly authorized representative IAW AFI 31-101, Integrated Defense and command/local directives. The contractor shall safeguard all government-owned equipment and materials in his/her possession or use.

8.0 TECHNICAL POINTS OF CONTACT

AMC 618 AOC (TACC) Technical Point of Contact: Mrs. Loraine Watkins

9.0 DELIVERABLE RIGHTS

Commercial Software Ownership and Rights

UNCLASSIFIED

Contractor’s Commercial Software Products shall be provided to AMC; these software products shall be governed by the terms and conditions set forth in the applicable Contractor Software License Agreement, available at www.agi.com/sla. Furthermore, AMC’s right to use such Commercial Software Products is exclusively limited to the terms and conditions set forth herein or as otherwise stated within this PWS.

Contractor shall retain all ownership rights, title to and interest(s) in and to any and all pre-existing Contractor Commercial Software Products and Intellectual Property. Any capability or source code currently being developed by Contractor or developed to further enhance Contractor’s Commercial Software Products, shall remain the exclusive intellectual property of Contractor.

10.0 SOFTWARE

The contractor shall provide the following STK licenses:

Manager/Supervisor – Unlimited with permission restricted to 618 AOC (TACC) and USTC DDOC (if/as applicable)

Operator – Unlimited with permission restricted to 618 AOC (TACC) and USTC Deployment and Distribution Operations Center (DDOC) (if/as applicable)

Viewer – Unlimited to all persons with access to system.

Software License Coverage

Access Level Capabilities Technology

Access Organizational

Definition

Add content;

Create and publish template; Filter, create checklists

STK Online Server & Client &

Desktop C om m an d C en te r

M an ag er

Su pe rv is or

UNCLASSIFIED

O pe ra to r

Use Table Of Contents (TOC);

Search feeds; Pre-defined links;

Change graphics (colors/markers) Markup, create snapshots, debriefs

STK Online Client

D ire ct P ar en t C om m an d

(n ot su bo rd in at es

V ie w er

View only of snapshots, debrief, globe with zoom

STK Viewer

St ak e ho ld er s

11.0 GLADS PHASE VI – X MILESTONES

Note: Government is responsible for determining the NIPR and SIPR Server hosting solution and operational implementation of Mobility Enterprise Information System 4 (MEIS4). Note: See APPENDIX 1 for acronym definitions.

12.0 TRAVEL

UNCLASSIFIED

As an integral part of performing some of the requirements of the PWS the contractor shall perform temporary duty (TDY) non-local travel (over 50 mile radius) to domestic locations.

Travel is accomplished on a firm fixed price basis and the Contractor shall fund all local travel. If an emergency or an unforeseen travel arises, a contract modification will be negotiated at that time and executed by the Contracting Officer.

13.0 ANNEX 1

AMC Notional Phase Requirement Descriptions

Phase VI Integration Requirements – The Contractor Shall:

1. Ingest JMPS JRT (JMPS Route Files) as another optional source to get flight plans for sorties. JRTs contain more tactical data than CRDs.

2. Integrate AOC JRE Web Service tracks.

3. Add AOC JRE Web Service tracks to Area Search

4. Integrate of threat/ROZ proximity DST sourced from ACOs.

5. Integrate FAA data

6. Per DO/DDO's, integrate an option to toggle the divert range ring between the existing capability of distance based on fuel, to a second new option of distance based on 3 hour flight time. This is needed to support KC-46 ETOPS operations.

7. Add steps in checklists to timeline in manner similar to Gantt chart. (Requested by FM leadership)

8. Use MEIS AircraftTypeRefService to present users with exact aircraft MDS text and other filterable criteria required by MEIS instead of relying on user knowledge and wildcarding.

9. Allow users to build sortie filters that only they see, as opposed to adding all filters to the community list. (Requested by FM leadership)

10. Upload WKT based country borders provided by DAWS and integrate into Area Search

DST.

11. In presentation mode, add a parameter that allows dwell for x seconds at current time before beginning each time loop.

12. "IT Box" requirements for Phase VI. AMC and AGI will coordinate throughout the Phase VI period-of-performance to prioritize this content, focusing first on emerging high priority end user needs, then on high priority small scope backlog requirements.

Phase VII Integration Requirements – The Contractor Shall:

1. Per DO/DDOs integrate indications of whether individual sorties are ahead of or behind plan.

2. Per DO/DDO's, integrate an option to cycle between different aircraft/airfield icon sets that would be tailored to different user communities (e.g. FM's vs. BSD's vs. DO/DDOs)

3. Add to existing In-System-Select DST by identifying which eligible aircraft have enough spare cargo/PAX capacity to hold a user (BSD) defined load.

UNCLASSIFIED

4. Per DO/DDOs, integrate TFRs (Temporary Flight Restrictions) into route segment stoplights and drill-down.

5. Integrate OPIR missile warning alerts from C2BMC, JTAGS, or other appropriate source.

Generate displays and alerts relating impact ellipsoid, ICAOs/aircraft threatened, or other as appropriate.

6. Obtain CR (Contingency Response) force locations through TBD data source and represent their locations on the globe.

7. Obtain MSAS (Mobility Support Advisory Squadron) and Air Mobility Liaison Officer (AMLO) force locations through TBD data source and represent their locations on the globe.

8. Integrate SIPR data source (GPSOC) as input to the GPS DST integrated for NIPR in Phase IV.

9. Present information to the user enumerating all countries and FIRs that a given route intersects.

Phase VIII Integration Requirements – The Contractor Shall:

1. Integrate DIPS non-remark data from GDSS and drive route segment stoplights & drill-down information reflecting which sovereign airspaces have and do not have suitable DIPS established for a given sortie.

2. Dynamic links between UDOP and GDSS tools.

3. Integrate GCCS-JE tracks.

4. Integrate Notice To Airman (NOTAMs) into route segment stoplight & drill-down, and into airfield drill-down.

5. Integrate a DST that indicates how many operational tails are at a given airfield.

6. Utilize LIMS-EV or GO-81 data to display a dashboard of asset availability (as opposed to drill-down data on a specific asset as maintenance is being used in other requirements).

7. Generate alerts when winds in ACARS report off by more than x knots from plan, and when wind direction off by more than X degrees from plan.

8. Integrate MEIS "Notification" service. This will reduce overall system bandwidth requirements by allowing MEIS to tell GLADS when certain data changes instead of GLADS constantly polling for changes.

9. "IT Box" requirements for Phase VIII. AMC and AGI will coordinate throughout the Phase VIII period-of-performance to prioritize this content, focusing first on emerging high priority end user needs, then on high priority small scope backlog requirements.

10. Integrate capability to support plans/replans/diverts by automatically calculating potential routes to a user defined location that consider; what DIPS are already established, what weather/ROZ/TFR threats exist, comm/GPS degradation zones, and "Equal Time Point" rules (max allowable distance to divert locations).

Phase IX Integration Requirements – The Contractor Shall:

1. Integrate JRE ground and surface tracks from AOC JRE Web Service.

UNCLASSIFIED

2. Create a "delay misery" DST indicating accumulated delays at given airfields.

3. Accept dynamic emitter indications from Talon Thresher and present ELINT based

DSTs.

4. Add remaining Crew Duty Day as another criteria in the In-System-Select algorithm, and add remaining CDD to sortie detail panel. Requires DAWS to expose results of the multi-sortie CDD calculation utilized for IMR.

5. Integrate taxiway, parking spot, and airport fuel data (MOG) from TBD data source (likely LIMS-EV or GO81) into existing divert DST.

6. Integrate weather stoplight thresholds specific to AR tracks.

7. Integrate airfield specific published ceiling & visibility minimums into weather stoplights

(as opposed to airfield independent ceilings integrated in previous Phases).

8. Allow users to “click-out” a notional route (add/delete/modify waypoints) and receive associated DST assessment (Note: MAFPS info via MEIS ARP service will be used/displayable if most current). User click points are optionally automatically tied to nearby DAFIF waypoints.

9. Calculate crosswind thresholds for runways other than primary. Remove some runways from consideration based on 618 AOC/XOCM table 6.9. Roll-up calculations for all valid runways into overall field stoplight.

10. "IT Box" requirements for Phase IX. AMC and AGI will coordinate throughout the Phase IX period-of-performance to prioritize this content, focusing first on emerging high priority end user needs, then on high priority small scope backlog requirements.

11. Integrate ability for a user to manually create 4D zones on the globe and optionally tie these zones to sortie specific alerts and route planning DSTs. (E.g. if air traffic controllers go on strike in France).

12. Add an altitude slider to the area search criteria panel.

Phase X Integration Requirements – The Contractor Shall:

1. Capture data usage metrics for individual (cached) weather layers. Over time, this metric data could be used to adjust cache settings on a layer-by-layer basis resulting in better user responsiveness (for higher use layers), and lower bandwidth (for lower use layers).

2. Create utilization metric capture mechanisms. The specific metrics desired are documented here https://otsf.sharepoint.com/sales/_layouts/15/WopiFrame.aspx?sourcedoc={FC827E16-

CA4A-4564-8A6D-

12CE020C0075}&file=AMC%20Metric%20Input.docx&action=default

3. Integrate alerts for refueling receivers that indicate when their assigned tanker is late to take-off, and vice versa.

4. Extract the new KC-46 'diverting’ indication from MEIS and drive a KC-46 unique Alert.

Presumes the indication is in a service GLADS doesn't already ingest.

5. Integrate MEIS 4 Sortie Cargo service for 'actual' load data.

6. Generate an alert when pre-departure payload (from GATES) is different than active plan payload.

https://otsf.sharepoint.com/sales/_layouts/15/WopiFrame.aspx?sourcedoc=%7bFC827E16-CA4A-4564-8A6D-12CE020C0075%7d&file=AMC%20Metric%20Input.docx&action=default https://otsf.sharepoint.com/sales/_layouts/15/WopiFrame.aspx?sourcedoc=%7bFC827E16-CA4A-4564-8A6D-12CE020C0075%7d&file=AMC%20Metric%20Input.docx&action=default https://otsf.sharepoint.com/sales/_layouts/15/WopiFrame.aspx?sourcedoc=%7bFC827E16-CA4A-4564-8A6D-12CE020C0075%7d&file=AMC%20Metric%20Input.docx&action=default

UNCLASSIFIED

7. Integrate "Overflight DST" business rule logic maintained by the AMC DIPS team and expand baseline DIPs stoplight/drill-down capability to include GDSS 'Remarks' fields based on those business rules.

8. Record when users confirm checklist items for post-mission review. Retain for a configurable time.

9. Establish RSS feeds that alert users and automatically open preconfigured UDOPs when specific world events occur (e.g. earthquake).

10. Add classified aerial refueling track locations to existing refueling track logic.

11. "IT Box" requirements for Phase IX. AMC and AGI will coordinate throughout the

Phase IX period-of-performance to prioritize this content, focusing first on emerging high priority end user needs, then on high priority small scope backlog requirements.

12. Integrate visual radar feeds for airfields from OWSs.

13. Utilize climatology from 557th for long range airfield forecasts when TAFs and gridded binary data isn't available.

14. Display & analyze ROBE and ROBE extension (comm bridge) coverage zones based on link characteristics and terrain masking. Allow for both live fly and mission planning purposes.

15. Package track data into a widely accepted format (potentially CZML, CoT, KML, etc.)

for export. This requirement does not include export of WMS / REST data.

14.0 ANNEX 2

USTC Notional Phase Requirements Description

Phase VI USTC Integration Requirements – The Contractor Shall:

1. Obtain USTRANSCOM Major Movement groupings of ULN and sortie information either from data services provided by USTRANSCOM Single Mobility System (SMS) or exported files containing the listing groupings of information.

2. Integrate USTRANSCOM Major Movement groupings into GLADS user interface as a user selectable filter set such that each Major Movement is grouped under each supported Combatant Command (CCMD) along with all sorties associated and aggregated passenger and cargo closure summary.

3. Provide summary graphic of USTRANSCOM Major Movements, grouped by supported CCMD, which displays each Major Movement as on-time or late defined by the estimated closure of cargo and personnel as compared to the ULN’s Latest Arrival Date

(LAD).