A02 SOW Attachment 4 Integrated Product Support (IPS).pdf

ATTACHMENT 5

STATEMENT OF WORK (SOW)

FOR DEVELOPMENT AND PRODUCTION OF INTEGRATED PRODUCT SUPPORT (IPS)

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

FOR THE IMPROVED ENVIRONMENTAL CONTROL UNIT (IECU)

TECHNICAL MANUALS (TM) 9K TM 10-4120-XXX-12&P, 18K TM 10-4120-XXX-12&PAND 36K TM 10-

4120-XXX-12&P

SECTION 1. Description/Specifications.

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.

1.2 Background. PM-FSS is the Army’s premier developer of force sustainment systems providing expeditionary, modular, and scalable life support capabilities that can quickly deploy and redeploy across the globe. Functional areas within the PM-FSS capabilities are Field Feeding, Field Services, Aerial Delivery, Shelters, and Force Provider. Each PM-FSS functional area maintains a portfolio of legacy or new equipment end item/systems /subsystems requiring full spectrum Logistics Product Data (LPD) consisting of supportability analyses, Technical Manuals (TMs), Technical Bulletins (TB), repair parts provisioning, packaging, special packaging, and training.

This Statement of Work (SOW) adopts new guidance contained in the Product Support Manager’s (PSM) Guidebook that is still emerging.

1.3 General Scope.

1.3.1 PM-FSS Project. 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 scope of this SOW covers the development of life-cycle logistics support for PM-FSS legacy and new equipment end item/ system/subsystem projects. The Contractor shall develop and produce the following as specified by this SOW, associated Contract Data Requirements List (CDRL) and attachments.

1.3.2 Requirements. Contractors shall refer to this SOW and to the Department of Defense’s DD Form 1423 – Contract Data Requirements List (CDRL) of each data item to determine the Government’s work requirements.

1.3.3 Technical Manual Quality Assurance (QA). The Contractor shall develop the TM Quality Assurance Plan.

1.3.4 Maintenance Strategy. The Contractor shall develop the supportability analysis required to support logistics development. This analysis includes Level of Repair Analysis (LORA), Failure Modes Effects and Criticality Analysis (FMECA), and Maintenance Task Analysis (MTA).

1.3.5 Technical Manuals (TM), and Repair Parts and Special Tools List (RPSTL). The Contractor shall develop new, changed or revised Operator and Field Maintenance Manual with Repair Parts and Special Tools List (RPSTL). The contractor shall be responsible for developing a TM Validation Plan and Report.

1.3.6 Provisioning. The Contractor shall provide a Maintenance Allocation Chart (MAC) with Engineering Drawing Tree, Provisioning Parts List (PPL), and Engineering Data for Provisioning (EDFP) to support the provisioning process.

1.3.7 Proposed Spare Parts List (PSPL). The Contractor shall develop a PSPL per CDRL XXXX as onboard spares for 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. This deliverable shall be delivered in contractor format, with all required content, as described in the requirements section of DI-PSSS-80134B.

1.3.8 Packaging. The Contractor shall develop Special Packaging Instructions (SPI) and Logistics Product Data (LPD) packaging data to support the end item.

1.3.9 Training Aids/Materials. The contractor shall develop training aids/materiels to include Mission Collective/Individual Task Data, Conduct of Training, Programs of Instruction as well as Lesson Plans, Student Guides and Visual Aids for both Operator and Maintainer.

1.3.10 Instructional Media Package. The Contractor shall develop the Instructional Media Package, including two Interactive Multi-media Instruction (IMI) courses along with associated documentation.

1.4 Contract Deliverables. All contract submission files shall be sent electronically without restrictions that would prevent the Government from reproducing or editing the information. Electronic submittal to the Government must use the Department of Defense (DoD) Secure Access File Exchange (SAFE) service, accessed via https://safe.apps.mil.

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. Maintenance Task Analysis (MTA) IPRs.

d. Maintenance Allocation Chart (MAC) IPRs.

e. TM and NMWR Government Provisioning Conferences.

f. Contractor TM Validation.

g. Maintainability Evaluation (ME) and Limited User Test (LUT).

h. Government TM Verification.

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.

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 will provide the necessary Government Furnished Information (GFI) to the Contractor at the Logistics Guidance Conference.

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 may require an additional IPR at the Contractor or Government facility to resolve problems with the rejected deliverable.

2.3 MAC IPRs. The Contractor shall participate in MAC IPR(s). Contractor personnel responsible for development of the MAC shall be present, shall assist with content clarification, and shall be engaged during the MAC reviews.

IPRs will be held via telecommunication, but the initial MAC IPR event will be in-person at a Government facility.

2.4 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.

2.5 Contractor Validation. The Contractor shall conduct a Validation of the TM submission and submit a Validation Plan and Report IAW this SOW and CDRL XXXX. This 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 will schedule observers as needed. The Contractor shall provide necessary administrative and technical support for the Government observation of the Validation effort.

2.6 Government Maintenance Evaluation (ME). The Contractor shall participate in Maintenance Evaluation (ME) IPRs and shall provide contractor support at the ME event in the form of the technical writer and technical support assigned to the project. Personnel are expected to assist in content clarification, be present and engaged for the performance of the tasks and produce on-the-spot 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 will be in-person at a Government facility.

2.7 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 and technical support assigned to the project. Personnel are expected to assist in content clarification, be present and engaged for the performance of the tasks, and produce on-the-spot 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 will be in-person at a Government facility.

SECTION 3. Contractor Tasks.

3.1 General Summary. The Contractor shall provide the services of developing the logistics support for the PM- FSS Project end item/system/subsystem, following Army instructions and directives.

3.2 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 Failure Modes Effects and Criticality Analysis (FMECA), Fault Tree Analysis (FTA), Maintenance Task Analysis (MTA), and Level of Repair Analysis (LORA). See Attachment 1 of this SOW for additional provisioning guidance and requirements.

3.2.1 Failure Modes Effects and Criticality Analysis (FMECA). The FMECA is a reliability evaluation and design review technique that examines the potential failure modes within a system to determine the effects of failures on equipment or system performance. The FMECA consists of essentially two analyses: Failure Modes Effects Analysis, which analyzes possible failures and their root causes, and Criticality Analysis, which analyzes the criticality of each effect on mission completion, environmental impacts, health hazards, and system safety. This information is ranked by severity and probability. The FMECA is performed using a “bottom-up” approach, which begins with looking at the effects of failure at the lowest level of the system hierarchy and then tracing upward to determine the end effect of each failure on system performance.

3.2.1.1 The output results from the FMECA 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.

3.2.2 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 will 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.

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

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

e. Required lubricants, solvents, kits, safety equipment, or piece parts: Identify any Petroleum Oils and Lubricants (POL) that may be required to perform each maintenance task.

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

3.2.3 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.

3.3 Maintenance Allocation Chart (MAC).

3.3.1 Preparation of the MAC. 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-40051-2D (Change 1). 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 RPSTL 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. Reverse word order shall be used in the MAC.

3.3.1.1 Initial MAC. 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.

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

3.3.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.

3.3.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 are 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 shall be structured according to the indenture codes for all assemblies in order 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 will 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.

3.3.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.).

3.3.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.

3.3.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. If the Maintenance Function is a replacement function only for a repair part, the repair part shall not be listed in the MAC, unless not listing the repair part would result in omission of the NHA group number; in this case, the part shall be listed in order to list the NHA functional group number.

3.3.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.

3.3.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.

3.3.8 Government Review, Approval, and Acceptance of the MAC. The Contractor shall submit the initial MAC with Engineering Drawing Tree to the Government IAW CDRL requirements. After Government review and acceptance of the MAC breakdown, the approved Government MAC shall form the base line for the associated TM(s), NMWR, and provisioning effort. Any revision made to the MAC after Government acceptance shall be presented and reviewed at an IPR and approved by the Government. MAC acceptance or rejection shall be in the form of a memo through the Contract Officer Representative (COR).

3.3.9 Media. The Contractor shall prepare and deliver the MAC and Drawing Tree in Microsoft Office products or equivalent electronic format.

3.3.10 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 in order to retain the functional group number.

Assemblies or subassemblies requiring a test procedure before replacement shall also be listed on the MAC.

3.3.11 Proposed MAC Submission IPR. An IPR shall be scheduled within fifteen (15) calendar days after Contractor submittal of the LORA, which is prior to the Contractor’s submitting the initial MAC. The MAC IPR will be held at a Government or Contractor facility, on a date and time dictated by program schedule, and mutually agreed on by the Contractor and Government. The length of the review will be determined by the Contractor and the complexity of the system. The purpose of the IPR is for the Contractor to tour the equipment with the Government representative, to explain its function, and to get a better understanding of the end item and its components. The Government representative can then provide a preliminary review of the MAC, including Functional Group breakdown, Maintenance Functions, and maintenance levels (i.e., field and sustainment), and can provide input to the Contractor of the end item. The Contractor should be prepared to discuss both field and sustainment level tasks, as applicable, as outputted from the supportability analyses. The IPR also provides the opportunity to review the Maintenance Plan philosophy from the Contractor as output from the LORA (Maintenance Concept) and to address upfront any potential issues with the MAC prior to the submittal of the initial MAC.

3.3.11.1 Contractor Personnel. The Contractor shall provide appropriate personnel to support the IPR, present the required content to the Government, and respond to Government comments and questions.

3.3.11.2 Contractor Briefing. The Contractor shall present a detailed briefing of the theory and principles of operation of the end item and/or sub-components, the MAC functional group breakdown, maintenance actions and processes, maintenance times, equipment troubleshooting strategy, and logic. The Contractor shall provide a top-down breakdown Engineering Drawing Tree of the end item to Government personnel. The Contractor may use block diagrams, drawings, functional flow charts, and/or schematics to support the functional breakdown of the system and subcomponents. The Contractor shall determine the agenda and may use appropriate office media (e.g., charts, slides, handouts) to present the supporting information.

3.3.11.3 Contractor Furnished Documentation. Contractor-provided aids in the Government evaluation of the MAC are listed below. Presentation of this documentation at the MAC IPR ensures Government understanding and reasoning of the composition of the MAC. Documents not provided must be addressed by the Contractor at the IPR.

These documents aid the Government evaluation of the submitted MAC.

a. Proposed MAC.

b. Schematic diagram of equipment functional groups and relationships.

c. Top-down generation breakdown Drawing Tree of the end item.

d. Troubleshooting logic diagram of the end item.

3.4 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, tools/special tools, and expendable/durable items. The Contractor shall also develop and prepare EDFP for all items recommended to be SMR “XD” 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 and NMWR RPSTL 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, tools/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. Original Equipment Manufacturer (OEM).

b. Government or recognized industry specification or standard.

c. Commercial Item Description (CID).

At a minimum, SPTD shall clearly and completely identify and describe the item, who manufactures the item (CAGE Code) or from whom the item was purchased and the 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.

3.4.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.

Should any Logistics event, i.e. Maintainability Evaluation, TM Verification require changes/additions/deletions to the PPL, the contractor shall be required to incorporate those changes and resubmit the PPL within 30 calendar days after receipt of the specific event Mark-up. The Government may also request additional submissions throughout the life of the contract.

3.4.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 (PLISN), 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 (Part Number) (Item Description). [For example: A010 (B12G56RE) (Hose Assembly)]

3.4.3 Media. The Contractor shall prepare and deliver PTD and/or SPTD technical documentation electronically using PDF format IAW CDRL XXXX. 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.

3.4.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.

3.5 Provisioning Parts List (PPL): The Contractor shall develop and prepare a PPL with all data elements selected by the Government from GEIA-STD-0007C. The PPL shall be provided in GEIA-STD-007C format. The Contractor shall provide the PPL at the Government Provisioning Reviews in addition to the scheduled previous 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 or repairable assemblies, subassemblies, and repair parts. The 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, tools/special tools, and expendable/durable items as defined within the respected tables.

3.5.1 Submission Requirements. The Contractor shall submit a “Proposed” Provisioning Parts List (PPL). The Contractor shall submit this sample PPL, consisting of 15–20 PLISNs, containing all data elements as selected in the SOW specific to the PM-FSS Project (end item/system/subsystem). The purpose of the Proposed PPL is for the Government to provide a courtesy review and feedback to the Contractor in order to identify any potential concerns consistent with correct and accurate coding and to verify the Contractor's understanding of parent/child relationships. This process will aid the Contractor and Government in addressing any potential issues or concerns with the PPL prior to the initial submission. A PPL IPR shall be conducted no more than five (5) calendar days after submittal of the Proposed PPL. The IPR shall be held via telecommunication as agreed upon by the Contractor and Government.

Approximately forty-five (45) calendar days after acceptance of the initial submission of the PPL (CDRL XXXX) and EDFP (CDRL XXXX), the Government shall conduct a Provisioning Conference. The Provisioning Conference shall be held either in Natick, MA or at a place mutually agreed upon by the Government and Contractor.

3.5.2 Media. The Contractor shall prepare the PPL electronically as a GEIA-STD-0007-C output file format.

3.5.3 Input Media Requirements for Provisioning Data. TACOM Life Cycle Management Command, Integrated Logistics Support Center (ILSC), Soldier–Product Support Integration Directorate (S-PSID) uses the Army Material Command (AMC) developed Logistics Modernization Program (LMP) applications program to process provisioning data. This program is designed to accept files that meet the following criteria:

a. GEIA-STD-0007-C File Format.

b. No header data present within PPL file (e.g., AAAA, AAAB, etc.).

3.5.4 Government Acceptance. The PPL shall contain all data fields selected from GEIA-STD-0007C before acceptance by the Government. Appendix 2 is provided as an attachment to this SOW. The PPL will be manually reviewed by a Government representative to ensure accuracy of the PPL along with PowerLog-J. The PPL must also pass the LMP Staging Area Validation operation with an error rate of less than (<) 2% before final acceptance by the Government.

3.5.5 Source, Maintenance and Recoverability (SMR) Codes. All NSN items shall be Source coded “P.”

Procured and non-procured items should be coded IAW Army Regulation 700-82. The Government will determine the final SMR coding of each provisioned item on the basis of the individual application.

3.5.6 Essentiality Code. This Code is used to indicate an item’s essentiality in relationship to an Army mission or the extent to which failure of the component spare/repair parts affect the ability of the end item to perform its intended mission. The Essentiality Code is significant to the provisioning process in that it affects the support item requirement determination process when availability computational models are utilized. To determine the Essentiality Code for support items, the Contactor will evaluate the function of each support item in terms of its essentiality to the operational readiness of the end item or system.

3.5.7 PLISN Numbering. The end item Model Record shall be numbered AAAA. Subsequent end item Model Records shall be numbered AAAB, AAAC, and so on, with individual Use on Codes (UOC) for each Model Record.

This information shall be provided to the Contractor at the Logistics Guidance Conference.

The Contractor shall follow the Government structure of Model Records (i.e., part numbers, UOC, and sequence).

The Contractor shall coordinate with the Government representative and structure the Model Records as the Government has structured the files within the Provisioning Master Record (PMR) within LMP. Submissions structured in a different manner will be rejected and must be corrected.

Other than Model Record PLISNs, all PPL items shall start with PLISN A010 (Figure 1, Item 1), and each following item incremented by 10 (e.g., A010, A020, A030, through A990). After A990, continue with B010, B020, through B990, and then continuing with all letters of the alphabet (excluding I and O) as the first position character.

The Contractor must request any desired deviation of PLISN numbering through an address to the Government at a Contractor-requested IPR.

3.5.8 Approved Item Name (AIN). The Contractor shall use an AIN for all entries in the PPL and TM processes and procedures involving repair parts. The Contractor shall review the H6 Federal Name Directory and select the most appropriate nomenclature for the item. The selected AIN shall be used in all TM maintenance processes and procedural references. Contractor naming will be reviewed at the Government Provisioning Conference to determine Government acceptance or rejection of the submitted AIN. Any desired deviation from an AIN may be addressed at the Provisioning Conference. If the nomenclature is changed, the Contractor shall update the TM references, PPL, and RPSTL(s) with the Government-approved AIN of the provisioned item.

3.5.9 Proprietary Names. Trade names, copyrighted names, and/or proprietary names that would require the use of a product or process of one company shall not be used throughout the TM.

3.5.10 Prescreening of Part Numbers. The Contractor shall research and prescreen all submitted repair parts (CAGEC and Part Number) and technical characteristics for existing NSNs within the DOD supply system and shall include this information on the PPL. The Contractor shall keep a record of all NSN research efforts and results. The NSN record shall be presented at the Government Provisioning Conference. Confirmation of screened NSNs on the PPL will take place at the Government Provisioning Review by the DLA. The DLA screening of the PPL will be utilized to update the TM references, PPL, and RPSTL(s). The DLA screening results will take precedence over all other references. On near matches between the PPL reference number and the DLA screening results, the Government will determine the correct reference number and configuration for the PPL. The Contractor shall update the PPL and RPSTL with the Government-approved SMR, CAGEC, Part Number, NSN, and description of the provisioned item.

3.5.11 Bulk Items. These items will be accounted for in their normal position within the top-down generation breakdown sequence, when maintenance practices establish a need for a “Make From” item. Bulk items are materials utilized to fabricate a repair item and purchased in bulk quantities (e.g., wire, fabric, hoses, PVC, gaskets, sheet metal, etc.). Bulk items shall be listed for all items that are source coded “M” (Make From). Bulk items are listed in the PPL by the equipment drawing number or location where the item is to be installed and identified by a unique CAGEC and Part Number. Additional remarks in the description column identify color, size, length, or shape of these items. The stocked bulk item (the bulk material from which the component is manufactured) shall appear in the PPL at the end of the PLISN structure by the bulk CAGEC and Part Number. Bulk items shall be listed in a bulk items list at the end of the PPL in functional group 99 and be “B” indentured. The NHA for the bulk material shall be the Model Record(s). The bulk items list shall contain the total dimensional quantity of each item used on the end item (e.g., length, square foot, etc.). MIL-SPEC, MIL-STD, FED-SPEC, Commercial, or Performance Standards for bulk items that are non-definitive must include documentation of class, type, size, shape, color, and/or dimensions.

Items selected to be made from bulk material shall also be reviewed to determine if the technical ability and tools to cut, make, assemble, and support the bulk material are available at the selected maintenance level.

3.5.12 Make Items. Items are coded as “Make From” items with an “M” series SMR Code, because it is not practical or cost effective to purchase small, modified quantities of a bulk material. Manufactured Items must have an exclusive, unique CAGEC and Part Number listed on the “A” Card. The unique CAGEC and Part Number is for the modified or cut-to-length part. Make From parts do not have NSNs. The PLISN listing the actual bulk item shall reflect the actual CAGEC, Part Number, and NSN for the bulk material used to make the parts. If a portion of bulk item appears more than once, each appearance shall require a PLISN listing of that portion at that location.

3.5.13 Part Numbers and Component Color. Repair parts that are procured either as bare metal or in different colors (i.e., black, green, or tan) from the source of supply shall have a Part Number that distinctly indicates the color of the repair part, assembly, or subassembly (e.g., XXXX-1 for Green and XXXX-2 for Tan). The Part Number indicated on EDFP must be recognized as valid by the source of supply. Repair parts and assemblies shall have the color of the part described on the remarks card of the PLISN entry of that item in the PPL and RPSTL. The Government will determine color of repair parts stocked in the Army supply system.

3.5.14 Common Hardware. The Contractor shall make maximum use of existing Government numbers for all common hardware items. In all cases where they exist, the Contractor shall use American National Standards Institute (ANSI), American Society of Mechanical Engineers (ASME), MIL-SPEC, MIL-STD, FED-SPEC, Commercial, or other Government standard numbers for items such as, but not limited to, nuts, bolts, washers, wire, rope, screws, lubricants, springs, roll pins, and clevis pins. MIL-SPEC, MIL-STD, FED-SPEC, Commercial, or Performance Standards that are non-definitive must include documentation of class, type, size, shape, color, and/or dimensions. The Contractor shall make maximum use of existing commercial or industry specifications or commercial or industry descriptions for all common and commercial items that do not have Government numbers or specifications. Common hardware shall have the dimensional characteristics described on the remarks card of the PLISN entry of that item in the PPL and RPSTL.

3.5.15 Government Rejection of Data Product. A PPL submitted solely with Contractor unique Part Numbers for common hardware (e.g., nuts, bolts, washers, screws) will be rejected. A PPL submitted with placeholders or inaccurate prices will be rejected. A PPL with no CAGEC for any item will be rejected.

3.5.16 Long Lead Time Items. The Contractor shall identify any item on the PPL that is a Long Lead Time Item (LLTI). An LLTI causes extended production or procurement lead-time due to its complexity of design, complicated manufacturing process, or limited production capability. An LLTI is one that would require more than 180 days to deliver the item to the Government.

3.5.17 Components of End Item (COEI). All COEI shall be listed in the PPL. All repairable COEI that are listed separately in the MAC shall be listed in the MAC in their normal top-down breakdown place. Non-repairable COEI that are not listed separately but that have a Work Package (WP) associated with them (replace only) shall also be listed in the PPL in their normal places. All other COEI that are not repairable, have an associated WP, and are not listed separately on the MAC shall be listed after the bulk material and are to be “B” indentured, with the NHA as the Model Record(s). The Contractor shall also provide EDFP for all “P” coded COEI to obtain an NSN.

3.5.18 Basic Issue Items (BII). All BII shall be listed in the PPL after all non-repairable COEI are listed. BII are to be “B” indentured with the NHA as the Model Record(s). The Contractor shall also provide EDFP for all “P” coded BII to obtain an NSN.

3.5.19 Expendable / Durable Items. All identified expendable/durable items shall be listed at the rear of the PPL, after all non-repairable COEI and BII listed. Expendable/durable items are to be “B” indentured with the NHA as the Model Record(s). The Contractor shall provide EDFP for all “P” coded expendable/durable items that require an NSN. Any chemicals or compounds that require NSNs need to have safety data sheets also included as part of their EDFP.

3.5.20 Tools / Special Tools. All identified tools/special tools shall be listed at the rear of the PPL, after all non-repairable COEI, BII, and expendable/durable items listed. Tools/special tools are to be “B” indentured with the NHA as the Model Record(s). The Contractor shall provide EDFP for all “P” coded tools/special tools that require an NSN. No special tool will be required to operate or maintain the IECU.

3.5.21 Government Provisioning Conference. The Government Provisioning Conference will be held at a place, time, and date dictated by program schedule, as indicated by CDRL and mutually agreed on by the Contractor and Government. The number of PLISNs on the end item shall determine the review length. As general guidance, the Contractor shall plan support for five (5) business days per 300 assemblies/subassemblies/repair parts (PLISNs) on the PPL/RPSTL.

3.5.21.1 Purpose. The purpose of the Provisioning Conference is to acquire and use EDFP, PTD, and SPTD to identify supply support for the end item and to complete provisioning actions associated with the provisioning decision process. (i.e., selecting, coding, computing, cataloging, procuring, and distributing support items). The Provisioning Conference will be used as a tool to identify and verify the items on the RPSTL, concurrently listed on the PPL and supported with EDFP, against the Government-approved production model of the end item.

3.5.21.2 Document Support. The Contractor shall provide copies of the MAC, TM(s), RPSTL, EDFP, and PPL at the Government Provisioning Review, as required in the Government Provisioning Conference Plan.

3.5.21.3 Contractor Technical Support. The Contractor shall provide a technical consultant or Field Service Representative (FSR) with expert technical knowledge of the end item and familiarity with all aspects (i.e., operation, maintenance processes, repair part(s), and demand rates) of the end item and related equipment. The FSR should be prepared to answer questions and point out, if requested by the Government team, the location and function of the provisioned item. This facilitates a relationship review of RPSTL items on the contracted end item by the Government team. There will be no teardown or disassembly of the end item, unless requested.

3.5.21.4 Contractor Data Collection. The Contractor shall be prepared with necessary personnel, supplies, and equipment to capture text, data field, and illustration change(s) identified during the Provisioning Conference of the RPSTL, PPL, and/or EDFP. The Contractor shall prepare a master markup of the PPL, RPSTL, and/or EDFP, reflecting any change or update identified during the review. A copy of the master markup shall be delivered to the Government representative at the close of the Provisioning Conference. The Contractor shall make all directed changes or updates to the RPSTL, PPL, and EDFP, depending upon Government guidance and cataloging decisions made at the Provisioning Conference. Updated and/or corrected data shall be included in the next submission of deliverables, such as the TM, PPL, and EDFP. The final submissions of the TM, PPL, and EDFP will not be accepted without inclusion of all technical data changes captured during the Government Provisioning Review.

The Contractor shall record the following for each PLISN on the PPL during the Provisioning Conference.

The Contractor shall provide a copy of this record to the Government at the conclusion of the Provisioning Conference.

a. PLISN items identified with existing NSN, CAGEC, and Part Number.

b. PLISN items reviewed and accepted with acceptable EDFP.

c. PLISN items reviewed and rejected with insufficient EDFP, noting the deficiency.

d. Nomenclature, CAGEC, Part Number, and Federal Supply Class for each PLISN.

3.5.21.5 Government Provisioning Conference Plan. A detailed Provisioning Conference Plan will be made available to the Contractor thirty (30) calendar days prior to the scheduled Review that outlines the agenda, attendees, and specific Contractor and Government roles and…