PWS - VM Data Analysis and Tools - cao 12 Jul 2024.docx

Performance Work Statement for

Vehicle Management Data Analysis and Tools

Purchase Request: FD2060-__-_____

Date QAPC signs QASP.

1.0 Description of Services

1.1 Objective(s): This Performance Work Statement (PWS) describes the services required to provide enterprise-level support for analysis and cleansing of Air Force vehicle management data and maintenance and updates of stand-alone vehicle management database tools. These services include, but are not limited to, the following:

· Personal Computer – Vehicle Management Tool (PC-VMT). PC-VMT is an Access-based tool with multiple modules used to prototype capabilities for fleet management. It is used as an interim tool until a formal LIMS-EV, BLADE, Salesforce, DPAS, or another tool is developed. The development of the formal tool uses PC-VMT as a baseline and the PC-VMT documentation as a guide.

· Maintain existing capabilities in PC-VMT that have been converted to use DPAS data. Some of the modules in PC-VMT have been converted to use DPAS data, while others were not converted (still pointing to legacy data). Perform software and documentation changes as needed to the operating modules.

· Convert additional modules from legacy systems (ILS-S, AFEMS, OLVIMS) to DPAS as needed. As required by VSCOS, evaluate what it would take to convert a module, map the changes (and what might be lost in the translation), and perform the conversion. Update the documentation once converted.

· Add new modules / prototype new capabilities through PC-VMT. VSCOS may have a new capability they want addressed in a tool. Evaluate the concept, address business rules, prototype various rules, and develop a working tool. Add documentation for the new capability.

· DPAS Data Quality (DDQ) Tool. DDQ is a tool that is run weekly (or so) to evaluate the quality of the data in DPAS. It identifies problems to be resolved.

· The contractor will maintain the DDQ tool, making changes as needed for additional data checks. Documentation on using DDQ will also be maintained.

· The contractor will act as a backup to the VSCOS team running DDQ and train VSCOS members on its use.

· Federal Automotive Statistical Tool (FAST).

· Maintain capability in the FAST Reporting Evaluation Tool (FRET). Maintain the FRET program and documentation. Add additional capabilities and rules as required.

· Aid VSCOS in the annual FAST Vehicle-Level Data reporting process. Aid by running FRET, evaluating the results, modifying results for processing, and other tasks to ensure proper and timely reporting.

· Aid VSCOS in cleaning data for FAST reporting. FRET and FAST reporting often identify many problems with the data. Aid VSCOS in identifying the problems and getting the right groups to correct errors.

· LIMS-EV/BLADE/Salesforce/DPAS. Aid VSCOS in:

· Evaluating LIMS-EV/BLADE/Salesforce/DPAS implementations of capabilities. When capabilities (from PC-VMT, DDQ, FAST, or other tools) are added formally into LIMS-EV, BLADE, Salesforce, DPAS, or another central system, the contractor will aid in providing documentation and test cases, addressing business rules, testing results, and otherwise aiding in a quality product.

· Evaluating LIMS-EV/BLADE/Salesforce/DPAS new capabilities. Similarly, new capabilities might be developed directly in the central system without prototyping. The contractor will aid in the requirements and testing of those products.

· Data Transfer.

· Aid VSCOS in transferring data from legacy systems to DPAS. For the most part, data is out of most of the legacy systems. However, the contractor may be tasked to move additional data as needed.

· Other Analyses.

· Perform ad hoc analyses to support vehicle management as required by VSCOS.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the United States Air Force (USAF) by assisting 441 VSCOS with analysis of vehicle management data and providing stand-alone database tools to help improve vehicle management processes.

1.3 Background: The Department of the Air Force (DAF) centrally manages the vehicle fleet enterprise through the 441 VSCOS. The 441 VSCOS provides vehicle fleet management support to 257 steady-state and contingency locations housing 387 units. A variety of systems are utilized by the 441 VSCOS in managing the vehicle fleet and data analysis and tools are required to assist with this process.

2.0 Services Summary

3.0 Government Property: Government property will be provided.

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

3.2 Government Property to be Provided: Government property provided includes office space, desk, chair, file cabinets, telephone, e-mail, internet access, and a computer with Windows and Microsoft software.

3.3 Base Support: The Government will furnish property incidental to the place of performance including office space and equipment, i.e., computer equipment, software, output device(s), phone/phone line, facsimile equipment, reproduction equipment and office supplies.

3.4 Reporting of Government Property: The Contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with FAR 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause. The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by DFARS 252.245-7005. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/.

3.5 Loss of Government Property

3.5.1 Definition of Loss of Government Property: “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.5.2 Reporting Loss of Government Property: The Contractor shall report loss of Government property in the GFP Module located in PIEE, https://piee.eb.mil/piee-landing/.

3.6 Return or Retention of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

4.0 Technical Requirements

4.0.1 Maintain PC-VMT, DDQ, and FRET and perform one software update a year for one of the three programs.

4.0.2 Aid VSCOS with FAST reporting.

4.0.3 Conduct one major effort each year (new module, ad hoc study, major data cleansing, etc.).

4.0.4 The Government Program Manager and contractor will periodically meet (at least once a year) to discuss priorities and related topics.

4.0.5 Status Report: The Contractor shall provide the report by close of business (COB) on the tenth day of each month. The report should include: progress of the previous month, status of the contract deliverables, issues/concerns and associated recommendations. CDRL A001 – E001, DID # DI-MGMT-80368A/T, STATUS REPORT

4.0.6 Contractor Personnel Qualifications: A minimum of fifteen (15) years of operations research, mathematical or statistical analysis and assessment experience related to the requirements as defined above in PWS paragraphs 4.0.1 through 4.0.5. A minimum of a bachelor’s degree in Operations Research, Mathematics, Information Systems or Statistical Analysis is required. A higher degree is desired. The Contractor may also propose candidates who have a degree in Engineering or Science if it can be verified that they have a minimum of twenty-four (24) college hours of advanced math such as calculus, differential equations, or advanced statistical analysis. The Contractor shall request a waiver from the government if other discipline degrees are proposed. The contractor shall have at least ten (10) years’ experience in logistics analysis, at least five of which deal with vehicles. The Contractor shall also possess a comprehensive understanding of Air Force data systems, including GCSS-AF, BLADE, and DPAS. The contractor shall possess experience implementing system, policy, and procedural changes within the Air Force context. The Contractor shall be trained in the use of computers using appropriate software applications; to include programming in Microsoft Access and Excel.

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance: The period of performance for the contract/order is 12 months after receipt of award (ARO) with four option years.

4.1.2 Place of Performance: These services will be performed at the following Government location:

441 VSCOS

445 Weyland Road, Bldg 1017 Langley AFB, VA 23665-2197

70% teleworking is authorized. Other work locations or additional teleworking requires approval of the 441 VSCOS COR.

4.2 Contract Data Requirements List(s) (CDRL)

Document Identifier Base Year Option Year Option Year Option Year Option Year

4.2.1 Quality of CDRL Deliverable: There shall be no more than one rejection of any deliverable. There shall be no more than three (3) total rejection(s) of deliverables per contract year. The Government will reject a deliverable if one (1) or more technical errors or five (5) or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within ten (10) business days of notification of Government rejection.

4.2.2 Receipt of CDRL Deliverable: CDRL deliverables shall be submitted via Wide Area Workflow (WAWF) and submitted directly to the Multi-Function Team (MFT) member identified on the CDRL. There shall be no more than two (2) late submission(s) of deliverables per contract year. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.3 Holidays and Facility Closings: Contractor/subcontractor personnel shall observe holidays and facility closings as authorized for government personnel. Contractor/subcontractor personnel shall only be permitted access to Government facilities when Government personnel are present. The Government will not be billed for such holidays, except when services are required by the Government and are approved by the Government’s Program Manager and by the Contracting Officer and are actually performed on a holiday. Holidays falling on a Saturday will be observed on the preceding Friday. Holidays falling on a Sunday will be observed on the following Monday. The following days are contract holidays:

· New Year's Day (January 1).

· Birthday of Martin Luther King, Jr. (Third Monday in January).

· Washington's Birthday (Third Monday in February).

· Memorial Day (Last Monday in May).

· Juneteenth National Independence Day (June 19).

· Independence Day (July 4).

· Labor Day (First Monday in September).

· Columbus Day (Second Monday in October).

· Veterans Day (November 11).

· Thanksgiving Day (Fourth Thursday in November).

· Christmas Day (December 25)

4.4 Travel: No travel is required to support this PWS.

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis: The Functional Commander/Director has determined these services are not mission-essential and will not continue in the event of a crisis.

5.2 Security Requirements

5.2.1 Security Regulations: The Contractor shall ensure personnel, information, system, property, facility and, if applicable, international security requirements are met. The Contractor shall ensure contractor/subcontractor personnel who perform work on a Government facility comply with the security requirements of the facility. The Contractor shall comply with the following security regulations: 32 CFR Part 117, National Industrial Security Program Operating annual (NISPOM); DoDD 5205.02E, DoD Operations Security (OPSEC) Program; and DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual.

5.2.2 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. DoDD 5205.02E and DoD Manual 5205.02-M require contractors supporting DoD activities use OPSEC to protect critical information for specified contracts, sub contracts, and information used in the performance of duties in support of Air Force requirements/missions. The Contractor shall ensure Contractor personnel who perform work on (or in) a Government facility comply with the OPSEC procedures and training requirements of the facility as specified in AFI 10-701.

5.2.3 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or Controlled Unclassified Information (CUI) in accordance with 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM), § 117.7(a). Applicable equipment shall be safeguarded, maintained and operated in accordance with 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM), § 117.7(a).

5.2.4 Security Clearance: The Contractor shall ensure applicable contractor/subcontractor personnel have security clearance(s) at the SECRET level for proper accomplishment of contract/order requirements. The security clearance(s) shall be obtained in accordance with the Department of Defense (DD) Form 254, Department of Defense Contract Security Classification Specification.

5.2.5 Security Incident or Violation: The Contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation.

5.2.6 Access to Government System(s): The Government will provide contractor/subcontractor personnel access to system(s) necessary to perform tasks under the contract/order. The Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified or classified Government Automated Information System (AIS) have the respective background check or security investigation conducted. At a minimum, the Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified AIS have a National Agency Check with Inquiries (NACI) conducted. Upon completion/termination of the contract/order or transfer/termination of contractor/subcontractor personnel, the Contractor shall ensure the system account(s) are closed.

5.2.7 Access to Government Facility or Military Installation: The Contractor shall ensure contractor/subcontractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation.

5.2.8 Common Access Card (CAC)

5.2.8.1 The Contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order. The Contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the PCO. The Government will provide the Contractor instruction on how to utilize Mission Partner Identity, Credential and Access Management (MP-ICAM) and notify the Contractor of approval/disapproval of contractor/subcontractor personnel application. Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility [usually the Military Personnel Flight (MPF)].

5.2.8.2 The Contractor shall immediately report a lost or stolen CAC as directed by local Government policy. The Contractor shall notify the PCO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within five business days. The Contractor shall return a CAC within five business days once contractor/subcontractor personnel no longer require computer network/system access and/or facility access. The Contractor shall return an expired CAC within five business days after the expiration date. The Contractor shall return any and all CACs within five business days after completion/termination of the contract as directed by local Government policy.

5.3 Environmental Management System (EMS): Contractor/subcontractor personnel who perform work on any Government facility shall comply with the EMS requirements established by the facility. Contractor/subcontractor personnel may be required to complete EMS training prior to beginning work.

5.4 Agency Affirmative Procurement Programs: This acquisition does not require the purchase of Environmental Protection Agency (EPA)-designated products or United States Department of Agriculture (USDA)-designated products; therefore, the requirement does not apply.

5.5 Safety Requirements

5.5.1 Contractor Environmental, Safety, and Occupational Health Compliance: The Contractor shall comply with Government Safety and Health regulations including, but not limited to, Public Law 91-596, Occupational Safety and Health Act (OSHA), and DoD Directive 4715.1E, Environmental, Safety, and Occupational Health (ESOH). The Contractor shall require all subcontractors to comply with required safety, health, and fire standards. If applicable, add local policy.

5.5.2 Contractor Safety & Health Program/Plan. The Contractor shall establish and maintain a safety and health program detailed in a written Contractor’s Safety and Health Plan (SHP) in accordance with OSHA and ESOH and tailored to the contract. The SHP shall address the requirements established in the Safety Appendix (Environmental, Safety and Occupational Health Requirements) to the contract. The Contractor shall submit the SHP to the MFT member identified on the CDRL [CDRL Reference Section 4.2 Table, DI-SAFT-82313, Environmental, Safety, and Occupational Health (ESOH) Plan]. The cognizant Government safety office will review the SHP to determine if safety requirements are correctly addressed. The Contractor shall notify the cognizant Government safety office of any revisions made to its SHP after contract award. All changes to the SHP must also be submitted in writing and approved by the cognizant Government safety office [CDRL Reference Section 4.2 Table, DI-MGMT-81580/T, Contractor’s Standard Operating Procedures – Company Safety Plan].

5.5.2.1 Mishap Notification/Investigation: In accordance with AFI 91-204, Safety Investigations and Reports, the Contractor shall report mishaps involving damage or injury to USAF assets/interests. The Contractor shall ensure the USAF is notified of mishaps. The Contractor shall contact the Contracting Officer’s Representative (COR), if available, or another MFT member by telephone within two hours. The Contractor shall immediately secure the mishap scene (and damaged property) and impound pertinent maintenance and training records until released by the Government’s Safety Office. Such release shall be accomplished through the Contracting Officer. The Contractor shall cooperate and assist Government personnel in the investigation of the mishap and submit an Accident/Incident Report within 24 hours of the mishap [CDRL Reference Section 4.2 Table, DI-SAFT-81563 NOT 2, Accident/Incident Report].

5.5.3 Voluntary Protection Programs (VPP): Contractor personnel performing work on a USAF installation shall participate in the local VPP.

5.5.3.1 VPP Description: In 1982, OSHA created the Voluntary Protection Programs (VPP) to recognize and partner with worksites that implement exemplary systems to manage worker’s safety and health. These sites implement comprehensive Safety and Health Management Systems that exceed basic compliance with OSHA standards. VPP applies to all personnel at Robins AFB - civil servants (both bargaining and non-bargaining), active duty (officer and enlisted), reservists and contractor employees. The Contractor shall ensure its employees and managers have a comprehensive understanding of VPP as well as full compliance with OSHA requirements. The Contractor, whether regularly involved in routine site operations or engaged in temporary projects such as construction or repair, shall follow the safety and health rules of the installation or VPP site. Detailed information on VPP is available on the OSHA website at http://www.osha.gov/dcsp/vpp/index.html. The Contractor shall access the site to ensure their understanding of VPP and how their performance is linked to the Air Force installation’s pursuit of VPP recognition.

5.5.3.2 Department of Labor (DoL) Inspection of Contractor Operations. The Contractor is subject to DoL inspections and enforcement by OSHA health and safety officials while performing work on a Government installation. OSHA health and safety officials may access workplaces on Government installations at any time, scheduled or unscheduled, during regular work hours. OSHA health and safety officials must meet security requirements to enter restricted or classified areas. The Contractor shall immediately notify the COR and the contracting unit’s Safety Office upon notification of a visit.

5.6 Inspection of Services: In accordance with the Inspection of Supply/Services clause(s) identified in the contract/order, the Government reserves the right to inspect Contractor performance.

5.7 Service Contract Reporting (SCR): The contract does not meet the DoD Contract Reporting criteria or reporting dollar threshold; therefore, SCR does not apply.

5.8 Invoicing/Payment and Receipt/Acceptance: The Contractor shall submit/process payment requests and receipt/acceptance documents via WAWF.

5.9 Quality Control Plan/Quality Management System (QMS): The Contractor shall ensure the quality of services through a quality and/or inspection system. The Contractor shall submit a Quality Control Plan (QCP) addressing detection of quality program problems and defects, identification of root causes for quality related problems/defects, correction of root causes related to detected problems/defects, and follow-up to ensure quality related problems/defects do not recur. The plan shall include the schedule of quality assurance/control inspections planned by the Contractor. 100% compliance with the QMS is required. (CDRL Reference in paragraph 4.2)

5.10 Trafficking in Persons: The Contractor shall comply in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract as it relates to Trafficking in Persons. Additional information about Trafficking in Persons is available at the site for the Department of State’s Office to Monitor and Combat Trafficking in Persons. http://www.state.gov/j/tip

PR: FD2060-__-_____ PWS REVISION: 0 14

6.0 Appendices

6.1 Appendix A, References

August 20, 2020 Entirety

October 29, 2020 Entirety

as amended through January 1, 2004

Entirety

6.2 Appendix B, Acronyms