Appendix E Performance Requirements Summary.docx

APPENDIX E - PERFORMANCE REQUIREMENTS SUMMARY (PRS).

Listed below are the main performance standards for this requirement. These standards represent “Satisfactory” performance. The QASP extends the performance levels to include “Very Good,” “Exceptional,” “Marginal,” and “Unacceptable.” The Government and Contractor will review the QASP on a quarterly basis to determine if any changes are necessary.

The contractor shall prepare and submit a Sustainment Modernization Plan comprising of a Management Plan and Application Software Support Plan. The Management Plan shall discuss the proposed program management and staff structure related to performance of the tasks in this PWS. The plan shall explain, in detail, how the contractor will manage the worldwide mission of the Sustainment Modernization Program.

The contractor shall prepare and submit an Application Software Support Plan. The plan shall discuss the continued support of the existing application software as well as any transitions to application software that will be new to the Sustainment Modernization program.

C 2.1.3 C.2.1.3.1 C.2.1.3.2 Contractor shall deliver the Sustainment Modernization Plan within 30 days of contract award. The Government DAC will review and may require revisions to this plan within 30 days of receipt.

Contractor shall deliver the Quality Control Plan within 30 days of contract award. The Government (DAC) will review and may require revisions to this plan within 30 days of receipt.

The contractor shall conduct development of architecture for data storage that allows ingesting large volumes of various types and formats of data and access to the collected data. Such example could be clouds or new procedures to make data access easier and more efficient for DAC analysts.

The contractor shall develop and maintain Enterprise Resource Planning System (ERP) data retriever applications to allow data collection and storage from Global Combat Support System – Army (GCSS-A), Vantage, and other Army web based data systems such as the General Fund Enterprise Business System (GFEBS).

The contractor shall provide support and automated processes for ingesting multiple data sources including time series sensor data and ERP data, into the DAC’s Sustainment Data & Analysis System (DAS).

C.3 C.3.1 Data shall be checked for completeness and accuracy prior to delivery to DAC.

The contractor shall perform data maintenance to identify, verify, and correct errors or anomalies in the historical data elements of the database as approved by DAC.

The contractor shall develop a standard operating procedure (SOP) for backup and recovery of data for each platform hosted by the contractor to ensure there is no loss of data, fidelity and access. The SOP shall address the interaction with DAC/Army network/cloud policies as well as any shortfalls of the DAC/Army/cloud network policies.

The contractor will provide all required elements from required data sources. Circumstances were this may not be possible must be explained to COR in writing.

C.3.2.1 C.3.2.2 C.3.2.3

The contractor shall perform data maintenance to identify, verify, and if required correct errors or anomalies in the historical data elements of the database to include software errors. The Backup/Recovery SOP shall be presented to DAC within 30 days of task order award. As part of this process, the contractor shall demonstrate by platform (at least once per year) a disaster requiring full restoration.

The contractor will provide research, analysis, and technical support for identifying and mitigating the architectural limitations and structural data gaps within the Global Combat Support System – Army (GCSS-Army) that inhibit data analysis efforts.

· The contractor will support the Analysis Team in the development of techniques to determine the veracity and integrity of GCSS-Army data through comparative analyses with the legacy Sample Data Collection & Analysis database.

· The contractor will research statistical or AI/ML methods to identify and resolve identified data gaps.

· The contractor will assist the government Analysis Teams in developing business rules, work flows, and system logic to build the protocols necessary to verify ERP data and to validate analysis tools.

· The contractor will leverage existing and emerging technologies to shape, inform, and train data models capable of establishing quantitative and qualitative measures for verifying the veracity of ERP data.

C.3.3

The contractor will execute tasks related to Prognostics and Predictive Maintenance (PPMx), Condition Based Maintenance+, Predictive Logistics (PL), and other sustainment modernization projects. This includes tasks such as: data processing, maintaining and sustaining tools (e.g., FIT & VePRO), producing analytical products, and engineering support for the Army’s PPMx/PL implementation. Bi-weekly per Appendix G format the contractor shall provide appropriate documentation, code and other artifacts that can be used to help transition capabilities to the cloud and Logistics Enterprise.

The contractor will provide engineering and analysis support for PPMx for various Army customers including AMC, PMs, CASCOM, and AFC.

The contractor will provide Failure Reporting Analysis and Corrective Action System (FRACAS) capabilities and tools by providing DSC data from TWVs Monthly (or in near real time where wireless is approved), FRACAS technician field support, Government engineering/analytical support and G-Army maintenance data cleansing and analysis.

The contractor will provide the following on selected C5ISR to enable CECOM platforms with PL/PPMx capabilities. These capabilities will align to the PPMx ICD.

- Data Collection

- Data Evaluation & Analysis

- Data Conversion

- Mx & ERP Data Analysis

- Cost Modeling/Analysis Support

- Overall Engineering and Oversight of tasks The contractor will download JBLM HIMARS DSC and usage data from both truck and launcher on the same day once a month.

The contractor will provide technical support to develop and implement a 6TAGM battery capacity tester by performing discharge and charging events at various field locations.

The contractor will provide technical support on the implementation of solar panels on ground equipment at various CONUS field locations.

The contractor will provide Material Issue Analysis technical support providing analytical expertise to uncover systemic materiel failures and issues arising from inefficient sustainment processes or policies.

The contractor will provide technical support to ground units within the MDO Backpack innovation project.

The contractor will perform monthly site visits and collect NGATS data in support of DACs mission to conduct a Performance & Return of Investment (ROI) analysis on the NGATS for COMPOs I-II after initial fielding to locations at Ft Bliss, Ft Hood, Idaho, and Mississippi.

The contractor will coordinate with unit POCs & extract monthly archived data from each NGATS location and pull each location UIC workload data documented within GCSS-Army.

The contractor will investigate processes for Integration of Artificial Intelligence (AI) and Machine Learning (ML) directly into SAP products.

The contractor will integrate advance forecasting of supply parts and predictive approaches for health of systems using AI & ML to improve readiness.

The contractor will create models, dashboards and analysis techniques directly in Army Vantage using Supply, Maintenance and PPMx data.

The contractor will utilize Army Vantage and Advana data sources for logistics and PPMx analytics at echelon.

The contractor will leverage and develop analysis products in Palantir software tools to support customer needs.

The contractor will perform modeling and simulation of ERP data to improve decision making for customers.

C.3.4

Bi-weekly per Appendix G format the contractor shall provide appropriate documentation, code and other artifacts that can be used to help transition capabilities to the cloud and Logistics Enterprise.

Contractor shall deliver a report containing the JBLM HIMARS DSC and usage data to the Government (DAC) by the 25th of each month.

Contractor shall provide manually downloaded DSC data no fewer than once a month.

The contractor shall follow the DoD security controls defined in NIST 800-53, Recommended Security Controls for Federal Information Systems and the Army guidance on implementation of security requirements to ensure that the software will be or has been developed using secure coding practices in a manner that minimizes security flaws within the software.

The contractor shall maintain, secure and backup all software.

The contractor shall maintain two environments, one for production and one for development.

The contractor shall revise, enhance and improve the DAS, including software, databases, data warehouses, hardware, environments, processes and procedures as required by DAC.

The contractor shall have responsibility to sustain all Army Portfolio Management System (APMS) administrative roles, certifications and registrations of proposed software within the limits of authority granted by DAC.

C.5.1 C.5.2 C.5.3 C.5.4 Prior to the execution of a software development Task Order, the contractor shall provide the Army a copy of the contractor‘s secure coding best practices policy. Upon delivery of the software to the Army the contractor shall certify to the Army in writing that the contractor complied with the Policy in the performance of its obligations under the task order. Software shall be version controlled, thereby enabling an audit trail of changes and version rollback when necessary

The contractor shall deliver source and executable code for any new portal, graphical user interface, business layer logic or customized data access layer, or for any modifications to existing portals, graphical user interfaces, business layer logic or customized data access layers.

The contractor shall deliver reports as listed in this PWS, pursuant to required CDRLs or other government required format.

Visibility of all tables and views shall be granted to any DAC employee or contractor approved by the COR that is not contractor-owned.

The contractor shall provide a list of all third party software products included in the application, development environment and/or runtime environment.

C.6.1 C.6.2 C.6.3 C.6.4 This list shall include both open source and commercially produced products. All licensing materials for the list shall be made available to the government for inspection. The government reserves the right to approve or deny the use of these products in the applications.

The contractor shall update the DoD Risk Management Framework (RMF) Assessment and Authorization (A&A) documentation to ensure that the A&A artifacts are kept current and contain all information, and supporting evidence is documented, complete, and available for the next A&A.

The contractor shall provide all required information to the DAC Information System Security Manager (ISSM) to obtain/renew any required RMF processes and applications.

The contractor shall ensure that all pertinent information is provided to the DAC IAM to obtain/renew the RMF for the ground and aviation data information software applications.

C.7.2 C.7.3 Application Certification and Accreditation documentation shall be kept current. Information provided to the government (DAC) will include, but is not limited to data flow diagrams and Security Technical Implementation Guide (STIG) checklists.

The contractor, in cooperation with DAC, shall ensure that the DAS maintains a 99 percent uptime.

The contractor shall notify the COR within twenty-four hours of any government furnished hardware failures.

The contractor shall receive, track and respond to all DAC Analyst Quality Deficiency Reports (A2QDRs) logged into the SharePoint QDR applications. The A2QDR process formalizes the process of correcting errors in the DAC applications and data when discovered by analysts. The contractor shall do causative research to determine the root cause of the discrepancy, fix all affected data and the root cause of the discrepancy, including software modifications, and report to the government COR team when the issue is resolved.

The contractor shall perform routine data maintenance to search for and correct errors in the static data elements of the data base.

All data under contractor control shall be backed up to ensure minimum data loss and downtime.

C.8.1 C.8.2 C.8.4 C.8.5 C.8.6 Production environment shall maintain a 99% uptime. The contractor shall notify the COR within twenty-four hours of any government furnished hardware failures. All contractor-purchased hardware or software shall be consistent with the DoD Unified Capabilities Approved Products List (UC APL). All purchases shall be in accordance with AR 25-2. The contractor shall have three business days to accept and provide an initial response to an A2QDR. The initial response does not have to fully resolve the A2QDR, but should provide the contractor’s initial assessment and path forward to correct the deficiency. Deficiencies that are simple in nature shall be corrected in five business days. More complex issues will be assigned a date for resolution by the government COR team after consulting with the contractor on the complexity and depth of the issue.

The contractor shall have a SECRET security clearance.

The Contractor shall develop and implement a security education program to ensure contractor personnel understand and are familiar with the safeguarding of classified information.

C.12.1.3 All contract personnel shall submit to COR: AKO sponsorship and CAC application within 7 days of hire. Once approved by COR, contractors shall have 7 days to obtain AKO/CAC.

QUALITY CONTROL. Quality Control (QC) shall be performed in accordance with the PWS and the attached Quality Assurance Surveillance Plan (QASP) below.

Acceptable Quality Level (AQL)

Quality Control Plan