MAF EFB PWS for SS July 2026 DRAFT.pdf

Mobility Air Forces Electronic Flight Bag

(MAF EFB) Support - DRAFT

Performance Work Statement

1 February 2026

Headquarters Air Mobility Command (HQ AMC)

Directorate of Strategic Plans, Requirements, & Programs (A5/8)

Systems Requirements Division (A5R)

1. DESCRIPTION OF SERVICES

1.1 Project Background

Headquarters Air Mobility Command’s (HQ AMC) Directorate of Strategic Plans, Requirements, & Programs’ (A5/8) primary responsibility is to oversee tanker and airlift concepts, budget strategies, manpower and organization, competitive sourcing, strategic planning and metrics, programs and policy, operations planning analysis, airlift and tanker doctrine, intergovernmental agreements, congressional interests, and management of the command’s validated acquisition programs.

This effort continues on-going support that provides HQ AMC/A5 with the workforce necessary to manage Electronic Flight Bag (EFB) operational capabilities and requirements derived from validated user needs. HQ AMC/A5R has selected specific capabilities-based processes and tools to assist in managing the integration of MAF operational requirements into a strategic operational vision. HQ AMC/A5R seeks to provide the needed expertise to implement and institutionalize those processes and tools.

In addition, operations are moving to leverage the fast pace of technology advancements to significantly enhance the operations of America’s air mobility forces worldwide. As the command lead for EFB capabilities and operations, HQ AMC/A5 is charged with the development of a strategic operational enterprise vision targeting integration, modernization, and interoperability within the Joint and Department of Defense (DoD) communities.

1.2 Scope

The EFB is a critical component to aircrew operations. The EFB is an electronic handheld device that enables removal of carry-on paper technical orders/flight manuals and provides ancillary situational awareness to the operator. Over time, the EFB has become critical and necessary equipment for aircrew operations. Since inception, support contractors have been necessary to assist with requirements development and sustainment of the EFB. This PWS is intended to continue necessary contractor support. The contractor shall support HQ AMC/A5R in managing EFB technical requirements and capabilities.

The contractor shall provide technical support to sustain the HQ AMC/MAF EFB effort and will provide support and assistance in transitioning EFB into an Air Force (AF) enterprise program. The contractor shall implement changes to the EFB hardware and software configuration. The contractor shall maintain SharePoint sites necessary to deliver and maintain EFB capabilities and support all EFB user/operators as necessary.

2.0 ELECTRONIC FLIGHT BAG (EFB) LIFE CYCLE MANAGEMENT (LCM)

TECHNICAL SERVICES REQUIREMENTS AND CAPABILITIES

The contractor shall provide the technical services required for EFB management and project integration/interoperability of this task order including documentation and related functions.

The contractor shall perform the following tasks:

2.1 TASK 1. Mobile Device Management (MDM)

2.1.1 Support hardware, software, and cloud services in order to deploy, manage, track, and audit mobile devices used as EFB.

2.1.2 Manage MDM issues and maintains a record of trends within the AMC MDM.

2.1.3 Ensure all EFBs and activations comply with AMC policies and procedures.

2.1.4 Audit device inventory and member accounts through EFB POCs in the MDM cloud environment.

2.1.5 Liaison with AMC EFB POCs and MDM administration for installations, deployments, and troubleshooting of new updates.

2.1.6 Help evaluate new OS mobile device releases for iOS.

2.1.7 Field requests from AMC Field and outside agencies.

2.1.8 Manage Acts as AMC Apple Device Enrollment Program administrator that is a requirement for the MDM.

2.1.9 Participate in local meetings up to SECRET to review threats and security settings for device management.

In summary, the contractor shall provide assistance in ensuring the MDM meets the requirements of EFB users. This will encompass working with the Enterprise Mobile Management (EMM) administrators on issues with the MDM. The contractor shall collaborate the government on courses of action and position recommendations (A002) in support of MAF and AF EFB MDM requirements.

2.2 TASK 2. Mobile Application Management (MAM)

2.2.1 Maintain all applications on AMC EFBs.

2.2.2 Technical liaison with the Air Combat Command Cyberspace Capabilities Center (CCC) Software Certification process.

2.2.3 Maintain AMC approved Hardware and Software List.

2.2.4 Administer EFB configuration changes, interact with user(s) submitting the request, manage the change request through program approval process, and assist with implementing the change once approved.

2.2.5 Provide technical support for loading commercial off-the-shelf and in-house developed, mobile applications into the EMM application store.

2.2.6 Assists with the deployment of approved applications.

2.2.7 Participate in local meetings up to SECRET to review threats and security settings for application management.

In summary, the contractor shall provide assistance in the management of EFB Mobile Applications. This will include maintaining the EFB approved hardware software list and working with CCC on the maintenance of approved applications. The contractor shall assist in the review of any proposed changes to the EFB applications. The contractor shall assist in the review of courses of action and provide position recommendations (A002) for Government review in support of EFB mobile application requirements.

2.3 TASK 3. Mobile Content Management (MCM)

2.3.1 Perform as technical liaison with the DAF365 for content access on the EFB.

2.3.2 Administrator EFB configuration changes.

In summary, the contractor shall provide assistance in the development of MCM solutions for the EFB. This will include assisting the Government in collaborating with all Major Commands (MAJCOMs), Secretary of the Air Force (SAF) offices, and other government EFB users in MCM requirements. The contractor shall assist in the development of the MCM solution and the implementation of the approved MCM solution. The contractor shall assist in the review of courses of action and provide position recommendations (A002) for Government review in support of MAF and AF EFB MCM solutions.

2.4 TASK 4. EFB Clouded SharePoint Site Development and Management

2.4.1 Design, implement, and sustain Microsoft SharePoint sites necessary to support EFB program efforts.

2.4.2 Develop data collection sites on SharePoint to facilitate data queries for the various queries from A5R.

2.4.3 Ensure SharePoint information is reviewed weekly for accuracy and utilize a proper file structure.

2.4.4 Perform day-to-day management of AMC EFB SharePoint sites.

2.4.5 Manage content hosted on EFB SharePoint sites and ensure the site and content meet the needs of the EFB user community.

2.4.6 Create and configure new sites based on changing EFB requirements and capabilities.

2.4.7 Develop document libraries for EFB user and AMC EFB team use.

2.4.8 Create and configure EFB lists and forms to provide the EFB teams with SharePoint solutions.

2.4.9 Backs up and archive SharePoint sites as required.

2.4.10 Provide SharePoint support and user education to over 15,000 EFB users.

2.4.1.11 Manage EFB SharePoint permissions and rights for all levels of the EFB program.

2.4.1.12 Manage the EFB Delegated Rights for AMC and use SharePoint to maintain all EFB POCs with delegated rights.

In summary, the contractor shall develop and maintain EFB SharePoint dashboards, reviewing weekly to support requirement tracking, Program of Record (POR) lifecycle milestones, and policy.

These dashboards shall be updated and sustained to contain the most recent data to facilitate Government decision making.

2.5 TASK 5. Training Support.

The contractor shall provide the following training to group, wing, and squadron, EFB managers:

2.5.1 Device activation

2.5.2 Device/application password reset

2.5.3 Device/application unlock

2.5.4 Initiate lost mode/device retrieval

2.5.5 Perform set-up, maintenance, and restoration functions on End User Stand Alone (EUSA) devices, to include:

• 2.5.5.1 Facilitate EUSA device set-up IAW the MDM provider and configuration profile provided by HQ AMC EFB Program Office.

• 2.5.5.2 Initiate EUSA device operating system updates as approved by

Defense Information Systems Agency (DISA) and configuration profile provided by HQ AMC EFB Program Office.

• 2.5.5.3 Review audit logs for unauthorized access and/or configuration changes.

2.6 TASK 6. EFB Help Desk (Level 1/2) Wing/Group/Squadron Support

2.6.1 Provide guidance and assistance to Air Force EFB managers in resolving local issues.

2.6.2 Provide telephone, email, and on-site problem diagnosis and resolution.

2.6.3 Assist in enforcement of mobile device policies and procedures in the MDM environment.

3. Task Order Management

3.1 Post Award Conference

3.2 A Post Award Conference led by the Contracting Officer (CO) and HQ AMC/A5R representatives shall occur within two weeks following task order award to ensure a common understanding of the requirements, expectations, and ultimate products. Contractor shall discuss the overall understanding of the project and review the background information and materials provided by the Government. Discussions will also include inbound contractor personnel, in-processing/out-processing checklists, scope of work, deliverables to be produced, how the efforts will be organized and projects conducted; assumptions made/expected and results.

A concerted effort shall be made to gain a thorough understanding of the Government’s expectations. The contractor will provide a summary report or minutes for the conference. (A003) However, nothing discussed in this, or in any subsequent meetings between the Government and the contractor shall be construed as adding, deleting, or modifying any PWS requirements, including deliverable specifications and due dates.

Centralized Project/Requirement Management

The contractor shall provide a centralized task order management capability at the contractor site.

This function shall encompass administrative, clerical, documentation, and related functions, which provide general support for the task order. The contractor shall notify the CO immediately of the directions received from Government personnel that the contractor considers outside the scope of PWS requirements. To ensure seamless communication, the contractor will be responsible for designating a primary contact to address any and all issues that may arise during the execution of the task order. This person shall be the point of contact for task order issues.

3.3 Phase-in/Phase-out

3.3.1 Phase-in

Task order award recipients shall be allowed access to incumbent contractor’s personnel and Government facilities to familiarize supervisors and key personnel with equipment, reporting, work scheduling and procedures 30 calendar days prior to task order completion. Such access will not interfere with the production efforts of current personnel. To preclude such interference, arrangements for access will be made with the COR and CO. The incumbent contractor is fully responsible for PWS performance during the phase in period.

3.3.2 Phase-out

When there is a change in contractor upon award of a new task order, there will be a phase-out period associated with the transfer of records/data by the incumbent. Not later than 60 calendar days prior to the end of the task order, the contractor shall provide the Government with a phase-out/transition plan. The phase-out plan shall detail how all tasks will be transferred to the successor contractor. The incumbent and successor contractors shall cooperate during phase-out orientation, which will begin immediately after follow-on task order award, or whenever the CO directs the changeover, and conclude within 30 calendar days of follow-on task order award. During the phase-out period, the incumbent contractor shall be fully responsible for PWS performance requirements and cooperate to the extent required to permit an orderly changeover to the successor contractor.

The incumbent contractor is responsible for protecting Government intellectual property, while the Government remains responsible for facilitating Government Furnished Equipment (GFE) transfer from the incumbent to the successor contractor.

4. Personnel

4.1 Certifications and Competencies

Contractor shall provide key personnel with all competencies required to perform all requirements as specified in the task order prior to performance start date. Key personnel are defined as the skilled, experienced, professional and/or technical personnel that are essential for successful accomplishment of the work to be performed.

4.2 Continuity

Contractor shall maintain a fully staffed team in order to ensure continuity until task order completion. The contractor shall ensure their staff is trained and current on required skills, certifications, and qualifications. The contractor shall ensure continuation of services during personnel absences due to sickness, leave, and voluntary or involuntary termination from employment such that impact to the Government is minimal. Contractor shall provide follow-up documentation within 72 hours, stating the date and time the position shall be vacant, the anticipated replacement date of personnel, and what management action shall be taken to ensure task mission completion until resolution via Contract Data Requirements List (CDRL) A006). This provision shall be fully applicable to any subcontract, at any tier, which the prime contractor may enter into.

The contractor shall notify the CO and COR via email immediately, but not less than two weeks in advance, of the proposed replacement/substitution.

4.3 Contractor Full Time Equivalent Reporting

“In order to support the requirements of title 10, U.S.C., section 235 and 2330a, DoD contractors will report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for AMC, via the Service Contract Reporting (SCR) section of the System for Award Management (SAM) (http://sam.gov). Reporting inputs will 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 any time during the FY, all data shall be reported no later than 31 October of each calendar year. A DoD Guidebook for Service Contract Reporting in the SAM is available at https://dodprocurementtoolbox.com/site-pages/service-contract-reporting-scr. General Services Administration (GSA) has posted guidance at https://sam.gov, search the “HELP” section. Should contractors have issues using SAM, contact the Federal Service Desk at https://www.fsd.gov.”

4.4 Contractor Performance Review

Government Program Manager or COR, as appropriate, will meet with contractor to review performance. Performance Management Reviews (PMRs) will be held semiannually. The PMRs shall cover status and feedback on performance measures, contractor performance, and any significant events. Contractor shall provide written notice to the COR and Contracting Officer within 10 business days identifying any areas of non-concurrence.

4.5 Monthly Status Report (CDRL A001)

Contractor shall provide a Monthly Status Report by the 10th of each month noting status metrics on each task assigned, underway, and completed. The contractor shall identify problem areas incurred and how they were/are being resolved. The contractor shall identify and report all program management status. The contractor and COR shall agree on the MSR’s format during the post-award conference; the format may be modified prior to delivery of the first MSR. At a minimum, the MSR will include a task by task breakout that includes task title, brief task description, task percent complete, projected task completion date, actual task completion date, customer (i.e., EFB users, AMC/A5RS, EFB users, AMC other MAJCOM partners, etc.), and mission impact. This report shall be electronically delivered to the COR and Contracting Officer. Contractor format is acceptable as long as it contains the following information:

• Task order number

• Task order title

• Reporting period

• Brief description of requirements http://sam.gov/ https://dodprocurementtoolbox.com/site-pages/service-contract-reporting-scr https://dodprocurementtoolbox.com/site-pages/service-contract-reporting-scr https://dodprocurementtoolbox.com/site-pages/service-contract-reporting-scr https://sam.gov/ https://www.fsd.gov/

• Brief summary of accomplishments during the reporting period and significant events regarding the task order

• Any current or anticipated problems

• Staffing changes

• Brief Summary of activity planned for the next reporting period

• Description of any travel or unique services provided

• Deliverable summary (deliverable name, due date, percent completed, submittal date, comments)

• Billing summary (summary of other direct cost (ODC) charges task-to-date, including current period charges)

• Deferred charges

4.6 Planning and Strategy Sessions

Contractor shall effectively participate in planning and strategy sessions. The contractor shall effectively interact with EFB users/operators, resolve complaints and problems, and keep the Government properly informed of operational issues, problems, future needs, and developments.

5. GENERAL INFORMATION

5.1 Place of Performance

Primary place of performance shall be in the EFB program office, HQ AMC A5/8 at Scott AFB, IL.

5.2 Hours of Work

Normal Government duty hours are 0730 - 1630 Central Time and workweeks are Monday through Friday, excluding Federal holidays. If a holiday falls on a Saturday, it is observed on the preceding Friday. If the holiday falls on a Sunday, it is observed on the following Monday. The contractor shall ensure continuity of operations during periods of personnel turnover and long-term absences.

Long-term absences are considered those longer than two weeks’ duration. When the contractor permits, and upon approval of the COR, A5R, or A5RS, contractor employees may telework. Remote work is not authorized.

5.3 Travel

As an integral part of performing some of the requirements within this PWS, the contractor may be required to perform temporary duty (TDY) non-local travel (over 100 mile radius) to CONUS based locations. Travel shall be accomplished using government per diem rates when possible, if not possible travel will be on a firm fixed price basis. T h e c o n t r a c t o r i s r e s p o n s i b l e f o r i t s e m p l o y e e t r a v e l a r r a n g e m e n t s . The contractor shall accomplish the trips listed in the following travel table in support of EFB MDM, MCM, EMM, capability development efforts, and programmatic development meetings as required. This travel shall be in support of tasks identified in PWS paragraph 2.

Travel Requirements by Period of Performance

Detailed Purpose of Trip # of Trips Per Year

Estimated Days Per

Trip

# of Employees Per Trip

Base Period Test Development Plan Meeting

(CONUS Location, Program Office not yet identified, expect

Wright Patterson AFB, OH)

Work with AFLCMC as part of a test team to develop a TEMP and complete pertinent testing;

airworthiness, tempest, etc.

2 5 1

EFB MCM/MDM

Conferences (CONUS

Location(s))

Assist EFB Requirements Manager with EFB expertise

2 5 1

Application Capabilities Work with the 581st Software Development Group, Robins

AFB Georgia, to define software application capabilities

3 5 1

Option Period 1

Test Development Plan Meeting (CONUS Location, Program

Office not yet identified, expect Wright Patterson AFB, OH)

Work with AFLCMC as part of a test team to develop a TEMP and complete pertinent testing;

airworthiness, tempest, etc.

2 5 1

EFB MCM/MDM

Conferences (CONUS

Location(s))

Assist EFB Requirements Manager with EFB expertise

2 5 1

Application Capabilities Work with the 581st Software Development Group, Robins

AFB Georgia, to define software

Travel Requirements by Period of Performance

Detailed Purpose of Trip # of Trips Per Year

Estimated Days Per

Trip

# of Employees Per Trip

Option Period 2 Test Development Plan Meeting

(CONUS Location, Program Office not yet identified, expect

Wright Patterson AFB, OH)

Work with AFLCMC as part of a test team to develop a TEMP and complete pertinent testing, airworthiness, tempest, etc.

2 5 1

EFB MCM/MDM

Conferences (CONUS

Location(s))

Assist EFB Requirements Manager with EFB expertise

2 5 1

Application Capabilities Work with the 581st Software Development Group, Robins

AFB Georgia, to define software

Option Period 3

(CONUS Location, Program

Office not yet identified, expect Wright Patterson AFB, OH)

Work with AFLCMC as part of a test team to develop a TEMP and complete pertinent testing;

airworthiness, tempest, etc.

2 5 1

EFB MCM/MDM

Conferences (CONUS

Location(s))

Assist EFB Requirements Manager with EFB expertise

2 5 1

Application Capabilities Work with the 581st Software Development Group, Robins

AFB Georgia, to define software

Option Period 4

(CONUS Location, Program

Office not yet identified, expect Wright Patterson AFB, OH)

Work with AFLCMC as part of a test team to develop a TEMP and complete pertinent testing, airworthiness, tempest, etc.

2 5 1

EFB MCM/MDM

Conferences (CONUS

Location(s))

Assist EFB Requirements Manager with EFB expertise

2 5 1

Application Capabilities Work with the 581st Software Development Group, Robins

AFB Georgia, to define software

All travel arrangements shall be the responsibility of the contractor, to include airline, hotel, and rental car reservations. The contractor shall make all efforts to schedule travel far enough in advance to take advantage of reduced airfares. Airfare shall be the prevailing rates for commercial airlines. When required, the most reasonable means of ground transportation (i.e., taxi, bus, rental car) shall also be used. At least five working days prior to the travel start date, the contractor shall submit a travel itinerary (CDRL A004) and estimated cost to the COR. The COR will confirm the need for travel.

5.4 Travel Reimbursement

The Government will not reimburse local travel and related expenses to the contractor for ordinary daily travel to or from work at Scott AFB.

5.5 Trip Reports (CDRL A005)

A trip report shall be completed outlining the purpose and accomplishments of the trip to the Government. Each trip report shall be completed and submitted to the COR for approval/confirmation no later than five workdays after travel is completed.

5.6 Invoicing

Invoices shall be provided within 30 calendar days after the end of billing period, end of service performance period. Invoices shall be processed via Wide Area Work Flow (WAWF). Submit WAWF notification e-mails to the COR.

5.7 Non-Personal Services and/or Inherently Governmental Services

The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. 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, (e.g., inherently governmental functions). All decisions relative to programs supported by the contractor shall be the sole responsibility of the Government.

6. Contractor Furnished Items and Services

Except for those items or services specifically stated in Section 7.0 as government-furnished, contractor shall furnish everything needed to perform this task order.

6.1 Section 508 Compliance

All services and products provided in response to the requirements identified in this PWS shall comply with Section 508 of the Rehabilitation Act of 1973 (1.39 U.S.C. 794d), and the Architectural and Transportation Barriers Compliance Board Electronic and Information Technology (EIT)

Accessibility Standards (36 CFR part 1194).

7. ITEMS INCIDENTAL TO THE PLACE OF PERFORMANCE.

Government will provide the following resources to the contractor personnel assigned to this task order for task performance:

• Workspace at a Government facility.

• Standard workstation office equipment (office work area, telephone, computer, software, base network access, etc.).

• E-mail accounts on the AMC Office Information System (OIS). This includes the issuing of

Common Access Cards (CACs).

• Restricted area badges if required by AF directives.

• Telephone service with DSN and commercial access. Government will pay for all official commercial long-distance calls made in the performance of this task order.

• Unescorted access to Building 1600 to include 618 AOC (TACC), 1700, 1900, and 1961 on

Scott AFB to contractor personnel assigned to this task order.

• The contractor copies of or access to all required directives, publications, and documents as available. If the contractor requires additional copies of such documents, the Government shall provide the contractor access to Government reproduction facilities to produce these copies.

• Necessary, available, and reasonable access to functional personnel and facilities.

Government will coordinate and provide the required facilities for joint meeting sessions between functional personnel from other sites and contractor personnel.

• Technical guidance and clarification in support of PWS tasks. However, contractor personnel are expected to utilize available reference material and not rely solely on the technical point of contact. Documents produced or owned by the Government, including systems documentation, standards, specifications, or guidelines governing development of deliverables, manuals, to the extent that they are available, will be provided to contractor on request.

8. SECURITY.

8.1 Antiterrorism Level I Training

Within 30 calendar days after task order award, the contractor shall ensure its employees complete Antiterrorism Level I training, as required by DoDIO-2000.16V1_AFI 10-245-O. Contractor employees will update their training annually thereafter. A n y n e w c o n t r a c t o r employees shall complete the Antiterrorism Level I Training within the first 30 calendar days of their employment and annually thereafter as well.

8.2 Information Assurance Training

All personnel must complete annual Information Assurance (IA) training. All personnel must comply with DoD 8570.01-M, Information Assurance Workforce Improvement Program, with the exception of paragraphs C3.2.4.1.1, C4.2.3.2, C10.2.3.2, C11.2.4.1.1, and C11.2.4.1.3.

C o n t r a c t o r e mployees must complete this training within the first five days of their employment and complete annually thereafter as well.

All personnel shall complete required training as prescribed IAW with the instructions listed in the PWS. All required training can be found within MyLearning, https://lms-jets.cce.af.mil/moodle/ or training develop by the local Wing Information Protection Office.

9. Vehicle Registration

All contractor or contractor employees’ vehicles used for the performance of this task order shall comply with all local, state and federal regulations.

10. Clearance

Contractors are required to have a SECRET security clearance to perform work on this task order.

Work performed under this task order is conducted in a secure environment. Once contractor’s security clearance is verified, Government shall give contractor access to applicable Government facilities from the commencement of the task order until project completion. Some AMC missions are highly sensitive/limited need-to-know and occur with little or no notice. Contractor personnel shall comply with AMC security requirements as well as other organizational security requirements as appropriate. The Contractor must possess the required security clearance at award of this task order.

10.1 Personnel Security Investigation

Contractors working on this contract will be required to access classified information up to the Secret level. All contractor personnel working on the contract are required to have a minimum of a Tier 3 Security Investigation with “SECRET” eligibility and be currently enrolled in Continuous Vetting to perform work on this TO. Contractor personnel shall have at least an “interim “SECRET” access security clearance and accepted by AMC/A6 Director of Communications within 30 calendar days of task order award. Classified work performed under this contract will be conducted in a secure environment. Once contractor’s security eligibility is verified, Government will give contractor access to applicable Government facilities from the commencement of the contract until completion. Some AMC missions are highly sensitive/limited need-to-know and occur with little or no notice. Contractor personnel shall comply with AMC, USTRANSCOM, 618 AOC, and installation commander security requirements. The contractor shall also complete visit requests for each individual that will be performing work on the contract in the Defense Counterintelligence Security Agency (DCSA) Defense Information System for Security (DISS) prior to performance start date. The prime contractor shall ensure that any teaming partners or subcontractors (if approved by the GCA) have the appropriate clearances prior to beginning performance. If the Contractor is notified by any Government official having security cognizance over the contract that an employee’s Security Clearance has been revoked or suspended, the Contractor shall notify the Government the same day as the Contractor receives the notice.

10.2 Industrial Security Requirements

Contractor shall comply with DoD 5220.22, Volume 2_AFMAN 16-1406 Volume 2 and, DoDM 5200.01, Volume 1_DAFMAN 16-1404 Volume 1, DoDM 5200.01, Volume 2_AFMAN 16-1404

Volume 2, and DoDM 5200.01, Volume 3_DAFMAN 16-1404 Volume 3. Facility and employee security clearances are obtained according to DoDM 5220.22, Volume 2_AFMAN 16-1406 Volume 2 and DoDM 5200.02_DAFMAN 16-1405. This manual includes specific requirements for the handling of classified information, security clearance, control of areas, visitor control procedures, Sub- Contractors, vendors and suppliers, consultants, parent-subsidiary and multiple facility organizations, sensitive compartmented and Communications Security (COMSEC) information, overseas operations, security requirements for automated information systems, and operations security (OPSEC). This includes clearance procedures, visitors, and inspections.

10.3 Contractor Consent to Background Checks.

The contractor shall not employ persons to perform under this TO 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 TO who have an outstanding criminal warrant as identified by DataMax through the National Crime Information Center. DataMax checks will verify if a person is wanted by local, state, and/or federal agencies. All contractor and subcontractor (if approved by the GCA) personnel must consent to DataMax background checks. If contractor/subcontractor personnel who do not consent to DataMax check will be denied access to the installation. Information required to conduct DataMax 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. Contractor must have this information ready to provide to the Scott Visitor Control Center, if requested.

The contractor must ensure their employees and those of their subcontractors 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 these provisions. Furthermore, nothing shall excuse the contractor from proceeding with the task order as required.

10.4 Badges

The contractor is required to provide identification badges for their employees. All contractor personnel must wear these badges while on duty on Government site. Badges shall be clearly and distinctly marked as contractor and are required to identify the individual and company name. T h e c ontractor’s identification badge shall not be used as an entry requirement for installation entry or into any Government designated controlled or restricted area. The Government will provide all contractor personnel who are assigned to work at the Government site with a yellow lanyard labeled, “HQ AMC CONTRACTOR”. All contractor personnel shall wear this lanyard when working in the Government facility.

10.5 Access to Government Automated Information Systems

All contractor personnel provided government-furnished computer access shall observe DOD, USAF, AMC, and local Automated Information Systems (AIS) security policies and procedures as provided by the Information Systems Security Officer (ISSO). Violations of local AIS security policy, such as password sharing, performing personal work, file access violations, or browsing files outside the scope of the task order are prohibited.

10.6 Property Protection

Property protection for the facility where 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.

Contractors must safeguard all government-owned equipment and materials in his/her possession or use.

10.7 Safeguarding Controlled Unclassified Information (CUI)

Contractor must meet Air Force standards for storing, processing, and handling controlled, unclassified information and systems, IAW DoDI 5200.48_DAFI16-1403. Additionally, all resources (e.g. maps, publication/instructions, photos) provided by Government to assist contractor personnel in the performance of their contract will be surrendered upon termination of employment or the end of the contract performance period. The Government will take reasonable steps, by controlled access and need-to-know procedures, to protect against public release of attribution information of the contractor.

The Government may use and disclose reported information that includes attribution information only on a need-to-know basis to authorized persons for cyber security and related purposes (e.g., in support of forensic analysis, incident response, compromise or damage assessments, law enforcement, counterintelligence, threat reporting, and trend analysis). The Government may disclose attribution information to support contractors that are supporting the Government's cyber security and related activities if the support contractor is subject to legal confidentiality requirements that prevent any further use or disclosure of the attribution information. The Government agrees to consider available exemptions of the Freedom of Information Act to protect against disclosure of attribution information of the contractor to unauthorized persons. Within a reasonable period, necessary to perform an analysis after completion of the assessment, all contractor proprietary information or third party proprietary information in the possession of the Government as a result of the assessment will be destroyed unless other disposition is agreed upon in writing by the Parties or is required by law, Executive Order or regulation.

10.8 Privacy Act

Work on this project requires that personnel have access to Privacy Information. Personnel must adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations.

10.9 Contractor 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, Government personnel will ensure escort(s) are provided for the contractor at all times within a controlled or restricted area. T h e c ontractor must have an issued AF Form 1199 and work on base a minimum of four days a week (must have an assigned workspace on base). In addition, 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. Finally, the contractor must fulfill, maintain, and comply with all security requirements IAW, Integrated Defense, and command/local directives.

10.10 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. Due to specific mission requirements inherent in the nature of controlled or restricted areas on Scott AFB, Government personnel may direct contractor personnel to leave the controlled or restricted areas at any given time.

10.11 Safeguarding Classified Information

This task order deals with classified information. The contractor must meet Air Force standards for storing, processing, and handling classified information and systems. Additionally, all classified resources (e.g. maps, publication/instructions, photos) provided by the Government to assist contractor personnel in the performance of their task order will be surrendered upon termination of employment or the end of the task order performance period. The contractor shall not store any classified information at their company location.

10.12 Non-Disclosure Agreements (NDA)

In performance of this task order, 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 RFO; (b) to use and disclose such information only for the purpose of performing this task order 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. Due to the sensitive nature of the data and information being worked with on a daily basis, all contractor personnel assigned to the task order are required to complete the Government provided non-disclosure statement (Appendix A) within 30 calendar days after task order award to ensure information that is considered sensitive or proprietary is not compromised. All replacement contractor personnel are required to complete the Government provided non-disclosure statement within 30 calendar days of their hire.

Additionally, in performance of its responsibilities, the contractor (to include team members and any subcontractors) may be required to enter into agreements with other contractors (hereinafter called “associate contractors” (ASCONs)) to facilitate timely exchanges of information necessary to the performance of this task order. To safeguard information, contractor shall enter into non-disclosure agreements with the local security manager responsible as specified in the task order and after the appropriate briefing by the security manager. A copy of all non-disclosure agreements shall be provided to the COR and CO.

10.13 Avoidance of Organizational Conflicts of Interest (OCI)

To prevent conflicting roles that may bias the contractor’s judgment or objectivity, and to preclude the contractor from obtaining an unfair competitive advantage in concurrent or future acquisitions, the contractor shall be restricted as set forth below:

10.13.1 The following definitions and descriptions apply:

• “Technical Direction” includes a combination of substantially all of the following activities:

developing work statements, determining parameters, directing other contractors’ operations, and resolving technical controversies.

• “Development” includes all efforts toward solution of broadly defined problems.

• “Proprietary Information” includes all information designated as proprietary IAW laws and regulations and held in confidence or disclosed under restriction to prevent uncontrolled distribution. Examples include limited or restricted rights data, trade secrets, sensitive financial information, and computer software. Proprietary information may appear in technical data, cost and pricing data, or may involve classified information. For the purpose of this definition, proprietary information pertains to both contractor and Government information.

• “Contractor” includes the prime contractor, parent company, affiliates, divisions, and subsidiaries.

10.13.2 The contractor shall be familiar with the RFO, Subpart 9.5, entitled “Organizational and Consultant Conflicts of Interest,” and agrees to avoid conflicts of interest in accordance with the principles set forth in this subpart. Since the contractor, under the terms of this task order, will have access to Government and third party data which might place the contractor in an organizational conflict of interest (OCI), the contractor agrees to perform this task order as set forth below:

• To refrain from unauthorized use or disclosure to any individual, corporation, or organization of any data, advice, trade secrets, software, confidential financial information, proprietary or restricted information, to include CUI information (collectively referred hereinafter as “data”) of the Government or other companies coming into its possession in connection with the work under this task order for as long as it remains proprietary.

• To establish ASCON relationships by executing written agreements between companies having a proprietary interest in such data. These agreements shall prescribe the scope of authorized use of such data as well as necessary safeguards against unauthorized use or disclosure. A copy of the agreement shall be furnished to the CO promptly after execution of the task order.

• The contractor shall formally train its employees, in regard to OCI, that they shall not divulge proprietary data obtained from other companies or from the Government to anyone except as authorized in writing. The contractor shall require its employees to execute certificates attesting to their training and understanding of the requirements to safeguard all sensitive information. The contractor shall warrant that its employees shall not use for their benefit any data, advice, trade secrets, confidential financial information, proprietary or restricted information (to include CUI information) that the employee received in connection with this task order, during or subsequent to the term of his or her employment.

• To obtain from each of its employees, whose responsibility in connection with the work under this task order may be reasonably expected to involve access to such proprietary data or classified information (Government or contractor generated), a written agreement between the company and employee, which in substance shall provide that the employee will not, during employment by the contractor or thereafter, disclose any such proprietary data or classified information to which the employee had access in connection with the work under this task order.

• To refrain from utilizing such data or classified Government information coming into its possession in connection with work under this task order for purposes other than those for which it has been furnished, unless specifically authorized by the organization providing such data or Government information.

• To hold the Government harmless for any cost/loss resulting from the unauthorized use or disclosure of third party data or software by the contractor, its employees, subcontractors, or agents.

The contractor shall insert a provision conforming substantially to the language of this section, including this paragraph, in any subcontract or consultant/partnering agreement.

10.13.3 The contractor warrants that, to the best of their knowledge and belief, there are no relevant facts or circumstances that could give rise to an OCI as defined in RFO Subpart 9.5, or that the contractor has disclosed all such relevant information.

10.13.4 If a contractor determines that it, or any potential subcontractor, has an OCI, or a potential OCI, then the contractor shall address the conflict of interest, and shall provide a mitigation plan for the conflict of interest. The mitigation plan shall avoid, mitigate, or neutralize the OCI such that the full scope of work contemplated by the solicitation can be performed by the contractor.

10.13.5 The contractor agrees that if an actual or potential OCI is discovered after award, the contractor shall make full disclosure in writing to the CO. This disclosure shall include a description of the actions the contractor has taken, or proposes to take, after consultation with the CO, to avoid, mitigate, or neutralize the actual or potential conflict.

10.13.6 The CO may terminate this task order for convenience, in whole or in part, if he/she deems termination necessary, to avoid, mitigate, or neutralize an actual or potential conflict. If the contractor was aware of a potential OCI prior to award, or discovered an actual or potential conflict after award but did not disclose it, or misrepresented relevant information to the CO, the Government may terminate the task order for default, debar the contractor from Government task orders, or pursue other remedies as may be permitted by law or this task order.

10.13.7 General rules in RFO 9.505 prescribe limitations on contracting as the means of avoiding, neutralizing, or mitigating OCI that might otherwise exist in the stated situations. Illustrative examples are also provided in RFO 9.508. The two underlying principles are preventing the existence of conflicting roles that might bias a contractor’s judgment; and preventing unfair competitive advantage by a contractor competing for award.

10.13.8 Except with the prior written consent of the CO, the contractor shall not compete (as a prime contractor, subcontractor, main supplier, or consultant) during the period of this task order, including any extension thereof, and for one year thereafter, for the award of any task order for supplies, services, or construction which was generated under this task order. This prohibition does not prohibit the contractor from competing on the follow-on to this task order.

11. QUALITY CONTROL AND QUALITY ASSURANCE

11.1 Quality Control (A007)

The contractor shall be responsible for quality assurance and quality control of all services performed and all items delivered under this task order.

The contractor shall prepare and maintain a Quality Control Plan (QCP) as a guide for implementing quality assurance and quality control procedures. The contractor shall submit the QCP to the Government for information and acceptance. The Government has the right to require revisions to the contractor’s QCP should its implementation fail to control the quality of items and/or services delivered under this task order.

The QCP shall include an explanation of the processes and procedures for ensuring satisfactory performance and delivery of services.

11.2 Quality Assurance Surveillance Plan (QASP)

The Government will evaluate contractor performance under this task order IAW the QASP. The purpose of this evaluation is to ensure that the contractor’s performance meets Government requirements.

The QASP along with its attached “Surveillance Objectives, Measures, and Expectations” and “Performance Evaluation” chart identifies evaluation procedures, PWS items to be evaluated, and the measures against which performance will be evaluated.

12. SERVICES SUMMARY (SS)

The SS table below summarizes the most important performance objectives and 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 or limit the Government's rights or remedies afforded under this task order.

Performance Objective PWS Para Performance Threshold

Provide technical support. Capture accurate information and data to support findings, analysis, or recommendations and meet all identified timelines.

2.1 2.2 2.3 2.4 2.5

All minutes, reports, recommendations, staff packages, and briefings are accurate and provided with no more than one instance of incomplete information.

Exception is the Monthly Status Report (MSR) which shall have no more than two instances of incomplete information in a given contract year.

Successfully meet all security requirements.

Section 10.0 Contractor must meet and maintain all security requirements, 100% of the time.

12.1. TABLE OF DATA DELIVERABLES

All deliverables shall be accomplished and delivered by the Contractor in compliance with the table below, elsewhere in this PWS, or both, and shall be of professional quality. The table below does not necessarily contain all the documents or database entries that this PWS requires the Contractor to create, edit, contribute to, etc. in the course of contract performance; and the absence of such documents or database entries from the table shall not excuse their delivery. Nor are all such documents or database entries necessarily defined by a CDRL; and the absence of a relevant CDRL shall not excuse their delivery either. In the case of a document or database entry not defined by a CDRL, the document or database entry shall conform either to the format and delivery requirements defined elsewhere in this PWS, or else as agreed to between the contractor and the COR.