0
Unique Identification (UID) of Tangible Items
Agenda <ul><li>Overview </li></ul><ul><li>Technical Specifics </li></ul><ul><li>UID Lifecycle </li></ul><ul><li>UID Organi...
Overview
<ul><li>To create a policy establishing a strategic imperative for uniquely identifying tangible items relying to the maxi...
Strategic Purpose of UID is to… <ul><li>Integrate item data across government and industry asset management systems, resul...
DoD’s Approach to UID <ul><li>The Department of Defense (DoD) established a joint international/industry/government Integr...
Technical Specifics
What is U nique  ID entification  (UID)? UID is . . . . . . the set of data for tangible assets that is globally unique an...
Key Terms <ul><li>Enterprise : Entity responsible for assigning the unique identifier (UID) to a tangible asset. </li></ul...
Data Content Elements <ul><ul><li>For items that are serialized within the enterprise, the UID is a combination of the  en...
Collaborative Solution <ul><li>Seek international and intergovernmental support for use of three data standards: </li></ul...
Actions Underway <ul><li>Request of the ISO/IEC JTC1/SC31 that TEIs be added to ISO/IEC 15434 as a new code format to supp...
UID in the Supply Chain EI 194532636 PN 200H0028 SN 003896* Item Markings EI 083949107 PN 218H2861 SN 105742* Item Marking...
Clean Audit Opinions on Property, Plant and Equipment & Operating Materials and Supplies Enhance the Business Enterprise A...
UID Interfaces Planning/Systems Engineering Acquisition & Procurement Financial Management Operations & Deployments Logist...
UID Lifecycle
What is the UID Lifecycle? Require –  DoD contracts reflect the requirement for part marks to include UID data elements fo...
UID Lifecycle & Interface Flow Require Create & Generate Capture Use
Require the UID Which Items Require a Unique Identifier (UID)? 14
13 Require the UID <ul><li>All program managers for new equipment, major modifications, and reprocurements of equipment an...
Create and Generate the UID The components that make up the UID are identified in the table below.  Each enterprise has tw...
Create and Generate the UID <ul><li>BUSINESS RULES </li></ul><ul><li>The UID shall be derived from its discrete component ...
Create and Generate the UID <ul><li>Data qualifiers (semantics) will define each machine-readable data element marked on t...
Capture the UID <ul><li>For activities after initial delivery, in support of the product life cycle, any entity that colle...
Capture the UID <ul><li>BUSINESS RULES   </li></ul><ul><li>In a database, once the UID is derived, it shall not be parsed ...
Capture the UID
Capturing and Initiating UID Use
UID Organization & Efforts-to-Date
Current Organizational Structure Project Management LeAntha Sumpter, Greg Redick,Rob Leibrandt Policy Standards Implementa...
Policy Effort <ul><li>The Policy efforts-to-date have included: </li></ul><ul><ul><li>Publishing the July policy and polic...
DFARS Effort <ul><li>The DFARS Cases efforts-to-date have included: </li></ul><ul><ul><li>The public hearing was held on M...
Standards Team <ul><li>The Standards Team efforts-to-date have included: </li></ul><ul><ul><li>Establishing the UID Constr...
Implementation Team <ul><li>The Implementation Team efforts-to-date have included: </li></ul><ul><ul><li>Developing an AIS...
Next Steps
What’s Next <ul><li>Charter a Joint Requirements Implementation Board </li></ul><ul><li>Support RFID policy development  <...
What Does it Mean for Me? <ul><li>UID  item marking will be a mandatory requirement for all new weapons systems programs, ...
Upcoming SlideShare
Loading in...5
×

UID Overview Brief

1,163

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,163
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • The DoD vision for item marking has the following strategic objectives that closely align with the vision of the Business Enterprise Architecture initiative. (Read objectives)
  • The UID strategic imperative has been outlined and reinforced in four consecutive policy memos published since August 2002. USD(AT&amp;L) &amp; USD(COM) memo signed 6 Aug 2002 Subject: Universal Identifier Code PDUAS(AT&amp;L) memo signed 6 Sep 2002 Subject: Universal Identifier Code; Interim Policy PDUSD(AT&amp;L) memo signed 19 Dec 2002 Subject: Forecast of Policy for Unique Identification of Tangible Items PDUSD(AT&amp;L) memo signed 4 Apr 2003 Subject: Forecast of Policy for Unique Identification of Tangible Items - UPDATE These and other related policy documents can be found at www.acq.osd.mil/uid
  • In support of the strategic imperative, DoD established an Integrated Product Team (IPT) to identify the UID data standard and develop an implementation strategy that is both feasible and provides substantial benefit in a reasonable timeframe. The IPT consists of five simultaneous efforts: Standards, Business Rules, Implementation, Policy and DFAR cases.
  • The first thing the Standards Team accomplished was to define the UID in plain terms, giving it requirements that must hold up during all aspects of its life.
  • The next accomplishment was to define the terms that make up the UID in order to ensure consistency across international governments and industry. The key terms were designed to be simple and to exist, to the extent possible, in established ISO standards and to avoid imposing new UID-specific requirements.
  • In defining the standards, the team took into consideration that uniqueness needed to be contained within each of the elements that construct the UID. The first element, the enterprise ID, is unique because it is assigned by a registration (or controlling) authority that can be held to a standard of guaranteeing uniqueness. The next elements were more difficult to determine. All enterprises assign serial numbers. However, some enterprises assign serial numbers that are unique within the enterprise and others serialize within parts, or like items. For enterprises that serialize within the enterprise, a simple combination of the enterprise ID and the serial number is sufficient to guarantee uniqueness. For enterprises that serialize within part numbers, the enterprise ID and serial number does not guarantee uniqueness. For enterprises that serialize within part numbers, the original part number must be included in the UID composition in order to guarantee uniqueness. Lastly, an enterprise may mark or label any elements outside the UID-required elements on the part as needed for operational purposes.
  • The key agreements of the Standards Team are called the collaborative solution. The collaborative solution was a result of international industry and government coming together to determine how, among different standards currently in use, to consistently mark items to support the UID. The team decided that if multiple standards were interoperable, they could be supported by technology to enable each element of the supply chain to extract the necessary data from the item mark. The team agreed to support the use of three standards. In order to guarantee interoperability, the team selected a standard syntax, ISO/IEC 15434. Because of similar work that has been done by the ISO technical committee (TC 20) in working on TS WD 21849, the elements of that working draft were selected to be the UID standard for business rules.
  • In order for the “collaborative solution” to be successful, the necessary modifications need to be made to existing ISO standards to make them UID- compliant and compatible. This list shows the actions underway to accomplish the goal of aligning ISO standards with the UID collaborative solution.
  • This chart shows the relationships between product data, the components of the supply chain, unique items and the UID. An end item may be composed of subassemblies, components and parts. The prime contractor will build to the end item specifications and will pass down these specs, including the UID marking requirements to the tiered vendors for the build of subcontracted subassemblies, components and parts. The end item, as well as all the subassemblies, components and parts will have part numbers assigned in the specs. The various vendors will produce these part-numbered items and deliver them to the prime. Spares may be purchased directly from the vendors or through the prime. These UID-qualifying spare items also have to be marked appropriately with the UID components. So, when the prime delivers the end item, that is one UID. The spares are delivered with their own UIDs. The Government has the option of asking the prime to deliver a list of all UIDs for UID-qualifying items in the end item. The capture of the end item and spares UIDs at time of delivery will satisfy the valuation of assets and inventory and property management requirements. (Important note: the chart purposely does not use TEIs, AIs, or Dis – just associative abbreviations)
  • This chart illustrates the UID lifecycle. The business rules associated wit each “phase” are highlighted in this section. Detailed business rules are also available.
  • This chart represents the two UID constructs. Whether an enterprise uses UID Construct #1 or UID Construct #2 depends on whether they serialize items within the enterprise or within part number. The chart also illustrates how to handle rolling part numbers under UID Construct #2 and still guarantee that the UID is permanent over the life of the item. In order to ensure permanence over the life of the item, even if when using UID Construct #2 is used and the part number rolls, the team decided the following: The original part number (assigned at birth) will be used to construct the UID If the part number should roll, the original part number is required to be marked on the item for the entire life of the item in order to reconstruct he UID The current part number may be marked on the item as an additional element
  • One of the most important business rules tells the enterprise how to construct the UID, which is illustrated on this slide. Because the UID uses original part number rather than current part number in Construct #2, a rolling part number will not change the UID. Current part numbers and other necessary data elements that need to be communicated between the enterprise and its customer on the asset, will be done using identifiers separate from the UID data elements.
  • Semantics, or codes used to describe the data following the code, will be used to define each data element and assist the AIT reader in determining what elements it needs to construct the UID. Each of the 3 standards in the collaborative solution have worked to add codes to accommodate the UID. The semantics translation between the three standards is shown in this table. For example, the code for a EAN.UCC Enterprise ID is 3V for data identifiers, 776 for application identifiers, and EUC for Text Element Identifiers.
  • This chart illustrates the three formats and introduces a new concept that needs to accompany the UID. The concept is interoperability. Accepting the ISO/IEC 15434 syntax (in blue) as the UID standard enable interoperability between the three sets of semantics (in red): Text element identifiers, EAN.UCC application identifiers, and MH 10.8.2 data identifiers. Interoperability enables translation via inexpensive conversion software loaded in the AIT reader (shown above) or the AIS system. This type of interoperability enables DoD to accept commercially available standards rather than choosing one standard and forcing its suppliers to conform, which may ultimately result in higher item costs for DoD.
  • This chart shows how the UID should be translated to the database from the mark or label. An important element here is that once created, the UID cannot be parsed. It was determined by the IPT that parsing presented too much risk of error and could not be relied upon to guarantee data quality and integrity over the long run.
  • This chart shows how the UID should be translated to the database from the mark or label. An important element here is that once created, the UID cannot be parsed. It was determined by the IPT that parsing presented too much risk of error and could not be relied upon to guarantee data quality and integrity over the long run.
  • The IPT defined the UID in plain terms, giving it requirements that must hold up during all aspects of its life.
  • In order for the “collaborative solution” to be successful, the necessary modifications need to be made to existing ISO standards to make them UID-compliant and compatible. This list shows the actions underway to accomplish the goal of aligning ISO standards with the UID collaborative solution including the acceptance of text element identifiers by ISO/IEC 15434 and the acceptance of ISO/IEC 15434 syntax by the aerospace community to promote interoperability.
  • In order for the “collaborative solution” to be successful, the necessary modifications need to be made to existing ISO standards to make them UID-compliant and compatible. This list shows the actions underway to accomplish the goal of aligning ISO standards with the UID collaborative solution including the acceptance of text element identifiers by ISO/IEC 15434 and the acceptance of ISO/IEC 15434 syntax by the aerospace community to promote interoperability.
  • In order for the “collaborative solution” to be successful, the necessary modifications need to be made to existing ISO standards to make them UID-compliant and compatible. This list shows the actions underway to accomplish the goal of aligning ISO standards with the UID collaborative solution including the acceptance of text element identifiers by ISO/IEC 15434 and the acceptance of ISO/IEC 15434 syntax by the aerospace community to promote interoperability.
  • In order for the “collaborative solution” to be successful, the necessary modifications need to be made to existing ISO standards to make them UID-compliant and compatible. This list shows the actions underway to accomplish the goal of aligning ISO standards with the UID collaborative solution including the acceptance of text element identifiers by ISO/IEC 15434 and the acceptance of ISO/IEC 15434 syntax by the aerospace community to promote interoperability.
  • In order for the “collaborative solution” to be successful, the necessary modifications need to be made to existing ISO standards to make them UID-compliant and compatible. This list shows the actions underway to accomplish the goal of aligning ISO standards with the UID collaborative solution including the acceptance of text element identifiers by ISO/IEC 15434 and the acceptance of ISO/IEC 15434 syntax by the aerospace community to promote interoperability.
  • In order for the “collaborative solution” to be successful, the necessary modifications need to be made to existing ISO standards to make them UID-compliant and compatible. This list shows the actions underway to accomplish the goal of aligning ISO standards with the UID collaborative solution including the acceptance of text element identifiers by ISO/IEC 15434 and the acceptance of ISO/IEC 15434 syntax by the aerospace community to promote interoperability.
  • Depending on where you fall on the supply chain, the UID requirement will mean different things. The original implementation goal was to require UID-compliant item markings for all new weapons systems, including major modifications no later than July 2003. Because the July policy memo will be published prior to obtaining ISO approval for the collaborative solution, several questions have been raised about what to do in the interim or what to do if items are marked according to the the collaborative solution and ISO fails to approve it. The policy memo will provide the guidance necessary for government and industry in order to implement UID in the interim.
  • Transcript of "UID Overview Brief"

    1. 1. Unique Identification (UID) of Tangible Items
    2. 2. Agenda <ul><li>Overview </li></ul><ul><li>Technical Specifics </li></ul><ul><li>UID Lifecycle </li></ul><ul><li>UID Organization and Efforts to Date </li></ul><ul><li>Next steps </li></ul>
    3. 3. Overview
    4. 4. <ul><li>To create a policy establishing a strategic imperative for uniquely identifying tangible items relying to the maximum extent practical on international standards and commercial item markings. </li></ul><ul><li>Uniquely identified (UID) tangible items will facilitate item tracking in DoD business systems and provide reliable and accurate data for management, financial, accountability and asset management purposes. </li></ul>DoD Vision for Item Marking
    5. 5. Strategic Purpose of UID is to… <ul><li>Integrate item data across government and industry asset management systems, resulting in: </li></ul><ul><ul><li>Improved data quality and global interoperability </li></ul></ul><ul><ul><li>Rationalization of systems and infrastructure </li></ul></ul><ul><li>Improve item management and accountability </li></ul><ul><li>Improve asset visibility and life-cycle management through life cycle traceability </li></ul><ul><li>Enable more accurate audit opinions on the property, plant, and equipment and operating materials and supplies portions of financial statements </li></ul>
    6. 6. DoD’s Approach to UID <ul><li>The Department of Defense (DoD) established a joint international/industry/government Integrated Product Team (IPT) to achieve the following goals: </li></ul><ul><ul><li>Identify the UID data standard and business rules </li></ul></ul><ul><ul><li>Develop a feasible and rapid implementation strategy </li></ul></ul><ul><li>The IPT consists of five simultaneous efforts: </li></ul><ul><ul><li>Policy Development </li></ul></ul><ul><ul><li>Standards </li></ul></ul><ul><ul><li>Technical Interfaces </li></ul></ul><ul><li>Business Rules </li></ul><ul><li>DFARS Cases </li></ul>
    7. 7. Technical Specifics
    8. 8. What is U nique ID entification (UID)? UID is . . . . . . the set of data for tangible assets that is globally unique and unambiguous, ensures data integrity and data quality throughout life, and supports multi-faceted business applications and users. EID 194532636 Original Part Number 1234 Serial Number 786950
    9. 9. Key Terms <ul><li>Enterprise : Entity responsible for assigning the unique identifier (UID) to a tangible asset. </li></ul><ul><li>Registration (or Controlling) Authority : Organization responsible for assigning a non-repeatable identifier to an enterprise. </li></ul><ul><li>Enterprise Identifier : Code uniquely assigned to an enterprise by a registration (or controlling) authority. </li></ul><ul><li>Serial Number : Code assigned by the enterprise to an item providing for differentiation of that item from any other like or unlike item. Serial numbers can be unique within the enterprise or unique within the part number. </li></ul><ul><li>Part Number : Code assigned by the enterprise to a class of items with the same form, fit, function, and interface. The part number is original if assigned at asset birth and current if reassigned from the original. </li></ul>
    10. 10. Data Content Elements <ul><ul><li>For items that are serialized within the enterprise, the UID is a combination of the enterprise identifier and the serial number </li></ul></ul><ul><ul><li>For items that are serialized within the part number, the UID is a combination of the the enterprise identifier , the serial number , and the original part number </li></ul></ul><ul><ul><li>To display data elements not part of the UID data content, (i.e., current part number) a separate mark/label may be used </li></ul></ul><ul><ul><li>Human readable data may include data in addition to the data in the mark(s) </li></ul></ul>
    11. 11. Collaborative Solution <ul><li>Seek international and intergovernmental support for use of three data standards: </li></ul><ul><ul><li>ATA Spec 2000 CSDD text element identifiers </li></ul></ul><ul><ul><li>EAN.UCC application identifiers </li></ul></ul><ul><ul><li>ISO/IEC 15418 data identifiers </li></ul></ul><ul><li>Create an interoperable environment across industries and government by using ISO/IEC 15434 as the UID syntax standard </li></ul>
    12. 12. Actions Underway <ul><li>Request of the ISO/IEC JTC1/SC31 that TEIs be added to ISO/IEC 15434 as a new code format to support part marking </li></ul><ul><li>Modify ISO WD 21849 to reference ISO/IEC 15434 syntax (includes data element separator, header, and terminator) </li></ul><ul><li>Add AIs to the General EAN Specification to support multiple registration (or controlling) authorities and corresponding enterprise identifiers and reflect these in ISO/IEC 15418 </li></ul><ul><li>Modify the FACT DI specification in ISO/IEC 15418 to accommodate UCC/EAN enterprise identifiers </li></ul><ul><li>Modify ISO WD 21849 and ATA Spec 2000 to support multiple registration (or controlling) authorities and corresponding enterprise identifiers </li></ul><ul><li>Update the semantics of each of the three standards to incorporate the defined elements of the UID </li></ul>
    13. 13. UID in the Supply Chain EI 194532636 PN 200H0028 SN 003896* Item Markings EI 083949107 PN 218H2861 SN 105742* Item Markings Item Markings EI 040535536 PN 210H0611 SN 006392* EI 080907280 PN 216H1439 SN 020890* Prime Tier 1 Tier 2 Tier 3 Enterprise Supply Chain Unique Items Product Data End Item Specs Subassembly Specs Component Specs Part Specs PN 210H0611 PN 200H0028 PN 216H1439 PN 218H2861 Item Markings UN080907280216H1439020890 Delivery to Govt List of Hardware UIDs List of Hardware UIDs UID ** UN194532636200H0028003896 UN040535536210H0611006392 UN083949107218H2861105742 List of Hardware UIDs Delivery to Govt Delivery to Govt Delivery to Govt (Optional) (Optional) (Optional) Spares Spares Spares End Item UID = Unique Identifier; EI = Enterprise Identifier PN = Part Number; SN = Serial Number * Serialized within the part number using DUNS **UN = Issuing Agency Code for DUNS
    14. 14. Clean Audit Opinions on Property, Plant and Equipment & Operating Materials and Supplies Enhance the Business Enterprise Architecture UID Role - Business Enterprise Architecture Enhance Total Asset Visibility
    15. 15. UID Interfaces Planning/Systems Engineering Acquisition & Procurement Financial Management Operations & Deployments Logistics/Materiel Management Property Management UID 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 items accounted for? Industry Joint Financial Management Improvement Program (JFMIP) Other federal agencies; GSA, TSA, NASA Joint Total Asset Visibility DoD CFO Accountability Configuration Management How is the tech data managed?
    16. 16. UID Lifecycle
    17. 17. What is the UID Lifecycle? Require – DoD contracts reflect the requirement for part marks to include UID data elements for all items which require unique identification Create/Generate – Industry suppliers/manufacturers throughout supply chain assign and apply UID data elements and ensure the uniqueness of the component data elements Capture – DoD establishes the “birth” record of the UID by capturing the machine/human readable component data elements to create the UID in the AIT/AIS Use – Functional stakeholders use UID as a primary or alternate key in the AIS to access or update item information based on its UID Dispose – DoD/GSA records the “termination” of the UID at time of item disposal UID
    18. 18. UID Lifecycle & Interface Flow Require Create & Generate Capture Use
    19. 19. Require the UID Which Items Require a Unique Identifier (UID)? 14
    20. 20. 13 Require the UID <ul><li>All program managers for new equipment, major modifications, and reprocurements of equipment and spares shall begin planning to apply Unique Identification (UID) on tangible items </li></ul><ul><li>UID is a mandatory DoD requirement for all solicitations issued on or after January 1, 2004 </li></ul><ul><li>Specific guidance related to UID requirements can be found by referring to the following sources: </li></ul><ul><ul><li>DFARS (under revision to include UID) </li></ul></ul><ul><ul><li>DoD Guide to Unique Identification of Tangible Items </li></ul></ul><ul><ul><li>Coordinated Guidance </li></ul></ul><ul><ul><li>www.acq.osd.mil/uid </li></ul></ul>
    21. 21. Create and Generate the UID The components that make up the UID are identified in the table below. Each enterprise has two options for creating the UID. *The Issuing Agency Code (IAC) represents the registration authority that issued the enterprise identifier (e.g., Dun and Bradstreet, EAN.UCC). The IAC can be derived from the data qualifier for the enterprise identifier and does not need to be marked on the item. UID Construct #2 UID Construct #1 Current Part Number Current Part Number Data Identified on Assets Not Part of the UID (Separate Identifier) Issuing Agency Code* Enterprise ID Original Part Number Serial Number Issuing Agency Code* Enterprise ID Serial Number UID is derived by concatenating the data elements IN ORDER: If items are serialized within the Part Number If items are serialized within the Enterprise Based on current enterprise configurations
    22. 22. Create and Generate the UID <ul><li>BUSINESS RULES </li></ul><ul><li>The UID shall be derived from its discrete component data elements. The UID is not required to be marked on the item as a separate data element. 1 </li></ul>1 If the enterprise chooses to mark the UID as a discrete data element on the item, the component data elements must also be marked on the item as discrete data elements, in addition to the UID. 2 This example uses MH10.8.2 Data Identifiers. EID 12V194532636 Serial No. 18S786950 UID Construct #1 2 UID Construct #2 2 EID 12V194532636 Orig. Part No. 1P1234 Serial No. 18S786950
    23. 23. Create and Generate the UID <ul><li>Data qualifiers (semantics) will define each machine-readable data element marked on the item. </li></ul><ul><li>The data qualifier associated with the serial number will identify which UID construct is used to build the UID. </li></ul>Semantics Translation Between Data Identifiers (DI), Application Identifiers (AI), and Text Element Identifiers (TEI) 1
    24. 24. Capture the UID <ul><li>For activities after initial delivery, in support of the product life cycle, any entity that collects data about the item must be capable of associating the data with the UID in accordance with the program requirements. </li></ul><ul><li>Using the syntax and the semantics translation table on the prior slide, software that resides either in the AIT device or the AIS can translate between the three approved, interoperable formats </li></ul>(Format has to be assigned by SC 31, all 2-digit numbers used or reserved) Formats: TEI: [)> R S DD G S DUN 194532636 G S PNO 1234 G S SEQ 786950 E o T EAN.UCC: Application Identifiers [)> R S 05 G S TBD 194532636 G S 01 1234 G S 21 786950 E o T MH 10.8.2: Data Identifiers [)> R S 06 G S 12V 194532636 G S 1P 1234 G S S 786950 E o T
    25. 25. Capture the UID <ul><li>BUSINESS RULES </li></ul><ul><li>In a database, once the UID is derived, it shall not be parsed to determine the original elements 1 </li></ul>Never Changes (mandatory for audit) Can Change Incremental 1 This example uses MH10.8.2 Data Identifiers. 5678 Current Part No. 786950 Serial No.    1234 194532636 UN1945326361234786950 “ Other Data”… Orig. Part No. EID UID (Constructed with a Business Rule) Record ID EID 12V194532636 Orig. Part No. 1P1234 Serial No. 18S786950 Current Part No. 30P5678
    26. 26. Capture the UID
    27. 27. Capturing and Initiating UID Use
    28. 28. UID Organization & Efforts-to-Date
    29. 29. Current Organizational Structure Project Management LeAntha Sumpter, Greg Redick,Rob Leibrandt Policy Standards Implementation DFARS ISO Approval Process Enterprise Registration Authorities Technical Infrastructure Business Rules Executive Sponsor Michael Wynne IPT DoD Guide Coordinated Policy Guidance <ul><li>Part Marking (new & legacy) </li></ul><ul><li>System Requirements (new & legacy) </li></ul><ul><li>Critical path plan </li></ul><ul><li>Data Capture </li></ul><ul><li>Registry </li></ul><ul><li>Information Management </li></ul><ul><li>BSM/FLE Coordination </li></ul>DFARS Plan Integrated Policy Tools/DoD Guide Details <ul><li>Critical path to expedite </li></ul><ul><li>Interim rule </li></ul><ul><li>Systems Engineering requirements </li></ul><ul><li>Property management documentation </li></ul><ul><li>Integration with PBL </li></ul><ul><li>Contract language </li></ul><ul><li>Pre-solicitation </li></ul><ul><li>Pre-award </li></ul><ul><li>Contract Administration </li></ul><ul><li>Contract Closeout </li></ul>
    30. 30. Policy Effort <ul><li>The Policy efforts-to-date have included: </li></ul><ul><ul><li>Publishing the July policy and policy forecast memos </li></ul></ul><ul><ul><li>Identifying and completing coordinated guidance </li></ul></ul><ul><ul><li>Finalizing the first version of the Unique Guide for Uniquely Identifying Tangible Items (UID Guide) for implementing UID </li></ul></ul>
    31. 31. DFARS Effort <ul><li>The DFARS Cases efforts-to-date have included: </li></ul><ul><ul><li>The public hearing was held on May 28, 2003 </li></ul></ul><ul><ul><li>Responding to comments made during the hearings </li></ul></ul><ul><ul><li>Developing a final draft rule to submit to DAR Council </li></ul></ul><ul><ul><li>Submitting the draft DFARS interim rule to OMB for approval </li></ul></ul>
    32. 32. Standards Team <ul><li>The Standards Team efforts-to-date have included: </li></ul><ul><ul><li>Establishing the UID Constructs #1 and #2 </li></ul></ul><ul><ul><li>Identifying the collaborative solution </li></ul></ul><ul><ul><li>Adding the necessary semantics to all three data standards to support the elements of the UID </li></ul></ul><ul><ul><li>Submitting a new work item proposal to ISO/IEC for incorporating UID-specific requirements into existing standards </li></ul></ul>
    33. 33. Implementation Team <ul><li>The Implementation Team efforts-to-date have included: </li></ul><ul><ul><li>Developing an AIS infrastructure plan to accommodate the UID </li></ul></ul><ul><ul><li>Developing a plan for a UID registry </li></ul></ul><ul><ul><li>Finalizing the UID business rules for marking, conformance, and data capture </li></ul></ul><ul><ul><li>Reviewing existing serial number tracking and UID-related implementation programs to develop best practices for UID </li></ul></ul>
    34. 34. Next Steps
    35. 35. What’s Next <ul><li>Charter a Joint Requirements Implementation Board </li></ul><ul><li>Support RFID policy development </li></ul><ul><li>Develop tool kit for program managers </li></ul><ul><li>Develop a second DFARS case for Government Furnished Equipment and UIDs </li></ul><ul><li>Determine AIS and infrastructure requirements; continue working implementation solutions for existing programs </li></ul><ul><li>Secure funds to modify and fully deploy AIS tools to support UID </li></ul>
    36. 36. What Does it Mean for Me? <ul><li>UID item marking will be a mandatory requirement for all new weapons systems programs, including major modifications, no later than July 2003 and apply to contracts awarded after 1 Jan 2004 </li></ul>A variety of UID background materials and previous UID policy memos can be found at www.acq.osd.mil/uid
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×