the apache help and uid

7-9 September 2010Hilton Orlando – Orlando, Florida

1


2

Apache AH-64Unique Identification (UID)

USG: Charles R. Roesch256-842-1116

[email protected]

Boeing: Frank W. Murtagh480-891-7065

[email protected]


3

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


44

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


5

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)


6

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)


7

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


8

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


9

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


10

•Shows UID parts by installation location and ME plan:

Will alert missing UID scans before each line move automatically (by

email to team lead & management)

Provides metric to track scanning

Provides the following info by position:•Number of UID parts•How many scanned•How many missed•% complete by position


11

Progression of AH-64 IUID Parts Marking

27,956

31,143 32,361 32,99934,399 34,846 35,385

37,06940,340 40,985

0

5,000

10,000

15,000

20,000

25,000

30,000

35,000

40,000

45,000

Totals as of10/20/2009










Months

Contractors Total: 40,985

Apache PM Total: 62,886

Grand Total: 103,871

Contractor Marked


12

• 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

AH-64 IUID Program for Legacy Marking

UID Data Matrix

Tesa Tape UID Label Apache Legacy Marking

Boeing’s AH-64D UII Data Plate


13

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


14

• 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.

South Carolina National Army Guard Demonstration


15

South Carolina National Army Guard Demonstration Cont’d

• Date of reading – date that the reading was taken

• Missile S/N – missile serial number

• A\C Tail Number – aircraft tail number on which missile is installed

• Launcher Serial # - serial number of the missile launcher on which the missile currently installed

Using UII to Collect Information


16

South Carolina National Army Guard Demonstration Cont’d

• 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.

Benefits


17

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


18

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


19

QuestionsQ

THANK YOU


20

Back-up Slides


21

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


22

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

the apache help and uid

News & Politics