├── .github ├── linters │ └── .markdown-lint.yml └── workflows │ └── linter.yml ├── CNAME ├── Dashboard.md ├── FAQ.md ├── Gateway.md ├── LICENSE ├── Organization.md ├── Readme.md ├── Server.md ├── Specs.md ├── Specs ├── Fairs.md ├── Flatglass.md ├── GeometricalMeasuringSystems.md ├── Laser.md ├── MachineTool.md ├── PlasticsRubber.md ├── Software.md ├── WIP.md ├── Woodworking.md ├── pr40077.md ├── pr40079.md ├── pr40082-1.md ├── pr40082-2.md ├── pr40082-3.md ├── pr40084-11.md ├── pr40084-3.md ├── pr40084-9.md └── prgeneric.md ├── _config.yml ├── assets └── css │ └── style.scss ├── img ├── Addressspace_aggregated.png ├── Addressspace_sample.png ├── Fairconnect.png ├── Flatglass │ ├── Flatglass-Identification.png │ ├── Flatglass-Jobs.png │ └── Flatglass-Overview.png ├── GeometricalMeasuringSystems │ ├── GMS-ActiveProgram.png │ ├── GMS-CalibrationInformation.png │ ├── GMS-Identification.png │ ├── GMS-Monitoring-WorkingUnit.png │ ├── GMS-Monitoring.png │ ├── GMS-Overview.png │ └── GMS-Results.png ├── Laser │ ├── Monitoring.png │ ├── Overview.png │ └── Production.png ├── MachineTool │ ├── MT-ActiveProgram.png │ ├── MT-Identification.png │ ├── MT-Monitoring-WorkingUnit.png │ ├── MT-Monitoring.png │ ├── MT-Overview.png │ └── MT-Tools.png ├── PlasticsRubber │ ├── PR_40077_Overview.png │ ├── PR_40077_PDF.pdf │ ├── PR_40079_ImmRobotCellType.png │ ├── PR_40079_Overview.png │ ├── PR_40079_PDF.pdf │ ├── PR_40082-1_Overview.png │ ├── PR_40082-1_PDF.pdf │ ├── PR_40082-2_Overview.png │ ├── PR_40082-2_PDF.pdf │ ├── PR_40082-3_Overview.png │ ├── PR_40082-3_PDF.pdf │ ├── PR_40084-11_PDF.pdf │ ├── PR_40084-3_PDF.pdf │ ├── PR_40084-9_PDF.pdf │ ├── PR_Generic_Overview.png │ └── PR_Generic_PDF.pdf ├── Software │ ├── Software-Detail.png │ └── Software-Overview.png ├── VPN.png ├── WWM-ActiveProgram.png ├── Woodworking │ ├── WWM-ActiveProgram.png │ ├── WWM-Identification.png │ ├── WWM-MonitoringStationary.png │ ├── WWM-MonitoringThroughfeed.png │ └── WWM-Overview.png ├── map_pin_fair.svg ├── map_pin_machine_magenta.svg ├── map_pin_software_cyan.svg └── umati_logo.svg └── index.md /.github/linters/.markdown-lint.yml: -------------------------------------------------------------------------------- 1 | --- 2 | ########################### 3 | ########################### 4 | ## Markdown Linter rules ## 5 | ########################### 6 | ########################### 7 | 8 | # Linter rules doc: 9 | # - https://github.com/DavidAnson/markdownlint 10 | # 11 | # Note: 12 | # To comment out a single error: 13 | # 14 | # any violations you want 15 | # 16 | # 17 | 18 | ############### 19 | # Rules by id # 20 | ############### 21 | MD004: false # Unordered list style 22 | MD007: 23 | indent: 2 # Unordered list indentation 24 | MD013: 25 | line_length: 400 # Line length 80 is far too short 26 | MD026: 27 | punctuation: ".,;:!。，；:" # List of not allowed 28 | MD029: false # Ordered list item prefix 29 | MD033: false # Allow inline HTML 30 | MD036: false # Emphasis used instead of a heading 31 | 32 | ################# 33 | # Rules by tags # 34 | ################# 35 | blank_lines: false # Error on blank lines 36 | -------------------------------------------------------------------------------- /.github/workflows/linter.yml: -------------------------------------------------------------------------------- 1 | --- 2 | ########################### 3 | ########################### 4 | ## Super-Linter Workflow ## 5 | ########################### 6 | ########################### 7 | name: Lint Code Base 8 | 9 | ############################# 10 | # Start the job on all push # 11 | ############################# 12 | on: 13 | push: 14 | pull_request: 15 | branches: [main, develop] 16 | 17 | permissions: read-all 18 | 19 | ############### 20 | # Set the Job # 21 | ############### 22 | jobs: 23 | super-linter: 24 | # Name the Job 25 | name: Lint Code Base (super-linter) 26 | # Set the agent to run on 27 | runs-on: ubuntu-24.04 28 | 29 | ################## 30 | # Load all steps # 31 | ################## 32 | steps: 33 | ########################## 34 | # Checkout the code base # 35 | ########################## 36 | - name: Checkout Code 37 | uses: actions/checkout@v4 38 | with: 39 | # Full git history is needed to get a proper list 40 | # of changed files within `super-linter` 41 | fetch-depth: 0 42 | 43 | ################################ 44 | # Run Linter against code base # 45 | ################################ 46 | - name: Lint Code Base 47 | uses: super-linter/super-linter@v7 48 | env: 49 | VALIDATE_ALL_CODEBASE: false 50 | VALIDATE_JSCPD: false 51 | DEFAULT_BRANCH: main 52 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} 53 | -------------------------------------------------------------------------------- /CNAME: -------------------------------------------------------------------------------- 1 | showcase.umati.org -------------------------------------------------------------------------------- /Dashboard.md: -------------------------------------------------------------------------------- 1 | # umati Dashboard (The "umati app") 2 | 3 | The umati dashboard at [https://umati.app](https://umati.app) is available as a neutral sample application to demonstrate OPC UA companion specification standardization. 4 | 5 | - This dashboard shows all error free machine servers according to the defined [companion specifications](Specs.md). 6 | - It lists [software solutions](Specs/Software.md) from umati partners, who provide a web accessible demonstration instance. 7 | 8 | Machine data are available in a MQTT broker to provide live to the umati.app 9 | 10 | Currently the companion specifications listed at [Specs](Specs.md) are implemented. 11 | Integrations of future additional companion specification implementations based on the [OPC 40001-1 UA for Machinery](https://www.vdma.org/viewer/-/v2article/render/2737109) are in progress. 12 | 13 | ## Location of Fair, Machine and Software icons on the dashboard 14 | 15 | ### Fair pin 16 | 17 | ![Fair](img/map_pin_fair.svg) 18 | 19 | Fair location and icon is set by fair organiser. 20 | 21 | ### Machine pin 22 | 23 | ![Machine](img/map_pin_machine_magenta.svg) 24 | 25 | The machine instance _Location_ property (according to OPC 40001-1) shall be set to the following definition: 26 | 27 | - Add GPS coordinates ` `, e.g. `N 51.257315 E 6.740885` to get a machine icon on the world map 28 | - Add fair information ` `, e.g, “METAV 1 A22” to be associated to a fair 29 | - **NOTE:** Machines can be referenced to more than one fair by providing a list of fair locations, deliminated by slash e.g. `METAV /EMO 12 D17/N 51.257315 E 6.740885` 30 | 31 | ### FAIR Shortnames 32 | 33 | Fair shortnames are defined [here](Specs/Fairs.md). 34 | 35 | ### Software 36 | 37 | ![Software](img/map_pin_software_cyan.svg) 38 | 39 | The software location will be manual set as discribed [here](Specs/Software.md). 40 | 41 | ## Dashboard Features 42 | 43 | The dashboard provides information to solve a few use cases which are common in the companion specifications. 44 | 45 | - Identifiy machines from different manufactures 46 | - Provide an status overview of the machines 47 | - Provide tool/measurment data 48 | - Provide monitoring information 49 | 50 | For the usage on fairs, the above location information provide the additional use case: 51 | 52 | - Identify machines on a fair 53 | 54 | These use cases can be access through the Overview, Machines and Software tabs, as well as the filter functionality. 55 | -------------------------------------------------------------------------------- /FAQ.md: -------------------------------------------------------------------------------- 1 | # FAQ for the Showcase 2 | 3 | ## Connectivity Issues 4 | 5 | **The gateway stop with the following error message: `The remote certificate is invalid because of errors in the certificate chain: UntrustedRoot`** 6 | TLS inspection is active on your company firewall. Please ensure that the corresponding Root CA certificate is installed on your computer. 7 | 8 | ## Organizational questions 9 | 10 | **The participant shall connect to the demonstrator scenario with a machine and/or a “value-added service” (platform, dashboard,…). Are there any number limits or is just one machine OK?** 11 | Yes, one is enough, but you are free to connect more. 12 | 13 | **After implemented umati on the machine, the umati booth will show my machine on the dashboard as well as the machines of other participants. Is my understanding, right?** 14 | We will show all connected machines at the umati dashboard at the umati booth. 15 | 16 | **Do we need to show data from other participants at our own booth?** 17 | You are free to choose. All machine data is available to all participants. 18 | 19 | ## umati Experts and booth personell 20 | 21 | **What do you expect for "umati expert" at trade fair show ground?** 22 | The expert/ambassador should be able to answer the most common questions and what the manufacturer is planning with umati. We will provide a document with a unified perspective and the questions. He should knowable to more than what is currently written in the flyer. 23 | 24 | **What should the "umati expert" do?** 25 | Be a contact for sales and customers to tell more about umati, and point to the experts a the umati booth for deeper questions. 26 | 27 | **From when do you expect to start preparation at show ground? i.e. from when he must be at show ground?** 28 | This is many up to your preparation planning. We are anticipating that all machines the connect from the show ground are up and running until Friday. Therefore, he just needs to be reachable by phone or mail to troubleshoot the connection after you have set up the machine on the fair ground. 29 | -------------------------------------------------------------------------------- /Gateway.md: -------------------------------------------------------------------------------- 1 | # Gateway 2 | 3 | To connect your local OPC UA server to the umati.app the initiative provides a software gateway. 4 | This gateway subscribes via OPC UA (Client/Server; TCP Binary) to your server and publishes the information to an MQTT broker. 5 | 6 | ~~This [gateway](https://github.com/umati/Dashboard-OPCUA-Client) is provided as an open source version based on [open62541](https://open62541.org) and currently uses a _custom_ JSON encoding for the payload. It is planned to migrate to OPC UA part 14 JSON encoding and defined topic tree, as soon as v1.05.03 is published.~~ 7 | 8 | A new version of the [gateway](https://github.com/umati/umatiGateway) is provided as an open source version based on [OPC UA .NET Standard Stack](https://github.com/OPCFoundation/UA-.NETStandard) and currently uses a _custom_ JSON encoding for the payload. The umati core team currently migrate the encoding to OPC UA part 14 UA JSON encoding and a defined topic tree. 9 | 10 | ## Architecture 11 | 12 | ### High level 13 | 14 | OPC UA server --- Gateway --- MQTT Broker --- umati.app 15 | 16 | ### With protocols 17 | 18 | - OPC UA server --- OPC UA TCP binary ---> Gateway 19 | - Gateway --- MQTT over Websockets ---> MQTT Broker 20 | - MQTT broker --- MQTT over Websockets ---> device viewing umati.app 21 | 22 | ## Configuration and connection 23 | 24 | The detailed configuration of the client and how to deploy and run it is described in the [source repository](https://github.com/umati/umatiGateway/blob/develop/docs/user/usage.md). 25 | 26 | ### The gateway is provided as 27 | 28 | - Standalone binary x86 (32bit) Linux/Windows 29 | - Standalone binary x86_64 (64bit) Linux/Windows 30 | - Standalone binary x86 (32bit) Linux .deb package for ubuntu 22.04 and 24.04 31 | - Standalone binary x86_64 (64bit) Linux .deb package for ubuntu 22.04 and 24.04 32 | - container image x86_64/arm64 33 | 34 | The binaries can be downloaded [here](https://github.com/umati/umatiGateway/releases) 35 | 36 | To obtain credentials to connect to the umati.app MQTT broker please follow [Server documentation](Server.md#connecting-an-opc-ua-server-to-umatiapp). 37 | -------------------------------------------------------------------------------- /Organization.md: -------------------------------------------------------------------------------- 1 | # Organizational and technical requirements for umati showcase participants 2 | 3 | ## Disclaimer 4 | 5 | The following documentation is phrased for in-person trade fairs. Nontheless, the requirements shall be applicable to the virtual showcase as well. 6 | 7 | --- 8 | 9 | ## umati showcase demonstration participants 10 | 11 | Please register with [info@umati.org](mailto:info@umati.org) if you intend to participate at the umati showcase demonstration to ensure you receive all necessary information. 12 | 13 | Parties involved in the showcase will offer different umati technology. We distinguish three solution types: 14 | 15 | - **Component manufacturers (C)** supply umati partner components or industrial controls with [OPC UA Server](Server.md)s according to the umati showcase specification. 16 | - **Machine tool manufacturers (M)** equip machine with ([OPC UA Server](Server.md)) according to the umati showcase specification. 17 | - **Application providers (A)** display and analyze provided data available over the umati datahub according to the umati showcase specification. 18 | 19 | Participants can provide more than one umati partner solution type. 20 | 21 | ## Memorandum of understanding 22 | 23 | Regulations concerning offered services, obligations of the participants and brand usage are collected in a **memorandum of understanding** (MoU) which participants of the umati showcase will need to sign ahead of the umati showcase demonstration. Please refer to **MoU document** for further information. (Please request a copy by mailing to [info@umati.org](mailto:info@umati.org)) 24 | 25 | Every participant is permitted to advertise his or her involvement in the umati community through the free, time-limited **"umati partner"** logo, e.g. in the web or in prints etc. Details of this permission are regulated in the individual **MoU**. 26 | 27 | ### Services offered by umati iniative include 28 | 29 | - Listing all participants on the [http://umati.org](http://umati.org) site, prints, presentations etc. where practicable in scope and extent. 30 | - Providing a corporate design to be used by all participants for free. 31 | - Advertisement flyers, press conference, social media campaign with mentioning of all participants. 32 | - Access to a partners-only repositiory with necessary files and instructions to implement a solution 33 | 34 | ### Obligations of all participants include 35 | 36 | - The “partner” is responsible to actively support the dissemination of umati amongst his customers, suppliers and market competitors. 37 | - The “partner” shall participate in demonstration scenarios by connecting a product (obsolete if the partner is an end user of machinery or software) 38 | - The “partner” is obliged to ensure the visibility of umati in his communication, which includes placing a reference to umati in his internet presence and to link to [http://umati.org](http://www.umati.org) 39 | - The “partner” should become actively involved in the development of related OPC UA standards (providing feedback on documents circulated to the partners; participation in tests, plug fests, hackathons and the like). 40 | - The “partner” shall support communication of umati, e.g. by providing statements or visuals, and permits the use of the “partner’s” logo for all public relations activities relating to umati. 41 | - The “partner” must actively announce their participation in the umati showcase demonstration ahead of the trade show, e.g. in press conferences, newsletters, advertisement, etc. 42 | - The “partner” must advertise umati at its booth in a visible way (roll-ups, banners, stickers on machines with QR code, display of informational material). 43 | - The “partner” must educate booth personnel to inform visitors about umati. At any point in time at least one expert (umati proficient) must be available at the booth. 44 | - For networking events of other marketing events, the “partner” offers at least one employee for participation. 45 | 46 | #### Obligations of participants (M) connecting machinery 47 | 48 | - Participant (M) must connect one or more machines that offer reliant data during the exhibition times. The machines do not need to be present on the fair ground. 49 | - Participant (M) agrees to full data openness, i.e. the data delivered during exhibition times may be used by any other umati showcase participant without restrictions. 50 | - Participant (M) consents that all data delivered during exhibition times are archived by umati and can be used in anonymized form for future demonstrations or tests. 51 | 52 | #### Obligations of participants (C) supplying components 53 | 54 | - Participants (C) without connected machines must verifiably offer support to other participants (M) for the connectivity to the umati.app. 55 | 56 | #### Obligations of participants (A) showing applications 57 | 58 | - Participants (A) need to be aware, show sensitivity, and communicate that the umati showcase demonstration is demonstration only, i.e., data flowing in which can be used for analysis is not real production data and cannot be used to deduct any considerations regarding the performance of any connected equipment. 59 | 60 | Please refer to the MoU for further details. In case of doubt/discrepancies to the preceding list the regulations as denoted in the MoU shall apply. 61 | 62 | A separate MoU is available for associations or other organizations that want to support umati. Please contact us at [info@umati.org](mailto:info@umati.org) for details. 63 | 64 | ## Marketing package for umati showcase participants 65 | 66 | All participants received a marketing package which will be updated as the trade fairs approach. It currently contains the following items and can be found at: [https://umati.org/Partners/partner-material/](https://umati.org/Partners/partner-material/): 67 | 68 | - **umati partner logo:** The umati Partner logo should be used in your marketing and press materials online as well as offline. 69 | 70 | - **umati sticker for the connected machines:** Each machine should be outfitted with a umati sticker. If you are connecting a machine that is not located on the fair ground, please find a suitable place for this sticker on your booth to enable visitors to access the dashboard side of your machine with this code. 71 | 72 | - **press release from umati** : informs about the showcase and the registered parties. Please use it also for your own communication as a template. Further press releases are going to follow. 73 | - **umati showcase folder** : [is currently prepared – not yet available] we will prepare a umati showcase folder, with more content and listing every partner and the booth information. 74 | - **umati dashboard:** We provide a umati dashboard via a weblink to visualize all machines connected to the showcase. You are free to use this dashboard at your own booth. The dashboard access is described in chapter 4. 75 | - **umati representative preparation/briefing:** We provide extensive documentation for your umati representatives (called umati Ambassadors), such that your employees can answer the most common questions concerning umati. For other booth personnel we provide a shortened version of this document. 76 | 77 | ### Necessary interaction by the participants are 78 | 79 | - If you publish information or are mentioning umati partnership in other places, please **keep us informed by either sending a copy or a URL to [info@umati.org](mailto:info@umati.org)** for online material. 80 | - For fairs with a central **umati booth**, there will be a logo wall with all umati partners. Please **provide a logo to us**. 81 | - For picturing your machine on the umati dashboard, please **send us a picture of the specific machine** to [info@umati.org](mailto:info@umati.org) (Image will be compressed to 1100x800 if it's larger) together with the Namespace URI of the machine in the datahub. If you do not provide a picture, we will instead display a dummy machine icon. 82 | 83 | ## Documentation, timeline and notes on implementation details for umati showcase 84 | 85 | ### Provided documents and files 86 | 87 | We have provided reference documents for the umati showcase information model as follows: 88 | 89 | - Specification of [OPC UA server](Server.md) and parameter set for umati demonstrators, offers an extensive description of the umati showcase demonstrator story, organizational and technical requirements for all participants, specification of the umati showcase [OPC UA Server](Server.md) as well as documentation, timeline and notes for the umati showcase [OPC UA Server](Server.md) and client implementations 90 | - [Memorandum of understanding](TODO:LINK) regulates the use of the brand, services offered by VDW and obligations of the participant in context to the umati showcase demonstrations, if you have registered as a umati partner already, there is no need to sign the MoU again. 91 | - for marketing materials and the umati ambassador/booth personnel documentation see [https://umati.org/Partners/partner-material/](https://umati.org/Partners/partner-material/) for current versions and details. 92 | -------------------------------------------------------------------------------- /Readme.md: -------------------------------------------------------------------------------- 1 | # Welcome to the umati Showcase Repository 2 | 3 | This repository provides the specification to connect to the umati virtual demonstration showcase. 4 | 5 | ## What is umati - the universal machine technology interface 6 | 7 | To learn more about the umati initative, please visit [https://umati.org](https://umati.org) 8 | 9 | --- 10 | 11 | ## Structure of the specification 12 | 13 | - [Overview](index.md) 14 | - [OPC UA Server](Server.md) 15 | - [OPC UA Gateway](Gateway.md) 16 | - [Dashboard](Dashboard.md) 17 | - [Implemented Specifications](Specs.md) 18 | - [Flat Glass Processing](Specs/Flatglass.md) 19 | - [Geometrical Measuring Systems](Specs/GeometricalMeasuringSystems.md) 20 | - [IJT - Tightening](Specs/WIP.md) 21 | - [MachineTool](Specs/MachineTool.md) 22 | - [MachineVision](Specs/WIP.md) 23 | - [PlasticsRubber](Specs/PlasticsRubber.md) 24 | - [Robotics](Specs/WIP.md) 25 | - [Software Solutions](Specs/Software.md) 26 | - [WoodWorking](Specs/Woodworking.md) 27 | - Upcoming Specifications 28 | - [Scales](Specs/WIP.md) 29 | - [Organizational Information](Organization.md) 30 | - [Fairs](Specs/Fairs.md) 31 | - [FAQ](FAQ.md) 32 | 33 | ## Contact 34 | 35 | Please contact us for any questions: 36 | [info@umati.org](mailto:info@umati.org) 37 | 38 | ## License 39 | 40 | All information is licensed under the [![License: CC BY-NC-SA 4.0](https://licensebuttons.net/l/by-nc-sa/4.0/80x15.png)](https://creativecommons.org/licenses/by-nc-sa/4.0/). 41 | -------------------------------------------------------------------------------- /Server.md: -------------------------------------------------------------------------------- 1 | # OPC UA Server Requirements 2 | 3 | ## Connecting an OPC UA server to umati.app 4 | 5 | ### Process summary for connecting an OPC UA server to the [umati.app](https://umati.app) 6 | 7 | 1. Fill in and sign the MoU as participant and provide a GitHub account username of the responsible person to get access to the umati community. 8 | 2. Create an Onboarding issue [here](https://github.com/umati/support/issues/new?template=Onboarding.md) (only possible with an account in the umati community on GitHub) 9 | 3. Prepare a configuration as per documentation at [Gateway Config](Gateway.md) 10 | 4. (optional) Run a local OPC UA to MQTT over Websockets gateway 11 | 5. (optional) Check whether the connection to the MQTT broker is working and your gateway is publishing data 12 | 6. There is a delay between start of publishing of machine data to the broker until they are added to the dashboard. (the browser-based umati.app) as this takes a couple of minutes to propagate to the system. 13 | 7. Send an email to [info@umati.org](mailto:info@umati.org) with an image of the machine (PNG / 1000x800 pixel or larger) and the Namespace URI of the machine in the datahub. This image will be used for the dashboard at [https://umati.app](https://umati.app/) . If you do not provide a picture, we will instead display a generic machine icon. 14 | 15 | ## OPC UA server functionalities 16 | 17 | The functional requirements for the OPC UA server provided for the umati showcase demonstration are as follows. 18 | 19 | Provide at least the OPC 40001-1 UA for Machinery namespace and a instance namespace of your machine. 20 | 21 | The minimal required profiles according to the OPC UA Specification Part 7 are listed below: 22 | 23 | - Micro Embedded Device 2017 Server Profile this includes: 24 | - 2 Sessions 25 | - Attribute Read 26 | - Ua Binary Encoding 27 | - Core 2017 Server Facet 28 | - Authentication by username and password 29 | - TCP Binary 30 | - Enhanced DataChange Subscription 2017 Server Facet (500 Monitored Items) (Model might contain more than 100 nodes) 31 | - Data Access Server Facet 32 | - With mandatory _Data Access AnalogItems_ as _OverrideItemType_ is a subtype of _AnalogItemType_ 33 | 34 | ## Getting started: OPC UA server for umati showcase 35 | 36 | This manual focuses on the special features that are relevant when creating an umati OPC UA server for this fair demonstration. The general points about the OPC UA servers are not discussed in detail, e.g. how the data is linked with the OPC UA address space. 37 | 38 | In this chapter the necessary adaptations of the OPC UA information model, some important points about the running OPC UA server and the connection to the datahub will be described in short. 39 | 40 | ### OPC UA server 41 | 42 | - Load at least the Machinery types (as defined by OPC 40001-1 UA for Machinery) and the adapted instances in two separate namespaces into the OPC UA server. 43 | - Ensure that all variables have valid values, if a variable could not be provided by the machine tool, set a neutral value. (e.g. if no override is available, set the value to 1). 44 | 45 | ### Aggregating multiple OPC UA servers 46 | 47 | The aggregation should be equivalent to an aggregation that implement the [Device Information Model Specification](https://reference.opcfoundation.org/v104/DI/v102/docs/5.9/). 48 | 49 | We define a well-known entry point (Machines, nsu=;i=1001), which contains all Machinery-Instances (normally one, but there might be several). 50 | 51 | one machine tool: 52 | 53 | ![Address space](img/Addressspace_sample.png "Addressspace sample") 54 | 55 | These two address spaces should be merged so that in the aggregated server there is only one _Machines_-Folder and each Machine instance is under this organization-node with the same NodeId-Identifiers und NodeId-URI (the NodeId-Index will be different) as in the originating OPC UA server. 56 | 57 | The required namespaces for Machinery and related Companion Specifcations is only loaded once in the aggregated server. 58 | 59 | ![Address space](img/Addressspace_aggregated.png "Adress space aggregated") 60 | -------------------------------------------------------------------------------- /Specs.md: -------------------------------------------------------------------------------- 1 | # Current implemented companion specifications 2 | 3 | - [GENERIC-Plastics&Rubber](Specs/prgeneric.md) - Generic Model for umati Plastics and Rubber 4 | - [OPC 40077 - IMM 2 MES](Specs/pr40077.md) - Data exchange between injection 5 | moulding machines and MES 6 | - [OPC 40079 - IMM 2 Robot](Specs/pr40079.md) - Data exchange between injection 7 | - [OPC 40082-1 - TCD](Specs/pr40082-1.md) - Peripheral devices – Part 1: Temperature control devices 8 | - [OPC 40082-2 - HRD](Specs/pr40082-2.md) - Peripheral devices – Part 2: Hot runner devices 9 | - [OPC 40082-3 - LSR](Specs/pr40082-3.md) - Peripheral devices – Part 3: LSR Dosing Systems 10 | - [OPC 40084-3 - EXTRUDER](Specs/pr40084-3.md) - Extrusion – Part 3: Extruder 11 | - [OPC 40084-11 - CORRUGATOR](Specs/pr40084-11.md) - Extrusion – Part 11: Corrugator 12 | - [OPC 40210 UA for Geometrical Measuring Systems](Specs/GeometricalMeasuringSystems.md) 13 | - [OPC 40301 UA for Flat Glass Processing](Specs/Flatglass.md) 14 | - [OPC 40501-1 UA for MachineTool](Specs/MachineTool.md) 15 | - [OPC 40530 UA for LaserSystems](Specs/Laser.md) 16 | - [OPC 40550 UA for Woodworking](Specs/Woodworking.md) 17 | - [Software Solutions](Specs/Software.md) 18 | -------------------------------------------------------------------------------- /Specs/Fairs.md: -------------------------------------------------------------------------------- 1 | # Defined Fair shortnames 2 | 3 | | Shortname | Description | Site | 4 | | --------- | ------------------------ | -------------------------------------- | 5 | | AMB | AMB Stuttgart | | 6 | | AMTC | automatica | | 7 | | AMTECH | AMTech Shenzhen | | 8 | | CIMT | CIMT Beijing | | 9 | | CTRL | Control Stuttgart | | 10 | | EMO | EMO | | 11 | | FORMNEXT | Formnext | | 12 | | GLASSTEC | glasstec | | 13 | | GRIND | GrindingHub Stuttgart | | 14 | | HMI | Hannover Messe | | 15 | | IMTS | IMTS | | 16 | | INNOTEQ | Innoteq | | 17 | | ITMA | ITMA Milano | | 18 | | JIMTOF | JIMTOF | | 19 | | K | K | | 20 | | LASER | Laser World of Photonics | | 21 | | LIGNA | LIGNA Hannover | | 22 | | METAV | METAV | | 23 | | SPS | SPS Nürnberg | | 24 | | VIRTUAL | Permanent virtual fair | | 25 | -------------------------------------------------------------------------------- /Specs/Flatglass.md: -------------------------------------------------------------------------------- 1 | # umati showcase information model for Flat Glass Processing 2 | 3 | In the following the umati showcase describes the additional information on top of the [OPC 40301 UA for Flat Glass Processing](https://www.vdma.org/viewer/-/v2article/render/15410388) companion specification. 4 | 5 | The following describes the umati showcase information model for Flat Glass Processing. 6 | 7 | For participants that are familiar with the information model, we have included comments and descriptions about changes between the release candidate information model and the showcase information model. 8 | 9 | All participants not familiar with the release candidate information model do not need to review these changes in detail but rather follow the described model and refer to the provided XML Nodeset files and UA modeler project. 10 | 11 | ## NodeSets for the showcase 12 | 13 | [Normative NodeSet hosted by the OPC Foundation](https://github.com/OPCFoundation/UA-Nodeset/tree/latest/Glass/Flat) 14 | 15 | ## General information valid for the umati showcase demonstration 16 | 17 | | **DISCLAIMER** | For all applications the OPC UA server is to be configured without predefined NodeIDs for the instances. Clients will need to browse Instances or translate BrowsePaths find the NodeID for accessing the address space and available instances. | 18 | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | 19 | 20 | ### Identification data 21 | 22 | The identification for machine tools are inherited from the Machinery companion specification. 23 | To fill the demo dashboard machine page with the most content the variables marked with a **strong mandatory** should be provided if you like to look the machine identification nicely. 24 | 25 | #### [**MachineIdentificationType Definition**](https://reference.opcfoundation.org/Machinery/docs/8.6/) 26 | 27 | | **Attribute** | **Value** | | | | | 28 | | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | --------------------------- | --------------- | ------------------ | --------- | 29 | | BrowseName | MachineIdentificationType | | | | | 30 | | IsAbstract | False | | | | | 31 | | Description | Contains information about the identification and nameplate of a machine | | | | | 32 | | | | | | | | 33 | | **References** | **NodeClass** | **BrowseName** | **DataType** | **TypeDefinition** | **Other** | 34 | | Subtype of the 2:FunctionalGroupType defined in OPC 10000-100, i.e. inheriting the InstanceDeclarations of that Node. | | | | | | 35 | | 0:HasProperty | Variable | 0:DefaultInstanceBrowseName | 0:QualifiedName | 0:PropertyType | | 36 | | 0:HasInterface | ObjectType | IMachineVendorNameplateType | | | | 37 | | 0:HasInterface | ObjectType | IMachineTagNameplateType | | | | 38 | | Applied from IMachineVendorNameplateType | | | | | | 39 | | 0:HasProperty | Variable | 2:ProductInstanceUri | 0:String | 0:PropertyType | M, RO | 40 | | 0:HasProperty | Variable | 2:Manufacturer | 0:LocalizedText | 0:PropertyType | M, RO | 41 | | 0:HasProperty | Variable | 2:ManufacturerUri | 0:String | 0:PropertyType | O, RO | 42 | | 0:HasProperty | Variable | **2:Model** | 0:LocalizedText | 0:PropertyType | **M**, RO | 43 | | 0:HasProperty | Variable | **2:ProductCode** | 0:String | 0:PropertyType | **M**, RO | 44 | | 0:HasProperty | Variable | 2:HardwareRevision | 0:String | 0:PropertyType | O, RO | 45 | | 0:HasProperty | Variable | **2:SoftwareRevision** | 0:String | 0:PropertyType | **M**, RO | 46 | | 0:HasProperty | Variable | **2:DeviceClass** | 0:String | 0:PropertyType | **M**, RO | 47 | | 0:HasProperty | Variable | 2:SerialNumber | 0:String | 0:PropertyType | M, RO | 48 | | 0:HasProperty | Variable | **YearOfConstruction** | UInt16 | 0:PropertyType | **M**, RO | 49 | | 0:HasProperty | Variable | MonthOfConstruction | Byte | 0:PropertyType | O, RO | 50 | | 0:HasProperty | Variable | InitialOperationDate | DateTime | 0:PropertyType | O, RO | 51 | | Applied from IMachineTagNameplateType | | | | | | 52 | | 0:HasProperty | Variable | 2:AssetId | 0:String | 0:PropertyType | O, RW | 53 | | 0:HasProperty | Variable | 2:ComponentName | 0:LocalizedText | 0:PropertyType | O, RW | 54 | | 0:HasProperty | Variable | **Location** | 0:String | 0:PropertyType | **M**, RW | 55 | 56 | #### Special requirements for correct location of the machine icon on the dashboard 57 | 58 | The instance _Location_ property is evaluated according to the special requirements detailed [here](../Dashboard.md#location-of-fair-machine-and-software-icons-on-the-dashboard) to place a map icon for the machine. 59 | 60 | #### FAIR Shortnames 61 | 62 | Fair shortnames are defined [here.](Fairs.md) 63 | 64 | ### Adaption of the provided information models for your purpose 65 | 66 | - The provided NodeSet contains the address space with the ObjectTypes, VariableTypes and DataTypes of the Flat Glass Processing companion specificaion and **must not** be changed. 67 | - Change the URI of the instance namespace (optional, but recommended) 68 | 69 | `http://www./example` 70 | 71 | - The rules for creating a URI can be found online. Please follow [this link](https://en.wikipedia.org/wiki/Uniform_Resource_Identifier). 72 | In the case of a URL as a URI, it is not necessary that the site actually exists, it only identifies the machine uniquely. In order to simplify debugging it is recommended to choose a URI which allows an identification of the machine also for third persons, e.g. by including the company name. 73 | 74 | - The machine will get a unique NamespaceURI after being integrated to the datahub by addition of a suffix to ensure unique namespaces. 75 | 76 | ## Value mapping between OPC UA companion specification and umati.app Flat Glass Processing 77 | 78 | ### Flat Glass Processing - Overview 79 | 80 | ![Overview](../img/Flatglass/Flatglass-Overview.png "Flatglass Overview") 81 | 82 | ### Flat Glass Processing - Identification 83 | 84 | ![Identification](../img/Flatglass/Flatglass-Identification.png "Flatglass Identification") 85 | 86 | ### Flat Glass Processing - Jobs 87 | 88 | ![Jobs](../img/Flatglass/Flatglass-Jobs.png "Flatglass Jobs") 89 | -------------------------------------------------------------------------------- /Specs/GeometricalMeasuringSystems.md: -------------------------------------------------------------------------------- 1 | # umati showcase information model for Geometrical Measuring Systems 2 | 3 | In the following the umati showcase describes the additional information on top of the [OPC 40210 UA for Geometrical Measuring Systems](https://www.vdma.org/viewer/-/v2article/render/47597927) companion specification. 4 | 5 | Please refer to the provided XML-Nodesets or UaModeler-project for exemplary implementation. 6 | 7 | The following describes the umati showcase information model for Geometrical Measuring Systems. 8 | 9 | For participants that are familiar with the information model, we have included comments and descriptions about changes between the release candidate information model and the showcase information model. 10 | 11 | All participants not familiar with the release candidate information model do not need to review these changes in detail but rather follow the described model and refer to the provided XML Nodeset files and UA modeler project. 12 | 13 | ## NodeSets for the showcase 14 | 15 | [Release Candidate NodeSet](https://github.com/umati/Sample-Server/tree/develop/model/GMS) 16 | 17 | ## General information valid for the umati showcase demonstration 18 | 19 | | **DISCLAIMER** | For all applications the OPC UA server is to be configured without predefined NodeIDs for the instances. Clients will need to browse Instances or translate BrowsePaths find the NodeID for accessing the address space and available instances. | 20 | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | 21 | 22 | ### Identification data 23 | 24 | The identification for machine tools are inherited from the Machinery companion specification. 25 | To fill the demo dashboard machine page with the most content the variables marked with a **strong mandatory** should be provided if you like to look the machine identification nicely. 26 | 27 | #### [**MachineIdentificationType Definition**](https://reference.opcfoundation.org/Machinery/docs/8.6/) 28 | 29 | | **Attribute** | **Value** | | | | | 30 | | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | --------------------------- | --------------- | ------------------ | --------- | 31 | | BrowseName | MachineIdentificationType | | | | | 32 | | IsAbstract | False | | | | | 33 | | Description | Contains information about the identification and nameplate of a machine | | | | | 34 | | | | | | | | 35 | | **References** | **NodeClass** | **BrowseName** | **DataType** | **TypeDefinition** | **Other** | 36 | | Subtype of the 2:FunctionalGroupType defined in OPC 10000-100, i.e. inheriting the InstanceDeclarations of that Node. | | | | | | 37 | | 0:HasProperty | Variable | 0:DefaultInstanceBrowseName | 0:QualifiedName | 0:PropertyType | | 38 | | 0:HasInterface | ObjectType | IMachineVendorNameplateType | | | | 39 | | 0:HasInterface | ObjectType | IMachineTagNameplateType | | | | 40 | | Applied from IMachineVendorNameplateType | | | | | | 41 | | 0:HasProperty | Variable | 2:ProductInstanceUri | 0:String | 0:PropertyType | M, RO | 42 | | 0:HasProperty | Variable | 2:Manufacturer | 0:LocalizedText | 0:PropertyType | M, RO | 43 | | 0:HasProperty | Variable | 2:ManufacturerUri | 0:String | 0:PropertyType | O, RO | 44 | | 0:HasProperty | Variable | **2:Model** | 0:LocalizedText | 0:PropertyType | **M**, RO | 45 | | 0:HasProperty | Variable | **2:ProductCode** | 0:String | 0:PropertyType | **M**, RO | 46 | | 0:HasProperty | Variable | 2:HardwareRevision | 0:String | 0:PropertyType | O, RO | 47 | | 0:HasProperty | Variable | **2:SoftwareRevision** | 0:String | 0:PropertyType | **M**, RO | 48 | | 0:HasProperty | Variable | 2:DeviceClass | 0:String | 0:PropertyType | **M**, RO | 49 | | 0:HasProperty | Variable | 2:SerialNumber | 0:String | 0:PropertyType | M, RO | 50 | | 0:HasProperty | Variable | **YearOfConstruction** | UInt16 | 0:PropertyType | **M**, RO | 51 | | 0:HasProperty | Variable | MonthOfConstruction | Byte | 0:PropertyType | O, RO | 52 | | 0:HasProperty | Variable | InitialOperationDate | DateTime | 0:PropertyType | O, RO | 53 | | Applied from IMachineTagNameplateType | | | | | | 54 | | 0:HasProperty | Variable | 2:AssetId | 0:String | 0:PropertyType | O, RW | 55 | | 0:HasProperty | Variable | 2:ComponentName | 0:LocalizedText | 0:PropertyType | O, RW | 56 | | 0:HasProperty | Variable | **Location** | 0:String | 0:PropertyType | **M**, RW | 57 | 58 | #### Special requirements for correct location of the machine icon on the dashboard 59 | 60 | The instance _Location_ property is evaluated according to the special requirements detailed [here](../Dashboard.md#location-of-fair-machine-and-software-icons-on-the-dashboard) to place a map icon for the machine. 61 | 62 | #### FAIR Shortnames 63 | 64 | Fair shortnames are defined [here.](Fairs.md) 65 | 66 | ### Adaption of the provided information models for your purpose 67 | 68 | - The provided NodeSet contains the address space with the ObjectTypes, VariableTypes and DataTypes of the Geometrical Measuring Systems companion specificaion and **must not** be changed. 69 | - Change the URI of the instance namespace (optional, but recommended) 70 | 71 | `http://www./example` 72 | 73 | - The rules for creating a URI can be found online. Please follow [this link](https://en.wikipedia.org/wiki/Uniform_Resource_Identifier). 74 | In the case of a URL as a URI, it is not necessary that the site actually exists, it only identifies the machine uniquely. In order to simplify debugging it is recommended to choose a URI which allows an identification of the machine also for third persons, e.g. by including the company name. 75 | 76 | - The machine will get a unique NamespaceURI after being integrated to the datahub by addition of a suffix to ensure unique namespaces. 77 | 78 | ## Value mapping between OPC UA companion specification and umati.app Geometrical Measuring Systems 79 | 80 | ### Geometrical Measuring Systems - Overview 81 | 82 | ![Overview](../img/GeometricalMeasuringSystems/GMS-Overview.png "GMS Overview") 83 | 84 | ### Active Program Statusbar 85 | 86 | For the status overview in the dashboard, the _State_ of the _ProductionActiveProgramType_ is stored and plotted over time. The status bar **does NOT relate to the stacklight** status! 87 | 88 | Each status is assigned to a color, the color scheme is here (subject to change): 89 | 90 | | State | Color | 91 | | ----------------------------- | ---------------- | 92 | | Initializing | ⚪ Gray | 93 | | Running | 🟢 Green | 94 | | Ended | 🔵 Cyan | 95 | | Interrupted | 🟠 Orange | 96 | | Aborted | 🔴 Red | 97 | | Any other (unspecified) state | ⚫ Black | 98 | 99 | A gap is left for periods of time in which no data was recorded (e.g. machine offline). An exemplary timeline is shown above. 100 | 101 | ### Geometrical Measuring Systems - Identification 102 | 103 | ![Identification](../img/GeometricalMeasuringSystems/GMS-Identification.png "GMS Identification") 104 | 105 | ### Geometrical Measuring Systems - Active Program 106 | 107 | ![ActiveProgram](../img/GeometricalMeasuringSystems/GMS-ActiveProgram.png "GMS ActiveProgram") 108 | 109 | ### Geometrical Measuring Systems - Monitoring (Machine Tool / Channel) 110 | 111 | ![Monitoring](../img/GeometricalMeasuringSystems/GMS-Monitoring.png "GMS Monitoring Machine Tool / Channel") 112 | 113 | ### Geometrical Measuring Systems - Monitoring (Working Units) 114 | 115 | ![MonitoringWorkingUnits](../img/GeometricalMeasuringSystems/GMS-Monitoring-WorkingUnit.png "GMS Monitoring Working Units") 116 | 117 | ### Geometrical Measuring Systems - Results 118 | 119 | ![Results](../img/GeometricalMeasuringSystems/GMS-Results.png "GMS Results") 120 | 121 | ### Geometrical Measuring Systems - Calibration Information 122 | 123 | ![CalibrationInformation](../img/GeometricalMeasuringSystems/GMS-CalibrationInformation.png "GMS Calibration Information") 124 | -------------------------------------------------------------------------------- /Specs/Laser.md: -------------------------------------------------------------------------------- 1 | # umati showcase information model for Laser Systems 2 | 3 | In the following the umati showcase describes the additional information on top of the [OPC 40530 UA for LaserSystems](https://reference.opcfoundation.org/LaserSystems/v100/docs/) companion specification. 4 | 5 | ## NodeSets 6 | 7 | [Normative NodeSet hosted by the OPC Foundation](https://github.com/OPCFoundation/UA-Nodeset/tree/latest/LaserSystems) 8 | 9 | ## General information valid for the umati showcase demonstration 10 | 11 | | **DISCLAIMER** | For all applications the OPC UA server is to be configured without predefined NodeIds for the instances. Clients need to utilize the Services [Browse](https://reference.opcfoundation.org/Core/docs/Part4/5.8.2/) and [TranslateBrowsePathsToNodeIds](https://reference.opcfoundation.org/Core/docs/Part4/5.8.4/) to access nodes of interest. | 12 | 13 | ### Identification data 14 | 15 | The identification for Laser Systems are inherited from the Machinery companion specification. 16 | To fill the demo dashboard machine page with the most content the variables marked with a **strong mandatory** should be provided if you like to look the machine identification nicely. 17 | 18 | #### [**MachineIdentificationType Definition**](https://reference.opcfoundation.org/Machinery/docs/8.6/) 19 | 20 | | **Attribute** | **Value** | | | | | 21 | | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | --------------------------- | --------------- | ------------------ | --------- | 22 | | BrowseName | MachineIdentificationType | | | | | 23 | | IsAbstract | False | | | | | 24 | | Description | Contains information about the identification and nameplate of a machine | | | | | 25 | | | | | | | | 26 | | **References** | **NodeClass** | **BrowseName** | **DataType** | **TypeDefinition** | **Other** | 27 | | Subtype of the 2:FunctionalGroupType defined in OPC 10000-100, i.e. inheriting the InstanceDeclarations of that Node. | | | | | | 28 | | 0:HasProperty | Variable | 0:DefaultInstanceBrowseName | 0:QualifiedName | 0:PropertyType | | 29 | | 0:HasInterface | ObjectType | IMachineVendorNameplateType | | | | 30 | | 0:HasInterface | ObjectType | IMachineTagNameplateType | | | | 31 | | Applied from IMachineVendorNameplateType | | | | | | 32 | | 0:HasProperty | Variable | 2:ProductInstanceUri | 0:String | 0:PropertyType | M, RO | 33 | | 0:HasProperty | Variable | 2:Manufacturer | 0:LocalizedText | 0:PropertyType | M, RO | 34 | | 0:HasProperty | Variable | 2:ManufacturerUri | 0:String | 0:PropertyType | O, RO | 35 | | 0:HasProperty | Variable | **2:Model** | 0:LocalizedText | 0:PropertyType | **M**, RO | 36 | | 0:HasProperty | Variable | **2:ProductCode** | 0:String | 0:PropertyType | **M**, RO | 37 | | 0:HasProperty | Variable | 2:HardwareRevision | 0:String | 0:PropertyType | O, RO | 38 | | 0:HasProperty | Variable | **2:SoftwareRevision** | 0:String | 0:PropertyType | **M**, RO | 39 | | 0:HasProperty | Variable | 2:DeviceClass | 0:String | 0:PropertyType | O, RO | 40 | | 0:HasProperty | Variable | 2:SerialNumber | 0:String | 0:PropertyType | M, RO | 41 | | 0:HasProperty | Variable | **YearOfConstruction** | UInt16 | 0:PropertyType | **M**, RO | 42 | | 0:HasProperty | Variable | MonthOfConstruction | Byte | 0:PropertyType | O, RO | 43 | | 0:HasProperty | Variable | InitialOperationDate | DateTime | 0:PropertyType | O, RO | 44 | | Applied from IMachineTagNameplateType | | | | | | 45 | | 0:HasProperty | Variable | 2:AssetId | 0:String | 0:PropertyType | O, RW | 46 | | 0:HasProperty | Variable | 2:ComponentName | 0:LocalizedText | 0:PropertyType | O, RW | 47 | | 0:HasProperty | Variable | **Location** | 0:String | 0:PropertyType | **M**, RW | 48 | 49 | #### Special requirements for correct location of the machine icon on the dashboard 50 | 51 | The instance _Location_ property is evaluated according to the special requirements detailed [here](../Dashboard.md#location-of-fair-machine-and-software-icons-on-the-dashboard) to place a map icon for the machine. 52 | 53 | ### Adaption of the provided information models for your purpose 54 | 55 | - The provided NodeSet contains the address space with the ObjectTypes, VariableTypes and DataTypes of the Laser Systems companion specification and **must not** be changed. 56 | - Change the URI of the instance namespace (optional, but recommended) 57 | 58 | `http://www./example` 59 | 60 | - The rules for creating a URI can be found online. Please follow [this link](https://en.wikipedia.org/wiki/Uniform_Resource_Identifier). 61 | In the case of a URL as a URI, it is not necessary that the site actually exists, it only identifies the machine uniquely. 62 | In order to simplify debugging it is recommended to choose a URI which allows an identification of the machine also for third persons, e.g. by including the company name. 63 | 64 | - The machine will get a unique identifier like `clientId%3Dvdw%7Csmplsrv1%3Bnsu%3Dhttp%3A_2F_2Fwww.wenzel-group.com_2FWenzel_20LH_2087_2F%3Bi%3D66382` - `` in the MQTT tree and in the Dashboard URL. 65 | 66 | ## Value mapping between OPC UA companion specification and umati.app machine instance page 67 | 68 | ### Laser System - Overview 69 | 70 | ![Overview](../img/Laser/Overview.png "Laser System Overview") 71 | 72 | ### Active Program Statusbar 73 | 74 | For the status overview in the dashboard, the _StateNumber_ of the _4:Monitoring_.LasterSystemStatus.LaserSystemState*StateMachineType.CurrentState.Number* is stored and plotted over time. The status bar **does NOT relate to the stacklight** status! 75 | 76 | Each status is assigned to a color, the color scheme is here (subject to change): 77 | 78 | | State | Number | Color | 79 | | ----------------------------- | ------ | --------------- | 80 | | Off | 0 | ⚪ Grey | 81 | | EnergySaving | 1 | ⚪ Grey | 82 | | Idle | 2 | ⚪ Grey | 83 | | SetUp | 3 | ⚪ Grey | 84 | | LaserReady | 4 | ⚪ Grey | 85 | | Maintenance | 5 | ⚪ Grey | 86 | | Error | 6 | ⚪ Grey | 87 | | LaserOn | 7 | 🟢 Green | 88 | | Any other (unspecified) state | | ⚫ Black | 89 | 90 | A gap is left for periods of time in which no data was recorded (e.g. machine offline). An exemplary timeline is shown above. 91 | 92 | ### Laser Systems - Identification 93 | 94 | ![Identification](../img/Laser/Overview.png "Identification") 95 | 96 | ### Laser Systems- Production 97 | 98 | ![Production](../img/Laser/Production.png "Production") 99 | 100 | ### Laser Systems - Monitoring 101 | 102 | ![Monitoring](../img/Laser/Monitoring.png "Monitoring") 103 | -------------------------------------------------------------------------------- /Specs/MachineTool.md: -------------------------------------------------------------------------------- 1 | # umati showcase information model for Machine Tools 2 | 3 | In the following the umati showcase describes the additional information on top of the [OPC 40501-1 UA for MachineTools](https://www.vdma.org/viewer/-/v2article/render/1322270) companion specification. 4 | 5 | Please refer to the provided XML-NodeSets, UaModeler-project or the [Sample Server](https://github.com/umati/Sample-Server) for exemplary implementation. 6 | 7 | ## NodeSets 8 | 9 | [Normative NodeSet hosted by the OPC Foundation](https://github.com/OPCFoundation/UA-Nodeset/tree/latest/MachineTool) 10 | 11 | ### For umati Machine Tool partners 12 | 13 | [UaModeler Project](https://github.com/umati/MachineTool-Plugfest/tree/master/UaModelerProject) as a quick start ( **Remark:** You have to be an umati partner and added to the access list. (Contact: [info@umati.org](mailto:info@umati.org)) 14 | 15 | ## General information valid for the umati showcase demonstration 16 | 17 | | **DISCLAIMER** | For all applications the OPC UA server is to be configured without predefined NodeIds for the instances. Clients need to utilize the Services [Browse](https://reference.opcfoundation.org/Core/docs/Part4/5.8.2/) and [TranslateBrowsePathsToNodeIds](https://reference.opcfoundation.org/Core/docs/Part4/5.8.4/) to access nodes of interest. | 18 | 19 | ### Identification data 20 | 21 | The identification for Machine Tools are inherited from the Machinery companion specification. 22 | To fill the demo dashboard machine page with the most content the variables marked with a **strong mandatory** should be provided if you like to look the machine identification nicely. 23 | 24 | #### [**MachineIdentificationType Definition**](https://reference.opcfoundation.org/Machinery/docs/8.6/) 25 | 26 | | **Attribute** | **Value** | | | | | 27 | | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | --------------------------- | --------------- | ------------------ | --------- | 28 | | BrowseName | MachineIdentificationType | | | | | 29 | | IsAbstract | False | | | | | 30 | | Description | Contains information about the identification and nameplate of a machine | | | | | 31 | | | | | | | | 32 | | **References** | **NodeClass** | **BrowseName** | **DataType** | **TypeDefinition** | **Other** | 33 | | Subtype of the 2:FunctionalGroupType defined in OPC 10000-100, i.e. inheriting the InstanceDeclarations of that Node. | | | | | | 34 | | 0:HasProperty | Variable | 0:DefaultInstanceBrowseName | 0:QualifiedName | 0:PropertyType | | 35 | | 0:HasInterface | ObjectType | IMachineVendorNameplateType | | | | 36 | | 0:HasInterface | ObjectType | IMachineTagNameplateType | | | | 37 | | Applied from IMachineVendorNameplateType | | | | | | 38 | | 0:HasProperty | Variable | 2:ProductInstanceUri | 0:String | 0:PropertyType | M, RO | 39 | | 0:HasProperty | Variable | 2:Manufacturer | 0:LocalizedText | 0:PropertyType | M, RO | 40 | | 0:HasProperty | Variable | 2:ManufacturerUri | 0:String | 0:PropertyType | O, RO | 41 | | 0:HasProperty | Variable | **2:Model** | 0:LocalizedText | 0:PropertyType | **M**, RO | 42 | | 0:HasProperty | Variable | **2:ProductCode** | 0:String | 0:PropertyType | **M**, RO | 43 | | 0:HasProperty | Variable | 2:HardwareRevision | 0:String | 0:PropertyType | O, RO | 44 | | 0:HasProperty | Variable | **2:SoftwareRevision** | 0:String | 0:PropertyType | **M**, RO | 45 | | 0:HasProperty | Variable | 2:DeviceClass | 0:String | 0:PropertyType | O, RO | 46 | | 0:HasProperty | Variable | 2:SerialNumber | 0:String | 0:PropertyType | M, RO | 47 | | 0:HasProperty | Variable | **YearOfConstruction** | UInt16 | 0:PropertyType | **M**, RO | 48 | | 0:HasProperty | Variable | MonthOfConstruction | Byte | 0:PropertyType | O, RO | 49 | | 0:HasProperty | Variable | InitialOperationDate | DateTime | 0:PropertyType | O, RO | 50 | | Applied from IMachineTagNameplateType | | | | | | 51 | | 0:HasProperty | Variable | 2:AssetId | 0:String | 0:PropertyType | O, RW | 52 | | 0:HasProperty | Variable | 2:ComponentName | 0:LocalizedText | 0:PropertyType | O, RW | 53 | | 0:HasProperty | Variable | **Location** | 0:String | 0:PropertyType | **M**, RW | 54 | 55 | #### Special requirements for correct location of the machine icon on the dashboard 56 | 57 | The instance _Location_ property is evaluated according to the special requirements detailed [here](../Dashboard.md#location-of-fair-machine-and-software-icons-on-the-dashboard) to place a map icon for the machine. 58 | 59 | ### Adaption of the provided information models for your purpose 60 | 61 | - The provided NodeSet contains the address space with the ObjectTypes, VariableTypes and DataTypes of the MachineTools companion specification and **must not** be changed. 62 | - Change the URI of the instance namespace (optional, but recommended) 63 | 64 | `http://www./example` 65 | 66 | - The rules for creating a URI can be found online. Please follow [this link](https://en.wikipedia.org/wiki/Uniform_Resource_Identifier). 67 | In the case of a URL as a URI, it is not necessary that the site actually exists, it only identifies the machine uniquely. In order to simplify debugging it is recommended to choose a URI which allows an identification of the machine also for third persons, e.g. by including the company name. 68 | 69 | - The machine will get a unique NamespaceURI after being integrated to the datahub by addition of a suffix to ensure unique namespaces. 70 | 71 | ## Value mapping between OPC UA companion specification and umati.app MachineTool page 72 | 73 | ### Machine Tool - Overview 74 | 75 | ![Overview](../img/MachineTool/MT-Overview.png "MT Overview") 76 | 77 | ### Active Program Statusbar 78 | 79 | For the status overview in the dashboard, the _StateNumber_ of the _ProductionActiveProgramType.State.CurrentState.Number_ is stored and plotted over time. The status bar **does NOT relate to the stacklight** status! 80 | 81 | Each status is assigned to a color, the color scheme is here (subject to change): 82 | 83 | | State | Number | Color | 84 | | ----------------------------- | ------ | ---------------- | 85 | | Initializing | 0 | ⚪ Grey | 86 | | Running | 1 | 🟢 Green | 87 | | Ended | 2 | 🔵 Cyan | 88 | | Interrupted | 3 | 🟠 Orange | 89 | | Aborted | 4 | 🔴 Red | 90 | | Any other (unspecified) state | | ⚫ Black | 91 | 92 | A gap is left for periods of time in which no data was recorded (e.g. machine offline). An exemplary timeline is shown above. 93 | 94 | ### Machine Tool - Identification 95 | 96 | ![Identification](../img/MachineTool/MT-Identification.png "MT Identification") 97 | 98 | ### Machine Tool - Equipment - Tools 99 | 100 | ![Tools](../img/MachineTool/MT-Tools.png "MT Tools") 101 | 102 | ### Machine Tool - Active Program 103 | 104 | ![ActiveProgram](../img/MachineTool/MT-ActiveProgram.png "MT ActiveProgram") 105 | 106 | ### Machine Tool - Monitoring (Machine Tool / Channel) 107 | 108 | ![Monitoring](../img/MachineTool/MT-Monitoring.png "MT Monitoring Machine Tool / Channel") 109 | 110 | ### Machine Tool - Monitoring (Working Units) 111 | 112 | ![Monitoring](../img/MachineTool/MT-Monitoring-WorkingUnit.png "MT Monitoring Working Units") 113 | -------------------------------------------------------------------------------- /Specs/PlasticsRubber.md: -------------------------------------------------------------------------------- 1 | # Overview of Plastics and Rubber Specifications 2 | 3 | - [OPC 40077 - IMM 2 MES](pr40077.md) - Data exchange between injection 4 | moulding machines and MES 5 | - [OPC 40079 - IMM 2 Robot](pr40079.md) - Data exchange between injection moulding machines and robots 6 | - [OPC 40082-1 - TCD](pr40082-1.md) - Peripheral devices – Part 1: Temperature control devices 7 | - [OPC 40082-2 - HRD](pr40082-2.md) - Peripheral devices – Part 2: Hot runner devices 8 | - [OPC 40082-3 - LSR](pr40082-3.md) - Peripheral devices – Part 3: LSR Dosing Systems 9 | - [OPC 40084-3 - EXTRUDER](pr40084-3.md) - Extrusion – Part 3: Extruder 10 | - [OPC 40084-11 - CORRUGATOR](pr40084-11.md) - Extrusion – Part 11: Corrugator 11 | - [GENERIC](prgeneric.md) - Generic Model for umati Plastics and Rubber 12 | 13 | **Note:** The **Generic** Model is for all plastics and rubber machine manufacturers for whose machine types no OPC UA specification exists yet. 14 | 15 | For not listed OPC UA 400xx specifications or information about the Generic Model, please contact 16 | 17 | - Marc Schmitt [marc.schmitt@vdma.org](mailto:marc.schmitt@vdma.org) 18 | -------------------------------------------------------------------------------- /Specs/Software.md: -------------------------------------------------------------------------------- 1 | # How to display a software product in the umati dashboard 2 | 3 | You are a software vendor, who creates and markets dashboarding or similiar applications. 4 | Then you can showcase you products also through the umati.app. 5 | 6 | Going forward we will create software products as a separate listing inside the umati.app. 7 | So an user of the app, will not only be able to browse connected machines but also software solutions. 8 | 9 | ## What informations will be provided to a prospect 10 | 11 | - **Manufacturer** 12 | - URL of the manufacturer/product site 13 | - **Productname** 14 | - URL of a running product instance (accessible demonstration instance, connected to the datahub, - showcaseing the connected machines) 15 | - Software icon 16 | - Software screenshot (min 1024x768px PNG) 17 | - Short description of the product (1000 char) 18 | - Fair location (hall / booth) multiple assignments in the future 19 | - GPS location to place the marker on the map to 20 | 21 | For the upcoming fairs this list will be filled manual by the fair organizer, after you provide the information and are registered for the fair. 22 | 23 | This list will be selfmanagable going forward. 24 | 25 | ## Software - Overview (example) 26 | 27 | ![Overview](../img/Software/Software-Overview.png "Software Overview") 28 | 29 | ## Software - Detail (example) 30 | 31 | ![Detail](../img/Software/Software-Detail.png "Software Detail") 32 | -------------------------------------------------------------------------------- /Specs/WIP.md: -------------------------------------------------------------------------------- 1 | # :construction: Adoption of this companion specification is planned 2 | 3 | Stay tuned. 4 | -------------------------------------------------------------------------------- /Specs/Woodworking.md: -------------------------------------------------------------------------------- 1 | # umati showcase information model for Wood Working machines 2 | 3 | In the following the umati showcase describes the additional information on top of the [OPC 40550 UA for Woodworking](https://) companion specification. 4 | 5 | Please refer to the provided XML-Nodesets or UaModeler-project for exemplary implementation. 6 | 7 | The following describes the umati showcase information model for Wood Working. 8 | 9 | For participants that are familiar with the information model, we have included comments and descriptions about changes between the release candidate information model and the showcase information model. 10 | 11 | All participants not familiar with the release candidate information model do not need to review these changes in detail but rather follow the described model and refer to the provided XML Nodeset files and UA modeler project. 12 | 13 | ## NodeSets for the showcase 14 | 15 | [Normative NodeSet hosted by the OPC Foundation](https://github.com/OPCFoundation/UA-Nodeset/tree/latest/Woodworking) 16 | 17 | ## General information valid for the umati showcase demonstration 18 | 19 | | **DISCLAIMER** | For all applications the OPC UA server is to be configured without predefined NodeIDs for the instances. Clients will need to browse Instances or translate BrowsePaths find the NodeID for accessing the address space and available instances. | 20 | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | 21 | 22 | ### Identification data 23 | 24 | The identification for machine tools are inherited from the Machinery companion specification. 25 | To fill the demo dashboard machine page with the most content the variables marked with a **strong mandatory** should be provided if you like to look the machine identification nicely. 26 | 27 | #### [**MachineIdentificationType Definition**](https://reference.opcfoundation.org/Machinery/docs/8.6/) 28 | 29 | | **Attribute** | **Value** | | | | | 30 | | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | --------------------------- | --------------- | ------------------ | --------- | 31 | | BrowseName | MachineIdentificationType | | | | | 32 | | IsAbstract | False | | | | | 33 | | Description | Contains information about the identification and nameplate of a machine | | | | | 34 | | | | | | | | 35 | | **References** | **NodeClass** | **BrowseName** | **DataType** | **TypeDefinition** | **Other** | 36 | | Subtype of the 2:FunctionalGroupType defined in OPC 10000-100, i.e. inheriting the InstanceDeclarations of that Node. | | | | | | 37 | | 0:HasProperty | Variable | 0:DefaultInstanceBrowseName | 0:QualifiedName | 0:PropertyType | | 38 | | 0:HasInterface | ObjectType | IMachineVendorNameplateType | | | | 39 | | 0:HasInterface | ObjectType | IMachineTagNameplateType | | | | 40 | | Applied from IMachineVendorNameplateType | | | | | | 41 | | 0:HasProperty | Variable | 2:ProductInstanceUri | 0:String | 0:PropertyType | M, RO | 42 | | 0:HasProperty | Variable | 2:Manufacturer | 0:LocalizedText | 0:PropertyType | M, RO | 43 | | 0:HasProperty | Variable | 2:ManufacturerUri | 0:String | 0:PropertyType | O, RO | 44 | | 0:HasProperty | Variable | **2:Model** | 0:LocalizedText | 0:PropertyType | **M**, RO | 45 | | 0:HasProperty | Variable | **2:ProductCode** | 0:String | 0:PropertyType | **M**, RO | 46 | | 0:HasProperty | Variable | 2:HardwareRevision | 0:String | 0:PropertyType | O, RO | 47 | | 0:HasProperty | Variable | **2:SoftwareRevision** | 0:String | 0:PropertyType | **M**, RO | 48 | | 0:HasProperty | Variable | 2:DeviceClass | 0:String | 0:PropertyType | **M**, RO | 49 | | 0:HasProperty | Variable | 2:SerialNumber | 0:String | 0:PropertyType | M, RO | 50 | | 0:HasProperty | Variable | **YearOfConstruction** | UInt16 | 0:PropertyType | **M**, RO | 51 | | 0:HasProperty | Variable | MonthOfConstruction | Byte | 0:PropertyType | O, RO | 52 | | 0:HasProperty | Variable | InitialOperationDate | DateTime | 0:PropertyType | O, RO | 53 | | Applied from IMachineTagNameplateType | | | | | | 54 | | 0:HasProperty | Variable | 2:AssetId | 0:String | 0:PropertyType | O, RW | 55 | | 0:HasProperty | Variable | 2:ComponentName | 0:LocalizedText | 0:PropertyType | O, RW | 56 | | 0:HasProperty | Variable | **Location** | 0:String | 0:PropertyType | **M**, RW | 57 | 58 | #### Special requirements for correct location of the machine icon on the dashboard 59 | 60 | The instance _Location_ property is evaluated according to the special requirements detailed [here](../Dashboard.md#location-of-fair-machine-and-software-icons-on-the-dashboard) to place a map icon for the machine. 61 | 62 | #### FAIR Shortnames 63 | 64 | Fair shortnames are defined [here.](Fairs.md) 65 | 66 | ### Adaption of the provided information models for your purpose 67 | 68 | - The provided NodeSet contains the address space with the ObjectTypes, VariableTypes and DataTypes of the Woodworking companion specificaion and **must not** be changed. 69 | - Change the URI of the instance namespace (optional, but recommended) 70 | 71 | `http://www./example` 72 | 73 | - The rules for creating a URI can be found online. Please follow [this link](https://en.wikipedia.org/wiki/Uniform_Resource_Identifier). 74 | In the case of a URL as a URI, it is not necessary that the site actually exists, it only identifies the machine uniquely. In order to simplify debugging it is recommended to choose a URI which allows an identification of the machine also for third persons, e.g. by including the company name. 75 | 76 | - The machine will get a unique NamespaceURI after being integrated to the datahub by addition of a suffix to ensure unique namespaces. 77 | 78 | ## Value mapping between OPC UA companion specification and umati.app Woodworking 79 | 80 | ### Wood Working - Overview 81 | 82 | ![Overview](../img/Woodworking/WWM-Overview.png "WW Overview") 83 | 84 | ### Active Program Statusbar 85 | 86 | For the status overview in the dashboard, the _State_ of the _RecipeInRun_ is stored and plotted over time. The status bar **does NOT relate to the stacklight** status! 87 | 88 | Each status is assigned to a color, the color scheme is here (subject to change): 89 | 90 | | State | Color | 91 | | ----------------------------- | ---------------- | 92 | | STANDBY | ⚪ Gray | 93 | | WORKING | 🟢 Green | 94 | | READY | 🟠 Yellow | 95 | | ERROR | 🔴 Red | 96 | | Any other (unspecified) state | ⚫ Black | 97 | 98 | A gap is left for periods of time in which no data was recorded (e.g. machine offline). An exemplary timeline is shown above. 99 | 100 | ### Wood Working - Identification 101 | 102 | ![Identification](../img/Woodworking/WWM-Identification.png "MT Identification") 103 | 104 | ### Wood Working - Active Program 105 | 106 | ![ActiveProgram](../img/Woodworking/WWM-ActiveProgram.png "MT ActiveProgram") 107 | 108 | ### Wood Working - Monitoring Stationary 109 | 110 | ![MonitoringStationary](../img/Woodworking/WWM-MonitoringStationary.png "MT Monitoring") 111 | 112 | ### Wood Working - Monitoring Throughfeed 113 | 114 | ![MonitoringThroughfeed](../img/Woodworking/WWM-MonitoringThroughfeed.png "MT Monitoring") 115 | 116 | ### Device Classes 117 | 118 | Based on the _DeviceClass_ the image for the individual machine page is selected. 119 | 120 | This is the current mapping: 121 | 122 | #### Throughfeed 123 | 124 | - ProfilingMachine 125 | - EdgebandingMachine 126 | - BoringMachine 127 | - SandingMachine 128 | - HandlingMachine 129 | 130 | #### Stationary 131 | 132 | - MachiningCenter 133 | - Press 134 | - SawingMachine 135 | -------------------------------------------------------------------------------- /Specs/pr40079.md: -------------------------------------------------------------------------------- 1 | # umati showcase information model for Plastics and Rubber machines OPC 40079 2 | 3 | ## 1. General 4 | 5 | The namespace for the instances is manufacturer specific, e.g. 6 | 7 | For integrating OPC 40079 in the umati demonstrator it is necessary to combine the models for the IMM (injection moulding machine) and the robot in one entry point for the cell. For this an additional model opc40079forumati.xml with the ObjectType ImmRobotCellType has been created: 8 | 9 | ### Table 1 – ImmRobotCellType Definition 10 | 11 | ![OPC 40079 ImmRobotCellType](../img/PlasticsRubber/PR_40079_ImmRobotCellType.png "OPC 40079 ImmRobotCellType") 12 | 13 | ![OPC 40079 Overview](../img/PlasticsRubber/PR_40079_Overview.png "OPC 40079 Overview") 14 | 15 | ### Figure 1 – ImmRobotCellType overview 16 | 17 | The MachineIdentificationType is defined in OPC UA for Machinery. It includes basic information about a machine which are displayed in the umati dashboard (manufacturer, serial number, …). 18 | To show the combination of IMM and robot, the cell is handles as one machine for the dashboard. To make the different manufacturers and models of IMM and robot visible in the overview, the variables Manufacturer and Model inside the Identification object shall be filled with both information. Examples: 19 | 20 | Identification -> Manufacturer: “KraussMaffei / Kuka” 21 | 22 | Identification -> Model: “GX G02 / KR CYBERTECH ARC” 23 | 24 | In the detailed view of the cell, the manufacturers and model are displayed separately. For this, the Variables ImmManufacturer, ImmModel, RobotManufacturer and RobotModel are used. It is not required to have separate instances of the MachineIdentificationType for the IMM and the robot. 25 | 26 | Download: [Compleate documentation umati showcase information model Plastics and Rubber](https://github.com/umati/Showcase/tree/main/img/PlasticsRubber/PR_40079_PDF.pdf) 27 | 28 | Table 2 provides a list of namespaces and their index used for BrowseNames in this document. 29 | 30 | ### Table 2 – Namespaces used in this document 31 | 32 | | **NamespaceURI** | **Namespace Index** | **Example** | 33 | | :------------------------------------------------------- | :------------------ | :-------------------------------------------------------------------------------- | 34 | | | 0 | 0:NodeVersion | 35 | | | 1 | Default namespace of this specification --> no prefix used, e.g. ImmRobotCellType | 36 | | | 2 | 2:DeviceClass | 37 | | | 3 | 3:MachineIdentificationType | 38 | | | 4 | 4:ImmToRobotType | 39 | 40 | Table 3 shows the complete structure of the instance needed for the umati demonstrator. The demonstrator requires, that all mandatory elements of the ImmRobotCellType are existent, even if there are not displayed in the dashboard. If the value of a variable a not displayed, is can be filled with a static dummy value (e.g. empty string). All displayed values are marked in **bold**. 41 | 42 | ### Table 3 – Sample instance of ImmRobotCellType 43 | 44 | | **BrowseName** | **Type** | **Example Value** | **Remarks** | 45 | | ------------------------------------------------------------------ | :-------------------------- | :---------------------------------------------------- | :---------- | 46 | | Objects | | | | 47 | |  Machines | | | | 48 | |     | ImmRobotCellType | | | 49 | |     2:Identification | 4:MachineIdentificationType | | | 50 | |      2:ProductInstanceUri | | “” | 1) | 51 | |      **2:Manufacturer** | 0:LocalizedText | “Sample IMM Manufacturer / Sample Robot Manufacturer” | | 52 | |      **2:Model** | 0:LocalizedText | “Machine Model 3000 / Robot 99” | 2) | 53 | |      2:SerialNumber | 0:String | “Cell123” | 1) | 54 | |      **4:Location** | 0:String | “K 14 F42/N 51.260407 E 6.744588” | 2), 3) | 55 | | | | | | 56 | |     **ImmManufacturer** | 0:String | “Sample IMM Manufacturer” | | 57 | |     **ImmModel** | 0:String | “Machine Model 3000” | | 58 | |     **RobotManufacturer** | 0:String | “Sample Robot Manufacturer” | | 59 | |     **RobotModel** | 0:String | “Robot 99”” | | 60 | | | | | | 61 | |     Imm | 4:ImmToRobotType | | | 62 | |      4:EndOfOrder | 0:Boolean | false | 1) | 63 | |      4:ImmOperationActive | 0:Boolean | true | 1) | 64 | |      4:PrepareForOperationWithImm | 0:Boolean | true | 1) | 65 | |      **4:RobotMessageId_confirmed** | 0:UInt32 | 587 | | 66 | |      Mould_1 | 4:MouldType | | | 67 | |       0:NodeVersion | 0:String | “1” | 1) | 68 | |       4:MovablePlaten | 4:ImmAxisType | | | 69 | |        4:**InPosition1** | 0:Boolean | false | | 70 | |        4:**InPosition2** | 0:Boolean | true | | 71 | |        4:**Movement** | 4:MovementEnum | 0 (=NOT_MOVING) | | 72 | | | | | | 73 | |     Robot | 4:RobotToImmType | | | 74 | |      4:OperationWithImmRequested | 0:Boolean | true | 1) | 75 | |      **4:OperationWithImmActive** | 0:Boolean | true | | 76 | |      4:ReadyForOperationWithImm | 0:Boolean | true | 1) | 77 | |      **4:RobotMessageId** | 0:UInt32 | 587 | | 78 | |      MouldInteraction_1 | 4:MouldInteractionType | | | 79 | |       **4:MouldAreaFree** | 0:Boolean | true | | 80 | |       4:EnableMovablePlaten | 4:EnableImmAxisType | | | 81 | |        4:RelevantForInteraction | 0:Boolean | true | 1) | 82 | |        **4:EnableToPosition1** | 0:Boolean | true | | 83 | |        **4:EnableToPosition2** | 0:Boolean | true | | 84 | 85 | 1. This variable is mandatory in the model but will not be displayed in the demonstrator 86 | 2. Not mandatory in OPC UA for Machinery but for this model and will be displayed in the demonstrator 87 | 3. See for rules for filling the location. 88 | -------------------------------------------------------------------------------- /Specs/pr40082-1.md: -------------------------------------------------------------------------------- 1 | # umati showcase information model for Plastics and Rubber machines OPC 40082-1 2 | 3 | ## 1. General 4 | 5 | The namespace for the instances is manufacturer specific, e.g. 6 | 7 | Table 2 shows the complete structure of the instance needed for the umati demonstrator. The demonstrator requires, that all mandatory elements of the TCD_InterfaceType are existent, even if there are not displayed in the dashboard. If the value of a variable a not displayed, is can be filled with a static dummy value (e.g. empty string). All displayed values are marked in **bold**. 8 | 9 | Important: In OPC 40082-1 it is defined, that the instance of the TCD_InterfaceType is located under the Object DeviceSet. For umati it is necessary to add it under the Machines folder defined by OPC UA for machinery. In practice it is not necessary to create a new instance. It is sufficient to have an Organizes Reference from the Machines folder to the instance located under DeviceSet 10 | 11 | ![OPC 40082-1 Overview](../img/PlasticsRubber/PR_40082-1_Overview.png "OPC 40082-1 Overview") 12 | 13 | In addition, OPC 40082-1 uses the MachineInformationType defined in OPC 40083. For participation in the umati demonstrator it is necessary to create in parallel an instance of the MachineIdentificationType defined in OPC UA for Machinery. 14 | 15 | Download: [Compleate documentation umati showcase information model Plastics and Rubber](https://github.com/umati/Showcase/tree/main/img/PlasticsRubber/PR_40082-1_PDF.pdf) 16 | 17 | ### Table 1 – Namespaces used in this document 18 | 19 | | **NamespaceURI** | **Namespace Index** | **Example** | 20 | | :--------------------------------------------------------- | :------------------ | :-------------------------------------------------------------------------- | 21 | | | 0 | 0:NodeVersion | 22 | | | 1 | Default namespace of OPC 40082-1 --> no prefix used, e.g. TCD_InterfaceType | 23 | | | 2 | 2:DeviceClass | 24 | | | 3 | 3:MachineInformationType | 25 | | | 4 | 4:MachineIdentificationType | 26 | 27 | ### Table 2 – Sample instance of TCD_InterfaceType 28 | 29 | | **BrowseName** | **Type** | **Example Value** | **Remarks** | 30 | | -------------------------------------------------------------- | :-------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------- | 31 | | Objects | | | | 32 | |  Machines | | | | 33 | |    TCD*<Manufacturer>*<SerialNumber> | TCD_InterfaceType | | | 34 | |     2:Identification | 4:MachineIdentificationType | | 1) | 35 | |      2:ProductInstanceUri | | “” | 2) | 36 | |      **2:Manufacturer** | 0:LocalizedText | “Sample Manufacturer” | | 37 | |      **2:Model** | 0:LocalizedText | “TCD 3000” | 3) | 38 | |      **2:SerialNumber** | 0:String | “1234” | | 39 | |      **2:DeviceClass** | 0:String | “Temperature Control Device” | | 40 | |      **4:Location** | 0:String | “K 14 F42/N 51.260407 E 6.744588” | 3), 4) | 41 | | | | | | 42 | |     Identification | 3:IdentificationType | | 2) | 43 | |      2:DeviceClass | 0:String | “Temperature Control Device” | 2) | 44 | |      2:Manufacturer | 0:LocalizedText | “Sample Manufacturer” | 2) | 45 | |      2:Model | 0:LocalizedText | “TCD 3000” | 2) | 46 | |      2:SerialNumber | 0:String | “1234” | 2) | 47 | | | | | | 48 | |     MachineConfiguration | 3:MachineConfigurationType | | 2) | 49 | |      3:UserMachineName | 0:String | “My TCD” | 2) | 50 | |      3:LocationName | 0:String | “K 14 F42/N 51.260407 E 6.744588” | 2) | 51 | |      3:TimeZoneOffset | 0:TimeZoneDataType |

_offset_: 0

_daylightSavingInOffset:_ true

| 2) | 52 | | | | | | 53 | |     TCDSpecification | TCDSpecificationType | | | 54 | |      ConnectedLoad | 0:AnalogItemType à 0:Double | 10.2 | 2) | 55 | |       EURange | 0:Range |

Low: 0

High: 20

| 2) | 56 | |       EngineeringUnits | 0:EUInformation |

namespaceUri: “”

unitId: 4937556

displayName: “kw”

description: “kilowatt”

| 2) | 57 | |      **MaxTemperature** | 0:AnalogItemType à 0:Double | 160 | | 58 | |       **EURange** | 0:Range |

Low: 0

High: 200

| | 59 | |       **EngineeringUnits** | 0:EUInformation |

namespaceUri: “”

unitId: 4408652

**displayName: “°C”**

description: “degree Celsius”

| | 60 | |      **NominalFlowRate** | 0:AnalogItemType à 0:Double | 45 | | 61 | |       **EURange** | 0:Range |

Low: 0

High: 100

| | 62 | |       **EngineeringUnits** | 0:EUInformation |

namespaceUri: “”

unitId: 19506

**displayName: “l/min”**

description: “litre per minute”

| | 63 | |      **PowerValue** | 0:AnalogItemType à 0:Double | 8 | | 64 | |       **EURange** | 0:Range |

Low: 0

High: 20

| | 65 | |       **EngineeringUnits** | 0:EUInformation |

namespaceUri: “”

unitId: 4937556

**displayName: “kw”**

description: “kilowatt”

| | 66 | | | | | | 67 | |     Operation | OperationType | | | 68 | |      ActiveErrors | 3:ActiveErrorDataType | _empty array / NULL_ | 2) | 69 | |      DeviceMappingNumber | 0:UInt32 | 1 | 2) | 70 | |      HighestAlarmSeverity | 0:UInt16 | 0 | 2) | 71 | |      **OperationMode** | OperatingModeEnumeration | 2 (= NORMAL_OPERATION) | | 72 | |     DeviceZone | DeviceZoneType | | | 73 | |      Temperature | 3:ControlledParameterType | | | 74 | |       **ActualValue** | 0:AnalogItemType à 0:Double | 122.4 | | 75 | |        **EURange** | 0:Range |

Low: 0

High: 200

| | 76 | |        **EngineeringUnits** | 0:EUInformation |

namespaceUri: “”

unitId: 4408652

**displayName: “°C”**

description: “degree Celsius”

| | 77 | 78 | 1. Not included in OPC 40084-1 TCD_InterfaceType. To be added in the instance 79 | 2. This variable is mandatory in the model but will not be displayed in the demonstrator 80 | 3. Not mandatory in OPC UA for Machinery but for this model and will be displayed in the demonstrator 81 | 4. See for rules for filling the location. 82 | -------------------------------------------------------------------------------- /Specs/pr40082-3.md: -------------------------------------------------------------------------------- 1 | # umati showcase information model for Plastics and Rubber machines OPC 40082-3 2 | 3 | ## 1. General 4 | 5 | The namespace for the instances is manufacturer specific, e.g. 6 | 7 | Table 2 shows the complete structure of the instance needed for the umati demonstrator. The demonstrator requires, that all mandatory elements of the LDD_InterfaceType are existent, even if there are not displayed in the dashboard. If the value of a variable a not displayed, is can be filled with a static dummy value (e.g. empty string). All displayed values are marked in **bold**. 8 | 9 | Important: In OPC 40082-2 it is defined, that the instance of the LDD_InterfaceType is located under the Object DeviceSet. For umati it is necessary to add it under the Machines folder defined by OPC UA for machinery. In practice it is not necessary to create a new instance. It is sufficient to have an Organizes Reference from the Machines folder to the instance located under DeviceSet. 10 | 11 | ![OPC 40082-3 Overview](../img/PlasticsRubber/PR_40082-3_Overview.png "OPC 40082-3 Overview") 12 | 13 | In addition, OPC 40082-3 uses the MachineInformationType defined in OPC 40083. For participation in the umati demonstrator it is necessary to create in parallel an instance of the MachineIdentificationType defined in OPC UA for Machinery. 14 | 15 | Download: [Compleate documentation umati showcase information model Plastics and Rubber](https://github.com/umati/Showcase/tree/main/img/PlasticsRubber/PR_40082-3_PDF.pdf) 16 | 17 | ### Table 1 – Namespaces used in this document 18 | 19 | | **NamespaceURI** | **Namespace Index** | **Example** | 20 | | :--------------------------------------------------------- | :------------------ | :-------------------------------------------------------------------------- | 21 | | | 0 | 0:NodeVersion | 22 | | | 1 | Default namespace of OPC 40082-3 --> no prefix used, e.g. LDS_InterfaceType | 23 | | | 2 | 2:DeviceClass | 24 | | | 3 | 3:MachineInformationType | 25 | | | 4 | 4:MachineIdentificationType | 26 | 27 | ### Table 2 – Sample instance of LDS_InterfaceType 28 | 29 | | **BrowseName** | **Type** | **Example Value** | **Remarks** | 30 | | -------------------------------------------------------------- | :--------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------ | :---------- | 31 | | Objects | | | | 32 | |  Machines | | | | 33 | |    LDS*<Manufacturer>*<SerialNumber> | LDS_InterfaceType | | | 34 | |     2:Identification | 4:MachineIdentificationType | | 1) | 35 | |      2:ProductInstanceUri | | “” | 2) | 36 | |      **2:Manufacturer** | 0:LocalizedText | “Sample Manufacturer” | | 37 | |      **2:Model** | 0:LocalizedText | “LDS 3000” | 3) | 38 | |      **2:SerialNumber** | 0:String | “1234” | | 39 | |      **2:DeviceClass** | 0:String | “LSR Dosing System” | | 40 | |      **4:Location** | 0:String | “K 14 F42/N 51.260407 E 6.744588” | 3), 4) | 41 | | | | | | 42 | |     Identification | 3:IdentificationType | | 2) | 43 | |      2:DeviceClass | 0:String | “LSR Dosing System” | 2) | 44 | |      2:Manufacturer | 0:LocalizedText | “Sample Manufacturer” | 2) | 45 | |      2:Model | 0:LocalizedText | “LDS 3000” | 2) | 46 | |      2:SerialNumber | 0:String | “1234” | 2) | 47 | | | | | | 48 | |     MachineConfiguration | 3:MachineConfigurationType | | 2) | 49 | |      3:UserMachineName | 0:String | “My LDS” | 2) | 50 | |      3:LocationName | 0:String | “K 14 F42/N 51.260407 E 6.744588” | 2) | 51 | |      3:TimeZoneOffset | 0:TimeZoneDataType |

_offset_: 0

_daylightSavingInOffset:_ true

| 2) | 52 | | | | | | 53 | |     Operation | OperationType | | | 54 | |      ActivateRemoteControl | 0:MultiStateValueDiscreteType | 1 (= SEPARATE_INTERFACE) | 2) | 55 | |      ActiveErrors | 3:ClassifiedActiveErrorDataType | _empty array / NULL_ | 2) | 56 | |      DeliveryPressure | 3:ControlledParameterType | | | 57 | |       **ActualValue** | 0:AnalogItemType à 0:Double | 2.4 | | 58 | |        **EURange** | 0:Range |

Low: 0

High: 40

| | 59 | |        **EngineeringUnits** | 0:EUInformation |

namespaceUri: “”

unitId: 4342098

displayName: “bar”

description: “bar [unit of pressure]”

| | 60 | |      DeliveryType | 0:MultiStateValueDiscreteType | 0 (= PRESSURE) | 2) | 61 | |      DeviceMappingNumber | 0:UInt32 | 1 | 2) | 62 | |      HighestAlarmSeverity | 0:UInt16 | 0 | 2) | 63 | |      MaterialBalanceSystemType | MaterialBalanceSystemType
Enumeration | 0 (= NOT_AVAILABLE) | 2) | 64 | |      RemoteControlActivated | 0:MultiStateValueDiscreteType | 1 (= SEPARATE_INTERFACE) | 2) | 65 | | | | | | 66 | |      Component_A | ComponentType | | | 67 | |       **Status** | ComponentStatusEnumeration | 0 (= GOOD) | | 68 | |      Component_B | ComponentType | | | 69 | |       **Status** | ComponentStatusEnumeration | 0 (= GOOD) | | 70 | 71 | 1. Not included in OPC 40084-3 LDS_InterfaceType. To be added in the instance 72 | 2. This variable is mandatory in the model but will not be displayed in the demonstrator 73 | 3. Not mandatory in OPC UA for Machinery but for this model and will be displayed in the demonstrator 74 | 4. See for rules for filling the location. 75 | -------------------------------------------------------------------------------- /Specs/pr40084-11.md: -------------------------------------------------------------------------------- 1 | # umati showcase information model for Plastics and Rubber machines OPC 40084-11 2 | 3 | ## 1. General 4 | 5 | The namespace for the instances is manufacturer specific, e.g. 6 | 7 | Table 2 shows the complete structure of the instance needed for the umati demonstrator. The demonstrator requires, that all mandatory elements of the Corrugator_InterfaceType are existent, even if there are not displayed in the dashboard. If the value of a variable a not displayed, is can be filled with a static dummy value (e.g. empty string). All displayed values are marked in **bold**. 8 | 9 | Important: Version 2.0 of OPC 40084-11 must be used which defines, that the instance of the Corrugator_InterfaceType is located under the Machines folder defined by OPC UA for machinery and that the MachineIdentificationType (also defined in OPC UA for Machinery) is used for the identification. 10 | 11 | Download: [Complete documentation umati showcase information model Plastics and Rubber](https://github.com/umati/Showcase/tree/main/img/PlasticsRubber/PR_40084-11_PDF.pdf) 12 | 13 | ### Table 1 – Namespaces used in this document 14 | 15 | | **NamespaceURI** | **Namespace Index** | **Example** | 16 | | :---------------------------------------------------------------------- | :------------------ | :-------------------------- | 17 | | | 0 | 0:NodeVersion | 18 | | | 2 | 2:DeviceClass | 19 | | | 3 | 3:MachineInformationType | 20 | | | 4 | 4:ExtrusionDeviceType | 21 | | | 5 | 5:ClampClosed | 22 | | | 6 | 6:MachineIdentificationType | 23 | 24 | The default namespace OPC 40084-11 is not listed since all BrowseNames without prefix use this default namespace. 25 | 26 | ### Table 2 – Sample instance of OPC 40084-11 27 | 28 | 29 | 30 | | **BrowseName** | **Type** | **Example Value** | **Remarks** | 31 | | ---------------------------------------------------------------- | :------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------- | 32 | | Objects | | | | 33 | |  Machines | | | | 34 | |    Corrugator*<Manufacturer>*<SerialNumber> | Extruder_InterfaceType | | | 35 | |     4:IsPresent | 0:Boolean | true | 1) | 36 | |     4:LineId | 0:String | “Foil line 1” | 1) | 37 | |     3:SupportedLogbookEvents | 3:LogbookEventsEnumeration[] | _empty array / NULL_ | 1) | 38 | | | | | | 39 | |     2:Identification | 6:MachineIdentificationType | | | 40 | |      2:ProductInstanceUri | | “” | 1) | 41 | |      **2:Manufacturer** | 0:LocalizedText | “Sample Manufacturer” | | 42 | |      **2:Model** | 0:LocalizedText | “Corrugator 3000” | 2) | 43 | |      **2:SerialNumber** | 0:String | “1234” | | 44 | |      **2:DeviceClass** | 0:String | “Corrugator” | | 45 | |      **5:Location** | 0:String | “K 14 F42/N 51.260407 E 6.744588” | 2), 3) | 46 | |      ControllerName | 0:String | “My Controller” | 1) | 47 | | | | | | 48 | |     6:MachineryBuildingBlocks | 0:FolderType | | | 49 | |      2:Identification | 6:MachineIdentificationType | Reference to the instance _Identification_ above | | 50 | |      2:MachineryItemState | 4:ExtrusionMachineryItemState_StateMachineType | | | 51 | |       **CurrentState** | 0:LocalizedText | “Executing” | | 52 | |       Id | 0:NodeId | ns=4;i=5092 | 1) | 53 | |       4:ExtrusionExecutingSubState | 4:ExtrusionExecutingSubState\_
StateMachineType | | 1) | 54 | |        CurrentState | 0:LocalizedText | “ControlledRun” | 1) | 55 | |        Id | 0:NodeId | ns=4;i=5070 | 1) | 56 | | | | | | 57 | |      2:MachineryOperationMode | 6:MachineryOperationModeStateMachineType | | | 58 | |       CurrentState | 0:LocalizedText | “Processing” | | 59 | |       Id | 0:NodeId | ns=6;i=5026 | | 60 | | | | | | 61 | |     **5:ClampClosed** | 0:Boolean | true | | 62 | |     **ExtruderEnabled** | 0:Boolean | true | | 63 | |     **MouldId** | 0:String | “Mould 42” | | 64 | | | | | | 65 | |     5:Drives | 3:DrivesType | | 1), 4) | 66 | |      0:NodeVersion | 0:String | “1” | 1) | 67 | |      **MainDrive_1** | 3:DriveType | | | 68 | |     – **Position** | 0:String | “Main Drive” | | 69 | |     – 3:**ActualValue** | 0:AnalogItemType -> 0:Double | 40.5 | | 70 | |      – EURange | 0:Range | Low: 0, High: 80 | | 71 | |      – EngineeringUnits | 0:EUInformation |

namespaceUri: “http://www.opcfoundation.org/UA/units/un/cefact”

unitId: 12888

displayName: “m/min”

description: “metre per minute”

| | 72 | | | | | | 73 | |    5:TemperatureZones | 4:ExtrusionTemperatureZonesType | | | 74 | |    – 0:NodeVersion | 0:String | “1” | 1) | 75 | |    - **TemperatureZone_1** | 4:ExtrusionTemperatureZoneType | | | 76 | |     – **Id** | 0:String | “Mould Temperature” | | 77 | |     – IsPresent | 0:Boolean | true | 1) | 78 | |     – ControlMode | 3:ControlModeEnumeration | 0 (=AUTOMATIC) | 1) | 79 | |     – **3:ActualValue** | 0:AnalogItemType -> 0:Double | 37.5 | | 80 | |      – EURange | 0:Range | Low: 0, High: 100 | | 81 | |      – EngineeringUnits | 0:EUInformation |

namespaceUri: “http://www.opcfoundation.org/UA/units/un/cefact”

unitId: 4408652

displayName: “°C”

description: “degree Celsius”

| | 82 | 83 | 84 | 85 | 1. This variable is mandatory in the model but will not be displayed in the demonstrator 86 | 2. Not mandatory in used specifications but for this model and will be displayed in the demonstrator 87 | 3. See for rules for filling the location. 88 | 4. Container object is mandatory in the model, but no instances inside (besides Variable NodeVersion) needed. 89 | -------------------------------------------------------------------------------- /Specs/pr40084-3.md: -------------------------------------------------------------------------------- 1 | # umati showcase information model for Plastics and Rubber machines OPC 40084-3 2 | 3 | ## 1. General 4 | 5 | The namespace for the instances is manufacturer specific, e.g. 6 | 7 | Table 2 shows the complete structure of the instance needed for the umati demonstrator. The demonstrator requires, that all mandatory elements of the Extruder_InterfaceType are existent, even if there are not displayed in the dashboard. If the value of a variable a not displayed, is can be filled with a static dummy value (e.g. empty string). All displayed values are marked in **bold**. 8 | 9 | Important: Version 2.0 of OPC 40084-3 must be used which defines, that the instance of the Extruder_InterfaceType is located under the Machines folder defined by OPC UA for machinery and that the MachineIdentificationType (also defined in OPC UA for Machinery) is used for the identification. 10 | 11 | Download: [Compleate documentation umati showcase information model Plastics and Rubber](https://github.com/umati/Showcase/tree/main/img/PlasticsRubber/PR_40084-3_PDF.pdf) 12 | 13 | ### Table 1 – Namespaces used in this document 14 | 15 | | **NamespaceURI** | **Namespace Index** | **Example** | 16 | | :---------------------------------------------------------------------- | :------------------ | :----------------------- | 17 | | | 0 | 0:NodeVersion | 18 | | | 2 | 2:DeviceClass | 19 | | | 3 | 3:MachineInformationType | 20 | | | 4 | 4:ExtrusionDeviceType | 21 | | | 5 | 5:Machines | 22 | 23 | ### Table 2 – Sample instance of OPC 40084-3 24 | 25 | 26 | 27 | | **BrowseName** | **Type** | **Example Value** | **Remarks** | 28 | | ---------------------------------------------------------------- | :-------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------- | 29 | | Objects | | | | 30 | |  Machines | | | | 31 | |   Extruder*<Manufacturer>*<SerialNumber> | Extruder_InterfaceType | | | 32 | |    4:IsPresent | 0:Boolean | true | 1) | 33 | |    4:LineId | 0:String | “Foil line 1” | 1) | 34 | |    3:SupportedLogbookEvents | 3:LogbookEventsEnumeration[] | _empty array / NULL_ | 1) | 35 | | | | | | 36 | |     2:Identification | 5:MachineIdentificationType | | | 37 | |      2:ProductInstanceUri | | “” | 1) | 38 | |      **2:Manufacturer** | 0:LocalizedText | “Sample Manufacturer” | | 39 | |      **2:Model** | 0:LocalizedText | “Extruder 3000” | 2) | 40 | |      **2:SerialNumber** | 0:String | “987” | | 41 | |      **2:DeviceClass** | 0:String | “Extruder” | | 42 | |      **5:Location** | 0:String | “K 14 F42/N 51.260407 E 6.744588” | 2), 3) | 43 | |      ControllerName | 0:String | “My Controller” | 1) | 44 | | | | | | 45 | |     5:MachineryBuildingBlocks | 0:FolderType | | | 46 | |      2:Identification | 5:MachineIdentificationType | Reference to the instance _Identification_ above | | 47 | |      2:MachineryItemState | 4:ExtrusionMachineryItemState\_
StateMachineType | | | 48 | |       CurrentState | 0:LocalizedText | “Executing” | | 49 | |       Id | 0:NodeId | ns=4;i=5092 | 1) | 50 | |       4:ExtrusionExecutingSubState | 4:ExtrusionExecutingSubState\_
StateMachineType | | 1) | 51 | |        **CurrentState** | 0:LocalizedText | “ControlledRun” | 1) | 52 | |        Id | 0:NodeId | ns=4;i=5070 | 1) | 53 | | | | | | 54 | |      2:MachineryOperationMode | 5:MachineryOperationMode
StateMachineType | | | 55 | |       CurrentState | 0:LocalizedText | “Processing” | | 56 | |       Id | 0:NodeId | ns=5;i=5026 | | 57 | | | | | | 58 | |     Users | 3:UsersType | | 1), 4) | 59 | |      0:NodeVersion | 0:String | “1” | 1) | 60 | | | | | | 61 | |     TemperatureZones | 3:TemperatureZonesType | | | 62 | |      0:NodeVersion | 0:String | “1” | 1) | 63 | |      TemperatureZone_001 | 4:ExtrusionTemperatureZoneType | | | 64 | |       **3:Id** | 0:String | “Temperature Zone 1” | 1) | 65 | |       3:IsPresent | 0:Boolean | true | 1) | 66 | |       3:ControlMode | 3:ControlModeEnumeration | 2 (= AUTOMATIC) | 1) | 67 | |       **3:ActualValue** | 0:AnalogItemType à 0:Double | 120.5 | | 68 | |        **EURange** | 0:Range |

Low: 0

High: 200

| 1) | 69 | |        **EngineeringUnits** | 0:EUInformation |

namespaceUri: “
units/un/cefact”

unitId: 4408652

**displayName: “°C”**

description: “degree Celsius”

| | 70 | 71 | 72 | 73 | 1. This variable is mandatory in the model but will not be displayed in the demonstrator 74 | 2. Not mandatory in OPC UA for Machinery but for this model and will be displayed in the demonstrator 75 | 3. See for rules for filling the location. 76 | 4. Container object is mandatory in the model, but no instances inside (besides Variable NodeVersion) needed. 77 | -------------------------------------------------------------------------------- /Specs/pr40084-9.md: -------------------------------------------------------------------------------- 1 | # umati showcase information model for Plastics and Rubber machines OPC 40084-9 2 | 3 | ## 1. General 4 | 5 | The namespace for the instances is manufacturer specific, e.g. 6 | 7 | Table 2 shows the complete structure of the instance needed for the umati demonstrator. The demonstrator requires, that all mandatory elements of the Cutter_InterfaceType are existent, even if there are not displayed in the dashboard. If the value of a variable a not displayed, is can be filled with a static dummy value (e.g. empty string). All displayed values are highlighted in **bold**. 8 | 9 | Important: Version 2.0 of OPC 40084-9 must be used which defines, that the instance of the Cutter_InterfaceType is located under the Machines folder defined by OPC UA for machinery and that the MachineIdentificationType (also defined in OPC UA for Machinery) is used for the identification. 10 | 11 | Download: [Compleate documentation umati showcase information model Plastics and Rubber](https://github.com/umati/Showcase/tree/main/img/PlasticsRubber/PR_40084-9_PDF.pdf) 12 | 13 | ### Table 1 – Namespaces used in this document 14 | 15 | | **NamespaceURI** | **Namespace Index** | **Example** | 16 | | :---------------------------------------------------------------------- | :------------------ | :-------------------------- | 17 | | | 0 | 0:NodeVersion | 18 | | | 2 | 2:DeviceClass | 19 | | | 3 | 3:MachineInformationType | 20 | | | 4 | 4:ExtrusionDeviceType | 21 | | | 5 | 5:MachineIdentificationType | 22 | 23 | The default namespace OPC 40084-9 is not listed since all BrowseNames without prefix use this default namespace. 24 | 25 | ### Table 2 – Sample instance of OPC 40084-9 26 | 27 | 28 | 29 | | **BrowseName** | **Type** | **Example Value** | **Remarks** | 30 | | ---------------------------------------------------------------- | :-------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------- | 31 | | Objects | | | | 32 | |  Machines | | | | 33 | |   Cutter*<Manufacturer>*<SerialNumber> | Cutter_InterfaceType | | | 34 | |    – 4:IsPresent | 0:Boolean | true | 1) | 35 | |    – 4:LineId | 0:String | “Profile line 1” | 1) | 36 | |    – 3:SupportedLogbookEvents | 3:LogbookEventsEnumeration[] | _empty array / NULL_ | 1) | 37 | | | | | | 38 | |     2:Identification | 5:MachineIdentificationType | | | 39 | |     – 2:ProductInstanceUri | | “” | 1) | 40 | |     – **2:Manufacturer** | 0:LocalizedText | “Sample Manufacturer” | | 41 | |     – **2:Model** | 0:LocalizedText | “Cutter 3000” | 2) | 42 | |     – **2:SerialNumber** | 0:String | “1234” | | 43 | |     – **2:DeviceClass** | 0:String | “Cutter” | | 44 | |     – **5:Location** | 0:String | “K 14 F42/N 51.260407 E 6.744588” | 2), 3) | 45 | |     – ControllerName | 0:String | “My Controller” | 1) | 46 | | | | | | 47 | |     6:MachineryBuildingBlocks | 0:FolderType | | | 48 | |      2:Identification | 5:MachineIdentificationType | Reference to the instance _Identification_ above | | 49 | |      2:MachineryItemState | 4:ExtrusionMachineryItemState\_
StateMachineType | | | 50 | |      – **CurrentState** | 0:LocalizedText | “Executing” | | 51 | |      – Id | 0:NodeId | ns=4;i=5092 | 1) | 52 | |       4:ExtrusionExecutingSubState | 4:ExtrusionExecutingSubState\_
StateMachineType | | 1) | 53 | |       – CurrentState | 0:LocalizedText | “ControlledRun” | 1) | 54 | |       – Id | 0:NodeId | ns=4;i=5070 | 1) | 55 | | | | | | 56 | |      2:MachineryOperationMode | 5:MachineryOperationMode
StateMachineType | | | 57 | |      – CurrentState | 0:LocalizedText | “Processing” | 1) | 58 | |      – Id | 0:NodeId | ns=5;i=5026 | 1) | 59 | | | | | | 60 | |     CuttingProducts | | | | 61 | |     – ActualCuttingProductId | 0:String | “Profile42 400mm” | 1) | 62 | |      CuttingProduct_1 | CuttingProductType | | | 63 | |      – **Id** | 0:String | “Profile42 400mm” | | 64 | |      – **Length** | 0:AnalogItemType à 0:Double | 400 | | 65 | |       – EngineeringUnits | 0:EUInformation |

namespaceUri: “http://www.opcfoundation.org/UA/units/un/cefact”

unitId: 5066068

**displayName: “mm”**

description: “millimetre”

| | 66 | |      – SetOutput | 0:UInt64 | 1000 | 1) | 67 | |      – ActualOutput | 0:UInt64 | 100 | 1) | 68 | |      – **TotalOutput** | 0:UInt64 | 100 | | 69 | 70 | 71 | 72 | 1. This variable is mandatory in the model but will not be displayed in the demonstrator 73 | 2. Not mandatory in OPC UA for Machinery but for this model and will be displayed in the demonstrator 74 | 3. See for rules for filling the location. 75 | 4. Container object is mandatory in the model, but no instances inside (besides Variable NodeVersion) needed. 76 | -------------------------------------------------------------------------------- /Specs/prgeneric.md: -------------------------------------------------------------------------------- 1 | # umati showcase information model for Plastics and Rubber machines Generic Model 2 | 3 | ## 1. General 4 | 5 | The namespace for the instances is manufacturer specific, e.g. 6 | 7 | Table 1 shows the complete structure of the instance needed for the umati demonstrator when two process values are used. The demonstrator requires, that all mandatory elements of used MachineIdentificationType are existent, even if there are not displayed in the dashboard. 8 | If the value of a variable a not displayed, is can be filled with a static dummy value (e.g. empty string). All displayed values are marked in **bold**. 9 | 10 | **Note:** Please contact [Mikula Thiem](mailto:mikula.thiem@vdma.org) if your machine type (Section 2) is not available. 11 | 12 | ![Generic Overview](../img/PlasticsRubber/PR_Generic_Overview.png "Generic Overview") 13 | 14 | Download: [Compleate documentation umati showcase information model Plastics and Rubber](https://github.com/umati/Showcase/tree/main/img/PlasticsRubber/PR_Generic_PDF.pdf) 15 | 16 | ### Table 1 – Sample instance of UmatiPlasticsRubberGenericType 17 | 18 | 19 | 20 | | **BrowseName** | **Type** | **Example Value** | **Remarks** | 21 | | :------------------------------------------------ | :----------------------------------------- | :-------------------------------------- | :---------- | 22 | | Objects | | | | 23 | |   Machines | | | | 24 | |    <EntryNodeforMachine> | UmatiPlasticsRubberGenericType | | | 25 | |     2:Identification | 3:MachineIdentificationType | | | 26 | |      2:ProductInstanceUri | | “” | 1) | 27 | |      **2:Manufacturer** | 0:LocalizedText | “Sample Manufacturer” | | 28 | |      **2:Model** | 0:LocalizedText | “Machine Model 3000” | 2) | 29 | |      **2:SerialNumber** | 0:String | “BM123” | | 30 | |      **2:DeviceClass** | 0:String | “Blow moulding machine” | | 31 | |      **3:Location** | 0:String | “K 14 F42/N 51.260407 E 6.744588” | 2), 3) | 32 | | | | | | 33 | |     3:MachineryBulidingBlocks | 0:FolderType | | | 34 | |      MachineryItemState | 3:MachineryItemState\_
StateMachineType | | | 35 | |       **0:CurrentState** | 0:LocalizedText | “Executing” | | 36 | |        0:Id | 0:NodeId | ns=3,i=5006 | 1) | 37 | | | | | | 38 | |     ProcessValue_1 | ProcessValueType | | | 39 | |      **Name** | 0:String | “Temperature” | | 40 | |      **Value** | 0:Double | 120.5 | | 41 | |      **Unit** | 0:String | “°C” | | 42 | | | | | | 43 | |     ProcessValue_2 | ProcessValueType | | | 44 | |      **Name** | 0:String | “Pressure” | | 45 | |      **Value** | 0:Double | 5.2 | | 46 | |      **Unit** | 0:String | “bar” | | 47 | 48 | 49 | 50 | 1. This variable is mandatory in the model but will not be displayed in the demonstrator 51 | 2. Not mandatory in OPC UA for Machinery but for this model and will be displayed in the demonstrator 52 | 3. See for rules for filling the location. 53 | 54 | ## 2. Process values for different machine types 55 | 56 | The process values are modelled as optional placeholder in the generic model. This allows the model to be used for different machine types with reasonable effort. However, the contents should be the same for all machines of the same type. 57 | -------------------------------------------------------------------------------- /_config.yml: -------------------------------------------------------------------------------- 1 | theme: jekyll-theme-minimal 2 | title: umati showcase specification 3 | description: This provides the specification to connect to the umati showcase 4 | logo: img/umati_logo.svg 5 | show_downloads: false 6 | plugins: 7 | - jemoji 8 | - jekyll-titles-from-headings 9 | - jekyll-sitemap 10 | 11 | relative_links: 12 | enabled: true 13 | collections: false 14 | -------------------------------------------------------------------------------- /assets/css/style.scss: -------------------------------------------------------------------------------- 1 | --- 2 | --- 3 | 4 | @import "jekyll-theme-minimal"; 5 | @media print, screen and (min-width: 1060px) { 6 | .wrapper { 7 | width:1060px; 8 | margin:0 auto; 9 | } 10 | 11 | section { 12 | width:700px; 13 | float:right; 14 | padding-bottom:50px; 15 | } 16 | } 17 | -------------------------------------------------------------------------------- /img/Addressspace_aggregated.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Addressspace_aggregated.png -------------------------------------------------------------------------------- /img/Addressspace_sample.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Addressspace_sample.png -------------------------------------------------------------------------------- /img/Fairconnect.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Fairconnect.png -------------------------------------------------------------------------------- /img/Flatglass/Flatglass-Identification.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Flatglass/Flatglass-Identification.png -------------------------------------------------------------------------------- /img/Flatglass/Flatglass-Jobs.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Flatglass/Flatglass-Jobs.png -------------------------------------------------------------------------------- /img/Flatglass/Flatglass-Overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Flatglass/Flatglass-Overview.png -------------------------------------------------------------------------------- /img/GeometricalMeasuringSystems/GMS-ActiveProgram.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/GeometricalMeasuringSystems/GMS-ActiveProgram.png -------------------------------------------------------------------------------- /img/GeometricalMeasuringSystems/GMS-CalibrationInformation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/GeometricalMeasuringSystems/GMS-CalibrationInformation.png -------------------------------------------------------------------------------- /img/GeometricalMeasuringSystems/GMS-Identification.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/GeometricalMeasuringSystems/GMS-Identification.png -------------------------------------------------------------------------------- /img/GeometricalMeasuringSystems/GMS-Monitoring-WorkingUnit.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/GeometricalMeasuringSystems/GMS-Monitoring-WorkingUnit.png -------------------------------------------------------------------------------- /img/GeometricalMeasuringSystems/GMS-Monitoring.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/GeometricalMeasuringSystems/GMS-Monitoring.png -------------------------------------------------------------------------------- /img/GeometricalMeasuringSystems/GMS-Overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/GeometricalMeasuringSystems/GMS-Overview.png -------------------------------------------------------------------------------- /img/GeometricalMeasuringSystems/GMS-Results.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/GeometricalMeasuringSystems/GMS-Results.png -------------------------------------------------------------------------------- /img/Laser/Monitoring.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Laser/Monitoring.png -------------------------------------------------------------------------------- /img/Laser/Overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Laser/Overview.png -------------------------------------------------------------------------------- /img/Laser/Production.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Laser/Production.png -------------------------------------------------------------------------------- /img/MachineTool/MT-ActiveProgram.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/MachineTool/MT-ActiveProgram.png -------------------------------------------------------------------------------- /img/MachineTool/MT-Identification.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/MachineTool/MT-Identification.png -------------------------------------------------------------------------------- /img/MachineTool/MT-Monitoring-WorkingUnit.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/MachineTool/MT-Monitoring-WorkingUnit.png -------------------------------------------------------------------------------- /img/MachineTool/MT-Monitoring.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/MachineTool/MT-Monitoring.png -------------------------------------------------------------------------------- /img/MachineTool/MT-Overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/MachineTool/MT-Overview.png -------------------------------------------------------------------------------- /img/MachineTool/MT-Tools.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/MachineTool/MT-Tools.png -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_40077_Overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_40077_Overview.png -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_40077_PDF.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_40077_PDF.pdf -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_40079_ImmRobotCellType.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_40079_ImmRobotCellType.png -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_40079_Overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_40079_Overview.png -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_40079_PDF.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_40079_PDF.pdf -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_40082-1_Overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_40082-1_Overview.png -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_40082-1_PDF.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_40082-1_PDF.pdf -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_40082-2_Overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_40082-2_Overview.png -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_40082-2_PDF.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_40082-2_PDF.pdf -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_40082-3_Overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_40082-3_Overview.png -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_40082-3_PDF.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_40082-3_PDF.pdf -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_40084-11_PDF.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_40084-11_PDF.pdf -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_40084-3_PDF.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_40084-3_PDF.pdf -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_40084-9_PDF.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_40084-9_PDF.pdf -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_Generic_Overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_Generic_Overview.png -------------------------------------------------------------------------------- /img/PlasticsRubber/PR_Generic_PDF.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/PlasticsRubber/PR_Generic_PDF.pdf -------------------------------------------------------------------------------- /img/Software/Software-Detail.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Software/Software-Detail.png -------------------------------------------------------------------------------- /img/Software/Software-Overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Software/Software-Overview.png -------------------------------------------------------------------------------- /img/VPN.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/VPN.png -------------------------------------------------------------------------------- /img/WWM-ActiveProgram.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/WWM-ActiveProgram.png -------------------------------------------------------------------------------- /img/Woodworking/WWM-ActiveProgram.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Woodworking/WWM-ActiveProgram.png -------------------------------------------------------------------------------- /img/Woodworking/WWM-Identification.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Woodworking/WWM-Identification.png -------------------------------------------------------------------------------- /img/Woodworking/WWM-MonitoringStationary.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Woodworking/WWM-MonitoringStationary.png -------------------------------------------------------------------------------- /img/Woodworking/WWM-MonitoringThroughfeed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Woodworking/WWM-MonitoringThroughfeed.png -------------------------------------------------------------------------------- /img/Woodworking/WWM-Overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/umati/Showcase/44e7ba914c116c785d50b061b8456ee5e9c7831b/img/Woodworking/WWM-Overview.png -------------------------------------------------------------------------------- /img/map_pin_fair.svg: -------------------------------------------------------------------------------- 1 | 4 | -------------------------------------------------------------------------------- /img/map_pin_machine_magenta.svg: -------------------------------------------------------------------------------- 1 | 4 | -------------------------------------------------------------------------------- /img/map_pin_software_cyan.svg: -------------------------------------------------------------------------------- 1 | 4 | -------------------------------------------------------------------------------- /index.md: -------------------------------------------------------------------------------- 1 | # General Information 2 | 3 | - This document provides **all information** to get connected to the umati showcase demonstrator scenario. 4 | - Participants who connect to the showcase, need to do so **on their own**, or with the help of their controls or software supplier. 5 | - The umati project group **cannot** supply individual support on how to get [OPC UA Servers](Server.md) installed, online and deliver data. 6 | - If questions arise regarding the information provided in **this documentation** or the connection to umati showcase demonstrator, please open an issue [here](https://github.com/umati/support). 7 | 8 | - An FAQ is provided [here](FAQ.md) and will be updated as needed. 9 | 10 | ## What is umati - the universal machine technology interface 11 | 12 | To learn more please visit [https://umati.org](https://umati.org) 13 | 14 | --- 15 | 16 | ## Structure of the specification 17 | 18 | - [Overview](index.md) 19 | - [OPC UA Server](Server.md) 20 | - [OPC UA Gateway](Gateway.md) 21 | - [Dashboard](Dashboard.md) 22 | - [Implemented Specifications](Specs.md) 23 | - [Flat Glass Processing](Specs/Flatglass.md) 24 | - [Geometrical Measuring Systems](Specs/GeometricalMeasuringSystems.md) 25 | - [IJT - Tightening](Specs/WIP.md) 26 | - [LaserSystems](Specs/Laser.md) 27 | - [MachineTool](Specs/MachineTool.md) 28 | - [MachineVision](Specs/WIP.md) 29 | - [PlasticsRubber](Specs/PlasticsRubber.md) 30 | - [Robotics](Specs/WIP.md) 31 | - [Software Solutions](Specs/Software.md) 32 | - [WoodWorking](Specs/Woodworking.md) 33 | - Upcoming Specifications 34 | - [Scales](Specs/WIP.md) 35 | - [Organizational Information](Organization.md) 36 | - [Fairs](Specs/Fairs.md) 37 | - [FAQ](FAQ.md) 38 | 39 | ### Versioning 40 | 41 | This documentation is versioned, as some content details will be delivered later in time. Please refer to the latest version at [https://showcase.umati.org](https://showcase.umati.org) to receive the latest draft. If any errors or inconsistencies strike your attention, please contact us via [info@umati.org](mailto:info@umati.org) so that we can include the improvement in the next version: 42 | 43 | | **Version** | **Date published** | **Note on changes** | 44 | | ----------- | ------------------ | ----------------------------------------------- | 45 | | v0.01.0 | 08.07.2020 | First draft | 46 | | v1.00.0 | 21.07.2020 | First release | 47 | | v1.01.0 | 11.08.2020 | Update on Machine Tools and Fairs | 48 | | v1.02.0 | 28.08.2020 | Update on Machine Tools and Fairs | 49 | | v1.02.1 | 02.10.2020 | Update on Machine Tools | 50 | | v1.02.2 | 23.11.2020 | Update License and activate CLA | 51 | | v1.02.3 | 18.02.2021 | Update on Machine Tools and Software Solutions | 52 | | v1.03.0 | 21.05.2021 | Complete update to latest developments | 53 | | v1.04.0 | 03.09.2021 | Addition of Woodworking companion specification | 54 | | v1.04.1 | 08.02.2022 | Updates to Machine Tools, Woodworking | 55 | | v1.05.0 | 03.03.2022 | Integrates Geomentrical Measuring Systems | 56 | | v1.06.0 | 13.07.2022 | Integrates PlasticsRubber specifications | 57 | | v1.07.0 | 17.03.2023 | Remove Datahub and OpenVPN requirements | 58 | | v1.08.0 | 15.01.2025 | Integrate LaserSystems | 59 | 60 | ### Changelog 61 | 62 | | Doc | Area | Description | Commit | 63 | | --------------------------------------------------------------------- | -------------------------- | -------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 64 | | [Dashboard](Dashboard.md) | Dashboard | Extend the datahub section | [122940e](https://github.com/umati/Showcase/commit/122940ebdd091251cbe5a028c3ffe719b5b6ec63) | 65 | | [License](LICENSE) | License | Update of Repository License | [1e4f3d9](https://github.com/umati/Showcase/commit/1e4f3d934e4e4420554d0509fff11ba4f853e2f3) | 66 | | [MachineTool](Specs/MachineTool.md) | Mapping of information | Pictures of app with mapping added | [f59f93d](https://github.com/umati/Showcase/commit/f59f93dc4eda4bdf4bf00efc53f8560bc6108b35) | 67 | | [MachineTool](Specs/MachineTool.md) | Fair Specification | SoftwareRevision mandatory | [117ce4b](https://github.com/umati/Showcase/pull/16/commits/117ce4bde7a57574de1240e76d2d3aa1160bd517) | 68 | | [MachineTool](Specs/MachineTool.md) | NodeSets for Machine Tools | Clarification on prototyping nodeset for showcase | [a2c4926](https://github.com/umati/Showcase/commit/a2c49264ca66caf6813de1ad8a5706d83ec3aa46) [7628b8a](https://github.com/umati/Showcase/commit/7628b8af38c41da2e01dac70f3d8f8be44f8949c) | 69 | | [Fairs](Specs/Fairs.md) | Shortnames | Update of the fair shortnames | [084e061](https://github.com/umati/Showcase/commit/084e0611be0bf4618e17c07260dd24d397e31ce0) [7a63e15](https://github.com/umati/Showcase/pull/16/commits/7a63e15d3e0fe691630e07814ad9e82dfe2f92b0) | 70 | | [Software](Specs/Software.md) | Software Solutions | Dashboard will show software solutions | [231ffc1](https://github.com/umati/Showcase/commit/231ffc1089b60020570286e095011defcee29b3b) [3b193a3](https://github.com/umati/Showcase/commit/3b193a34d1e64d3e93153023345073ae70e97423) | 71 | | [MachineTool](Specs/MachineTool.md) | Description | Clarification of nodesets and requirements | [c61c73f](https://github.com/umati/Showcase/commit/c61c73fa74b17dce58fd7c938f9992746dbf688d) [e9313fb](https://github.com/umati/Showcase/commit/e9313fb65cd264aee6c256a43e3fd758b737c449) | 72 | | [MachineTool](Specs/MachineTool.md) | Mapping | Updated pictures and mapping | [938a064](https://github.com/umati/Showcase/commit/938a0645771e879ca7cb5ab79be7706b0d4267d4) | 73 | | [Server](Server.md) | Fairconnect | Updated fairconnect and connection possibilities | [4f46e04](https://github.com/umati/Showcase/commit/4f46e04431582ccbd1c6714cbd018255e1d09262) | 74 | | [Woodworking](Specs/Woodworking.md) | Specfication | Added specification for Woodworking companion specification | [7642c16](https://github.com/umati/Showcase/commit/7642c16db5f13a44fa8862483a8af8cd43fb43ec) | 75 | | [Organizational Information](Organization.md) | Timeline | Removed the obsolete timeline for a 2020 showcase | [2416d15](https://github.com/umati/Showcase/commit/2416d1569cc43267d86530a934dcab267833d7fb) | 76 | | [MachineTool](Specs/MachineTool.md) | Links | Updates broken links | [5e1af5c](https://github.com/umati/Showcase/commit/5e1af5ce1649addc68d87b87dd1323806a9194e3) | 77 | | [Woodworking](Specs/Woodworking.md) | Links | Updates broken links | [5e1af5c](https://github.com/umati/Showcase/commit/5e1af5ce1649addc68d87b87dd1323806a9194e3) | 78 | | [Geometrical Measuring Systems](Specs/GeometricalMeasuringSystems.md) | GMS | Adds specification page | [49c11bc](https://github.com/umati/Showcase/commit/49c11bc70113b8ceb4ea718e8cef5e27dd9ec5ff) | 79 | | [PlasticsRubber](Specs/PlasticsRubber.md) | PlasticsRubber | Adds specifications 40077, 40079 RC, 40082-1, 40082-2, 40082-3, 40084-2, 40084-11, PRGeneric | [5c95751](https://github.com/umati/Showcase/commit/5c95751e6a9220ed2fdda5f030d841a8b22e944b) | 80 | | [LaserSystems](Specs/Laser.md) | LaserSystems | Adds specification 40530 | [8391639](https://github.com/umati/Showcase/commit/839163922925d93c733563f6c99b133f2ccc120c) | 81 | 82 | ## Demonstrator story umati showcase 83 | 84 | ### The umati vision 85 | 86 | Connectivity with umati - universal machine technology interface - is simple, secure and future-oriented. Any machine with an umati interface can be easily connected with applications. 87 | No matter whether you are end user, system integrator or machine builder: with the umati endorsed companion specficiations you will be able to easily connect to machines of all manufacturers and controls. 88 | umati is an initiative by the umati community and is an association of companies from the mechanical and plant engineering industry that jointly and comprehensively bring a common interface concept based on OPC UA to the market for the entire mechanical and plant engineering sector. 89 | 90 | Currently it is sponsored and hosted by the German Machine Tool Builders' Association [(VDW)](https://vdw.de) and the mechanical engineering industry association [(VDMA)](https://vdma.org). 91 | 92 | ## umati showcase 93 | 94 | This showcase demonstrates how **umati partners** connect components, machines and applications via a connectivity showcase. 95 | This showcase targets decision-makers in the machinery industry with a uniform marketing strategy and demonstrations showing the depth of the umati interface: from umati component suppliers over umati machine builders to umati partner applications that cumulate the data in dashboards, ERP, MES and cloud systems. 96 | 97 | Trade fair guests will get information about umati at the virtual showcase and will be offered a hands-on experience via a white-label dashboard. The dashboard offers data of each individual machine connected through umati. The dashboard is easily accessible through any web browser with individual QR codes offering weblinks at each machine. It further offers responsive design for mobile end users. 98 | 99 | Marketing for umati will be visible at the virtual showcase. Central umati marketing events will offer general information, depict specific use cases, offer Q&A sessions and deliver experience reports over the duration of the trade fair. Marketing statements for umati showcase are coordinated centrally and distributed to all showcase participants. Please refer to chapter 3 for further details. 100 | 101 | Ramp-up for all umati showcase demonstrations will be available in advance of the virtual showcase with an offered exemplary umati showcase test server. 102 | --------------------------------------------------------------------------------