Sie sind auf Seite 1von 56

ATA 2004 eBusiness Forum

Part Traceability
Data Standards
Spec 2000 - An Industrial Standard for this Millennium

Jon Andresen
President
Technology Solutions
Oakland, CA

Atlanta, GA 29 October 2004

© Technology Solutions 2004


ATA 2004 eBusiness Forum

Who Am I ?

Here to tell you: forget the damn technology !


(I’m really the Data Guy!)
ATA 2004 eBusiness Forum

Don’t get sucked in by the technology !


ATA 2004 eBusiness Forum
ATA 2004 eBusiness Forum
ATA 2004 eBusiness Forum
ATA 2004 eBusiness Forum
ATA 2004 eBusiness Forum

Here’s the Problem !


n Ya gotta prove everything ! Safety
– Where did it come from?
– When did it come from there? Critical
– Who brought it?
– Where is it going ? Security
– When will it get there ?
– Where is it now ?
Critical
– Who has it ?
– What condition is it in? Cost
Critical
ATA 2004 eBusiness Forum

The Problem: Better – Faster – Cheaper !


Keep Costs
Down Collaborate
More Info to
w/ Suppliers
Customer

More
Less Staff Regulations

You !
Expand
Customer Base
More Efficient
ATA 2004 eBusiness Forum

Why Spec 2000 ?

Customer A Supplier 1

Is this your business model ?


ATA 2004 eBusiness Forum

…because of this !
Customer B Supplier 2

Customer D Supplier 5

Customer A Supplier 1

Customer C Supplier 4

Customer E Supplier 3

It is too costly to do business 25 (or 2500) different ways !


ATA 2004 eBusiness Forum

Customer/Supplier Interchanges
Requirements Specification for new part (documents, diagrams, etc.)

C S
Design Data (performance specs, visuals, CAD drawings, etc.)
u u
Commercial negotiations (discussion documents, contract drafts, etc.)
s p
Progress Monitoring/updates (letters, phone calls, documents, etc.)
t p
Initial/replenishment Purchasing Transactions (POs, expedites, etc.)
o l
Parts Shipments Involving New, Repair, Warranty, & Exchange Parts
m i
e Parts Traceability : mfgr, install, remove, repair, store, ship, scrap, etc.
e
r Trading Transactions (quotes, warranties, invoices, etc.)
r
s Engineering & Maintenance Information (manuals, graphics, training, etc.)

Customer Support & Service Bulletins (documents, photos, graphics, etc.) s


ATA 2004 eBusiness Forum

What’s Needed for Success?


n Common data
– Whose Part # are we talking about? How long can it be?
Can it have special characters in it?

n Common identity
– How does everyone uniquely identify this part? What is its
Social Security Number that never changes?

n Minimum Standard for Traceability


– When you do something to the part, what data do you
record? What business benefit is gained by having data?
ATA 2004 eBusiness Forum

The Issues
n Data standards?
– When you say “Part #”, whose are you talking about?

n Common format to the data you send/receive?


– Excel spreadsheet? Word document? Transaction?

n Communication means?
– Email? FTP? Online? Paper?
ATA 2004 eBusiness Forum

Issues Solved !
With Spec 2000
n Data Dictionary defines all data
– Definition, field lengths, special characters, etc.

n Simple spreadsheet data formats


– It works from PC’s Excel to mainframe SQL

n Communication remains flexible


– accommodates your needs and capabilities
What is Spec 2000 ?
Ø A specification to exchange information:
- Purchasing transactions
- Repair Order transactions
- Aircraft and Engine warranty
- Reliability Data Collection and Exchange
- Part Marking using data (not just text)
Ø System for buying and selling aircraft parts and repair services
- Defines data for business transactions
Ø Established network of 1500 suppliers and airline operators
Ø Established and very well supported EDI format
- used for 40+ years - started as ATA Spec200
In Summary:
Spec 2000 is a data standard and an eBusiness standard.
ATA 2004 eBusiness Forum

Spec 2000 eBusiness


Customer Marketplace
Databases
EDI Standards
El
Purchasing / Invoicing ec
tro Manufacturer Prices / Lead Times
Repair Order Admin. nic
Da Tools, Test, & Ground Equip.
Warranty Claims
ta Repair Agency Capabilities / Prices
File Transfers Int
erc Surplus Parts Availability
Provisioning ha Reliability Database
Delivery Configuration ng
Lead Time Performance Data e Traceability Databases
Inventory Consumption Data
Reliability Data

1500+ companies involved AutoID


Worldwide ! Bar Coded Shipping Labels
Perm. Bar Code/RFID ID on Parts

MFR / Supplier / Repair Agencies


ATA 2004 eBusiness Forum

Spec 2000
Functional and Data Architecture
The Foundation is laid with common data!
(giving parts a Social Security Number)

Permanent Bar Code/RFID Identification of Parts


Spec 2000 Common Data

Existing Standards
Legend:
‘In-Process’ Standards Jon Andresen, President

Future Standards © Technology Solutions


Rev: May 2004
ATA 2004 eBusiness Forum

• It is the strong foundation you want to build on


• It is persistent
• It guides corporations in all decisions
• It spans applications and ERP systems, and yes,
even Vice Presidents!
ATA 2004 eBusiness Forum

How much does bad data cost you ?

2000 Cost to
fix an
error

!
0 x
0
20

Cost to
make
an error
ATA 2004 eBusiness Forum

Benefits of RFID/Bar Code Technology


Manual Data Entry RFID/Bar Code Data Entry

Time Accuracy Time Accuracy


1) Touch typists average 1 error every 30 characters
How many touch typists in
2) Bar code errors occurs once every 3 million characters ! your production areas ?
3) RFID is even more accurate than that !
ATA 2004 eBusiness Forum

What’s this ?
? Ser
er ial N
b um

Part
Num
263265930 n ?
ber
?

atio
er? Loc
umb
ee N
loy
Emp Orde
SSN w r Nu
ithout mbe
the da r?
Who knows ??? shes
?

This is a NAKED number with no intelligence whatsoever !


ATA 2004 eBusiness Forum

Example of an Intelligent Number


Serial Number showing the Text Element Identifier (TEI)

SER 263265930
space

TEI Serial Number

4 characters 1à15 characters

Simple, plain text, WYSIWYG, easy for people - easy for computers
ATA 2004 eBusiness Forum

Example of an Intelligent Number


Serial Number showing the Text Element Identifier (TEI)

<SER> 263265930 </SER>


Serial Number

RFID
Tag Antenna

Simple, plain text, WYSIWYG, easy for people - easy for computers
ATA 2004 eBusiness Forum

Tracking Parts – Why so hard ?


Ø Historically, real parts traceability is done poorly
and is very expensive
– Most parts tracked by Serial # within Part # it
hasn’t worked !
– Three logic flaws
» Customers invent their own numbering systems for parts
» When form / fit / function changes - new Part # required
- this effectively loses the ability to track it
» No control between companies of Part Numbers assigned, no legal
‘teeth’ regarding bogus parts

The business problem we’re trying to solve is one of


( common ) identification and traceability.
ATA 2004 eBusiness Forum

Tracking Parts - the Solution


Spec 2000 Permanent Bar Code/RFID

What is it?
§ A universal ‘Social Security Number’ for serialized parts
§ Simple elegance - Only 2 rules:
1) unique Serial # within CAGE Code
2) RFID tag, label or mark lasts the life of the part

Easy to understand,
Easy to communicate
ATA 2004 eBusiness Forum

Who is using Perm. Part Marking?


§ Used by 1500+ international companies
§ An ISO 21849 specification
§ Adopted by the AIA (Aerospace Industries Association)
§ Included in DoD Unique Identifier (UID) policy
§ It is adopted by the railroad industry
§ It is used in some automotive companies
§ It is used in several military programs
§ C17, CH47 Helicopter, torpedo marking
ATA 2004 eBusiness Forum

So why do we want to mark parts ?


1. We have too much money and we need to spend it.

2. We want to look busy for the rest of our careers.

3. We are mentally unstable.

The sharing of identification and tracking of the part has ALL the benefits !
ATA 2004 eBusiness Forum

Benefits of Spec 2000 Implementation


§ Every piece of data is intelligent
§ the electronic data (quotes, orders, adv. shipping notice, etc.) and the bar coded data
(shipping labels, perm. bar code ID) both use the same data identifier
identifier

§ Bar coded data and HRI allows for business transitions


§ Human readable data allows for existing business systems to continue,
continue, and allows for
more advanced companies to benefit from Auto ID savings.

§ Bar coded data and HRI allows for manual fail-over


§ Human readable data is included with all bar codes to allow manual
manual processes to
continue when technology fails
ATA 2004 eBusiness Forum

Example of Spec 2000-Formatted


Permanent ID Data Plate

“Current”
Part #

Permanent
Identifier
( = SSN )
ATA 2004 eBusiness Forum

1D 2D
For New Parts: ß ß
Data Elements 1-D Linear Barcode 2-D Data Matrix
(Preferred on Data Plates) (Preferred on Direct Part Marking)

MFR 12345
MFR / SER SER ABC123 (see Note)
MFR 12345
Encoded in Data Matrix
MFR 12345/SER ABC123
SER ABC123
Note:
Human Readable Interpretation does NOT include
embedded slash “/” but the data does include it.
A Carriage Return is not embedded in the 2D Data Matrix

or
USN 12345ABC123
USN 12345ABC123
USN (= MFR+SER)

PNR F100F200
PNR F100F200
PNR (Conditional on DPM Applications)

DMF 082000 DMF 082000


DMF
(Conditional Data Element)
ATA 2004 eBusiness Forum

1D 2D
For In-Service Parts: ß ß
Data Elements 1-D Linear Barcode 2-D Data Matrix
(Preferred on Data Plates) (Preferred on Direct Part Marking)

SPL / UCN SPL 54321


(Used for In-Service Serialized
Parts) SPL 54321
UCN 123ABC (see Note)
UCN 123ABC
Encoded in Data Matrix
SPL 54321/UCN 123ABC

Note:
Human Readable Interpretation does NOT include
embedded slash “/” but the data does include it.
A Carriage Return is not embedded in the 2D Data
Matrix

UST 54321123ABC
or
UST 54321123ABC
UST (= SPL+UCN)

Other Data Elements Other data elements shown above may also be included.
ATA 2004 eBusiness Forum

2D SSN on a turbine blade

0.10”
ATA 2004 eBusiness Forum

Example of Spec 2000-Formatted


Permanent ID Data Plate

“Current”
Part #

RFID chip

Permanent
Identifier
( = SSN )
ATA 2004 eBusiness Forum

Data Summary
n Confused about what makes up a SSN ?
CAGE Code of the Unique Number within the CAGE Code
company marking the part

New SSN: MFR xxxxx SER yyyyyy…

In-Service SSN: SPL xxxxx UCN yyyyy…

PNR is the current , manufacturer’s Part #


DMF is conditional on New Parts, doesn’t apply for In-Service Parts
ATA 2004 eBusiness Forum

So how should I mark my parts?


Ø Forget the technology !
– create a unique Serial Number system first
Ø The preference for Serialized Part Marking
– Labels : Data Plates or Polyester Labels, if appropriate
» Data: CAGE Code, unique Serial #, Part # on 2nd label
» Bar code: on existing data plate using Code 128 symbology
– Direct Part Marking
» Data: CAGE Code, unique Serial #, Part # in 2nd bar code
» Bar code: 2D Data Matrix symbology using laser etch/dot peen
3. RFID chips – same data as in bar code, plus more !!
We’re aiming at lowest cost, most ubiquitous use of the data !
ATA 2004 eBusiness Forum

Permanent Bar Code/RFID ID on Parts – Benefits


WIIFM
è - parts can be tracked from cradle-to-grave

- easy, error-free data entry to improve tracking

- social security number for every company to use:


OEM, Supplier, Customer, repair shop, distributor

- no clearinghouse to allocate serial numbers or to register them

- works for New parts and existing In-Service parts

- meets FAA/JAA regulations and Best Commercial Practice – safety!

è - works in today’s “open systems” world


Traceability
è -allows industry to share data, e.g., Reliability
Serial # tracking
Supply chain collaboration
ATA 2004 eBusiness Forum

So We’ve Marked our Parts

• Let’s Get to Traceability !


ATA 2004 eBusiness Forum

What is Traceability ?

n The ability to show where a part has been


since it was manufactured/last certified.

How do you get it ?

n By sharing data with others – Customers,


Suppliers, distributors, repair agencies, and,
yes, even Competitors!
ATA 2004 eBusiness Forum

Spec 2000 Traceability Standard


n International Coordinating Group approval in
October 2003

n The first Traceability standard to cover


repairable and rotable parts

n Provides a data standard and an industry


standard for cradle-to-grave tracking of parts
ATA 2004 eBusiness Forum

Example: Data record for MFG

Minimum Traceability Standard


Action Code
Data You Want

Social Security #

Unique Current Action Date Action Action OEM Original Cond. Your Part # Other data, etc…..
CAGE Serial # Part # Company Code Name Serial # Code
Code
61G49 1234567 P7DTR26 20020420 81979 MFG Collins 1234567 SRV P7DTR26

MFG – Manufactured
The six common required data elements are sufficient for a new part
being manufactured with a Spec 2000 unique identification on the
part/data plate. The ‘birth’ record of the part contains the necessary
social security number.
ATA 2004 eBusiness Forum

Example: Data record for SHP

Minimum Traceability Standard

Action Code Data You Want


Social Security #

CAGE Unique Current Action Date Action Action Ship To Cond. Your Part # Other
Code Serial # Part # Company Code Location Code data,
etc…..
61G49 1234567 P7DTR26 20020420 81979 SHP Honeywell - Phoenix UNS P7DTR26

61G49 A234567 P7DTR26 20020420 81979 SHP UAL – MIAJL SRV

61G49 BB34567 P7DTR26 20020420 81979 SHP BA – LHRJJ SRV

61G49 123456S P7DTR26 20020420 81979 SHP AC – YVL depot UNS

SHP – Shipped
Shipped To Location (Mandatory) – when any part is shipped from one location to another
(within a company), or from one company to another (outside the company), a mandatory
Shipped To Location text field should be included to track the parts’ destination. The text
should be descriptive enough for a non-expert to make sense of whether the location is an
outside vendor, the OEM, or an internal warehouse.
ATA 2004 eBusiness Forum

TRACEABILITY Database Example


Min. Traceability Standard Your Information (optional)

“Social Security Number”

CAGE Serial Current Action Action Action OEM Original Aircraft Condition Internal Etc
Code Number Part # Date company Serial # Number Code Location …
61G49 1234567 P7DTR26 RMV 23/11/99 83PH4 Collins T52D611 UA3482 UNS Shop 141
91673 83H6290 459873L8 INS 23/11/99 83PH4 Collins 83H6290 UA3482 SRV UA3482
91673 SS12932 9J9846 SCP 24/11/99 83PH4 Honeywell H12933 UNS
1283S 836 LPY67FF INS 29/11/99 83PH4 Lucas UA5534 SRV UA5534
91673 9943 28374-22 OVH 30/11/99 83PH4 Boeing SRV Shop 180
83845 489GD5 938475-1 SLD 01/12/9 83PH4 P&W 489GD5 SRV Delta
83845 MR32121 - P9475-503 OVH 5/8/00 83PH4 Lucas 75463 UA2234 SRV StkRm C
143
81979 TS1-5221 7109783H MRK 6/29/00 81979 EIA 591783 UA1731 UNS Shop 142

Action Codes: Condition Codes:


MFG - manufactured SRV - Serviceable
MRK - marked (initialized) unit UNS - Unserviceable
SHP - shipped
INS - installed
RMV - removed
RPR - repaired
OVH - overhauled
EXC - exchanged
SLD - sold
SCP - scrapped
WHR - warehoused
ATA SCD/Traceability Database Example
ATA 2004 eBusiness Forum

Traceability Requirements

Common Required Data Elements in All Processes

1. CAGE Code of the manufacturer (MFR) or supplier (SPL)


2. Part Serial Number (SER) or Unique Component No. (UCN)
3. Current Part Number (PNR)
4. Action company’s CAGE Code (ACO)
5. Action Date (ACD)
6. Action Code (ACT) – see approved codes below
ATA 2004 eBusiness Forum

Traceability Requirements
Approved Industry Action Codes are:
• MRK – marked unit • SLD – sold to
• MFG – manufactured • BUY – bought from
• SHP – shipped to • SCP – scrapped
• INS – installed on/in • WHR – warehoused
• RMV – removed from • OTH – other
• RPR – repaired • RCD – received from
• OVH – overhauled • UPG – upgraded to new Part #
• EXC – exchanged with • INP – inspected / tested

These are the events in a part’s life that should be tracked


ATA 2004 eBusiness Forum

Spec 2000
Functional and Data Architecture
The Foundation is laid!
(giving parts a Social Security Number)

Permanent Bar Code/RFID Identification of Parts


Spec 2000 Common Data

Existing Standards
Legend:
‘In-Process’ Standards Jon Andresen, President

Future Standards © Technology Solutions


Rev: May 2004
ATA 2004 eBusiness Forum

Spec 2000
Functional and Data Architecture
This important piece added in
2003 !
Reliability Data

Pilot, Cabin, & Maint. Log


Line Removal
Down Report

Interruption

Flight Hours & Landings


Shop Tear

Schedule
Purchasing

Warranty
Invoicing

Data

Data
Repair

Traceability/Authentication of Parts
Permanent Bar Code/RFID Identification of Parts
Spec 2000 Common Data

Existing Standards
Legend:
‘In-Process’ Standards Jon Andresen, President

Future Standards © Technology Solutions


Rev: May 2004
ATA 2004 eBusiness Forum

Spec 2000
Functional and Data Architecture
Advanced Forecasting & Planning Maintenance Cost Analysis

Inventory Control Reliability Data

Cost-to-Repair
Exchange Parts

Pilot, Cabin, & Maint. Log


Documentation

Line Removal
Serial Number

Down Report
Loan/Borrow

Interruption

Flight Hours & Landings


Scrap Parts
Configuration Model

Unapproved

Electronic

Shop Tear

Schedule
Tracking

Purchasing

Warranty
Invoicing

Data

Data
Parts

Repair

Traceability/Authentication of Parts
Permanent Bar Code/RFID Identification of Parts
Spec 2000 Common Data

Existing Standards
Legend:
‘In-Process’ Standards Jon Andresen, President
© Technology Solutions
Future Standards Rev: May 2004
ATA 2004 eBusiness Forum

The Near Term Future – Commercial World


Customer A Reliability
Database

Customer B
Supplier 1
ODBC Links
or
Internet Traceability DB
web services

Supplier 2

Customer C Traceability DB

Supplier 3
Repair Agency

Traceability DB
ATA 2004 eBusiness Forum

Old Way of Doing Business


Technical
Inf
0 Information orm
210 Job atio
EC als Engineering
SP u Ca n
Man rds

Suppliers Maintenance
Pa Operations
SP rts
EC
20 arts
00 P
Warehouse
Materials
Management
This is a monologue – not a dialogue !
ATA 2004 eBusiness Forum

Spec 2000 Approach to Collaboration


Technical
Sp
0 Information ec
210 Job 210
EC als Engineering Ca 0
SP u rds
Man
Data Data
Suppliers Database(s) Maintenance
Key: common data
Pa
like SSN Operations
SP rts Data
EC Data
20 arts 0
00 P 210
E C
Warehouse SP
Materials
Management
ATA 2004 eBusiness Forum

Spec 2000 Approach to Collaboration

Technical
0 Information Inf
orm
210
EC als Engineering ati
SP u on
Man
Data Data
Suppliers Database(s) Maintenance
Key: common data
Pa
like SSN Operations
SP rts Data
EC Data
20 arts
00 P
Warehouse
Materials
Management
Customer
Network of
Detailed Internal
Database Sharable
Traceability Databases
Parts Data

Firewall
Data

Authentication

ks
lin

OD
Supplier rvi
ce
Supplier

BC
Se

or
eb

W
W
or

eb
BC

Se
Detailed Internal
Detailed Internal OD

rv
Database

ice
Database

Authentication
lin
ks
Authentication

Firewall
Firewall

Data
Data

Sharable
Parts Data OD
BC Internet Sharable
Parts Data

ks
or
W

lin
eb

ice
Se

rv
rv

Se
ice

eb
lin
ks

W
or
BC
OD
Detailed Internal Authentication
Database
Firewall

Data

Sharable
Parts Data
Jon Andresen
Technology Solutions
Airframe 21 February 2003

Manufacturer © Technology Solutions


ATA 2004 eBusiness Forum

Why Spec 2000 ?

n Complete system with a SSN concept for parts


n Simple – unique Serial # within CAGE Code
n WYSIWYG – good for computer and people
n Common data definitions for eBusiness
n XML-compatible data
n Established : 20 years, 1500+ companies
n It works!
ATA 2004 eBusiness Forum

Part ID and Tracking is Complex in our business…


but it all revolves around Standard Data

Pr
rts
Standard

oc
Pa

es
s
DATA

People
Standard data is the only True North
– not your policies, not ERP systems – Data !

Spec 2000 delivers standard, collaboration-quality data !


ATA 2004 eBusiness Forum

Thank You
for your attention !

For more information on Spec 2000 Permanent Bar Code ID:

www.spec2000.com

Or contact:

Jon Andresen
President, Technology Solutions
5069 Dublin Ave.
Oakland, CA 94602-2604
(510) 531-2201
Email: Jon@TechSoln.com

© Technology Solutions 2004

Das könnte Ihnen auch gefallen