IUID Scorecard - Under Secretary of Defense for Acquisition ...

IUID Scorecard - Under Secretary of Defense for Acquisition ...

IUID Scorecard Briefing Mr. David Ahern OSD/AT&L, Portfolio Systems Acquisition January 10, 2011 Agenda Welcome Dave Ahern Integrated Schedule for Policy Updates Rob Leibrandt Joint Staff (J8) UID Vision George Sprung Joint Staff Vision for Identifiers as a warfighter planning and execution requirement Service Brief (AF EDCL) Gregg Beecher Status of Intensive Item Management efforts Kathy Smith Item Traceability (Draft SOP, Federal Anti Counterfeiting) Rob Leibrandt IRB Conditions on AISs (Draft KPP Guide) LeAntha Sumpter Open Discussion 2 Integrated Policy Schedule Pre-FY2009 2000 -05 2006 2007 2008 1Q FY2009 2Q 3Q 4Q 1Q DFARS 2009-D043 Opened case, proposed DFARS rule DFARS 2010-D018 DARC opened case, proposed DFARS rule

DFARS 2009-D008 DARC opened case, proposed DFARS rule DFARS 20008-D050 DFARS 2008-D049 IUID Policy Clarification 4Q 1Q DoD approval to publish draft DFARS rule DARS opened case, proposed DFARS rule DFARS 2009-D023 DoD 5000.64 FY2010 2Q 3Q OIRA cleared proposed DFARS rule DoD approval to publish draft DFARS rule OIRA cleared proposed DFARS rule FY2011 2Q 3Q 4Q OIRA cleared proposed DFARS rule Case manager forwarded draft proposed rule to DAR editor Report Due 1/12/11 (1st ext.)

Published proposed DFARS rule in Federal Register (75 FR 75444) Opened case, proposed DFARS rule OIRA cleared proposed DFARS rule OIRA cleared final DFARS rule Opened case, proposed DFARS rule OIRA cleared proposed DFARS rule DAR editor received DoD & OIRA approval to publish draft final DFARS rule Currently published version (replaced August 13, 2002 version) Proposed completion timeline Policy Memo Formulation Policy Memo Signed DFARS 7003 Coordination Start DODI 8320.04 Technical Documentation Policy Memo Government Assigned Serial Number Marking Coordination Start Policy Memo Formulation The final rule published

Coordination Restarted Memo Signed 3 Global Force Management Data Initiative (GFM DI) Vision for using Unique Identifiers 10 January 2011 Joint Staff, J8 Models and Analysis Support Division Purpose /Agenda Purpose: Present to IUID Scorecard meeting attendees the Global Force Management Data Initiative vision for using Unique Identifiers Agenda: GFM DI Strategic Precept GFM DI Overview Task 1: Document, uniquely identify, and expose DoD authorized force structure and command relationships Task 2: Next Steps GFM DI Next Steps: Linking real people, equipment, locations, etc. to authorized force structure (e.g., spaces to faces; equipment authorizations to uniquely identified equipment) Underpins Department processes End-to-End (Example Use Cases) Priorities for Next Steps Information Brief 5 GFM DI Strategic Precept: Force Structure is the Common Reference Capabilities Risk Assessment GFM DI Programming/Budgeting $ Common Force Structure Representation

Programs Appropriations Military Force Structure B Execution Materiel Force Structure C Civilians Contractors Reporting Readiness DRRS/GVC C2 Metrics Force Structure D To integrate data across domains Universal identifiers enable data to be integrated to realize the power of the information Use authoritative Planning Force force structure in Adaptive Planning Structure A Plans Service/User Systems Timely, accurate, relevant information for senior leaders

Sharing data across domains empowers decision making 6 GFM DI Overview GFM DI documents and exposes authorized force structure and standardizes representation for use in Department information systems regardless of domain Divided into two tasks Task 1: Organization (Org) Servers Develop ADS for force structure data making it visible, accessible, and understandable Task 2: Next Steps Use of standardized representation enterprise-wide GFM DI is the Department-wide enterprise solution that: 1. Enables visibility, accessibility, and sharing of entire DoD force structure 2. Allows integration of data across domains and systems 7 Org Servers Document Every Element of DoD Force Structure and Command Relationships Authorized Force Structure Standardized data format Standardized rule set Uniquely Identifies: - Every space for equipment & personnel - All potential command relationships (ADCON, COCOM / OPCON, TACON) Doctrinal Organizations Crew-platformed equipment Billets Command Relationships GFM DI documents and standardizes the representation of organizations and command relationships (CY + 6 Yrs) GFM DI uniquely identifies organizational elements and time tags the data

8 GFM DI: Document Authorized Force Structure as the Basis for On-Hand and Execution GFM DI Task 1 What are you authorized? GFM DI Next Steps Task 2 -- Service/User Systems What do you actually What do you have to have? operate with? 16 16 16 4 4 14 3 Authorization data On-Hand data Authorized by Law and organized by the Components Property Books & Personnel Systems Org Servers ITAPDB, MCTFS, MilPDS, etc. 4 14

12 3 2 Execution data Readiness, Logistics & Personnel Systems DRRS, JOPES etc. 9 GFM DI Next Steps Feeder Systems eJMAPS TFSMS DRRS-N FMS GCSS-AF Raw Data Billet Data - Rank/Grade - MOS/AFSC - Skill Code - Skill Level - Service - Effective Date - Service Billet ID AIR FORCE ARMY ARMY MARINE COPRS CORPS NAVY Intel Community OSD OSD JOINT STAFF JOINT STAFF Org Servers

Types of Data Organizational Elements Command Relationships Net-Centric Enterprise Services Content Discovery Core Enterprise Service Metadata Registry NCES Service Registry Force Structure GFM XML Schema DOD Visible USA USAF USN USMC States ANG ARNG Accessible Elements tagged with unique identifiers per DODD 8320.3 Apply Organizational & Force Structure Construct (OFSC) Document hierarchies & command/support relationships (per the Service's Title 10 responsibilities) Force Structure is the central theme for integrating data Org Servers are the ADS for force structure authorizations per DODI 8260.03 Web Services Publish/Subscribe IAW Net-Centric Data Strategy Authoritative

Force Structure Data Data Consumers PPBE BFT Force Employment Intelligence Personnel Initialization Data DoD HR DMDC Adaptive Planning C2 Systems Financial Analytic Agenda DRRS Readiness OUID Registry Installations Logistics Battle C2 Systems Understandable 10 GFM DI: Linking OUIDS to Real Equipment, People and other identifiers OE A OUID OUID OE TK 1 Military MilitaryForce ForceTracking Tracking URN, UIC, ... M1 TK 4 UII C-2 M1 OUID M1A2

OE E-6 SSG 19K3O ASI: K4 Tank Cdr Gunner Equipment Equipment EDIPI SSG Smith RPUID Real RealProperty Property Loader OE: OUID: UII: RPUID: EDIPI: Driver Organizations Organizations &&Authorizations Authorizations Fort Hood Person Person URN: UIC: Organization Element Organization Unique Identifier Unique Item Identifier

Real Property Unique Identifier Electronic Data Interchange Personal Identifier Unit Reference Number Unit Identification Code 11 GFM DI Data Underpins Department Processes End-to-End (Example Use Cases) Force Structure documented in GFM DI Org Servers Congressional authorizations On-Hand Force Structure data in Service systems augmented with Org Server data COCMD Assignment through Automated Forces For tool Org Server data consumed by other DoD Systems Strategic Guidance Concept Development Plan Development Plan Refinement Force Structure in theater taskorganized by Combatant Commander Adaptive planning using real time availability of actual units

Force Structure (Units & Personnel) tracked across DoD systems using GFM DI data as common reference. Augmented Force Structure used in JCRM to allocate forces to current operations Force Structure data augmented with readiness data in Service systems Facilitates quick, easy data analysis to answer the Who, What, When, and Where. GFM DI data is common reference between tactical friendly force tracking systems and other IT systems GFM DIs authoritative organization data used to GFM DI data as common control access to key data resources (Attribute-Based reference facilitates Access Control) tracking of forces between disparate systems GFM DI leveraged during continued support by external Agencies 12 GFM DI Next Steps Priorities GFM DI Next Steps capabilities priorities Assignment [Apportionment Tables] Achieve GFM Assignment by end of FY12

Manpower and Personnel Readiness Allocation Command and Control Logistics & Movement Adaptive Planning Financial Electronic Health Records ABAC, EIAS, & EUI Achieve GFM Allocation by end of FY13 Military Force Tracking Memo. Services present plans for linking force structure to military force tracking system identifiers Defense Transportation System Memo. TRANSCOM present plan for linking force structure to DTS identifiers Accelerate GFM DI Next Steps to support ABAC role based authorities needed for DoD Secure Computing Environment by end CY11 13 GFM DI Contact Info J8 MASD POCs Col Erick McCroskey, USAF, (703) 697-7413 DSN 227-7413 Mr George Sprung, (703) 697-7544 DSN 227-7544 Maj Brian Balazs, USAF, (703) 697-7434 227-7434 GFM DI NIPRNet wiki page: https://www.intelink.gov/wiki/Global_Force_Management_Data_Initiative (Requires CAC or Intelink Account - see http://ra.intelink.gov) GFM DI SIPRNET wiki page: http://www.intelink.sgov.gov/wiki/Global_Force_Management_Data_Initiative_GFM_DI IChart webpage on AKO: https://www.us.army.mil/suite/page/180709 14

Headquarters U.S. Air Force Integrity - Service - Excellen ce Enterprise Data Collection Layer (EDCL) Update Mr Gregg Beecher AF/A4ID 10 Jan 2011 15 Current Architecture 16 EDCL Overview The Enterprise Data Collection Layer (EDCL) is an IT infrastructure hosted in the GCSS-AF framework Provides support for mobile computing and fixed infrastructure Automatic Identification Technology (AIT) devices Collects supply chain events from AIT devices Transform the events (as necessary) and forward the events to the appropriate AIS(s) Transactional system and not a persistent system of record for supply chain events TO BE BOTH EFFECTIVE AND AFFORDABLE 17 Full EDCL Architecture: Legacy Systems DAAS GCSS-AF EDCL A K A M A I T A

M CAS GloberRanger Server (Fixed Infrastructure) ES-S ACES IDM Sybase M-Biz Server (Mobile Computing) BPEL Engine CMOS IMDS DoD IUID Registry Base LAN RFID Infrastructure 18 EDCL BLUF Standardized Hand Held Program deployment Disconnected operations Portable Object Deployments (PODs) for scanners, wireless radios, communication ports, Common Access Card (CAC) Licensed browser Single data file for all Automated Data Collection (ADC) event data Business process layer to translate ADC event data to transactions back end systems can understand Enterprise IUID reading capability Enterprise RFID reading capability 19 EDCL Customers

ILS-S (Asset Management) CMOS (in-check with Asset Management) CAS (CAS AIT) GATES (Active RFID Reading) PIC NWRM (PIC ADC and Pickup and Delivery) Enterprise Part Marking and Registration (AFSDB) AFEMS Marking (Asset Inventory and Marking Tool) IMDS (Point of Maintenance) Depot (DRILS and LDMS) 20 EDCL v1.0 EDCL v1.0 Mobile Applications Framework to support mobile computing Operational in Production 19 Feb 2010 21 EDCL v1.5 EDCL v1.5 Fixed Infrastructure Builds onto EDCL v1.0 Incorporates Mobile Lighthouse (provides Tivoli Access Manager navigation) BPEL (set of distinct services forming an end-to-end process flow) Applications Combat Ammunition System (CAS) Asset Management/ES-S Positive Inventory Control (PIC) Operational in Production Aug 2010 22 EDCL v1.6 EDCL v1.6 AFSDB Builds onto EDCL v1.5

Incorporates Mark registration with DoD IUID Registry Support for SNT metrics database PIC Fusion support TMO In-Check Support Management Console Applications TRIAD2 AIMT GATES (EDCL v1.6.1) Mar 2010 Operational in Production date 7 Dec 2010 23 EDCL v1.7 EDCL v1.7 Device Management Builds onto EDCL v1.6 Applications Framework Diagnostic Toolkit POMX Upgrades M-Business v7.0 Oracle 11 SQL Anywhere 11 UltraLite 11 Enables Background Synchronization Planned Production date is Jun 2011 24 EDCL v2.0 EDCL v2.0 Clustering/FLB

Builds onto EDCL v1.7 Enables Sybase Clustering Failover Load Balancing Recovery Scenarios Planned Production date is TBD 25 Future Versions Integrate RTLS/WhereNet/AFGET Track and identify the location of objects in real time Systems that provides passive or active (automatic) collection of location information A2B UID Engine Lifecycle Asset Management UID-relevant events occur during asset lifetime Different applications witness these events Maintained UID engine to react to these events Insight and guidance as to current UID & DoD standards 26 Future Versions Integrate Enterprise UII Reading Capability Leverage EDCL to scan UII and return the pedigree information Enterprise RFID Capability Leverage EDCL to read and process RFID reads Sensor Tag (munitions) House the Sensor log data for analysis Provide analysis capability 27 Summary

An Enterprise Data Collection capability provides numerous benefits: Partition business rules to minimize or avoid updating legacy AIS implement technology driven business rules in device and process layer Shared data configurable routing of data destinations in process layer Aggregated data in a shared environment minimizes data transmissions while maximizing data availability Provides timely, accurate supply chain events to decision makers Increases the velocity and visibility of the AF Supply Chain 28 EDCL Benefits Partition business rules to minimize or avoid updating legacy AIS Shared data configurable routing of data destinations in the process layer Aggregated data in a shared environment minimizes data transmissions while maximizing data availability Provides timely, accurate supply chain events to decision makers Increases the velocity and visibility of the AF Supply Chain 29 eLog21 and AMT Benefits Manufacturers - Suppliers - Air Force Forecasting Acquisition Planning & Scheduling Inventory Mgmt. DLA or Depot Customer Service Require-ments Repair or

Storage Activity Transportation AIT 1. Mark it Unique Identification Automated data capture Improved data accuracy Reduced paperwork 2. Track it Deploy 3. Share it Reduced cycle-time Improved asset visibility and accountability Improved capacity utilization of tools Increased dispatch reliability End to End Visibility and Information Exploiting IUID Is Key to Logistics Transformation 30 Repair history Cycle time info Centralized documentation Increased maintenance reliability Transformation Drivers

Since DESERT SHIELD the Air Force operating at a wartime pace with diminished resources Average 2.3 million flight hours per year Total Active Duty fleet strength reduced by 36% Total Active Duty force reduced by 38% The Air Force must fundamentally transform Air Force logistics to address current and future operations Now engaged in multiple, simultaneous operations with a smaller force We support an aging aircraft fleet that requires more frequent upgrades, repair and maintenance Todays contingencies require flexible, modular, and scalable logistics processes TO REMAIN EFFECTIVE & RELEVANT 31 Status of Intensive Item Management: Implementing IUID in the Supply Chain Ms. Kathleen Smith OSD/L&MR, Supply Chain Integration January 10, 2011 Purpose Provide an overview of our progress implementing IUID in the DoD Supply Chain 33 The Proposed IUID Timeline (To be coordinated with Services) June 2008 3 Value Chains and 10 Logistics Nodes are analyzed creating recommendations back to JLB on IUID Implementation requirements and policy SCI and MPP lead the efforts to define and publish IUID integrated requirements in IUID Guidebook June 2008

8320.04 established requirement to uniquely identify personal property via UII June 2009 JLB directs the formation of an IUID Task Force February 2010 JLB approves IUID Task Force recommendations December 2010 DPAP Issues IUID Refinement Memo June 2011 Components complete comprehensive implementation planning based on IUID Guidebook March 2012 IUID Task Force Deliverables completed, IUID Guidebook published Implementation Planning Complete December 2012 MPP, SCI and DPAP complete revisions of DFARS and all DoD Issuances Components develop and field capabilities to intensively manage items in compliance with IUID Guidebook and Policies** **Components will have varying schedules for full implementation based on development cycles and funding requirements December 2015 Deadline to apply UII to applicable legacy items IAW updated policy & use UII for December 2015 34 lifecycle management JLB Task Force Analysis (April 2010)

Acq Log Planning Acq & Suppliers Distrib Centers OSD Navy DLA Intensive Item Management Transport Base & Fwd Supply Depot Maint Field Maint In Serv Engr & Log Analy OSD Army OSD OSD AF NWRM Classified Items

CSI Sensitive Property Book Property Accountability GFP MEV MDAP Tooling Product Lifecycle Management RCM / CBM Field Activities & Opns Disposal J4 DLA Functional Requirements Validated Requirements IIM -- 198 Requirements PA -- 231 PLM -- 305 Systemic Benefits Value Warranty Mgmt Config Mgmt Product Recall Counterfeit Parts Costs 35

JLB Decisions (April 2010) Current Policy Recommended Policy Mark all applicable items by 2015 and end items by 2010. Apply UII to applicable legacy items IAW updated policy. Use UII for lifecycle management NLT 2015. Links mark and use policy. Mark all sensitive, classified and controlled items. Apply IUID management to intensively managed & tracked items (IIM, new and legacy): Targets population can reduce IUID managed items by ~176M. Small arms, NWRM, sensitive and classified. Pilferable and CSI over $5K. Impact Mark all new acquisition and legacy items over $5K, and all mission essential, serially managed, and GFP items. Apply UII to these new acquisition and legacy items: All other items at discretion of requiring authority (RA). No change achieve management goals and benefits in orderly, cost-effective manner. N/A

Services and DLA budget for implementation costs. Services and DLA prioritize non-recurring engineering for IUID in budgets. Focus implementation strategy. End items. Mission essential items. Reparable items. Serially managed items. GFP. Non-intensively managed consumables by RA discretion. Targets items that provide greatest benefit and can reduce number of managed items by ~ 90M. Bottomline - Maintain current IUID policy for ME/GE (>$5000 unit cost) - Change current IUID policy for secondary inventory from >$5000 unit cost to focus on items with a unique item level traceability requirement 36 Concept of Operations for Implementing Item Unique Identification (IUID) Suppliers are required to assign a UII to the item and mark the item with a 2D symbol to carry the UII. Manufacturers/

Suppliers The Distribution Centers collect the UIIs from the exterior packaging or suspend until items can be validated. The Suppliers are required to have UII(s) available on the exterior of the packaging upon shipment. Maintenance activities remove items from the box and scan the 2D symbol to capture identity of the item during repair action. Forward Supply Distribution Centers UID Materiel Items are inventoried by UII (optional for some items) and eventually issued by UII to customers. UID Materiel If the items are owned by more than one owner, the items are stored by owner to facilitate proper inventory and issue. Field Maintenance UID Materiel The Forward Supply Activity collect the UIIs from the exterior packaging or suspend

until items can be validated. 37 RECEIPT USING IUID: DLA Distribution Center receives new procurement items by UII from the commercial vendor* Distribution Depots 1 Supplier enters item UII into WAWF, along with other shipment info Manufacturers/ Suppliers UID Registry 6 WAWF sends UIIs to the UID Registry 2 WAWF sends advanced shipment notice to customer system, incl. the UII(s) (DLMS 856) 3 System will prompt user to collect AIT off the exterior of the package DSS WAWF 5 Customer performs acceptance, sending a transaction back to WAWF (DLMS 861)

4 Customer performs a receipt, sending a transaction back to Item Manager via DAAS, incl. the UII(s) (DLMS 527R Receipt); generate an SDR if discrepant DAAS Item Manager 7 *This depicts FOB Destination Acceptance All business events impacting high-intensity managed items will be communicated to the IMM (DLMS 527R & DLMS 861) 38 INVENTORY USING IUID: Wholesale and below-wholesale activities perform inventory 1 Inventories are initiated by the Owner/Manager sending inventory requests (846P) to WMS (depot or local system accountable record), or by the WMS based on schedule or other requirement e.g., denial. Inventory line item will be defined as stock number + supply condition code + UII. IMM 3 Owner/Manager must verify reported UII against their record. Owner/Manager may request transaction history (846P) for analyzing inventory discrepancies

(WMS responds with the historical balance affecting transactions with all UII(s) included). UII mismatches require new reconciliation procedures between owner record and WMS accountable record. DAAS 2 WMS or local system When performing inventories, the WMS must verify, by physical location, all UII(s) against the accountable record and report differences to the owner/manager (947I) Details for reporting UII differences to the owner/manager must be determined (e.g., when only UII has mismatches no quantity or condition change) Mismatches on UII-- Causative research is required on any discrepancies found as a result of the inventory. Wholesale or belowwholesale activity 39 ISSUE USING IUID: DLA Distribution Depots issue items to customers based on receipt of a Materiel Release Order (MRO) Service Customer DLA Distribution Depot 3 DSS will issue items by NSN and ensure that UII(s) are included on the exterior package label DSS Customer

system 5 DLA will send a shipment status, incl. UII(s) to the customer (856S) Recipient performs a receipt, sending a transaction back to the Item Manager via DAAS, incl. the UII(s) (DLMS 527R MRA); generate an SDR if discrepant 6 4 DLA will send a MRC or Issue (945A/867I) with UII(s) to the IMM DAAS 7 All business events impacting high-intensity managed items will be communicated to the IMM (945A, 867I and 527R MRA) Item Manager 1 Service customer will send a requisition (DLMS 511R) for a quantity of an NSN (not by UII) to an IMM 2 IMM will send a MRO (DLMS 940R) to the DLA Distribution Depot 40 Definition of Serialized Item Management By UII

SIM by UII: Management and tracking of a select population of items that have a unique item level traceability requirement Unique item level traceability is defined as the requirement to trace lifecycle management events related to acquisition, property accountability, storage, operation, maintenance, safety, physical security, retirement, and disposal by each individual item Individual item is defined as a single instance of a stock-numbered item or a single assembly/ subassembly The need for unique item level traceability requirement is determined by the manager of the item (IMM for consumables and PICA for reparables) Existence of a manufacturers serial number does not constitute a requirement for SIMmust meet at least one of the following: DoD serially-managed sensitive, DoD serially-managed critical safety, and/or DoD serially-managed pilferable items All depot-level reparable items Any items that the requiring activity decides require unique item level traceability In scopesecondary inventory governed by DoD 4140.1-R 41 Levels of Supply Management Intensity Standard-intensity serialized management by UII Managed by UII in accountable records (storage activity) DoD serially managed items that are classified confidential, sensitive or pilferable or DoD serially managed critical safety items or depot level reparables High-intensity serialized management by UII Managed by UII in accountable records (storage activity) and owner records (ICP) DoD serially managed classified secret and above or NWRM FLIS code under development will enable standard and high intensity 42 Standard-Intensity Serialized Management t en y or N by

Worldwide Inventory for owned materiel by NSN X and Qty NSN X - Qty 2 Location: Supply Base NSN X - Qty 1 Location: Maintenance SN inv e id R) ldw 527 r o ( tr W f 3 po ty o e R Q as IMM pe UIIs ship t r o p e R Repo rt DLA Distribution Center Inventory by Qty (By UII is Optional) Receipt, Store and Issue by UII UIIs s h d (856S

ipped Supply Base: Receipt, Store, Inventory and Issue for NSN X by UII ) Supply Activity Base 1 (856S ) Maintenance Base: Store UII at receipt, capture UII during repair action Report UIIs shipped upon Materiel Return (856R) Mismatches are researched by UII Accountable Records By UII Maintenance Activity Base 2 Validate correct UII received, Resolve UII mismatches, discrepancies 43 High-Intensity Serialized Management Owner Records By UII Receive NSN X with Qty 3 UII #1 UII #2 UII #3 UID Materiel DLA Distribution Center

Receipt, Store, Inventory and Issue by UII Mismatches are researched by UII I UI y b ry o t en v n I de i ldw or tW or p I Re rt UI o p e R ed shipp IMM Worldwide inventory for owned materiel by NSN X and UII: UII #1 Location: Supply Base UII #2 & #3 Location: Maintenance Base Daily reconciliation by UII Resolve UII mismatches, discrepancies Supply Activity Base 1 Supply Base: Receipt, Store, Inventory and Issue for NSN

X by UII: UII-#1 Accountable Records By UII R epor t 2 U shipped IIs Report UIIs shipped upon Materiel Return (856R) Maintenance Activity Base 2 ALL SUPPLY CHAIN NODES MANAGE AN ITEM BY UII Maintenance Base: Receipt, Store, Inventory and Issue for NSN X by UII: UII #2 UII #3 Validate correct UII received; Resolve UII mismatches, discrepancies 44 IUID Policy Today Modernize acquisition, logistics, and property management Automated Information Systems with UII requirements including use of the IUID Registry Standard UIT programs shall be established within the Department of Defense for selected items to maintain visibility of each uniquely identified asset for the primary purpose of inventory control and/or engineering analysis. SIM programs shall facilitate the effective management of populations of select items throughout their life cycle using data associated to a unique item by its UII. DPAP SCI Focuses secondary inventory on DoD serially-managed sensitive, pilferable and CSI items and depot level reparables, removing the current generic $5000 per item requirement

MPP DPAP 45 IUID Policy Tomorrow Will be updated to reflect JLB Task Force maintenance workshops Will be updated to reflect refinement memo requirements Unique item level traceability is required for all DoD serially managed items that are controlled inventory items, all DoD serially managed critical safety items, all depot level reparables and all NWRM using a UII MPP DPAP SCI IUID Guidebook SCI L&MR Components shall account for all DoD serially managed items that are CII, or DoD serially managed critical safety items or NWRM by UII within NSN or by serial number until such time as system changes implementing IUID are complete. These items shall be assigned a UII in accordance with DoD Instruction 8320.04 (Reference (d)) and a level of management intensity commensurate with the risk (high and standard). Detailed procedures such asThe ICP system will receive update from receiving activity on UII(s) received (i.e. 527R transaction) 46 The Way Ahead FY2010

4QFY10 FY2011 1QFY11 2QFY11 3QFY11 4QFY11 FY12 & Beyond 1. Policy/Guidance Updates 2. Cost Effective Item Identification 3. Develop/Refine Business Rules Across Logistics Enterprise 4. Develop/Refine Standard Data Exchanges and Mechanisms 5. Rationalize Cost of Management Intensity Level with Item Population 6. Obtain Approval for DLMS changes, FLIS Codes & Implementation CONOPS 9. GO LIVE! 7. Implementation Planning 8. System Development 47 Next Steps SCI and MPP, with comment from Services and DLA, develop Guidebook June 2011 SCI, MPP and DPAP revise DoD issuances and DFARS complete by Dec 2012

Services and DLA define UID requirements for their ERPs thru 2QFY12 Components develop and field capabilities to intensively manage items in compliance with IUID Guidebook FY12 and beyond Services and DLA continue with legacy marking efforts complete by Dec 2015 48 Item Traceability: Federal Anti-Counterfeiting Efforts Mr. Robert Leibrandt OSD/AT&L, Defense Procurement & Acquisition Policy January 10, 2011 Framework for Discussion The Threat Our Vulnerabilities Potential Consequences Task: Develop DoD Response(s) to: Department of Commerce Report GAO Reports Continuing Media Coverage 2010 National Security Strategy Draft Legislation NDAA 2011 Executive Order Congressional Interest TASK: Counter effects of Counterfeits in DoD Counterfeiting is a Daily Media Topic and raises Congressional interest.

*Challenges in Acquisition & Procurement *Uncertainty with Respect to Numbers * Lack of Trust in Supplier Base 50 Risk Factors Part Designation Mission critical components; Safety Items Controlled Inventory Design, Production, Sustainment, Intellectual Property Control Government Contractor Traceability Prime, Sub-tier Suppliers, Government Inventory Intensity of Item Management High: Detailed Chain of Custody Medium: Certificate of Authenticity Low: Range of Existing Receipt and Acceptance Regulations 51 Focus Areas [Lead] Focus Areas Course of Action Standards Industry/ Engineering Standards DoD-IP NASA Procurement Contractor Selection: Evaluation Factors, Past Performance

[DoD-DPAP] Qualification Requirements ( QPL, QML, or QBL) FAR Part 9 [ DoD-DPAP] Traceability Contractor Purchasing System Reviews [?] Require Program/Item Managers to determine susceptibility to anti-counterfeiting in their risk management planning for any requirements and to ensure authenticity of delivered items including critical embedded components Leverage existing higher level quality requirements to invoke anti-counterfeiting by applying industry standards (e.g., SAE AS 6081, SAE AS5553, SAE AS XXXX) Primary Support Reporting (e.g., GIDEP) [DoD] Support Support Primary Establish requirements for potential suppliers to demonstrate traceability to the design/manufacturing authority

when it is commercial Primary Support Support Support Primary Establish an Notification/ Information Sharing Capability (e.g., GIDEP) Marking/ Identifying [DoD-DPAP] Primary Establish the regulatory framework to contractually require stronger anticounterfeiting procedures to be taken by suppliers Require documented flowdown of traceability requirements from prime contractors to their suppliers Traceability [DoD DPAP] Outside of Scope of Jan 19th Collaboration, Training, & Agency Oversight [NASA] Support

Primary Support 52 Focus Areas [Lead] Outside of Scope of Jan 19th Focus Areas Standards Course of Action Industry/ Engineering Standards Do DIP NASA Procurement Contractor Selection: Evaluation Factors, Past Performance [DoD-DPAP] Implement item and package marking approaches that enable the government to ensure the item delivered is an authentic item, meets performance specification and can be used to verify its traceability/authenticity during its lifecycle Support Establish ad-hoc group of federal agency and industry advisors from existing industrial

base and government bodies to advise on proposed regulatory requirements, standards, training, etc. Consider establishing a government/industry consortium of test/evaluation facilities to share best practices in anti-counterfeiting techniques Contractor Purchasing System Reviews [?] Traceability [DoD-DPAP] Marking/ Identifying [DoD-DPAP] Support Primary Reporting (e.g., GIDEP) [DoD] Collaboration, Training, & Agency Oversight [NASA] Primary Support Primary Establish training and outreach strategy and identify resources (e.g. NASA training)

Consider legislation that clarifies federal rights to hold suspect parts, withhold payment, dispose of suspect parts and recoup costs incurred Qualification Requirements ( QPL, QML, or QBL) FAR Part 9 [ DoD-DPAP] Traceability Primary Primary 53 Status of Next Steps Dec 15th - Joint meeting with DoD/NASA/GSA to further refine the proposed course(s) of action, develop a high level strategy document, establish action leads and prepare for next ad-hoc group meeting Jan 14th Next ad-hoc group meeting OMB/DoD/NASA/GSA to initiate the proposed courses of actions through sub-group action leads Jan 19th Federal outreach to Agency and Industry session to share best practices and information 54 Planning for Jan 19th Location: Rosslyn, VA Invitees Agencies [OMB, OSD, NASA, GSA, DCMA, DOE, DLA, NRO, DOJ, MDA, DHS, DOC, HHS] Associations [CODSIA, AAQG, ASQC, INCOSE, SAE, Semiconductor Industries Association (SIA)] Read Aheads Informational Brief Questions to consider for each of the following focus area Traceability and Reporting Standards Procurement

Hyperlink to GAO Report and Commerce Report 55 Agenda for Jan 19th Notional Agenda for Outreach Session Opening Situational Awareness Discussion of Approach IPEC DoD and NASA Introduction by Focus Area Leads General Discussion Morning Session: Leads-facilitated discussions with prepared questions Traceability and Reporting (DoD-DPAP/SCI) Standards (DoD-IP/NASA) Procurement (DoD/OMB) Break Afternoon Session: (Repeat of morning session with different participants) Leadsfacilitated discussions with prepared questions Factual Outbrief/Minutes* of Morning and Afternoon Sessions Next Steps Collaboration, Training and Outreach Strategy (NASA)

Focus Area Development and Coordination 56 IUID Scorecard Update (Army) 10 Jan 2011 Policy Implementation Status AR 70-1 Army Acquisition Policy (release planned by 2Q FY11) AR 750-1 Army Maintenance Policy (adjudicating comments) AR 710-2 Army Supply Policy (release planned by 4Q FY11) US Army Materiel Command (USAMC) IUID Implementation Plan (released Nov 2010) Installation Management Command IUID Implementation Plan (under Army Staff review) Draft Policy Memorandum Legacy Data Plate Marking (release planned 2Q FY11) Legacy Marking Guide (release planned 4Q FY11) Resource Formulation Guidance for POM 12-17 Implementing IUID Business Processes in ERP Environment DFARS 252.211-7003 (IUID clause) Army Regulations Incorporating IUID

Contract Compliance Rate DFARS 252.211-7007 (GFP) USAMC Marking Management Pilot Identifying gaps and redundancies (materiel, technical, policy and business process requirements) Communication and Outreach ALT Magazine Army IUID IPT Workgroup established 01 Dec 2010

Tests integration of Enterprise Software Solution Leverages geographically based marking management Pilot kick-off in US Army Europe (USAEUR) planned 2Q FY11 Challenges: Modeling major IUID impacts in ERPs IUID Newsletter 4QFY10 16% of Contracts where GFP is provided included this clause Compliance is Up from 15% in 3QFY10 Opportunities & Challenges 4QFY10 94% of Contracts that met IUID criteria included this clause Compliance is Up from 93% in 3QFY10 Developing IUID business processes Acquiring, fielding and supporting AIT Infrastructure End-to-End use of IUID throughout the Army Enterprise Developing automated tools to track metrics for improved oversight Issues & Concerns IUID requirement should be in Capabilities Documents (Include IUID in CJCSI 3170.01 & 6212.01) DCMAs ability to monitor compliance for new items AIT and AIS readiness to use IUID 57

IUID Scorecard Update (USAF) 10 Jan 2011 Policy Publication Status AFPD 63-1/20-1: Acquisition and Sustainment Life Cycle Management Published 3 April 2009 Implements DODD 4140.1, 4151.18, 5000.01 Revision Drafted; in Technical/Functional Coordination Estimated Publication in Summer 20 11 AFI 63-101: Acquisition and Sustainment Life Cycle Management Published 17 April 2009; last updated: 10 Oct 10 Implements : DODI 5000.02; DODM 4140.01; DODD 8320.03; DODI 8320.04; DODI 4151.19 Complete rewrite in progress Draft update: DFARS 252.211-7003 (IUID clause) 4QFY10 86% of Contracts that met IUID criteria included this clause Compliance is up from 54% in 2QFY10 DFARS 252.211-7007 (GFP) Incorporates OSD Policy Memos: MDAP Tooling , GFP, and CAP Aligns IUID process flows to SEP processing Anticipated guidance: Technical Document s, JLB, and FMS Estimated Publication in Summer 2011 AFPAM 63-128: Acquisition and Sustainment Life Cycle Management Published 5 October 2009 Complements AFI 63-101 with detailed guidance

Draft updates align with AFI 63-101 and AFI 63-1201 SEP Processes Estimated Publication in Summer 2011 AFI 63-131, Modification Program Management Published 6 November 2009 Used with AFI 63-101 & AFPAM 63-128 IUID Policy on Modifications Draft Revision in Technical Functional Coordination Estimated Publication in Summer 2011 AFI 20-110, Nuclear Weapons-Related Materiel Management Published 20 August 2009 AFI Revision in mandatory coordination, anticipate publishing in Feb 11 AFI 63-1201: Life Cycle Systems Engineering, dated 23 Jul 2007 Being revised as AFI 62-101, Systems Engineering Estimated revision publication date Dec 2011 SEP policy revisions supplement AFI 63-101 detailed IUID guidance 58 Contract Compliance Rate 4QFY10 60% of Contracts where GFP is provided included this clause Initial Baseline Report Opportunities & Challenges IUID Implementation planning--legacy assets Integrate into a SEP review /approval process flow Maximizing opportunistic marking of prioritized assets ECSS MSC AIDC IPT with AF Enterprise Resource Planning (ERP) System to ensure IUID synchronized with ERP rollout Marking ~2.3M Class VII items

Issues & Concerns Standardized FMS Exemptions Pending Guidance ADPE IUID Scorecard Update (DON) 10 Jan 2011 Service/Agency/Functional Policy Implementation Status Directive/Instruction Contracting Direction PEDRP/PQDR is IUID enabled for all services, auto populates based IUID interface with Registry to capture delivered item deficiencies Should Cost Model developed for Independent Government Cost Estimates Infrastructure AIT/AIS Developed POM 12 Issue Paper for enablement of Business Systems (resource sponsor rejected) Developing DON IUID AIS implementation roadmap based on functional areas of greatest benefits (in conjunction with resource sponsors) USMC developing Capability Development Document for IUID as a POR

DASN is working with US Fleet Forces Command (US FFC) and AIT program office to standardize handheld scanner for shore establishments and USFFC US FFC funded to equip fleet with scanners and software to complete legacy marking in 3 years, and start using IUID immediately NAVSUP purchase of 2,000+ scanners, in support of Navy ERP rollout Shipyards/Depot developed plan for IUID compliance of Plant Property Equipment Developed a standardized approach to accelerate IUID AIS enablement in support of financial auditability (DASN FMO funded, in progress) Progress made on GCSS-MC plan for compliance. USMC readiness AIS (MERIT) and major logistics repository (MDR) will be IUID compliant by June 2011. Communication and Outreach Published quarterly DON IUID Journal Sponsored DON IUID Enterprise Training Symposium (DIETS4), 225 participants Jan 11-13, 2011 (DIETS3 also 225 participants) BGen Simmons, USMC, to be keynote speaker at UID Forum in March 2011 DFARS 252.211-7003 (IUID clause) 2QFY10 96% of Contracts that met IUID criteria included this clause DFARS 252.211-7007 (GFP) Contract monitoring for GFP n/a Opportunities & Challenges Compliance Program and Budget Guidance DON IUID Implementation Strategy draft (adjudicating comments)

DON Marking Guide (released December 2010) PEO LMW NOTE 4105, Item Unique Identification (IUID) Implementation Guidance and IUID Plan Template (released 9 Dec 2010) Naval Shipyard Plant Equipment Corporate Policy for IUID (draft) Contract Compliance Rate Developed Low Cost Alternative for IUID enablement of Business Systems (resource sponsor considering) IUID Field Receipt & Acceptance demonstrated in pilot for WAWF, meeting all OSD requirements USMC Automated Armory pilot to be implemented in several deployed units with II MEF deployment Metrics Monitoring Program Legacy Item Get Well Plans for Class VII items (31 December 2010) Resources Resourcing of Supply and Maintenance systems will be addressed after the Navy Logistics Solution Analysis of Alternatives is completed. This will provide the logistics AIS roadmap that determines which legacy AISs will be retained and integrated, and should have IUID enabled, with the N40 caveat if a business case is made for IUID enablement. Earliest opportunity is POM 14. Issues & Concerns Contract Clause Compliance - Contracting Officers are circumventing the intent of the DFAR clauses. Examples are PEO CARRIER CVN 21, 78 Class: SUPSHIP MSMO & CARRIER Overhaul/Repair; PEO SUBS, AN/WLR-8 and AN/BRD-7 ESM; and PEO SUB VIRGINIA CL DASN is working with the Deputy Under Secretary for Business Transformation to address business systems that have an overdue

IRB/DON IUID Condition. Efforts are underway to develop a better way to achieve the desired outcome, thus obtaining commitment from the resource sponsors to comply with existing policy. 59 IUID Scorecard Update (DLA) 10 Jan 2011 Policy Publication Status DFARS 252.211-7003 (IUID clause) implemented in contract writing systems for use when IUID technical requirements are identified by customer Technical Quality Memo (Q- Tip 2009-06) provides direction to product specialist for inclusion of IUID requirements in item descriptions Upgrade of DLA Form 339 (June 2009) to include a drop down menu that addresses the IUID marking requirement which provides the user to conduct searches based upon the IUID requirement Contract Compliance Rate DFARS 252.211-7003 (IUID clause Opportunities & Challenges IUID Implementation for Items that do not require engineering analysis capital equipment Issues & Concerns Risk of marking items without technical

review/requirements Verification of IUID marking on receipt The marking of legacy items impact on the distribution operations and the cost to do this work Contracting with dealers and distributors when IUID marking applies ) Implementation in contracts for items where IUID marking is required. Acquisition Policy is mandating compliance per the DFARS clause and directives. _ Automated buys valued up to the SAT currently include the clause. Marking plan complete Data labeling equipment purchased Projected completion date is Aug 2012 IUID implementation for the Marines Establishing the list of NSNs that require IUID marking Original list of 88,00 NSNs that the Marines have design authority for has been scrubbed and 1,855 NSNs will require IUID marking 40 NSNs are already being marked by the Marines 646 NSNs are Non-Critical and can be marked with labels 312 NSNs have a tech data package Marines will provide DLA with an official documentation listing what NSNs require IUID marking 60 IUID Scorecard Update (SOCOM) 10 Jan 2011 Policy Publication Status SOCOM Directive 70-1 (Acquisition Management System Policy) March 2010

SOCOM Directive 70-2 (Item Unique Identification) Directs Implementation Plan Directs DFARS Clause Register pedigree data Original version dated Jan 08 Draft Updated Version in staffing SOCOM Directive 700-2 (MFP-11 Funded Asset Visibility and Opportunities & Challenges Special Operations Forces Support Activity (SOFSA) IUID Marking Lab Lexington, KY Lab has produced 266K IUID marks (2005-10) Portable lab produced over 6,000 marks Collect Metrics/Interface with DOD Registry Ops Tempo - Limits access to mark legacy assets Funding Challenges Insufficient funding to support a HQ USSOCOM oversight capability Component commands lack funding to mark non-program of record assets Accountability) July 2008 SOCOM IUID Database Initiative

Reinforces IUID requirements for PM s Contract Compliance Rate Issues & Concerns DFARS 252.211-7003 (IUID clause) Metrics collected quarterly 321 of 332 contracts DFARS compliant Compliance 96% in 4th Qtr 10 IUID Implementation Plan Review 71 programs reviewed 58 programs have current plans (82%) DOD Registry Unable to sort DoD registry to only identify SOCOM specific assets Inconsistent UIIs constructs by OEMs - causes duplicative marking by SOFSA and/or components. 61 Backup 62 GFM DI Problem Statement

We need Global Force Management Data Current Unit Locations Event data Operational Availability Total US Inventory Historical archive Timely, reliable, and authoritative What forces do I have? Where are the forces today? What residual capability exists? How do I manage forces, manpower, & equipment from acquisition to end of service? What happens if? Department information technology systems: 1. Developed separate force structure representations for different domains 2. Designed to source and track forces at a higher level than we currently execute 63 Leadership Guidance NEED GFM DI PLAN GFM DI USE GFM DI FUND GFM DI IMPLEMENT GFM DI To support Global Force Management, the CJCS will develop...a joint hierarchical way to organize force structure data for integration across Service lines. SPG, Mar 04 The CJCS with USD (P&R) will provide the SecDef a plan to make force structure authorization data visible and accessible by Sep 07 and address the resources to reach

full operational capability by Oct 09 JPG VII, Jun 06 Only force structure data authorized under this Instruction [GFM DI data] is used for any force structure representation DoDI 8260.03, Organizational Force Structure Construct for GFM, Aug 06 Services fund and complete GFM DI force structure authorization data by the end of FY 08 Program Decision Memorandum III, Dec 06 GFM DI Implementation Plan briefed to DAWG 9 Mar 07, DepSecDef approved 26 Mar 07 update DAWG Fall 07 (JS, OSD, all Services planned to document to the billet level) Capability Development Document for GFM DI Increment 1 - JROCM signed 28 Jan 08 Provide DepSecDef with the funding implications of GFM DI Next Steps across the FYDP RMD 700, Dec 09 IMPLEMENT GFM DI Next Steps It is DoD policy that all relevant Department systems use authoritative GFM DI force structure data as central theme for integrating data throughout DoD 64 Task 1: Org Servers Feeder Systems eJMAPS TFSMS DRRS-N FMS GCSS-AF Raw Data Billet Data Rank/Grade MOS/AFSC - Skill Code - Skill Level - Service - Effective Date - Service Billet ID - AIR FORCE ARMY ARMY COPRS MARINE CORPS

NAVY Intel Community OSD OSD JOINT STAFF JOINT STAFF Org Servers Types of Data Organizational Elements Command Relationships Force Structure DOD Net-Centric Enterprise Services Content Discovery Core Enterprise Service Metadata Registry NCES Service Registry GFM XML Schema Visible USA USAF USN USMC States ANG ARNG Elements tagged with unique identifiers per DODD 8320.3 Apply Organizational & Force Structure Construct (OFSC) Document hierarchies & command/support relationships (per the Service's Title 10 responsibilities) Force Structure is the central theme for integrating data Org Servers are the ADS for force structure authorizations per DODI 8260.03 Accessible Web Services

Publish/Subscribe IAW Net-Centric Data Strategy Authoritative Force Structure Data Understandable 65 OFSC Basics: Command Structure The Fundamental Tree Structure of the OFSC Command Structure: The organizational hierarchy Command Structure through which command is exercised. A command structure is predicated upon command authority, or the concept of designated leadership authority. This is based on the military premise that anytime people are present, someone is in charge. A Is-composed-of B D C F E G H I J K

L M N O P Q R S T U V W Principle: Principle: Stable StableNodes, Nodes, Dynamic DynamicLinks Links Formally, a command structure is a set of composition associations that connect together any type of OE [doctrinal, crews, or billets] and whose purpose is to denote aggregation due to command authority (but not limited to formal command i.e., it extends to any level of leadership). Billets can not be decomposed into other OEs. Therefore, billets are always leaves (at the bottom) of a composition tree, like a command structure. An organization tree defined by a command structure denotes a unit. Many different units can be built from a common set of OEs via different command structures.

66 OFSC Basics: Organization Elements (OEs) & C2 Relationships Billet: Crew: An OE with a (planned) 1:1 correspondence with a person An OE with a 1:1 correspondence with a platform or system that requires operation by one or more persons and transports those persons. Doctrinal: An OE that serves as an aggregation point due to doctrine, tactics, techniques, or procedures, or business practices. A is_composed_of Regiment B B C Squadron C D Company D H 1 I 2 3 E F J 4 5 K 6 7 G

L 8 9 M 10 11 N 12 13 O 14 15 16 BILLETS 67 OFSC Basics: Time is a Discriminator in the OFSC a Base and b and a c Tx A c a B a c E c

c C c b B a D b F b Ty C c C c a Tree Filtered on Add Labels to Nodes & Links c G a Tx a and c c A c c E c G a and

c c a b c A c a b and E c b D b b F b Tree Filtered on b and c Ty Use Time Intervals as Labels c a T1 T2 T1 Tx T2 Ty T3 b

T3 68 Proposed Definitions for UID Items Standard Intensity The owner system does not have visibility into the exact location of a particular UII, but the local storage system does and can locate it if queried. Storage activities receive new procurements, recording UII(s) for reporting UII acceptance discrepancies. Storage activities receive, store, and ship by UII, but are not required to regularly perform physical inventory by UII or report changes in status/condition/location to the owner system. Mismatches identified by receiving activities must be reported under Discrepancy Report business rules, and corrective action taken where appropriate. High Intensity The owner system will have worldwide visibility into the exact location of a particular UII at all times and can locate it if queried. Storage activity and owner records must be synchronized and differences in their records be immediately reconciled by UII. Storage activities receive new procurements, recording UII(s) reporting UII acceptance discrepancies. Storage activities receive, store, ship, and perform physical inventories by UII, and report changes in status/condition/location to the owner system by UII. 69 69 Identifying IUID items - Proposed IUID Flags Assigned to each NSN requiring SIM using the UII, as determined by the National Inventory Control Point (NICP) Indicates to all DoD systems, and practitioners using these systems, the level of management intensity required for the individual items within each IUID-eligible NSN Standard-intensity serialized management by UII managed by UII in accountable records High-intensity serialized management by UII managed by UII in accountable records and owner records Interim IUID Flags may be necessary Applies to NSNs that require serial management by IUID but on which legacy assets on

the NSN have not yet been IUID-marked Enables the supply system to manage the item by the NSN with the legacy serial number in the interim until all legacy assets on the NSN have been marked with a UII Once the legacy assets on the NSN have been marked with a UII, the flag will be updated to full serialized item management using the UII 70 70 Proposed IUID Flags - Detail CODE 1A EXPLANATION Proposed Standard-intensity serialized management by UII (INTERIM). Applies to NSNs that require serial management by IUID but on which legacy assets on the NSN have not yet been IUID-marked. This flag enables the supply system to manage the item by the NSN in the interim until legacy assets on the NSN have been marked with a UII and contracts have been updated to include the IUID clause. Once the legacy assets on the NSN have been marked with a UII, the flag will be updated to serialized item management by UII using the Standard-intensity flag below. 1B Proposed High-intensity serialized management by UII (INTERIM). Applies to NSNs that require serial management by IUID but on which legacy assets on the NSN have not yet been IUID-marked. This flag enables the supply system to manage the item by the NSN in the interim until legacy assets on the NSN have been marked with a UII and contracts have been updated to include the IUID clause. Once the legacy assets on the NSN have been marked with a UII, the flag will be updated to full serialized item management by UII using the High-intensity flag below. 2A Standard-intensity serialized management by UII. The owner system does not have visibility into the exact location of a particular UII, but the local storage system does and can locate it if queried. Storage activities receive new procurements, recording UII(s) for reporting UII acceptance discrepancies. Storage activities receive, store, and ship by UII, but are not required to regularly perform physical inventory by UII or report changes in status/condition/location to the owner system. Mismatches identified by receiving activities must be reported under Discrepancy Report business rules, and corrective action taken where appropriate. 2B High-intensity serialized management by UII. The owner system will have worldwide visibility into the exact location of a particular UII at all times and can locate it if queried. Storage activity and owner records must be synchronized and differences in their records be immediately reconciled by UII. Storage activities receive new procurements, recording UII(s) reporting UII acceptance discrepancies. Storage activities receive, store, ship, and perform physical inventories by UII, and report changes in status/condition/location to the owner system by UII. 71 71

Recently Viewed Presentations

  • HELLENISTIC ASTRONOMY - Purdue University

    HELLENISTIC ASTRONOMY - Purdue University

    ROMAN EMPIRE. 31 BCE — 476 CE. collapse of Republic. imperial rule. religious cults "fall" of Rome. Alexandrian Museum and Library • Alexandria founded 331 BCE • state patronage of arts and sciences under Ptolemaic rulers • Museum and Library...
  • Service Provider requirements for 802.11n

    Service Provider requirements for 802.11n

    Trialing FTTH Verizon announces FTTP at ~19.5M over fiber (video separate from data and voice) Plan to move to GPON in future Bell Canada announces initiative to deliver 20-25M DS over copper KT deploys 50M DS/10-30M US over copper, moving...
  • Overview - University of Calgary in Alberta

    Overview - University of Calgary in Alberta

    This lighting scheme is often associated with "hard-boiled" or suspense genres such as film noir. Mise-en-scene - lighting High-Key Low-Key Mise-en-scene - game lighting High-Key Low-Key - Dead Space Space The representation of space affects the reading of a play...
  • Correcting Miscommunication: Head Injury among Criminal ...

    Correcting Miscommunication: Head Injury among Criminal ...

    Program Advisory Committee (PAC): Membership . A key component of this Research Program is the promotion of meaningful cross-sectoral engagement with knowledge users, including persons with lived experience, caregivers of persons with lived experience, and service providers through collaboration and...
  • The Implications of the New International ISO Standard for ...

    The Implications of the New International ISO Standard for ...

    The Presenter - Professor Tony Bendell . ... The requirements for this in ISO18404 for the three levels of Six Sigma personnel are complex, and you should refer to the standard for full details. However, the following slides provide a...
  • Wonders Of The Modern World - hgsitebuilder.com

    Wonders Of The Modern World - hgsitebuilder.com

    Then, his son, Lincoln took up the incomplete project and completed carving Roosevelt's face.# Though the original design was meant to sculpt the 4 presidents till their waists, but time and money could only accommodate for the carving of their...
  • Integrating Theory and Practice Through the Field Instruction ...

    Integrating Theory and Practice Through the Field Instruction ...

    What is the Field Instruction Program? An integral part of the Social Work curriculum. It is a supervised fieldwork, the kind of experience where the student begins to translate theory into actual practice under the guidance of a trained and...
  • Enabling Sales Effectiveness Through Data Quality and Business

    Enabling Sales Effectiveness Through Data Quality and Business

    Enabling Sales Effectiveness Through Data Quality and Business Process Integration Matt Lawrence Wind River Systems Strategic Transformational Change Dirty Customer Data Technology Roadmap Combined Project Scope Upgrade Siebel Sales from 6.3 the 7.8 platform, Streamline the Sales process from Lead...