September, 2016
www.us-
tech.com Implementing the Internet of Manufacturing Continued from previous page
context for information from the machine also comes from operation outside the machine scope, such as material supply. After many years of frustration
with inadequate and poorly main- tained standards, machine vendors have out of necessity created an envi- ronment in which they can deliver value from data. This works, as long as the customer is willing to select a narrow range of machines, usually from a single vendor. The scope of the solutions also are restricted, pro- viding little support
for non-
machine-centric operations. Clearly a new standard commu-
nication mechanism has been needed to create factories that are not only connected but also speak the same language, enabling the Internet of Manufacturing (IoM).
A New Paradigm To spur on the adoption of com-
puter control over existing automat- ed processes and to enable more intelligent processes in the future, Mentor Graphics recently introduced its Open Manufacturing Language (OML) specification. This language defines the way in which information is exchanged between automated and manual systems, both the data for- mat and content. By adopting this specification,
any new machine or process intro- duced into a manufacturing opera- tion can be integrated immediately without having to rewrite software interfaces, algorithms and data defi- nitions. OML supports the creation of a true plug-and-play architecture for every part of the manufacturing process. The OML specification is available free of charge to anyone who registers as a member of the OML community (
www.omlcommu-
nity.com). Each member has full access to
the specification, white paper and supporting documentation that defines it. Manufacturing companies can use the specification to start the development of IoM communication projects that are suited to each oper- ation, which allows full compatibility with any future projects and new machines that will create and output OML directly. OML enables a computer sys-
tem to create more value from the available process information. An example is the interpretation of a simple event on the production line. The raw data capture from a machine usually provides informa- tion about the state of the machine, for example, if the machine has stopped because no PCB arrived. This event can be used to calculate machine uptime and downtime, but with no understanding of its context. Most messages from processes are similar, dependent on external events, yet ignorant of their causes. In a normalized OML environ-
ment, the computer system receives raw event data and investigates the cause of the non-arriving PCB imme- diately. The preceding process may belong to a different platform, be from a different vendor, or may be something completely different. OML normalizes the data into a standard language, and the comput- er system can easily determine that the preceding machine may have
OML adds real value to information through data normalization.
been stopped for another reason, such as an error when attempting to pick up a material for placement.
The true cause of the issue behind the event is then made perfectly clear.
When OML is used to represent
material and logistics events, such as verification, the nature of the reason for the mis-pick can be determined. In this example, the event could have many causes, including a replenish- ment of material that was not deliv- ered, the wrong material, an MSD issue occurring with the material, or a feeder jam. Only by putting together all the
information from the relevant sources can the original event be qualified. The qualified event can also be stored in a cloud-based sys- tem, where subsequent analysis can reveal patterns that may yield signif- icant improvements.
Continued on next page
Page 67
Thermal systems for the electronic and photovoltaic industries
For more information visit
www.rehm-group.com or call + 1 770 442 8913
See at SMTAI, Booth 706
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116