Posts Tagged ‘automotive’

AIAG Welcomed Impressive Number of New Member Companies in Most Challenging Year Ever

Wednesday, April 21st, 2010

Southfield, Mich., January 20, 2010 — The Automotive Industry Action Group added 75 new member companies in 2009, a year overflowing with major turmoil for the automotive industry.

Collaboration and co-opetition are at the base of this impressive growth. “We know that on a going forward basis, our interdependence as an industry will have a significant impact on our ability to manage the recovery and sustain profitable growth,” remarked J. Scot Sharland, executive director.

AIAG’s membership actively engages in numerous initiatives, to facilitate industry consensus and resolve issues via the adoption of common business practices (e.g. engineering, logistics, packaging, quality, environmental health and safety, health care, etc.) and interoperable business systems counting application-to-application (A2A), plant-to-business (P2B) and business-to-business (B2B).

By collaborating with competitors in a neutral environment, members are able to identify inefficiencies in business processes. Initiatives are then developed and implemented at AIAG, by member companies, to save the industry millions of dollars and drive rework, error and scrap out of the global automotive supply chain.

New member companies joining the AIAG family in 2009 include:
Alta Mfg. Co.
AmeriPlate Inc.
Anderson Cook
Autodesk Inc.
Bellwright Industries, LLC
Bianchi Public Relations
Borg Indak, Inc
BridgeSpeak
Burlington Technologies Inc.
California Manufacturing Technology Consulting
CHEP USA Inc
Circuit Works Corporation
Colonial Diversified Polymer Products, LLC
Corporation for International Business
D & R Technology, LLC
DATAForge, LLC
Detroit Products International, LLC
Ditech, Inc.
Durapart Industries AS
Edicom Corporation
Epic Technologies
Fontaine International, Inc
Foster and Associates, Inc.
Francis Tuttle Technology Center
GZA GeoEnvironmental, Inc.
Huntington Quality Associates, Inc
I.D. Systems, Inc.
INA Industria Nacional De Autopartes, A.C.
International Rectifier Corp.
International TechneGroup, Inc.
Johnson Controls, Inc.
KPA, LLC
M.K. Chambers Company
Magni-Power Company
Metaldyne
Methode Electronics, Inc.
Michigan State University
Microsoft Corporation
Monbat PLC
Morbern Inc.
Mueller Impacts Company
Neuman Aluminum
Nissan Motor Manufacturing Corporation USA
North Carolina State University Industrial Extension Service
Oracle Corporation
ORBIS Corporation
Orick Tool & Die, Inc.
Panasonic Automotive Systems of America
Paramount Group
Plexus Corporation
Polymer Inc
Q&A Chemical Co., Ltd.
Qdos Flexcircuits BDN. BHD
Quality House, S.C.
Radar Industries, Inc.
Resource International LLC
RF-IDI, LLC
RSJ Technical Consulting
SEEBURGER, Inc.
Sinclair Community College
Symbolic Systems, Inc.
System Seals, Inc.
Tecnologico De Monterrey
TFT Global Inc. – Woodstock
THRU-U.COM INC
Tieco International (Aust) P/L
Trademerit Corp.
Unicell Limited
Universidad Iberoamericana, A.C.
Vertare, LLC
Vitec LLC
Vogelsang Corporation
Watlow
Williams Controls, Inc.

Links:
http://www.aiag.org

Data Quality Open Issues and Questions?

Tuesday, March 2nd, 2010

Now that we have determined that MDM, Data Governance, Data Cleansing and Data Quality are important as well as the new trend for blogging, tweeting and discussion in general, I ask the most important question . . . HOW?  When do we get to the discussions on the content?

I am a very detail oriented person; I have to be as one of my largest accounts requires me to participate in the day to day deployment of global MDM processes for one the largest automotive manufacturers! I am very interested to learn how businesses in other industries manage their data. I would hope that sharing of information and best practices among industry partners will be a win-win situation. At a minimum the discussion will be refreshing; the sharing of innovative information the will spawn the creative improvement needed to create truly efficient knowledge driven business processes, data classifications, metadata and definitions and translation. . . is anyone interested in discussing the logistics of managing translation as part of Master Data Management?

Is anyone interested in discussing my struggles and sharing yours trying to find standard global translations for ISO UOM (Unit of Measures)?

Is anyone interested in discussing what fields should be included in a MDM Data Governance Program for MRO data; UNSPSC, warranty, term of warranty, lead time, estimated price, ECCN, etc.

What Schema or classification structures are you using for spare parts and maintenance items? What about a discussion on using a public vs. priority classification system?

What are some best practices for migrating, profiling, structuring, mismatching and re-verifying legacy system data?

We have a nifty data mismatch process for manufacturer contact information; will this be easily implemented for a CRM data project? What about patient contact information in the healthcare industry?

There are a few bloggers out there that continually add content to their writings but it is starting to appear to be a small group, anyone out there interested in achieving data quality want to discuss “real” life best practices, lesson learned or discuss HOW of MDM, data quality or data cleansing.

View Jackie Roberts's profile on LinkedIn

New Data Management System Implementation Common Sense

Friday, January 8th, 2010

With the ever increasing emphasis on finding ways to reduce cost, one of the clear targets is IT and more specifically data management systems. On the surface it can seem like there is real fat to trim, and many times this is true. But it is easy to become lost in the details and eliminate or negate some of the potential savings. Some of these ideas may seem obvious but are often forgotten. The evidence is clear with missed timing and over budget issues seen.

If we’re talking about a large company then inevitably with this new system comes the monolith project with whole organizations of people and processes, projects and documentation. The compulsion is to be sure that everyone, everywhere who has any relationship to it has their input and their needs accounted for. Along the way, the cost of implementation and other peripheral indirect costs have likely negated a great deal of at least any short term savings. Not to mention the potential increase in continuous maintenance costs and loss in performance. These are a few things I’ve learned from experience and I welcome yours.

Always have a specific objective when planning for development or evaluating software to purchase that overrides all others. Start with something like a mission statement, “We need this new system for….”

Determine the Real Needs. Try to separate the “must haves” from the “nice to haves”. Bells and whistles are great but there needs to be a true benefit. Seek a balance between development time, software performance, hardware performance and user experience. I always try to put special emphasis on the user group which stands to benefit the most. Having many users who can do their job faster and more efficiently can add up to real savings versus the few users who have a special need which bogs down the project and performance.

Change is inevitable. If some requests for additional features come along, evaluate them against the mission objective. There is nothing wrong with listening and investigating ideas for project add-ons as long as the benefits outweigh the costs in time and money, but there needs to be a limit or you’ll never complete the project. Good ideas can always be implemented later if it makes sense then you’ll have the benefit of the research already done, but be quick with the research. Evaluate the impact for doing it now or waiting. Here are some good questions to start with: 1) How much more money?  2) Would this be faster/cheaper for programming to do it now versus waiting and doing a more complicated enhancement?  3) Is the impact to the users great enough to warrant it?

Know the roles. Good ideas can come from anyone. Every project must have a project champion who makes the final decisions (and live with them) and also eliminate roadblocks. You need a user advocate who has done the job and knows what it takes. Have programmers who possess both talent and vision, not just code crunchers, and listen to them.

Have good documentation, and “Good” is subject to interpretation. This is another area where the KISS principle is very often not utilized. If you have to hire ten people to sit in meetings just to maintain your documentation you’ve probably overcomplicated it and certainly increased your project cost. I try to start with these principles:

  1. Document the people on the project and their responsibilities. Let there be no question as to who does what.
  2. Everyone who has a job to do needs to understand what they need to do and have the documentation to reference.
  3. Keep the language simple. Focus on getting the point across. If it takes a rocket scientist to understand it you’ve failed.
  4. Of course, document the issues, decisions made, by whom etc. but be sensible. Document enough to cover for the “he said/she said” but content is most important. No bonus points for flash.
  5. Know who is supposed to have what done and when. Another obvious one here but I see too often where target dates are determined top down with little or no thought to cost or the tasks. Don’t let the tail wag the dog. Pushing hard to get the job done is fine but be realistic. Listen to the people who know before making bold predictions.

Implementation and Use of MRO Naming Standards

Friday, October 23rd, 2009

With all the discussion focusing on Master Data Management and Data Quality, I always come back to these questions: How is the data structured and how is the accuracy and content completeness measured? In our business of managing the coding and verification of items and spare part information needed to keep manufacturing plants running, a structured schema of naming conventions (class), descriptive attribute standardization (properties) and verification at the sources of manufacture (coding @ source) is “key” to quality and completeness measurement. We are managing the ECCMA eOTD for the Automotive Industry Content Standards Council (AICSC) focusing on MRO naming definitions which is the foundation to a spare part description, just as a table of contents is the foundation of a text book.

The first step is to develop the Identification Guide (IG) in order to baseline the properties needed to best describe the class. For example, let’s take the class of SCREW, SHOULDER and the properties TYPE, MATERIAL, FINISH, THREAD SIZE, DRIVE SIZE, SHOULDER DIAMETER, SHOULDER LENGTH, THREAD LENGTH, HEAD DIAMETER, HEAD HEIGHT, SHOULDER LENGTH TOLERANCE, MINIMUM TENSILE STRENGTH, CLASS, HARDNESS RATING and PACKAGE QUANTITY. The IG also provides the information needed for our analysts to acquire properties and our applications to sequence the properties within the short and long descriptions that are built:

SCREW,SHOULDER – | TYPE: HEX HEAD | MATERIAL: 18-8 STAINLESS STEEL | FINISH: PLAIN | HEAD STYLE: HEX | THREAD SIZE: 3/8-16 INCHES | DRIVE SIZE: 3/4 INCHES | SHOULDER DIAMETER: 1/2 INCHES | SHOULDER LENGTH: 2-1/2 INCHES | THREAD LENGTH: 3/4 INCHES | HEAD DIAMETER: 3/4 INCHES | HEAD HEIGHT: 1/4 INCHES | SHOULDER LENGTH TOLERANCE: ±0.005 INCHES | MINIMUM TENSILE STRENGTH: 80.000 POUND-FORCE PER SQUARE INCH | CLASS: 2A | HARDNESS RATING: B85 TO B95 ROCKWELL A | PACKAGE QUANTITY: 2

Each time an item is submitted for coding or processing the item is imported into a master database. Through intervention by our data analysts, the item navigates its way through a number of checkpoints including an auto-suggest to propose a class. The class and properties via the IG are the requirements our coding analysts use to verify the accuracy of the information submitted, to verify the completeness and to acquire the additional information needed to enhance and build an item or spare part description for our clients to base real business decisions.

The implementation of the eOTD is a two process scenario when working with our clients. First, the legacy data is mapped to the class, the item data is profiled, cleansed and enhanced to meet the requirements of eOTD IG, ensuring the client’s data quality goals are met. The updated item information needs to be applied to existing client item data. It is critical that all changes to data be tracked and logged. A properly planned and executed update to legacy ERP and CMMS systems should be initiated to incorporate the enhanced and corrected item information into the user facing systems. This is an extremely critical step as the downstream information flow will affect systems and uses such as inventory re-distribution, purchasing and contract management, engineering bills of materials and maintenance schedules. A thorough and complete mapping of data through the enterprise should be used to understand data flow across all business units. The mapping should include data entry points and data use points through all departments which set up all of the cost saving pay points as the data processing is streamlined.

The second process is an on-going data maintenance plan for new items that are introduced into the organization. This process should start at the introduction of item information into the system. All items and spare part information should be verified with the manufacturer and classified to the eOTD before setup or use in any system. The length of time the coding process requires is a critical element as the item or spare part information should be as complete as possible while at the same time be ready and waiting for the buyer to put the item on a contact or a maintenance employee to setup the tasking information in the CMMS for a piece of equipment. The only requirement for the employees who use the information after its initial entry into the system is to perform the actual requirement of their job and not to decipher a cryptic unstructured description.

If the items are pre-processed using the eOTD and the associated ISO standards, every item and spare part will be structured and standardized. The engineering, purchasing and maintenance departments will focus on the core of their day to day specialized responsibilities instead of searching for parts or dealing with trying to purchase items that a supplier does not recognize or have to acquire the missing information.

We all agree on some of the basic benefits both in process and cost such as reducing inventory with the identification of duplicate items, facilitation of inventory sharing and internal purchasing programs, reduced employee time searching for parts, common spare part usage strategies, reduced downtime in manufacturing equipment due to lack of information availability and ability to manage using a just in-time inventory model. The eOTD and its Identification guides are the building blocks and the roadmap to achieving structured and accurate data that can be reliably used to base real world decisions.

For more information on the eOTD please visit www.eccma.org.

View Jackie Roberts's profile on LinkedIn

DATAForgeTM LLC Managing the Automotive Industry Content Standardization Council (AICSC) Through ECCMA

Tuesday, July 21st, 2009

SOLON, OH–(Marketwire – July 21, 2009) – The ECCMA (Electronic Commerce Code Management Association) awarded DATAForge LLC the distinct honor of managing the Automotive Industry Content Standardization Council (AICSC).  Read More…