PWS Visible Accessible Understandable Linked Trusted (VAULT) SME Support_Final.docx

Attachment 1

FA5000‐XX-X-XXXX

FA7014‐XX-X-XXXX

PERFORMANCE WORK STATEMENT

FOR

Visible Accessible Understandable Linked Trusted (VAULT) SME Support

AT

JOINT BASE ANDREWS, MARYLAND

04 March 2020

FINAL

Contents

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General. The Director, Air Force Chief Data (SAF/CO), pursuant to 10 U.S.C. §§ 8031-8038, and as authorized by AFMD 1, Headquarters Air Force, and this Headquarters Air Force Mission Directive, assists the Under Secretary of the Air Force (USecAF), other Secretariat offices, the Chief of Staff of the Air Force (CSAF), and the Vice Chief of Staff of the Air Force (VCSAF) in leading, carrying out, reviewing, and ensuring the visibility, accessibility, understanding, sharing, and trustworthiness of data across air, space, and cyberspace domains. The CDO represents both the SecAF and CSAF in senior venues associated with the optimization of the use of AF data and the operationalization of associated plans and capabilities. He/she serves as a member of the Air Force Corporate Structure and the Air Force Council. Within his/her areas of responsibility, the CDO prepares policies for approval and issues official guidance, procedures, compliance items, and directed actions to ensure implementation of those policies.

SECTION II

2.0 TASK AREA DESCRIPTIONS

The Contractor shall provide all services, materials, supplies, equipment, and project supervision, as required in connection with this Performance Work Statement (PWS).

2.1 Data Acquisition, Preparation & Architecture. The contractor shall perform tasks necessary to acquire data and develop a scalable technical architecture necessary to enable consumption of prepared datasets by the analytical and/or systems development communities in both cloud and on premise environments at multiple security classification levels up to Special Access Programs (TS/SCI, SAP). For example, develop data export standards and perform Extract-Transform-Load activities to maximize dataset exploitability, populate the Enterprise Information Model with metadata aspects (catalog, glossary, attributes, business rules), perform data feed automation using industry standard tools like Kylo and NiFi, data sets, perform data quality and curation activities, generate synthetic data sets for AI/ML algorithm training, synthesize multiple data sets into common formats for efficient storage and rapid processing (e.g. SQL to parquet), ensure data sets are machine readable, tagging data for transport data up and down across multiple security classification levels, etc.

2.1.2 Data Acquisition. The contractor shall perform or facilitate services relating to well-managed coordination between data originators and data system owners as necessary to acquire or connect to operational systems for data analysis purposes. This includes, but is not limited to, developing relationships with data originators and system owners to facilitate the exposure of USAF data across the enterprise; editing the documentation outlining procedures and agreements between data originators, system owners, CDO, and authorized consumers; producing technical justification for product acquisition including both software license procurement and cloud environment hosting costs, be they DISA MilCloud 2.0, Azure GovCloud, or AWS GovCloud; communicating data extraction/movement standards, and/or contributing to the technical extraction of data sources from source databases and Authoritative Data Sources. This requirement includes Data Transport (e.g. Snowballs, Courier services, Cloud exfill) at multiple security classification levels up to TS/SCI/SAP.

2.1.3 Data Preparation. The contractor shall perform all Data Preparation tasks necessary to transform data from its raw form into a format ready for consumption by the analytical and/or systems development communities in both cloud and on premise environments. Data preparation must also be done in support of the Chief Data Office’s statutory responsibilities to comply with the Federal OPEN Data Act. These tasks include, but are not limited to: data feed automation using industry standard tools, data tagging, metadata tagging, data export standards, data quality application and business rule creation, data munging and wrangling in support of machine learning tools and techniques, and performing advanced Extract-Transform-Load activities to maximize dataset exploitability. The contractor shall comply with Department of Defense and Joint Force Headquarters data practices as well as inform USAF data preparation and modeling best practices across enterprise. This requirement applies to all network classifications up to TS/SCI/SAP and connections.

2.1.4 Data Environment Architecture. The contractor shall develop a scalable technical environment architecture necessary to enable consumption of prepared datasets by the analytical and/or systems development communities. This includes identifying hardware (physical, virtual, hypervisor, containers, lambda or other serverless functions), software, tools and applications related to developing a data service enterprise technical architecture. This architecture shall not result in reduced performance of operational / transactional systems because of increased data consumption workloads. Additionally, the architecture will leverage artifacts produced by data originators, system owners, data preparation teams, and data modeling and documentation teams to maximize effectiveness of exposed datasets. The architectural solutions proposed must comply with Air Force Software Factory Best Practices (Agile development, Continuous Integration, Continuous Delivery (CI/CD) pipeline lifecycle, Continuous ATO Risk Management Framework certification, CloudONE, PlatformONE, DataONE, WrapONE, AI/SmartONE, FuseONE Advanced Battle Management System alignment). This requirement applies to all network classifications up to TS/SCI/SAP and connections.

2.1.5 Technical, Education, and Training Services. The contractor shall offer technical advisory, education & training services relating to data preparation and modeling ensuring raw data is being effectively transformed into an exploitable information asset. The contractor shall possess extensive expertise in Extract-Transform-Load and data modeling. The contractor shall inform USAF data preparation and modeling best practices across enterprise. This requirement applies to any network classification or connection.

2.2 Agile Algorithm Solutions. The contractor shall develop algorithms for execution on cloud and on premise infrastructure to enable exploitation of USAF enterprise or mission-specific datasets to include production and experimental design that ensure maximum effectiveness to serve the USAF data consumers and enabling data integration and analysis across the enterprise. The contractor shall support establishment of a Continuous Integration, Continuous Delivery Development Operations pipeline for Analytics using DevSecOps agile methodology. The contractor shall apply machine learning and artificial intelligence principles using open source or COTS frameworks in R, Python, or other language libraries supported by the Air Force VAULT Data Platform.

2.2.1 Analytics Partnerships. The contractor shall evaluate new data science/analytics products and vendor frameworks for relevance and usability/insertion into the data environment. The contractor shall also provide engineering estimates for network capacity requirements, cost/budget estimates for mission problem sets provided, and support for the definition and execution of data-centric use-cases including staffing with data science experts engaged and knowledgeable in functional communities and capable of solving complex mission problems using appropriate data analysis techniques to include compilation, aggregation, linear programming, complex statistical analysis, visualization, machine learning, artificial intelligence, and other advance analytical processes and tools.

2.2.2 Data Service Operations. The contractor shall influence and/or establish USAF best practices in data environment development, capability exposure, and system sustainment measures. All solutions developed shall result in a capability force multiplier to the USAF. The contractor shall develop web services exposing, communicating and exploiting data capabilities to the USAF systems development and analytical communities enabling data integration and analysis across the enterprise to enable data-driven decisions at all levels. The contractor shall develop, collect, and report metrics on the state of Air Force enterprise datasets as they are managed across the air, space, and cyberspace domains, collected or federated to the enterprise, and reported to the Department of Defense in compliance with the OPEN Data Act. The contractor shall support operational issue resolution with the capabilities deployed in support of the Data Science Reference Architecture and in the execution of Use Cases. The contractor shall establish a Data Operations Center for centralized issue management, reporting, and resolution. The contractor shall operate an Issue Management system for data-related activities across the Air Force enterprise and generate regular (weekly, monthly) metrics against the data-related activities across the enterprise. This requirement applies to all network classifications up to TS/SCI/SAP and connections.

2.2.3 Data Service Sustainment. The contractor shall provide senior product expertise, security patch administration, and Risk Management Framework (RMF) artifact creation for the Data Service Reference Architecture capabilities deployed across the Air and Space Force enterprise. The contractor shall support the Certification and Accreditation (C&A) of environments enabling data preparation, analysis environments designed to transform USAF data into strategic assets. The contractor’s efforts shall include, but not limit to, C&A artifact development and process oversight. This requirement applies to all network classifications up to TS/SCI/SAP and connections. The contractor shall provide mission user familiarity training on the Data Service Reference Architecture capabilities deployed and educate potential users on how to take maximum advantage of the capabilities for their specific mission vertical and/or problem space.

2.3 Data Governance. The contractor shall provide expertise to develop data maturity models that account for the entire lifecycle, conduct maturity assessments, develop data models that support data management, apply design concepts to create reliable data storage environments, apply metadata management principles and develop data quality techniques that ensure data is fit for its intended purposes. The contractor shall provide expertise in the areas of data stewardship, ownership, and data management policy that enable decision makers at all levels to make better operational and strategic decisions. The contractor shall author policy documents essential to strategic concept adoption and operational and tactical execution success for the Air Force Enterprise. Documentation will include, but is not limited to, ISSM Entity Relationship Diagrams (ERD), enterprise data dictionary, meta-data repositories, and data environment standard operating procedures. Support senior leader governance forums and facilitate large, recurring, multi-organization, multi-level collaborations to iteratively improve the understandability, provenance, registration, tagging, publication, protection, consumption, exploitation, and weaponization of Air Force and all-source data needed to enable Digital Air Force functions and missions. The contractor shall provide secretariat support for established Governance fora including managing membership rosters, regular communications across the governance structures (AF Data Council, AF Data Board, and various Working Groups), addressing appropriate General Officer and Senior Executive Service protocol actions, coordinating, collecting, generating and distributing read-ahead materials, and publication of minutes, lessons learned, and tracking action items following events. This requirement applies to all network classifications up to TS/SCI/SAP and connections.

2.4 Data Analytics. The contractor shall conduct data analytics using state-of-the-art mathematical and machine learning/artificial intelligence techniques to support exploitation and understanding of data both within specific mission domains and across the Air and Space enterprise in order to improve effectiveness in operations and support data-driven decisions. The contractor shall provide support for complex analysis of multiple data sets across a diverse range of mission functional areas. The contractor shall develop dynamic visualizations exploiting available, curated data sets using a variety of visualization tools or custom-developed scripts to meet mission needs and provide continually-current mission dashboards for commanders at all levels across the Air Force Enterprise. The contractor shall guide the government’s capabilities to achieve various levels of technical sophistication ranging from business intelligence to state-of-the-art applied mathematical and machine learning/artificial intelligence techniques. This requirement applies to all network classifications up to TS/SCI/SAP and connections.

2.5 Data Environment Development. The contractor shall perform or facilitate services relating to developing solution architectures based on cloud-agnostic, vendor-agnostic, open-source, requirement-driven product selections, all designed to securely design, build, deploy, operate and sustain enterprise-quality, commercially-used data science tools and services in accordance with the published AF Data Services Reference Architecture. The contractor shall perform or facilitate services relating to technical infrastructure design enabling large scale analysis, exposure and exploitation of USAF data to analytic and systems development communities. The contractor shall develop USAF best practices and guide the community to realize the benefits of scalable infrastructure without impacting business operations. The contractor shall develop Data Science Reference Architecture capability requirements documents, project management plans, and cost estimates for implementation of new products and services filling gaps in or enhancing the usability of the data in the enterprise environments. The contractor shall apply the Agile development philosophy described in paragraph 2.2 Agile Algorithm Development for all new capabilities deployed. This requirement applies to all network classifications up to TS/SCI/SAP and connections.

2.5.1 Data Environment Management. The contractor shall document and establish all appropriate operational and support capabilities needed for a world-class analytics environment to include configuration, license management, release management, user account management, requirements management, and operational metrics reporting. The contractor must be able to operate and sustain these tools wherever needed on NIPR, SIPR, JWCS, CENTRIX, DREN, S-DREN, FENCES, or other SAP/SAR or forward-deployed environment. Contractor must leverage agile DevSecOps practices, processes, and tools for capability development, project management, and status reporting.

2.5.2 Applied Research, Data Development & Testing. The contractor shall identify requirements, plan and conduct research and analyses of alternatives and develop and test new and innovative tools, techniques and methodologies to enhance AF data analytics capabilities ranging in technical sophistication from business intelligence to state-of-the-art applied mathematical and machine learning/artificial intelligence techniques. The contractor shall perform experimental research and development using proven, state-of-the-art, and novel approaches to exploiting USAF enterprise data to improve operations and sustain mission effectiveness.

2.6 Deliverables. The contractor shall provide task order deliverable(s) in a format mutually agreed upon by the Government and the Contractor. The Contracting Officer does not require copies of listed deliverables with the exception of the Non-Disclosure Agreements (NDAs). If a deliverable due date falls on a weekend or holiday, the Contractor shall submit the deliverable on the last work day prior to the due date.

2.6.1 Program Management Plan. The contractor shall provide a draft Program Management Plan at the time of the kickoff meeting.

SECTION III

3.0 SERVICE SUMMARY

The contractor service requirements are summarized into performance objectives that relate directly to mission essential items The performance threshold briefly describes the minimum acceptable levels of service required for each requirement and will be assessed on an “Acceptable” or “Unacceptable” basis. These thresholds are critical to mission success.

SS – 1

Data Prep & Architecture

SS – 2

Agile Algorithm Solutions

SS – 3

Data Governance

SS – 4

Data Analytics

Configuration Control Board review and approval of artifacts

SECTION IV

4.0 DELIVERABLES

The contractor shall provide task order deliverable(s) in a format mutually agreed upon by the Government and the Contractor. The Contracting Officer does not require copies of listed deliverables with the exception of the Non-Disclosure Agreements (NDAs). If a deliverable due date falls on a weekend or holiday, the Contractor shall submit the deliverable on the last work day prior to the due date.

The following enumerated deliverables are not expected to change. Due Date intervals are not expected to change but actual dates may need to be revised depending on actual contract/task order start dates.

4.1 A Monthly Status Report will be furnished for all projects due on the 10th business day of each month followed by a Monthly Status Meeting to be scheduled the following week. Minutes for these meetings are due within no later than one business day after the meeting.

(1) business days after the meeting By email to the COR in Microsoft Word format

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL, INFORMATION, OR SERVICES

5.1 Government Furnished Property, Equipment, Material, Information, or Services. The Government will not furnish property or services for this requirement.

5.2 Contractor Acquired Property. The contractor will not be required to acquire any property.

SECTION VI

6.0 GENERAL INFORMATION

6.1 Scheduling Concerns.

6.1.1 Duty Hours. The contractor shall have access to Government facility five days per week, Monday through Friday, eight hours a day, except when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings, unless otherwise approved. Contractor personnel are expected to conform to customer agency normal operating hours; however the Contractor may be required access to Government facility outside of duty hours based on the customer agency’s needs. As a baseline, Contractor personnel shall work 8 hours per day, 40 hours per week. Compensatory time arrangements are permissible for temporary spikes in worktime; but overtime pay is prohibited without COR and CO approval. Federal Holidays shall be observed in accordance with Office of Personnel Management policy.

6.1.2 Core Duty Hours and Base Shutdown/Inclement Weather. Core duty hours are 0800 - 1600, Monday through Friday (excluding federal holidays). The Contractor shall follow guidance of the installation containing their place of performance to determine reporting schedules whether due to a base closure or inclement weather. The website for guidance regarding status of performance for work to be performed in the National Capital Region (NCR) is http://www.opm.gov/status/.

6.2 Kickoff Meeting/Orientation Meeting

6.2.1 The contractor shall schedule and coordinate a Project kick-off Meeting no later than (NLT) five (5) calendar days after contract award at the location approved by the Government. The meeting will provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract. The meeting will provide the opportunity to discuss technical, management, and logistic issues; travel authorization; communication process between Government and Contractor; and reporting procedures. At a minimum, the attendees shall include key Contractor personnel, SAF/CO, key Government representatives, and the COR. The Contractor shall provide a Kick-Off Meeting Agenda that will include, but not be limited to, the following.

6.2.2 The contractor shall provide a draft copy of the agenda NLT 3 days after contract award for review and approval by the COR prior to finalizing. The Government will provide the Contractor with the number of participants for the kick-off meeting and the Contractor shall provide sufficient copies of the presentation for all present.

6.2.3 The Kickoff Meeting location will be held at the Government’s facility or another designated location and the date and time will be mutually agreed upon by both parties.

6.3 Transition-In Plan

6.3.1 The contractor shall provide a Transition-In Plan at the Kickoff Meeting, the plan shall facilitate the accomplishment of a seamless transition from the incumbent Contractor (if applicable) and incoming Contractor. The Contractor shall identify how it will coordinate with the incumbent Contractor and Government personnel to transfer knowledge regarding the following:

6.3.2 The contractor shall also establish and maintain effective communication with the incumbent Contractor and Government personnel for the period of the transition via weekly status meetings per the COR’s direction.

6.3.3 Incumbent employees may be interviewed for possible employment by the incoming Contractor; however, the employees will have the first right of refusal.

6.4 Transition-Out Plan

6.4.1 The contractor shall provide a Transition-Out Plan NLT than 60 calendar days prior to expiration of the contract. The plan shall facilitate the accomplishment of a seamless transition from the incumbent to and incoming Contractor (if applicable). In addition, the Contractor will continue to accomplish all tasks as outlined in the contract during this period. The Contractor shall identify how it will coordinate with the incoming Contractor and Government personnel to transfer knowledge regarding the following:

6.4.2 The contractor shall also establish and maintain effective communication with the incoming Contractor and Government personnel for the period of the transition via weekly status meetings.

6.4.3 Current employees under this contract may be interviewed for possible employment by a succeeding Contractor; however, the Contractor will have the first right of refusal. The current Contractor will release any employee who chooses to be employed by a succeeding Contractor. The current Contract will assist by orienting assigned employees of the succeeding Contractor during the last 30 days of the period of this contract, if so directed by the CO. The Government shall make available to such employees existing Government Furnished Property listed under Section V of this PWS. Items that are not accountable, such as desks, chairs, telephones, and other normal office equipment and office supplies during the orientation period, will only be transferred to the incoming Contractor if items were solely purchased by the current Contractor’s company.

6.5 Quality Control.

6.5.1. Quality Assurance. The Government shall rely on the Contractors’ existing quality assurance system as the method to ensure that the requirements of the contract and performance thresholds are met; however, the Government reserves the right to monitor and evaluate the quality of services provided and compliance with the contract terms and conditions at any time.

6.5.2. Quality Control Plan (QCP). The Contractor shall develop and maintain an effective quality control program to ensure services are performed IAW this PWS, applicable laws and regulations, and best commercial practices. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services with special emphasis placed on those services listed in this PWS. The Contractor’s quality control program is the means by which it assures itself that the work complies with the requirement of the contract.

6.6 Emergency Operations/Mission Essential Personnel.

6.6.1. Continuation of Essential Contractor Services During Crisis. All services in this PWS HAVE NOT been defined or designated as essential services for performance during crisis IAW DFARs 252.237-7023, “Continuation of Essential Contractor Services.”

6.7 Contractor Manpower Reporting Application (CMRA)

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

6.7.2 Subcontractor Input in CMRA: Prime Contractors are responsible to ensure all subcontractor data is reported. Subcontractors will not be able to enter any data into CMRA, but will enter their information into a Bulk Loader spread sheet available from the AF CMRA helpdesk. Subcontractor shall fill in columns A-C then return it to the AF CMRA helpdesk after it's completed and a technician team will enter the information into CMRA.

6.8 Security Instructions

6.8.1 Physical Security. The Contractor shall safeguard all Government property, documents and controlled forms provided for Contractor use and adhere to the Government property requirements contained in this contract. At the end of each work day, all Government facilities, equipment, and materials shall be secured by a Government POC. Contractors are not allowed to secure Government facilities, equipment, and materials.

6.8.2 Access Control. The Contractor shall establish and implement methods of ensuring that no building access instruments issued by the Government are lost, misplaced or used by unauthorized persons. Access codes shall not be shared with any person(s) outside the organization. The Contractor shall control access to all Government provided lock combinations to preclude unauthorized entry. The Contractor is not authorized to record lock combinations without written approval by the Government COR. Records with written combinations to authorized secure storage containers, secure storage rooms, or certified vaults, shall be marked and safeguarded at the highest classification level as the classified material maintained inside the approved containers.

6.8.3 Pass and Identification Items. The Contractor shall ensure the pass and identification items required for contract performance are obtained for employees and non-government owned vehicles.

6.8.4 Retrieving Identification Media. The Contractor shall retrieve all identification media, including vehicle passes, from employees who depart for any reason before the contract expires.

6.8.5 Traffic Laws. The Contractor and its employees shall comply with base traffic regulations.

6.8.6 Weapons, Firearms, and Ammunition. Contractor employees are prohibited from possessing weapons, firearms, or ammunition, on themselves or within their Contractor-owned vehicle or privately-owned vehicle while on any Government facility.

6.8.7 Communications Security (COMSEC). Contractors may require access to COMSEC information on Air Force installations. The Contractor shall not require a COMSEC account. Access shall be controlled by the sponsoring agency. Access to COMSEC material by personnel is restricted to US citizens holding final US Government clearances. Such information is not releasable to personnel holding only reciprocal clearances. If it is determined the Contractor is required to access COMSEC information, the necessary training information and courses shall be provided by the COR. The DD Form 254 shall give further instructions on safeguarding and managing COMSEC material.

6.8.8 Contractor Identification. All Contractor personnel shall wear the Air Force issued Common Access Card at all times when away from their immediate work area so as to distinguish themselves from Government employees. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, Contractor personnel shall identify themselves as a contractor to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors 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, contractors occupying collocated space with their government program customer should identify their work space area with their name and company affiliation or as a minimum “Contractor” after name.

6.8.9 Drug, Tobacco, and Alcohol Use Policy. The consumption of alcoholic beverages or illegal drugs by contractor personnel, while on duty, is strictly forbidden. Contractor shall immediately remove any employee who is under the influence of alcohol or drugs.

6.9 Travel

6.9.1 Local Travel. Local travel to attend meetings or events may be required at no cost to the Government. Travel within the National Capital Region commuting vicinity is considered a cost of doing business and shall not be separately reimbursed.

6.9.2 CONUS Travel: Prior to travel, the Contractor shall coordinate with, and receive approval from, the COR at least 10 business days prior to trip.

6.9.3 OCONUS Travel: (e.g., to EUCOM and/or PACOM Area of Responsibility) Prior to travel, the Contractor shall coordinate with, and receive approval from, the COR at least 20 business days prior to trip. Theater Business Clearances shall be obtained, as necessary, prior to travel.

6.9.4 Further guidance for Contractor travel can be found at https://www.defensetravel.dod.mil/site/faqctr.cfm.

6.9.5 Trip Reports: Following each trip, the Contractor shall prepare and deliver Trip/After Action Reports to the COR IAW AFH 33-337. The trip report shall be completed in accordance with SAF/CO guidance.

6.10 Employee Accountability & Turnover

6.10.1 Staffing of Contractor Personnel. Contractor shall provide a stable workforce, throughout the duration of the contract, by maintaining a 10% or less employee turnover rate. No positions shall remain vacant for more than 20 working days. The government shall not be billed for positions left vacant over 20 working days unless the vacancy is due to government delay and otherwise approved by the CO.

6.10.2 Key Personnel.

(a) The following individual(s) are considered to be essential to the successful performance of the work under the contract: Subject Matter Expert (fill in name after award); etc..

The contractor agrees that personnel may not be removed from the contract work or replaced without compliance with paragraphs (b) and (c) of this section.

(b) If one or more of the key personnel, for whatever reason, becomes, or is expected to become, unavailable for work under this contract for a continuous period exceeding 30 calendar days, or is expected to devote substantially less effort to the work than indicated in the proposal or initially anticipated, the contractor shall immediately notify the contracting officer and shall, subject to the concurrence of the contracting officer, promptly replace the personnel with personnel of at least substantially equal ability and qualifications.

(c) Each request for approval of substitutions must be in writing and contain a detailed explanation of the circumstances necessitating the proposed substitutions. The request must also contain a complete resume for the proposed substitute and other information requested or needed by the contracting officer to evaluate the proposed substitution. The contracting officer and the project officer shall evaluate the contractor's request and the contracting officer shall promptly notify the contractor of his or her decision in writing.

(d) If the contracting officer determines that suitable and timely replacement of key personnel who have been reassigned, terminated, or have otherwise become unavailable for the contract work is not reasonably forthcoming, or that the resultant reduction of productive effort would be so substantial as to impair the successful completion of the contract or the service order, the contract may be terminated by the contracting officer for default or for the convenience of the Government, as appropriate. If the contracting officer finds the contractor at fault for the condition, the contract price may be equitably adjusted downward to compensate the Government for any resultant delay, loss, or damage.

6.10.3 Contractor professionalism. The contractor shall:

· Present a professional appearance and maintain professional demeanor and conduct at all times.

· Conduct their work assignments IAW project schedules

· Function effectively and efficiently during extended periods of high pressure and stress.

· Function as an integral member of a team of highly trained professionals responsible for the safety and security of USAF personnel and resources.

6.11 Miscellaneous Paragraphs.

6.11.1 Freedom of Information Act (FOIA). All official Government records affected by this contract are subject to the provisions of the FOIA (5 U.S.C. 552/DoD 5400.7-R/AF Supplement). Any request received by the Contractor for access/release of information from these records to the public (including Government/Contractor employees acting as private citizens), whether oral or in writing, shall be immediately brought to the attention of the CO for forwarding to the AFDW FOIA Manager to ensure proper processing and compliance with the Act.

6.11.2 For Official Use Only (FOUO). The Contractor shall comply with DoD 5400-7-R, Chapter 4, DoD Freedom of Information Act (FOIA) Program requirements. This regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding FOUO material.

6.11.3 Privacy Act. Work on this contract may require that personnel have access to information protected by the Privacy Act. Contractor personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations when handling such information.

6.11.4 Records. All records created and received by the Contractor in the performance of this contract shall be maintained and readily accessible. Records shall remain the property of the Government.

6.11.5 Safety Concerns. The Contractor is solely responsible for compliance with OSHA standards for the protection of their employees. The Government is not responsible for ensuring that Contractors comply with “personal” safety requirements that do not present the potential to damage Government resources.

6.11.6 Project Policy. The Contractor shall comply with all industry standards. All work shall be done in accordance with all federal, local, and state laws and regulations.

6.11.7 Inherently Governmental Functions. The Contractor shall not perform inherently Governmental functions as defined in the Federal Acquisition Regulation (FAR) Subpart 7.5 in relation to this PWS.

6.11.8 Ethics. The Contractor shall not employ any person who is an employee of the US Government if employing that person would create a conflict of interest. Additionally, the Contractor shall not employ any person who is an employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives approval according to DoDD 5500-7, Joint Ethics Regulation.

6.11.9 Professional Appearance of Work Space. The Contractor shall keep work space areas neat and orderly and avoid conditions leading to safety violations.

6.11.10 Non-Personal Services. The Government shall not supervise or task Contractor employees in any manner that generates actions of the nature of personal services, or that creates the perception of personal services. It is the responsibility of the Contractor to manage its employees directly and to guard against any actions that are of the nature of personal services, or give the perception of personal services to the Government or to Government personnel. If the Contractor feels that any actions constitute, or are perceived to constitute personal services, it is the Contractor’s responsibility to notify the CO immediately. Non-personal Contractor services shall not be used to perform work of a policy/decision making or management nature.

SECTION VII

APPENDIX 1

1.0 DEFINITIONS, ABBREVIATIONS, AND ACRONYMS

Contracting Officer (CO). The duly appointed Government agent authorized to award or administer contracts. The contracting officer is the only person authorized to contractually obligate the Government.

Defective Service. A service output that does not meet the standard of performance specified in the contract for that service.

Government Furnished Property (GFP). Facilities, equipment, tools, supplies, parts, or any other items furnished for the concessionaire's use by the Government. A full list, if applicable, is in Section V.

Performance Threshold. The minimum performance level of a performance objective required by the Government.

2.0 ACRONYMS