umati / ua-for-machinetools Goto Github PK

Example: Machine does not habe job management, a MES system handles the running programs etc. Case in umati: job list is one element only
UC-29

Link issue that suggests that the job model presentation to JWG be included in the white paper
Link issue, which displays the instance view of jobs in different machines/production types.

UC-9
UC-39
UC-228

Test cases need to be defined and implemented which test for correct implementation of textual instructions.

Example: Identifier in PartUnloadPrognosisType as a copy of Identifier in PartType

Original UC-191

Add how to section to whitepaper

Original UC-135
Relates to #5

Additional background:
Please also note: BaseModelChangeEvent - Reasons for use and usage example

See OPC UA Part 3, 9.32 ModelChangeEvents

Coming soon: This event is triggered when the address space changes. In umati we use it in dynamic lists. This way a client can recognize that a list item has been added/deleted. If the list is always static in the server, the event never has to be sent. Changes are additionally visible at the NodeVersion (property of the node which is the entry point or "head" of the list) - the NodeVersion changes as well when the list changes. The OPC UA specification specifies that the NodeVersion must be present if the server sends ModelChangeEvents and should not be present if it does not. Whether a list changes at runtime can therefore be determined from the presence of the NodeVersion in the "list header".

Translated with www.DeepL.com/Translator (free version)

Implementation example on how to do the aggregation

Original UC-217
Relates to #5 and umati/MachineTool-Plugfest#2

-> include in a whitepaper how to use it

Especially consider the SmartLight from Balluf. A change of color during runtime is not expected by the clients because it is not explained/foreseen. If your client is able to handle this (e.g. the lamp asks for its color more often), you are welcome to do so, but a third party client will probably not have this feature integrated.

Relates to: #5

UC-131

This proposal was send it for consideration in the JWG.

2020-12-09 FlexibleGuideBushType_OPC UA CS for Machine Tools.pdf

After Feedback from Siemens, the alarm object of those two specifications are differing a bit.
Therefore, they suggest to align/harmonize both.

Subtasks can certainly be processed sensibly by Mr. Senftleben.

To record the discussion around application examples in a kind of whitepaper.

How to use the CS

Record best practice for use in common cases

two slides from JWG sessions and audio track written

Implementation notes

UC-118

Subtasks:
UC-119
UC-120
UC-121
UC-122
UC-123
UC-124
UC-130
UC-131
UC-135
UC-217

Blocked by:
UC-20
UC-24
UC-30
#3

Relates to:
UC-171

Check the Signals on the umati interface for compatibility with the ProdNet Attributes "ApplicationMode" "Status" and "OrderRelation".

either include these ProdNet Attributes as Enums (as suggested by Jonas Ruesch) or create a comprehensive mapping between the umati model and the ProdNet Attributes.

UC-19

„The open metering system OMS stands for a manufacturer- and utilities-independent standardization for Meter-Bus (M-Bus) based communication between utility meters (electricity, gas, water, district heat, heat cost allocators) and systems in the field of smart meters.“

https://de.wikipedia.org/wiki/Open_Metering_System

UC-99

Tranfer the documentation from Confluence into repo here.

Future nodesets should include node descriptions in the necessary fields.

Original UC-222

Similar to proposal by @veithammerstingl

With instance example. Graphic is available

UC-124

Siemens suggested to integrate the content of 40502 as a profile/facet into 40501.

There is NO definition as to how a prognosis is to be built, where the information comes from and how accurate it is

UC-30

Prognoses Presentation in JWG? Presentation in Whitepaper?
Or explanation for control manufacturers?

Wiki: Whitepaper 1.1.7. Events / Prognosis - How to use to be done
How it is build? → Implementierungsdetails der Maschinenhersteller/Steuerungshersteller
Where the information comes from?
PartLoad/UnloadPrognosis und ProductionJobEnd → Job
ManualActivity → Job
ProcessChangeOver, ToolLoad/Unload → Planung der Aufträge auf der Maschine
Maintenance → Handbuch und Kalender, Fehler
ToolChange → ToolLife, Fehlermeldungen
UtilityChange → Handbuch oder Benutzung/Sensorwerte, Kalendarische Werte
How accurate? - Implementation, for calender events, errors, better, for Job predictions, less accurate

In addition to the identifier, introduce a resource identifier (Betriebsmittelkennzeichen) (optional) (String)
Introduce as soon as components are included

Original UC-227

raw material or sheet sizes

Comment on ProductionJobType (Kilian Kehr - Messer Cutting)

For thermal cutting machines it is also important to have additional production-related meta-data being part of a job, which cannot be[TH1] [CD2] mapped onto a part. Most important example is the “plate size”. This is not a property that could be expressed on the part level. In contrast the plate thickness and steel types could be mapped onto a part, but it would be the same value for each part in a job, i.e. quite redundant. How should we deal with this specific issue?

Observation:
Check overlap/harmonization with Glass (@Kantiran91) and WoodWorking

Original: UC-132
Duplicate to UC-97
Relates to UC-22

As DI will be made a mandatory base model for Companion Specifications within VDMA by the OPC UA for Machinery Companion Specification some elements of DI will be relevant for MachineTool shortly, e.g. regarding the information we planned for the Identification area in the MachineTool model.

Therefor it might be useful to also check the element DeviceHealth of DI for use in MachineTool.

Original UC-205

Slide set after presentation on 16.07. in CWG → Take over relevant contents in Whitepaper

Relates to:
#5

Explain use of the NumberInList
include in accompanying document
was also presented at ISW-FTF

UC-119

Subtask of:
#5

Clarify how OPC UA Server variables could be changed (theory in the accompanying document): How to change values in the OPC UA Server: SDK, client, client rights etc.

Relates to:
#5

UC-130

See Mail from Randy Armstrong to @TonjaHeinemann and @GoetzGoerisch on Jan 28, 2021:

The NodeSetValidator expects this table format

this needs to be addressed in future spec versions.

Heidenhain: IdentificationType: maybe some more optional properties / variables?
e.g. like installation time (as UtcTime); inventory number; image or icon; contact information of a responsible person;...

Check current scope of OPC UA for Machinery and DI

Relates to umati/MachineTool-Plugfest#41 and UC-102
Original UC-142

The UA4MT documentation needs a comprehensive textual description how

• The StateMachines "ProductionPartStateMachine", "ProductionJobStateMachine" and "ProductionProgramstateMachine"
• the TransitionEvents for those StateMachines
• the InterruptionConditions

are intended to be used in different scenarios.

Original UC-171
Relates to #5