In MTConnect, a new working group has been formed relating to Parts and it is being lead by Jim Smith of Nexas America. The first phone conference was only June 5 and the second June 17, 2012. Below is a summary of what has been discussed thus far.
Transformation Model
Production Resource Model
"A single identifiable item that has defined characteristics and is created by applying a series of one of more processes to raw material or to another part."
Look to STEP-NC for a lot of the part information. John Michaloski from NIST referred to STEP-NC 14649 and that it could be a great basis for a start here. He also mentioned that the full STEP-NC APT238 has all the STEP models, but it is a bit unwieldy - like "sipping from a fire hose". Also it was discussed how this data may be up in the engineering office, or the MES system and not necessarily available at the machine. We can also embed some of this STEP-NC parts data in an RFID tag with the part and thus enabling traceability.
"Smart Comments" in RS-274 are another way of adding the rich data to MTConnect.
Josh Davids from Scytec talked about using the DNC system to auto-insert ERP data into comments on remote call file. Will Sobel mentioned that DNC needs love right now in MTConnect.
Discussion of Operator Requirements
Human Assets Tracking Discussion - track operator or maintenance working with the machine. An operator ID and perhaps roles could be monitored. Also Tom Gaasenbeek of Nexas Networks mentioned the need MTConnect Human Asset tracking for operators to address ITAR compliance concerns, In these defense centric operations only qualified people should be able to download controlled part programs, or even log into a machine for instance.
Transformation Model
- Stock
- Work Piece
- Operations
- Material Reveved
- Operations
- Setup/ In Process / Completed
- Expected process time
- Material information
- Source
- Lot Number
- serial numbers, batch and lot numbers
- process information
- part programs
- machine
- Dimensional Metrology Standards (QIF)
Production Resource Model
- Operator
- Machine ID
- Start Time
- Process Information
- Safety data
- Manual processes
- assemblies
- tertiary data
- fictures
- Part ID - Part Program file name - DNC functionality
- ITAR - security
- take a phased in approach
- separate buckets
- have a draft for IMTS
- Jim works with others to create a document for people to throw stones at it.
- create a schedule with an eye on a draft release before IMTS
- seek additional user members
"A single identifiable item that has defined characteristics and is created by applying a series of one of more processes to raw material or to another part."
Look to STEP-NC for a lot of the part information. John Michaloski from NIST referred to STEP-NC 14649 and that it could be a great basis for a start here. He also mentioned that the full STEP-NC APT238 has all the STEP models, but it is a bit unwieldy - like "sipping from a fire hose". Also it was discussed how this data may be up in the engineering office, or the MES system and not necessarily available at the machine. We can also embed some of this STEP-NC parts data in an RFID tag with the part and thus enabling traceability.
"Smart Comments" in RS-274 are another way of adding the rich data to MTConnect.
Josh Davids from Scytec talked about using the DNC system to auto-insert ERP data into comments on remote call file. Will Sobel mentioned that DNC needs love right now in MTConnect.
Discussion of Operator Requirements
Human Assets Tracking Discussion - track operator or maintenance working with the machine. An operator ID and perhaps roles could be monitored. Also Tom Gaasenbeek of Nexas Networks mentioned the need MTConnect Human Asset tracking for operators to address ITAR compliance concerns, In these defense centric operations only qualified people should be able to download controlled part programs, or even log into a machine for instance.
No comments:
Post a Comment