FSD-STORES2-ICCs-Draft1.pdf

FEDMALL STORES 2.0 ITEM CLASSIFICATION CODES

Functional Specification Title: FedMall STORES 2.0 ITEM CLASSIFICATION CODES (ICC)

Team: FedMall PMO, STORES 2.0 Implementation Team, STORES PMO, DLA Subsistence Team

Core Process: ServiceNow, FEDS, Commerce, DAAS, and EBS (external interface)

Application: FedMall/STORES 2.0

Associated Requirement:

Ownership and Signoffs

Name/Contact Date Version

Functional

Requirement Analyst:

Terryl Benson tbenson@part.net

FedMall Project

Requirement

Manager:

Adam Pepper

Adam.Pepper@dla.mil

FedMall

Configuration

Management Team:

Joe Taylor

Joseph.Taylor@dla.mil

Russell Zinke

Russell.Zinke@dla.mil

Customer Process

Owner:

Evan Newpher-Lockard

DLA Troop Support - Subsistence

Commodity Support Liason – Lead

Evan.Newpher-Lockard@dla.mil

Customer

Requirement POC:

Kevin Burza

DLA Troop Support - Subsistence

Tech Quality/Cataloging Supervisor kevin.burza@dla.mil

FedMall Program

Manager:

James Mette

James.mette@dla.mil mailto:beleazer@part.net mailto:Joseph.Taylor@dla.mil mailto:Russell.Zinke@dla.mil mailto:James.mette@dla.mil was

ITEM CLASSISFICATION CODES (DRAFT) Functional Specification

FedMall STORES 2.0 Item Classification Codes

Functional Specification – DRAFT v1 ii

November 2023

Partnet Development

Team Owner(s):

Brian Polka

Tech/Architecture Lead brian.polka.ctr@dla.mil

Andrew Hayes

Software Engineering Lead andrew.b.hays.ctr@dla.mil

Leigh Hibner

UI/UX Lead leigh.hibner.ctr@dla.mil

Abraham Josiah

Testing Lead ajosiah@amyx.com

James Spak

Task Order PM jspak@amyx.com

FedMall Subject

Matter Experts

(SME):

Richard Campagna

Richard.Campagna@dla.mil iii

TABLE OF CONTENTS

1.0 INTRODUCTION

1.1 SUPPLEMENTAL REQUIREMENTS DOCUMENTATION

1.2 DOCUMENT SCOPE

2.0 ITEM CLASSIFICATION CODES

2.1 ICC DEFINITIONS AND ATTRIBUTES

3.0 ITEM CLASSIFICATION CODE MAINTENANCE

3.1 MAINTAINING ICCS

Functional Requirements

3.2 MAINTAINING ICC ATTRIBUTES

Functional Requirements

3.3 MAINTAINING ICC ASSOCIATIONS

Producer Price Index Distribution Fee Categories Functional Requirements

3.4 DEVELOPMENT TASKS

4.0 FOLLOW-UP

4.1 ISSUES AND IMPLEMENTATION CONSIDERATIONS

5.0 GLOSSARY OF TERMS

6.0 REVISION HISTORY

6.1 CHANGE HISTORY FOR CONTENT OF THIS FUNCTIONAL SPECIFICATION

6.2 VERSION OF FUNCTIONAL SPEC TEMPLATE (FOR CM USE ONLY)

7.0 REQUIREMENT – FUNCTIONAL SPECIFICATIN APPROVALS

7.1 DIGITAL SIGNATURE REQUIRED

iv

TABLE OF FIGURES

Figure 1: ICC Definitions, Levels and Attributes for Perishable Beef

Figure 2: Item Classification Code Maintenance

Figure 3: Maintaining ICC Attributes

Figure 4: Item Classification Code (ICC) Association

Figure 5: ICC Management - Master Stock Number Maintenance

1.0 INTRODUCTION

STORES (Subsistence Total Order and Receipt Electronic System) is the ordering hub for the

Defense Logistic Agency’s (DLA) Subsistence supply chain. Built, updated, and enhanced over the course of several decades to support Subsistence’s unique business requirements, STORES provides customers across the globe with 24/7 access to over 550 catalogs where they can order a variety of food and beverage items, including fresh produce, packaged and canned goods, MREs, and operational rations.

This Functional Specification captures requirements for the utilization of Item Classification

Codes in in STORES 2.0. These requirements will be a central point of reference in the design and solutioning of these capabilities. Functional requirements and use cases will be reflected in the implementation requirements (Epics and User Stories) that will provide the detailed design and acceptance criteria needed to develop the solution.

The Functional Specification will serve as an agreement between the implementation team

(FedMall, Partnet, Amyx) and the business stakeholders (STORES PMO, DLA Troop Support) where the implementation team agrees to provide the capabilities defined in the Functional

Specification and the client agrees to find the product satisfactory if it does. Finalizing the

Functional Specification will require continued collaboration and input from the STORES business and technical team members, FedMall PMO, and the FedMall implementation team

(Partnet and Amyx).

1.1 Supplemental Requirements Documentation

The following requirements documents are companion documents to the Functional

Specification:

• Catalog Management BRD

The Business Requirements Document (BRD) covered all functional areas associated with Catalog Management, including not only stock number management, but manufacturer maintenance, core catalog, and pricing and distribution fees. The purpose of the BRD is to provide stakeholders with a consolidated readout of all business requirements and learnings captured by the Integrated Product Team (IPT) during requirements discovery, including business requirements, opportunities to improve business processes in the future state system, and key learnings and notes captured in the working group sessions.

• Requirements Traceability Matrix (RTM)

The RTM is a spreadsheet that will ultimately contain all the functional requirement statements documented in this Specification. It will be used to ensure that the scope, implementation requirements (epics and user stories), and deliverables for STORES 2.0 remain “as is” when compared to the baseline requirements. Thus, it traces the deliverables in the final buildout back to the requirements agreed to in the Functional

Specification.

Once finalized, a requirement # or ID will be added to each requirement captured in the

Functional Specification. These requirements will form the basis of the RTM, which will be managed in a spreadsheet or Web-based application like JIRA or Confluence, that is better suited for capturing traceability linkages, status, and dependencies.

• Item Classification Code (ICC) Attributes

The DLA Subsistence Tech Quality team manages and maintains the approved list of ICC definitions and attributes currently used in STORES. These codes and associated attributes are detailed in the following companion spreadsheet to this Functional

Specification:

o ICCAttributes.xlsx

• Producer Price Index (PPI) Codes

STORES is updated each month with this latest PPI data for each supported commodity.

ICCs are used to associate PPI Commodity Codes with master stock number records. PPI

Commodity Codes currently supported in STORES are documented in the following companion spreadsheet to this Functional Specification:

o PPICommodityCodes.xlsx

1.2 Document Scope

This Functional Specification is intended to capture requirements statements, use cases, design considerations, and assumptions needed to design the STORES 2.0 solution for the application and management of Item Classification Codes and supported functions. This includes the following:

1) ICC Maintenance Utility

This module or utility is necessary to:

a. Maintain ICC Code Definitions, Attributes, and Values

b. Associate ICC Codes to PPI Codes and Distribution Fee Categories.

c. Associate ICC Codes with Master Stock Number Records.

Requirements and any resulting development tasks for an interface to ingest monthly PPI data from the Bureau of Labor Statistics will be documented in the STORES 2.0 Interfaces

Functional Specification.

2.0 ITEM CLASSIFICATION CODES

Item Classification Codes (ICCs) are one to five-character alphanumeric identifiers used to define and classify master stock number records based on a defined set of attributes and characteristics. ICCs are proprietary to DLA and allow items to be grouped based on shared characteristics so that similar items can be readily identified and utilized for analysis and reporting.

ICCs are also used to associate distribution fee categories and Producer Price Index (PPI) Codes to a master stock number record. ICCs are maintained by the DLA Tech Quality Team.

2.1 ICC Definitions and Attributes

An Item Classification Code can be defined at one of five levels (five being the highest and one being the lowest) depending on the level of definition required by the item. Each level provides another level of definition. Definitions applied to the ICC at a lower level are automatically inherited by subsequent levels of the ICC.

Figure 1 illustrates this concept. In this example, an item associated with a Level 2 ICC code

(P1) would only be identifiable as perishable, beef. Whereas if the item is associated with the

Level 5 code (P1211), then it would be identifiable as perishable, beef, diced, regular, less than

3/4 inch. Each level builds on the previous level and assigns an additional definition to the item of supply.

Figure 1: ICC Definitions, Levels and Attributes for Perishable Beef

In addition to the definition(s) being assigned by the code itself, more detailed attributes may be available to define and associate with the ICC. In the example shown in Figure 1, there are ten secondary attributes that can be defined for ICC P1211. In this example the attributes are only definable at level 5; although attributes may be available to assign at a lower level depending on the ICC. Attributes assigned at a lower level are inherited by higher level ICCs. A unique identifier (code) is associated with each attribute and value pair. For example, a code of “016E” tells the system that the PACKAGING TYPE for the item is “INDIVIDUALLY WRAPPED”.

There are currently 56 ICC attributes that can be defined and assigned to an item of supply depending on the type of item.

These attributes and values are defined in the following companion spreadsheet:

• ICCAttributes.xlsx

The following provides a summary description of ICC definitions and attributes.

ICC Definitions

Every level of an ICC (1-5) provides a definition. These definitions are tied to the code itself. Each level of an ICC (1-5) associates the item with an additional definition—meaning an item assigned a level 1 ICC is identifiable by only one definition (either PERISHABLE or SEMIPERISHABLE) while an item assigned a level 5 ICC will be identified by four additional definitions

(for example, PERISHABLE, BEEF, DICED, REGULAR, GREATER

THAN 1.5 INCH.

ICC Attributes

Attributes are additional characteristics available to be defined for an item.

For example, an attribute can be used to define how an item is supposed to be cooked or how an item is packaged. They allow additional details not available in the item description or inherent in the code itself to be associated with an item. These additional attributes allow the system to accurately determine similar items for the purposes of assigning PPI commodity codes and distribution fee categories—necessary to make the master stock numbers actionable for reporting and price evaluation purposes.

The attributes available to assign to a stock number depends on the ICC itself and the level at which it is defined. Attributes assigned to the ICC at a lower level (e.g., level 3) are automatically inherited by higher levels of the ICC

(e.g., levels 4 and 5). If Tech Quality sets an attribute as the Primary attribute, then that attribute will be applied to each item to which the ICC is assigned.

3.0 ITEM CLASSIFICATION CODE MAINTENANCE

ICCs are currently maintained and managed by the Tech Quality team. The current state system provides separate screens to perform the following tasks:

• Maintain ICCs

• Maintain ICC Attributes

• Maintain ICC Associations

3.1 Maintaining ICCs

The Item Classification Code Maintenance screen allows Tech Quality users to add, edit, and update ICCs.

Figure 2: Item Classification Code Maintenance

TQ uses the information provided in the product specification sheet and label when assigning an

ICC to a stock number record.

Functional Requirements

The following functional requirements for maintaining ICCs are based on requirements discovery and the current-state feature set.

Requirement # Requirement (The application shall…) Notes/Elaboration

Only allow Tech Quality users to maintain

(define, edit, delete) ICCs.

The ability to maintain ICCs is currently provided through the Maintain Item

Classification Code permission included with the Data Maintenance - Tech

Quality role.

Provide users with the following search options for looking up an ICC:

• Entering the ICC Code

• Entering all or part of the ICC description

System should provide incremental search (typeahead) when the user is entering a code or description.

Allow users to confine the search to a selected

ICC Level (1-5).

Default is All.

Display the following information for each ICC returned in the search results set:

• ICC

• Description

Display ICC descriptions so that the user can visually determine the level at which a particular description was applied to an

ICC (comma-separated in current state).

Allow user to navigate through pages of results.

(Conditional) If attributes are associated with the ICC, allow the user to view those attributes.

(Conditional) If ICC is Level 1-4, allow users to add a new ICC description.

REWRITE based on the fact that there might not be a Level 5 (look to see what the possibilities are here). Some end at level 3.

(Conditional) If ICC is not currently associated with a stock number, then allow user to enable or prevent the ICC from being assignable to a stock number record.

Scott to verify usage. (For example, can an ICC be assigned at level 2 if it is definable up to level 5.) Confirm if it is assignable at lower level if Assignable checkbox is marked. Depends on the level where the attributes are defined.

Allow users to edit an ICC description.

Allow users to assign attributes to the ICC as defined ins ICCAttributes.xlsx.

Attributes assigned to the ICC at a lower level should be inherited by the higher-level ICC. For example, if adding attributes to a Level 4 ICC, all the attributes associated to the Level 3 ICC in question will be inherited and remain associated with the ICC.

(Conditional) Allow user to mark an attribute as the Primary attribute if no primary attribute is assigned to the ICC at a higher level.

If an inherited attribute was identified as the Primary attribute for the ICC, then the user should be prevented from designating a different attribute as the primary.

Supported ICCs and attributes that can be defined for a stock number are detailed in the following companion document:

3.2 Maintaining ICC Attributes

The Item Classification Code Attribute Maintenance screen allows Tech Quality users to manage

(add, edit, delete) ICC attributes and values. This functionality is rarely used in STORES as ICC

Attributes in STORES are fully defined.

Figure 3: Maintaining ICC Attributes

Functional Requirements

The following functional requirements for maintaining ICC attributes and values are based on requirements discovery and the current-state implementation.

Requirement # Requirement (The application shall…) Notes/Elaboration

Support the creation/display of Attribute codes and associated values as detailed in the following companion spreadsheet:

o See Attributes-Values worksheet

Only allow Tech Quality users to manage (add, edit, delete) descriptions for ICC attributes and values.

The ability to maintain ICC attributes and values is currently provided through the

Maintain Item Classification Code permission included with the Data

Maintenance - Tech Quality role.

Provide users with the following search options for looking up an Attribute Code:

• Entering the Attribute Code

• Entering all or part of the Attribute description

System should provide incremental search (typeahead) when the user is entering a code or description.

Display the following information for each ICC returned in the search results set:

• Attribute Code

• Description

Allow users to edit an attribute code description. Document field-level validation based on format and character length.

Allow users to edit a value code description. Document field-level validation based on format and character length.

Supported ICCs and attributes that can be defined for a stock number are detailed in the following companion document:

3.3 Maintaining ICC Associations

In addition to providing additional levels of classification to an item, ICCs are used to associate stock numbers with distribution fee categories and to Producer Price Index (PPI) Commodity codes.

Figure 4: Item Classification Code (ICC) Association

Figure 5: ICC Management - Master Stock Number Maintenance

Producer Price Index

The Producer Price Index (PPI) is used to measure the average change over time in the prices domestic producers receive for their output. It is a measure of inflation at the wholesale level compiled from thousands of indexes measuring producer prices by industry and product category. The index is published monthly by the U.S. Bureau of Labor Statistics (BLS).

STORES is updated each month with this latest PPI data for each supported commodity. For

Subsistence to be able to use the PPI data to review prices or determine price trends, a PPI commodity code must be associated with each relevant stock number. PPI commodity codes are associated to items in STORES through the ICC. Once the association is made, the stock number is made available in the following ICC/PPI reports used by the DLA Subsistence team.

ICC/PPI Report Description

ICC Master Report

The ICC Master Report displays a snapshot of ICC data provides a snapshot of the PPI data contained in STORES and shows updates and/or changes made to the PPI tables during a specified date range based on input parameters chosen for

Codes, Code Descriptions, Attribute Codes/Values, and Attribute Code/Value

Descriptions.

ICC Associations Report

Displays the assigned relationships among ICCs, PPI Codes, Distribution Fee

Categories, and Stock Numbers based on input parameters chosen

Produce Price Index (PPI) Master

Report

Snapshot of the PPI data contained in STORES and shows updates and/or changes made to the PPI tables during a specified date range.

Table 1: ICC/PPI Reports

The requirements for importing and updating the system with monthly PPI data from the Bureau of Labor Statistics will be captured and documented in the STORES 2.0 External Interfaces

Specification.

Distribution Fee Categories

A Distribution Fee Category is a general type of item category (e.g., Dry Goods, Beef, Fruits and

Vegetables, etc.). Distribution fee categories are associated with stock number records so that the distribution fees charged by vendors of the item can be checked to ensure they are fair and reasonable.

Item Classification Codes are used by Tech Quality to associate Distribution Fee Categories with master stock number records. Distribution fee categories are assigned based on the vendor unit of measure. There is a one-to-one relationship between the distribution fee category and the unit of measure.

The functional requirements for managing distribution fee categories will be documented in the Distribution Fee Management Functional Specification.

Functional Requirements

The following functional requirements for maintaining ICC associations are based on requirements discovery and the current-state implementation of the feature set.

Requirement # Requirement (The application shall…) Notes/Elaboration

Only allow Tech Quality users to manage (add, edit, delete) ICC associations.

The ability to maintain ICC associations is currently provided through the

Maintain Item Classification Code permission included with the Data

Maintenance - Tech Quality role.

Allow users to associate an ICC with the following:

• Producer Price Index (PPI) Codes

• Distribution Fee Category

• Stock Number Record

When associating an ICC with a PPI or

Distribution Fee Category, allow user to look up an ICC based on ICC or Description.

Allow users to associate a PPI code with one or more ICC attribute values.

System should identify discontinued PPI codes.

Allow users to disassociate a PPI code from an

ICC attribute value.

Allow users to associate the following distribution fee category info with an ICC:

• Distribution Fee Category Source Code

• Distribution Fee Category and Description

• Distribution Fee Category UoM

Allow users to disassociate Distribution Fee

Category Information from ICC.

Allow users to look up master stock number by stock number or stock number description.

Allow user specify attribute values when associating ICC to a Stock Number Record.

Users should also be allowed to make the association in Master Stock Number

Maintenance. See Stock Number Maintenance

Functional Specification.

The system will allow Tech Quality Users to view ICC attributes and values associated with the stock number when viewing it in Master Stock Number

Maintenance.

See Stock Number Maintenance

Functional Specification.

Allow user to disassociate ICC from master stock number record.

3.4 Development Tasks

The following development tasks are anticipated for development of the MSNM pages and utilities.

Task Description System(s) Responsible Parties

Load Item

Classification

Codes (ICC) Data into STORES 2.0

Database

• Build STORES 2.0 database tables

• Populate STORES 2.0 database with ICCs, including definitions, descriptions, attributes, values, and levels.

• See ICCAttributes.xlsx to identify definitions, attributes, values, and assignment levels.

• ICC data is stored in the following current state database tables:

o ICC o ICC_ATTRIBUTE o ICC_ATTRIBUTE_CAT o ICC_ATTRIBUTE_VALUE o ICC_DIST_FEE

STORES 2.0

(FedMall Enclave)

STORES 2.0

Implementation Team

Load Producer

Price Index (PPI)

Data into

STORES 2.0

Database

• Build STORES 2.0 database tables for PPI data.

• Populate STORES 2.0 database with monthly PPI Data for development and testing purposes.

• See PPICommData.xlsx to identify PPI

Codes and Descriptions included in monthly import.

• The requirements for the interface to ingest monthly PPI data published by the Bureau of Labor Statistics is being captured and documented in the STORES 2.0 External

Interfaces Specification.

• ICC data is stored in the following current state database tables:

o PPI_CYCLE o PPI_DATA o PPI_DATA_DISCOUNT o PPI_DOWNLOAD_LOG o PPI_FOOTNOTE o PPI_GROUP o PPI_ITEM o PPI_ITEM_DISCOUNT o PPI_PERIOD

STORES 2.0

(FedMall Enclave)

STORES 2.0

Implementation Team o PPI_RAW_STAGE o PPI_RECODED

Populate

STORES 2.0

Database with

Distribution Fee

Category

Information

• Add STORES 2.0 database tables for managing Distribution Fee Category

Information.

• Populate database with distribution fee category data.

• Distribution Fee data is stored in the following current state database tables:

o DIST_FEE o DIST_FEE_CATEGORY o DIST_FEE_SOURCE

Develop User

Interface to maintain Item

Classification

Codes

• Develop and finalize UI/UX design comps (working prototype, wireframes, storyboards, etc.)

• Implement UI in Development environment o Link UI fields to associated database columns o Code dependencies and data validation logic.

• Test (Full testing will not be possible until all search attributes used for filtering and sorting are developed and defined in the system).

STORES 2.0

(FedMall Enclave)

STORES 2.0

Implementation Team

Develop module in MSNR to

Associate/Disasso ciate ICCs

Develop module in Master Stock Number

Maintenance to:

• Display ICCs associated with a master stock number record.

• Associate/Disassociate ICC from master stock number record

STORES 2.0

(FedMall Enclave)

STORES 2.0

Implementation Team

4.0 FOLLOW-UP

4.1 Issues and Implementation considerations

• Functional Testing: Interdependencies between modules and components being developed for STORES 2.0 and the necessary staggering of solutioning and development activities for those pieces will impact testing strategies. Testing the initial deployments of code may be limited to unit testing combined with a limited set of functional tests. As additional components are developed and deployed, additional functional testing will be possible, including UAT for more mature components.

Acceptance Criteria and Test Cases will need to be closely tracked and assigned to a

Sprint Cycle once they can be verified.

5.0 GLOSSARY OF TERMS

The following table identifies acronyms and terms used within this document.

Term Description

Baseline Catalog Pre-Production catalog that is undergoing updates by the vendor or DLA before being submitted for publishing. It is used by non-EDI Vendors to view and submit changes to products for a given contract. The Baseline interface allows for Vendors to import a catalog file, copy from another Baseline Catalog, or pull a copy from the

Pending or Active Catalogs.

BDFA (Basic Daily Food

Allowance)

BDFA Information is provided monthly to the Joint Subsistence Advisory Board.

BDFA uses a Core Catalog of essential daily nutritional requirements by Service and then looks across all Catalogs per Ordering Point to identify the required measure

(calculates the cost per service member to meet daily allowance).

Catch Weight Item An item that is sold by its weight but varies in weight from one package to another, (i.e., variable weight items).

Catch Weight Multiple Number of units (in LBs) that must be ordered to purchase 1 case of a “catch weight” item (a variable weight item for which vendor submits average case weight, in LBs).

Competitive Pricing Determining a price is fair and reasonable primarily through, but not limited to, comparative price analysis, the use of government in-house records, data obtained from market environment, and/or published commercial indices.

CONUS Within Continental United States (compare to OCONUS).

CS (Contract Specialist) Prepares contract records in the system that align with established contracts.

Reviews all contract and catalog elements to ensure completeness and accuracy prior to review by the KO.

DAAS (Defense

Automatic Addressing

System)

DAAS provides STORES with data mapping and routing services so that inbound and outbound transactions can be converted to the proper file format for ingestion into STORES or partner systems.

Distribution Fees Distribution fees set up per contract per option period. This is important because there is error checking in item request process that is linked back to this information in CCM where the distribution fee schedule is set up. Distribution Fee categories are tied to a specific unit of measure.

EBS (Enterprise Business

System)

Financial system of record for all STORES transactions.

EDI (Electronic Data

Interchange)

EDI is a standardized message format used to transfer transactional data between

STORES and EDI-enabled partner systems using VANs, such as prime vendors. All

EDI file generation and translation for STORES is handled by DAAS.

FIC (Food Item Code) Three-character code specific to the Navy for identifying an item. FIC not as specific as a stock number. Multiple stock numbers can be associated with one FIC code.

eProcurement DLA developed EProcurement to provide enterprise-level procurement capabilities to replace legacy procurement systems (Pre-Award Contracting System, Electronic

Contract Folder, Procurement Automated Contract Evaluation, and Base Operations

Support System).

The Intended functions of EProcurement are to manage purchase requisition, source and solicit, manage award, manage vendor performance, perform receipt, and process invoice.

FMS (Food Management

System)

FMS is used to refer to any of the Miliary Service Systems used for managing subsistence-related tasks such as sourcing and planning meals. They are as follows:

• Army Food Management Information System (AFMIS)

• Navy Food Management System (FMS)

• Air Force Equipment Management System (AFEMS)

• Marine Corps Food Management Information System (MCFMIS)

FSE (Food Service

Equipment)

Equipment used in the preparation, storage, and serving of food items.

FSOM (First Sunday of

Month)

FSOM is a term referring to how MPA Imports and reports are grouped. Users can select to view records for the upcoming FSOM or previous FSOM.

FSOS (Food Operating

Supplies)

Supplies used by individuals to consume and temporarily store food (includes paper and plastic-based items like cups, plates, and flatware).

GTIN A Global Trade Item Number (GTIN) is a unique and internationally recognized identifier for a product. It appears next to the barcode on a product's packaging.

IAW (In Accordance

With)

Term used in reference to whether an LSN complies with a Service’s Buyers Guide.

ICC (Item Classification

Code)

An ICC is a code representing specific attributes about the item taken from a specification sheet or label. ICC codes allows “like” items to be identified in

STORES.

IDoc (Intermediate

Document)

IDoc is a standard data structure used in SAP applications like EBS to transfer data to external systems like DAAS. EBS supports both inbound and outbound IDocs for

STORES.

JCCoE (Joint Culinary

Center of Excellence)

The JCCoE serves as the focal point for all Army Food Program issues, including lead organization for the Department of the Army (DA) G4 food program.

KO (Contracting Officer) Reviews and gives final approval of all contract and catalog elements.

LSN (Local Stock

Number)

Local Stock Number assigned in EBS. STORES Team maintains a ledger of all

LSNs to manage them. Once an LSN is created, it will never be reused even if retired. Commonly recognized with an “E” in the NIIN portion. Example: 8960-01-

E113663

MLL (Master Load List) The Navy Mandatory Load List (MLL) identifies items that should be on each

Ordering Point. The Navy submits MLLs for each class of ship that DLA manages to ensure Catalogs at ship Ordering Points cover the items. The initial Stock

Number for these items does not change; however, if some items are not provided globally, then the Stock Number is updated with Acceptable Replacements. The

MLL is implemented using a Core Catalog.

Market Fresh Market Fresh (or Market Ready) items include fresh milk, eggs, and bread.

Master Catalog A master catalog is a collection of stock items established and maintained by the

Subsistence Tech/Quality group. The master catalogs specify the exact definition and related details for all Stock Numbers contained within the catalog.

Master Stock Number Primary item identification number tracked in EBS; usually an LSN (vs. NSN).

Pricing Specialist Manages pricing agreements with manufacturers and vendors and ensures the catalog price data is in compliance with those agreements.

MPA (Manufacturer

Pricing Agreement)

An MPA is where manufacturers negotiate a fixed price for every Vendor such as with a Prime Vendor. Vendors allowed a distribution cost. Manufacturers can change prices monthly. Manufacturers reimburse DLA on products purchased. Primarily used OCONUS. Not allowed in conjunction with NAPA.

MPL (Mandatory Product

List)

The Mandatory Products List (MPL) is a listing of items supplied by industries that participate in the Ability One (formerly Javits-Wagner-O’Day Act) Program.

MSNM (Master Stock

Number Management)

<ADD>

NAPA (National

Allowance Program

Agreement)

NAPA is where Manufacturers provide rebates to DLA for volume purchases.

Normally used in CONUS where DLA is not considered a volume buyer relative to other sales. Manufacturers submit a NAPA Catalog with discounts per product.

Mostly CONUS. Cannot give a bottom-line price and then go to MPA and offer a higher price. Agreements with vendors to allow for discounts - usually for CONUS

- different prices based on allowances - can be $10s millions per year - 80% of the items - wants generic numbers. Designated after Stock Numbers assigned.

Agreement Holders will submit their offered discounts by SKU or manufacturer code

NPL (National Price List) Manufacturers provide item prices to government. The price can't be increased without notifying the customer.

NSN (National Stock

Number)

A National Stock Number is simply the official label applied to an item of supply that is repeatedly procured, stocked, stored, issued, and used throughout the federal supply system. One NSN can apply to multiple manufacturers. Rations are NSNs.

OCONUS Outside the Continental United States (compare to CONUS).

OpRats (Operational

Rations)

OpRats include Meals Ready to Eat (MRE) and Unitized Group Rations

(UGRA/B/H&S).

Package Size Number of measures within an intermediate package (example: 12 OZ CN).vi

Package unit of measure Unit by which intermediate package is measured (example: 12 OZ CN)

Packaging Code How intermediate unit is packaged (example: 12 OZ CN)

PCPL (Published

Commercial Price List)

A PCPL is a list of prices put out by the manufacturer that apply to everyone

(depending on their pricing tier). Due to everyone getting the same price, F&R evaluations are not required (no price analysis required). However, DLA still does audits on these items to ensure all prices are being added correctly. A price included in a catalog, price list, schedule, or other form that is regularly maintained by the manufacturer or vendor (established catalog / market prices), is either published or otherwise available for inspection by customers, and states prices at which sales are currently, or were last, made to a significant number of buyers constituting the general public. A government-only price list without commercial sales does not meet the definition.

PPI (Producer Price

Index)

The PPI is the Government-standard for forecasting and managing vendor prices and for tracking inflation.

Produce Fresh fruits & vegetables (FF&V)

Production Catalog Live STORES catalog from which customers can order items.

PRF (Purchase Ratio

Factor)

The PRF is used to translate between UoI and UoM to enable varying items to be compared at a consistent volume or mass. Consists of (2) fraction values where: the denominator is usually 1 representing the UoI; and the numerator that represents the

UoM. For example: 6/1 PRF means there are 6 UOIs in one UOM.

PV (Prime Vendor) Commercial food distribution companies contracted to provide subsistence items.

Most LSNs in STORES are on PV contracts.

SPV (Subsistence Prime

Vendor)

See PV (Prime Vendor).`

TQ (Tech/Quality) Tech Quality operator with primary responsibility to verify the completeness and accuracy of catalog items.

TVLS (Tailored Vendor

Logistics Specialist)

Tailored Vendor Logistics Specialist with primary responsibility to communicate with Vendors to share and/or obtain information applicable to their accounts, catalog items, etc.

UOI (Unit of Issue) Unit by which DLA Troop Support sells an item to the customer (example: “CO” – container).

UOM (Unit of Measure) Unit by which vendor sells an item to DLA Troop Support (example: “CS” - case).

Units per Purchase Pack Number of intermediate or “inner packaging” units within a vendor Unit of Measure

(example: 24 – 12 OZ CN)

VAN (Value Added

Network)

EDI-enabled Vendors use 3rd party VANs to send and receive transactions from

STORES via DAAS, including the EDI-850 Purchase Order, EDI-810 Invoice, EDI-

997 Functional Acknowledgement, and EDI-832 Catalog Update.

6.0 REVISION HISTORY

6.1 Change History for Content of This Functional Specification

Revision

Date

Revision used:

Workbench version#

Name

Project/Team

Description

11/16/2023 Draft 1 Terryl Benson FedMall

STORES 2.0

Implementation

Team

Initial Draft

6.2 Version of Functional Spec Template (For CM Use Only)

Revision

Date

Revision used

Workbench version#

Revised By

Description

7.0 REQUIREMENT – FUNCTIONAL SPECIFICATIN APPROVALS

7.1 Digital Signature Required

Approving Official X

3.4 Development Tasks