Download presentation
Presentation is loading. Please wait.
1
IUID Scorecard Steering Group
AGENDA 4 November 2011 Pentagon, Room 4E979 1230 Welcome/Opening Remarks Mr. Ahern Mr. Peters 1240 Steering Group Purpose Ms. Conrad Meeting Objective IUID Implementation Timeline 1250 IUID Scorecard Updates USA, USN, USAF, USMC, DLA, SOCOM 1315 IUID Registry Overview Mr. Whittington 1345 IUID – Going Forward Ms. Conrad 1350 Closing Comments Mr. Ahern 1400 Adjourn
2
IUID Scorecard Purpose & Meeting Objective
The IUID Scorecard Steering Group provides governance and oversight for the Department of Defense IUID implementation Today’s Objective Components will provide Progress Reports in the areas of: Policy Updates Systems Updates (AIS and ERP) Contract Compliance Rate Physical Marking Use of IUID Registry
3
IUID Timeline Components develop, fund, and field capabilities to manage items in compliance with “Guidance” and Policies* Components complete comprehensive implementation planning based on “Guidance” Dec 2015 Leverage IUID TF to develop and issue IUID “Guidance” Product Lifecycle Management & Intensive Item Management via IUID-enabled SIM IUID TF conducted value proposition analysis Dec 2012 Mar 2012 Complete policy and DFARS revisions Jun 2011 Dec 2010 Complete Implementation Planning Deliver IUID “Guidance” Feb 2010 Jun 2009 DPAP Issued IUID Policy Clarification Jun 2008 JLB approved IUID Task Force recommendations Dec 2006 JLB directed the formation of an IUID Task Force established IUID standards for Tangible Personal Property established SIM for Materiel Maintenance
4
IUID SCORECARDS
5
IUID Scorecard (Army) – 4 November 2011
Objectives Policy Updates Systems Updates (AIS and ERP) Contract Compliance Rate Physical Marking Use of IUID Registry Engage Key Stakeholders Key Accomplishments/Events Policy Update: AR 70-1 “Acquisition Policy” released AR 700-XX IUID Policy (Worldwide Staffing comments under review) IUID Secondary Item (in use/inventory) Policy Refinement memo released Technical Documentation memo for Labeled Legacy Items released Legacy Mark Progress Reporting memo released HQDA G-4, IUID Process Integration Team memo released 94% of contracts compliant (based on random survey) Senior Executive Service Steering Group Established Quarterly meetings ASA(ALT), G-8, G-4, CASCOM and HQAMC participation Assess implementation progress (focus on developing use processes) Last meeting conducted 9 August 11 HQDA, G-4 IUID Process Integration Team Facilitate alignment & synchronization with implementation Coordinate policy, integration & processes with USAMC, subordinate commands, and USAMC marking activities Timeline Legacy items requiring marking ~ 12M (estimate does not include controlled items) Identify, Synchronize & Finalize Requirements: Develop Plan for Marking items Synchronized with GCSS-A and LMP Deployments – Sep 2011 AIT: Basis of Issue Plan – May 2012 Procure scanners – Oct 2012 Training - Jul 2012 Mobile Marking Teams: Request funding – Feb 2012 Begin marking – Aug 2012 Update Army Regulations (AR) – Oct 2013 Systemic updates with IUID GCSS-A: Process mapping & gap analysis – Aug 2013 Fielding – 4Q FY12 through 4Q FY17 LMP: Identify technical requirements – Jan 2013 Implement SAP Enhancement Pack – Nov 2013 Design & build LMP IUID solution – Aug 2014 Integrate & test with Trading Partners, Army IUID Warehouse & DoD IUID Registry beginning Apr 2014 through to full implementation – Sep 2015 Issues & Concerns Accuracy of Service Legacy Numbers In DoD IUID Registry (e.g., marked vice registered, using Service codes, etc.) Developing “Use” processes & capabilities across the Enterprise Map processes and identify gaps and cost drivers Identify policy & process impacts Operate in a “Mixed” IUID Environment (i.e., some items not marked) Mitigation through SES Steering Group (marking, AIT & AIS integration)
6
IUID Scorecard (Navy) – November 2011
Placeholder
7
IUID Scorecard (USAF) – Nov 2011
Objectives Policy Updates Systems Updates (AIS and ERP) Contract Compliance Rate Physical Marking Use of IUID Registry Key Accomplishments/Events Contract Compliance Rate Briefed Contracting Sr leadership/MAJCOM Policy Chiefs on requirement at Policy Conference 7 Apr 11 DFARS (IUID clause) 3QFY % of contracts that met IUID criteria included this clause (up from 86% in 4QFY10) DFARS (GFP) 3QFY % of contracts where GFP is provided included this clause (up from 60% in 4QFY10) Revised AFMAN to include IUID marking Asset Marking & Tracking WG -- Apr 11 Legacy Part-marking WG -- Mar/Jun 11 – Class IX AFEMS Marking WG -- Mar/Jun 11 1M Marked Legacy Equipment Item -- Sep 11 Commemorative ceremony 22 Sep/Whiteman AFB Timeline Systemic updates ECSS (design to go-live) – FY 2012 Enterprise UII Read Application (FY 2012) Over 2M Items Marked as of Jul 11 (Acquisition and Legacy) Legacy Data Class IX: 7M (~40K marked/~10K registered) Class VII: 5.3M (~1.1M marked/ ~700K registered) Class II: 1M (gas masks, ESAPI) In Work Acquisition and Legacy – Class IX/VII/II Drive increased use of DFARS: On-going Class IX marking in depots -- FOC: Dec 15 Class VII – AFEMS Project: Jun 12 Class II – Developing project -- Pilot: Sep 11 Issues & Concerns Engineering Analysis Lagging Class IX assets requires ECOs; 3K of 18K completed Functional Involvement to achieve SIM Change management IUID integration into business process Funding for marking and eTools Governance Structure needed to drive change Status of ERP ... Legacy AIS requires modification Data Validation and Management
8
USMC IUID Scorecard – Nov 2011
Objectives Close Battle: - Draft CONOPS in final staffing prior to submission to DC I&L. - IUID incorporated into AIT ICD. - IUID CDD being drafted ISO making IUID a program of record. - Draft SIM policy incorporates UII. - Incorporate IUID into Marine Corps Logistics Roadmap. Deep Battle: - Incorporate IUID in Marine Corps Order 4400 Series, Supply Management Policy. - Seamless integration of IUID Data into a system of record. - Incorporate IUID Into Remaining GCSS-MC Modules & other AIS with Item-Level Tracking. Key Accomplishments/Events Theater Deployment of IUID-Enabled Maintenance Management with Light Armored Reconnaissance (LAR) Battalions (LAV & Automated Armory - Afghanistan). Maintained 100% Contracts Inclusion of IUID DFARS Clause. Confirmed main IUID DFARS Clause is Included in all USMC Interservice Support Agreements (ISSAs). Entered 500,000th Record into TDS. Completed Marking Legacy PEIs at MC Prepositioning Program-Norway (~2,000 items). Completed weapons & optics marking at two large armories in preparation for automation with AIT and AIS. Over 2,000 marking instructions published ISO PEIs & Secondary Reparables (SECREPs). Timeline 44% PEIs marked/captured – 537,983 Items in USMC IUID Repository Marked/Registered with USMC IUID Data Standards (New & Legacy), Oct 2011 (Class II, VII, VIII) Phase I: 70K of 107K (Mission Essential) Phase II: 339K of 752K (Controlled Items) Phase III: 130K of 366K (SIM/>$5K/PM) Nov DLA Authorization to Include IUID DFARS clauses for USMC Items by NSN without Technical Drawing Updates. Nov 2011 – Contracting compliance deep dive. Dec 2011 – Reparable deep dive. Aug 2012 – Scheduled integration of IUID into the Warehouse Management module of GCSS-MC. Development of requirements in process. Issues & Concerns Funding for completion of legacy equipment and reparable marking. Funding for legacy AIS enablement. Funding for technical drawing package updates. AIT interface and UII functionality within GCSS-MC. Historical logistics and financial item data. Promoting AIS compliance and business process improvement to realize the value proposition of IUID implementation. Contract compliance and quality assurance of OEM IUID marks. Program Manager’s roles and responsibilities for clean financial audit and readiness. Enforcement of IRB IUID condition on AIS. Objectives: “Support completion” was used for SIM since it’s not directly under the control of the IUID team/program, it’s in PG10 Timeline: The Registry includes many more UIIs for USMC new Acquisition (possibly on the order of tens of thousands). The Registry monthly report for new and legacy UIIs, broken down by service, shows 478, 255 total new acquisition UIIs from USMC contracts in Registry as of July 6, But we don’t understand their methodology exactly for new acquisition, and prefer to work with our own repository, which has a larger data set per item. And certainly don’t understand it for legacy link to service. If necessary, we can put in the bullet under Timeline: 478, 255 total new acquisition UIIs from USMC contracts in Registry as of July 6, 2011
9
IUID Scorecard (DLA) – Nov 2011
Objectives Policy Updates - issued DLA PROCLTR 11-02, dated Mar 8, 2011 mandating compliance with DFARS Clause Contract Compliance Rate - 100% of contracts compliant Key Accomplishments/Events Participated in DLA/DoD working group that addresses the different levels of intensity for the handling of items marked with IUID Teamed with the Marines to identify ground equipment items that require IUID marking Timeline Establish and promulgate guidance of IUID indicator in Federal Catalog – J6 (Information Services) is prepared to implement pending decision on levels of intensity Issues & Concerns Lack of marking & reading capability at the DLA Distribution depots No progress on Service identification of DLA managed items that require IUID marking Impact on the DLA Distribution storage requirements
10
IUID Scorecard (USSOCOM) – Nov 2011
Objectives Policies in Revision SOCOM Directive 70-2 (Item Unique Identification) January 2008 SOCOM Directive (MFP-11 Funded Asset Visibility and Accountability) July 2008 SOCOM IUID Working Group Restart SOCOM IUID Working Group VTC/Teleconference between HQ and Components Address on-going issues and challenges Key Accomplishments/Events DFARS (IUID clause) 418 of 522 contracts DFARS compliant Compliance 80% in 3rd Qtr 11 IUID Implementation Plan Review 71 programs reviewed 66 programs have current plans (94%) Physical Marking 402,535 of 487,509 Items Marked Compliance 83% as of 3rd Qtr 11 Special Operations Forces Support Activity (SOFSA) IUID Marking Lab – Lexington, KY Lab has produced 282K IUID marks ( ) Timeline Policy Revisions Complete Physical Marking 487,509 IUID Required items as of Jul 2011 All will be marked IAW DoD Directive by 2015 Issues & Concerns Ops Tempo continues to limit access to employed legacy assets for marking OEMs still use both UII constructs which causes duplicative effort to correctly mark items upon receipt DOD Registry – Unable to sort DoD registry to segregate SOCOM specific assets Y On schedule and no significant issues Behind schedule but will meet ECD Behind schedule and won’t meet ECD
11
Item Unique Identification (IUID) Registry
4 November 2011
12
IUID Introduction Need for the IUID Registry
WARFIGHTER-FOCUSED, GLOBALLY RESPONSIVE, FISCALLY RESPONSIBLE SUPPLY CHAIN LEADERSHIP IUID Introduction Need for the IUID Registry The Unique Item Identifier Super Users Future of the IUID Registry Future IUID Registry Requirements Milestones WARFIGHTER SUPPORT ENHANCEMENT STEWARDSHIP EXCELLENCE WORKFORCE DEVELOPMENT
13
WARFIGHTER-FOCUSED, GLOBALLY RESPONSIVE, FISCALLY RESPONSIBLE SUPPLY CHAIN LEADERSHIP
Introduction The IUID Registry is the central repository for IUID information and serves as the acquisition gateway to identify What the Item is How and when it was acquired Initial unit cost of the item Current Custody (Government or Contractor) How the item is marked This information when applied to New Acquisition is typically coined the “Birth Record” of a tangible asset. Although this is still true, it is important to understand the mission of the IUID Registry is more than the capture of the acquisition data. The IUID Registry also stores information relating to the modification and other Life Cycle Events (LCE) of assets in addition to custody (GFP). WARFIGHTER SUPPORT ENHANCEMENT STEWARDSHIP EXCELLENCE WORKFORCE DEVELOPMENT
14
WARFIGHTER-FOCUSED, GLOBALLY RESPONSIVE, FISCALLY RESPONSIBLE SUPPLY CHAIN LEADERSHIP
DoDI Item Unique Identification (IUID) Standards for Tangible Personal Property 1.3. Establishes the IUID Registry as: The authoritative source of Government unit acquisition cost for items with UII acquired after January 1, 2004, and for UII pedigree data established at delivery as defined by Reference (f). The master data source for Government Furnished Property (GFP). An authoritative source for establishing the full cost of end-item equipment. 1.4. Establishes the functional framework for IUID as it relates to associated DoD policy and guidance. WARFIGHTER SUPPORT ENHANCEMENT STEWARDSHIP EXCELLENCE WORKFORCE DEVELOPMENT
15
Need for the IUID Registry
WARFIGHTER-FOCUSED, GLOBALLY RESPONSIVE, FISCALLY RESPONSIBLE SUPPLY CHAIN LEADERSHIP Need for the IUID Registry Asset data sharing across Automated Information Systems (AIS) Assurance that item data retrieved is definitive and not that of another like item Ability to share data across DoD AIS Acquisition systems, Logistics Systems and Financial Systems Identify assets in the possession of Contractors (Improve Readiness) Data in the Registry is valuable and being adopted The IUID Registry is a DoD level system that accepts and store the Unique Item Identifiers and the data set they represent. It is also a DoD level system to identify all Government property (GFP) held by contractors. This will allow users and senior level management to go to one system for information on items and custody The repository for the UII. The Registry, in addition to providing data about items, provides a method to map data from other AIS to get additional item information. The UII can not be duplicated and is never deleted. This ensures that the information retrieved relates only to the information desired WARFIGHTER SUPPORT ENHANCEMENT STEWARDSHIP EXCELLENCE WORKFORCE DEVELOPMENT
16
The UII “Data Key” The Unique Item Identifier (UII) “data key”
WARFIGHTER-FOCUSED, GLOBALLY RESPONSIVE, FISCALLY RESPONSIBLE SUPPLY CHAIN LEADERSHIP The UII “Data Key” The Unique Item Identifier (UII) “data key” The UII gives access to a specific sub-set of information pertaining to a specific item The UII does not replace the National Stock Number (NSN) UII and Standard Serialization AIS often use different Data Keys such as Serial/NSN or Serial/Part Number for item identification An OEM serial number alone will not definitively identify an item The UII and the NSN are Data Keys. The keys alone provide limited information, but enable AIS to retrieve a wide range of item information The National Stock Number (NSN) is a data key allowing access to a sub-set of information to a commodity or group of items sharing form, fit and function characteristics The UII is a data key representing a sub-set of information about a specific item These Keys have different data sub-sets and are complimentary; the UII or NSN can not be used in place of the other. They are used to answer different questions There is not a standard across the DoD to identify assets with custodial systems. Some custodial systems use the NSN and Serial while others may utilize the CAGE / Part Number. Sharing data across these dissimilar systems can be problematic The UII remains with the asset through the entire life cycle from procurement to disposal. The UII is never changed or deleted from the IUID Registry regardless of item modifications or life cycle status Standard Serial numbers can and do get changed (Serialized) WARFIGHTER SUPPORT ENHANCEMENT STEWARDSHIP EXCELLENCE WORKFORCE DEVELOPMENT
17
Unique Item Identifiers (UII)
WARFIGHTER-FOCUSED, GLOBALLY RESPONSIVE, FISCALLY RESPONSIBLE SUPPLY CHAIN LEADERSHIP Unique Item Identifiers (UII) ~40K items registered per week 16 Million UII October 2011 1M Feb 2007 4M Nov 2008 8M Nov 2009 12M Dec 2010 14M Jun 2011 15M Aug 2011 600K UII in GFP Status UIIs are expected to exceed 100 million 4.9 Legacy 10.8 New Acquisition 600K are Government Furnished Property (GFP). GFP is legacy by definition. The 600K are part of the 4.9M WARFIGHTER SUPPORT ENHANCEMENT STEWARDSHIP EXCELLENCE WORKFORCE DEVELOPMENT
18
Customers Early Program Customers
WARFIGHTER-FOCUSED, GLOBALLY RESPONSIVE, FISCALLY RESPONSIBLE SUPPLY CHAIN LEADERSHIP Customers Early Program Customers Questions from Government customers concerned Cost and Requirement Larger number of contractor customers interested in contract compliance Current Customers Shift from a majority Contractor customers to a greater number of Government (Logistics) customers Greater level of sophistication More interest in leveraging IUID Registry Data and design of the IUID Registry system (Questions have moved beyond compliance) Early IUID Registry program questions were mostly concerned with how implementation would be funded and if the requirement could be waived. Contractor interest was greater than government and appeared to be driven primarily by the need to comply with contract clauses. There was not a lot of interest in leveraging the data Customers now look to leverage the Unique Item Identifier data within their specialties. As customers have become more familiar with IUID, their questions are much more sophisticated and demonstrate creative thinking towards the use of the IUID Registry data. Government and Industry customers are taking a much more active role in the design and functionality of the IUID Registry reports and design WARFIGHTER SUPPORT ENHANCEMENT STEWARDSHIP EXCELLENCE WORKFORCE DEVELOPMENT
19
Mine Resistant Ambush Protected (MRAP) - Program Management
WARFIGHTER-FOCUSED, GLOBALLY RESPONSIVE, FISCALLY RESPONSIBLE SUPPLY CHAIN LEADERSHIP Mine Resistant Ambush Protected (MRAP) - Program Management Multiple Manufacturers of the same end item Subsequent modifications for mission requirements Use of the Unique Item Identifier to assist with Configuration Management and Tracking Outcome: Readiness & Transparency of all MRAP Assets MRAP is an example of data use from a weapon system Program Management perspective IUID Registry data used for configuration management tracking and data quality for financial, acquisition, logistics support Mine Resistant Ambush Protected (MRAP) Vehicles. MRAP personnel were dealing with an aggressive production schedules to meet mission needs. Multiple entities were involved with the production and modification of platforms. The Joint Program Management Office encountered difficulties of tracking. Configurations of the vehicles presented a challenge. WARFIGHTER SUPPORT ENHANCEMENT STEWARDSHIP EXCELLENCE WORKFORCE DEVELOPMENT
20
WARFIGHTER-FOCUSED, GLOBALLY RESPONSIVE, FISCALLY RESPONSIBLE SUPPLY CHAIN LEADERSHIP
LOGSA – PEO/Logistics Collaboration with Army; USAMC Logistics Support Activity (LOGSA) Army Item Unique Identification (IUID) Warehouse (AIW) Property Book Unit Supply Enhanced (PBUSE) populated with over 1 million UIIs due to work that has been accomplished between the Army and the IUID Registry By leveraging the Unique Item Identifier, LOGSA is removing the possibility of ambiguity of information in PBUSE at the item level LOGSA is an example of data use from the PEO/Logistics perspective Discussion Paper 14 Jul 2010 SUBJECT: Army Item Unique Identification (IUID) Warehouse (AIW) Issue. Provide information and status on the AIW at the USAMC Logistics Support Activity (LOGSA). The Army IUID Warehouse (AIW) is referenced in both the USAMC Draft IUID Implementation Plan (awaiting signature) and the Army IUID Implementation Plan (signed 15 Jul 09). The intent of AIW is to provide an authoritative source of Army IUID data, integrated with other logistics data. AIW will include Army specific reports, will interface with the DoD IUID Registry and Army systems such as PBUSE. LOGSA has coordinated AIW interfaces and requirements with OSD, AMC, HQDA, ASA(ALT), AESIP, PBUSE, and GCSS-A. AIW is currently updating the unique item identifier (UII) in PBUSE, eliminating the need for manual scanning. ASA(ALT) is currently drafting policy for PMs which will reference this AIW/PBUSE interface. AIW currently contains all DoD IUID Registry data, all Wide Area Workflow (WAWF) NSN/UII data, all AMCOM Maintenance Consolidated Database System (MCDS) UII data, all PBUSE UII data, and PM UII data via uploads. WARFIGHTER SUPPORT ENHANCEMENT STEWARDSHIP EXCELLENCE WORKFORCE DEVELOPMENT
21
Future of the IUID Registry
WARFIGHTER-FOCUSED, GLOBALLY RESPONSIVE, FISCALLY RESPONSIBLE SUPPLY CHAIN LEADERSHIP Future of the IUID Registry A primary goal of the IUID Registry is to leverage existing data / systems to meet mission requirements for Acquisition, Logistics and Financial reporting Data must be useful and relevant Great effort is taken to prevent the duplication of information available elsewhere Work with Service Enterprise Resource Planning (ERP) for data exchange standards One of the directives given to the IUID Registry IT team is to find existing sources of information to meet requirements. One obvious example is the data sent from Wide Area Workflow with assets are accepted by the government. The UIIs are reported to the IUID Registry systemically as opposed to a “Swivel chair” approach to entering data as a separate transaction. We are currently working with ECSS Air Force create interfaces to the IUID Registry and other services. WARFIGHTER SUPPORT ENHANCEMENT STEWARDSHIP EXCELLENCE WORKFORCE DEVELOPMENT
22
Future Requirements for IUID
WARFIGHTER-FOCUSED, GLOBALLY RESPONSIVE, FISCALLY RESPONSIBLE SUPPLY CHAIN LEADERSHIP Future Requirements for IUID Future requirements will be driven by Government Furnished Property Accountability Property Information for Existence & Completeness Financial Improvement Audit Readiness Cyber Security Threat Traceability Anti-Counterfeit Initiatives Customer Input The IUID Registry team meets routinely with representatives from Government Service agencies and Industry. There are 2 IUID Registry user group meetings for government and 2 for industry per year. We will continue to work with customers to help they comply with regulations and instructions. WARFIGHTER SUPPORT ENHANCEMENT STEWARDSHIP EXCELLENCE WORKFORCE DEVELOPMENT
23
IUID Registry Milestones
WARFIGHTER-FOCUSED, GLOBALLY RESPONSIVE, FISCALLY RESPONSIBLE SUPPLY CHAIN LEADERSHIP IUID Registry Milestones IUID Registry Government User Group Meeting: 12/8/11 v5.1 Version Release: 2/27/2012 Development Brownout for Re-host: 4/15/2012-9/1/2012 Fully Operational at DISA DECC: 8/15/2012 v5.2 Development Begins: 9/2012 v5.2 Estimated Delivery: 3/25/13 The IUID Registry software version 5.2 is in the requirement gathering stage The IUID Registry Industry User Group conducted on 3 November 2011 Held in conjunction with the Aerospace Industries Association (AIA) WAWF/UID/RFID eBusiness Industry group Version 5.2 will be the next release of the IUID Registry software after the move to the DISA DECC WARFIGHTER SUPPORT ENHANCEMENT STEWARDSHIP EXCELLENCE WORKFORCE DEVELOPMENT
24
WARFIGHTER-FOCUSED, GLOBALLY RESPONSIVE, FISCALLY RESPONSIBLE SUPPLY CHAIN LEADERSHIP
Questions? WARFIGHTER SUPPORT ENHANCEMENT STEWARDSHIP EXCELLENCE WORKFORCE DEVELOPMENT
25
IUID Implementation Going Forward
Continue development and execution of an enterprise IUID implementation strategy Finalize requirements for IUID: Indicator in Federal Logistics Information System (FLIS) Defense Logistics Management System (DLMS) Refine and publish applicable policy documents Update technical documentation Establish progress report update schedule
Similar presentations
© 2025 SlidePlayer.com Inc.
All rights reserved.