Uid Forum - Uid 201 Final 4-19-06 (1)

8/6/2019 Uid Forum - Uid 201 Final 4-19-06 (1)

1/52

Pam Rooney (WFI)James Clark (Keane)

UID 201: Using IUID

Introduction


2/52

Resources - General IUID Toolkit Four tracks: PMs, Suppliers, Depot,

Operations and Field Maintenance http://www.iuidtoolkit.com

DAU UID Special Interest Area Within Acquisition Community Connection https://acc.dau.mil/simplify/ev.php?ID=18058_201&ID2=DO_TOPIC

Resources
http://www.iuidtoolkit.com/https://acc.dau.mil/simplify/ev.php?ID=18058_201&ID2=DO_TOPIChttps://acc.dau.mil/simplify/ev.php?ID=18058_201&ID2=DO_TOPIChttps://acc.dau.mil/simplify/ev.php?ID=18058_201&ID2=DO_TOPIChttps://acc.dau.mil/simplify/ev.php?ID=18058_201&ID2=DO_TOPIChttps://acc.dau.mil/simplify/ev.php?ID=18058_201&ID2=DO_TOPIChttp://www.iuidtoolkit.com/http://www.iuidtoolkit.com/


3/52

IUID Toolkit

Resources


4/52

DAU UID SIA

Resources


5/52

Scope Vision Data Flow Case Study - 160 th S.O.A.R. Case Study PCARSS Benefits Questions

Agenda

Agenda


6/52

Scope

UID 201: Using IUID

Scope


7/52

IUID

New items Legacy items Government Furnished Property

Real Property RFID

Policy & Regulation

Scope


8/52

Planning/SystemsEngineering

Acquisition &Procurement

Financial Management

Operations &Deployments

Logistics/MaterielManagement

Property Management

IUID

What items are needed?How are items marked?How is uniqueness assured?

What item am I buying?How do I buy the item?

How many items are there?How much are the items worth?

What items are available?Where are the items en route

to a location?

How is the item located?

How is the item transported?How is the item managed?

What items are there?How are the itemsaccounted for?

Industry

Joint FinancialManagement Improvement

Program(JFMIP)

Other federal

agencies; GSA, TSA,NASA

Joint Total Asset

Visibility

DoD CFOAccountability

ConfigurationManagement

How is the tech data managed?

Secure Collaboration?Data Access/Sharing?

CoalitionPartners

MaintenanceManagement

What is the maintenance history of the items?Which items do I fix vs. discard?

StakeholdersScope


9/52

UID 101

Select Itemsto be

MarkedMark Items

Decide Whereto Mark and

Marking

Technology

IUID Plan Requirements Responsibilities Business Rules

IUID Budget

IUID ResourcesDevelopMarking

Capability

DocumentEngineeringDecisions

TransactData

Scope


10/52

UID 201

Select Itemsto be

MarkedMark Items

Decide Whereto Mark and

Marking

Technology

Do Somethingwith Mark

IUID Plan Requirements Responsibilities Business Rules

IUID Budget

IUID ResourcesDevelopMarking

Capability

DocumentEngineeringDecisions

SIM Plan

MaterielReadinessBudget &

Resources

TransactData

IUID Registry

Service/

DLA AISs

IDE

Scope


11/52

Operational Architecture Overview

Scope


12/52

Data Capture Opportunities

Scope


13/52

Require DoD contracts reflectthe requirement for part marksto include UII data elements for all items which require uniqueidentification

Create/Generate Industrysuppliers/manufacturersthroughout supply chainassign and apply UII data

elements and ensure theuniqueness of thecomponent data elements

Capture DoD establishes the birth record of the

UII by capturing the machine/human readablecomponent data elements to create the UII in the AIT/AIS

Use Functionalstakeholders use UIIas a primary or alternate key in the

AIS to access or update iteminformation basedon its UII

Dispose DoD/GSA recordsthe termination of the UII at time of item disposal

UII

What is the IUID Lifecycle?

Scope


14/52

IUID will enable the requisition by UII-

related data Replace item with one just like it Not all items have NSNs If good performers are identified via UIIs,

greater probability of increasing thepercentage of good performers

Catalog alias enables reuse of vendor data

Require

Scope


15/52

Create/Generate Suppliers can take advantage of the same

benefits of UII that the DoD receives Greater data accuracy through the

manufacturing/assembly process

Improved item visibility

Improved supplier-to-supplier data exchange

Scope


16/52

Capture By establishing the birth record, data

can be associated across multiplesystems

The IUID Registry serves as theauthoritative source for items and their pedigree

Scanning the mark reduces time andincreases accuracy of data

Scope


17/52


18/52

Dispose

UIIs improve the capability to knowwhat has left the inventory

UIIs improve the capability to knowwhat is coming back into inventory

Scope


19/52

IUID RegistryUnique Item Identifier (UII)

STEP 1: Mark ItemsSTEP 1: Mark Items STEP 2: Register DataSTEP 2: Register Data STEP 3: Automatic Data CaptureSTEP 3: Automatic Data Capture

STEP 4: Application ProcessingSTEP 4: Application Processing

Updates

Metric Quantity (millions)

UII Items in DoD Inventory 67.7

Property in Possession of

Contractors

29.5

Total UIIs 97.2

Estimated Scope of UII Coverage

Acquire

Store Use

Expend/Dispose

MaintainEDI

Transactions

WAWF

XML

Automatic information data capture (AIDC) eliminates error-prone and time-consumingmanual data collection and data entry. AIDC provides quick, accurate, and cost-effective

collection and entry of data.

Retrieval

Identify Item

Scope


20/52

Vision

UID 201: Using IUID

Vision


21/52

Time Line2007-2008

2006-2007

2005-2006

2002-2005

Enterprise Visibility

Accountability Value

Organization Program Location Status

AT&L/P&R PA&E AT&L CJCS/P&R/AT&L

Le g a l

Co n t r o llin g

Cu s tod y

S t e w a r d

Property (AT&L)

Real Property PersonalProperty

AT&L

People (P&R)

Person Role

P&R

CJCS/P&R/AT&L

Formal Ad Hoc Budget ACAT Absolute Relative Condition Disposition

UIIRPUID FMIDEDIPI

Ability to describe

Ability to valueand account

UID Elements

Vision


22/52

IUID Enabled Intensive Life CycleSupport Management

Value

Processes

Analysis

Information Systems

Supply Chain Events

Uniquely Identified Items

Item UniqueIdentifier

(UII)

MachineReadableMarking

AutomatedDataCollection

Item UniqueIdentification

(IUID)

Financial ManagementWarranty ManagementTracking Item Performance & AgeFailure AnalysisReliability ImprovementMaintenance ProductivitySupply ProductivitySafetyAccountability

Intensive Life CycleSupport Management

Capabilities Requirements Objectives

R e s o u r c

e s

R e s o u r c

e s

P a y b a c k

P a y b a c k

Vision


23/52

Registry Data CaptureSupplyDepots

Operating Construct for IUID Systems EnvironmentOperating Construct for IUID Systems Environment

UID Registry Services

IUIDRPUIDGFP

Accountability& Value

Maintenan

ceSystems

PropertySystems

Config.MgtSystems

ExternalData

SourcesEPCRegistries

Catalogs

DoD LegacySystems

Updates for Changes

Organization Value Status

WAWF

WIPAccounting

RealProperty

DirectAccess PCard

Vision


24/52

UID Registry

UID Registry ConceptUID Registry Concept

PeopleRegistry

RPUIDRegistry

IUIDRegistry

OrganizationsRegistry

GFP AssetRegistry

PropertyAccountability:

Equipment,Parts, Materials

The IUIDCommon Key

Acquisition Full CostAccounting

The IUIDCommon Key

The IUIDCommon Key

FMSCountry

DMLS

Master Property

Plans

Depots

ParentChild Parent

Child

Rules

Keys

Context

ProgramRegistry

eGovCCR

FedREG

P&R:FMID

NII to incorporateUID in data

architecturein 2005

Full Integration of Force Structure, Personnel &Property Assets

Life Cycle Cost Improvements

Land/Facility

Site Geo-spatial

DoDAAC

Vision


25/52


26/52

Data Flow

UID 201: Using IUID

Data Flow


27/52

Data PrinciplesCreate data one time, reuse oftenProperty should be active in one accountability system at a timeData should be seamless throughout the item lifecycleAcquisition value will only be recorded and updated in the IUID registry;enabling the elimination of the DD1662IUID Registry will -- Never be an accountability system; but will be the audit trail of

current and previous accountability systems- Maintain basic/master IUID data, including acquisition value- Not maintain contextual data (full life cycle); the registry will point to

accountability system(s)- Will be updated with key lifecycle events

The concatenated UII will be the common data key across systems

Data Flow


28/52

IUID Data Capture for New Items via WAWFIUID Data Capture for New Items via WAWF

DoD Apps

Vendors

UDFDirect

Invoice,Receiving Report,IUID Data

IUID XML

Invoice,Receiving Report

Mark Items with IUID Data ElementsShipment Notice

Invoice

Wide AreaWorkflow

EDI

IUID Registry EDI Electronic Data InterchangeUDF User Defined Format

ACMSBSM

CAPSEBIZIAPS

MOCASMOCAS-RS

One PaySABRSSAMMS

WebUser Interface

Data Flow


29/52

Registry Data CaptureSupplyDepots

Operating Construct for IUID Systems EnvironmentOperating Construct for IUID Systems Environment

UID Registry Services

IUIDRPUIDGFP

Accountability& Value

Maintenance

Systems

PropertySystems

Config.MgtSystems

ExternalData

SourcesEPCRegistries

Catalogs

DoD LegacySystems

Updates for Changes Organization

Value Status

WAWF

WIPAccounting

RealProperty

DirectAccess PCard

Data Flow


30/52

Item Histo r y

IUIDRegistr

yInitial

Acceptance

Replace/Repair UIId

Component

Storage

Restor e for Use

Maint.

&Repair

Replace,Repair,UIId

ComponentDispose

Restor e &Use

Item Histo r y

Maint.&

Repair (Non-

IUID)

T r a n s p o r t

U s eU s e

I d l e

T r a n s p o r t

U s e

U s e

FMS

SURPLUS

DRMS

Reentry

Acquisition

Item LifecycleItem Lifecycle

Data Flow


31/52

Data Lifecycle Register at Birth

At time of acceptance for newprocurement items

At time of identification for items ininventory or operational use

Update during Use Change to part number or value

due to recapitalization or remanufacture

Change in accountability system Change of custodian Change to mark Change to components

Notify at Death Expend during operational use Disposed at end of useful life

Acquire

Store Use

Expend/Dispose

Maintain

Data Flow


32/52

Sample changes

Data Flow


33/52


34/52

Field Operation ConceptField Operation Concept

LogisticsSystems

Property

Systems

Maint.Systems

IUIDRegistry

Item level data visibilityData discovery serviceStandardized report formats, query formats for registryMay include authorization/authentication schemeManages ad hoc inquiriesKnowledge enablement transparent to the user

Passes information back to user

Passes updates back to registry

What is it?Where has it been?What is the items history?Who do I call?

How do I get another?

Information to User

Operational Functionality

EnablersAlias

Mark aliasSystem key aliasCatalog alias

Source system ID/Doc ID

Data Flow


35/52

Future IUID Data EnvironmentIssue items from inventory by UID or RFIDCapture Source, Target, and Accountable

system ID in Registry to enable data drill down inrelated systemsPassively tap relevant data during the normalcourse of businessDevelop net-centric presence and approach

Data Flow


36/52

Data exchange formats must be standardized and identifiable,known and repeatable (PLCS, XML, X12, etc.)Underlying data elements must be standardizedGating points definedTrigger events defined (how gate will recognize and pull IUIDdata)Operates without system or human interventionSystem access needs to be establishedAutomatic data extraction, data transformationFilter function; data cleansingPushes reports, posts reports, sets report formatsRobust test approach and test environment

IUID Data Receipt Approach

Data Flow


37/52


38/52

UID and RFID

IUID RFIDMark Item PackageTechnology 2D Data Matrix UHF RF w/EPC

encoding

Purpose Life cycle visibility Supply chain visibilityThreshold Value > $5000 + Ship To DDC; Class of

Supply

Implementation 1 Jan 04 1 Jan 05 +

Data Submission WAWF ASN + WAWF ASN

Separate but integrated initiativesDifferent technologies

Different business rules

Data Flow


39/52

Case Study 160th

Special OperationsAviation Regiment

UID 201: Using IUID

Case Study


40/52

IUID Value Proposition Background Can not install a new part until the partsmaintenance history is known

An engine requires rebuild maintenanceevery 2500 hours of operation If an engine is received that does not have

history with it Technician calls the hot line If still no info, engine must be rebuilt

Case Study


41/52

IUID Near Term Value Paper history not needed Scan IUID

System uses UII to reach into registry

Extract item data; identify maintenance system Registry reaches into source maintenance system Combined data transmitted back to requestor Data pre-populates the maintenance data viewed by

the technician

Case Study


42/52

IUID Long Term Value IUID enables condition based

maintenance Data aggregation and trend analysis enable

Predictive failure analysis Preferred sourcing Condition related failure analysis

IUID provides cross-service insight intoitem, maintenance and component history

Case Study


43/52

Case Study PCARRS Integration

UID 201: Using IUID

Case Study


44/52


45/52

1. Identify those events that we need to know about, where IUIDinformation is affected

Change in ownershipParent/child change

Change in form/fit/function (part number roll)Status change (demil, etc.)Change in accountable system

1. Develop a set of data standard requirements for systems to feedregistry data

2. Map events to existing transactions in architecture3. Modify transaction sets to carry IUID information4. Develop system migration strategy

Capturing IUID information

Case Study


46/52

PCARSS To-Be Data Flow

PCARSS*

WAWF-PT

GEX

IUIDRegistryAbandoned

ConsumedDestroyedLostScrapped

DonatedInactiveSold

DispositionXML

IUID XML/WAWF UDF Transfer/Receipt

Info via GEX

Change in

ownershipor status

* Enhance PCARSS to carry UII

Case Study


47/52

Benefits

UID 201: Using IUID

Benefits


48/52

Planning/SystemsEngineering

Acquisition &Procurement

Financial Management

Operations &Deployments

Logistics/MaterielManagement

Property Management

IUID

What items are needed?How are items marked?How is uniqueness assured?

What item am I buying?How do I buy the item?

How many items are there?How much are the items worth?

What items are available?Where are the items en routeto a location?

How is the item located?How is the item transported?How is the item managed?

What items are there?How are the itemsaccounted for?

Industry

Joint FinancialManagement Improvement

Program(JFMIP)

Other federalagencies; GSA, TSA,NASA

Joint Total AssetVisibility

DoD CFOAccountability

Configuration

Management

How is the tech data managed?

Secure Collaboration?Data Access/Sharing?

CoalitionPartners

MaintenanceManagement

What is the maintenance history of the items?Which items do I fix vs. discard?

Benefits


49/52


50/52

Similar Reasons + Standardization + Profitability . Early success stories

RR 99% parts being marked on Current Trent Engines Pratt and Whitney P&W Took the next step beyond just marking with integration

into business processes Serialization fat finger error input rate in production documentation

reduced 40% PW6000 achieved 20% Reduction in final assembly build time Improved quality of marks, tech data easily linked to part production

and acceptance test data etc etcIUID - ERP and E-Business Integration = Maximized Profits

Industry..IUID: Why Do It?

Benefits


51/52

1. Exploit automatic data capture to improve productivity2. Enhance precision of logistics, contracting, and financial

business transactions3. Consistently capture the value of items DoD buys, control

these items during their use, and improve item performance4. Track items in property accountability, inventory, and

financial management systems toward achievingcompliance with the Chief Financial Officers Act

5. Improve reliability, predictive maintenance capability, andfailure tracking

Results of Using IUID

Benefits


52/52

Questions?

UID 201: Using IUID

Date post:	08-Apr-2018
Category:	Documents
Upload:	kiran-naik
View:	229 times
Download:	0 times

Uid Forum - Uid 201 Final 4-19-06 (1)

Documents