0007851: Offline file descriptor, file etc needs to be completely described (what is expected)

ID	Project	Category	View Status	Date Submitted	Last Update

0007851	Part 81: UAFX Connecting Devices and Information Model	Spec	public	2022-03-09 14:42	2022-04-12 14:21

Reporter	Georg Biehler	Assigned To	Bob Lattimer
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	no change required
Product Version	[Field eXchange (UAFX)] 1.00.00 RC1

Summary	0007851: Offline file descriptor, file etc needs to be completely described (what is expected)
Description	Part 83 is very limited in its description of the contents of this file My first concern is regarding what a controller specifies and how it changes after a program is loaded. I think Brian asked a similar question regarding workflow. My second concern is not related C2C MVS. I am wondering if this file should be associated with functional entities and not the AutomationComponent. When we start discussing devices that have multiple functional entities, it is not clear to me how you can create 1 offline descriptor file to represent all the possibilities and combinations of functionality. Note: discussion also included the identifier and version related to descriptor and also the content of the descriptor file. – also ProductInstanceURI is in the asset – should there be a relationship between them (maybe in some cases – device model) Requirement state that it is product descriptor file – which would need to be explain
Tags	No tags attached.

Paul Hunkar 2022-03-10 02:47 manager ~0016285	We allow multiple descriptor files. The content of file can be different ( device manufacture file vs System Integrator file vs end user Application file vs ...). In all case there needs to be some common information that allows an engineering tool to match the file to the application / AutomationComonent / Asset and for prescribed information a standard format for it (i.e. identification item or preconfigured PubSub configuration etc.) - some of this might be covered in Part 83 or might be fixed/standardized by the AML tool, but I would think it should also be documented - again maybe in a normative AML file, but the linkage from specs may need to be better explained

Bob Lattimer 2022-03-21 22:47 developer ~0016434	Part 83, in combination with the AutomationComponent Descriptors folder adequately describe all concerns in Issue Description. The attached work file includes a detailed description of the resolution. Mantis Issue 7851 resolution note.docx (15,545 bytes)

Bob Lattimer 2022-03-21 22:49 developer ~0016435	See details in the last note and attached file.

Paul Hunkar 2022-04-12 14:21 manager ~0016577	Agreed in call that no further updates are needed

Date Modified	Username	Field	Change
2022-03-09 14:42	Georg Biehler	New Issue
2022-03-10 02:47	Paul Hunkar	Note Added: 0016285
2022-03-10 02:48	Paul Hunkar	Relationship added	related to 0007850
2022-03-15 13:24	Paul Hunkar	Assigned To	=> Bob Lattimer
2022-03-15 13:24	Paul Hunkar	Status	new => assigned
2022-03-21 22:47	Bob Lattimer	Note Added: 0016434
2022-03-21 22:47	Bob Lattimer	File Added: Mantis Issue 7851 resolution note.docx
2022-03-21 22:49	Bob Lattimer	Status	assigned => resolved
2022-03-21 22:49	Bob Lattimer	Resolution	open => no change required
2022-03-21 22:49	Bob Lattimer	Note Added: 0016435
2022-04-12 14:21	Paul Hunkar	Status	resolved => closed
2022-04-12 14:21	Paul Hunkar	Note Added: 0016577