Attachment 0003 Integrated Product Support SOW Final.pdf

STATEMENT OF WORK (SOW)

FOR DEVELOPMENT AND PRODUCTION OF INTEGRATED PRODUCT SUPPORT

DELIVERABLES FOR PRODUCT MANAGER-FORCE SUSTAINMENT SYSTEMS (PM-FSS)

9/16/36K IECU

SECTION 1. Description/Specifications.

C.IPS.1.1 Statement of Work (SOW). The contractor shall furnish all the necessary personnel, materials, services, and facilities (except as otherwise specified herein), and otherwise do all the things necessary for or incident to the performance of the work as set forth herein.

C.IPS.1.2 Reserved.

C.IPS.1.3 Scope. This Statement of Work (SOW) establishes the scope for the development of Integrated Product Support (IPS) for the 9K/18K/36K Improved Environmental Control Units (IECU). The Contractor shall develop and produce the following as specified by this SOW, associated Contract Data Requirements List (CDRL). The requirements contained in this statement of work shall apply to each of the IECU variants below.

Variant BTU/hr. Voltage Phase Hertz

9K IECU 9,000 115 1 50/60

18K IECU* 18,000 115 and 230 1 & 3 50/60

36K IECU 36,000 208 3 50/60

*Note: The contractor shall provide separate, individual Technical Data Package deliverables and Physical Configuration Audit Plan and Report deliverables for the single phase and three phase 18K IECU. But all remaining data items required by this SOW shall combine the single phase and three phase 18K IECU into a single deliverable. For example, a single technical manual shall be delivered that covers both the single phase and the 3-phase variant of the 18K IECU.

C.IPS.1.3.1.1 The contractor shall develop and produce the following as specified by Section 7 of this SOW, associated CDRL, listed authorities and Appendices in Table below.

CDRL AUTHORITY TITLE SOW PARA/ATT

A033 DI-TMSS-81812(T) Monthly Status Report/Integrated Master

Schedule, (9K/18K/36K IECU)

C.IPS.1.3.14

A007 MIL-STD-31000B

DI-SESS-80776B

DI-SESS-81001E

DI-SESS-81002F

DI-SESS-81000F

ASME Y14 Series

TDP, Level III, (9K/18K/36K IECU) C.IPS.1.3.15, 6, Appendix 5

A009 DI-SESS-81646C

DI-SESS-81022E

Physical Configuration Audit (PCA) Plan & Report

C.IPS.1.3.3, 3.

A010

SA TA-STD-0017A

DI-SESS-81495B

MIL-STD-882E

Failure Modes Effects and Criticality Analysis

(FMECA)

C.IPS.1.3.4,

C.IPS.3.3.1,

Appendix 1

A011

SA TA-STD-0017A Fault Tree Analysis (FTA) C.IPS.1.3.4, C.IPS.3.3.1.1, Appendix 1

A012

SA TA-STD-0017A

Maintenance Task Analysis (MTA) C.IPS.1.3.4, C.IPS.3.3.2, Appendix 1

A013

DI-PSSS-81872A Level of Repair Analysis (LORA) C.IPS.1.3.4, C.IPS.3.3.3, Appendix 1

A014

MIL-STD-40051-2D w/C1

DI-SESS-81758A

Maintenance Allocation Chart (MAC) C.IPS.1.3.6, C.IPS.3.4, Appendix 1

A015

SAE GEIA-STD-0007-C

GEIA-HB-0007B

TA-HB-0007-1

IEEE 315-1975

DoD 4100.39-M

DI-SESS-81759A

Provisioning Parts List (PPL) (-12&P)

C.IPS.1.3.6,

C.IPS.3.6,

Appendix 1

A016

SAE GEIA-STD-0007-C

DI-SESS-81874

TA-STD-0017

Engineering Data for Provision (EDFP) (-12&P)

C.IPS.1.3.6,

C.IPS.3.5

A041 DI-TMSS-81817(T) TM Quality Assurance (QA) Plan (9K/18K/36K

IECU)

C.IPS.1.3.5,

C.IPS.1.3.8,

C.IPS.3.7.1

A017 DI-CMAN-80792B

DI-TMSS-81818

DI-TMSS-81819A

Validation Plan and Validation Report for -12&P TMs

C.IPS.1.3.5,

C.IPS.3.8.7

A018 MIL-STD-40051-2D w/C1 Operator and Field Maintenance Manual, including Repair Parts and Special Tools List (RPSTL) -12&P TM (New)

C.IPS.1.3.5,

C.IPS. 3.8,

Appendix 2, 4

A019 DI-SESS-81526C(T) Interactive Multi-media Instruction (IMI) Courseware

C.IPS.1.3.10,

C.IPS.3.12

A028 DI-SESS-81518D(T) Conduct of Training, Operator and Operator Maintenance (9K/18K/36K IECU)

C.IPS.1.3.9, C.IPS.

3.11, C.IPS.3.12

A026 DI-SESS-81518D(T) Program of Instruction (POI) Operator and Operator Maintenance, (9K/18K/36K IECU)

C.IPS.1.3.9,

C.IPS.3.11,

C.IPS.3.12

A022 DI-SESS-81518D(T) Instructional Performance Requirements Document, Operator (9K/18K/36K IECU)

C.IPS.3.11.1.2

A023 DI-SESS-81518D(T) Lesson Plan/Student Handouts/Visual Aids

(OPNET), (9K/18K/36K IECU)

C.IPS.1.3.9,

C.IPS.3.11,

C.IPS.3.12

A024 DI-SESS-81518D(T) Lesson Plan/Student Handouts/Visual Aids

(FLMNET), (9K/18K/36K IECU)

C.IPS.1.3.9,

C.IPS.3.11,

C.IPS.3.12

A043 DI-PACK-80121C

Special Packaging Instructions (SPI)

C.IPS.1.3.7,

C.IPS.3.9,

Appendix 3

A025 DI-SESS-81758A Logistics Management Information (LMI), Preservation & Packaging, (9K/18K/36K IECU)

C.IPS.3.9.3

A026 DI-SESS-81518D(T) Program of Instruction (POI) Field Level Maintenance, (9K/18K/36K IECU)

C.IPS.1.3.9,

C.IPS. 3.11,

C.IPS.3.12

A027 DI-SESS-81518D(T) Instructional Performance Requirements Document, Maintainer (9K/18K/36K IECU)

C.IPS.3.11.1.3

A028 DI-SESS-81518D(T) Conduct of Training, Maintenance (9K/18K/36K

IECU)

C.IPS.1.3.9,

C.IPS.3.11,

C.IPS.3.12

A029 SAE GEIA-STD-0007-C

GEIA-HB-0007B

DI-SESS-81759A

LOGISTIC PRODUCT DATA SUMMARIES

(LDPS)-Screening

C.IPS.3.6.1.1

A030 DI-PSSS-80134B Proposed Spare Parts List C.IPS.1.3.11, C.IPS.3.13

A031 MIL-PRF-63002M Modification Work Order (MWO) C.IPS.1.3.14, C.IPS.4

A032 DI-CMAN-80792B(T)

DI-TMSS-81818

DI-TMSS-81819A

MWO Validation Plan and Validation Report C.IPS.1.3.12, C.IPS.4.4

C.IPS.1.3.2 Requirements. Contractors shall refer to this SOW and to the Department of Defense’s DD Form 1423 – CDRL of each data item to determine the Government’s work requirements. Proposals shall demonstrate experience developing quality IPS contract deliverables in support of the PM-FSS equipment item(s) specified in the solicitation.

C.IPS.1.3.3 Physical Configuration Audit (PCA). The contractor shall develop a PCA Plan and develop a PCA Report.

The PCA Report shall include the results of an evaluation of a production representative end item against the production drawings. The evaluation shall include all assemblies that report to the end item, all subassemblies, all Components of End Item (COEI), all Basic Issue Items (BII), and all provisioned parts.

C.IPS.1.3.4 Maintenance Strategy. The contractor shall be responsible for the development of the supportability analysis required to support logistics development. This analysis includes Level of Repair Analysis (LORA), Fault Tree Analysis (FTA), and Maintenance Task Analysis (MTA).

C.IPS.1.3.5 Technical Manuals (TM), and Repair Parts and Special Tools List (RPSTL). The contractor shall be responsible for the development of new Operator and Field Maintenance Manual including Repair Parts and Special Tools List (RPSTL). The contractor shall be responsible for developing a TM Validation Plan and Report.

C.IPS.1.3.6 Provisioning. The contractor shall be responsible for providing a Maintenance Allocation Chart (MAC) with Engineering Drawing Tree, Provisioning Parts List (PPL), and Engineering Data for Provisioning (EDFP) to support the provisioning process.

C.IPS.1.3.7 Packaging. The contractor shall develop any required Logistics Product Data (LPD) packaging data and Special Packaging Instructions (SPI) to support the end item.

C.IPS.1.3.8 Reserved

C.IPS.1.3.9 Training Aids/Materials. The contractor shall be responsible for the development of training aids/ materials inclusive conduct of training, lesson plans, trainee guides, visual aids and POIs.

C.IPS.1.3.10 Instructional Media Package. The contractor shall be responsible for the development of the Instructional Media Package, including three Interactive Multi-media Instruction (IMI) courses along with associated documentation.

C.IPS.1.3.11 Proposed Spare Parts List (PSPL). The contractor shall be responsible for the development of a Proposed Spare Parts List (PSPL) as onboard spares within the end item. The PSPL content shall provide a list of contingency spares sufficient to support the end item for the first ninety (90) days of deployment to any region in the world.

C.IPS.1.3.12 Modification Work Order (MWO). The contractor shall be responsible for the development of an MWO, which contains detailed instructions (including text and graphics) for making changes/ improvements to a particular system in order to bring the system up to date and/or to improve its overall efficiency. The contractor shall be responsible for developing an MWO Validation Plan and Report.

C.IPS.1.3.13 Reserved

C.IPS.1.3.14 Technical Manual (TM) Schedule and Status Report. The contractor shall provide this report monthly as an appendix to the Monthly Status Report (MSR) and Integrated Master Schedule IMS required by CDRL A033 and Contract Section C.4.2. The TM Schedule and Status Report provides information to the Government to permit program managers to determine if TMs are being prepared and delivered in accordance with approved contract schedule, and to take timely corrective action in the event discrepancies are identified (DI-TMSS-81812(T)).

C.IPS.1.3.15 Technical Data. The contractor shall be responsible for the development of technical data. This technical data package (TDP) shall contain elements, associated lists and data management products of the required level, type and format specified in Appendix 5 “TDP Option Selection Worksheet” and in accordance with MIL-STD-31000B and DI-SESS- 80776B.

C.IPS.1.3.16 Reserved

C.IPS.1.3.17 Schedule. Schedules to accomplish work requirement under this SOW are contractor-proposed according to each CDRL and are Government-approved. Exceptions to CDRL-driven schedule development are:

a. Contractor deliverable submissions to the Government are due by 1300 Eastern Time (ET) on or before the scheduled due date.

b. When a contractor deliverable or Government response of a data product falls on a weekend or holiday; in this case, delivery will be defaulted to the next business day. Example: The due date of May 1 is a Saturday, so the delivery date would become Monday, May 3 instead.

c. When a scheduling event is anticipated to require three or fewer days to complete, it should occur during a non-holiday, Monday–Friday workweek.

d. When a scheduling event is anticipated to require greater than three days to complete, it should begin on a non-holiday Monday.

e. C.IPS.1.3.18 Contract Deliverables.

C.IPS.1.3.18.1 Lifecycle Management Process (LCMP) Contract Data Requirements List (CDRL) Module and TARDEC ADVANCED COLLABORATIVE ENVIRONMENT (ACE) Windchill. See Section C.26 of the statement of work. The CDRL Module provides a secure mechanism for submitting, receiving, reviewing, and accepting contract deliverables. The system provides dashboards, metrics, automated workflow messages, process status indicators, and a complete tracking solution from delivery to acceptance of contract deliverables. The contractor shall utilize the module to submit and manage all CDRL exhibits in Section J.

SECTION 2. Meetings, In-Process Reviews (IPRs), and Events. The Government requires the following meetings, reviews, and events throughout the life of this contract to provide guidance and ensure program development and quality of the contractor-developed logistical support data products.

a. Logistics Guidance Conference.

b. Bi-weekly teleconference IPR.

c. Physical Configuration Audit (PCA).

d. Maintenance Task Analysis (MTA) IPRs.

e. Maintenance Allocation Chart (MAC) IPRs.

f. TM and Government Provisioning Conferences.

g. Contractor TM, MWO Validation.

h. Government TM Maintainability Evaluation (ME).

i. Government TM, MWO Verification.

f. Training Review Conference (TRC).

The following SOW paragraphs give guidance to the support required from the contractor at meetings, IPRs, and events. The contractor or a contractor-designated representative, as directed by this SOW, shall be a required attendee for all meetings, IPRs, and events.

C.IPS.2.1 Logistics Guidance Conference. To ensure mutual understanding of the end item and to discuss logistical support requirements that exist between the contractor and Government, a Logistics Guidance Conference shall be held to discuss the Logistics Data Product(s), as well as contractor and Government responsibilities, roles, and scope of work, and to assign appropriate Points of Contact (POCs). The Logistics Guidance Conference shall be a primary event to discuss and clarify requirements of the SOW, schedule, and tasks.

A Logistics Guidance Conference shall be held within thirty (30) days of contract award, on a date and time mutually agreed upon between the Government and contractor. The Government shall facilitate the review.

The Logistics Guidance Conference is a combined discussion of all Government requirements and data products, including Provisioning/Maintenance, Technical Publications, Training, and Packaging. The stated Government contract data product requirement(s) will determine the contractor personnel attendance. The contractor shall provide appropriate representation at this review to ensure a thorough understanding of the support requirements of all functional areas. The Government shall provide the necessary Government Furnished Information (GFI) to the Contractor at the Logistics Guidance Conference.

C.IPS.2.2 Bi-weekly Teleconference IPRs. Bi-weekly IPRs between the contractor and Government shall be held by teleconference. Postponement or cancellation of IPRs may occur with concurrence of the Government representatives. If the Government rejects a submission, the Government will require an additional IPR to resolve problems with the rejected deliverable. If deemed necessary, additional IPRs shall be held at the Government facility at no extra charge to the Government.

C.IPS.2.3 Physical Configuration Audit (PCA). The PCA is an examination of a production representative end item against the production drawings. The evaluation shall include all assemblies that report to the end item, all subassemblies, all Components of End Item (COEI), Basic Issue Items (BII), and all provisioned parts. The contractor shall perform the PCA at their facility with the Government as observers.

C.IPS.2.4 MTA and MAC IPRs. The contractor shall participate in MTA and/or MAC IPR(s). Contractor personnel responsible for development of the MTA/MAC shall be present, shall assist with content clarification, and shall be engaged during the MTA/MAC reviews. IPRs shall be held via telecommunication, but the initial MTA/MAC IPR event shall be in-person at a Government or contractor facility.

C.IPS.2.5 Government Provisioning Conference. The Government shall hold the Provisioning Conference at a place, time, and date dictated by the program schedule as indicated by the CDRL and mutually agreed upon by the contractor and Government. The contractor shall participate in the Government provisioning conference. Contractor personnel responsible for the development of the provisioning deliverables shall be present, shall assist with content clarification, and shall be engaged during the provisioning conference.

C.IPS.2.6 Contractor Validation. The contractor shall conduct a Validation of the TM and MWO submission and submit a Validation Plan and Report IAW this SOW and applicable CDRL The Validation shall be held at the contractor’s facility, unless otherwise specified by the contracting activity. The contractor shall notify the Government no fewer than thirty (30) days prior to conducting the Validation. The Government shall schedule observers as needed. The contractor shall provide for necessary administrative and technical support for the Government observation of the Validation effort.

C.IPS.2.7 Government Maintainability Evaluation (ME). The contractor shall participate in Maintainability Evaluation (ME) IPRs and shall provide contractor support at the ME event in the form of the technical writer assigned to the project and staffing necessary to implement real time edits with XML for Interactive Authoring and Display System (IADS5) during the event. Personnel are expected to assist in content clarification, be present and engaged for the performance of the tasks and produce rewrites within 24–48 hours to allow for re-performance of the tasks at the direction of the Government Technical Publications Manager. IPRs shall be held via telecommunication, and the ME event shall be in-person at a Government facility.

C.IPS.2.8 Government Verification. The contractor shall participate in Verification planning meetings and shall provide contractor support at the Verification conference in the form of the technical writer assigned to the project and staffing necessary to implement real time edits with XML for IADS5 during the event. Personnel are expected to assist in content clarification, be present and engaged for the performance of the tasks and produce rewrites within 24–48 hours to allow for re-performance of the tasks at the direction of the Government Technical Publications Manager. Verification planning meetings shall be held via telecommunication, and the Verification conference shall be in-person at a Government facility.

SECTION 3. Contractor Tasks.

C.IPS.3.1 General Summary. The contractor shall provide the services of developing the logistics support for the IECU following Army instructions and directives. Examples may include:

a. Contractor establishing OEM support.

b. Contractor establishing subcontractor support.

C.IPS.3.2 PCA. The purpose of the PCA is to provide assurance to the Government that the end item configuration documentation accurately reflects the validated product, and the documentation is a clear, complete, and accurate representation of the intended design that establishes the final product baseline.

C.IPS.3.2.1 PCA Plan. A PCA Plan shall be developed IAW this SOW and applicable CDRL. The PCA Plan shall identify all assemblies, subassemblies, COEI, and BII to be evaluated. The PCA Plan shall identify the method of evaluation. A hands-on audit, to include disassembly of major assemblies down to lowest components, to ensure that the current production drawings match the production end item is required. The PCA Plan shall include the following:

a. Date of the configuration audit.

b. Location of the configuration audit.

c. Complete listing of available technical documentation to be used during the audit.

d. Technical documentation should represent latest version of the production system.

e. List of subject matter experts attending the configuration audit.

f. List of all tools and equipment required.

g. Method of tracking validation and discrepancies.

C.IPS.3.2.2 Conduct of the PCA. The contractor and Government shall conduct a PCA to examine the “as-built” configuration of a validated end item, comparing results against its “as-designed” documentation plus any approved changes.

Each PCA non-compliance element identified during the audit is documented by the contractor and evaluated for appropriate action by the contractor and Government. At the conclusion of the PCA, the final product baseline is established, and all subsequent changes are processed by formal engineering change actions.

C.IPS.3.2.2.1 The Government and contractor will coordinate formal scheduling of the PCA as specified in the Government accepted PCA Plan.

C.IPS.3.2.2.2 A PCA Kickoff Meeting shall be conducted to establish a mutual understanding of PCA requirements between the Government and contractor. As a minimum, the meeting agenda should include the following:

a. Establish ground rules for disassembly and reassembly of any hardware back to operational configuration. (The contractor shall perform all disassembly and assembly steps as required by work package.)

b. Review results of previous configuration audits.

c. Review shortages/deviations/waivers.

d. Review status of any Engineering Change Proposals (ECPs).

e. Review status of test plans and procedures.

f. Establish procedures for configuration update releases.

g. Establish sub-teams and assign areas for PCA.

h. Establish Deficiency Report (DR) rules and method of documenting.

i. Establish schedule for daily meeting.

j. Establish rules for returning system to operational configuration at conclusion of PCA.

C.IPS.3.2.2.3 The following documentation shall be available at the PCA:

a. Manufacturer drawings to include top drawing to piece part components, wiring diagrams, pneumatic schematics, refrigeration schematics, and plumbing.

b. Manufacturer operating, maintenance, and illustrated parts breakdown manuals.

c. Software description flow charts.

d. Bill of Materials (BOM).

e. Parts Lists/Part Numbers to include consumables.

f. ECPs.

g. List of deviations requested/approved.

h. List of waivers requested/approved.

i. Vendor manuals to include all subcomponent technical documentation as well as any available vendor contact information.

j. List delineating both approved and outstanding changes against the configuration item, including action items being taken to resolve discrepancies.

k. Complete fault code list.

C.IPS.3.2.2.4 During the PCA, engineering documentation shall be reviewed for completeness. Areas of review shall include the following:

a. Drawings’ continuity - top drawing down to piece part drawing

b. Software description flow charts, i.e., how software integrates with hardware.

c. Bill of Materials (BOM) accuracy.

d. Parts Lists/Part Numbers to include consumables.

e. ECP incorporation.

f. Deviations requested/approved.

g. Compliance with ASME Y14.100 and other relevant Y14 series standards.

C.IPS.3.2.2.5 The following tasks shall be accomplished at the PCA:

a. Drawing review to level necessary to confirm COEI for field and sustainment level maintenance.

b. Disassembly to level as required to confirm configuration of end item for field and sustainment level maintenance.

c. Review of knowledge gaps and unincorporated design changes.

d. Determine action items required to resolve uncovered issues as well as create a plan for contractor to provide resolutions.

C.IPS.3.2.2.6 Following the review of configuration and documentation, a final meeting of the PCA team shall be held. Items to be covered during a PCA Closeout Meeting are as follows:

a. Review all DRs written by PCA Team.

b. Establish schedule for DR resolution.

c. Establish ground rules for DR signoffs.

d. Review PCA certification sheets (as applicable).

e. Receive Government guidance on submitting minutes and post-audit report.

f. Receive Government guidance on submitting final audit report.

C.IPS.3.2.3 PCA Report and Certification. The PCA Report documents the results of an examination of a production representative end item against the production drawings. The Report shall also provide the results of a configuration audit of the current production drawings against the RPSTL and PPL that support the end item. The Report shall validate assemblies and provisioned parts and match the production drawings or identify the discrepancies. The PCA Report and Certification shall include all the following information:

a. A complete listing of all evaluated assemblies, subassemblies, COEI, and BII, including Cage Codes and Part Numbers for each part, assembly, COEI, and BII.

b. Results of the evaluation of the production drawings against the production end item, including all assemblies that report to the end item, subassemblies, COEI, BII, and provisioned parts. Any discrepancies and corrective action in the “as-built” configuration and the “as-designed” configuration must be included.

c. Results of the evaluation of the production drawings against the RPSTL and PPL, including all assemblies that report to the end item, COEI, BII, and provisioned parts.

d. Certification that the PCA was completed and that any discrepancies were properly adjudicated.

C.IPS.3.2.4 Formal Engineering Change Action. After successful completion of the PCA and the establishment of a Product Base Line (PBL), all subsequent changes resulting from Government testing, contractor validation, obsolescence, Maintainability Evaluation (ME), Technical Manual (TM) Verification, are processed by formal engineering change action coordinated between the contractor and Government.

C.IPS.3.3 Supportability Analysis. Supportability analysis includes the integration of various analytical techniques with the objective of designing and developing an effective and efficient logistics support infrastructure. Some techniques used in supportability analysis are Fault Tree Analysis (FTA), Maintenance Task Analysis (MTA), and Level of Repair Analysis (LORA). See Appendix 1, Provisioning of this SOW for additional provisioning guidance and requirements.

C.IPS.3.3.1 Fault Tree Analysis (FTA). The FTA is a “top-down,” systematic method for defining a single undesirable event and determining all possible reasons that would cause the event to occur.

C.IPS.3.3.2 The output results from the FTA provide recommendations for the creation of corrective actions, Preventive Maintenance, and other maintenance actions, which, in turn, provide the basis to perform the MTA. The results of those analyses provide information to conduct the LORA.

C.IPS.3.3.3 Maintenance Task Analysis (MTA). The MTA shall be documented in contractor format IAW Two-Level Maintenance (TLM) (i.e., to include field and sustainment level tasks) and shall identify the Maintenance Functions, level of maintenance, manpower requirements, spare and repair parts, and support equipment required for each replaceable and repairable item. Functional Group Codes (FGCs) will not be used. The following shall be included:

a. All Maintenance Functions/Tasks to be performed: Provide a list of each Maintenance Function and its associated Maintenance Task(s).

b. Manpower requirements for each Maintenance Task to include the following:

1. Skill level of technician.

2. Identification of either Crew/Maintainer/Below Depot/Depot.

3. Number of technicians: Identify number of technicians required to perform each Maintenance task.

4. Number of labor hours to perform each task: Identify the estimated time required to perform each task.

5. Identification of the Military Occupational Specialty (MOS) required for each Maintenance task

i. Required tools or special tools/equipment to perform the task.

ii. Identification of common tool sets and/or individual special tools to perform each task.

iii. Required packings, lubricants, solvents, kits, safety equipment, consumables, or piece parts.

Identify any Petroleum Oils and Lubricants that may be required to perform each Maintenance Task.

6. Any environmental factors or safety concerns to equipment and personnel that should be addressed when performing the task (e.g., NOTES, CAUTIONS, WARNINGS). Identify any additional considerations, such as safety-related warnings or cautions or other concerns in performing the task.

C.IPS.3.3.4 Level of Repair Analysis (LORA). The LORA shall be developed using the Army-approved modeling tool Computerized Optimization Model for Predicting and Analyzing Support Structures (COMPASS), or COMPASS Lite. This concept shall be based on economic and non-economic constraints and readiness requirements, emphasizing repair strategy throughout the life cycle and using engineering estimates that will be refined over time with field experience.

C.IPS.3.4 Maintenance Allocation Chart (MAC).

C.IPS.3.4.1 Preparation of the MAC. The contractor shall prepare a Maintenance Allocation Chart (MAC) IAW MIL-STD 40051-2D. The MAC shall be derived from an LSA-004 report. The MAC must be in either Functional Group Code (FGC) sequence as described in TB 750-93-1 for tactical ground vehicles or top-down, pyramidal breakdown sequence of the end items’ maintenance-significant assembles, subassemblies, and modules. The MAC must contain all repair, replace, and related maintenance functional tasks that are contained within maintenance work packages (WPs). The MAC must contain entries for all levels of maintenance from Operator through Depot for both hardware and software maintenance tasks. For each repairable assembly or subassembly, the MAC must identify the maintenance function to be performed, the level of responsibility for the function, the active repair time, and the tools and test equipment necessary to perform the function. The MAC must contain all items unless deletion has been authorized by the acquiring activity. The contractor shall utilize the MTA and LORA to determine the operational, maintenance, and support functions of the system for the appropriate levels of maintenance: field or sustainment. The contractor shall ensure that all logistics documents created under this effort agree with each other and that there is consistency among all products, particularly as required by MIL-STD. The contractor shall develop and prepare the MAC in top-down generation breakdown sequence in the logical order of disassembly, starting with the end item, and containing all functional groups that require maintenance. The process of breakdown is established from the engineering drawing structure in a Next Higher Assembly (NHA) progression, until the lowest repairable assembly/subassembly in each family tree group is identified. All repairable components must have a functional group or subgroup assigned that aligns with the applicable maintenance work package. The top-down generation breakdown sequence developed in the MAC shall be used to create the TM maintenance WP’s, PPL, and RPSTL. All these files shall remain in alignment throughout the life of the contract. The RPSTL supports the maintenance WPs derived from the MAC and identifies all repair parts required for the maintenance process. Contractor shall prepare the MAC two-level maintenance format IAW MIL-STD 40051-2D and AR 750-1, aligned with TM requirements.

The basic entries in the MAC shall be a list of functional groups applicable to the end item that require maintenance. The term “functional group” applies to repairable assemblies and subassemblies. The end item group shall be numbered "00," with each subsequent group number ascending from there. Parts that are not subject to maintenance shall not be listed in the MAC.

All item names of MAC functional groups shall be official nomenclature IAW the Defense Logistics Agency (DLA) H6 Item Name Directory located at https://public.logisticsinformationservice.dla.mil/H6/search.aspx . Reverse word order shall be used in the MAC.

C.IPS.3.4.1.1 Proposed MAC. A "Proposed" MAC shall be submitted concurrently with the first submission only of the LORA. The purpose for the Proposed MAC is to ensure the Maintenance Concept being produced by the LORA is expressed accurately in the MAC, follows the logical order of disassembly, and is compliant with MIL-STD 40051-2D. Based on the MAC, the contractor shall also provide a recommended listing of all maintenance work packages (Crew/Maintainer) to support all Maintenance Functions listed on the MAC. An IPR with the Government and contractor shall be conducted virtually within fifteen (15) calendar days after Government receipt of the initial LORA submission and Proposed MAC. See para

3.4.11 for complete description and details.

C.IPS.3.4.1.2 Initial MAC. The initial MAC with Engineering Drawing Tree shall be submitted thirty (30) calendar days after the contractor receives acceptance of the LORA. An IPR with all Government and contractor stakeholders shall be conducted no more than fifteen (15) calendar days after Government receipt of the initial MAC with Engineering Drawing Tree submissions.

C.IPS.3.4.2 Provisioning Process and Interface. This section describes how the RPSTL for the TM evolves during the provisioning process and how it interfaces with the other provisioning-oriented documents (e.g., the MAC and PPL).

3.4.2.1 Preparation of the RPSTL. The RPSTL must be developed as an extension of the PPL, and both must align with a properly prepared MAC. RPSTL figure titles shall align with the MAC functional groups and be in correct reading order.

C.IPS.3.4.2.2 PPL and MAC Preparation Interface. When the PPL and MAC are prepared in top-down generation breakdown format, Functional Group Codes (FGCs) must be assigned to all items on the PPL during the provisioning process and must agree with the MAC group numbers before RPSTL preparation can begin. These groups then become the basis for the RPSTL Table of Contents and figure/listing captions. The names used in the RPSTL must equate to the group number of the item called out in the MAC; all repairable items must have a group or subgroup number assigned. The structure of the FGCs is tied to the indenture structure of the PPL. For example, the A indenture item (system/end item) would have an FGC equivalent to 00; B would be 01; C would be 0101. For ease of preparation and revision of the MAC, and since the FGCs will appear on the PPL, the MAC should be structured according to the indenture codes for all assemblies to ensure traceability of Next Higher Assembly (NHA) relationships. If some groups are subsequently determined to be non-repairable, they may also be deleted later. A repairable item that appears as a one-line entry in the PPL shall have an entry in the MAC. At a minimum, all repairable items must be listed in the MAC.

Compatibility between the MAC and PPL is a prerequisite for preparing the RPSTL; any disagreement between the two documents must be resolved. To ensure compatibility, the MAC must not be considered final until it is cross-referenced against the PPL and the FGCs have been verified.

See Appendix 8, Provisioning Requirements Statement.

https://public.logisticsinformationservice.dla.mil/H6/search.aspx

C.IPS.3.4.3 Functional Group Code (FGC). An FGC is a basic (usually two-position) group code assigned to identify major components, assemblies, and subassemblies to a functional system. Subordinate sub-functional groups/subassemblies are coded to relate back to the basic (top position) FGC in a sequential, NHA relationship (i.e., top-down breakdown structure).

a. Top-down is accomplished by sequencing all parts comprising the end item in a lateral and descending “family tree/generation breakdown.” This breakdown shall consist of the end item, including all components, listing every assembly, subassembly, and part that can be disassembled, reassembled, and/or replaced. All parts shall be listed in their relation to the end item, component, assembly, or installation system in which they are contained and to their own further subassemblies and parts. The only exception is welded components, which will not be broken down into piece parts.

b. Breakdown is accomplished by starting with the end item as the “Top Level Assembly” (A) and descending, by subsequent indenture level (B, C, D, etc.), resulting in a complete depiction of the end item. Major assemblies, subassemblies, or components would normally be at the “B” indenture level, etc., utilizing as many levels as necessary until the last item(s) is/are depicted. When more than one group is to be depicted at the same indenture level, standard practice and best maintenance procedures will dictate which group will appear first (e.g., A cylinder head assembly would normally necessitate removal prior to removing the cylinder block assembly; therefore, the cylinder head assembly would appear prior to the cylinder block in the breakdown sequence.)

C.IPS.3.4.4 Indenture. This top-down breakdown relationship is shown by means of an indenture code in the RPSTL and PPL. The indenture code indicates that the item is either associated with, contained in, or part of the preceding item identified with an indenture code of the preceding alpha character.stable

C.IPS.3.4.5 Maintenance Code. The maintenance code entered in the third position of the Source, Maintenance and Recoverability (SMR) code in the RPSTL shall be used to identify the lowest category of maintenance that is authorized to remove, replace, and use the spare or repair parts. SMR codes are defined in AR 700-82. All items on the MAC shall specify the maintenance level(s) to which a function is authorized: field or sustainment.

C.IPS.3.4.6 Preparation of Maintenance Instructions. Maintenance instructions shall be prepared and subdivided into individual work packages that support the functional groups of the MAC. The maintenance instructions provide information to enable the technician to receive, process, inspect, clean, service, test, repair, and replace the weapon system/equipment and associated Weapons Replacement Assemblies/Shop Replacement Assemblies (WRAs/SRAs) to an acceptable performance standard. Maintenance Tasks shall be developed IAW the Logistics Product Data (LPD), MAC, which serves as the Maintenance Plan, and SMR code developed for the weapon system/equipment and components. Maintenance work packages shall be arranged to coincide with the FGC sequence followed in the MAC, which applies to both Field and Sustainment levels.

C.IPS.3.4.7 Engineering Drawing Tree. The contractor shall provide a top-down generation breakdown Engineering Drawing Tree of the end item with sufficient detail so that the Government can verify the functional groups and NHA for each item listed on the MAC. The indenturing structure represented on the Drawing Tree shall provide sufficient detail so that the Government can verify the NHA for each item listed on the PPL and associated EDFP. The Drawing Tree shall clearly show to which function group the assembly, subassembly, and/or part belongs and the NHA. The Engineering Drawing Tree shall be an accurate representation of the Technical Drawing Package (TDP) and shall include all assemblies, subassemblies, and repairable components. The following elements shall be provided as a minimum on the Drawing Tree:

a. CAGE/Part Number.

b. Item Name.

c. Next Higher Assembly (NHA).

d. Indenture Level/Code.

e. Functional Group Code (FGC).

f. PLISN (if known).

The contractor may include, at their discretion, any other pertinent information they feel is relevant to the Drawing Tree.

C.IPS.3.4.8 Government Review, Approval, and Acceptance of the MAC. The contractor shall submit the initial MAC with Engineering Drawing Tree and MAC, RPSTL and WP Crosswalk to the Government IAW CDRL requirements with the three accurately correlating to each other in all material and documented respects. After Government review and acceptance of the MAC breakdown, the approved Government MAC shall form the base line for the associated TM(s) and provisioning effort. Any revision made to the MAC after Government acceptance shall be presented, reviewed and approved by the Government. If substantial edits are required to the MAC, the Government may request an IPR at any time. MAC acceptance or rejection shall be in the form of a memo through the Contract Officer Representative (COR). After the Initial MAC is accepted, revisions made to the MAC shall be documented by an email sent to the Government and require a Government response, acknowledging and approving the changes before they can be implemented. All changes shall be captured in the WP Crosswalk spreadsheet.

C.IPS.3.4.9 MAC, RPSTL and WP Crosswalk. The MAC is the framework for development of both the Repair Parts and Special Tools List (RPSTL) and the Maintenance instructions, and all three must be coordinated and consistent in nomenclature and sequence. All maintenance functions listed in the MAC for a component must have an associated Maintenance work package(s) at the appropriate level of maintenance containing tasks supporting the maintenance function. A listing of spare parts supporting the required maintenance functions must also be listed in the RPSTL work package. The sequence of the Maintenance work packages and the RPSTL work packages must strictly follow the FGC or top-down breakdown sequence in the MAC. A revised MAC, RPSTL, and WP Crosswalk shall be provided with each TM deliverable.

A Government furnished MAC, RPSTL, and WP Crosswalk template will be provided.

C.IPS.3.4.10 Media. The contractor shall prepare and deliver the MAC; Drawing Tree and MAC, RPSTL and WP Crosswalk in Microsoft Office products or equivalent electronic format.

C.IPS.3.4.11 Overview of Army Maintenance Strategy. [ Reference: Army Regulation 750-1.] The two-level MAC designates overall authority and responsibility for the performance of Maintenance Functions on the identified end item or component within the Army maintenance system. The MAC shall include all maintenance significant components, assemblies, subassemblies, and modules for field and sustainment level maintenance. No item shall be deleted from or added to the MAC without Government approval. If a Maintenance Function is a replacement function only for a repair part, the item shall not be listed in the MAC, unless not listing the item would result in deletion of the group number, in which case the item shall be listed to retain the functional group number. Assemblies or subassemblies requiring a test procedure before replacement shall also be listed on the MAC.

C.IPS.3.5 Engineering Data for Provisioning (EDFP). The contractor shall develop and prepare EDFP for all items recommended by the contractor to be SMR “P” coded but that currently are not assigned an NSN, including COEI, BII, special tools, and expendable/durable items. The contractor shall also develop and prepare EDFP for all items recommended to be SMR “X” coded. EDFP consists of Provisioning Technical Documentation (PTD) and/or Supplemental Provisioning Technical Documentation (SPTD) to ensure sustainment and maintenance support throughout the product’s life cycle.

EDFP is data acquired by the contractor to support the assignment of SMR codes to each item on the PPL/RPSTL. EDFP is also used for assignment of item management codes, prevention of the proliferation of identical items in the Government inventory, maintenance decisions, and item identification necessary in the assignment of an NSN. EDFP, PTD, and SPTD, as defined, may be used interchangeably within this SOW.

PTD is the generic term for the various provisioning lists and provisioning data as defined in this SOW for EDFP. SPTD is considered part of PTD. PTD is used by the Government for identification, selection, and determination of initial requirements and cataloging of support items to be procured through the provisioning process. PTD shall provide technical identification of items for maintenance of end items to include location within the NHA (e.g., internal location of an electrical component within an engine starter assembly). If the drawing, commercial literature, specification, or standard does not identify the location of the part within the end item, then a sketch or illustration must be attached to that specific document. TM illustrations will be sufficient to meet this requirement when provided with EDFP.

SPTD is technical data used to describe repair parts and/or equipment and consists of data such as specifications, standards, drawings, photographs, sketches, descriptions, quantities, and the necessary assembly and general arrangement drawings, schematic diagrams, wiring and cable diagrams, etc., needed to indicate the physical characteristics, location, and function of the item. SPTD shall be provided for all SMR “P” coded items listed in the RPSTL, COEI, BII, special tools, and expendable/durable tables without an NSN. SPTD shall clearly indicate the physical characteristic(s) and/or specification(s) of the item or assembly (e.g., color, type of paint, dimensions, radius, thickness, dimensions, inlet/outlet dimensions, pressure range, length, width, height, shape, surface treatment, thread size, thread type, type of material, wall thickness, amperage, voltage).

SPTD shall be provided in the following order of precedence:

a. Government or recognized industry specification or standard

b. Original Equipment Manufacturer (OEM)

c. Commercial Item Description (CID)- performance specification or other similar technical requirement or purchase description that does not contain data with restricted rights.

At a minimum, SPTD shall clearly and completely identify and describe the item, who manufactures the item (CAGEC) or from whom the item was purchased, and cost of the item.

Items procured from OEM sources that are altered or modified shall have a unique and separate drawing that indicates what modification was performed on the provisioned item and the contractor’s CAGEC and contractor unique part number. EDFP shall include the necessary information to identify the item prior to its alteration including the original part number and the name and CAGEC of the source of the original part.

Supplier/Distributor part numbers and EDFP will not be accepted (unless otherwise directed). All technical data must be from the OEM. Military Specification (MIL-SPEC), Military Standard (MIL-STD), and Federal Specification (FED-SPEC) for items that are non-definitive must include documentation of class, type, size, shape, color, and/or dimensions for that standard.

C.IPS.3.5.1 Government Rejection of Data Product. The Government will reject any submitted EDFP, if the technical documentation of the individual EDFP is not sufficient in clearly outlining technical specifications and dimensions of the provisioned item. EDFP submitted without a CAGEC for any item will be rejected. EDFP submitted using a supplier/distributor CAGEC will be rejected. EDFP shall be reviewed concurrently with MAC, PPL and RPSTL to ensure symmetry is consistent within all products prior to Government acceptance. EDFP and PPL are mutually supported deliverables. If one is deemed unacceptable, the other shall not be accepted until the proper corrections are made.

C.IPS.3.5.2 Marking of EDFP. EDFP shall be clearly marked with the Provisioning Contract Control Number (PCCN), Provisioning Control Code (PCC), Provisioning Line Item Sequence Numbers (PLISNs), CAGEC, Manufacturer’s Part Number, and NHA PLISN. Technical data and EDFP shall match the data/drawing to the PLISN on the PPL for all applicable items. If EDFP for any item has more than one page, all pages shall be marked IAW information contained in this paragraph.

EDFP for each individual item shall be submitted as separate PDF files. EDFP that has more than one page for any individual part may be sent as one file. Names for each file shall be as follows: PLISN, (PCC(UOC)), (CAGE Code), (Part Number) (Item Description). [For example: A010 (ABC)(81337)(B12G56RE) (Hose Assembly)]

C.IPS.3.5.3 Media. The contractor shall prepare and deliver PTD and/or SPTD technical documentation electronically using PDF format IAW CDRL A016. All submitted data products shall be written in English, and PTD and/or SPTD shall be organized in alphanumeric order by the PLISN sequence and consistent with the MAC and RPSTL.

C.IPS.3.5.4 Data Rights. EDFP submitted when the contractor or OEM has proprietary data rights shall be marked in such a manner as to identify the rights, limited or unlimited. These markings shall be IAW Defense Federal Acquisition Regulation Supplement 252.227-7015, Rights in Technical Data.

C.IPS.3.6 Provisioning Parts List (PPL): The contractor shall develop and prepare a PPL with all data elements selected by the Government from GEIA-STD-0007-C. The PPL shall be provided in TA-HB-0007-1 format. The contractor shall provide the most current PPL at all Government Provisioning Reviews or as requested by the Government, in addition to the scheduled submissions.

The PPL shall be in a top-down generation breakdown structure consistent with the MAC. The MAC, RPSTL, and PPL organization shall be consistent and of the same sequence. The MAC is the base document that is used to sequence and generate the PPL. The RPSTL then becomes an output product of the PPL.

The PPL shall be a complete list of all replaceable and/or repairable assemblies, subassemblies, and repair parts. The parts list structured at the end item, component, or assembly level shall contain the end item, component, or assembly equipment and all support items that can be disassembled, reassembled, or replaced and, when combined, constitute the end item, component, or assembly equipment. The PPL shall also include all COEI, BII, AAL, special tools, and expendable/durable items as defined within the respected tables. COEI, BII, AAL, special tools, and expendable/durable items shall be properly identified within the PPL IAW Provisioning Appendix.

The contractor shall identify on the PPL all interchangeable part numbers, drawing numbers, and specification numbers for each item listed in the PPL. All SMR coded “P” items that will be provisioned as a result of the Provisioning Conference shall be supported with applicable EDFP to receive an NSN. The contractor shall provide OEM data for all items on the PPL, as applicable. Any non-OEM data contained within the PPL, for which the contractor has exhausted all methods of research and still cannot find proper OEM data, shall be identified to the Government during the initial PPL submission.

The contractor shall manage the field and sustainment level PPL as one continuous file. Once the final field level PPL is accepted, the contractor shall use that file, with applicable sustainment level parts added/identified, as the baseline for the NMWR PPL submissions if required. If the contractor choses to identify sustainment level parts during creation of the field level PPL, they must be properly identified IAW section 3.6.1.

C.IPS.3.6.1 Submission Requirements.

C.IPS.3.6.1.1 The Contractor shall perform Defense Logistics Information Service (DLIS) Screening of items on the PPL per DoD 4100.39-M, Volume 5, GEIA-STD 0007, DI-SESS-81759A, CDRL, Logistics Product Data (LPD) Summaries - Provisioning and Other Pre-procurement Screening Data. The results of the Screening shall be entered on the PPL per DI- SESS-81759A CDRL. The contractor shall provide each 9K/18K/36K IECUs screening results to the Government 30 days prior to each Provisioning in Process Review (IPR) 20%,60% and 100% and have the results of screening data available at each Provisioning IPR. The following data elements obtained as a result of valid National Stock Number (NSN) matches through DLSC screening shall be inserted into the Provisioning Parts List (PPL) LSA- 036 for review by Government personnel at each IPR per the GEIA-STD -0007 screening data source Table 8 for the LSA -032.txt report. Final screening results shall be submitted as part of the PPL delivery. Final screening shall include all approved drawing. Drawings shall be OEM CAGE, EDP must be primary EDF. MC Master Card item NSN not accepted.

C.IPS.3.6.1.2 A "Proposed" Provisioning Parts List (PPL) shall be submitted by the contractor concurrent…