Attachment 4 Provisioning Statement of Work (PSOW).pdf

PROVISIONING STATEMENT OF WORK (PSOW)

1.0 SCOPE. This Provisioning Statement of Work (PSOW) specifies the Provisioning Technical Documentation (PTD) requirements for this Navy acquisition contract and is furnished in accordance with GEIA-STD-0007-B and GEIA-HB-0007-B.

These commercial products cannot be furnished as extracts within the PSOW due to copyright infringement laws.

2.0 APPLICABLE DOCUMENTS. The following documents apply to this acquisition.

GEIA-STD-0007-B, Logistics Product Data

GEIA-HB-0007-B, Guide to Logistics Product Data

TA-HB-0007-1, Logistics Product Data Reports Handbook

Provisioning, Allowance and Fitting Out Support Manual, Chapter 4

NAVSUP P-719 of 6 June 1999, Guide of the Assignment, Application and Use of Source, Maintenance & Recoverability (SM&R) Codes

MIL-STD-31000, Technical Data Packages (TDPs)

MIL-HDBK-695E, Rubber Products: Recommended Shelf Life

3.0 PROVISIONING REQUIREMENTS.

3.1 PROVISIONING PROGRAM. The Contractor shall establish, implement, and maintain a Provisioning Program in accordance with this PSOW, the Data Item Descriptions (DIDs) DD Form 1664 and the Contract Data Requirements Lists (CDRLs) DD Form 1423 (see Exhibit B of the solicitation). The Contractor shall establish necessary procedures to assure that provisioning data is collected, tracked, and integrated into the provisioning data files described in paragraph 3.5.

3.2 DEVIATIONS. When, in the opinion of the Contractor, a deviation from standards, previous instructions from the technical representative, or requirements of this PSOW is in order, the Contractor shall make a request for deviation in writing to the Contracting Officer with an information copy to the technical representative. The Contracting Officer shall notify the Contractor in writing of approval or disapproval, of the deviation, within thirty (30) days after receipt.

3.3 PROVISIONING CONFERENCES.

3.3.1 CONFERENCES AGENDAS AND MINUTES. The Contractor shall be required to deliver the agenda and minutes for all provisioning related conferences.

3.3.2 PROVISIONING GUIDANCE CONFERENCE (PGC). The PGC is held to ensure mutual understanding of provisioning requirements and responsibilities. It is used to solidify the provisioning team’s understanding of the provisioning system being used to develop and submit Provisioning Technical Documentation (PTD). The Contractor shall make facilities available at the Contractor's site for the PGC, which should be convened within 60 days after contract award.

The Contractor and subcontractor personnel that will prepare the provisioning documentation shall be required to attend. The attendees of the PGC shall thoroughly review the requirements of this PSOW and be ready to present any questions and recommendations relative to the provisioning requirements. [For GFE contracts] The Contractor shall have prepared a system block diagram/family tree (refer to System Configuration Provisioning List [SCPL]) to facilitate the determination of the level to which PTD submission will be required.

3.3.3 LONG LEAD-TIME ITEM PROVISIONING CONFERENCE (LLTIPC). Requirements and criteria for the LLTIPC will be addressed during the PGC. The purpose is to identify those items with a production/acquisition time frame warranting early acquisition.

3.3.4 INTERIM SUPPORT ITEM PROVISIONING CONFERENCE (ISIPC). Requirements and criteria for the ISIPC will be addressed during the PGC or when the ISS option is exercised.

3.3.5 PROVISIONING CONFERENCE. The purpose of the Provisioning Conference is to finalize the technical and management coding of the Data Product Deliverables (DPD). Requirements and criteria for any provisioning in-process reviews leading up to the provisioning conference will be addressed during the PGC. The requirement and criteria for a Provisioning Conference will be addressed during the PGC. When the provisioning conference is required, the Contractor shall provide facilities unless the Government chooses to hold the conference at a Government facility.

3.4 PROVISIONING TECHNICAL DOCUMENTATION (PTD).

3.4.1 PROVISIONING SUBMITTAL. PTD submittal shall include Component Identification Data (CID), Data Product Deliverables and Engineering Data for Provisioning (EDFP). The Contractor shall provide PTD in accordance with this PSOW, the data element requirements of Appendix D of GEIA-HB-0007, TA-HB-0007-1 (for reference), the associated DIDs and CDRLs (see Exhibit B of the solicitation), and the General APL Worthiness Guidance and the HM&E APL Worthiness Guidance (Date applicable at contract award) located on the Provisioning Center of Excellence (PCOE) website at https://icaps.dc3n.navy.mil/pcoe/pcoe.html.

3.4.1.1 PTD SEQUENCING. Individual Provisioning List Item Sequence Numbers (PLISNs) shall be sequenced by one of the following methods:

a. Electronic Systems and Equipment. PTD for electronic systems and equipment shall be sequenced by reference designation.

b. Non-electronic Systems and Equipment. PTD for non-electronic systems and equipment shall be sequenced by indenture code.

c. Non-electronic Systems and Equipment having Electronic Components that are designed with Reference

Designations. Any non-electronic systems or equipment containing electronic components shall be sequenced by indenture code; however, the PTD for the electronic components in these systems or equipment shall be sequenced by reference designation.

3.4.1.1.1 REFERENCE DESIGNATORS. For end items requiring a top-down breakdown by means of reference designation, the contractor shall assign reference designators. PAFOS Chapter 4, Appendix E provides an example of a breakdown in electronic equipment, and illustrates the relationships between Reference Designation, Quantity per Assembly, Quantity per End Item, and Part Number or Reference Number.

3.4.1.1.2 INDENTURE CODES. The contractor shall assign indenture codes for all non-reference designator provisioning packages. PAFOS Chapter 4, Appendix F provides an example of a breakdown in HM&E equipment, and illustrates the relationship between Indenture Code, Quantity per Assembly, Quantity per End Item, and Part Number or Reference Number.

3.5 PTD DEVELOPMENT AND DELIVERY. Delivery of Logistics Product Reports (LPRs) shall be via the Navy’s Interactive Computer Aided Provisioning System (ICAPS). ICAPS was developed by the government for the purpose of developing and transmitting provisioning related data and is available free of charge to contractor personnel as well as government agencies. Two versions of ICAPS, with supporting documentation, are currently available for downloading from the ICAPS home page at https://icaps.dc3n.navy.mil/. The contractor shall contact the TSA to obtain a user ID and password required for access to ICAPS C/S.

3.6 STATEMENT OF PRIOR SUBMISSION (SPS). The Contractor shall submit an SPS by providing Component Identification Data (CID) in accordance with the requirements of paragraph 3.7.2. The SPS shall apply to the end item, or to any component thereof, and it shall provide total identification of the system, equipment or component. By submitting an SPS, the contractor certifies all of the following:

• PTD, which may satisfy the requirements of the contract, has previously been furnished to the Government for the system, equipment or component being procured. (When an SPS is submitted without an APL identified, the submitter shall identify the Procurement Contract Control Number (PCCN), the submittal date and the government agency to which the PTD was previously submitted.)

• The required maintenance philosophy is fully supported.

• All replacement parts are 100% identical to those provided by the previously furnished PTD.

If there are maintenance philosophy/part differences, an SPS with Differences shall be submitted as a DCN with supporting EDFP that identifies the differences. The SPS with Differences shall identify the changed part numbers from before the change as deletions and the new part numbers as additions. The government shall reject an SPS if it does not meet both the data and certification requirements of this contract. If an SPS is rejected, the contractor shall be required to submit a new provisioning package that meets the requirements of paragraph 3.4.1.

3.7 COMPONENT IDENTIFICATION DATA (CID). The CDRLs (see Exhibit B of the solicitation) and LMI Worksheet specify the data, format and media requirements for CID. The Contractor shall use CID to submit identification data for all systems and equipment. CID shall be delivered concurrently with every submittal of Data Product Deliverable. The Contractor shall use CID for submittal of Provisioning Header Data, Statements of Prior Submission (SPS), and Advance RIC requests.

https://icaps.dc3n.navy.mil/pcoe/pcoe.html https://icaps.dc3n.navy.mil/

3.7.1 PROVISIONING HEADER DATA CID. The Contractor shall submit header data with each provisioning project.

For Provisioning Header Data, the Contractor shall submit the Logistics Product Data (LPD) (provisioning data elements) as specified by GEIA-HB-0007-A, Appendix D, Figure D-3 for each PCCN. The data shall provide the Navy sufficient end item information to identify the system or equipment, the applicable contract, and the planned installations. NOTE: If LPR is developed in a system other than ICAPS this data cannot be established until the project is uploaded into ICAPS for submission IAW the CDRL (see Exhibit B of the solicitation).

3.7.2 STATEMENT OF PRIOR SUBMISSION (SPS) CID. To satisfy the data and delivery requirements of SPS, the Contractor shall submit the following LPD:

- PCCN

- Repairable Item Code (RIC) [Allowance Parts List (APL) and/or Allowance Equipage List (AEL)]

- Copy of Purchase Order or Certificate of Identity (COI) or other documentation, as agreed upon during the PGC, to certify item procured/installed is supported by the SPS

3.7.3 ADVANCE RIC CID. The Contractor shall use CID to submit the data required to request an Advance RIC for any system or equipment that will not have provisioning completed prior to 60 days before Load COSAL Cutoff beginning at 120 days prior to Load COSAL Cutoff unless otherwise specified by the TSA. The Contractor shall submit the Contractor shall submit the following LPD:

- End Item Part Number (Final – Incomplete or Unknown is not acceptable)

- RIC Nomenclature

- Scheduled date for complete PTD to be provided to the NAVSEA TSA

- Applicable system/function, if known

3.8 TOOLS AND TEST EQUIPMENT. Tools and test equipment unique to, or built-in as an integral part of the equipment, shall always be included in the PPL for the equipment.

3.9 ENGINEERING DATA FOR PROVISIONING (EDFP). APPROVED EDFP meeting the requirements of DID DI-SESS- 81874 is required for all systems or equipment that is acquired for Navy use and for which PTD is being acquired. EDFP that does not identify the original manufacturer of the part, and, material or material specifications, and, dimensions, and, other characteristics shall be supplemented with catalog cuts or specification sheets identifying all items required to accomplish maintenance during the life cycle of the equipment listed in the EDFP Bill of Material (BOM) or corresponding EDFP parts list.

3.10 MANUFACTURER’S COMMERCIAL MANUALS. The Contractor shall provide the manufacturer's commercial manuals.

These manuals will be used to supplement EDFP and the provisioning data. This requirement applies only if commercial manuals are available. If no commercial manual exists for the equipment or component, then this requirement for that equipment or component will be waived.

3.11 PROVISIONED ITEM ORDER (PIO). If the Government elects to procure support items from the contractor, the Government will release an initial basic PIO for the required support items. If concurrent delivery is required and such delivery necessitates a delay in the delivery of the end items or components, an adjustment in the delivery requirements will be considered.

The Government reserves the right to place additional orders for support items during the life of the contract.

3.12 VENDORS/SUBCONTRACTORS. When the prime contractor buys end articles or a portion thereof from a vendor/subcontractor, the prime contractor shall impose this specification upon its vendors/subcontractors. The inclusion of the requirement for such data on contractor’s subcontracts/purchase orders to its vendor/subcontractors does not relieve the prime contractor of its obligation to insure timely delivery of the required Provisioning Data Products, EDFP, and other provisioning deliverables.

3.13 PTD SUBMISSION SCHEDULES. PTD will be delivered as specified IAW the submission schedule approved during the PGC. The PTD Submission Schedule presented by the contractor at the PGC shall, at a minimum, consist of a graph developed from the ratio of anticipated monthly PTD submissions for the acquisition. This graph shall be plotted across a timeline depicting the length of construction period in months. PTD submissions shall be entered into a configuration database by the contractor, in accordance with local procedures, for monitoring.

3.14 SHIP LEVEL PROVISIONING PARTS LIST (SLPPL). The SLPPL shall be prepared to the ship level with submissions broken down, at minimal, IAW the Ship Work Breakdown Structure (SWBS) table below. The Procuring Program Office will notify the contractor if further SWBS breakdown structures will be required and to what level. A SLPPL shall contain miscellaneous parts and items that are not included in individual equipment or component (unit) provisioning data or Common and Bulk Items List (CBIL). SLPPL items are not associated with a specific parent system or equipment; however, they can be related to an overall ship system and they are used to develop the 89000 Series APLs. The below Ship Work Breakdown Structure (SWBS) represents the minimally acceptable SLPPL submissions:

SWBS Code Functional Title SWBS Code Functional Title 100 Hull Structure 600 Outfit and Furnishings 200 Propulsion Plant 700 Armament 300 Electric Plant 800 Integration/Engineering 400 Command and Surveillance 900 Ship Assembly and 500 Auxiliary Systems Support Services

At a minimum, a separate SLPPL shall be prepared for each SWBS code listed above. An item having multiple applications shall be listed in each SLPPL for each ship level SWBS code in which it is used.

3.15 SYSTEM CONFIGURATION PROVISIONING LIST (SCPL). The SCPL establishes a “family tree” relationship of components to the end item (system). This is required for GF end items (systems) only. The GF SCPL will detail each separate appearance of the component level items that comprise the end item (system) and will also list all attaching parts used to integrate the component level items into the end item (system). These attaching parts should not be included in the individual component level item PPL.

3.16 DESIGN CHANGE NOTICE (DCN). The contractor shall notify the TSA of all changes, whether of a production or modification type, which are approved for incorporation into the end item and which modify, add to, delete, or supersede parts in the end item or its supporting equipment. When an approved engineering design or production change requires new identification as specified in DoD-STD-00100D (AR), paragraph 402.14, the contractor shall submit PTD revisions via DCNs in accordance with the following:

a. When the approved change affects interchangeable repairable assemblies so as to introduce non-interchangeable parts, identify the part number before the change as a deletion and the part number after the change as an addition.

b. Change and document the part number of the next higher assembly, and those of all progressively higher assemblies, up to the assembly where interchangeability is reestablished. PTD shall include the interchangeable assembly.

c. EDFP is not required for deleted items.

d. Changes that occur after PTD has been delivered shall be documented as a revision to the applicable PTD.

When the design change significantly impacts the system or equipment configuration, and when directed by the Administrative Contracting Officer, a changed system or equipment shall be provisioned as a new end item and documented by PTD with associated

EDFP.

3.17 INTERIM SUPPLY SUPPORT (ISS) PROVISIONING REQUIREMENTS. If the ISS option is exercised, Interim Support Item Lists (ISILs) will be required. This will provide a parts breakdown of the system or equipment using mandatory LPDs for each part. The specific DPDs required in determining ISS requirements shall be IAW Appendix I of PAFOS Chapter 4.

The contractor shall utilize the same data development and submission methodology for ISS as required for the remainder of the LPR.

PROVISIONING STATEMENT OF WORK (PSOW)