This briefing looks at the Apache case study in implementing UID.

1. 7-9 September 2010
Hilton Orlando – Orlando, Florida
1

2. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Apache AH-64
Unique Identification (UID)
USG: Charles R. Roesch
256-842-1116
Charles-Roesch@u.s.army.mil
Boeing: Frank W. Murtagh
480-891-7065
frank.w.murtagh@boeing.com
2

3. 7-9 September 2010
Hilton Orlando – Orlando, Florida
UID Policy
• DFARS Clause 252.211-7003 is included in all
new contracts.
– MIL-STD-130
• DA Memorandum, 9 Dec, 2008 Subject: DoD
instruction 8320.04 “Item Unique Identification
(IUID Standards for Tangible Personal
property)” June 16 2008
3

4. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Boeing Mesa UID Plan
– Effective 14 December, 2006
– Developed in Mesa, coordinated and signed by Defense
Contract Management Agency (DCMA) Mesa and the
Apache PM Logistics office
– Included in the Extended Block ll (EB ll) Apache contract
– Includes Foreign Military Sales (FMS) aircraft under the EB
ll contract
– Future aircraft production contracts, e.g. Apache Block 3
(AB3), will have addendums added for specific
requirements
– All changes formalized via contract change
– Part numbers will not be changed to indicate UID
4

5. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Implementation
• Formed site team for Automated Identification Technology
• Appointed PM for Apache programs
• Bi-weekly telecon with the U.S. Government (USG)
• Three Phased Plan
• Engineering drawings and process specifications used to
control UID
• Part by part basis
• MIL-STD-130 governing USG regulation
• Follow common Boeing Defense Systems practice (when
possible)
5

6. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Implementation Cont’d
• UID Construct 1 is used at the Mesa site.
• Implementation schedules are dependent on:
• The date of effectivity of each contract
• The level of complexity of the part and marking
technique
• The lead time of the part
• Once a part receives a UID all future new procurements of
the part will include UID requirements
• Government Furnished Equipment (GFE) parts provided
under a re-manufacturing or overhaul contract will be
marked if specified in the contract and all non-recurring
requirements are met (e.g. Depot Maintenance Work
Requirements [DMWR] updates)
6

7. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Phased Approach
• Extended Block ll (EB II) Apache
• All Phases- 297 parts UID compliant
– DFAR UID requirements
– Coordination with the USG
• Phase I (contracted in Wartime Replacement Aircraft
[WRA] and EB II)
– Contracted September, 2005
– UID applied to 94 new production parts
• Phase II
– Contracted December, 2009
– UID will be applied to 144 parts (contains GFE ‘used’ parts)
• Phase III
– Contracted August, 2010
– UID (Direct on the Part Mark) UID will be applied to 59 parts
7

8. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Future Apache
(Prototypes Are Flying)
• Apache Block 3 (AB3)
– Proposing Low Rate Initial Production (LRIP)
• Milestone C scheduled for September, 2010
– Contracts in place for the System Design and
Development (SDD) Phase and Long Lead LRIP support
– AB3 Apache UID
• UID plan in place
• Non Recurring Engineering complete
– (Data plates and Direct on Part Mark)
• Marking 62 AB3 unique parts that meet DFAR
requirements
8

9. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Boeing UID System (BUS)
• IT Systems at Mesa have been developed to support UID
implementation
• BUS
– Oracle based
– Maintains contracted lists of parts that require UID
– Collects incoming supplier provided UID part data
– Tracks UID part from receiving through aircraft
delivery
– Reports Aircraft and Spares UID items data IAW
DFARS requirements to the DoD registry
– BUS Change Control Board (BCCB) keeps the
system relevant and current with evolving DoD,
Army and Boeing requirements
9

10. 7-9 September 2010
Hilton Orlando – Orlando, Florida
•Shows UID parts by installation Provides the following info by position:
location and ME plan: •Number of UID parts
•How many scanned
•How many missed
•% complete by position
Will alert missing UID scans before
each line move automatically (by
email to team lead & management)
Provides metric to track scanning
10

11. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Progression of AH-64 IUID Parts
Marking
Contractor Marked
45,000 40,985
40,340
37,069
40,000 34,399 34,846 35,385
32,361 32,999
35,000 31,143
27,956
30,000
25,000
20,000
15,000
10,000
5,000
0
Totals as of Totals as of Totals as of Totals as of Totals as of Totals as of Totals as of Totals as of Totals as of Totals as of
10/20/2009 11/20/2009 12/20/2009 1/20/2010 2/20/2010 3/20/2010 4/20/2010 5/20/2010 6/20/2010 7/20/2010
M onths
Contractors Total: 40,985
Apache PM Total: 62,886
Grand Total: 103,871 11

12. 7-9 September 2010
Hilton Orlando – Orlando, Florida
AH-64 IUID
Program for Legacy Marking
• Objectives: Progress towards legacy UID compliance
• Assign UIIs by adding a laser etched-printed tag
(along with existing data plates)
• AH-64 marked with Tesa Tape UID Label
UID Data Matrix
Apache Legacy Marking
Boeing’s AH-64D UII Data Plate
Tesa Tape UID Label
12

13. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Depot Maintenance Work
Requirements (DMWR)
• Apache PM began DMWR updates, Aug 2008
– Apache has 59 DMWRs requiring IUID-90%
complete
– Depots will include IUID as the DMWR are
updated
• Most DMWRs have numerous parts
• Contracts, Depots and OLR began marking - Jan 08
Enable Depots and Contractors to apply IUID
13

14. 7-9 September 2010
Hilton Orlando – Orlando, Florida
South Carolina National Army
Guard Demonstration
• PM-JAMS Missile Launcher Data Collection
System Demonstration on AH-64
– Purpose: To collect missile and missile launcher data on-
site using information contained within the component’s
UID data matrix.
– Advantage: Distribute the data from the unit to all
command and project management levels to improve
security, safety, reliability, and performance of the weapon
system.
14

15. 7-9 September 2010
Hilton Orlando – Orlando, Florida
South Carolina National Army
Guard Demonstration Cont’d
Using UII to Collect Information
• Date of reading – date that the reading was taken
• Missile S/N – missile serial number
• AC Tail Number – aircraft tail number on which missile is installed
• Launcher Serial # - serial number of the missile launcher on which
the missile currently installed
15

16. 7-9 September 2010
Hilton Orlando – Orlando, Florida
South Carolina National Army
Guard Demonstration Cont’d
Benefits
• Provides a standardized input format for collecting vital
aircraft, launcher, and missile Captive Carry Health
Monitor (CCHM) data.
• UID integration reduces the occurrence of inaccurate
data due to input errors being collected and sent to key
decision makers.
• Automated data export insures the timely and seamless
acquisition of critical condition based maintenance data.
16

17. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Tool Room Manage System (TRMS)
• Developed by 160th Special Operations Aviation
Regiment (Airborne) and U. S. Army Aviation
and Missile Research Development and
Engineering Center (AMRDEC),
– Funded by PM - JAIT
• AH-64D units being field by AMRDEC
• TRMS fielding to Apache continues
– 1-285 ARB
– 1-211 ARB
– 1-135 ARB
– 4-3 ACS
17

18. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Current & Future AIT Efforts
• Apache PM and Boeing continual to implement IUID
marking.
– Legacy
– Fielding of Tool Room Management System (TRMS) to Apache
Battalions
– Conduct study to determine additional marking candidates.
Apache PM awaiting for STAIMS to support IUID Tracking
18

19. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Questions
Q
THANK YOU
19

20. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Back-up Slides
20

21. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Apache PMO and Boeing
IUID Coordination
• Continue working War Replacement Aircraft, Extended
Block II and Apache Block III IUID marking with Boeing
• Block III Low Rate Initial Production Alpha Contracting
– Working with Boeing to mark Block III unique parts
with IUID
• Implementation in all Apache DMWRs
– Coordinate with Corpus Christi Army Depot and
Boeing
– DMWRs have numerous parts
21

22. 7-9 September 2010
Hilton Orlando – Orlando, Florida
Apache PMO and Boeing
IUID Coordination Cont’d
•Boeing UID System (BUS) data base has adequate
information to register items with DOD IUID registry
• Serial number
• Part number
• Contract number
• Other data that can be in the DOD Register
• PM Office and Boeing to assess processes to
implement legacy parts marking
22