Ref_FA810917R0001_Update_03_Feb_2017.pdf

Ref FA8109-17-R-0001 DMSMS Predictive Tool

Updated Information:

A. Sources Sought Synopsis - Period of Performance change:

The planned service acquisition is for three years; a one-year basic ordering period and two one-year priced option periods, and a potential six-month extension.

B. Questions posed to government program team – generic or combined questions/responses-

[Note: Industry Day Charts were posted on FedBizOps on 22 Nov 2016]

1.Q.With respect to the Appendix C data, it appears that this effort will potentially require the vendor to provide those 30 data attributes for 26,000,000 lines of data (780,000,000 data elements); and that each will have to be researched, pulled, and validated within 90 days?

A. Appendix C of Draft PWS has 37 data fields and as shown in Industry Day Appendix C Chart.

This requirement requires the contractor to upload Appendix B data, relink every component item to its next higher assembly and have all Appendix C data loaded into the tool and made available to the users within 90 days of contract award.

2.Q.What is rationale for collecting the Appendix C data within DMSMS tool and within 90 days?

A. Appendix C data is vital to solving DMSMS issues at the component level. Past market research has shown all major DMSMS tool owners claim the Appendix C data has already been collected by them on millions and millions of parts and that it’s just a matter of transferring it to the USAF data configuration. Users cannot use the tool to effectively combat part obsolescence until all the data is transferred and populated per the requirements.

3.Q. How is Appendix C data used in tool?

A.With Appendix C data usage, the USAF combats DMSMS at the lowest part indenture level which is the individual component item. The DMSMS tool supports the in-house repair of all weapon systems managed across USAF enterprise. Not having the Appendix C data would make it almost impossible for engineers to find a form/fit/function replacement for a part that is no longer being produced.

4.Q. Couldn’t the USAF transfer Appendix C data for access or compilation?

A. The USAF has limited user rights to the Appendix C data and is afforded no other rights beyond that which is allowed under current contract. No Appendix C data will be provided by the USAF.

5.Q. How and where is existing Appendix C data stored and is it from a single source?

A.The current contractor provides the Appendix C data as a limited rights service to the

USAF. The USAF has no knowledge of where the data was collected or what medium it is stored on.

6.Q. .Q. How much of Appendix C data is used?

A. Appendix C data is used for tool functionality.

7.Q. Will offerors be given access to Appendix C data?

A.The USAF has limited user rights to the Appendix C data and is afforded no other rights beyond that which is allowed under current contract. No Appendix C data will be provided by the USAF.

8.Q. Could potential offerors view the current DMSMS Predictive Tool data prior to RFP release, say with a sample of part numbers queried in the live database?

A. USAF users have their own set of unique circumstances for logging into the DMSMS tool and running reports. Each report contains the data the user wants to see at that time for that circumstance. A site visit to look at the current DMSMS tool Appendix C data would not provide the level of information as stated in this question. The USAF is only providing Appendix B data so all the Appendix C data will be missing. So the actual level of effort is really as simple as researching, collecting and populating each part number with the data required per Appendix C.

9.Q. Does the USAF have a process to detect, validate and correct bad data during the initial migration data loading process?

A. The USAF will be providing all the Appendix B data in flat file format to the contractor on

CD ROMs. The data is in the same format as the sample data posted to FBO during the Sources Sought Synopsis. The USAF has no process to use during the data loading.

10.Q. Does the USAF have an idea of the actual tracked items out of the 26M items?

A. The USAF has provided a draft Performance Work Statement (PWS) that details the requirement for this effort. Based on their tools capability and the PWS requirements, the USAF would expect contractors to propose the level of component tracking they have the ability to provide. The USAF does not know what components map to industry subscription filters.

11.Q. How many of the 26 million parts are unique vendor parts (since a part may be used in multiple locations on many platforms)? A part may be used in multiple locations on many platforms. That unique part only needs to get its status information one time for the many locations it resides in. It is important for any potential bidder to understand the actual count of unique vendor parts involved in order to provide a viable solution to meet the Air Force’s DMSMS needs.

A. The USAF would refer industry to the charts provided at Industry Day 1-2 Nov 2016. The specific chart titled Appendix C: Contractor-Supplied Part Data. This chart estimates approximately 6.65M records will be populated with Appendix C data.

12.Q. On unique parts, what percentage of those items are COTS, Electronics, Mechanical, and Non-Tracked items?

A. The USAF has limited rights to the Appendix C data. However, based upon the data load history and focus of the USAF to address electrical and electronic type parts, the majority of the parts requiring status are electrical and electronic.

13.Q. What is the definition of each Contractor Supplied Data Field and where is this data pulled from?

A. The USAF has limited rights to the Appendix C data. The USAF has no knowledge of where the Appendix C data can be pulled from.

The Appendix C data fields are common throughout the obsolescence industry, the following may assist for clarification.

1. Part Number Type- What type of part is the item (Electrical, Electronic, Mechanical)

2. Item Standardization Code (ISC)- This is a DLA code

3. Flag Status- This is the status of the item (Typically a red/yellow/green)

4. Manufacturer- no explanation needed

5. Manufacturer CAGE (MFG CAGE)- Common Government identifier

6. Manufacturer Part Number (MFGPN)- no explanation needed

7. STATUS- This corresponds with 5&6, it is whether the manufacture of item is still active/inactive

8. LOT DATE- Date manufacturer is going to stop producing part; LOT=Life of Type

9. Lead Time- Manufacturing lead time

10. Generic- Refers to base manufacturing part number identifying if there is a generic build from

11. Package- Electronic part terminology. Electronic parts are associated with a package

12. Pins- Electronic part terminology. # of pins on the part if applicable

13. QGRADE- the minimum and maximum operating temperature of a part

14. Website URL- Link to Manufacturers website

15. Not recommended for New Design (NRND)- Yes or No; Based upon analysis performed

16. Description- item description

17. Function- Function of the part

18. Technology- Items 18 thru 26 are standard electronic family identifiers

19. Class- Items 18 thru 26 are standard electronic family identifiers

20. Family- Items 18 thru 26 are standard electronic family identifiers

21. Type- Items 18 thru 26 are standard electronic family identifiers

22. Group- Items 18 thru 26 are standard electronic family identifiers

23. Org- Items 18 thru 26 are standard electronic family identifiers

24. Capacity- Items 18 thru 26 are standard electronic family identifiers

25. Program- Items 18 thru 26 are standard electronic family identifiers

26. Category- Items 18 thru 26 are standard electronic family identifiers

27. Generic Package Pin Alternates (GPP Alternates)- Form/Fit/Function equivalent parts

28. Generic Alternates- These are a step down from GPP alternates

29. Aftermarket- Separate list of potential sources

30. Datasheet- Specification

31. Part Discontinuance Notice (PDN)- Notice from Manufacturer

32. Part Change Notice (PCN)- Notice from Manufacturer

33. GIDEP- Alerts and Notices from GIDEP associated with the part

34. DMSMS Notices COTS- Additional communication of obsolescence from Industry

35. Market Survey Business- Manual analysis performed by tool provider

36. Case Analysis Alerts- Notification process within the tool to identify obsolescence

37. Health Analysis- Product developed within the tool to provide health analysis on item or system

14.Q. Would it be possible to provide potential bidders with a sample of real appendix C data for a couple of parts, preferably for a COTs part, Electronic part, and Mechanical part?

A. The USAF has limited rights to the Appendix C data. The USAF cannot distribute Appendix C data outside of the licensing agreement.

15.Q. Can you provide information on C&A and ATO?

A. Reference information:

DoDI 8500.01 March 14, 2014

DoDI 8510.01 May 24, 2016

AFI17-101 October 28, 2016(formerly AFI33-210)

16.Q. What is the amount of error data collected within the government source documentation?

A. A sample year has approximately 50,000 errors in data.

17.Q. Does back-up system requirement require single access?

A. Yes 18.Q. Is some of Appendix C data on mechanical items?

A. Yes