-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated information + CS release (#17)
* Release v1.02.01 * Updated information + CS release * Update of app pictures
- Loading branch information
1 parent
86910d3
commit a38fea7
Showing
10 changed files
with
63 additions
and
34 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,16 +13,16 @@ Please register with [[email protected]](mailto:[email protected]) if you intend to pa | |
| Parties involved in the showcase will offer different umati technology. We distinguish three solution types: | ||
|
|
||
| - **Component manufacturers (C)** supply umati partner components or industrial controls with [OPC UA Server](SERVER.md)s according to the umati showcase specification. | ||
| - **Machine tool manufacturers (M)** equip machine tools with the umati interface ([OPC UA Server](SERVER.md)) according to the umati showcase specification. | ||
| - **Application providers (A)** display and analyze provided data available over the umati interface according to the umati showcase specification. | ||
| - **Machine tool manufacturers (M)** equip machine with ([OPC UA Server](SERVER.md)) according to the umati showcase specification. | ||
| - **Application providers (A)** display and analyze provided data available over the umati datahub according to the umati showcase specification. | ||
|
|
||
| Participants can provide more than one umati partner solution type. | ||
|
|
||
| ## Memorandum of understanding | ||
|
|
||
| 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 [[email protected]](mailto:[email protected])) | ||
|
|
||
| Every participant is permitted to advertise his or her involvement in the umati project through the free, time-limited **"umati partner"** logo, e.g. in the web or in prints etc. This permission ends one year after publication of the first umati OPC UA Companion Specification (OPC 40001-1 UA for Machinery). A product-assigned label will follow. | ||
| 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**. | ||
|
|
||
| ### Services offered by umati iniative include | ||
|
|
||
|
|
@@ -34,10 +34,8 @@ Every participant is permitted to advertise his or her involvement in the umati | |
| ### Obligations of all participants include | ||
|
|
||
| - The “partner” is responsible to actively support the dissemination of umati amongst his customers, suppliers and market competitors. | ||
| - The “partner” shall participate in demonstration scenarios by connecting a product (obsolete | ||
| if the partner is an end user of machinery or software) | ||
| - 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) | ||
| - The “partner” shall participate in demonstration scenarios by connecting a product (obsolete if the partner is an end user of machinery or software) | ||
| - 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) | ||
| - 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). | ||
| - 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. | ||
| - 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. | ||
|
|
@@ -55,11 +53,13 @@ placing a reference to umati in his internet presence and to link to [http://uma | |
|
|
||
| - Participants (C) without connected machines must verifiably offer support to other participants (M) for the connectivity via the umati interface. | ||
|
|
||
| Obligations of participants (A) showing applications | ||
| #### Obligations of participants (A) showing applications | ||
|
|
||
| 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. | ||
| - 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. | ||
|
|
||
| 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. A separate MoU is available for associations or other organizations that want to support umati. Please contact us at [[email protected]](mailto:[email protected]) for details. | ||
| 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. | ||
|
|
||
| A separate MoU is available for associations or other organizations that want to support umati. Please contact us at [[email protected]](mailto:[email protected]) for details. | ||
|
|
||
| ## Marketing package for umati showcase participants | ||
|
|
||
|
|
@@ -97,12 +97,13 @@ Infrastructures and tools are still under development. In the following you find | |
|
|
||
| | **Item** | **Supplier** | **Prototype available for all umati showcase participants** | **Design Freeze for umati showcase** | | ||
| | --- | --- | --- | --- | | ||
| | **Information Model Outline** | umati Initiative | 21.07.2020 | | ||
| | **Parameter Specification** | umati Initiative | 21.07.2020 | 31.08.2020 | | ||
| | **Server Functionality Specification** | umati Initiative | 21.07.2020 | | ||
| | **Information Model Outline Machine Tools** | umati Initiative | 21.07.2020 | [available](https://github.com/umati/Showcase/commit/86910d3ccae820a3b683a6edab1125e79425faad) | | ||
| | **Information Model Outline Future Machinery** | umati Initiative | tbd | | ||
| | **Parameter Specification Machine Tools** | umati Initiative | 21.07.2020 | [31.08.2020](https://github.com/umati/Showcase/commit/86910d3ccae820a3b683a6edab1125e79425faad) | | ||
| | **Server Functionality Specification** | umati Initiative | 21.07.2020 | [availabe](https://github.com/umati/Showcase/commit/86910d3ccae820a3b683a6edab1125e79425faad) | ||
| | **Dashboard** | umati | available | | ||
| | **Testserver** | umati | available | | ||
| | **Datahub update** | T-Systems | 23.08.2020 | 31.08.2020 | | ||
| | **Datahub update** | T-Systems | 23.08.2020 | available | | ||
| | **OpenVPN configuration** | T-Systems | available | | ||
| | **Authentication at the datahub ([OPC UA Server](SERVER.md))** | T-Systems | available | | ||
|
|
||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,12 +1,8 @@ | ||
| # umati showcase information model for Machine Tools | ||
|
|
||
| In the following the umati showcase OPC UA Information Model for **Machine Tools** describes the additional informations on top of the [OPC 40501-1 UA for MachineTools](https://opcua.vdma.org/catalog-detail/-/catalog/3914) companion specification. | ||
| Please refer to the provided xml-Nodesets or UaModeler-project for exemplary implementation. | ||
|
|
||
| ## umati showcase information model based on current standardization activities | ||
| In the following the umati showcase describes the additional information on top of the [OPC 40501-1 UA for MachineTools](https://opcua.vdma.org/catalog-detail/-/catalog/3914) companion specification. | ||
|
|
||
| The umati showcase information model highly relies on the information model release candidate [published](https://opcua.vdma.org/catalog-detail/-/catalog/3914) in May 2020. | ||
| Furthermore a few bugfixes are incorporated in the nodeset files provided. | ||
| Please refer to the provided xml-Nodesets or UaModeler-project for exemplary implementation. | ||
|
|
||
| ## Changes/Deletions/Exceptions to the release candidate information model | ||
|
|
||
|
|
@@ -18,16 +14,16 @@ All participants not familiar with the release candidate information model do no | |
|
|
||
| ### NodeSets for the showcase | ||
|
|
||
| [Release Candidate NodeSet](https://github.com/umati/MachineTool-Plugfest/tree/master/UaModelerProject) | ||
| [Release NodeSet](https://github.com/umati/MachineTool-Plugfest/tree/master/UaModelerProject) | ||
|
|
||
| [Protoyping NodeSet](https://github.com/umati/MachineTool-Plugfest/tree/master/UaModelerProtoyping) | ||
|
|
||
| **Remark:** You have to be umati partner and added to the access list. (Contact: [[email protected]](mailto:[email protected])) | ||
|
|
||
| ### Prototyping vs Non-Prototyping Machine Tools Nodesets | ||
|
|
||
| The OPC UA companion specification for Machine Tools uses the *OrderedListType*, which was introduced in [OPC 10001-13 / Errata 1.04.7](https://opcfoundation.org/developer-tools/specifications-unified-architecture/specification-release-candidates-for-review/). | ||
| This specific nodeset can only be integrated to an OPC UA server, which also supports this amendment. As severals SDKs and toolchains are not yet updated to 1.04.7 and do not allow the exchange of namespace 0, we provide the prototyping nodeset which is compatible to all 1.04 Servers. The prototyping nodeset introduces an additional namespace `http://vdw.de/protoyping/`, which adds the required ObjectTypes of the amendmend to the address space. | ||
| The OPC UA companion specification for Machine Tools uses the *OrderedListType*, which was introduced in [OPC 10001-13 / Errata 1.04.7](https://reference.opcfoundation.org/v104/Core/docs/Amendment13/). | ||
| This specific nodeset can only be integrated to an OPC UA server, which also supports this amendment. As severals SDKs and toolchains are not yet updated to 1.04.7 and do not allow the exchange of namespace 0, we provide the prototyping nodeset which is compatible to all 1.04 Servers. The prototyping nodeset introduces an additional namespace `http://vdw.de/protoyping/`, which adds the required ObjectTypes of the amendment to the address space. | ||
|
|
||
| To determine if your toolchain is compatible with the OPC UA companion specification for Machine Tools specification, check for the *OrderedListType* (NodeId `ns0;i=23518`) and have a look at `Root->Objects->Server->Namespaces->http://opcfoundation.org/UA/->NamespaceVersion` (NodeId: `ns0;i=15959`) whether the version is greater or equal to 1.04.7. If the toolchain is not compatible, stick with the prototyping nodeset for the showcase. | ||
|
|
||
|
|
@@ -60,19 +56,19 @@ To fill the demo dashboard machine page with the most content the variables mark | |
| | 0:HasProperty | Variable | 2:ProductInstanceUri | 0:String | 0:PropertyType | M, RO | | ||
| | 0:HasProperty | Variable | 2:Manufacturer | 0:LocalizedText | 0:PropertyType | M, RO | | ||
| | 0:HasProperty | Variable | 2:ManufacturerUri | 0:String | 0:PropertyType | O, RO | | ||
| | 0:HasProperty | Variable | 2:Model | 0:LocalizedText | 0:PropertyType | **M**, RO | | ||
| | 0:HasProperty | Variable | 2:ProductCode | 0:String | 0:PropertyType | **M**, RO | | ||
| | 0:HasProperty | Variable | **2:Model** | 0:LocalizedText | 0:PropertyType | **M**, RO | | ||
| | 0:HasProperty | Variable | **2:ProductCode** | 0:String | 0:PropertyType | **M**, RO | | ||
| | 0:HasProperty | Variable | 2:HardwareRevision | 0:String | 0:PropertyType | O, RO | | ||
| | 0:HasProperty | Variable | 2:SoftwareRevision | 0:String | 0:PropertyType | **M**, RO | | ||
| | 0:HasProperty | Variable | **2:SoftwareRevision** | 0:String | 0:PropertyType | **M**, RO | | ||
| | 0:HasProperty | Variable | 2:DeviceClass | 0:String | 0:PropertyType | O, RO | | ||
| | 0:HasProperty | Variable | 2:SerialNumber | 0:String | 0:PropertyType | M, RO | | ||
| | 0:HasProperty | Variable | YearOfConstruction | UInt16 | 0:PropertyType | **M**, RO | | ||
| | 0:HasProperty | Variable | **YearOfConstruction** | UInt16 | 0:PropertyType | **M**, RO | | ||
| | 0:HasProperty | Variable | MonthOfConstruction | Byte | 0:PropertyType | O, RO | | ||
| | 0:HasProperty | Variable | InitialOperationDate | DateTime | 0:PropertyType | O, RO | | ||
| | Applied from IMachineTagNameplateType | | | | | | | ||
| | 0:HasProperty | Variable | 2:AssetId | 0:String | 0:PropertyType | O, RW | | ||
| | 0:HasProperty | Variable | 2:ComponentName | 0:LocalizedText | 0:PropertyType | O, RW | | ||
| | 0:HasProperty | Variable | Location | 0:String | 0:PropertyType | **M**, RW | | ||
| | 0:HasProperty | Variable | **Location** | 0:String | 0:PropertyType | **M**, RW | | ||
|
|
||
| #### Special requirements for correct locating on the dashboard | ||
|
|
||
|
|
@@ -97,9 +93,15 @@ Fair shortnames are defined [here.](Fairs.md) | |
|
|
||
| - **Change the BrowseName and DisplayName of MachineTool** to `Company (short only alphanumeric)-Machine Name (alphanumeric)`, e.g. `ISW-TestServerMachine` or `ISW-SharpDriller5000. This helps a human to identify the machine in the aggregated server. **Do not use any other characters than {A…Z, a…z, 0…9} for the name**. Skipping this step prevents an automated integration to the dashboard. | ||
|
|
||
| ## Dashboard Status Overview | ||
| ## Value mapping between OPC UA companion specification and umati.app MachineTool | ||
|
|
||
| ### Machine Tool - Overview | ||
|
|
||
| For the status overview in the dashboard, the *State* of the *ProductionActiveProgramType* is stored and plotted over time. The status overview bar **does NOT relate to the stacklight** status! | ||
|  | ||
|
|
||
| ### Active Program Statusbar | ||
|
|
||
| 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! | ||
|
|
||
| Each status is assigned to a color, the color scheme is here (subject to change): | ||
|
|
||
|
|
@@ -112,4 +114,20 @@ Each status is assigned to a color, the color scheme is here (subject to change) | |
| | Aborted | 🔴 Red | | ||
| | Any other (unspecified) state | ⚫ Black | | ||
|
|
||
| A gap is left for periods of time in which no data was recorded (e.g. machine offline). An exemplary timeline is shown below. | ||
| A gap is left for periods of time in which no data was recorded (e.g. machine offline). An exemplary timeline is shown above. | ||
|
|
||
| ### Machine Tool - Identification | ||
|
|
||
|  | ||
|
|
||
| ### Machine Tool - Equipment - Tools | ||
|
|
||
|  | ||
|
|
||
| ### Machine Tool - Active Program | ||
|
|
||
|  | ||
|
|
||
| ### Machine Tool - Monitoring | ||
|
|
||
|  | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| # :construction: Adoption of this companion specification is planned | ||
|
|
||
| Stay tuned. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters