-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
ADD TestResult element to OpXXXActualType in OperationsPerformanceTypes.xsd to align with updated 950002 #16
Labels
Milestone
Comments
racheliurui
added
ERDi
Issues that need to be fixed in ERDi version
MESA
Issues that need to be fixed in MISA Version
labels
Aug 21, 2019
|
Pending discussion and linked issues,
|
racheliurui
changed the title
TestResultType: Align with ISA-950002
TestResultType attribute Align with ISA-950002
Aug 23, 2019
CharlieG021163
changed the title
TestResultType attribute Align with ISA-950002
Change TestResultType in Common.xsd and/or Approve Pull Request for OperationsTest.xsd align with updated 950002
Jan 23, 2020
CharlieG021163
changed the title
Change TestResultType in Common.xsd and/or Approve Pull Request for OperationsTest.xsd align with updated 950002
ADD TestResult to OpXXXActualType in OperationsPerformanceTypes.xsd to align with updated 950002
Mar 5, 2020
CharlieG021163
changed the title
ADD TestResult to OpXXXActualType in OperationsPerformanceTypes.xsd to align with updated 950002
ADD TestResult element to OpXXXActualType in OperationsPerformanceTypes.xsd to align with updated 950002
Mar 5, 2020
racheliurui
referenced
this issue
Mar 9, 2020
ERDi, MESA: complexType name = "OpPersonnelActualType", ADD element name = "TestResultType", CHANGE element name = "PersonnelActual" to "PersonnelActualChild"; DELETE = element name = "TestSpecification". ERDi, MESA: complexType name = "OpMaterialActualType", ADD element name = "TestResultType"; CHANGE element name = "MaterialActual" to "MaterialActualChild"; DELETE = element name = "TestSpecification". ERDi, MESA: complexType name = "OpEquipmentActualType", ADD element name = "TestResultType", CHANGE element name = "EquipmentActual" to "EquipmentActualChild" ERDi, MESA: complexType name = "OpPhysicalAssetActualType", ADD element name = "TestResultType"; ADD element name = "PhysicalAssetActualProperty"; CHANGE element name = "PhysicalAssetActual" to "PhysicalAssetActualChild"; DELETE = element name = "TestSpecification". ERDi, MESA: complexType name = OpPersonnelActualPropertyType", ADD element name = "PersonnelActualPropertyChild"; ADD element name = "PersonnelClassPropertyID"; ADD element name = "PersonPropertyID"; DELETE element name = "RequiredByRequestedSegmentResponse" ERDi, MESA: complexType name = OpMaterialActualPropertyType", ADD element name = "MaterialActualPropertyChild"; ADD element name = "MaterialLotPropertyID"; ADD element name = "MaterialDefinitionPropertyID"; ADD element name = "MaterialClassPropertyID"; DELETE element name = "RequiredByRequestedSegmentResponse" ERDi, MESA: complexType name = OpEquipmentActualPropertyType", ADD element name = "EquipmentActualPropertyChild"; ADD element name = "EquipmentClassPropertyID"; ADD element name = "EquipmentPropertyID"; DELETE element name = "RequiredByRequestedSegmentResponse" ERDi, MESA: complexType name = OpPhysicalAssetActualPropertyType", ADD element name = "PhysicalAssetActualPropertyChild"; ADD element name = "PhysicalAssetClassPropertyID"; ADD element name = "PhysicalAssetPropertyID"; DELETE element name = "RequiredByRequestedSegmentResponse"
CharlieG021163
modified the milestones:
AgreedByWorkingGroup,
AuthorisedForMESASubmission
Mar 17, 2020
I agree with the change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
ERDi, MESA: Related to #7, #101
Align TestResult element with updated 950002, Operations Test Model where the Test Result object has an association relationships with the resource actual objects.
Under issue Add OperationsTest.xsd to align with updated 950002 #101, the new OperationsTest.xsd schema is added to align with 950002 by including TestSpecificationType and TestResultType together which allows 1st order transactions for both types.
B2MML 7.0 beta only created a B2MML-TestSpecification.xsd schema and created the complex types of "TestResultType" and TestPropertyMeasurementType in the Common Schema.
HOWEVER, B2MML 7.0 still has the TestResult element in each instance resource property per the old version of ISA-95 resource models and B2MML 6.0. The old resource model had a composite relationship from the each resource property of the resource master data objects which did not allow Test Result attribute to be exchanged and queried as a 1st class object. This design has the logic issue where a test result is related to testing of a resource actual to a master data resource's test specification. The old resource models had a composite relationship which did not allow Test Result to be exchanged and queried as a 1st class object.
Supporting Documents
Clause 6.3.6 Personnel actual, Table 208 – Personnel actual relationship roles
Clause 6.3.8 Equipment actual, Table 212 – Equipment actual relationship roles
Clause 6.3.10 Physical asset actual, Table 216 – Physical asset actual relationship roles
Clause 6.3.12 Material actual, Table 220 – Material actual relationship roles
Impacted Type and Solutions
_OperationsPerformanceTypes.xsd,
ADD: "TestResult" type = "TestResultType" to align with updated Part 2 Operations Test Model's relationships.
The text was updated successfully, but these errors were encountered: