FINAL AF PreProposal Conference Provisioning 9 Dec 22.pptx

MP-TACAN

Provisioning Foundation for Sustainment Amanda Jones Lori Church Valerie Gauthier

December 9, 2022

UNCLASSIFIED

Air Force Sustainment Center

Disclaimer Statement No statement or conduct of any government representative at this meeting is to be construed as any form of change or amendment to the Request for Proposal (RFP) FA8102-23-R-2000. All participants are reminded that only the contracting officer has the authority to change or modify the RFP or any of its requirements. Should the contractor believe that any statement or conduct of any government representative in any way changes or modifies the RFP, the contractor is required to comply promptly with RFP Attachment 4 Section L Paragraph 2.2.3.

This briefing is intended to provide an overview of the provisioning requirements included in the MP TACAN to support award without discussions. The Government intends to award without discussions, but reserves the right to conduct discussions if necessary

This conference does not constitute a contract, a promise to contract, or a commitment of any kind on the part of the Government nor does it constitute a change to the RFP. Any discussions or suggested information at the meeting are for discussion purposes only.

Rules of Engagement

ALL QUESTIONS SHALL BE SUBMITTED IN WRITING VIA CHAT BOX IN THIS MEETING

You may use the chat during the meeting Don’t hold questions until the end The Government may respond via Chat or Verbally during the discussion and reserves the right to respond at a later date or not respond at all as appropriate The Government will post the slides presented and the Q&A from this meeting to SAM.Gov.

Introductions Amanda Jones- USAF- Contracting Officer Lori Church- DLA- Air Force Provisioning Team Lead Valerie Gauthier- USAF- Provisioning Carla Bogan- USAF- Provisioning Team Lead

Agenda

MP TACAN General Information Purpose: PRE-RFP Provisioning Conference is held to ensure offerors understand contract requirements for provisioning Request for Proposal (RFP) FA8102-23-R-2000, dated 18 Nov 22 First Provisioning Guidance Conference (PGC) held 45 days after contract award IAW SOW 9.1.6.2 Provisioning Requirements Outlined in the Statement of Work (SOW) SOW para.- 7.2.1, 9.1.1.1, 9.1.2.8, 9.1.5, 9.1.6, 9.1.7, 14.1, 23, 25, and 26 Associated Contract Line Items Numbers (CLINs) CLINs x001- x006, x008, x011, x013, and x017 Contract Data Requirements Lists (CDRLs) X022- Logistics Product Data (LPD) X023- Engineering Data for Provisioning (EDFP)

Transition Change to DLA- Ms. Lori Church

A pre-proposal conference is held to ensure offerors understand RFP requirements. The RFP provides information on specific Air Force provisioning documentation, data submittal, media, Initial Provisioning Performance Specification (IPPS),long lead items list (LLIL), provisioning parts list (PPL), etc., to permit them to develop realistic responses to the RFP

PRE-PROPOSAL CONFERENCE (PPC)

The PGC is the first provisioning related meeting with the successful offeror after contract award. The guidance conference provides a medium through which the contractor, major vendors, and Air Force personnel can achieve a mutual understanding of the contractual provisioning requirements. Responsibilities are clearly defined and provisioning milestones reviewed and updated as needed on the Provisioning Performance Schedule (PPS), AFMC Form 718.

PROVISIONING

GUIDANCE CONFERENCE (PGC)

The Spares Provisioning Conference provides for the Government to make item selection and assign technical and management codes (previously referred to within the Air Force as a Source Coding Conference) using the Logistics Product Data (LPD), Engineering Data for Provisioning (EDFP), Maintenance Engineering Analysis (MEA) and/or Repair Level Analysis(RLA).

The Contractor assists/answers questions relating to the drawings, answer NSN questions and provide suggested quantities.

SPARES

PROVISIONING CONFERENCE (SPC)

Legal Governance for Provisioning Public Law TITLE 10 - ARMED FORCES, Subtitle A- General Military Law, Part IV - SERVICE, SUPPLY, AND PROCUREMENT.

10 U.S.C. 2451 (reference (b))

Federal Acquisition Regulation FAR 52.215-1 through 52.219-2

DoD Oversight DFARS 217.76, Contracts with Provisioning Requirements DFARS PGI 217.76, Contracts with Provisioning Requirements DFARS PGI 217.7601, Provisioning DoDD 5000.01, The Defense Acquisition System DoDI 5000.02, Operation of the Defense Acquisition System DoDM 4140.01, DoD Supply Chain Material Management Procedures MIL-HDBK-502A, Product Support Analysis

DoD 4140.1-R was canceled and replaced by DoDM 4140.01 DoD Manual 4140.01, Volume 1 – Operational Requirements DoD Manual 4140.01, Volume 2 – Demand and Supply Planning** DoD Manual 4140.01, Volume 3 – Materiel Sourcing DoD Manual 4140.01, Volume 4 – Make and Maintain Materiel DoD Manual 4140.01, Volume 5 – Delivery of Materiel DoD Manual 4140.01, Volume 6 – Materiel Returns, Retention, and Disposition DoD Manual 4140.01, Volume 7 – Supporting Technologies DoD Manual 4140.01, Volume 8 – Materiel Data Management and Exchange DoD Manual 4140.01, Volume 9 – Materiel Programs DoD Manual 4140.01, Volume 10 – Metrics and Inventory Stratification Reporting DoD Manual 4140.01, Volume 11 – Inventory Accountability and Special Management and Handling DoD Manual 4140.01, Volume 12 – Sales and Operations Planning

Legal Governance for Provisioning USAF Oversight AFI 63-101/20-101, Acquisition and Sustainment Life Cycle Management AFPD 23-1, Materiel Management AF Initial Provisioning Performance Specification (IPPS) AFMCMAN 20-106, Provisioning

Commercial Oversight GEIA-STD-0007, Logistics Product Data (subsequent versions) GEIA-HB-0007, Logistics Product Data Handbook (subsequent versions)

NOTE: GEIA-STD-0007 and GEIA-HB-0007 are copyrighted materials and may not be reproduced without permission from TechAmerica. Copies of GEIA-STD-0007 and GEIA-HB-0007 must be bought from TechAmerica. The Prime Provisioning Activity (PPA) will not provide copies to anyone; Government or Contractor.

LOGISTICS CONCEPT

Decisions involving the Supply Chain Management (SCM) and ownership of the items.

Used by the PPA to determine which type of provisioning is required.

A short definition and purpose of each data requirement for Provisioning on an acquisition effort DID 81758A LPD PTD – This is the Data Item Description that describes the data that the requiring authority needs for the government Provisioning review. It is imperative that the offeror, at a minimum, read the DID.

DD1423 CDRL x022 (DI-SESS-81758A/T PTD) – This is the CDRL (aka data delivery) that is put on contract that tells the successful offeror what/who to deliver PTD data. No one is to revise our Provisioning/EDFP data requirements without our written permission (the request has to go thru the PPA to obtain HQ Provisioning OPR’s approval). The Contracting Officer will provide written notification of any approved revisions.

SOO= Statement of objectives; RFP=Request for Proposal; LPD= Logistics Product Data; PTD=Provisioning Technical Document DID= Data Item Description; CDRL= Contract Data Requirements List; PPA= Prime Provisioning Activity; SERD= Support Equipment Recommendation Data; EDFP= Engineering Data for Provisioning

LOGISTICS PRODUCT DATA (LPD)

for PROVISIONING TECHNICAL DATA (PTD)

SOW= Statement of Work SOO= Statements of Objectives PWS= Performance Work Statement

LOGISTICS PRODUCT DATA (LPD)

for PROVISIONING TECHNICAL DATA (PTD) A. Attachment:

1. Initial Provisioning Performance Specification (IPPS) w/Atchs dated 10 Aug 2017

B. The Prime Provisioning Activity (PPA) for this effort is 406 SCMS/GULAB-Tinker. Physical address is identified in Block 14; E-mail: gbmsp.Provisioning@us.af.mil.

C. Specific LPD summaries and summary sequence to be delivered on this contract are:

C.1_x__Provisioning Parts List (PPL) in Topdown Sequence C.2___Short Form Provisioning Parts List (SFPPL) in Reference Number Sequence C.3___Common and Bulk Items List (CBIL) in Reference Number Sequence C.4_x__Design Change Notice (DCN) in PLISN Sequence C.5_x__Statement of Prior Submission (SPS).

C.6_x__Long Lead time Items List (LLIL) in Reference Number Sequence - Recommended

LOGISTICS PRODUCT DATA (LPD)

for PROVISIONING TECHNICAL DATA (PTD) D. Blocks 10, 11,12 & 14:

D.1. PPL, SFPPL, LLIL, CBIL: Date(s) to be established at the Provisioning Guidance Conference (PGC) and reflected on the AFMC Form 718 (Atch 1 to the Initial Provisioning Performance Specification (IPPS)). See para 3.1 of the IPPS.

D.2. DCN: See para 10 of the IPPS.

D.3. Incremental submission of PTD is authorized.

D.4. SPS: When the IPPS is provided with the solicitation, an offeror’s SPS shall be as outlined by the solicitation. When the IPPS is furnished after contract award, the contractor shall furnish a SPS within thirty (30) days after receipt of the IPPS. See para 7 of IPPS.

E. PTD transmittal document will reflect content of PTD submitted; i.e., Contract Number, PCCN, SCC, Type PTD, and Line Item Count.

F. Data Element definitions will be in accordance with GEIA-STD-0007-C and attached IPPS.

G. In the event PTD submittal deliveries are to be made to a secured program specific electronic site (Contractor or Government), a transmittal notification will be concurrently forwarded to the PPA via e-mail at gbmsp.Provisioning@us.af.mil.

Provisioning Technical Documentation (PTD) Types

Long Lead Time Items Listed (LLTIL) – Recommended: Type PTD Code “R”. A list of those items with long lead times, which due to their complexity of design, complicated manufacturing processes, or limited production capacity, may cause production or procurement cycles which would preclude timely and adequate delivery, if not ordered in advance of normal provisioning. Adequate delivery means delivery of spares 30 days before Operational Need Date (OND). When the same item appears on the PPL, Prior PLISN block will show the PLISN from the LLTIL.

Provisioning Parts List (PPL): Type PTD Code “G”. PPL is a 100% top down/breakdown sequence document with all repairable and assembly items broken down. Assignment of PLISNs will begin with A (ex: AAAA, AAAB, etc. thru 9999). PTD and one set of drawings will be required sixty (60) days prior to provisioning source coding conference (i.e. Spares Provisioning Conference) be sent to the PPA and one set to DLA Info Svcs, Battle Creek, MI.

PTD Types (cont.)

Short Form Provisioning Parts List (SFPPL): Type PTD Code “F”. SFPPL contains only those support items which are recommended by the contractor for maintenance of the end item, component, or assembly (LRUs/SRUs). Assignment of PLISNs will begin with A (ex: AAAA, AAAB, etc. thru 9999). PTD and one set of drawings will be required sixty (60) days prior to provisioning source coding conference be sent to the PPA and one set to DLA-LIS, Battle Creek, MI.

Items LRU’s (Line Replaceable Units): Components that are removed/replaced on equipment as a complete unit (ex: avionics or electronic components).

SRU’s (Shop Replaceable Units): Repairable subcomponents that are removed/replaced from LRU’s to make them serviceable. They are then sent to a repair shop where they are repaired and returned to supply.

Recoverable Item Breakdown (RIB): Type PTD Code “B”. Also known as a Recoverable Item Provisioning Parts List (RIPPL). This a “structured” list of all the items which made up a recoverable item. A RIB is requested from the contractor when such a breakdown was omitted from a PPL. Source coding is required, just as for a PPL.

Design Change Notices (DCNs): Type PTD Code “D”. Required on changes after the initial provisioning has been accomplished. All required blocks are to be filled. Notifies provisioning of an engineering change which is approved for incorporation into the end item on contract and which modifies, adds to, deletes, or supersedes parts in the end item. DCNs fall into two categories:

(1) ECP (Engineering Change Proposal). Requires an entry in D220 Block 65 (change authority block). This block identifies the contractor’s Engineering Change Number (ECN) that directs the change, or some other authorization. On changes resulting from an ECP, with the ECN in Block 65 and the TOCC (type of change code) (block 53) showing a “D” (delete), “L” (limited P/N application), or “Q” (quantity change), D220 will output a DCN. With TOCC “T” (typographical error) or “M” (modify), and Block 65 blank, D220 will output an ACN (Administrative Change Notice).

Non-ECP. These are commonly called ACNs which result from omission or correction of data submitted by the contractor. In these cases, Block 65 will be blank. ACNs are handled one of two ways:

TIME FRAME ON DCNs:

Within 21 calendar days after release for fabrication or purchase for prime contractor design items.

Within 42 calendar days after release for fabrication and purchase for sub-tier supporter design items.

IPPS Aug 2017 – This is the Initial Provisioning Performance Specification; this outlines to the “sucessful offerors” the programming specifications needed in data submittal that is compatible with the D220 system.

IPPS ATCH 1 AFMC 718 Provisioning Performance Schedule (Attachment 15 to RFP) – This is the Provisioning Performance Schedule (PPS) and a blank form is an attachment to the IPPS for a Request for Proposal (RFP) aka Data Call*. At the PGC, this form is filled out/reviewed and signed by the government and contractor which sets the schedule for Provisioning data submittal from the contractor. An action item must be generated to the Program Manager during the PGC to have the approved PPS added to the contract (replacing the proposed PPS).

IPPS PTD Format – This is attachment 2 to the IPPS; this provides the “successful offerors” contractor the cards, card columns, and format needed for our D220 legacy system to accept contractor raw data for “load”.

INITIAL PROVISIONING PERFORMANCE SPECIFICATION (IPPS)

IPPS (CONT.)

AFMC 718 Provisioning Performance Schedule (PPS) IPPS Attachment 1

RFP Attachment 15

AFMC 718 (PPS) DATA ELEMENTS

Elements of data essential to develop the Provisioning Performance Schedule to ensure support by the Operation Need Date. *all dates use the eight-digit format, YYYYMMDD.

Date: 20221103 End Article: Man-Portable Tactical Air Navigation (MP TACAN) Contractor: Enter the contractor’s name and address End Article Delivery Dates: Enter the date of first delivery and the date of last delivery (considering time frame proposed under Factor 1, Subfactor 5- Delivery) Solicitation or Contract Number: FA8102-23-R-2000 Revision: if it’s a revision to a contract-enter the revision number and associated date Type of Contract: Engineering and Manufacturing Development w/Production Option (EMD w/Prod Opt) *error on form says EMC w/Prod Opt

AFMC 718 (PPS) DATA ELEMENTS (CONT.)

Event #1-Contract Award: enter date of contract award 20230929 (estimated)

Event #2- Guidance Conference: the Provisioning Guidance Conference (PGC) is held at the earliest possible date, but no later than 45 calendar days after the mailing date of the contract.

Event #3- Defense Logistics Services Center (DLSC) Screening: The contractor submits provisioning screening data to DLCS not earlier than 30 days prior to the submittal of PTD to the PPA. LSA-032 data is sent to Prvsngscrng@dla.mil

Event 4-SAIP- all of the section 4a-4e is no longer used so all areas are N/A

Event 5: Long Lead Items List (LLIL) with EDFP and DLSC Screening Results *discussion to be had at PGC to determine what Long Lead Items time frame is, i.e. Longest production lead time.

Start: when the contractor can deliver the data Finish: maybe 45 days

Event 5b- Recommended Items: These items are furnished by the contractor as soon as possible after award of the contract and progressively as quickly as engineering design and data are released by the contractor. A reasonable cutoff date by which all Long Lead Time Item Lists are received for Air Force processing would be 45 calendar days prior to release of Provisioning Parts List by the contractor. *generally this will be N/A

Event 5c- Provisioning Conference: (Spares Provisioning Conference) A Spares Provisioning Conference, for the long lead items is scheduled no later than 90 calendar days prior to the contractor's order need date.

Event 5d- PIOs Released to Contractor: Provisioned Item Orders (PIOs) for Long Lead Items are released to the contractor within 30 calendar days of receipt of the Long Lead Time Item List. *this section is N/A

Event 6- PTD/EDFP Requirements: Provisioning Technical Documentation/Engineering data for Provisioning Requirements (PTD/EDFP). The contractor prepares and submits the Logistics Product data/Engineering data for Provisioning not later than 60 calendar days prior to the scheduled Spares Provisioning Conference. *however, need to wait for D155 review from Battle Creek which can take up to 90 days.

Event 7- Provisioning Conference: Spares Provisioning Conference. The scheduling of the spares Provisioning Conference depends upon the capability of the contractor to produce the required Logistics Product data and Engineering data for Provisioning on a timely basis. However, the conference needs to be scheduled no later than 60 calendar days after receipt of Provisioning Technical Documentation/Engineering data for Provisioning. Start and end dates entered in YYYYMMDD format.

Event 8- PIOs w/Delivery Schedule: Provisioned Item Orders with Delivery Schedule. **N/A Tinker AFB does not do PIOs.

Event 9- Acceptance/Revision of Delivery Schedule: *N/A as this is in regard to PIOs and Tinker AFB does not do PIOs.

Event 10- Spares Need Date: The established date wherein spares are needed to provide logistics support. IAW Programming Checklist but NLT 90 days prior to OND

Event 11- Training Start Date: The established date wherein spares are needed to provide logistics support for training equipment. As needed, add comments to the Timing column.

Event 12: Operational Need Date: The established date for operational capability of the end item. As needed, add comments to the Timing column. *this is discussed at the PGC and the date is dependent on many factors; ultimately-when the supply system (organic) is able to support.

Remarks. Comments need to be provided in this block for any discrepancies in the calendar dates, or for any justification for actions taken outside of the standard/normal timeframes.

Approval Signature Blocks. The completed form needs to be signed by the Air Force provisioning chairperson, contractor representative and applicable product support manager.

LPD CARD FORMAT

IPPS Attachment 2

SAMPLE LSA-036

NO!

SAMPLE LSA-036 (cont.)

NO!

SAMPLE LSA-036 RAW DATA

YES!

PIIN cc 7-25, Model or Type cc 26-46, Prime CAGE cc 57-61 intentionally left blank for guidance purposes only

DID 81874 EDFP – This is the Data Item Description that describes the data that the requiring authority needs for the government in support of Provisioning reviews.

DD 1423; CDRL x023; (DI-SESS-81874/T EDFP) - This is the CDRL (Engineering Data for Provisioning; aka data delivery) that is put on contract that tells the “successful offeror” what/who to deliver the “supporting technical documentation” to a provisioning PTD.

ENGINEERING DATA FOR PROVISIONING

(EDFP)

IPPS

(EDFP)

3D MODELING

For provisioning purposes three-dimensional (3-D) “model-based data” in Adobe (.PDF) format is preferred by the Government

EDFP shall be an integral part of the electronic 3D Model

The EDFP will be annotated within the model to provide definitive identification of dimensional, material, mechanical, electrical, or other characteristics adequate to describe the end article(s) on contract

The data known as geometry, dimension, and tolerance (GDT) is included in this definition of EDFP as is the data often referred to as form, fit, and function which indicates the physical characteristics, location, and functions of the item

(EDFP)

The Government prefers electronic EDFP delivered using DoD Safe over paper copy

Submitted EDFP package is to be clearly marked to identify the following information:

Name of Equipment/Item Being Provisioned (Acronyms defined) Contract Number CAGE Code

PCC

SCC

Contact Information (who to contact if there are questions)

All EDFP is to be written to files and folders without excess software, reader files, or software. Delivery media shall be: CD+/-R, DVD +/-R or email.

Note: CD+/-RW and DVD +/-RW are not acceptable

Checklist for Contractor’s EDFP

CONTRACT NUMBER: FA8102-23-R-2000

CONTRACTOR:

CHAIRPERSON’S NAME/OFFICE SYMBOL:

CHECKLIST FOR CONTRACTOR’S EDFP

1. Tech data packages should be submitted as specified on the AFMC Form 718 Provisioning Performance Schedule (PPS) and in the sequence specified in Block 16 of the CDRL x023 Delivery of EDFP must occur on schedule or the provisioning conference may be delayed. NOTE: Assistance from the Administrative/Procuring Contracting Office (ACO/PCO) will be requested if the contractor fails to deliver quality tech data on schedule.

2. Tech data packages must include information sufficient for provisioning, cataloging, and standardization purposes (e.g., physical, dimensional, mechanical, electrical performance characteristics, location, form, fit and function of the item) so items entering the inventory can be fully described.

3. Tech data packages must be translated to English if foreign contractors are involved.

(cont.)

4. Letters of refusal to supply tech data are not acceptable. DFARS 252.227-7013, Rights in Tech Data, the government is entitled to unlimited rights in tech data in the following categories: form, fit or function data that describes the required overall physical, functional and performance characteristic of an item, component or process to the extent necessary to permit identification of physically and functionally interchangeable items. Subcontractors or suppliers may submit data directly to the government, rather than through a higher-tier contractor, subcontractor or supplier. Therefore, regardless of limited rights claims, the prime and all subs must provide adequate tech data for the express purpose of identifying and cataloging items with a full description.

5. Drawings are required for all first appearance non-stock listed items with the exception of those identified as a government specification or standard regardless of SMR code.

6. When the prime contractor is the Design Control Activity (DCA) and the actual manufacturer is someone else, two or more reference numbers will be indicated on the EDFP.

(cont.)

7. Procedures are established to withhold payment until adequate technical data is received. For items that are not separately priced from the hardware buys which they support, DFARS 242.227-7030 is applicable and provides for up to ten percent (10%) of the contract amount to be withheld pending acceptance of the data requirement. For data that is separately priced, payment will be made after acceptance has been performed by the Government via submission of a DD Form 250 for said data.

8. In accordance with Block 12 of CDRL x023 for DI-SESS-81874, complete and legible EDFP is to be delivered concurrent with delivery of the Provisioning Technical Documentation (PTD) to the PPA (i.e., all drawings are included and necessary information is included on each drawing). If the complete EDFP is not provided at that time, the contractor will identify and provide the missing EDFP no later than 30 days prior to the provisioning conference.

SUMMARY

PROVISIONING is one of the most important Logistics Functions Air Force Initial Provisioning Performance Specifications (IPPS) Provisioning Technical Documentation (PTD) Types

LLTIL

PPL

DCN

PTD delivery schedule will be in accordance with Provisioning Performance Schedule (PPS) AFMC Form 718 Engineering Data for Provisioning (EDFP) is delivered concurrently with its associated PTD EDFP in accordance with ASME Y 12.24M Electronic PTD and EDFP deliveries

QUESTIONS?

image3.jpeg image4.jpeg image1.png image5.jpeg image6.png image7.png image8.png image9.png image10.png image11.png image12.png image13.png image14.png image15.png image16.png image17.png image18.png image19.png image20.png image21.png image22.png image23.png image24.png image25.png image26.png image27.png image28.png image29.jpeg image2.png