Atch 1_PWS_RST Ontology Supt_30 Oct 24 DRAFT CLEAN.pdf

FA300225Q0003

Attachment 1

Performance Work Statement (PWS) for

Requirements Sourcing Tool (RST) + data ontology Sustainment & Maintenance Support 30 Oct 2024

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1. General.

Air Force Personnel Center (AFPC), Force Generation Operations & Readiness Division (AFPC/DPMW) executes enterprise-wide policy and guidance for the centralized mission essential tasks of sourcing available Air Force unit type codes (UTC) to fill area of responsibility combatant commander operational plan requirements. AFPC requires contractor support to manage the requirements sourcing tool, data ontology and data warehouse that provides capability to control deployment related data through an extract transform and load (ETL) process that use web service subscriptions and user generated text or MS Excel files.

1.2. Scope.

AFPC requires contractor support to maintain the capability within the Force Generation Operations & Readiness RST + Data Ontology application. The application allows designated users to view, report, source (match requirement to UTC availability (UTA), decrement matched authorizations), un-source (un-match requirement to UTC availability (UTA), increment matched authorizations), look up, export, and view historical sourcing and user notes on data attributes. The Contractor shall also maintain the Deliberate and Crisis Action Planning and Execution System (DCAPES) authoritative data source web subscriptions (UTA, Manpower Equipment Force Package (MEFPAK), and allocated tool suite (ATS)), to ensure the number of records that have changed, deleted, or been added since the last data refresh.

SECTION II

2.0 Task Descriptions

The Contractor shall support the RST + Data Ontology in connection with this Performance Work Statement (PWS).

2.1 Requirements Sourcing Tool (RST)

2.1.1 Supervisor Dashboard

a. The contractor shall assign permissions, to include the ability to move/assign OS and create/modify/delete users, create announcements, identify/track transactions, requirements, and workload based on OS, section, or member.

2.1.2 Requirements Sourcing

a. The contractor shall identify/select unsourced & sourced requirements based on OS, identify unreconciled data between the sourcing tool and DCAPES/JOPES. source requirements using MilPDS/UTA assets or source to a generic Tasked PASCodes, source/add notes/toggle a category to multiple requirements simultaneously, view all requirement data easily and show notes/sourcing history to include rack and stack data

2.1.3 MilPDS Sourcing

a. The contractor shall ensure the system automatically conducts rack and stack function based on AFPC defined process, automatically select AFSC, AEFI, and Service Component based on the requirement data and assigned OS, skip (and add notes) for individuals not available for use, look up SEI, Unit, AEFI, and DAV reference data, look up SEI, Unit, AEFI, and DAV reference data.

look up personnel based on SSN.

2.1.4 Automated Unit Type Code (UTC) selection and Force Generation Phasing

a. The contractor shall ensure the system automatically selects UTC and phase based on the requirement data and assigned OS, and can review UTC data to include MISCAP and standard UTC make-up .

2.1.5 Ontology

The contractor shall provide oversight of the data flows to ensure accurate transfers, ensuring the refresh cycles are completed with data from authoritative data system (DCAPES) set to preview data linage to see all the transformation happen to data and the ontology to see the authoritative dat.

b. The contractor shall grant permission to view/manipulate/updating in AFFORGEN ontology per Envision PII guidance and HAF A3OD JPERMS, and provide Requirements, Deployed Current and History, and Shortfall Current and Historical data.

d. The Contractor shall maintain and verify the Deliberate and Crisis Action Planning and Execution System (DCAPES) authoritative data source web subscriptions (UTA, Manpower Equipment Force Package (MEFPAK), and allocated tool suite (ATS)), to ensure the number of records that have changed, deleted, or been added since the last data refresh.

SECTION III

3.0 SERVICE SUMMARY

Performance Objective

PWS

Para.

Performance Threshold Method of Surveillance/Frequency

SS – 1 Supervisor Dashboard

2.0 and 2.1.1

Performance is acceptable when:

Fully Functional and displays metrics 95% of the time.

100% Inspection (Daily)

SS – 2 Requirements Sourcing Tool

2.0 and 2.1.2

Performance is acceptable when:

Users are capable to automatically source requirements 95 % of the time.

100% Inspection (Daily)

SS – 3 MilPDS Sourcing

2.0 and 2.1.3

Performance is acceptable when:

Users are capable to automatically source requirements 95% of the time.

100% Inspection (Daily)

SS – 4 Unit Type Code

2.0 and 2.1.4

Performance is acceptable when:

System auto selects a UTC based on requirements 95% of the time.

100% Inspection (Daily)

SS – 5 Ontology 2.0 and 2.1.5

Performance acceptable when:

Receives automatic updates from DCAPES 95% of the time.

100% Inspection (Daily)

3.1 SERVICE SUMMARY PERFORMANCE

3.2.2 Maintenance Activities

The contractor shall support operations of developed applications, and the underlying data sets, configuration efforts that allow existing capabilities to remain operational, fixing breakages in existing data connections, integrations and application logic or user workflows.

The contractor shall support additional minor enhancements are defined as changes to integrations or application configuration to address changes in underlying source data systems or minor changes to business processes. In sustainment, minor enhancements will be scoped and mutually agreed to by the Government and the Contractor on a recurring basis. In addition to regular touchpoints to review issues or enhancements, the Contractor maintains multiple avenues for Envision platform support.

3.3 New Data Connection Requests and Ontology Support

the contractor shall support new data connection(s) and ensure proper mapping to all customer defined objects.

3.3.2 Re-Performance

The contractor shall provide support for any application defects. The expected timeframe to address break fix items impacting operations should be no longer than eight hours from identification. Corrected issues/defects will be tested by the customer and any noted issues shall be addressed by the contractor.

SECTION IV

4.0 DELIVERABLES

The Contractor shall provide deliverable(s) in a format mutually agreed upon by the Government and the Contractor. 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 start date.

DELIVERABLE DUE DATE DELIVERY FORMAT

Technical Meeting Minutes/Reports

No Later than (NLT) one

(1) business days after the meeting

MS Teams (recorded) and contractor provided notes sent via email to the COR in Word and PDF format

Kickoff Meeting Agenda NLT 3 days after contract award In person or via MS Teams Quality Control Plan Submitted at Kickoff Meeting and annual revisions submitted 15 days after OY award.

By email to the COR in Word and PDF 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 (except for computers-certified for classified use to access AF applications) or services for this requirement. Contractors will require Common Access Cards (CAC), and this will be identified during pre-award, see additional information concerning CACs in para 6.8.8.

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

SECTION VI

6.0 GENERAL INFORMATION

6.1 Scheduling

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, AFPC, A1 DTA, and A1XI 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:

Introduction of personnel Overview of project tasks Review of organization (complexity) Schedule (shows major tasks, milestones, and deliverables; planned and actual start and completion dates for each) Communication Plan/lines of communication overview (between both Contractor and Government) Travel notification and processes.

Government-furnished information (GFI) Security requirements (Building access, badges, Common Access Cards (CAC)) Analytical Support Status Accreditation (ASSA) Documentation Invoice procedures.

Monthly meeting dates Reporting Requirements, e.g. Monthly Status Report (MSR) POCs Roles and Responsibilities Overview of incoming Transition Plan to include process, timeframes, and status.

Prioritization of Contractor activities Any initial deliverables Other logistic issues Quality Control Plan (QCP) Sensitivity and protection of information Additional issues of concern (Leave/back-up support)

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 (Joint Base San Antonio-Randolph) facility or another designated location and the date and time will be mutually agreed upon by both parties.

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 90 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:

• Project management processes

• Points of contact

• Location of technical and project management documentation

• Status of ongoing technical initiatives

• Transition of key personnel

• Schedules and milestones

• Actions required of the Government

• Coordination of IT related programs, issues

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 how 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 Security Instructions

6.7.1 Security Agreement (SA). The contractor shall enter into a security agreement if service performance is on base. This agreement shall outline how the contractor integrates security requirements for service operations with the Air Force to ensure effective and economical operation on the installation. The agreement shall include:

a. Security support provided by the Air Force to the contractor shall include storage containers for classified information/material, use of base destruction facilities, classified reproduction facilities, use of base classified mail services, investigation of security incidents, and the use of security forms and conducting inspections required by DoDM 5220.32 Vol 1, National Industrial Security Program: Industrial Security Procedures for Government Activities, Air Force Policy Directive 16-14, Security Enterprise Governance, and Air Force Manual 16-1406, National Industrial Security Program: Industrial Security Procedures for Government Activities.

b. Security support requiring joint Air Force and contractor coordination includes packaging classified information, mailing and receiving classified materials, implementing emergency procedures for protection of classified information, security checks and internal security controls for protection of classified material and high-value pilferable property.

c. On base, the long-term installation security agreement may take the place of a Standard Practice Procedure (SPP).

6.7.2 Obtaining and Retrieving Identification Media.

a. DoD Common Access Card (CAC), (AFI 36-3026 Vol 2, Common Access Card), used for contracts for more than six months and requirement exists for access to the government computer systems and software. CAC applications are accomplished by Mission Partner Affiliation Sponsor (MPAS) via the Mission Partner Identity, Credential and Access Management

(MP ICAM).

6.7.2.1 Security Clearance Requirements. The contractor must possess or obtain an appropriate facility security clearance Secret prior to performing work on a classified government contract. If the contractor does not possess a facility clearance the government will request one. The government assumes costs and conducts investigations for Top Secret, Secret, and Confidential facility security clearances. The contractor shall request personnel security clearances, at the company’s expense, for employees requiring access to classified information within 15 days after receiving a facility clearance or, if the contractor is already cleared, within 15 days after service award. Due to costs involved with security investigations, requests for personnel security clearances shall be kept to the minimum amount employees required to perform contract requirements.

6.7.2.2 Joint Operation Planning and Execution (JOPES) / Deliberate and Crisis Action Planning and Execution System (DCAPES) Requirements. DD Form 2875s, System Access Authorization Request (SAAR) must be submitted, approved, and on file with HAF A3OD to have appropriate Joint Operations Planning and Execution System Permissions (JPERMS) for access to classified data/information. These permissions are critical to gain access to DCAPES and JOPES data which is used to update the Requirements Sourcing Tool (RST) and mission essential data housed within the Ontology. Contractors must have the appropriate permissions in-place to conduct sustainment, maintenance, and feature requests on RST + Ontology.

6.7.4 Suitability Investigations. Contractor personnel not requiring access to classified shall successfully complete, as a minimum, a Tier 1 (T1) investigation, before operating government furnished workstations. The contractor shall comply with the DoDM 5200.02, Procedures for the Department of Defense Personnel Security Program and AFI 17-130, Cybersecurity Program Management, requirements. T1 investigation requests are initiated using the Standard Form (SF) 85 and are submitted to the installation Information Protection Office through the using agency’s Security Assistant (SA). T1 investigations are different from the Wants and Warrants checks and are provided by the government at no additional cost to the contractor.

For contracts requiring IT-Level I and II access with no access to classified material, the contractor shall complete a Tier 5 (T5) or Tier 3 (T3) investigations, respectively. These investigations are submitted using the SF 86 and are submitted to the Information Protection Office through the using agency Unit Security Assistant within five calendar days after contract start. These investigations are provided by the government at no additional cost to the contractor.

6.7.5 Security Monitor Appointment. The contractor shall appoint a security representative for the on base long term visitor group. The security representative may be a full-time position or an additional duty position. The security representative shall work with the host organization to provide employees with training required by DoDM 5200.01, Information Security Program, AFPD 16-14, Security Enterprise Governance, and AFI 16-1404, Air Force Information Security Program. The contractor shall provide initial and follow-on training to contractor personnel who work in Air Force controlled/restricted areas. Air Force restricted and controlled areas are explained in AFI 31-101, Integrated Defense.

6.7.6 Additional Security Requirements. In accordance with DoDM 5200.01, Information Security Program and AFMAN 16-1404, the contractor shall comply with local communications squadron policy. The contractor shall comply with AFSSI 7700, Emission Security (EMSEC)

Program; applicable AFKAGs, AFIs, and AFSSIs for Communication Security (COMSEC); and AFI 10-701, Operations Security (OPSEC) Instructions. The contractor will comply with DoD Standard 22/Force Protection Condition Measures, DoD Standard 25/Level I-AT Awareness Training, and associated tasking contained in DAFI 31-145-0, Antiterrorism (AT) standards.

Level I AT Awareness training is available for contractor personnel and can be requested by calling 210 652-8298 or by visiting Bldg. 205 Room 13.

6.7.7 Freedom of Information Act Program (FOIA). The contractor shall comply with DoD Manual 5400.07_AFMAN33-302, DoD Freedom of Information Act Program, requirements.

6.7.8 Reporting Requirements. The contractor shall comply with AFI 71-101, Volume- 1, Criminal Investigations, and Volume-4, Counterintelligence, requirements, as referenced in AFMAN 16-1406, para 2.2.e.

6.7.9 Physical Security. Areas controlled by contractor employees shall comply with AFI 31-101

6.7.10 Operating Instructions. For controlled areas used exclusively by the contractor, the contractor shall develop an Operating Instruction (OI) for internal circulation control, protection of resources and to regulate entry into Air Force controlled areas during normal, simulated, and actual emergency operations. The OI shall be written in accordance with AFI 31-101 and coordinated through the Information Protection (IP) office.

6.7.11 Lock Combinations. The contractor shall comply with DoDM 5200.01, Vol 3 security requirements for changing combinations to storage containers used to maintain classified materials.

6.7.12 Controlled Unclassified Information (CUI). The contractor shall comply with DoD Instruction 5200.48, DoD Controlled Unclassified Information (CUI), requirements.

6.8 Travel

6.8.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.8.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.8.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.8.4 Further guidance for Contractor travel can be found at

https://www.defensetravel.dod.mil/site/faqctr.cfm.

https://www.defensetravel.dod.mil/site/faqctr.cfm

6.8.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 COR guidance.

6.9 Employee Accountability & Turnover

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

6.9.2 List of Employees. The Contractor shall maintain a current listing of employees assigned under this contract and define who are key personnel. The list shall include the employee's name, social security number and level of security clearance. The list shall be validated and signed by the company Facility Security Officer (FSO) and provided to the Contracting Officer, Program Manager, and Servicing Security Activity. An updated listing shall be provided upon request.

6.9.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.10 Miscellaneous Paragraphs.

6.10.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 AFPC FOIA Manager to ensure proper processing and compliance with the Act.

6.10.2 Controlled Unclassified Information (CUI). All DoD CUI must be controlled until authorized for public release in accordance with DoD Instructions (DoDIs) 5230.09, 5230.29, and 5400.04, or DoD Manual (DoDM) 5400.07. These regulations set policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding of CUI material.

6.10.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.10.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.10.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.10.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.10.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.10.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.10.9 Professional Appearance of Workspace. The Contractor shall keep workspace areas neat and orderly and avoid conditions leading to safety violations.

6.10.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

Air Force Force Generation – AFFORGEN Air Force Personnel Center – AFPC Allocation tool suite – ATS Authority To Operate – ATO Consolidated Database – CDB Data Warehouse – DWH Deliberate and Crisis Action Planning and Execution System – DCAPES Defense Information Systems Agency – DISA Extract Transform and Load – ETL Manpower Equipment Force Package – MEFPAK Performance Work Statement – PWS Requirements Sourcing Tool – RST Unit Type Code – UTC Unit Type Code Availability – UTA