Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ResourceLocationType Child Relationship #82

Open
gerardmoloneyetpartners opened this issue Mar 7, 2023 · 2 comments
Open

ResourceLocationType Child Relationship #82

gerardmoloneyetpartners opened this issue Mar 7, 2023 · 2 comments

Comments

@gerardmoloneyetpartners
Copy link

gerardmoloneyetpartners commented Mar 7, 2023 •
edited
Loading

Currently, the B2MML-Common.xsd defines the ResourceLocationType as per below.
image

As there are certain objects (OperationalLocation, Equipment, PhysicalAsset) with the 'is made up of' relationship, I would like to see this updated to support this part of the ISA95 data models and suggest the update as a new line inserted at line 1642 as per below.
I believe this would then support the ability to have these objects nested and reported appropriately.
image
@gerardmoloneyetpartners
Copy link
Author

Hi @Dennis-Brandl, you were a bit quick for me to get this bug documented before the recent update.
Can we please get this also put into the V7.0.1 also.
I'd really like to have this ready for our next project implementation so that the following will allow nested locations
OpMaterialActualType for the StorageLocation
OpEquipmentActualType for the OperationalLocation
OpPhysicalAssetActualType for the PhysicalLocation

@Dennis-Brandl
Copy link
Contributor

Dennis-Brandl commented Mar 9, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Dennis-Brandl @gerardmoloneyetpartners