Performance_Work_Statement.pdf

PERFORMANCE WORK STATEMENT

(PWS)

For

448th Supply Chain Management Wing

Artificial Intelligence/Machine Learning (AI/ML)

PR# FD2030-19-02655

Date: 20 Sep 19

PREPARING ORGANIZATION: 418 SCMS/GUMBB TINKER AFB, OK 73145

PR# FD2030-19-02655 2

1. SECTION I – DESCRIPTION OF SERVICES/GENERAL INFORMATION

1.1. Purpose

The 448th Supply Chain Management Wing ( 448 SCMW) requires an acquisition for advisory and assistance services (A&AS) for the 418th Supply Chain Management Squadron, Data and Science Analysis Flight (DSAF), 948th Supply Chain Management Group, 448th Supply Chain Management Wing, located at Tinker Air Force Base (TAFB), OK.

1.2 Scope

The Contractor shall provide analysis of supply chain data for the Air Force Sustainment Center.

Included in this effort shall be the application of artificial intelligence/machine learning (AI/ML) methods to address complex and difficult problems impeding the 448 SCMW. This contract shall include the implementation of the solution, integration with select Air Force (AF) data sets, and testing in accordance with Key Performance Indicators. Utilization of artificial intelligence tools with supply chain data to: Identify leading indicators within historical demand patterns that predict future demand patterns, stock-outs, back orders (BO), and Mission Impaired Capability Awaiting Parts (MICAPs). Compare, contrast, and rank all leading indicators against each other and the existing eight-quarter moving average.

1.3 Contractor Tasking’s/Requirements

The Contractor shall utilize artificial intelligence/machine learning tools and techniques with AF data to accomplish the following task:

1.3.1 Leading Health Indicators (LHI)

Contractor shall automate research capability of up to 30 supply questions from the Supply Chain (SC) portion of the LHI checklist. In addition, Data Models and analytical models will be constructed to support the following organic supported Engine Type Model (TMs) for F100, F101, F107, F108, F110, F118, F135, F139, and TF33. In addition, individual Type Model Series (TMS) identified in Table 1. (CDRL A001 – Automation of LHI Risk Framework for Supply Chain)

Contractor shall Productionize Leading Health Indicator (LHI) data and analytical models for Organic supported Engine (TMs) and individual TMS identified in Table 1. (CDRL A002 – Productionizing of LHI Risk Framework for Supply Chain)

TYPE MODEL SERIES – Table 1

F100-200 F108 F139-100 (No Series) F100-220A F108-100

F100-220B F108-201 TF33

F100-220C TF33-100

F100-220/229 F110 TF33-102C

F100-229A F110-100 TF33-103

PR# FD2030-19-02655 3

F100-229B F110-129 TF33-5

TF33-5/9

F101-102 (No Series) F118 TF33-3/103 F118-100 F107 F118-101 F107-101 F107-105 F135 (No Series)

1.3.2 Supply Chain (SC) Metrics

Contractor shall identify leading indicators listed below within historical demand patterns that predict future demand patterns, stock-outs, back orders, and MICAPs. Compare, contrast, and rank all current leading indicators against each other as well as any potential predictive indicators identified/developed during period of performance against the existing eight – quarter moving average from D200A. Develop predictive analytics models for enterprise measures listed below;

(CDRL A003 – Model Test and Acceptance)

• Aircraft Availability (AA) Develop models to predict future Total Non-Mission Capable Supply TNMCS Drivers by Weapon System (W/S) based on Historical patterns in data Develop models to predict availability of parts that will have the most impact on Aircraft Availability (AA) Develop models to predict why and when aircraft may be unavailable due to parts shortages

• BO/MICAP

Develop models to predict BO/MICAPs. (I.E. Aggregation of data should be by Commodity line, Weapon System, Enterprise, Type Model Series, etc)

• On Time Delivery (OTD) Develop models to predict OTD by source of supply for each part on each contract

• Awaiting Parts (AWP) Develop models that predict levels of awaiting parts and impact that these levels have on parts availability, backorders, MICAPS, TNMCS, and AA

• Order Fulfillment/Order Response Time (ORT)

Develop models to predict impacts to ORT from increased AF/Defense Logistics Agency (DLA) backorders Develop models to predict Product Quality Deficiency Reports (PQDRs) and impact to Business Metrics

PR# FD2030-19-02655 4

1.3.3 Supply Chain Planning Predictive Analytics

Use ML for SC planning to identify patterns in historical demand data and provide insights for future model development. Focus is on Demand Planning function and using historical demand data as a data feed for ML Model to project insights not currently realized with current demand planning process. (CDRL A004 – Supply Chain Planning Predicative Analytics)

1.3.4 Natural Language Processing (NLP)

Data mine text fields in Product Item Description (PID) sheets to identify trends, key words and leading indicators. Data mine text fields in contract documents to identify all National Item Identification Number (NIINs) and the type of work being accomplished (buy, repair, engineering services, other) Data mine purchase requests to identify all NIINs and the type of work being accomplished (buy, repair, engineering services, other) (CDRL A005 – Natural Language Processing (NLP)

1.3.5 Transition Efforts

Contractor shall develop transition of prototype into development environment collaboratively with DSAF. Contract shall transition development environment architecture and models into a production environment collaboratively with DSAF. (CDRL A006 – Transition efforts in collaboration with DSAF)

The data environment will provided by the United States Air Force (USAF) and will be defined upon contract award. Initial work will be accomplished in a development environment that does not contain real time data. Work will migrate to production environment once it is established.

The data environment is subject to change.

The development environment is currently the Defense Research Engineering Network (DREN).

Initial prototype development will be incorporated into DREN. The contractor shall, be proficient with fundamental front-end languages (e.g., Hypertext Mark-up Language, Cascading Style Sheet (CSS) and JavaScript) as well as JavaScript frameworks (e.g., Angular, React, Amber). The contractor shall also be proficient with server languages (e.g., Python, Java, etc…) and databases including PostgreSQL and must have a working-knowledge of frameworks, deployment and container management. The contractor shall automate Extract. Transform and Load (ETL) of up to 100 Global Command and Control Systems (GCSS) files within development environment into PostgreSQL database including jobs to be run as needed.

The contractor shall document and deliver the following: (CDRL A007 – Detailed documentation of algorithms identified, methodologies used, steps/procedures, guidebook)

• Blueprint solutions on latest integration paradigms and Applications, Programs and Indentures (D200F) (API) based interactions (including Microservices) in a diverse technology and product landscape

• System architecture design for web-based applications

• Working with or managing NoSQL databases (i.e. Mongo)

• RESTful service-based architecture for new business capabilities or

PR# FD2030-19-02655 5

transformations around legacy implementation

• Configure and maintain containers along with supporting documentation

• Front end website architecture and user interaction on web pages

• Back-end database design and supporting documentation

• Algorithm development, model selection and evaluation criteria, data dictionary, and data flow diagrams

• Provide transition plan

• Timeline

• Acceptance test plans

• Developer guide book

The production environment shall be in a Government approved source, most likely Amazon Web Services (AWS) with the possibility of some Open Source tools. Efforts to include at a minimum, database changes, model recoding, container modifications, and redeployment of visualizations. The contractor shall document and deliver the following: (CDRL A008 – Re- Engineering of data visualization)

• Connect directly to Air Force supply chain authoritative data sources databases

• Aggregate the raw datasets into standard data models developed during the data science process

• Ingest/Feed the standard data models into the formalized and tested and approved by the DSAF machine learning models

• Receive the predictive results from the machine learning models

1.3.6 Model Test and Acceptance

All models will be tested and upon acceptance; documentation will be provided to the government as produced/required. (CDRL A009 – Acceptance Pkg. of developed models to Production Environment after approved Verification/Validation)

1.3.7 Project Management

The contractor shall provide all management, administration, staffing, planning, scheduling and support for all items or services required by the Contract. The contractor shall identify a Project Manager (PM) who shall be the primary representative responsible for all work awarded and deliverables due under this Contract and the contractor’s representative in Technical Interchange Meetings (TIMs) to ensure all standards and agreements referenced herein are adhered to.

The contractor shall:

• Participate in the kickoff meeting to establish and coordinate achievement of objectives

• Utilize a Project Management Plan (PMP) (CDRL A010 – Project Management Plan) The contractor shall develop a Project Schedule providing a detailed work breakdown structure (WBS) and master completion schedule for capability delivery and rollout

PR# FD2030-19-02655 6

methodology as defined by the PMP, and a risk management plan (CDRL A011 - Project Work Breakdown Structure (WBS) for incorporation in the Project Master Schedule, and a Risk Management Plan)

1.3.8 Project Manager (PM)

The contractor shall appoint a PM to plan, organize, staff, schedule and oversee the contractor’s activities to meet requirements on schedule and within cost. The PM shall assign resources and have the authority to ensure efficient and timely project execution for all contractor-related activities. The PM shall provide oversite to ensure effective, efficient and timely satisfaction of all tasks called out in this PWS.

1.4 REPORTS AND DELIVERABLES

1.4.1 Meetings

The Contractor shall provide agendas/minutes and support the following meetings

1.4.2 Meeting Agendas

The contractor shall develop and deliver suggested agenda topics to the government Contracting Officer Representative (COR)/PM, with a courtesy copy to the Contracting Officer (CO) no later than (NLT) five business days prior to the scheduled meeting. Contractor format is acceptable.

(CDRL A012 – Meeting Agendas)

1.4.3 Meeting Minutes

The contractor shall submit meeting minutes to the government COR/PM, with a courtesy copy to the CO, NLT five business days following the end of meeting. Contractor format is acceptable.

(CDRL A013 – Meeting Minutes)

1.4.4 Kick-Off Meeting

The contractor shall prepare and present a program kick-off meeting at Tinker AFB within 30 business days of Contract Award to confirm customer requirements, current business processes, and key performance indicators. During the kick-off meeting, the contractor shall demonstrate how they will meet all the requirements of this PWS. (CDRL A014 – Kick-Off Meeting)

1.4.5 Weekly or Bi-weekly Telecoms

The contractor shall participate with the government team and project managers. The contractor shall provide progress status, and utilize this time for questions/issues concerning current subject.

A standardized reporting format shall be used that has been agreed to by the government PM and the contractor. (CDRL A015 – Weekly or Bi-weekly Telecoms)

1.4.6 Monthly Status Reviews (MSR)

Each month, the team will conduct a consolidated MSR covering all elements of activity. The contractor shall develop the agenda and materials to be distributed to all participants in advance via email in the form a draft MSR. During the MSR the contractor shall provide at a minimum:

• Scheduled status report

• Funding and Expense Status Report

• Key Issues and Risks

PR# FD2030-19-02655 7

• Accomplishments since last MSR

• Planned activities before next MSR

• Document results and issues/action items

Following the MSR, the monthly MSR report will be finalized and provided to the PM/COR and CO in electronic format (Microsoft Office), via email. (CDRL A016 – Monthly Status Reports/Reviews)

1.4.7 Technical Interchange Meetings (TIMs)

TIMs will occur bi-monthly for duration of Period of Performance (PoP). The contractor shall participate in TIMs at government facility up to four times in the basic contract year; the following option years up to four times per year. Contractor will host the government team up to four times in the basic year contract year; and host the government team up to four TIMs each following option year. At minimum, one employee from prime contractor and one employee from any sub-contractors must be physically present at each TIM. (CDRL A017 – Four Technical Interchange Meetings (TIMs) – one per quarter at the government facility)

1.4.8 Mid-point Review

The contractor shall prepare and host a mid-point review at Government facility for the 448 SCMW leadership and DSAF team in mid-point of the PoP. The contractor shall host this review to discuss progress and achievements made during the contract period of performance, as well as any outstanding DSAF issues requiring the attention of the Air Force. The contractor shall submit a mid-point review final report to the government PM/COR, with a courtesy copy provided to the CO. (CDRL A018 – Mid-point Review)

1.4.9 Annual Program Review

The contractor shall prepare and host an Annual Program Review at Government facility for the 448 SCMW leadership and DSAF team in the last month of the period of performance. The contractor shall host this review to discuss progress and achievements made during the contract period of performance, as well as any outstanding DSAF issues requiring the attention of the Air Force. The contractor shall submit an Annual Program Review final report to the Government PM/COR, with a courtesy copy provided to the CO. (CDRL A019 – Annual Review)

1.4.10 Transition Out

Ninety (90) calendar days prior to the end of the second year of performance, or upon Government request, the Contractor shall provide a Transition-Out Plan (CDRL A020 – Transition Out Plan)

The Transition-Out Plan shall facilitate the accomplishment of a seamless transition from the incumbent to incoming Contractor/Government personnel at the expiration of the Contract. The Contractor shall also execute the transition, to include establishing and maintaining effective communication with the incoming Contractor/Government personnel for the period of the transition via regularly scheduled status meetings.

PR# FD2030-19-02655 8

1.4.11 Meeting Delivery Schedule

Meeting Delivery Schedule – Table 2

SECTION DESCRIPTION DUE DATE CDRL

1.4.2 Meeting Agendas 5 business days before the event A012

1.4.3 Meeting Minutes 5 business days after the event A013

1.4.4 Kick-Off Meeting

Within in 30 business days of Contract Award A014

1.4.5 Weekly or Bi-weekly telecoms As scheduled in PMP /as required A015

1.4.6 Monthly Status Reports (MSR) As scheduled in PMP A016

1.4.7 Technical Interchange Meeting (TIMs) Every other month A017

1.4.8 Mid-point Review 6 months from start of contract A018

1.4.9 Annual Program Review Last month of contract PoP A019

1.4.10 Transition Out

90 days prior to end of 2nd year of

POP A020

1.5 Travel Requirements/Schedule

The contractor shall be required to travel in table 3 (per performance period) in support of the objectives of this PWS. The Travel will be included in the firm fixed price portion of the contract and will not be paid separately.

Travel Requirements/Schedule – Table 3

Destination Year of Contract

Quantity of Round Trips

Number of personnel

Number of days

Tinker AFB, OK Basic 5 2 3 Tinker AFB, OK Option I 4 2 3 Tinker AFB, OK Option II 4 2 3

1.6 Contractor Information

1.6.1 Government-Furnished Property and Services

The contractor shall conform to the provisions of AFI 31-101, Integrated Defense (FOUO), for safeguarding the government-furnished data and all classifications of government property contained therein. All records, files, documents and work papers provided by the government or generated by the contractor in support of the contract are government property and shall be maintained and disposed of per AFI 23-111, Management of government Property in Possession of the Air Force.

1.6.2 Protection of Data

Unless otherwise stated in the Contract, the Contractor shall protect system design-related

PR# FD2030-19-02655 9

documents and operational data whether in written form or in electronic form via a network in accordance with all applicable policies and procedures for such data, including DoD Regulation 5400.7-R, September 1998, and DoD Manual 5200.01(v1-v4), February 24, 2012, to include latest changes, and applicable service/agency/ combatant command policies and procedures.

1.6.3 Data Rights

All Government information and data are considered to be For Official Use Only (FOUO). All Government information and data used by the Contractor in performance of this Contract shall only be disclosed to authorized personnel on a need-to-know basis. The Contractor shall comply with DoD 5220.22-M, National Industrial Security Program, April 17, 2014, and shall ensure that appropriate administrative, technical and physical safeguards are established to ensure the security and confidentiality of this information and data is properly protected. When no longer required, this information, data and/or equipment shall be returned to Government control, be destroyed, or held until otherwise directed.

Destruction of items shall be accomplished by tearing into small parts, burning, shredding, or any other method that precludes the reconstruction of the material. All sensitive information contained on Contractors computers shall be either degaussed or shall use a three-time overwrite of the sensitive data. The Government reserves unlimited rights to all documents/material produced under this Contract. All documents and materials, to include interfaces and models written under this Contract shall be Government-owned and are the property of the Government with unlimited rights and privileges of the ownership and intellectual property rights belonging exclusively to the Government. All materials produced for the Government shall be the sole property of the Government and may not be used for any other purpose without written permission from the CO. These rights do not abrogate any other Government rights under the applicable Data Rights clause(s).

The Contractor shall formally deliver as a Government Data Deliverable (CDRLs A006 and A008). All AF specific enhancements and customizations, configurations, configuration files, data, metadata, design documents, models written for the Government for the purpose of this contract, intellectual property, applicable software, applicable licensing, physical records, files, documents, working papers, test scripts, and test results for any solutions, and other data for which the Government shall treat as deliverable.

The Contractor shall have an approach that provides significant detail as to the offeror's plan that describes the Technical Data (TD), Computer Software (CS), and Computer Software Documentation (CSD) offering to the government. The Contractor’s approach shall ensure unimpeded, innovative, and cost effective production, operation, maintenance, and upgrade of the Service throughout the contract lifecycle, to include transition periods. The Contractor shall address all technical risks that may have a potential for disruption to schedule or degradation of performance. The Contractor shall provide the rationale for each risk, including quantitative estimates to schedule, and performance. For each risk the Contractor identifies, the Contractor shall outline how that risk is eliminated or reduced to an acceptable level in a proposed mitigation plan.

PR# FD2030-19-02655 10

1.6.4 Revisions to Government Data Environment Impacting Scope of Work During the course of writing this PWS, the government has made a good-faith effort to provide the current operating environment. However, the government recognizes the data environment is subject to change.

1.6.5 Security Requirements

The contractor shall ensure each employee displays badges on the outer clothing on the front of the body between the neck and waist so that the badges are visible at all times, when on base.

The contractor shall comply with the following paragraphs:

1.6.6 National Agency Check (NAC) Investigation Requirements

All contractor personnel performing under this order shall have a favorable Tier 1 investigation (formerly NACI) National Agency Check (NAC). The Tier 1 investigation is a background check conducted by the Office of Personnel Management and adjudicated by the Air Force DoD Central Adjudication Facility. The contractor shall provide information to obtain favorable investigations for its employees to the 448 SCMW Security Manager.

1.6.7 Government Systems

Other than what is required to perform the requirements of the contract, contractor personnel shall not release or remove system documentation, data, or reports generated by or through use of government systems. The contractor shall forward all requests for information to the government PM/COR. The contractor shall not use or disclose the data provided by the government for any purpose or in any manner not specifically authorized or required by the contract and its PWS.

1.6.8 Base/Area Badges

The government PM and project managers will assist contractor personnel in processing the necessary DoD forms to obtain base or area badges for access to government facilities.

1.6.9 Automated Information Systems (AIS)

The contractor shall not divulge any information regarding files, data, processing activities or functions, user identifications (ID’s), passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. The contractor shall ensure responses to requests for information and for data are provided only to customers with a need-to-know in performance of official duties.

Contractor personnel shall abide by all government rules, procedures and standards of conduct.

Contractors requiring access to government AIS shall have background investigations and security awareness training completed prior to the start of order performance. When the period of performance is complete or when contractor personnel leave work on this project, they shall return all access cards and base identification badges to the issuing office. The contractor shall submit written verification to the government PM/COR that the ID cards have been turned in.

All contractor personnel who will be issued a Common Access Card shall successfully complete Information Assurance (IA) training prior to obtaining access to the network. All contractor personnel shall comply with IA policies and revisions. The contractor shall notify

PR# FD2030-19-02655 11

the government PM/COR employee is being terminated and provide written verification that all access cards and base identification badges have been turned in. Upon notification the government PM/COR will terminate the contractor’s access to the network. The AF Communications Squadron reserves the right to terminate the contractor’s access to the network at any time to preserve the integrity of the local network.

1.6.10 Non-Disclosure Agreement (NDA)

Access to the government-furnished data requires a signed NDA within five business days with the owning contractor. Contractor personnel shall strictly adhere to the limitations of the NDA, especially the proprietary restrictions and data cleansing procedures upon termination of services.

1.6.11 Government Contract Management

Responsibility for contracting activities rests solely with the government CO. No conversation, recommendations, or direction, whether given directly by or implied by government personnel affecting the scope, schedule, or price of the program covered by this PWS shall be acted upon by the contractor unless specifically approved in writing by the government CO.

1.6.12 Contracting Officer’s Representative (COR)

The government COR for this requirement resides in the 418 SCMS located at Tinker Air Force Base, OK. The government COR will assist the government CO with approval or disapproval of all deliverables listed in this PWS. Complaints validated by the COR will be reported in writing to the CO and to the contractor for action. Failure of the contractor to correct validated complaints will be considered a failure to perform.

1.6.13 Government Quality Assurance Surveillance Support

The contractor shall support government quality assurance surveillance to periodically evaluate the contractor’s performance in accordance with the government’s Quality Assurance Surveillance Plan (QASP).

NOTE: For those requirements listed in Section II, Services Summary, the COR will follow the methods of surveillance specified in the QASP. The COR is the government’s authorized representative for the CO and will participate in the administration of this contract. At time of award, the government will notify the contractor by letter of the identities and contact information of the primary and alternate CORs assigned to this order.

1.6.14 Protection of Government Property

The contractor shall protect government property to prevent damage during the period of time the property is in the possession of the contractor.

1.6.15 Combating Trafficking in Persons

The contractor shall comply with government policy regarding combating trafficking in persons.

1.6.16 Mission Essential Contractor Services

N/A

PR# FD2030-19-02655 12

1.6.17 Government Hours of Operation and Holidays

Government personnel will be available during installation core hours. Core hours at Tinker AFB are 8:00 AM to 4:00 PM, Monday through Friday, excluding Federal holidays (Table 3.2) and base closure dates.

Table 3.2 Federal Holidays

New Year’s Day January 1st * Martin Luther King, Jr.’s Birthday 3rd Monday in January Presidents’ Day 3rd Monday in February

Memorial Day Last Monday in May Independence Day July 4th * Labor Day 1st Monday in September Columbus Day 2nd Monday in October Veteran’s Day November 11th * Thanksgiving Day 4th Thursday in November Christmas Day December 25th *

* If the date falls on a Saturday, the holiday will be observed on the preceding Friday. If the date falls on a Sunday, the holiday will be observed on the following Monday.

1.6.18 Security

All Contractor personnel shall strictly adhere to all requirements, provisions, and restrictions of the Privacy Act of 1974 and with AFI 33-332, The Air Force Privacy and Civil Liberties Program, particularly with regard to Personally Identifiable Information, which is defined as personal information, which if lost, compromised or disclosed without authorization, could result in substantial harm, embarrassment, inconvenience, or unfairness to an individual.

1.6.19 Base Safety

While on a Government installation, the Contractor will be required to follow applicable installation traffic safety regulations and any applicable safety requirements required by the work center supervisor as they pertain to execution of the contract while in the work center.

These safety regulations and requirements may include, but are not limited to, general personal protective equipment such as safety glasses, hearing protection, and hard hats. The Contractor shall comply with base and shop emergency procedures for fire, tornado, etc. It is the responsibility of the Contractor to provide guidance and to establish procedures for responding to an emergency for its employees. It is the Contractor’s responsibility to account for its employees following an emergency evacuation. Contractor Personnel shall participate with Government personnel in all fire and tornado drills at no additional cost to the Government.

Applicable Regulations and AFIs:

29 Code of Federal Regulations (CFR) 1910 Occupational Safety and Health Administration (OSHA) Standards for General Industry AFI 91-203; AF Consolidated Occupational Safety Instruction

PR# FD2030-19-02655 13

AFI 91-207; the USAF Traffic Safety Program AFI 31-218; AF Motor Vehicle Traffic Supervision

1.6.20 Contractor Manpower Reporting Application (CMRA)

The Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The Contractor is required to completely fill in all required data fields at https://afcmra.dmdc.osd.mil. 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. Contractors may direct questions to the CMRA help desk. To document compliance, the Contractor shall identify in the October MSR that this reporting has been accomplished.

2. SECTION II – SERVICES SUMMARY (SS)

The contractor service requirements are summarized into performance objectives that relate directly to the mission essential items. The performance threshold describes the minimum acceptable levels of service for each requirement. The contractor shall be aware that in the absence of any contract requirement from the Services Summary does not detract from its enforceability nor limit the rights or remedies of the government under any other provision of the contract. The government will use the surveillance methods contained in the Quality Assurance Surveillance Plan (QASP) to evaluate the contractor's performance for the performance objectives listed below. In the event the performance threshold is not met, the contractor will be given five business days, after notification to correct the unacceptable performance. The contractor shall immediately take corrective action in accordance with the performance threshold(s). In cases where the contractor fails to implement corrective action, the CO will take appropriate measures. The government COR will inspect and approve or disapprove the services listed in the Services Summary. The contractor shall ensure the following Services Summary requirements are accomplished:

2.1 Services Summary (SS) Requirements

The contractor shall ensure the performance objectives, performance thresholds and support for surveillance methods are achieved as follows:

2.2 Performance Objectives and Thresholds

The contractor shall achieve performance thresholds identified in this PWS.

NOTE 1: The performance thresholds are designed to:

Align contractor performance with objectives.

Focus on critical success factors in meeting performance objectives.

Reflect performance goals.

Promote continuous improvement in performance.

PR# FD2030-19-02655 14

NOTE 2: The COR will exercise surveillance over the performance thresholds.

2.3 Surveillance Methods

The contractor shall support the 418 SCMS’ surveillance methods as identified in the QASP.

2.4 Contractor Performance Evaluation

The contractor shall be aware that the evaluation of performance will occur when the COR evaluates the services provided by the contractor to determine whether or not it meets the performance parameters of the order.

3. Government Inspection and Acceptance of Deliverables

The government COR will have the right to reject or to require correction of errors found in deliverables. In the event of rejection of any deliverable, the contractor will be notified in writing by the government CO of the specific reasons why the deliverable was rejected. The contractor shall have 30 calendar days to correct the rejected deliverable and to resubmit to the government CO for re-inspection. If no comments are provided within 30 calendar days of deliverable receipt, the deliverable will be deemed to have been accepted by the government.

3.1 Contract Deliverables

The Contractor shall provide the following CDRLs. Reference the attached DD Form 1423-1s for detailed descriptions. All deliverables shall meet professional standards, DoD and Air Force policy, and comply with the requirements set forth in this PWS.

CONTRACT DATA REQUIREMENTS LIST (CDRL)

MILESTONE/DELIVERABLE

DESCRIPTION ESTIMATED DELIVERY DATE CDRL

Automation of LHI Risk Framework for Supply Chain (A001) As produced/required

A001

Productionizing of LHI Risk Framework for Supply Chain (A002) As produced/required

A002

Model Test and Acceptance (A003) As produced/required A003

Supply Chain Planning Predictive Analytics (A004)

As Required A004

Natural Language Processing (NLP) (A005) As produced/required

A005

Transition efforts in collaboration with DSAF (A006) As produced/required

A006

Detailed documentation of algorithms identified, methodologies used, steps/procedures, guidebook (A007)

As produced/required

A007

PR# FD2030-19-02655 15

Re-Engineering of data visualization (A008) As produced/required A008

Acceptance Pkg. of developed models to Production Environment after approved Verification/Validation (A009)

As produced/required

A009

Project Management Plan (A010)

Draft delivery NLT 10 business days after award.

Final delivery NLT 5 business days following review.

A010

Project Work Breakdown Structure (WBS) for incorporation in the Project Master Schedule, and a Risk Management Plan (A011)

Draft delivery NLT 10 business days after award.

Final delivery NLT 5 business days following review.

A011

Meeting Agendas (A012) 5 business days prior to scheduled meeting

A012

Meeting Minutes (A013) 5 business days after end of meeting A013

Kick-Off Meeting (A014) Within 30 days of Contract Award A014

Weekly or Bi-weekly Telecoms (A015)

As Required A015

Monthly Status Reports/Reviews (A016)

Due every 30 days A016

Four Technical Interchange Meetings (TIMs) - one per quarter at the government facility (A017)

Delivery Schedule TBD Draft delivery 1 business day after TIM.

Final delivery 1 business day after Review.

A017

Mid-point Review (A018) 6 months from contract award A018 Annual Review (A019) End of PoP A019 Transition Out Plan (A020) 90 business days prior to end of PoP A020

Quality Assurance Surveillance Plan (QASP) Service Summary (SS)

PERFORMANCE OBJECTIVE PWS

PARA

PERFORMANCE

THRESHOLD

SS-1 Automation of LHI Risk Framework for Supply Chain

1.3.1. As produced/required

SS-2 Productionizing of LHI Risk Framework for Supply Chain

1.3.1. As produced/required

SS-3 Model Test and Acceptance

1.3.2. As produced/required

PR# FD2030-19-02655 16

SS-4 Supply Chain Planning Predictive Analytics

1.3.3. As required

SS-5 Natural Language Processing (NLP)

1.3.4. As produced/required

SS-6 Transition efforts in collaboration with DSAF

1.3.5. As produced/required

SS-7 Detailed documentation of algorithms identified, methodologies used, steps/procedures, guidebook

1.3.5. As produced/required

SS-8 Re-Engineering of data visualization

1.3.5. As produced/required

SS-9 Acceptance Pkg. of developed models to Production Environment after approved Verification/Validation

1.3.6. As produced/required

SS-10 Project Management Plan 1.3.7. Draft delivery NLT 10 business days after award.

Final delivery NLT 5 business days following review.

SS-11 Project Work Breakdown Structure (WBS) for incorporation in the Project Master Schedule, and a Risk Management Plan

1.3.7. Draft delivery NLT 10

business days after award.

Final delivery NLT 5 business days following review.

SS-12 Meeting Agendas 1.4.2. 5 business days prior to scheduled meeting

SS-13 Meeting Minutes 1.4.3. 5 business days after end of meeting

SS-14 Kick-Off Meeting 1.4.4. Within 30 days of Contract Award

SS-15 Weekly or Bi-weekly Telecoms

1.4.5. As Required

SS-16 Monthly Status Reports/Reviews

1.4.6. Due every 30 days

SS-17 Four Technical Interchange Meetings (TIMs) -one per quarter at the government facility

1.4.7. Delivery Schedule TBD

Draft delivery 1 business day after TIM.

Final delivery 1 business day after Review.

SS-18 Mid-point Review 1.4.8. 6 months from contract award

SS-19 Annual Review 1.4.9. End of PoP SS-20 Transition Out Plan 1.4.10 90 business days prior to

PR# FD2030-19-02655 17

end of PoP

APPENDIX A: ACRONYMS

A&AS Advisory and Assistance Services AA Aircraft Availability AF Air Force AI Artificial Intelligence AIS Automated Information Systems API Applications, Programs and Indentures AWP Awaiting Parts AWS Amazon Web Services BO Back Order CDRL Contract Data Requirements List CO Contracting Officer COR Contracting Officer Representative CS Computer Software CSD Computer Software Documentation CSS Cascading Style Sheet DLA Defense Logistics Agency DREN Defense Research Engineering Network DSAF Data Science and Analysis Flight ETL Extract, Transform and Load FOUO For Official Use Only GCSS Global Command and Control Systems IA Information Assurance IDs Identifications LHI Leading Health Indicators

MICAP

Mission Impaired Capability Awaiting Parts

ML Machine Learning MSR Monthly Status Reviews NAC National Agency Check NDA Non-Disclosure Agreement NIIN National Item Identification Number NLT No Later Than ORT Order Response Time OTD On Time Delivery PID Product Item Description PM Project Manager

PR# FD2030-19-02655 18

PMP Program Management Plan PoP Period of Performance PQDRS Product Quality Deficiency Reports PWS Performance Work Statement QASP Quality Assurance Surveillance Plan SC Supply Chain SCMW Supply Chain Management Wing SS Services Summary TD Technical Data TIM Technical Interchange Meeting TM Type Model TMS Type Model Series TNMCS Total Non-Mission Capable Supply USAF United States Air Force WBS Work Breakdown Structure WS Weapon System