PM Soldier Medical Devices acts as the primary materiel developer for Army medical capabilities. PM SMD supports 400 LINs with a catalog of over 17,000 NSNs and is constantly creating and modifying SKOs to support its mission. PM SMD is required to maintain multiple SKO versions ranging from production, development and historical fielded SKOs which all share the same NSN. Average SKO quantity totals 150 components with some assemblages reaching over 1,200 lines. Many kits share common components. As capabilities are changed, PM SMD will replace components across all kits in the enterprise. Currently ELMS SKO process will not allow variations of different SKO assemblies sharing the same NSN, users to compare to SKOs to view component differences, NSNs to be searched and return results for each SKO the component is associated with, and mass update allowing the user to swap component NSNs within multiple SKOs at the same time.
PM SMD Product Managers will identify Army requirement changes which result in mass SKO updates across the enterprise. When modernizing and updating common medical components across the board, catalogers will have to dive into each SKO one by one to inquire if a component is associated with it. This will drastically increase research efforts and time to update medical assemblages across the board. This will also cause opportunities for misses. Catalogers will have to work around this by extracting each SKO into excel and manually comparing. Without these changes PM SMD will realize a significant increase of man hours required to swap single component lines in over 100 SKOs. Manual swapping can increase opportunities for error and decrease cataloging accuracy across PM SMDs enterprise.

Modify ELMS SKO process to (1) display MUAG, TIC Code as component grid column. (2) Allow for multiple variations of the same SKO NSN, versions may represent test, production and historical variants. (3) Show historical changes and allow for reversion to a previous configuration. (4) Allow an NSN to be searched returning all SKOs the NSN is associated to. (5) Allow for comparisons between SKOs to view component differences, as well as historical changes to a SKO. (6) Allow Mass SKO Changes. The user should be able to select multiple SKO/Versions and specify a component NSN within all kits and a new NSN for it to be replaced by. Replacement should impact all selected SKOs.
For example, PM SMD may support 100 SKOs that contain a caliper device. Product managers may identify the current generation caliper to not meet the Army capability requirement. PMs will then direct the cataloging team to update all of PM SMDs SKOs. Updated SKOs will use the new caliper device which will have a new NSN. All 100 SKOs will need to be updated to replace the old generation caliper NSN with the new generation NSN. Quantity conversion may need to be taken into consideration (swapping QTY 2 for new requirement of QTY 1).

Proposed modifications will deliver the capability to manage several versions of a SKO for the purpose of material development, as well  as reducing manual excel manipulation required to compare multiple SKOs. Development activities require production, test, development and historical variants of the same federally cataloged NSN. Without these versions PM SMD will not be able to accurately and efficiently facilitate medical material development within ELMS. This change aims to  enhance unit efficiency, benefiting the individual Soldier by ensuring they can train and fight with confidence, knowing their equipment sets are current, reliable, and tailored to their mission requirements

PM Soldier Medical Devices supports 400 LINs with a catalog of over 17,000 NSNs and is constantly creating and modifying SKOs to support its mission. Several additional catalog data elements PM SMD uses to make business decisions are currently not present in ELMS. Without the additional catalog fields, PM SMD will not be able to create accurate procurement documents that represent the correct SKO subset.
The only alternative source for these catalog attributes will be WebFLIS or AESIP Web. If working with a SKO containing 500 components, users will have to manually search each component NSN in WebFLIS/AESIP to determine relevant attributes required to create purchasing lists

Modify ELMS Stock Number process to import AESIP fields, MUAG, UA Code, TIC Code, Army Data, Storage/Handling Notes, ASIOE
3. Allow search by ACC for purposes of finding non-procurable components

Proposed modifications will significantly reduce man-hours by eliminating need for manually searching catalog attributes in WebFLIS and AESIP Web. Without the additional catalog fields, PM SMD will not be able to create accurate procurement lists that represent the correct SKO subset. Without accurate purchasing documents, PM SMD will not be able to quickly and efficiently deliver medical capabilities to the Army

During the Marine Corps attempt to move to an Enterprise Logistics Program (LP) Structure, it became obvious that modification to the existing LP layouts in ELMS would be required. The Marine Corps Total Force Structure Management System (TFSMS) provides a detailed eight-level tiered structure which will allow allowance information to be placed on top of the Marine Corps warehousing inventory. To accomplish this task, length extension to existing fields and new attributes will be required with an explanation as provided.

See attachments for details.

To correctly align Unit structure hierarchy to the command and control of inventory.

Currently there is not an option to add attachments to Custodian Profiles. It would be a good resource to review any current memo assigning the role of custodian or view the last signed inventory report.

Add the option to upload attachments to Custodian Profiles.

DoDI 5000.64_DAFI 23-111, Accountability and Management of DoD Equipment
and Other Accountable Property, 6 December 2021

NECC ELMS users currently lack the capability to attach historical documents or records directly within Master Data Mgmt -> Warehouse. Which makes it difficult to track changes such as updates to Warehouse names or structures impacting tracability and audit readiness. Adding an attachment feature in Master Data Mgmt allows users to link historical documents to warehouse records

An "Attachment" button alongside the existing "Add" button on the Master Data Mgmt -> Warehouse.
Or when selecting "Edit" on a Warehouse an "Attachment" tab will populate next to existing tabs.

NECC 5200.45

NECC ELMS users are requesting additional functionality when conducting a Physical Inventory in ELMS to include the ability to view and inventory individual components of a SKO. Current,there is no way to see the SKO components listed when conducting a physical inventory. Adding additional lines below the SKO to allow the user to verify each component of a SKO individually when conducting the inventory would greatly improve the Physical Inventory process when SKO's are being inventoried.

During the Physical Inventory process, the user should have the ability to view and inventory each individual component when their inventory includes SKO'd assets.

NECCINST 5200.45

NECC ELMS users are requesting a new searchable report for SKOs that displays both SKO end items and its respective components on a single page, similar to the current ICN Report, and to show SKO assembly completeness (e.g., 1 of 4 components attached) to quickly identify deficient kits. This would greatly improve users ability to view and manage their SKOs.

A new report within the Inquiries - Inventories tab similar to the ICN report that allows users to search their SKOs, see their components, and evaluate SKO assembly completeness on one page.

NECCINST 5200.45

ELMS currently fails to aggregate individual component prices into a total SKO value. This discrepancy results in inaccurate asset valuations during transfers, hindering fiscal visibility and the accuracy of Key Supply System Documents (KSSDs). For instance, an SKO comprising three components valued at $100 each should reflect a consolidated value of $300. The current failure to automate this calculation necessitates manual intervention and increases the risk of reporting errors.

Implement an automated aggregation function within ELMS that dynamically calculates and displays the total SKO value by summing the individual prices of all assigned components to all associated reports with a new Grid Option Column ie. ICN inventory, Inventory update manager and prices within receipt/shipment forms as required.

NECC 5200.45

1) 440 SCOS built a dashboard tracking KSDs w/ attachments (Y/N).  See attachments
2) BLADE Supply Chain team need additional fields from the feeder_asset_ingest_staging table to build out requirements in apps.    

Requesting ELMS send BLADE the entire feeder_asset_ingest_staging table to eliminate multiple requests for specific fields in this table.  Requesting data refresh rate to be every 4 hrs.

Air Force Leadership has directed that all data analytics be performed within Advana/BLADE. This request is in line with the vision detailed in the attached decision memorandum.  

Multiple MAJCOMS are requesting the asset table to be updated every 4 hours, especially USTRANSCOM (Joint Enabling Capabilities Command, Joint Communications Support Element, and Joint Planning Support Element).  They are using ELMS (DPAS) data to inform deployable readiness on short notice.  

Change the data refresh rate on the asset table to every 4 hours.

Air Force Leadership has directed that all data analytics be performed within Advana/BLADE. This request is in line with the vision detailed in the attached decision memorandum.