Open racheliurui opened 5 years ago
Table 145 – Operations definition relationship roles
Is WorkDefinitionID refers to "Work Master" in the table?
YES, Table 145 – Operations definition relationship roles WorkDefinitionID refers to "Work Master" in the table
Work Definition is an abstract type and Work Master is the first-order object. @CharlieG021163 mentioned it's better to directly refer to work master in the schema. Might consider a change to Erdi version.
Answer to Rachel Comment above. I agree. Change WorkDefinitionID to WorkMasterID. Change made. Updated Original Comment. Ready for final approval and submission to MESA.
I disagree with making OperationsMaterial Bill a first level object, since it is not reflected in Part 5.
Background OperationsDefinition.xsd
OperationsDefintionType and OperationsSegmentType use WorkDefinitionID, Per the updated 950002, the "corresponds to" association is from the Work Master object, not the Work Definition object. Align with updated 950002.
B2MML is using the an incorrect multiplicity for each relationship target names for OperationsDefinitionType and OperationsSegmentType. Align with updated 950002 Operations Definition Model.
Supporting Documents ISA-950002 JWG5 CDV01 version (2019 12) Clause 6.1.2 Operations definition, Table 145 – Operations definition relationship roles Clause 6.1.5 Operations segment, Table 151 – Operations segment relationship roles
Impacted Types and Solution B2MML-OperationsDefinition.xsd
1.2. For the following elements:"BillOfMaterialsID", "WorkMasterID", "BillOfResourcesID" CHANGE: minOccurs = "0"/>min TO: Occurs = "0" maxOccurs = "unbounded"/>
2.2. For the following elements: "BillOfMaterialsID", "WorkMasterID", "BillOfResourcesID" CHANGE: minOccurs = "0"/>min TO: Occurs = "0" maxOccurs = "unbounded"/>