Send/Propose & General Releasing Tips: Version: IMDS Release 10.0
Send/Propose & General Releasing Tips: Version: IMDS Release 10.0
Send/Propose & General Releasing Tips: Version: IMDS Release 10.0
This document discusses the types of ways to “Release” or make productive your MDS or module.
It assumes there are no errors in the datasheet.
For information on correcting errors – please read on the IMDS Information pages > FAQ
category IMDS Errors and Warnings > What do the errors in IMDS mean and how can I fix
them?
If you are familiar with ISO certified processes where there is only true and controlled copy of a
document or process stored in a document library and other documents may list the URL of the
document, you may think of the MDS that is being created as linking to other certified MDSs stored
elsewhere. Instead of a URL, the link is an IMDS ID and version (or node ID).
In fact the “certified” example is a useful one. When you “release” an MDS, you are “certifying” that
all the information is true and final. You cannot go back and make changes without changing the
version number and releasing (or certifying). You cannot release (or certify) a top node while it links
to uncertified (unreleased) MDSs/Modules.
A “Released” or “Productive” MDS or Module has a whole number version.
The process of sending or proposing and acceptance is supposed to be a quality check on the data.
During this interaction, the creator of the MDS is essentially certifying the information for their
customer and the customer either agrees or disagrees by accepting or rejecting the submission –
although there are some companies who accept everything and come back later with a rejection in
an email. While the IMDS Steering Committee has published Recommendations – each customer
may have special requirements that could require resubmission.
The process of publishing is one-sided – the creator certifies, but there is no agreement on the
quality of the data. Although it looks easier for suppliers – most customers have processes in place
that eliminate the incorporation of published data. Unless you produce a commodity item – e.g.
paint, wire, fastener – you should not be publishing.
Since there were too many suppliers who were publishing when they should not, publish is only an
option if you have taken the time to read the instructions. The Company Administrator should read
the Company Administrator tips in order to set the company and users up for publishing.
Before you can let an MDS be viewed by someone else (Internal Release, Send, Propose, or
Publish) ALL the nodes of the tree must be released. That is why it is a good idea to work the BOM
from the bottom up.
Once you Internally Release, Publish, or Propose, the version is set and you cannot make
ANY changes.
Once an MDS is accepted by your customer – you cannot delete the datasheet or the
recipient.
Decide:
Pro Con
Send If recipient rejects it, the MDS can be Can only send to one company. If you need to
edited to correct the problem. send to another, need a new copy (/copy not /new
version).
Propose Same MDS can go to multiple Once proposed, the information cannot be edited.
customers each with their own part If a recipient rejects it, a new copy or version must
number. be created.
In the Create Tips, we added the customer information. In this case, I have made sure that I
released all the nodes of the tree and that all weights and tolerances are correct so I don’t get any
errors.
I can now click on Send.
Under Administration > Personal Settings, everybody can subscribe to receiving e-mails in case
of certain events. In this case, an e-mail is sent to the recipient, if an MDS is received - notifying the
user that an MDS was received and is available in the Inbox.
Under Administration > Personal Settings, you can also subscribe for e-mail notification for the
case an MDS is accepted or rejected and is available in the Outbox. So, if your customer accepted
or rejected your MDS you will receive an e-mail.
In case of a received MDS, the system will generate an e-mail message to you (according to your
subscriptions under Personal Settings). From your Inbox you can directly access the MDS. In this
case the part number was incorrect and the customer decided to reject the MDS. Here is what he
sees after rejecting:
In case of a rejected MDS, the system will generate an e-mail message to you (according to your
subscriptions under Personal Settings). From your Outbox you can directly access the MDS:
NOTE: if your customer says you have the wrong part number or
description, fix it here and not on your ingredients page as this
is what they see on their ingredients page.
Name – the article name from your Ingredients chapter NOT the name from the Recipient Info
Internal number – the information from your Ingredients chapter NOT the information from the
Recipient Info Screen
External number - the information from the Recipient Info Screen NOT your Ingredients chapter
ID - the IMDS ID number
Versions – either just the latest (current) or All versions
Preliminary MDS – MDSs that have had the Preliminary MDS box checked
Org.-Unit that is associated with the MDS. An MDS can be placed into an Org.-Unit by:
Selecting the Org.-Unit when creating on the Supplier Data Page
The Company Administrator using Administration > MDS Admin to move the MDS into the
respective Org.-Unit
YOU MUST HAVE THE ORG.-UNIT ASSIGNED TO YOUR ID TO USE THIS FILTER – your
Company Administrator can assign the Org.-Unit to your ID.
If you do not check “Enable search by recipient”, you will get ALL recipients.
Include all Org Units – you will get all MDSs that you have sent to an Org.-Unit or the “roof” of your
recipient.
Add recipient to list – here you can add recipient
companies to your list of recipients, remove them or
save the recipient list – if it is saved, it will be available
as default next time you use this screen
In this case, I’ve searched on rejected MDSs because I want to find the rejected ones (Status
rejected).
Right-click on an MDS and choose “Show reject reason”.
In the screen, all the available information on the user that rejected the MDS appears.
Since this MDS was SENT (version .01) changes can be made anywhere. If it was Proposed, only
changes on the recipient data screen could be made. If you right-click and choose View you can go
to the MDS.
In order to edit the MDS, you need to choose Edit after right-clicking.
Since we used Send I can make changes anywhere. If this was Proposed, I could only make
changes on the Recipient Data Screen.
Click the little disk icon to Save your changes. You can always initiate a check by either using the
menu item check or directly check by clicking the check icon. Otherwise, the check will be
automatically carried out once the Send button is clicked.
The MDS is now in the hands of your customer - note the status change.
If there’s something else you need to fix, you can click on the Sent MDSs tab to go back to the
Outbox list.
How can I?
• Prove that I submitted
• Have a record customer accepted
• Print a copy for my records
All of these can achieved by using the MDS Report function.
Since PPAPs usually require IMDS submission, some customers require proof that the submission
was made and that it was accepted – use of the MDS Report function has helped with this.
Highlight the desired MDS and click on MDS Report.
My company is the top (IH Automotive) – my customer
is IMDS Service Team.
Section 1 contains information about the Supplier Contact and the information from the Recipient
Page. It also gives the Recipient Status and the date of acceptance. This is usually sufficient for
PPAP.
Whether you Send or Propose is up to your internal processes and your customer’s requirements.
Unless you produce a commodity item, it is preferred you not use Publish. Remember anyone with
an ID in IMDS (and at last count that was over 250,000 people in just about every country in the
world) can see your structure.