FA8770-RFI-18-IMLCI.pdf

DEPARTMENT OF THE AIR FORCE

BUSINESS AND ENTERPRISE SYSTEMS DIRECTORATE

WRIGHT-PATTERSON AIR FORCE BASE OHIO

REQUEST FOR INFORMATION (RFI)

FA8770-RFI-18-IMLCI

A. Synopsis

This is an RFI to gather information about industry’s capabilities to provide Information Technology (IT) Services for the Item Master Logistics Capability Initiative (IMLCI) for the Business and Enterprise Systems Directorate of the Air Force Life Cycle Management Center (AFLCMC/HIQ). There is no solicitation available at this time. Requests for a solicitation will not receive a response. This RFI is for planning purposes only and shall not be considered as an invitation for bid, request for quotation, request for proposal, or as an obligation on the part of the Government to acquire any products or services. Your response to this RFI will be treated as information only. No entitlement to payment of direct or indirect costs or charges by the Government will arise as a result of contractor submission of responses to this announcement or the Government use of such information. No funds have been authorized, appropriated, or received for this effort. The information provided may be used by the Air Force in developing its acquisition strategy and enhancing the requirement specifications. Interested parties are responsible for adequately marking proprietary or competition sensitive information contained in their response. Do not submit any classified information in response to this RFI. The Government reserves the right to contact the submitting parties, on an as required basis, for further clarification on material provided. The Government reserves the right to contact additional customers to obtain information that will be used to evaluate the offeror’s capability.

The Government does not plan to respond or conduct formal debriefings to vendors as part of this RFI.

B. Introduction

This announcement is being issued to garner information only at this time. The purpose of submissions is to identify potential project-level performers that may have promising technologies relative to the IMLCI Threads described later in this RFI. Following the Government’s review of the submissions, the government may request proposals utilizing an Other Transaction Authority (OTA) or traditional FAR-based contract vehicle.

Notionally, the Air Force is considering making multiple prototype awards (two or more) totaling approximately $3M (i.e. two awards will made for $1.5M each) for 6-8 months of prototype development.

C. Overview

The United States Air Force may choose to acquire a commercial off the shelf (COTS) solution(s) with expansion capability to provide comprehensive Item Catalog and Provisioning functions for the Air Force Logistics business community. The solution must interoperate and

FA8770-RFI-18-IMLCI

26 Mar 2018 interface with other legacy and modernized Air Force and DoD systems. It must be capable of utilizing diverse data that may require protection under security and/or privacy laws and regulations. The solution should have the ability to authenticate and perform role-based authorization in response to dynamic policies and emergent conditions. Likewise, the solution must be capable of being assessed and authorized under the Risk Management Framework at a (Moderate, Moderate, and Moderate) level as described in Reference A.

D. Background

The Air Force is exploring the use of COTS software to replace many decades-old core logistics enterprise systems. To accelerate this change, the AF has split the Enterprise Logistics business area into separate capability initiatives (CIs), and has worked solution exploration of each CI separately. It has been recognized that Item data is a core underlying need for each CI, and as such will integrate with many logistics enterprise systems. The IMLCI is targeted to provide comprehensive Item Catalog and Provisioning functions for the Logistics business systems, and will replace the Item Management Control System (IMCS) suite of legacy systems, at a minimum. IMLCI will be the central repository for the Item core business objects, providing standardization of Item cataloging processes, structure, attributes, propagation, and standardized views for all applicable Item types. Additionally, IMLCI will receive product structure input from an engineering PLM type system.

The Item Management Control System (IMCS) suite of systems is the official authoritative source of all AF-used and/or managed items of supply. The suite of systems provide the following major functions: maintains and distributes logistics management information on all Air Force-used and Air Force-managed items of supply, acts as the central repository of Federal and Air Force logistics data for all Air Force-used and Air Force-managed items of supply, performs as the entry point for new items of supply and is the Air Force interface to the Federal Catalog System.

E. Requirements/IMLCI Potential Design

The Air Force wants to rapidly modernize its enterprise logistics systems, most of which require Item data. The new IMLCI should provide essential functionality of the legacy IMCS more efficiently and effectively in addition to implementing new functionality as described below.

The Air Force desires to employ industry leading existing COTS capabilities, configured to provide the needed functionality with minimal development to achieve an acceptable initial capability in the very near term. Air Force intends to perform sustainment with organic and/or contractor resources modifying configuration and/or adding development in compliance with future upgrades, patches, and/or pushes.

The response should describe an Item Master Logistics Capability Initiative (IMLCI) system solution architecture, supporting all logistics enterprise systems, including legacy and future state of CIs using COTS software. Potential design must emphasize COTS tools (i.e. software), and depict modern data management practices for capturing and implementing the business rules of an authoritative repository of Item data. Potential design must also address the need to provide this data to other logistics systems, including the conversion or transformation of Item data between record formats. Vendor responses should address how their solution will implement the functional capabilities (e.g., configuration, development, etc.) described in Attachment A of this

RFI.

F. References

A. NIST Special Publication 800-37 Rev. 1 (Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach)

B. AFMCMAN 23-3 (Cataloging and Standardization) C. Mission Process Map – Item Master D. Model – Manage Item Master – Execute Provisioning E. Model – Manage Item Master – Assistance Request F. Model – Manage Item Master – Assign Management Information to IM AR Line Item G. Model – Manage Item Master H. Model – Manage Item Master – Manage Federal Catalog Action

Term Definition Assistance Request

A data set that allows a user to submit a request for Item Master assistance.

The Assistance Request contains detailed information, to include the request types(s), priority, and contact information of the originator(s). Requests can be for information access to an item, creation of a new item record or update to an existing item record. ARs will include detailed responses, Cognizant Authority (CA) approvals (if appropriate), and Item Master Lifecycle Management team contact information. This information asset contains the information to support the assistance request. Line item requests contain information such as why the request is necessary and include descriptive details about the item in question (e.g., Part Number/CAGE Codes, Technical Order (TO) references, quantity unit pack details, descriptive data). Line item responses contain cataloging actions taken as well as status.

Catalog A collection of Items, typically a listing of all Items used by an enterprise.

Cataloging The activity of managing Item data records within an enterprise.

Cognizant item authority

A user/role within the Item Management capability who has authority to maintain item attributes associated to an item type.

End Item A final combination of end products, component parts, and/or materials that is ready for its intended use, e.g., ship, tank, mobile machine shop, or aircraft. The listing of the collection of items in an End Item is called a Master Configuration, or a Configuration Bill of Material.

Inventory (data object)

An instance of an Item. The Inventory data object has the attributes that define the countable instance of Items, such as location, count, unique instance identifiers (like IUID, Serial numbers).

Item (data object)

A distinct object defined by form, fit and function. The Item data object has the attributes of an Item in the abstract, identifying characteristics, descriptors, and information. Item data does not include Inventory information – location, count, unique instance identifiers (like IUID, Serial

Term Definition numbers) of physical Items. Items can be collections of other items, which are listed in a Bill of Material.

Item Type An aggregation of data elements and business rules specific to the type of item. This could include Vendor, Customer, Product Structure, Munitions etc.

Provisioning A set of actions taken to facilitate the best selection, procurement, and cataloging of items of supply required to sustain weapons systems and other government requirements (e.g., technical data validation, data calls, provisioning, guidance conferences, Logistics Support Analysis conferences, etc.)

Product Structure

A data set used to identify the hierarchical decomposition of a product, typically known as the bill of materials (BOM). It is a representation of the way in which the parts of a product fit together and interact, organized in levels of detail based on structure.

G. Due Date:

Responses to this RFI should be submitted via email by 4:00 PM EST 13 Apr 2018 to Charlotte Perry, Contracting Officer, at charlotte.perry@us.af.mil. Late responses may not be reviewed. Responses should be submitted in accordance with Paragraph K below.

Respondents who submit proprietary data shall clearly mark the data with appropriate markings.

Any questions should be submitted via email to the Contracting Officer, Charlotte Perry, at charlotte.perry@us.af.mil. The Government does not intend to award a contract on the basis of this RFI. A determination not to compete this action based on responses received is solely within the discretion of the Government. Responses to the RFI will not be returned. Please note that all prospective contractors must be registered in the System for Award Management (SAM) database, formerly the Central Contractor Registration (CCR), to be awarded a Department of Defense contract. To learn more about this SAM requirement and how to register, please visit the SAM internet website at http://www.sam.gov/ or call 1-866-606-8220.

In accordance with AFFARS 5352.201-9101, an Ombudsman has been appointed for this acquisition. The Ombudsman does not diminish the authority of the Program Director or Contracting Officer, but communicates contractor concerns, issues, disagreements, and recommendations to the appropriate Government official. When requested, the Ombudsman shall maintain strict confidentiality as to the source of the concern. The Ombudsman does not participate in the evaluation of proposals or in the source selection process. The Ombudsman should be contacted only with issues or problems that have been brought previously to the attention of the Program Manager and/or Contracting Officer and could not be resolved satisfactorily at that level. The AFLCMC Business and Enterprise Systems Ombudsman can be contacted at:

Lt Col Peter A. Sandness, Deputy Director, USAF AFLCMC/AQ-AZ 2640 Loop Road West Wright-Patterson AFB, OH 45433

Phone: 937-255-5512 Email: peter.sandness@us.af.mil

H. Data Rights

1. Describe the data rights of the potential solutions provided. Note: Unlimited Rights Preferred / Government Purpose Rights Acceptable

2. Describe the potential of an Enterprise license for use of COTS software including license for software development kits necessary to execute lifecycle configuration updates.

I. Estimated Travel

No travel is anticipated for the RFI portion of this initiative.

J. Deliverables

There are no deliverables required for the RFI, however potential deliverables should be outlined in the RFI response.

K. Content and Format:

Offerors are required to electronically submit a not-to-exceed 15 page response summarizing their proposed approach/solution. The response shall be formatted as follows:

a. Section A: Title, Notional Period of Performance, Name/Address of Company, CAGE Code, DUNS Number, NAICS code(s), Technical and Administrative Points of Contact (phone , email, and available contract vehicles), and a website address (if applicable) that provides additional information about the prospective business. Please note that this section is NOT included in the page count.

b. Section B: Task Objective and Capabilities

Offerors shall ensure the following unique items are fully addressed in their response submission(s).

1. Describe your organization’s ability to meet the technical requirements set forth in RFI

Attachment A, IMLCI Mission Capabilities Description. Please do not simply restate the technical requirements in your response. Be sure to identify any areas which likely would require subcontracting or a teaming arrangement. Clearly describe, with reference to the technical requirements, the division of effort between the primary performer and anticipated team members.

2. Please describe your proposed approach. Note that US Air Force has strong preference to compose capability with COTS building blocks. Hence, to the extent it is relevant, summarize your approach in terms of how you would:

a. Identify baseline COTS capability

b. Identify gap between existing COTS and total requirement

c. Identify how to rapidly configure and deploy COTS-based aspects of solution

d. Identify how to add new functionality, transition it as COTS, and connect it to COTS-baseline

e. Identify how to conduct continuous lifecycle tech refresh

3. Given the above, describe how you would develop the IMLCI Mission Thread prototype to demonstrate your solution’s off-the-shelf capabilities and explain any projected or needed customization. Please highlight proposed changes to Air Force IMLCI Mission Capabilities.

4. Describe the experience and qualifications of personnel and other organizational resources that would be used to meet the technical requirements. Provide information describing the level of knowledge and capabilities in the applicable domain.

5. Indicate any factors concerning your organization’s ability to perform the technical requirements.

6. Indicate if your organization is considered a traditional or non-traditional Government contractor according to Section D1.11 of the Department of Defense Other Transactions Guide for Prototype Projects dated January 2017, and in Article 1.041 of Agreement No.

FA8750-16-9-9000. If submitting as a traditional Government contractor, please indicate if the organization will be including significant participation from a non-traditional contractor or a one-third cost share as outlined in Section C1.2 of the Department of Defense Other Transactions Guide for Prototype Projects dated January 2017.

7. Please identify products and services by name and hyperlink reference to ordering procedures, license, feature descriptions, lifecycle cost, tech refresh process, etc. if your approach includes use of, or modifications to, your own existing COTS products and services.

8. Please specify any existing government procurement vehicles through which your labor and/or COTS offering(s) described above may be obtained.

9. Please specify any current and past cyber security or authorizations, certifications, or accreditations associated with your COTS offering(s) identified above.

10. Please explain how you think the Air Force should validate, verify, and certify your solution for performance against the Air Force’s stated IMLCI Mission Capabilities.

11. Please explain how your company will comply with all security clearance requirements specified in RFI Attachment A.

12. If members of your team have performed successfully on recent, relevant projects (government sponsored or otherwise) please concisely describe performance on no more than three of those projects. For each project description, in 400 words or less, include:

a. Performing company(ies) name(s)

b. Project name and period of performance

c. Name and contact information for a sponsoring official who can verify your contribution

d. Performing company(ies) role in the project

e. Relevance

f. Hyperlinks to more detail (optional)

L. Organizational Conflict Of Interest:

Organizational Conflict of Interest (OCI) as defined and discussed in FAR 9.5, Organizational and Consultant Conflicts of Interest, is a concern in all acquisitions across the Department of Defense.

Interested vendors are requested to evaluate your potential OCI issues with regard to this requirement for IT services for IMLCI, and the Contractor is encouraged to identify any OCI issues, as stated in FAR 9.5 to the Contracting Officer (CO). This will assist the CO in determining if the contractor will need to submit an OCI Mitigation Plan for any solicitation that might result from this notice.

M. Attachment: IMLCI Mission Capabilities (RFI Attachment A)

N. Questions:

Questions about this RFI should be submitted via email to Charlotte Perry, Contracting Officer, at charlotte.perry@us.af.mil. Questions received after 4:00 PM EST 13 Apr 2018 may not be answered.

O. Summary:

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY to gather information about industry’s capabilities to provide Information Technology Services for the Item Master Logistics Capability Initiative. The information provided in the RFI is subject to change and is not binding on the Government. The Air Force has not committed to a procurement, and this RFI should not be considered a commitment or authorization to incur cost or as a basis to seek reimbursement for any costs. Submissions become Government property and will not be returned.

ATTACHMENT A

Required Capabilities

Capability 1: Item Standardization and Item Configuration Management: This capability provides AF Logistics Enterprise with a standard, repeatable item cataloging process, item content development, and configuration management of the item data through enhanced business rule development and policy changes that is facilitated by a central Item Master organization.

This includes two sub-capabilities: 1.1) Item Standardization 1.2) Item Configuration

Management.

Sub-Capability 1.1: Item Standardization: This sub-capability provides the standardization and transformation of Item cataloging processes, structure, and content for all applicable Item types.

Item Types include but are not limited to: National Stock Number (NSN), Bill of Material

(BOM), Logistics Bill of Material (LBOM), Foreign Military Sales (FMS), Non-definitive (ND), Kit, Software, etc. Additionally, this expands the total number of records used in sustainment to include the non-stocklisted/non-cataloged items required for a specified level for repair and capacity to include all future acquisition items.

Item standardization provides a single repeatable process for Item Cataloging through enhanced business rules and policy changes, providing enterprise visibility of an estimated 4.8 billion dollars in locally managed inventory tracked through 260+ instances of Standard Base Supply

System (SBSS). Enterprise visibility enhances demand forecasting, allows for potential economies of scale purchasing, and enables total asset visibility.

Sub-Capability 1.2: Item Configuration Management: This sub-capability maintains consistency of item product structure, attributes, and propagation through a single organization comprised of logistics enterprise experts. A controlled and reliable data record increases accuracy, decreases duplication, ensures coordination among all stakeholders, provides standard views and attributes, and establishes consistency. Item Master provides knowledge of item and relationships to assets/product structures, associates documents, and manages necessary changes to all AF Logistics stakeholders.

Capability 2: Item Authoritative Source: This capability will provide a single authoritative source, enterprise release, and enterprise acceptance for all Item information also enhancing the item record, its associated product structure, and its required attributes to support the AF logistics business process re-engineering. Currently, each community maintains their own authoritative

Attachment A source for Item leading to duplication of Item records; data discrepancies; costly interfaces; lack of coordination, integration, and configuration management; multiple exchanges with external agencies; and excessive manpower requirements to facilitate reconciliation of duplicative data which leads to the inability to share coordinated Item structures across the AF Logistics

Enterprise. Furthermore, inaccurate cost reporting prevents DoD mandated FIAR compliance.

Enhancing the item record consolidates ILM attributes into an authoritative item record. The enhancement and creation of a complete item record becomes the authoritative source for all logistics activities. This will include changes and improvements to item content, classification and business rules; while providing capability and flexibility to support future Item requirements and types. ILM attributes includes information from, but not limited to, supply, financial, technical, transportation, maintenance, and vendor communities.

Capability Details:

A. Item Master Authoritative Data Source

The IMLCI system(s) will be the Authoritative data source of Item business data objects for the logistics enterprise. (Definitions of Item and Item TYPES are in the References section of the

RFI)

Establish item standard constructs (Item Type), defining attributes and business rules within enterprise logistics

Central repository for all Item Types (e.g., Stock-listed Part, Non-Stock-listed Part, Foreign Military Sales (FMS), Non-definitive (ND), Kit, Software, etc.)

Establishment of a single AF Item Master data repository for Items, replacing the Item Management Control System (IMCS) suite of systems (the focus of IMCS is Stock-listed Items)

Establishment of centralized Item control through Role Based ownership by cognizant authorities for AF managed and utilized items, with clear assignment of roles for Item Master Management with controlled accessibility, authorization, and ownership for Item data

Generation and standardization of Item data content and structures that will enable other enterprise logistics activities such as Equipment Management, Stock/Inventory Control, and Maintenance Programs

B. Cataloging

Cataloging actions include naming, classifying, describing, and numbering items. It also includes the maintenance and dissemination of that information. AF cataloging operations are conducted within the framework of the Federal Catalog Program (FCP). Cataloging of new items and maintenance transactions of existing items results in the comprehensive logistics data Total Item

Record (TIR) required to identify, requisition, ship, store, dispose, or make other logistics decisions related to an item of supply during its lifecycle.

Examine potential items for inclusion in the FCP, known as Item Entry Control (IEC), by screening the part number (PN) of the candidate item with existing items to see if a previously existing item can be used in its place

Request and manage National Stock Number assigned to AF management Maintain TIR data required to identify, requisition, ship, store, dispose, or make other logistics decisions Manage interchangeability and substitutability rules, coordinating with responsible parties Validation of technical data in TIR for purposes of Item Name assignment, Federal

Supply Class (FSC) determination, IEC, special characteristics, and the item identification (II)

See AFMCMAN 23-3 14 Sep 2010 (reference H) for description of Cataloging in IMCS operations. Note: where they differ, the Mission Process Maps overrule the

AFMCMAN 23-3

C. Provisioning

Provisioning are the actions taken to facilitate the best selection, procurement, and cataloging of items of supply required to sustain weapons systems and other government requirements (e.g., technical data validation, data calls, provisioning, guidance conferences, Logistics Support Analysis conferences, etc.). See AFMCMAN 23-3 14 Sep 2010 (Reference H) for description of Provisioning in IMCS operations

D. Item Expansion

Expansion of centralized repository by incorporating non-cataloged Items.

Enabling visibility across the Enterprise to allow resolving duplicates of locally defined items in the Supply systems o Potential long-term solution may subsume multiple Air Force Logistics/Supply systems Support of Item Types not currently treated as Items in AF enterprise logistics systems, which could be handled as Items in COTS (e.g. vendors, customers, product structures)

E. Integration and Interoperability

The solution must be easily and quickly integratable and interoperable with external systems (such as Federal Logistics Information System (FLIS), other legacy systems and/or new AF logistics systems), software infrastructure, databases, and content repositories. This should include the following:

Feature an open interface to export information to structured external data sources Be readily configurable to exchange data with both legacy and modernized applications

Support Air Force data transfer constructs and tools such as the Enterprise Service Bus (ESB), Secure File Gateway (SFG), and/or other secure transfers

F. Workflow/Assistance Request

The solution must provide comprehensive, robust, role-based, collaborative, and user configurable workflows for Item data record maintenance. The solution must enforce data quality and management rules, routing, and logging of approval by cognizant authorities of item records.

Search across all data in the system with onscreen filtering and sorting Grant access to various users based on their role and cognizant authority grouping Development of standard requests, action plans, templates, and notifications, applied by

Item Type Documentation of a decision tree, process and organizational flow charts, and business rules to determine Assistance Request paths, applied by Item Type Segmentation/grouping of Item records into management groupings for limitation of search or filters, and for the application of business rules, flows, and approvals Historical record retention Ability to collaborate from within the solution

G. Technical (Security and Infrastructure)

The solution must include a robust security model to ensure access to entities (processes, data, etc.) within the solution is appropriately limited. Administrations of portions of the security model shall be able to be delegated to subordinate organizations while overall administration is maintained at the centralized, enterprise level. This should include the following:

Support for single sign-on with a Department of Defense (DoD) Common Access Card (CAC) authentication

Provide accessibility across platforms to include Air Force standard desktop clients and mobile devices

Have a non-proprietary open database architecture which allows developers and external applications to directly interact with and modify the database and associated data

Support both on premise and/or cloud implementations and be certifiable and operable on the Sensitive-but-Unclassified (SBU) Air Force Network (AFNET) or accessible via the AFNET at an Impact Level 4 (IL4). For more information:

https://iase.disa.mil/cloud_security/cloudsrg/Pages/ImpactLevels.aspx

H. Lifecycle Support

The solution must offer an environment and an integrated business rule engine for accelerating development and maintenance of the Item data objects. The solution should also provide a solution that is sustainable for future upgrades and modifications. This should include the following:

Test, simulate, and analyze updates to applications and process models, and manage internal application and process libraries

Generate updated system documentation for ongoing application development and maintenance

Provide logging, monitoring and other management capabilities to support governance of the solution and infrastructure such as data model, interfaces, etc.

Maintainability – Solution will be configured to ensure that upgrades easily combine with Air Force development and customization. Vendor will provide all necessary patches and upgrades to keep the solution stable and secure. These patches/upgrades allow the Air Force to have exclusive control over application and installation

Deployability - Solution can be secured and meet necessary Risk Management Framework and software assurance controls/requirements at a (Moderate, Moderate, Moderate) level to gain accreditation and networthiness to operate on Air Force/DoD networks

Trainability - All user-facing technology in solution components must have training capabilities included that can be developed and/or maintained by the Air Force's organic/contractor skillsets

Usability - Solution will be usable with Air Force Standard Desktop, Group Policies and browser configuration constraints

Integratability – Solution components have been proven to integrate with all required functional components, Air Force database standards, internal legacy applications, and external system partners

Supportability (Platform Support) – Solution is sufficiently mature and at a stage in its support lifecycle wherein implementation will provide the Air Force with a reasonable expectation of long-term support from both the manufacturer and associated industry

Supportability (User Support) - User support (if applicable) is available on a schedule that meets both daily usage and surge support requirements as defined by the functional end user community (i.e. Air Force enterprise logistics systems, both existing legacy systems and future CIs)

Availability – Solution can support the maximum downtime, data loss and high availability requirements of the functional community

Scalability – Solution should employ "cloud like" platform elasticity to increase and decrease computing resources in scale, as required

NOTE: The following two reference documents are provided in separate files.

FA8770‐RFI‐18‐IMLCI Reference A NIST SP 800‐37 rev 1

FA8770‐RFI‐18‐IMLCI Reference B AFMCMAN23‐3 14 SEP 2010

Item Master ATP 3 Mission Process Map TO-BE (high level) H ig h

-l ev el M is si on P ro ce ss

2/9/2018

Manage Item Master assistance request

Manage Item Master

Assign management information to IM

AR Line Item

Manage federal catalog action

Execute Provisioning

FA8770-RFI-18-IMLCI Ref C) PM - Mission Process Map - Item Master

Execute provisioning (To Be) Pr od uc t Su pp o rt

En gi n ee ri ng Pr im e

Pr ov is io n in g O ff ic e

It e m M a st e r

R ol e

P ro g ra m O ff ic e (A cq u is it io n an d

/o r

Su st ai nm en t)

D

LA

C on tr ac ti ng th

PP

CO

O

EM

Subject to A4PT and Item Master SME approval

Coordinate PLISN review with DLA to validate tech data

PLISN

When: Data is in correct format

Provisioning data [Incorrect format] When: Data is not in correct format

PPL [Missing tech data] When: Tech data is incomplete (Need to request TO)

Execute PLISN review on complete

PPL

Perform data call to gather information

Build CDRL and

SOW

Complete acquisition documentation

CDRL, SOW

CDRL: Training & Engineering info, SOW: Training & Engineering info

Award contract

Hold Provisioning Guidance

Conference

Notification of contract award

Create POP Plan

Develop provisioning data

Provisioning data expectations

Provisioning data

Screen provisioning data

PPL [Complete] PPL [For screening]

Item information When: LR is not required

AND

When: PIO process is not required

Manage IM AR Item record

Non-AF LR Item information When: LR is required

FMS F-16 item information When: PIO process is required

Close out PLISN PLISN [Closed]

PLISN AF actions

Receive AF actions on PLISN

Collaborate on data call to gather information

Product support information

PO information

Execute logistics reassignment

Execute PIO process

Item information from LR

Item information from PIO process

Determine provisioning submission status

Close provisioning submission

Submission [Complete]

Programming checklist

Data call notification received Provisioning of Item is complete

FA8770-RFI-18-IMLCI Ref D) Manage Item Master - Execute Provisioning

Execute provisioning (As Is) od uc t Su pp o rt

PS

O

EM

E ng in ee ri ng Pr ov is io ni ng O ff ic e Pr og ra m O ff ic e (A cq u is it io n an d

/o r

Su st ai nm en t)

D

LA

O th er S er vi ce s

C on tr ac ti ng

D

IS

A

ES

/I M th

The OEM provides recommendations for LCSP

Deliver the LCSP and TDP via LSA-036

Load LSA-036 data

PPL

Coordinate PLISN review with DLA to validate tech data

Provisioning data [Loaded]

PPL [Annotated] When: Tech Data is complete

Provisioning data [Incorrect format] When: Data is not in correct format

PPL [Missing tech data] When: Tech data is incomplete (Need to request TO)

Send PPL to DLA for PLISN review to validate tech data on the content

Perform data call to gather information

Build CDRL and

SOW

Add training and engineering information

CDRL, SOW

CDRL, SOW

Review CDRL, SOW, and legal information Award contract

CDRL [Reviewed], SOW [Reviewed]

Set up Provisioning Guidance

Conference (includes contractor)

Notification of contract award

Create Provision Project List (aka

POP Plan) (includes PLISNs)

Develop provisioning data

Deliver provisioning data

Provisioning data expectations

Provisioning data

Provisioning data [Delivered]

This is where Item Master takes over (transformation) since AF can now directly load the LSA-036 data. No longer need to pay DISA for this and then perform QA on the load by DISA ) We may be paying DISA for this load (need to confirm). If so, this may be a cost saving feature in addition to an efficiency savings

Receive provisioning data from contractor

Provisioning data [Received]

Screen provisioning data for NSNs, AAC, etc (provisioning office)

Process NSN request

(cataloging office)

PPL [Complete]

PPL [For screening] When: Data is in correct format

Receive complete

PPL

Review PPL in preparation for SPC

PPL [For Review]

Conduct SPC document review

(by hand)

PPL [Reviewed]

Today, the review is a 2 week process that is done prior to a formal Spares Provisioning Conference. By using Item Master, the review and SPC can be done in real time since users can review each PLISN individually within the system. The work is still done, just more efficiently due to the collaborative environment.

Today, we want for the entire document to come back in order to review it in entirety.

Tomorrow, we want to look at the data line level (PLISN).

Review tech data results from DLA

Execute PLISN review on tech data Need to define complete PPL

Update system (D220) with SPC results

Catalog item for stock number

(D143C)

PPL [Loaded] When: DLA managed item or consumable

Build SSR for stock number (D169)

Build JLC-19, JLC-17 for stock number (Other Services)

PPL [Loaded] When: AF managed item repairable

PPL [Loaded] When: Other service managed item repairable

Results are typed in by hand

Close out PLISN

NSNNSN

Record AF actions on PLISN

PLISN [Closed]

NSN request

NSN

Receive AF actions on PLISN

Collaborate on data call to gather information

Product support information

PO information

Need to capture all information added

Process NSN request

NSN request Send AF actions on PLISN to contractor (sent in LSA-036 or

PPL format per contract)

Execute LR (D075 is used as a work around)

Execute PIO process PPL [Loaded]

When: Item is F-16 FMS

PPL [Loaded] When: Logistics Reassignment to make AF PICA is required

NSN

NSN

Data call notification received

Provisioning of Item is complete

Execute provisioning (DRAFT) od uc t Su pp o rt

PS

O

EM

E ng in ee ri ng Pr ov is io ni ng O ff ic e P ro g ra m

O ff ic e

(A cq u is it io n an d /o r Su st ai nm en

t) D

LA

O th e r Se rv ic e s

C on tr ac ti ng

The OEM provides recommendations for LCSP

Deliver the LCSP and TDP via LSA-036

Load LSA-036 data into Item Master

PPL

Coordinate PLISN review with DLA to validate tech data

(Item Master)

Provisioning data [Correct format] When: Data is in correct format

PPL [Annotated] When: Tech Data is complete

Provisioning data [Incorrect format] When: Data is not in correct format

PPL [Missing tech data] When: Tech data is incomplete (Need to request TO)

Send PPL to DLA for PLISN review to validate tech data on the content

Execute PLISN review on from complete PPL

(Review and update in system)

Perform data call to gather information

Build CDRL, SOW

Add training, engineering information

CDRL, SOW

CDRL, SOW

Review CDRL, SOW, and legal information Award contract

CDRL [Reviewed], SOW [Reviewed]

Set up Provisioning Guidance

Conference (includes contractor)

Notification of contract award

Create Provision Project List (aka

POP Plan) (includes PLISNs)

Develop provisioning data

Deliver provisioning data

Provisioning data expectations

Provisioning data

Provisioning data [Delivered]

This is where Item Master takes over (transformation) since AF can now directly load the LSA-036 data. No longer need to pay DISA for this and then perform QA on the load by DISA ) We may be paying DISA for this load (need to confirm). If so, this may be a cost saving feature in addition to an efficiency savings

Receive provisioning data from contractor

Provisioning data [Received]

Screen provisioning data for NSNs, AAC, etc (provisioning office)

Process NSN request

(cataloging office)

PPL [Complete]PPL [For screening]

Receive complete PPL (now have foundation in Item Master to start working)

Review PPL in preparation for SPC

PPL [For Review] When: Traditional provisioning process is followed

Conduct SPC Document review

(by hand) PPL [Reviewed]

Today, the review is a 2 week process that is done prior to a formal Spares Provisioning Conference. By using Item Master, the review and SPC can be done in real time since users can review each PLISN individually within the system. The work is still done, just more efficiently due to the collaborative environment.

Today, we want for the entire document to come back in order to review it in entirety.

Tomorrow, we want to look at the data line level (PLISN).

Review tech data results from DLA

Execute PLISN review on tech data

Need to define complete

PPL

PLISN [For review] When: Item Master ability is utilized

Item information When: LR is not required

AND

When: PIO process is not required

Update system (D220) with SPC results

Request IM / ES to build a transaction for stock number

(D143C)

PPL [Loaded] When: DLA managed item or consumable

Request ES/IM to build SSR for stock number (D169)

Request IM/ES to build JLC-19, JLC-17 for stock number (Other Services)

PPL [Loaded] When: AF managed item repairable

PPL [Loaded] When: Other service managed item repairable

Submit request for Item Manager / ES to create AF number for Item

Results are typed in by hand

Manage IM AR

IM AR

When: AF managed repairable

OR

When: DLA managed item/consumable

Manage JLC-19, JLC- 17 process for stock number (Other Services)

Other Service coordination package When: other service manages repairable item

This may already be captured in IM models (Manage Federal Catalog Action). Need to confirm if the JLC is sent directly to DLA. If so, this is already captured. Need to talk to a rep from the 418th (Paul Hale).

Execute LR (D075 is used as a work around)

Execute PIO process Non-AF Item information

When: LR is required

FMS F-16 item information When: PIO process is required

Close out PLISN

NSN

NSN

NSN

Send AF actions on PLISN to contractor (sent in LSA-036 or

PPL format per contract)

PLISN [Closed]

NSN request

NSN

Receive AF actions on PLISN

This is done by DISA today

Perform data call to gather information

Product support information

PO information

Need to capture all information added

Is this still done by the provisioning office?

Is this still done by the provisioning office?

Process NSN request

NSN request

NSN request

Data call notification received

Provisioning of Item is complete

Item Master – IM.01 – Manage Item Master Assistance Request.vsd last modified: Wednesday, March 14, 2018

It em

M as te r

Tr ad in g

Pa rt ne r

B as ic I te m

M as te r

U se r It em M as te r R ol e

C og n iz an t

A u th o ri ty

D

LI

S En gi n ee ri ng Su pp ly

D ep o t

M x

Fi el d M x Pl an ni n g

N o n -A

F en ti ty

O

EM

Subject to A4PT and Item Master SME approval

Model Object Key

Process Description

This process model supports the creation, management, and closure of an Item Master

Assistance Request (IM AR). An IM AR allows for the configuration management and change control of Item Master product data. The IM AR is separated into IM AR Line Items for the appropriate follow-on work and is closed once all IM AR Line Items have been completed.

The IM AR process enables:

* Review of IM AR content

* Centralized and standardized Item management processes across the enterprise

* Comprehensive workflow capability with tracking, notification, and historical query

DOT_LPF-P

action unconditional resource flow conditional resource flow when: condition

Activity

MT###

M### measure point mission thread path

Role

Request Item Master assistance

Assign management information to IM

AR Line Item

Evaluate access request

Grant access to Item Master record

Determine IM AR completion status

Close IM AR

Send non-AF information through DLIS for AF item record

Send product lifecycle information

Send supply information

Send Depot Mx information

IM AR

Non-AF item information from DLIS

PLI

Supply information

Depot Mx information

IM AR Line Item: CA approval required When: Line Item requires CA approval

AND

When: Line Item is a request for item access

IM AR Line Item: CA approval not required When: Line Item does not require CA approval

AND

When: Line Item is a request for item record access

IM AR Line Item [Assigned] When: Line Item is a request for an Item record attribute update/create

AND

When: AF is PICA of Item

Manage Item Master

IM AR Line Item [Record access authorized]

IM AR Line Item: Unauthorized requestor When: Item Master customer is not unauthorized for Item record

IM AR Line Item: Authorized requestor When: Item Master customer is authorized for Item record

IM AR [Complete] Manage Federal Catalog Action

IM AR Line Item [Stocklisted]

IM AR Line Item: Federal catalog requirement [Assigned] When: Line Item is a request for an Item record attribute update

AND

When: AF is not PICA of Item

IM AR Line Item [Item record created] When: Item record does not require federal catalog action

IM AR Line Item [Cancelled] When: CA responses for IM AR Line Item are not in conflict

AND

When: Item record attribute does not have CA approval for change

Send Field Mx information

Field Mx information

Send planning information

Planning information

Item information

Item record

IM AR Line Item [Item record updated] When: Item record does not require federal catalog action

IM AR Line Item [Item record update pending] When: Item record requires federal catalog action

IM AR Line Item [Item record creation pending] When: Item record requires federal catalog action

Receive item information for product lifecycle work

Receive item information for supply work

Receive item information for Depot Mx work

Receive item information for Field Mx work

Receive item information for planning work

Item information: Planning

Item information: Field Mx

Item information: Depot Mx

Item information: Supply

Item information: PLI

Item information from LR

Item information from PIO process

Send non-AF update for AF item record

Non-AF item update

Send SERD information

SERD information

Receive item information for non-AF work

Receive item information for

OEM work

Item information: Non-AF

Item information: OEM start trigger end condition

Sending Process – Sending activity

Receiving Process – Receiving activity

Parent Process – Sending activity

Parent Process – Receiving activity

Item Master customer identifies need for Item Master assistance request (IM AR)

Item Master customer s IM AR has been completed

Execute provisioning – Execute PLISN review on complete PPL

Execute provisioning – Close out PLISN

Execute provisioning – Execute logistics reassignment

Execute provisioning – Execute PIO process

FA8770-RFI-18-IMLCI Ref E) Manage Item Master - Assistance Request

Item Master – IM.02 – Assign management information to IM AR Line Item.vsd last modified: Tuesday, March 13, 2018 em

M as te r

T ra d in g P a rt n e r

It em

M as te r

R ol e D

LI

S

C og n iz an t

A u th o ri ty

B as ic I te m

M as te r U se r

Subject to A4PT and Item Master SME approval

Model Object Key

Process Description

This process supports the review and evaluation of the Item Master Assistance Request (IM AR) Line Item. AF Item Record access requests that do not require authorization or have been preauthorized are staged for AF Item Record implementation, while all other AF Item Record access requests are submitted to the appropriate Cognizant Authority (CA) for approval. IM AR Line Items for actions other than access are staged for support by an assigned ILM Team. This assignment identifies the owning catalog management team and is used for routing. IM AR Line Items for new Item records are reviewed against the AF Item Master and Federal catalog for Like Items (Items with similar form/fit/function). Like Item selection is confirmed with both the Cognizant Authority and requestor of the Item Master Assistance Request. This process determines the Item Master response time based on predetermined business rules of the task.

The management information assignment process enables:

Centralized and standardized Item management processes across the enterprise Prevention of duplicative AF Item Records

Identification of Federal Cataloging requirements

DOT_LPF-P

action unconditional resource flow conditional resource flow when: condition

Activity

MT###

M### measure point mission thread path

Role

IM AR

Look for Like Items in Federal catalog and AF Item Master

Search Federal catalog for Like Item

Federal catalog: Like Item request

Assemble information about

Like Items

Evaluate Like Item suitability

Select most suitable Like Item

Federal catalog:

Like Item response

Like Item result: CA review required

Like Item result: Suitable Like Item

Assign response time

Establish Federal catalog requirement

Review IM AR for number of IM AR

Line Items

Like Item result [Selected]

IM AR Line Item [Assigned] When: Line Item is a request for an Item record attribute update

AND

When: AF is PICA of Item

IM AR Line Item: Federal catalog requirement [Assigned] When: Line Item is a request for an Item record attribute update

AND

When: AF is not PICA of Item

IM AR Line Item: CA approval not required When: Line Item does not require CA approval

AND

When: Line Item is a request for item record access

IM AR Line Item: CA approval required When: Line Item requires CA approval

AND

When: Line Item is a request for item access

IM AR Line Item: New When: Line Item is a request for new AF Item record

AF Item Master: Like Item response

Determine if IM AR Line Item is request for Item record access, Item record update or new Item record

IM AR Line Item

Review Like Item selection

Like Item result: AF item When: Like Item selected by Basic User is in the AF Item Master

Like Item result [Reviewed] When: No suitable Like item found

OR

When: Like item that AF is not a user of found in Federal catalog

IM AR Line Item: Update When: Line Item is a request for an update to a new AF Item record

IM AR Line Item:

Federal catalog requirement

When: Line Item is a request for item record access start trigger end condition

Sending Process – Sending activity

Receiving Process – Receiving activity

Parent Process – Sending activity

Parent Process – Receiving activity

IM AR Line Item requires management data for processing

Manage Item Master – Request Item Master assistance

Manage Item Master Assistance Request – Manage Federal Catalog Action

Manage Item Master Assistance Request – Manage Item Master

IM AR Line Item management information assigned

FA8770-RFI-18-IMLCI Ref F) Assign Mgmt Info to IM AR Line Item

Item Master – IM.03 – Manage Item Master.vsd last modified: Tuesday, March 13, 2018 em

M as te r

It em

M a st er

R o le C og n iz an t A u th o ri ty

Subject to A4PT and Item Master SME approval

Model Object Key

Process Description

This process model supports the creation and update of AF Item Records within the AF Item Master as dictated by the Item Master Assistance Request (IM AR) Line Item.

The Item Master management process enables:

Review of the IM AR Line Item to disposition the appropriate follow-on activities Centralized and standardized Item management processes across the enterprise Establishment of an AF Item Master Identifier for Rapid and Routine Response create requests Assignment of AF Item Master attributes to the AF Item Record Coordination with Cognizant Authorities (CA) to update an AF Item Record Management of AF Item Records using discreet role and responsibility assignment

DOT_LPF-P

action unconditional resource flow conditional resource flow when: condition

Activity

MT###

M### measure point mission thread path

Role

Prioritize IM AR Line Item based on response time

IM AR Line Item: Create record When: IM AR Line Item requires a new Item record

Determine need for additional approval for attribute change

Request approval for attribute change

Determine if attribute may be changed

Resolve disputed attribute change request

Evaluate disposition among CA(s)

Update AF item record

Create AF item record

IM AR Line Item: Attribute update When: IM AR Line Item requires an update to an existing Item record

IM AR Line Item: CA signature required When: Item record attribute is missing CA approval for change

IM AR Line Item: Attribute authorization request

IM AR Line Item: Attribute authorization response

IM AR Line Item [Negotiation] When: CA responses for IM AR Line Item are in conflict

IM AR Line Item [CA conflict resolved]

IM AR Line Item [CA approved] When: CA responses for IM AR Line Item are not in conflict

AND

When: Item record attribute has CA approval for change

IM AR Line Item: No additional CA…