Attch 1- RMRC_PWS.pdf

Section F - Deliveries or Performance

PERFORMANCE WORK STATEMENT 16 August 2020

Remote Manifesting Resolution Center (RMRC) Performance Work Statement (PWS)

Name: Remote Manifesting Resolution Center (RMRC)

Organization: HQ AMC A4TI, AMC Transportation Systems & Data Management Branch

Address: 402 Scott Drive, Unit 2A2, Scott AFB IL 62225

1. PURPOSE

The overall purpose/objective of this contract is to provide services necessary enabling functional, technical, and analytical support for execution and management of the RMRC for Headquarters (HQ) Air Mobility Command (AMC) located at Scott AFB, IL. This support is divided into two main categories: Functional, Technical, and Analytical Support and Project Management Support.

2. SCOPE

This PWS outlines the breadth of services and related management support functions for the United States Air Force (USAF), AMC Directorate of Logistics, Transportation Division, Transportation Systems and Data Management Branch (A4TI) located at Scott AFB, Illinois.

The A4TI branch acts as the USAF functional manager for the Global Air Transportation Execution System (GATES).

3. REQUIREMENT(S)/DESCRIPTION OF SERVICE(S)

3.1. Functional, Technical and Analytical Support. The contractor shall:

3.1.1. Utilize, but not limited to the following Information Management and software tools:

• Defense Enterprise Accounting and Management System (DEAMS)

• Distribution Component Billing System (DCBS)

• Global Air Transportation Execution System (GATES)

• Integrated Development Environment GTN Conveyance (IGC)

• Global Decision Support System (GDSS)

• C2Remedy

• Hyperion

• Toad Data Point

• Microsoft Office products

• SharePoint

• Electronic Advance Passenger Information System (eAPIS)

• eSecure Flight

• Transportation Management System (TMS)

*The list above is inclusive of any follow-on version(s) or updates.

3.1.2. Perform Department of Homeland Security (DHS), Transportation Security Administration (TSA) eSecure Duties to electronically transmit and screen passengers using TSA e-Secure Flight per Defense Transportation Regulation (DTR) Part 1, Chapter 103, Section Paragraph O for stations or locations who do not have GATES or direct access to eSecure capabilities. ESecure Duties are considered Mission Essential, as defined in section

7.8. This task shall be accomplished as required 24 hours per day, 365 days per year.

3.1.3. Identify, analyze, trouble-shoot and resolve interface issues concerning applicable Automated Information Systems (AIS). Maintain manual manifesting aides and post to the A4T SharePoint site. This task shall be accomplished as required 24 hours per day, 365 days per year.

3.1.4. Maintain manual passenger and cargo manifesting automated tools/products.

3.1.5. Maintain A4T web information management sites (ex. Sharepoint, MS Teams, web page resources). The contractor shall receive all requests for outside agency access to air transportation web information sites, process the requests through staff agencies, sponsor persons approved by the information owners for access and maintain records of the sponsorship. Maintaining A4T web information management sites are considered Mission Essential, as defined in section 7.8. This task shall be accomplished as required 24 hours per day, 365 days per year.

3.1.6. Facilitate overall process improvement for data collection, input, analysis, presentation, and record keeping processes at Air Terminal Records and Reports functions world-wide.

3.1.7. Provide AMC Data Records Transportation services in accordance with (IAW) Air Force Instruction (AFI) 24-605, Volume 2 Section 4B assisting and training personnel 24/7

(365) when necessary in data records functions, and ensuring all data records functions are performed effectively. The Contractor shall provide a Summary Report of Data Records Management Activity.

3.1.7.1. Perform manifest register management IAW AFI 24-605, V2 Section 4B, paragraph 4.37, and all applicable Data Records updates in future volumes/messages. The Contractor shall provide a Summary Report of Reconciled Passenger and Cargo Manifests.

3.1.7.2. Maintain a file plan IAW Air Force Records Information Management System (AFRIMS) for the storage of all required documents.

3.1.8. Assist GATES users, GATES sites, and combat command and service operated fixed and remote manifesting locations (estimated total of 169 locations) for general air manifesting, record keeping and report guidance related to manual passenger and cargo manifesting when automated airlift information systems (electronic) means are not available. This is to ensure that cargo and passenger movement data is effectively populated in the USTRANSCOM Integrated Data Environment (IDE) / Global Transportation Network (GTN) Convergence (IGC) per the Defense Transportation Regulation, Part II Cargo movement and Part III passenger movement. The Contractor shall create a Report of Manual Manifesting Activity.

Performance Work Statement tasks 3.1.8 and subparagraphs shall be provided 24/7 (365).

Provide assistance to GATES users are considered Mission Essential, as defined in section 7.8.

This task shall be accomplished as required 24 hours per day, 365 days per year.

3.1.8.1. For fixed/strategic Aerial Port of Embarkation (APOE) AMC aerial port locations with GATES: When GATES is unavailable the contractor shall assume the role of that aerial port; and shall input cargo and passenger transportation data into GATES. The contractor shall use passenger/cargo transportation data to create air and surface manifests on departing aircraft and/or cargo surface conveyances from the affected location.

3.1.8.2. For locations without GATES supporting Transportation Working Capital Fund (TWCF) Channel missions: Input cargo and passenger transportation data into GATES. Data shall be used to create air and surface manifests on departing aircraft and/or cargo surface conveyances from the affected aerial port. This ensures the correct data is in the Defense Transporation System (DTS) to facilitate in-transit visibility (ITV) and billing to recover TWCF funds.

3.1.8.3. For service owned/operated locations without GATES. Primarily a unit-move/ contingency operation; contractor shall enter cargo and passenger transportation data into GATES to facilitate the interface with the USTC IGC system for ITV in accordance with in transit visability provisions detailed in the Defense Transportation Regulation (DTR). No locations will be supported without vetting and coordination with the COR.

3.1.8.4. Support airlift locations with deployment/redeployment forces that typically utilize remote tools or some form of automated transportation system hardware/software to capture and submit passenger and cargo movement to IGC. When units are unable to establish communication/manifesting capability, the contractor will input cargo and passenger transportation data into GATES. Airlift users will provide data that shall be used to create cargo and passenger manifests on departing aircraft from the affected aerial port/loation. No locations will be supported without vetting and coordination with the COR.

3.1.8.5. Monitor all Aerial Port GATES sites passenger suspense listings for erroneous or missing Customer Identification Code (CIC) billing data as required by HQ AMC.

3.1.9. Provide a Summary Report of Missing Passenger and Cargo Manifests fed between the GATES and DCBS systems interface that are in a missing status for more than seven (7) days.

3.1.9.1. Facilitate expeditious manifest interface data flow from GATES to DCBS for billing and reconciliation.

3.1.9.2. Facilitate aerial ports’ reduction of missing/unreconciled manifest delay times to less than seven (7) days by investigating the cause and coordinating their activities with the responsible aerial port to rectify the discrepancy.

3.1.10. Monitor all GATES locations over/short shipment reports on a weekly basis. Provide assistance to locations to resolve over/short shipment issues.

3.1.11. Provide an Over/Short Shipment Report showing trends of Aerial Port excessive over/short shipments IAW AFI 24-605, V2 Section 3G, paragraph 3.58 and 3.59 and all applicable updates in future policy.

3.1.12. When requested by the COR, the contractor shall collect, analyze, and report data relative to worldwide Air Transportation activity. The contractor shall provide Ad Hoc Data Requests supporting new requests for aerial port specific data to support executive level decisions. Requests for Ad Hoc Data Requests may come outside of the Government normal working hours. Analyze and report data relative to worldwide air transportation activity are considered Mission Essential, as defined in section 7.8.

3.1.12.1. The contractor shall conduct analysis of informational elements contained in the Global Air Transportation Execution System (GATES) database and other sources to include information/data in the defense transportation systems such as GDSS, JOPES, IGC and the Global Command and Control System (GCCS).

3.1.12.2. The contractor shall perform predictive analysis that requires the use of analytical methods to predict or forecast the impact to the global Air Mobility Transportation

Enterprise based on anticipated changes fluctuations in demand, airlift capacity or policy.

This may require the use of daily/weekly/monthly matrices and/or dashboards for display to Air Transportation Enterprise functional areas.

3.1.13. Create Cargo and Passenger Metrics from utilization queries upon request. Creating cargo and passenger metrics are considered Mission Essential, as defined in section 7.8.

3.1.14. Maintain and manage the Reports Control System (RCS), AMC-A4T (M&Q), Monthly Station Traffic Handling Reports and the Workload Reporting System (WRS). Input Data for AMC Aerial Ports unable to access the application into the web-based WRS by the 20th of the month for the previous month. If a location is unable to access the Reporting System, the contractor shall manually input the data within 24 hours of receipt of the manual input. The contractor shall provide a Workload Reporting System Report.

3.1.14.1. Ensure user profiles are up-to-date.

3.1.14.2. Using either Government furnished systems produced standard report data or through the use of a commercial off the shelf software solution, the contractor shall provide the information through Ad Hoc Data Requests.

3.1.15. Contractor shall provide and maintain a Daily Shift Log.

3.1.16. The contractor shall attend meetings such as staff meetings and rapid improvement events as determined by the contractor and COR. The contractor shall provide Meeting Minutes.

3.1.17. Provide technical and functional database management and application testing support to correct GATES data quality issues and improve application functionality.

3.1.18. Provide Department of Homeland Security (DHS) passenger screening for AMC (GATES) passenger processing locations during systems and/ or communications outages.

This is a critical time-sensitive action that must be completed immediately but no later than 60 minutes prior to scheduled departure for the affected mission. Provide 24 hours a day, 7 days a week, 365 days a year coverage for DHS passenger screening for AMC locations during systems and/or communications outages are considered Mission Essential, as defined in section 7.8.

3.1.19. Operate AMC owned accounts (18 total) for the Transportation Security Administration’s (TSA) electronic Secure Flight (eSF). The contractor shall:

3.1.19.1. Upon receipt of eSecure input file, the contractor shall ensure the input file is properly formatted in accordance with DHS instructions. The contractor shall take the eSecure input file from the affected GATES location and electronically upload the file to the eSecure application for passenger vetting.

3.1. 19.2. Pass vetting results back to the affected location.

3.1. 19.3. Facilitate the resolution when an “Inhibited” or “Selectee” response is received in GATES based on receiving direct results from direct access with the TSA Secure Flight (eSecure) system when contacted by a passenger manfeisting agency in conjuunctiuon with policy and procedures directed by HQ AMC A4T through the COR.

3.1.19.4. Transmit passenger data to Customs and Border Protection’s (CBP) electronic Advanced Passenger Information System (eAPIS) for flights that will depart from or enter into the Customs Territory of the United States. Passenger data must also be transmitted to eAPIS in addition to eSF. Transmit passenger data to CBP advance passenger information system are considered Mission Essential, as defined in section 7.8.

3.1.19.5. Maintain sufficient user account/passwords to ensure 24/7/365 coverage.

3.1.19.6. Act as an eSF backup for locations when their GATES system is unavailable.

3.1.19.7. Enter the passenger data received from the aerial port into eAPIS for clearance.

3.1.19.8. Pass the results back to the affected aerial port.

3.1.19.9. Produce and maintain a DHS Log Summary to reflect each instance for submitting data to either eSF or eAPIS on behalf of an aerial port and to reflect the summary of all events entered into the DHS Log Summary.

3.1.20. Trace mishandled (lost, found, damaged, or pilfered) baggage AMC-wide, determine final action of case files, and compile statistical data for HQ AMC.

3.1.20.1. Perform the Baggage Resolution Center (BRC) functions IAW AFI 24-605, Volume 2, paragraph 2.118. These functions shall be performed 24/7/365.

3.1.20.2. Create, maintain, and dispose of Government-required records IAW Records Disposition Schedule (AFRIMS), Table 24-01, 24-02, and Global Air Transportation Execution System (GATES).

3.1.20.3. Provide the original record or a reproducible copy of any such record on-hand, within three (3) duty days of receipt of the request.

3.1.20.4. Audit and correct all case file errors and discrepancies within twenty-four (24) hours of discovery or notification.

3.1.20.5. Provide Baggage Resolution Center Daily Log.

3.1.21. The contractor shall, upon coordination with the COR, provide Web GATES support for aerial port locations supporting worldwide force movement in transit visibility requirements. Web GATES support is considered Mission Essential, as defined in section 7.8.

This task and/or sub tasks shall be accomplished as required 24 hours per day, 365 days per year.

3.1.21.1. Commission & decommission Web GATES sites on the RMRC GATES server.

3.1.21.2. Create a Work Area Security Officer (WASO) GATES account for each deployed site.

3.1.21.3. Monitor and provide support for each site to include monitoring cargo and passenger manifest registers.

3.1.21.4. Maintain a log of all Web GATES events. Events will be summarized in the Monthly Status Report.

3.2 Travel.

3.2.1. Frequent travel is not anticipated, but some short CONUS and Overseas travel may be required in support of the contract.

3.2.2. As a part of this contract, the contractor may be required to perform Temporary Duty (TDY) non-local travel (over 100 mile radius) to both CONUS and OCONUS locations. Travel is accomplished on a firm-fixed price basis and the Contractor shall fund any local travel. If travel is required to perform the requirements of the PWS, a modification will be negotiated at that time and executed by the Contracting Officer.

3.2.3. If contractor travels, upon return of the trip, the contractor shall submit a Trip Report of activities and details of the travel.

3.3. Program Management Support. The contractor shall:

3.3.1 The contractor shall designate one individual Point of Contact (POC) to manage the RMRC contract within five business days of award. This individual shall be the focal point for data collection , input, analysis, presentation, and record keeping of manifesting activities at all AMC designated Aerial Port sites as required by HQ AMC. If the individual is replaced, the contractor shall notify the Government COR with the new POCs information within five business days..

3.3.2. At a minimum, the designated POC shall meet with Government personnel monthly to discuss, at a minimum, projects status, metrics development and estimated completion dates, and identify, discuss, and resolve concerns/issues.

3.3.3. Provide a written Monthly Status Report.

4. INFORMATION ASSURANCE (IA) REQUIREMENTS

4.1. Information Assurance. The contractor shall ensure that all system or application deliverables meet the requirements of DoD and AF Information Assurance (IA) policy.

Furthermore, the contractor shall ensure that personnel performing IA activities obtain, and remain current with, required technical and/or management certifications at no additional cost to the Government..

4.1.2 System IA. For those solutions that will not inherit existing network security controls, and thus integrate an entirely new application system consisting of a combination of hardware, firmware and software, system security assurance is required at all layers of the TCP/IP DoD Model. The contractor shall ensure that all system deliverables comply with DoD and AF IA policy, specifically DoDI 8500.2, Information Assurance Implementation, and AFI 33-200, Information Assurance Management. To ensure that IA policy is implemented correctly on systems, contractors shall ensure compliance with DoD and AF Certification & Accreditation policy, specifically DoDI 8510.01, DoD Information Assurance Certification and Accreditation Process (DIACAP), and AFI 33-210, Air Force Certification and Accreditation Process (AFCAP). The contractor shall also support activities and meet the requirements of DoDI 8520.02, Public Key Infrastructure (PKI) and Public Key (PK) Enabling, in order to achieve standardized, PKI-supported capabilities for biometrics, digital signatures, encryption, identification and authentication.

4.1.3 Application IA. For those solutions that will be deployed to Infrastructure as a Service (IaaS), Platform as a Service (PaaS) or similar environments, and thus inherit existing network security controls, application security assurance is required at the Application layer of the TCP/IP DoD Model. The contractor shall ensure that all application deliverables adhere to Public Law 111-383, which states the general need for software assurance. Specifically, the contractor shall ensure that all application deliverables comply with the Defense Information Systems Agency (DISA) Application Security & Development Security Technical Implementation Guide (STIG), which includes the need for source code scanning, the DISA Database STIG, and a Web Penetration Test to mitigate vulnerabilities associated with SQL injections, cross-site scripting, and buffer overflows. The contractor shall also support activities and meet the requirements of DoDI 8520.02, Public Key Infrastructure (PKI) and Public Key (PK) Enabling, in order to achieve standardized, PKI-supported capabilities for biometrics, digital signatures, encryption, identification and authentication.

5. CONTRACTUAL REQUIREMENTS

5.1. Place of Performance. The primary place of performance is 402 Scott Drive, Unit 2A2, Scott AFB, Illinois.

5.2. Normal Hours of Operation.

The core duty hours for the Government are between the hours of 7:30 a.m. and 4:30 p.m. Central Standard Time, Monday through Friday, with the exception of federal holidays. Contractor personnel may be required to support short notice adjustments to the daily work hours. Contractor personnel shall rely on their firm’s guidance for alternate duty location for observed federal holidays, and in the event of early release during duty hours. Federal holidays are defined as the dates the following holidays are observed: New Year’s Day, Martin Luther King’s Birthday, President’s Day, Memorial

Day, Independence Day, Labor Day, Columbus Day, Veteran’s Day, Thanksgiving Day, and Christmas Day.

5.3. Items Incidental to the Place of Performance. The Government will furnish or make available working space, yellow lanyards (see paragraph 5.4), network access, and the following incidental equipment to include:

• Windows PC with Microsoft Office Suite (Outlook, Word, Excel, PowerPoint, etc.)

• Telephone (local/long distance calls authorized as dictated by contract performance requirements)

• Facsimile

• Copier

• Printer

5.4. AMC Contractor Lanyard. All contractor employees are required to wear Government provided yellow lanyards when performing PWS tasks on base, i.e., in the workplace or in meetings.

5.5. Training Requirements. Within 30 calendar days after contract start, all contractor personnel shall complete Antiterrorism Level I training, as required by DODI O-2000.16 Volume 1. 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 Force Protection Course (ZZ133079) at https://golearn.adls.af.mil/login.aspx

Certification Requirements. The on-site contractor performs Functional Support Administration (FSA) responsibilities that require him/her to meet and maintain training certification requirements for the information assurance functional categories/levels listed:

Information Assurance (IA). Contractor shall comply with all security requirements pursuant to DoD Instruction (DoDI) 8500.01, Cybersecurity, and DoD Directive 8140.01; Cyberspace Workforce Management. Contractor must ensure that all personnel assigned to work on the contract requiring access to Government networks must complete initial Information Assurance training within five days after the individual receives his/her Common Access Card (CAC), and subsequently annually. The training is accessed through the Advanced Distributed Learning System (ADLS) via a computer with a .mil account at https://golearn.adls.af.mil/kc/rso/login/ADLS_login.asp or through the AF Portal

IAT Category Training Requirements. The contractor shall, within the timeframe of the transition period, complete and/or acquire the following training, certification maintenance, continuing education, or sustainment training required for the information assurance functional responsibilities as follows:

• Anti-terrorism Level I

• electronic Advanced Passenger Information System

5.6. Data Rights and Non-Commercial Computer Software. In order to implement the provisions at DFARS 252.227-7013(b) and (e) and DFARS 252.227-7014(b) and (e) and DFARS 252.227-7017, the Contractor shall disclose to the ordering Contracting Officer and ordering office in any proposal for a contract, or after award of a contract if not previously disclosed in the proposal, any technical data or non-commercial computer software and computer software/source code documentation developed exclusively at Government expense in performance of the contract. This disclosure shall be made whether or not an express requirement for the disclosure is included or not included in the PWS or solicitation for the contract. The disclosure shall indicate the rights asserted in the technical data and non-commercial computer software by the Contractor and rights that would be acquired by the Government if the data or non-commercial software was required to be delivered under the contract and its CDRL requirements and any cost/price associated with delivery. This disclosure requirement also applies to segregable routines of non-commercial software that may be developed exclusively at Government expense to integrate Commercial Software components or applications provided under a commercial software license or developed to enable Commercial Software to meet requirements of this contract. Performance of this disclosure requirement shall be considered a material performance requirement under which such technical data or non-commercial computer software is developed exclusively at Government expense.

5.7. Software Support and Data Rights. Unless specified otherwise in the contract, the contractor shall fully support all unique software developed to support integrated solutions on this contract. The contractor shall be able to support all software revisions deployed or resident on the system, and sub-systems. The data rights ownership/licensing guidance is specified in Section I, Clause 252.227-7013 and 252.227-7015 in the overarching contract section B.

Defense Federal Acquisition Regulation Supplement Contract Clauses.

5.8. Section 508 of the Rehabilitation Act. The Contractor shall meet the requirements of the Access Board’s regulations at 36 CFR Part 1194, particularly 1194.22, which implements Section 508 of the Rehabilitation Act of 1973, as amended. Section 508 (as amended) of the Rehabilitation Act of 1973 (20 U.S.C. 794d) established comprehensive requirements to ensure:

(1) Federal employees with disabilities are able to use information technology to do their jobs, and (2) members of the public with disabilities who are seeking information from Federal sources will be able to use information technology to access the information on an equal footing with people who do not have disabilities.

5.9. Release of Information. The contractor shall not hold any discussions or release any information relating to this PWS to anyone not having a direct interest in performance of this PWS, without written consent of the contracting officer or designated representative of the contracting officer. 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. Public release of classified information is not authorized.

5.10. Protection of Information. In performance of their duties, the contractor may obtain access to sensitive, nonpublic information. The contractor agrees (a) to use and protect such information from unauthorized disclosure IAW the Federal Acquisition Regulations (FAR); (b) to use and disclose such information only for the purpose of performing of duties 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.

5.11. Privacy Act. Work on this project may require contractor personnel to have access to Privacy Information. Contractor personnel shall adhere to the Privacy Act, Title 5 of the U.S.

Code, Section 552a, and applicable agency rules and regulations.

5.12. Non-Disclosure Agreements. 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 in accordance with the 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/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 COR of any unauthorized release of such information. Upon request, the contractor shall have its employees assigned to this contract execute a non-disclosure agreement for delivery to the Government. The Government will require contractor personnel to sign a non-disclosure statement to protect non-public information of the Government. See Attachment 3 below.

5.13. Unauthorized Work. The contractor shall not accomplish work outside the scope of this PWS nor deviate from technical orders, manufacturers’ recommendations, Air Force Instructions or National Consensus Standards at the Government facility. The contractor shall not perform any other work, other than the work required under this contract PWS with the supplies, materials, or resources acquired or provided under this contract.

5.14. Compliance With Local, State And Federal Laws And Requirements. The contractor and the contractor’s employees are subject to, and shall abide by and comply with, all relevant statutes, ordinances, laws and regulations of the United States (including Executive Orders of the President) and any state (or other public authority now or hereafter in force).

The contractor shall observe and comply with all applicable federal requirements regarding Social Security, Worker’s Compensation, Unemployment Insurance and any other matter concerning employment applicable to the performance of this PWS or rules, regulations, directions and orders not inconsistent herewith as may from time to time be issued by the Government.

The unilateral act of any Governmental body against any employee of the contractor for the violation of a Local, State or Federal law or regulation (to specifically include persons barred by any appropriate military commander or Government authority) shall not excuse the contractor from full compliance with the terms and conditions of this contract.

5.15. Qualified Personnel. All personnel performing work under this PWS shall be fully trained to accomplish all services associated with this PWS.

5.16. Phasing. Key Personnel: The contractor shall provide a Startup, Phase in/Phase Out Plan. Provide assurance of ability to perform the requirements of the PWS and the ability to perform all duties starting on day one of the contract.

5.16.1 Phase In

5.16.1.1 To ensure a smooth transition in the change of work effort from the current contract if a new contractor is selected, the new contractor shall begin a 30-day Phase-In Period prior to the end of the existing contractor’s performance period.

5.16.1.2 The successor contractor will be allowed access to the facilities to familiarize supervisors, key personnel and staff with equipment, reporting, work scheduling and procedures.

However, such access shall not interfere with the production efforts of current personnel. To preclude such interference, arrangements for access to Government facilities shall be made with the Contracting Officer Representative (COR) and Contracting Officer (CO).

5.16.1.3 At the completion of the Phase-In Period, the successor contractor shall be fully capable of providing all services outlined in the PWS.

5.16.1.4 Access to Government computer systems requires additional national agency clearance checks. Common Access Cards (CAC) require background checks prior to issuance to successor contractor personnel. The process for this includes submitting personal information for each applicant to the Government's Trusted Agent for input into the Trusted Associate Sponsorship System (TASS). Successor contractor employees must clear a background security check before being issued a CAC. To avoid delays in starting work, it is imperative that the successor contractor, at the earliest possible time prior to contract start date, be proactive in submitting applications for personnel security clearances.

5.16.2 Phase-Out

5.16.2.1 The contractor shall provide a Phase-out Plan describing the method of transferring responsibility for tasks described in the PWS. The contractor shall cooperate fully with the Government and any successor contractor(s) to ensure an orderly transition through the end of this contract.

5.17. Safety. The contractor shall comply with the latest applicable Air Force, AMC, and Installation regulations, instructions, policies, management plans, and requirements regarding personnel health, occupational/operational safety and airfield operations. The COR shall provide copies of publications not available on the web and updates as they become available.

5.18. Non-Personal Services. The Government will neither supervise contractor employees nor control the method by which the contractor performs the required services. Under no circumstances shall the Government assign services 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 (CO) immediately. All decisions relative to programs supported by the contractor shall be the sole responsibility of the Government.

5. 19. Contractor Identification. The Government will provide security badges and passes for access to controlled areas upon verification of security clearances. The individual(s) shall be clearly identified as contractor employee(s).

All contractor/subcontractor personnel shall be required to wear AF-approved or provided picture identification badges so as to distinguish themselves from Government employees.

When conversing with Government personnel during business meetings, over the telephone or via electronic mail, contractor/subcontractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors/subcontractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, contractor/subcontractors occupying collocated space with their Government program customer should identify their work space area with their name and company affiliation.

5.20. Performance Reporting. The contractor’s contract performance will be monitored by the Government and reported in Contractor Performance Assessment Reports (CPARs) or a Customer Survey, depending on the dollar amount of the contract. Performance standards shall include the contractor’s ability to provide or satisfy the following:

• Provide satisfactory solutions to requirements with the necessary customer support

• Provide solutions and services that meet or exceed specified performance parameters

• Deliver timely and quality deliverables to include accurate reports and responsive proposals

• Ensure solutions to requirements are in compliance with applicable policy and regulation

5.21. Contract Kick-Off Meeting. The contractor shall initiate work by meeting with Government representatives and contracting to ensure a common understanding of the requirements, expectations, and ultimate end products. The contract kick-off meeting shall be scheduled within 15 days of award. The contractor shall discuss the overall understanding of the project and review the background information and materials provided by Government.

Discussions shall also include the scope of work, deliverables to be produced, how the efforts will be organized, and how the project will be conducted. A concerted effort shall be made to gain a thorough understanding of the Government expectations. However, nothing discussed in this or in any subsequent meetings or discussions between the Government and the contractor shall be construed as adding, deleting, or modifying any contract requirements, including deliverable specifications and due dates.

5.22. Records, Files and Documents. All physical records, files, documents, and work papers, provided and/or generated by the Government and/or generated for the Government in performance of this PWS, maintained by the contractor which are to be transferred or released to the Government or successor contractor, shall become and remain Government property and shall be maintained and disposed of IAW AFMAN 33-363, Management of Records; AFI 33- 364, Records Disposition – Procedures and Responsibilities; the Federal Acquisition Regulation, and/or the Defense Federal Acquisition Regulation Supplement, as applicable. Nothing in this section alters the rights of the Government or the contractor with respect to patents, data rights, copyrights, or any other intellectual property or proprietary information as set forth in any other part of the Application Services contract or this PWS.

5.23. Contractor Manpower Reporting. As required and when directed by the Contracting Officer in writing, the contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site.

6. Service Summary (SS) The Services Summary summarizes the most important performance objectives and performance thresholds (specific standards) as identified within the body of the PWS. The absence of any performance objective and threshold from this SS shall not detract from its enforceability nor limit the rights or remedies of the Government under any provision of the contract.

Performance Objective PWS Para Performance Threshold Provide accurate, complete, and timely production of reports, case files, and briefings for Technical Support

3.1. thru 3.1.21.4

Accurate reports and briefings provided by the scheduled due date 95% of the time. Information provided to be at least 95% accurate with no more than 5 errors. All inaccuracies corrected within one work day

Provide passenger screening for Space Available passengers using Transportation Security Administration, e-Secure Flight

3.1.2. Passenger screening required 100% of the time

Provide timely and satisfactory assistance to locations with/without GATES (fixed/deployed) for general aerial port guidance on manual passenger and cargo manifesting

3.1.8. thru 3.1.10. Accurate data entry with no more than 5 errors;

available in IGC 95% of the time at least 2 hours prior to departure

Provide accurate, complete, and timely production of reports and briefings for Program Management Support

3.3. thru 3.3.3. Accurate reports and briefings provided by the scheduled due date 95% of the time. Information provided to be at least 95% accurate with no more than 5 errors. All inaccuracies corrected within one work day

Provide accurate processing of passenger baggage clains

3.1.20. thru 3.1.20.1 and 3.1.20.5

Accurate reports and briefings provided by the scheduled due date 95% of the time. Information provided to be at least 95% accurate with no more than 5 errors. All inaccuracies corrected within one work day

Provide Ad Hoc Data Requests 3.1.12 Accurate reports and methodology for the implementation of analytical processes in order to gather, process, and disseminate recurring and specially requested mission data and informational products with 90% accuracy under very stringent timelines.

Provide Web Services 3.1.5 Act as the primary focal point for design, application, user access and permissions based on applicable government policy, and maintaining Air Transportation Web Resources. Information provided to be at least 95% accurate with no more than 5 errors. All inaccuracies corrected within one work day.

7. SECURITY REQUIREMENTS

7.1. Secret Clearance. The Government will provide access to facilities consistent with security clearances and a need-to-know. Contractor personnel must possess a Security Clearance granted by the DOD and their parent contractor facility must also have the appropriate Facility Clearance IAW DoDM 5220.22M prior to performing work on any classified Government systems or products. All contractor personnel supporting this requirement shall have a SECRET security clearance. Personnel must obtain security clearances prior to contract award. Any replacement contractor personnel must obtain the appropriate security clearance prior to supporting this requirement. Assigned contractor personnel shall not have any open Joint Personnel Adjudication System (JPAS) issues/comments prior to working PWS tasks.

Contractor shall comply with all appropriate provisions of applicable security regulations.

Specific security requirements are identified in the DD Form 254, DOD Contract Security Classification Specification. For access to unclassified AF networks only, contractor must, at a minimum, have a completed verifiable T-1.. The contractor shall establish and maintain security requirements and procedures to ensure this security level is maintained at all times. The contractor will be given access to applicable documentation to include requirements, plans, specifications, studies, and analyses up to and including SECRET classification.

The contractor shall transmit and deliver classified material/reports IAW the National Industrial Security Program Operating Manual (DoDM 5220.22-M). These requirements shall be accomplished as specified in this contract. All classified work will occur at a Government location or another cleared contractor’s facility.

The contractor must possess or obtain an appropriate facility security clearance as identified below prior to performing work on a classified Government contract: (SELECT ONE)

Top Secret Secret

7.2. Security Clearance. The Government will coordinate the issue of required CAC and Controlled Area Badges. The contractor shall submit all names of contract employees to the Scott AFB Security Services Center (SSC) for vetting through Joint Personnel Adjudication

System (JPAS) to ensure investigative and clearance requirements have been satisfied. This shall be completed before the COR personnel /Trusted Agent (TA) accesses the DOD Contract Verification System (CVS) and submits requests for issuance of CACs to the contract employees. If a contract employee does not have the required investigative or security clearance level, the contract employee will be denied the ability to work in support of this PWS, and the employee’s information will not be loaded into CVS.

7.3. Return of Government Issued Supplies, Equipment, and Materials. Upon completion of this contract, the employee shall surrender all Government supplies, materials and equipment to the COR. All contract employees assigned to this contract who possess CAC cards shall return these cards to the COR at Scott AFB for turn-in to the appropriate Scott AFB Security office. Assigned contract employees who possess any security badges shall turn these badges in to the COR in person during out-processing. Contract employees shall out-process on the last day of the contract or upon termination or reassignment from duties.

7.4. Contractor Employee Vetting. 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. 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 Scott Visitor Control Center, if requested.

7.5. Roles and Privileges. The Government shall ensure the roles/privileges assigned to contract employees on the Government computing platforms are limited to the roles/privileges essential to that individual’s performance of his/her assignments. The Government may limit or revoke these roles or privileges for any reason.

7.6. Contractor Employee Conduct. Contractor personnel shall be removed and barred from the worksite if the Government notifies the contractor that the employment or the continued employment of the individual is prejudicial to the interests or endangers the security of the United States of America during the course of the contract period.

7.7. Badges. The contractor is required to provide identification badges for their employees.

All contractor personnel must 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 COR personnel. The contractor’s identification badge shall not be used as an entry requirement for installation entry or into any Government designated controlled or restricted area.

7.8. Mission Essential Designation. Certain personnel will be designated as Mission Essential Personnel. Contractor shall ensure personnel required to accomplish tasks designated as Mission Essential Personnel report to assigned work locations and perform required tasks, regardless of weather, security conditions, or delectation of health protection conditions. The Government has identified ESECURE DUTES (section 3.1.2), MAINTAIN A4T WEB INFORMATION MANAGEMENT SITES, (section 3.1.5), PROVIDE ASSISTANCE TO GATES USERS (section 3.1.8), ANALYZE AND REPORT DATA RELATIVE TO WORLDWIDE AIR TRANSPORTATION ACTIVITY (section 3.1.12), CREATE CARGO AND PASSENGER METRICS, (section 3.1.13), PROVIDE 24 HOURS A DAY, 7 DAYS A WEEK, 365 DAYS A

YEAR COVERAGE FOR DEPARTMENT OF HOMELAND SECURITY (DHS)

PASSENGER SCREENING FOR AMC LOCATIONS DURING SYSTEMS AND/ OR

COMMUNICATIONS OUTAGES, (section 3.1.18), TRANSMIT PASSENGER DATA TO

CUSTOMS PROTECTION AND BORDER PROTECTION (CBP) ADVANCE PASSENGER

INFORMATION SYSTEM (eAPIS), (section 3.1.19.4), PROVIDE WEB GATES SUPPORT FOR AERIAL PORT LOCATIONS, (section 3.1.21) services as Mission Essential. The contractor shall provide a list of essential personnel required to perform the tasks to CO and COR no later than 10 business days after contract start. The contractor will maintain this list with updates provided to the CO and COR with any personnel changes or as required. The CO and/or COR will be responsible for providing Government security personnel with list of contractor Mission Essential Personnel to enable access to Government facilities when non-essential personnel are barred. Contractor shall operate IAW DFARS 252.237-7023 Continuation of Essential Contractor Services. Mission Essential Personnel are personnel allowed to enter Scott AFB during periods of restricted access as designated by the Base Commander. Contractor personnel may be required to relocate to alternate locations within the CONUS or OCONUS in the events of a critical occurrence. The contractor shall be required to participate in disaster, emergency preparedness, and Continuity of Operations (COOP)/Failover exercises

7.9. Property Protection. Property protection for the facility where the contractor’s 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. If the contractor’s failure to use reasonable care causes damage to or loss of any Government property, the contractor shall replace or repair the damage at no expense to the Government as the CO directs.

If the contractor fails or refuses to make such repair or replacement, the contractor shall be liable for the cost. All Government provided products remain the property of the Government and shall be returned upon completion of the support services. Contractor personnel supporting this requirement shall return all items that were used during the performance of these requirements by the end of the performance period.

7.10. Safeguarding Unclassified and/or For Official Use Only (FOUO) Information.

Contractor shall meet Air Force standards for storing, processing, and handling classified information and systems, IAW AFI 16-1404, Air Force Information Security Program.

Additionally, all resources (e.g. maps, publications/ instructions, photos) provided by the

Government to assist contractor in the performance of the contract shall be surrendered upon termination of employment or the end of the contract performance period. The contractor shall safeguard information IAW DoDI 5200.48 and AFI16-1404_AFGM2020-01.

7.11. Contractors Working in Controlled or Restricted Areas. In the unlikely event that a contractor requires access to the controlled or restricted area, the Government will ensure escort(s) are provided for the contractor at all times when within a controlled or restricted area.

Contractors may act as escort officials under certain circumstances. The contractor must have an issued AF Form 1199 and 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.12. Access to Government Facilities with Controlled or Restricted Areas. The contractor must comply with security regulations imposed by the installation commander and/or the agency responsible for the project location.