AIAG Standards Update

Download Report

Transcript AIAG Standards Update

AIAG Standards Update
Tim Fowler
Director Supply Chain
[email protected]
Agenda
• AIAG Overview
• Committee/Project Structure
• Messaging Examples
– Regional
– Global
2
Who is AIAG?
• A unique not-for-profit organization where retailers,
automakers, suppliers and service providers work
collaboratively to drive cost and complexity from the
supply chain via global standards development and
harmonized business practices
• Globally recognized trade association founded in 1982
• 1,100 member companies
• 42 full-time staff
– 4 Senior Executive OEM “loans”
– 650+ industry volunteers providing subject matter expertise
• Offices in Southfield, Michigan and Shanghai, China
3
AIAG: 3 Dimensions of Value
• AIAG facilitates global industry consensus to
resolve supply chain issues
– Common business practices
– Systems Interoperability (vertical/horizontal)
• AIAG provides an industry voice and presence at
international standards organizations
• AIAG ensures effective communication &
delivery of consistent requirements, guidelines,
education and training to the industry
4
Board of Directors
Automotive OEMs
Other OEMs
Suppliers
Service Providers
5
Global Alliances
6
AIAG’s Collaboration Model
AIAG Members & Steering Committees
• Provide the industry perspective
• Identify opportunities to streamline and harmonize business processes
AIAG Staff and Industry Loans
• Provide the collaboration infrastructure
• Facilitate project management to address opportunities and resolve
issues
Industry Volunteers
• Provide the subject-matter expertise
• Put aside competitive differences to work together at AIAG to develop
harmonized solutions for the supply chain
AIAG Members within the Automotive Supply
Chain
• Deploy AIAG-developed solutions to the industry, resulting in the
reduction of rework, error and waste
7
AIAG’s Committee/Project Structure
8
Messaging Approach
• Business Process Workgroup
• Define cross-supply chain business process
• XML Schema Workgroup
• Define data models schemas and guidelines
• Web Services Technical Framework
• Enable implementation of business processes
• Through standards-based, secure, reliable electronic
messaging
9
Messaging Examples
•
•
•
•
•
•
•
•
•
•
Advanced Product Quality Planning
Long Distance Supply Chain Logistics
Electronic Inventory Management (Kanban)
Quality Measurement Data
Dimensional Markup Language for Plant Floor
Truck & Heavy Equipment Warranty Management
Early Warning Standards
Outbound Logistics Message Standardization
RFID Event Capture & Tracking
Etc.
10
Global Messaging
•
•
•
1.
2.
3.
4.
5.
6.
Joint Automotive Industry Forum (JAIF) sponsored the Joint
Automotive Data Model (JADM) workgroup
Working with JAMA/JAPIA, Odette and STAR to develop XML
messages for Supply Chain
Develop/update BOD and EDIFACT guidelines and overlays for six
Supply Chain messages
Material Release/Planning Schedule
Ship Schedule
Ship Notice
Receiving Advice
Invoice
Remittance Advice
11
Methodology
• Global Automotive EDIFACT Guidelines
used as basis for requirements
• Base OAGI BODs extended by using
overlays
• Used generic types with codes e.g:
– Party
– DateTimePeriod
– Quantity
12
JADM Results
• Draft message Guidelines developed for 5 messages
• Develop detailed mappings between XML and EDIFACT
Guidelines
• Develop Sample instances for 5 messages
• Developing Remittance Advice BOD based on OAGIS
9.2 PaymentStatus Noun
13
Overlays
14
Message Guidelines
• “x” represents
disabled BOD
fields/components
15
Message Mapping Report
xsd:sequence
oa:DocumentIDsGroup
xsd:sequence
oa:DocumentID
xsd:sequence
oa:ID
oa:RevisionID
oa:VariationID
oa:DocumentDateTime
oa:FreeFormTextGroup
EDI Mapping
M
M
M
O
M
M
1 .. 1
1 .. 1
1 .. 1
0 .. 1
1 .. 1
1 .. 1
O
0 .. 1
Remark:
Example:
Mapping:
Remark:
0 .. 1
Example:
Mapping:
Remark:
O
M
0 .. 1
1 .. 1
Example:
Mapping:
Mapping:
Remark:
M
O
1 .. 1
0 .. unbounded
O
0 .. unbounded
O
Mapping:
xsd:sequence
oa:Desc ription
oa:Note
language ID
O
optional
Example:
Mapping:
Remark:
Example:
Mapping:
Pattern:
Remark:
Example:
Mapping:
Unique identifier of a document. Synonym: document number.
232234
DELFOR.BGM.C106.1004(0020:020:01)
RevisionID is used to indicate a revision of each individual company's message
specification, which is composed based on the global message.
A
DELFOR.BGM.C106.1060(0020:020:03)
VariationID is used to indicate a version of each individual company's message
specification, which is composed based on the global message.
02
DELFOR.BGM.C106.1056(0020:020:02)
DELFOR.DTM[D_2005="137"].C507.2380(0030:010:02)
Used to send general text information within the BOD, e.g. to satisfy legal requirements
like Japan's "Law for the Protection of Suppliers Against Payment Delays
and Related Infractions"
DELFOR.FTX(0040)
AAI
DELFOR.FTX.4451(0040:010)
A line of plain, non-structured text information.
This forecast is for you.
DELFOR.FTX.C108.4440(0040:040:01)
DELFOR.FTX.C108.4440#2(0040:040:02)
DELFOR.FTX.C108.4440#3(0040:040:03)
DELFOR.FTX.C108.4440#4(0040:040:04)
DELFOR.FTX.C108.4440#5(0040:040:05)
([a-zA-Z]{2}|[iI]-[a-zA-Z]+|[x X]-[a-zA-Z]{1, 8})(-[a-zA-Z]{1,8})*
Code specifying the language name.
EN
DELFOR.FTX.3453(0040:050)
16
JADM 2008 Planned Activities
• Convert all BODs/Guidelines to OAGIS 9.2
• Map/compare to Supply Chain Core
Components
• Submit changes to CEFACT as needed
• Map/compare to UN/CEFACT Core Component
Library
• Submit changes to TBG17, as needed
• Update BODs with UN/CEFACT Unique
Identifiers
17
Questions?