Attachment_4_-_PWS_for_Task_UPDATED_20170818.docx

Task Sample Data Collection and Analysis

This task is similar in format to a typical AMSAA Sample Data Collection Task Order. This is a cost plus fixed fee and firm fixed price task order. The Background Section includes information about the task and is intended to provide sufficient information so that Offerors have an understanding of the environment and scope of the effort. The Applicable Documents Section is representative of the documents that would be pertinent to conducting the Task Order work. The Requirements Section contains several products typical for most Task Orders.

In response to this task, include a detailed technical approach describing how you will solve the requirements. For this task the period of performance (PoP) will be 12 months as that is representative of AMSAA SDC task orders.

The offeror shall provide a narrative response describing the Technical Approach of this task. Offerors shall provide a Basis of Estimate (BOE). The BOE shall include the labor categories and hours required to complete the Task as proposed and the rationale to support the labor estimates. The BOE shall be correlated with each task and subtask as described. The BOE shall NOT include any rates or cost information inclusive of material, travel or other direct costs (ODCs). The Offeror shall populate the Government provided spreadsheet, Attachment 1 Cost Model, with all costs for this task. The BOE file is NOT included in the Task page limitations.

This task order will have FFP and CPFF CLINs. The FFP will be for services of the “Core Team” and the CPFF will be for services of Base SDC-A. The Base SDC program changes frequently precluding it from being FFP. The Core Team is those positions outlined in the PWS that are not likely to change due to changes in equipment densities and collection locations. Core Team under this task order shall be primarily located at Aberdeen Proving Ground, MD. Core team members may also be located at other SDC-A sites based on positions that are constant and not likely to change. The Core Team responsibilities include management, training, database administration, quality control and analysis duties and functions in support of the Sample Data Collection contract. Services to be performed under this task order are outlined in section C.3 Deliverables are outlined in CDRLs A0001-A0009. Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation and the limitation of funds specified in this contract. All travel requires Government approval/authorization and notification to the COR. The allowability of travel costs are determined by FAR 31.205-46.

C.1. INTRODUCTION TO SAMPLE TASK

This Performance Work Statement (PWS) describes the requirement for performance of Sample Data Collection and Analysis (SDC&A) services on selected models of Army aviation equipment (rotary, winged, and unmanned aerial systems), ground combat systems, tactical wheeled vehicles, and ground support equipment.

The Army SDC&A Program involves three types of data collections:

1. The first type captures data during field training exercises (FTX). Generally, a sample of select equipment from a Brigade Combat Team (BCT) or Combat Aviation Brigade (CAB) is captured during the entire rotation of the exercise. The duration of an FTX typically ranges from two weeks to three months.

1. The second type captures data on select equipment on a continuous basis for an indefinite period of time. This may include unit deployments in support of Overseas Contingency Operations (OCO).

1. The third type includes special, short-term field information tasks designed to support Army Staff, Combined Arms Support Command (CASCOM), Program Executive Offices (PEO), Program Managers (PM), and Life Cycle Management Command (LCMC) requirements that do not dictate a full-scale SDC&A project. They may also be used to augment selected Army Staff objectives, but will not duplicate other ongoing efforts.

The contractor shall collect, maintain, and deliver required data elements for the SDC&A program. Data elements are used for multiple analyses, including repair parts analysis, identifying reliability and maintainability characteristics of equipment over the life cycle, providing assessments of fleet health, analysis of component life, and providing data for estimating Army studies for Manpower requirements.

Figure 1. AMSAA Organizational Chart. Sample Data Collection and Analysis (SDC&A) is a responsibility of the Field Studies Branch within the Logistics Engineering and Analysis Division.

The U.S. Army Materiel Systems Analysis Activity (AMSAA), is the Headquarters, Department of the Army (HQDA) Responsible Official for the Army SDC and Analysis (SDC&A) Program, and has full responsibility for administering the program as prescribed in Army Regulation 750-1. The SDC&A program requires the capture of operational tempo (OPTEMPO), and all specified on-item maintenance data (e.g., actual part replacements and maintenance man-hours) performed on Army ground systems and aviation systems at the weapon system platform/serial number level of detail. This includes vehicle health data on ground vehicles. Army Regulation 700-138 states, “Empirical data generated by SDC&A offers the most extensive maintenance/logistical information available. Because of the high confidence level of the data, it is used by materiel developers and readiness analysts to identify, target, and fix equipment deficiencies that adversely impact materiel readiness. SDC&A provides feedback to participating units on a recurring basis, as well as lessons learned to all users and maintainers of equipment in the SDC&A program. This provides an essential link between the users, maintainers, and the materiel developers for rapidly identifying and correcting equipment and logistical deficiencies that impact readiness.”

These data are collected on a non-interference basis with operational units worldwide during FTX, garrison activities, and contingency operations. Comprehensive quality control/assurance of the baseline data is performed, and appropriate corrections are made within the SDC&A dataset to allow for the most accurate analyses as possible.

Requests for SDC&A data and analysis are routinely received from senior Army leaders, support brigades, and operational units to influence ongoing planning and decisions. Examples of requests include: materiel system non-mission capable rates; part replacement cost/frequency drivers; readiness drivers, OPTEMPO trends; seasonal/environmental trends; system and component reliability trends; vehicle aging trends; logistical impacts of add-on-armor; and usage data, root cause, special studies and fleet health assessments.

The SDC&A program also includes ground vehicle operational Health and Usage Monitoring (HUM) and Reliability Centered Maintenance (RCM) data collection and analysis. AMSAA provides critical health and usage monitoring system data and analysis to maintainers, commanders, users, testers, engineers, and LCMCs. Development of algorithms will continue to identify vehicle issues and help predict impending failures. Development of health indicators and prognostic algorithms will continue through multiple data sources. Each algorithm will be capable of predicting and providing significantly earlier warnings of failure than current warning indicators on major assemblies. AMSAA will also utilize data acquisition systems to monitor other items of interest, to include but not limited to electrical power consumption of vehicles and generators. The AMSAA HUM program results in significant benefits, such as: identification of readiness drivers, avoiding a non-mission capable day through prognostics; preventing an accident through improved situational awareness; better understanding of the condition of a vehicle prior to dispatch; continuous product improvement; influencing condition-based RESET; and cost avoidances/savings. RCM data collection provides AMSAA with validated and verified root causes of failure, failure modes and effects information at the platform either when it is currently undergoing maintenance or preceding an anticipated component failure.

The SDC&A program requires collection and verification of data in support of the SDC&A additional mission to provide independent logistics analysis and provide the Army with materiel analyses to detect systemic materiel issues and develop actionable recommendations derived through Soldier feedback, technical and statistical analyses, and direct observation. The SDC&A research and analysis component of this program develops and delivers comprehensive mitigating and corrective courses of action for systemic materiel issues on wheeled, tracked, engineer, materiel handling, weapons, and ground support equipment using data-driven analyses. The methodology used for this program consists of onsite data collection; problem definition; technical research; root cause analysis; solution and mitigation strategy development; corrective action implementation; and disposition tracking.

Products developed by AMSAA include: product improvement analysis; physics of failure analysis; failure mode and effect analysis; root cause analyses; systems performance and effectiveness analysis; quality deficiency exhibits; field advisory reports; and special studies upon request. The SDC&A research and analysis capabilities are a valuable asset to the Army's program managers, the Army Materiel Command, and to operational forces. The results of SDC&A efforts influence improvements to engineering design, reliability, maintainability, quality, safety, and training, and generate millions of dollars in cost avoidance/savings/quality.

The results of the SDC&A program data collection effort must be complete and of the highest possible quality, as the products of the SDC&A Program are used by HQDA staff, PEOs/PMs, AMC, TRADOC, FORSCOM, CASCOM, and (most importantly) operational commands and units.

C.2 APPLICABLE DOCUMENTS AND REFERENCES

The contractor shall be responsible for ensuring that the most current version of all applicable documents are used. Some applicable references are:

· AR 25-2, “Information Assurance (IA)”

· AR 70-1, “Army Acquisition”

· AR 700-138, “Army Logistics Readiness and Sustainability”

· AR 700-139, “Army Warranty Program”

· AR 700-4, “Logistics Assistance”

· AR 702-7, “Product Quality Deficiency Report Program”

· AR 702-7-1, “Reporting of Product Quality Deficiencies”

· AR 710-2, “Supply Policy Below the National Level”

· AR 750-1, “Army Materiel Maintenance Policy”

· AR 750-10, “Army Modification Program”

· DA PAM 738-751, “The Army Maintenance Management System – Air”

· DA PAM 750-8, “The Army Maintenance Management System”

· DA PAM 700-24, “Sample Data Collection”

· DA Form 2408-12, “Army Aviators Flight Record”

· DA Form 2408-13-1, “Aircraft Inspection and Maintenance Record”

· DA Form 2408-13-2, “Related Maintenance”

· DA Form 2408-13-3, “Aircraft Technical Inspection Worksheet”

· DA Pamphlet 750-8, “The Army Maintenance Management System (TAMMS)”

· DA Pamphlet 738-751, “Functional User’s Manual for the Army Maintenance Management System”

· DoD 8140.01, Cyberspace Workforce Management

· DoDI 8500.01, Cybersecurity

· DoD 8570.01-M, Information Assurance Workforce Improvement Program

· Software Development Standards Life Cycle (SDLC) Guidelines

· National Institute of Standards and Technology (NIST) 800-53, “Recommended Security Controls for Federal Information Systems”

· Special Devices Standard Operating Procedures

· Condition Based Maintenance Standard Operating Procedures

· Management Plan

· Quality Control Plan

· Field Monitors Guide

· Technical Manual 9-2320-Series, Wheeled and Engineer Vehicles

· Technical Manual 9-2330-Series, Trailers

· Technical Manual 9-2350-Series, Combat Systems (Tracks)

· Technical Manual 9-2355-Series, MRAP Vehicles

· Technical Manual 9-6115-Series, Power Generation

· Technical Manual 1-1520 Series IETM Aviation

· Technical Manual 1-2840-248 Series IETM Aviation

· Technical Manual 1-2835-205 Series IETM Aviation

· Technical Manual 1-1550-689-23&P IETM Shadow

· Technical Manual 1-1550-1689-23&P IETM Shadow V2

· Technical Manual 1-1550-696-23&P IETM Gray Eagle

· Vehicle Health, Usage and Monitoring Diagnostic Trouble Code, Field Root Cause Analysis Guide

C.3. SERVICES TO BE PERFORMED

The offeror must be prepared to explain their program and management techniques to be applied in the establishment and management of this program.

The contractor shall ensure that databases are populated with the current and historical data captured under this contract.

The contractor shall ensure that the data recorded accurately reflects the event that is captured. When issues occur, the contractor shall research the issue and correct all data (past and present), as needed to address the issue. Additionally, if the cause of the issue is rooted in the collection software or collection methodology, the contractor shall correct the software and/or methodology so that the issue does not happen again.

Data collected, compiled and aggregated (regardless of platform) during performance of this PWS is Government-owned. The original sources of data are also Government-owned.

Unless otherwise stipulated and agreed to in the contract, the software used to collect, revise, manage and aggregate the collected data is Government-owned.

Work performed under this contract shall comply with the latest versions of applicable industry standards.

C.3.1. Phase-In.

C.3.1.1. Within 15 days after contract award, the contractor shall conduct an initial review of current organization equipment authorization documents applicable and current equipment technical manuals (TMs), military specifications (MILSPECs) and other technical publications which pertain to the unit equipment involved. These documents will be made available by AMSAA to be reviewed on site at the AMSAA office, APG, MD or through the Logistics Support Activity’s (LOGSA) website (https://liw.logsa.army.mil).

C.3.1.2. SDC&A Seminar.

Within 15 days of contract award (and annually thereafter) the contractor shall participate in a two-day AMSAA-conducted SDC&A seminar at Aberdeen Proving Ground, Maryland. At a minimum, the contractor’s supervisory personnel shall participate.

AMSAA will determine the exact dates, time, and location of the seminar.

The seminar will cover the following areas:

· Introduction to the SDC&A Program

· Background

· Program Methodology

· Data Requirements

· Equipment sample densities

· Definitions of important terms

· Army Structure

· Maintenance and Supply Flow

· Field Level Maintenance

· Sustainment Level Maintenance

· Review of Standard Forms and Reports

· Particular Areas of Concern

· Operation and input of data into the SDC&A database

· Special data collection devices standard operating procedures

· Application Software Development Standards and Change Management Policies

· Data accuracy standards and requirements

C.3.1.3. SDC&A Orientation.

Select contractor personnel shall participate in a two-week orientation on the steps and procedures for the compilation of standardized reports generated in the SDC&A program, and operation and maintenance of the government SDC&A database. Specific personnel to participate in the orientation will be identified after award, but will likely include program managers, database managers, and other technical support staff.

During the orientation, each deliverable product required by this PWS will be reviewed and explained to ensure mutual understanding.

AMSAA will determine the exact dates, time, and location of the orientation.

C.3.1.4. Data Collection Plan.

The contractor shall prepare and submit a Management Plan, Quality Control Plan and a Field Monitor’s Guide within 30 days of contract award. These three documents comprise the Data Collection Plan.

C.3.1.4.1. Management Plan. See CDRL A0001

The contractor shall prepare and deliver a Management Plan within 30 days of contract award. The 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 SDC&A Program.

Specifically, the Management Plan shall:

· Explain how issues that arise in the field will be communicated and resolved expeditiously, whether internal to the company, or between the contractor and the Government.

· Include provisions that data monitors’ work load is monitored and periodically assessed and re-balanced as required to ensure maximum efficiency.

· Describe the contractor’s optimal ratio of “front line” SDC&A employees to supervisors.

C.3.1.4.1.1 Application Software Support Plan.

The contractor shall prepare and submit an Application Software Support Plan within 30 days of contract award. 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 SDC&A program. A copy of the plan must be provided to the AMSAA Information System Security Manager (ISSM).

Minimally, the Application Software Support Plan shall address:

· Define the support requirements and impact during the transition period.

· Define the methodologies, procedures, environment(s) and documentation for change management.

· Application software testing strategies

· Development environment assessment highlighting any differences required from the current environment.

· Third party packages, commercial off the shelf (COTS) to be incorporated into the SDC&A software applications or procedures.

AMSAA will review and may require revisions to this plan within 30 days of receipt.

C.3.1.4.2. Quality Control Plan (QCP). See CDRL A0002

The contractor shall prepare and deliver a QCP within 30 days of contract award. The QCP will detail the methodology the contractor shall use to measure compliance with the requirements of this PWS, and describe mitigation measures to ensure continuous improvement.

Specifically, the QCP shall:

· Outline the contractor’s organizational roles and responsibilities for quality management.

· Describe, in detail, processes and procedures for measuring process quality, identifying trends, and implementing effective corrective actions when required.

· Outline procedures for software installation and upgrade for each platform, to ensure efficiency and cost effectiveness.

· Outline procedures for backup and recovery of data for each platform, to ensure there is no loss of data, fidelity and access. Network Enterprise Center (NEC) hosted platforms are backed up by NEC policy. This document shall address the interaction with NEC policies as well as any shortfalls of the NEC policies.

AMSAA will review this plan within 30 days of receipt. Revisions may be required.

C.3.1.4.3.Field Monitor’s Guide. See CDRL A0003

The contractor shall prepare and deliver a Field Monitor’s Guide within 30 days of contract award. The Field Monitor’s Guide shall describe in detail the responsibilities and tasks required to execute the AMSAA’s Sample Data Collection and Analysis Program Specifically, the Field Monitor’s Guide shall describe the contractor’s:

· Processes/procedures for data collection, verification; and

· Methods for validating data accuracy.

The Field Monitor’s Guide shall be updated at least annually.

AMSAA will review this guide within 30 days of receipt. Revisions may be required.

C.3.2. Sample Data Collection, Analysis and Reporting.

AMSAA may require SDC&A services at the following sites:

Note: This is not an all-inclusive list. AMSAA reserves the right to expand or reduce the site list.

Projected equipment densities for collection will be specified in each task order. Exact sites and projected equipment densities are estimates only. The exact sites for data collection are dependent on unit OPTEMPO, AMSAA priorities, and funding. The number of collection sites and equipment may increase or decrease depending on AMSAA budgetary adjustments, unit deployments, and data collection requirements. The contractor shall adjust according to fluctuations in workload. Task orders will not be modified unless the variance in equipment quantities is +/- twenty percent.

Conduct Initial Inventories C.3.2.1.

Data Verification C.3.2.3.

Monitor and Record Data C.3.2.2.

Data Reporting C.3.2.6.

Data Maintenance of Historical Elements in database C.3.2.5.

Data Delivery C.3.2.4.

Health and Usage Monitoring (HUM) C.3.2.7.

Reliability Centered Maintenance (RCM) C.3.2.9.

Research, Analysis, and Technical Support C.3.2.8.

Figure 2 .SDC&A Collection and Reporting Tasks

Demonstrate your methods for accomplishing the following tasks in an expedient and effective manner. Describe how you would perform the initial inventories and reporting/validating data: identify any performance risks and explain risk mitigation measure; explain how they would manage the worldwide mission and maintain quality control of the data collection tasks. Must describe how the data monitor will locate equipment out of the immediate area to insure all inventories are completed and the baseline is set in order to conduct the program and explain how to keep AMSAA apprised.

C.3.2.1. Initial inventories.

C.3.2.1.1. The contractor shall conduct initial inventories of the specified unit’s equipment selected for induction in the SDC&A program. See Appendix A for the overall equipment list. This task involves collecting data on items of ground and aviation equipment as specified in this paragraph. Equipment is considered enrolled into the SDC&A program, once the inventory is completed and the associated data described in this paragraph is entered into the SDC&A system.

Each Task Order will include an equipment density list for that effort if required. AMSAA may adjust the equipment density as required. On each item, the following data shall be recorded during the initial and final inventories. Data elements may be added or eliminated as required by AMSAA. See Appendix B for a detailed explanation of the forms.

Ground and Aviation Systems

· Unit standard designation (including brigade and division affiliation)

· Unit Identification Code (NOTE: UICs do not include the letters “I” or “O”)

· Unit home location

· Data collection location

· Date of inventory

· Type of item (bulk or individual)

· Configuration (armor packages installed)

· Equipment noun nomenclature

· Equipment model number (Army type designator as listed in the current Master Maintenance Data File-MMDF)

· Equipment serial number (individual items only) as shown on the data plate and validated with unit records.

· Equipment unit identification number (e.g. bumper number)

· Equipment National Stock Number (NSN) End item NSNs shall be compared to the equipment model list. The list will be periodically updated by AMSAA and provided to the contractor in writing. An initial model listing is provided in Appendix A.

· Name of manufacturer

· Year of manufacture (individual items only)

· Year of overhaul (if any, individual items only)

· Cumulative usage since new or last overhaul (miles, actual rounds, hours) (individual items only), while under collection

· Identify all maintenance and OPTEMPO/Usage as described in paragraph C.3.2.2. Monitor and record data.

· Not mission capable time, maintenance, or by Army Materiel Status System (AMSS) rollup by system/subsystem administration number (Unit).

· Not mission capable time, supply, or by AMSS rollup by system/subsystem administration number (Unit).

· Quantity serviceable (bulk items only)

· Quantity unserviceable (bulk items only)

· POL consumption (as directed by the COR)

· Current usage metrics (miles, hours, rounds, flight hours, landings, launches, etc). Usage source for ground includes visual readings and on-item Digital Tracking Equipment. Usage source for aviation includes DA Form 2408-13-2, “Related Maintenance”.

· Vehicle registration number (ground only)

· Digital Operations Requirement (log digital component metadata)

· Global Combat Support System-Army (GCSS-A) notifications and other unique terms

· System of systems considerations

· Component configuration management and unique identification where appropriate

*Note: Each reportable item of equipment in the unit is classified as either “individual” or “Bulk”. The difference is that the individual items have usage indicators (odometers, hour-meters, round count, etc..) while the “bulk” items do not.

Note: The current primary source for Aviation data is ULLS-A(E) and Unmanned Aircraft Systems-Initiative (UAS-I)as well as communications with the maintaining unit. Other sources can and should be used to supplement and correct the data from the above sources.

Note: Ground data is currently captured from several sources, including: hardcopy documents, SAMS-1 (Legacy System), GCSS-A and communications with the maintaining unit. Other sources can and should be used to supplement and correct the data from the above sources.

The offeror must be able to explain how they would administer database maintenance and software maintenance type tasks in order to insure an effective data mining program.

C.3.2.2. Monitor and record data.

This task involves monitoring and recording data from all documentation, using units current LIS, and/or observed unit and support activity maintenance actions and maintenance records for equipment enrolled in the collection effort. It includes any maintenance action performed by the operator/crew, unit/support activity, or other echelon of support that corrects a fault or deficiency, or that requires a replacement part and shall be recorded. In addition, it includes any documented inspection, regardless of faults found, that records man-hours expended to complete the inspection.

Applications of Modification Work Orders (MWO) are scheduled maintenance events under the SDC&A program. When a repair action/part that is not included in the equipment’s applicable technical manual scheduled maintenance (service schedule) list is found, that action/part shall be recorded as an unscheduled maintenance event.

All scheduled maintenance shall be recorded as NMC “No” in the database.

Must be able to demonstrate the procedures for insuring accurate recording of this data. Also include how the working relationship that are required to be established with the individual units in order to ensure the data is correct and reliable.

C.3.2.2.1. The contractor shall monitor and record data from all documented and/or observed unit and support activity maintenance actions, and maintenance records for equipment enrolled in the collection effort. This includes both ground equipment and aviation equipment. Contractor shall collect required data from units current Logistics Information Systems (i.e. Global Combat Support System-Army, Standard Army Maintenance System-Enhanced, Unit Level Logistics System Aviation Enhanced (ULLS-A(E) and Unmanned Aircraft Systems-Initiatives (UAS-I), etc.).

The Military Occupational Specialty (MOS) of personnel performing maintenance shall be verified and edited when unit records are incorrect (see DA Pam 611-21 for MOS information).

The contractor shall annotate whether maintenance is performed by a contractor or Department of the Army civilian. Verify and record direct labor man-hours for each maintenance action. If the maintenance code is recorded as a replacement, the contractor shall verify that the part was actually replaced. For each recordable maintenance action that occurs during the collection period or exercise, the following data shall be reported by the contractor personnel. Data elements may be added or eliminated as required by AMSAA.

The repair times recorded during the data collection effort shall reflect all of the time utilized by the mechanic(s) in the performance of that specific action. It shall include time consumed in accomplishing all of the following:

1. Getting to a job in the immediate area.

1. Consulting reference materials (such as log books and training manuals).

1. Preparing the item for maintenance (such as cleaning, lifting, and warming).

1. Diagnosing the problem (obtaining, connecting, and using diagnostic equipment in the immediate area).

1. Disassembly (including acquisition of tools in the immediate area).

1. Remove and replace actions (including acquiring parts available in the immediate area).

1. Align and adjust actions.

1. Final checkout actions

1. Documentation (preparing standard forms such as log books, DA Form 2407)

1. Initial and final inspections, including maintenance test flights when applicable. Maintenance test flight time shall only include the portion of the flight applicable to the test.

The repair times shall not include the following:

1. Contact team travel time to and from Maintenance Jobs.

1. Any delays during which the mechanic is available to perform other duties (waiting for parts delivery, waiting for facilities to become available, waiting for additional personnel).

1. Other activities not specifically related to the maintenance action being performed at the time (cleaning or maintaining the maintenance facility and equipment).

Note: Army units are expected to cooperate in providing maintenance and maintenance manpower information, but the contractor is responsible for the completeness and accuracy of the data through selected verification. A Unit Procedures Guide (Extract of DA PAM 700-24, Sample Data Collection) developed by the Army is provided as Appendix B, it outlines the procedures of the Sample Data Collection effort at the unit level. This approach uses slightly modified versions of the Army Maintenance Management System (TAMMS) forms. Equipment Inspection, and Maintenance Worksheets, Materiel Condition Status Report (ESR), The contractor may propose changes to the suggested procedures; however any changes shall be coordinated and approved by the Contracting Officer’s Representative (COR) prior to usage.

Contractor personnel shall avoid interfering with the participating unit’s or activity’s performance of its mission while collecting and verifying data. Contractor personnel shall be afforded access to pertinent data at each Army unit participating in this SDC&A effort. In particular, Field level, AVIM, and AVUM data recorded under TAMMS (DA Pamphlet 750-8 and DA Pamphlet 738-751) on DA Forms and other such information may be requested by contractor personnel on those items of material specified in Appendix A.

The offeror must be able to prove that the employees possess the adequate knowledge and experience required in order to understand of the wide variety of weapons systems they will be inducted into this program for the purpose of obtaining the maintenance, supply, and OPTEMPO data required. This must be clearly documented prior to any offers for employment is let.

All Equipment:

· Unit standard designation (Division, Brigade, Battalion, and Company)

· OPCON/ADCON Relationship

· Unit Identification Code (NOTE: UICs do not include the letters I and O)

· Equipment noun nomenclature

· Equipment model number

· Equipment serial number (individual items only) as shown on the data plate and validated with unit records.

· Technical Manual number and date

· Technical Manual figure and item number

· Date item returned to duty (aka Corrective Date)

· Functional Group Code (FGC) or Work Unit Code (WUC). For ground, the FGC is captured at the Task level. For all aviation, the WUC is captured at the event and task level.

· Noun nomenclature of each repair part used

· Prime NSN and actual NSN of part removed and installed. If the NSN is not available, the part number of each part shall be used to include Manufacturer Federal Supply Code (MFSC).

· Part numbers shall be researched and updated in the SDC&A database with the appropriate NSN when published in the Army Master Data file (AMDF). The contractor shall research and update this information monthly. When NIINs are assigned to part numbers, all database records shall be updated accordingly with all pertinent information. Part pricing shall reflect the most current FedLog pricing available in AMDF. The price shall be set at 1) Exchange Price, 2) Army Unit Price – Unserviceable Credit Value, or 3) Army Unit Price.

· Quantity of each repair part used. Document number of the repair part unless the action is recorded as “found during visit”.

· Manufacturer of Part (if available)

· Source of each part (e.g., Quick Supply Store (QSS), shop stock, ASL, Repairable Exchange (RX), controlled substitution, commercial source, etc.)

· Any part, as defined by the applicable Technical Manual Preventive Maintenance Checks and Services chart that would cause the item to be Not Mission Capable (NMC) shall be identified. This requirement is not dependent on how the equipment’s readiness status is reported by the owning unit and is not dependent on whether or not the part is identified as a safety deadline per AR 385-55. NOTE: Repair parts shall be recorded in the database as either NMC “Yes” or “No” for Ground equipment and Grounding X “Yes” or “No” for all Aviation equipment. Any maintenance, other than unscheduled maintenance, shall define maintenance actions as NMC “No”, regardless of the repair part designation.

· Level of maintenance

· Maintenance Code (repair, replace, adjust, service, inspection, test, odometer change, etc., shall be recorded using standard Army codes identified in DA Pamphlet 750-8 or as designated by AMSAA).

· Source Maintenance Recoverability code (SMR) from the part NSN is found in the equipment technical manual repair parts and special tools list (RPSTL).

· Brief narrative description of incident and corrective narrative action (equivalent to work order/notification description).

· Failure codes — (Shall be recorded using codes identified in Department of the Army Pamphlet 750-8 or as designated by AMSAA).

· MOS, skill level and additional skill identifier (ASI) of maintenance personnel who performed the work. Annotate KTR or CIV when maintenance is performed by contractor or Department of the Army Civilian personnel. MOS’s shall be compared to an allowable list provided by AMSAA. An initial MOS list is provided in Appendix (C).

· Maintenance Man-hours expended for each task.

· Part cost (as defined above) applied and Unit of Issue (UI) applied, current at time of maintenance event

· Full Army Master Data File (AMDF) information to include price of part, Materiel Category Code, Essentiality Code, Recoverability Code, Weight, Cube

· AMDF source of supply recorded on maintenance event at time of the event

· Exercise number - (Identifies each FEDC exercise and represents unique SDC&A sets)

· Identification of Scheduled, Unscheduled, MWO or other maintenance type.

· Remarks to explain unusual or extreme data (e.g. Maintenance man-hours that exceed the normal average for a particular task)

· Induction start date

· Induction stop date

· Work Order Number/Order Number - (If recorded maintenance action is under a valid work request) if no valid work order is available but a maintenance action has occurred, the action shall be recorded in the database as observed during unit visit.

· Cross reference identifier from sourcing system

Specific to Ground Equipment

· Unit identification number (e.g. bumper number) (individual items only)

· Date of maintenance visit/action/task

· Visit number

· Action number

· Task number

· Vehicle registration number

· CBM installation date (as provided by AMSAA)

· Standard Army Maintenance Systems Work Order Number or GCSS-A notification / order number

· Appendix for Reliability Centered Maintenance data elements to be collected

Specific to all Aviation Equipment Retrieve aviation equipment data collection elements. See Appendix D for aviation data forms and elements. TAMMS-A electronic forms including:

1. DA Form 2408-12, “Army Aviators Flight Record”

1. DA Form 2408-13-1, “Aircraft Inspection and Maintenance Record”

1. DA Form 2408-13-2, ”Related Maintenance”

1. DA Form 2408-13-3, “Aircraft Technical Inspection Worksheet”

1. Phase maintenance checklist

NOTE: The aviation equipment forms are collected via electronic file from Unit’s ULLS-A(E) and UAS-I server. For each recordable maintenance action that occurs during the collection period or exercise, the following data shall be reported by the contractor personnel. In addition, the following data elements shall be collected on each piece of aviation equipment. Data elements may be added or eliminated as required by AMSAA.

Data sources for Aviation Equipment are UAS-I, ULLS-A(E) (logbook, phasebook, work order, operations)

· End Item Identifier (EI_ID)

· Fault Date

· Task Number

· Zone (garrison, training, or deployed)

· System code (A, E, O, W)

· Status symbol

· When discovered code

· How Recognized code

· Malfunction effect code

· Begin age at time of event (e.g. hours)

· End age at completion of event (e.g., hours)

· Transaction Code - (e.g., Tech Supply, Repairable Exchange (RX), controlled exchange, or controlled substitution).

· In addition to MOS, record the Rank and Role of the maintainer and/or crew member

· When applicable, designate the event as being caused by Battle Damage

· When applicable, designate the event as being caused by (or related to)

· Corrosion

· OPTEMPO:

· Operation Date

· Beginning Flight Hours

· Ending Flight Hours

· Operation start location date and time

· Operation interim location date and time

· Operation end location date and time

· Mission symbol

· Crewmember(s) duty symbol

· Crewmember(s) hours

· Standard landings

· Non-standard landings

· Flight start location

· Flight interim location

· Flight end location

Specific to Aviation - UAS Equipment

· OPTEMPO for the UAV component shall be consistent with that stated for all aviation equipment.

· OPTEMPO for the Ground support equipment shall capture (as applicable) in place of Flight Hours: Launches, Landings, Operating Hours, Uses

· OPTEMPO for the Ground support equipment shall not capture starting, interim and ending measurements for locations.

C.3.2.3. Data verification during data entry.

Data verification is an integral part of the data entry process. All data fields shall be verified for minimally the following: range limits, reasonableness, applicability to weapon system or component, event time frame, locality/theater of event, consistency with Army guidelines and documentation, interrelated data elements, interrelated weapon systems, elimination of duplicates, deterrence to create multiple entities for a single entity, maintainer classification, and more as needed.

C.3.2.3.1. The contractor shall be responsible for the processing and quality control of field logistics data to include, but not limited to, verification of part numbers/NSNs, scheduled/unscheduled maintenance flags, Military Occupational Specialties (MOS), maintenance man-hours, repair part/task maintenance level and/or non-mission capable coding and OPTEMPO accuracy. OPTEMPO entries shall be no less than 98% complete and accurate. Mileage and hours shall be physically checked and recorded monthly and non-decreasing when comparing the initial versus operational statistics records.

C.3.2.3.2. The contractor shall assure that the event level data is appropriate for the specific end item model, to include but not limited to, the proper parts for the model are replaced as well as the proper MOSs are utilized.

C.3.2.3.3 The contractor shall provide a capability to compare individual equipment usage readings from all SDC&A program collection source. This capability shall be used to validate usage readings collected from any of the sources. It shall mark all readings as invalid or valid and both valid and invalid readings from all sources shall be delivered to the government. This capability shall also serve to facilitate a feedback mechanism by which invalid readings can be researched and validated, or archived as not for use. This capability shall provide an interface to input data provided by the government or third party sources to provide additional functionality as well as future compatibility.

The validity of a reading or set of related readings shall be determined by a set of rules that will be determined with input from the contractor and government. These rules shall include, but are not limited to, considerations for the nominal value of the readings, time period between readings, source of the readings and other technical aspects.

C.3.2.4. Data delivery.

The data collected from the field is recorded at the appropriate event level (weapon system dependent) in the Combined Enhanced Data Review Application (CEDRA(G) and CEDRA(A)) databases. This database is defined as an On-Line Transaction Processing (OLTP) database. As such, it is engineered to be responsive to data collection processes. Access for analysis is kept to a minimum.

The contractor shall collect data from DSC equipped vehicles at a frequency defined by the government and IAW paragraph C.3.2.7.4. The collected data shall be transmitted to AMSAA via electronic means at the end of each business day in the given time zone. The contractor shall keep records to insure that all data has been transmitted and the integrity has not been compromised.

Each night at the end of the business day, the daily events are aggregated into the CEDRA Metrics database, which is characteristic of a Decision Support System (DSS) and/or Data Warehouse. This database provides all the data for the analytic needs of the SDC&A program.

The contractor’s responsibility is to collect, verify, correct and maintain the Weapon System Event Level Data.

C.3.2.5. Data maintenance of historical elements in database.

C.3.2.5.1. 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 AMSAA. If the cause of the error is found to be software related, the software shall be corrected to prevent the problem from happening in the future.

C.3.2.5.2. The contractor shall develop a standard operating procedure (SOP) for backup and recovery of data for each platform, to ensure there is no loss of data, fidelity and access. DOIM hosted platforms are backed up by DOIM policy. The SOP shall address the interaction with DOIM policies as well as any shortfalls of the DOIM policies. The Backup/Recovery SOP shall be presented to AMSAA within 30 days of contract award. As part of this process, the contractor shall demonstrate by platform (at least once per year) a disaster requiring full restoration. This requirement is included in CDRL A0002.

C.3.2.5.3. At each collection site, the contractor shall maintain file storage of raw data collected from units in digital format, or hard copy format if digital storage is not available at the collection site. All supporting documents collected by the contractor during the period of performance of the task order shall be scanned and digitally stored for future reference for a period no less than 12 months from the end date of the task order.

C.3.2.5.4. The data forms for each item shall contain as a minimum the data specified in paragraph 3.2 of this Performance Work Statement. The quality and completeness of the data shall be the criteria for acceptability of the data. The specific minimum criteria are shown in the Performance Requirements Summary (PRS) Paragraph C.4, Appendix L.

C.3.2.5.4.1. All maintenance and OPTEMPO data shall be no less than 98 percent complete and accurate when delivered to AMSAA for use in the Army SDC&A program. Data accuracy will be measured by quarterly SDC&A data reviews from analysis of the data and government COR team site visits and assessments.

1. Quarterly SDC&A Data Accuracy Reviews will be scheduled by the government COR team and will focus on the completeness and accuracy of the contractor provided data present in the SDC&A database for all maintenance and OPTEMPO. The government COR team will determine the focus and extent of each SDC&A Data Accuracy Review. (i.e., Locations, Time Periods, and Models Reviewed)

1. The primary report used to calculate contractor accuracy during a Quarterly SDC&A Data Accuracy Review is the Maintenance Raw Data Report pulled from the SDC&A database CEDRA. Similar adhoc reports pulled from the SDC&A database will also be used as long as the report reflects the normal data composition and integrity of a standalone Army Maintenance Work Order/Maintenance Visit/Maintenance Event.

1. Each recorded Maintenance Visit/Event will be analyzed to determine the accuracy and completeness of the required data elements outlined in 3.2.2.1. Each Maintenance Visit/Event may consist of Maintenance Actions and/or Maintenance Tasks. To determine data accuracy, each Maintenance Visit/Event will be evaluated at the Maintenance Task level of detail.

1. In the Maintenance Raw Data Report, each Maintenance Task is represented by a “row” of data consisting of multiple data elements/fields as described in paragraph C.3 and all subparagraphs of this PWS. Therefore, each Maintenance Task will be evaluated by analyzing the accuracy of each data element in its “row” of data.

1. A Maintenance Task will be determined “not accurate” if one or more of the required fields outlined in Para 3.2.2.1 are missing, incomplete, or incorrect based on the original collected maintenance forms, the applicable Technical Manual, written instructions from the government COR Team, or are out of tolerance with acceptable usage, man hours, or parts quantities without corresponding comments in the remarks to satisfactorily explain the discrepancy.

1. Equipment OPTEMPO usage readings will be measured by each individual meter reading as required by this PWS. Readings will be determined “not accurate” if they do not meet the following accuracy requirements:

5. Meter readings from initial inventory throughout the data collection period shall be non-decreasing unless an actual meter change maintenance action has been recorded.

5. Meter readings resulting in a usage exceeding normal historical values must be reconciled as described in paragraph C3.2.3.3.

1. Aviation systems will follow a process similar to Ground Systems, with the following differences:

6. The Aviation Reviewed Database will be the primary source of information. In addition, Adhoc reports sourced from the Reviewed, Master and Raw databases will be incorporated.

6. Maintenance Events and Ops Events will be scored separately due to the difference in detail.

6. UAS and Helicopter will be scored separately.

6. When an error is found in an event, the process is to pull the entire event until it is corrected. Therefore, an event, in its entirety, will be considered “not accurate” when one or more errors are found in the event or any of its subcomponents, such as: tasks, crew, parts, and work hours.

6. The accuracy score will be calculated for the sample as: (total sample events – events in error) / total sample events.

1. There are critical data items to Aviation reports and analyses. The Aviation Systems scoring will focus on these items. However, AMSAA reserves the right to modify this list. Currently, the critical data items include:

7. OPTEMPO

0. Aircraft, OPS Date and OPS Number (key)

0. Location

0. UIC

0. Flight Hours

0. Mission Symbol

0. Beginning and Ending Flight Hour Age

7. Maintenance Events

1. Aircraft, Date, Event Number and System Code (key)

1. Location,

1. UIC

1. Maintenance Type

1. Status

1. When Discovered

1. How Recognized

1. Malfunction Effect

1. Level of Maintenance

1. Corrective WUC

1. Battle Damage

1. Mission Abort

1. Corrosion

1. Operationally Induced (Accident)

1. Beginning and Corrected Aircraft Flight Hour Age

1. Corrected Date

1. Man Hours

16. MOS, Rank, Role

16. Maintenance Level

16. Technical Inspection Hours

16. Total Man Hours

1. Part Corrections

17. NSN/Part No

17. WUC

17. Source Code

17. Tran Code

17. Fail Code

17. Part Quantity

17. AMDF Prices, SOS, Part Nomenclature, Prime NSN/NIIN

C.3.2.6. Data reporting.

The contractor shall prepare and deliver the following data reports.

C.3.2.6.1. SDC&A Monthly Activity Report (MAR) See CDRL A0004

Purpose: This report shall contain the contractor’s comments and significant issues encountered during the prior calendar month or the duration of the training exercise, as applicable. In addition, the report shall contain any suggested changes or improvements to the data collection and reporting procedures. The report shall address activities at each collection site.

Frequency: Once a month for the previous calendar month as stated in the CDRL. See Appendix E for an example of the MAR.

C.3.2.6.2. SDC&A Unit Feedback Reports. See CDRL A0005

Purpose: The contractor shall prepare a SDC&A Unit Feedback Report for every unit and/or location enrolled in the data collection program. The contractor shall deliver a copy of the feedback report to AMSAA within 14 calendar days of notification to produce the report. There are eight different sections in the Feedback report:

1. End Item Summary. A summary of the unit’s exercise equipment by model and nomenclature. Lists the model quantity, average and cumulative usage for each type of end item, maintenance information, total man-hours, parts costs, and parts replacement costs per mile.

1. Cost Drivers. Listed by end item, provides total parts replacement information in order of cost of replacement parts.

1. Frequency Drivers. Listed by end item, provides total parts replacement information in order of frequency of replacement.

1. Man-hours Drivers. Listed by end item, provides total parts replacement information in order of man-hours to replace.

1. MOS Summary. Listed by end item, provides information on Military Occupational Specialties, contractors, or Department of the Army Civilians that performed maintenance on the end item.

1. Acronym List

1. AMSAA Point of contact list

1. Unit Comments. A preprinted feedback sheet shall…