Delete elements, OperationsRequestID from JobOrderType in WorkSchedule.xsd to align with updated 950004

[CharlieG021163]

Background
To align with Updated Work Schedule Model, Job Order object does not have cross model relationships with Operations Request. The Job Order has reference to the Operations Request through the Segment Requirement.

Solution
complexType name = "JobOrderType"
DELETE: <xsd:element name = "OperationsRequestID" type = "IdentifierType" minOccurs = "0" maxOccurs = "unbounded"/>

Supporting Document
950004 JWG5 CDV01 version (2019 12)
Clause 7.6 Job Order, Table 58 – Job order relationship roles

Impacted Types
B2MML WorkSchedule.xsd: "JobOrderType"

[gerardmoloneyetpartners]

Supporting Document should be Table 58 as per below...
950004, Clause 7.6 Job Order, Table 58 – Job order relationship roles

[gerardmoloneyetpartners]

Agreed with solution.

I would like to rehash the 'RequiredbyResquestedSegmentResponse" (listed in WS, WD, WE) and the SegmentResponse (listed in the OS).

Question: is the 'SegmentResponse" in the OS a complete set of empty SegmentResponse that the OS is asking to be used in the reporting (e.g. future message of WS, WD, WE and PT?)
Are all of the "RequiredByRequestedSegmentResponse" elements in the WS, WD, WE supposed to list the "SegmentResponseID" from the OS? or are they supposed to list the 'WorkRequestID"? Or a just a Yes/No reference?

[CharlieG021163]

@gerardmoloneyetpartners
We will discuss in next session the accepted with modification comment on Requested Segment Response approach. It is Table 58 in updated JWG5 IEC version based addition of table as part of approved comments at ISA95 October 2019 Meeting. Final approved ISA version of 2018 used Table 57.

[CharlieG021163]

@gerardmoloneyetpartners
Updated original comment to Table 58. Issue is that ALL the issue will need to updated to JWG5 Voting Draft 1 version of 950004. Will discuss this as convention before running through.

[gerardmoloneyetpartners]

Agreed to fix.

OpsSchedule will be including both options for segment response to provide either a yes/no (Required, Optional, other) or to provide the actual template of elements.
all other references in other schemas of 'RequiredByRequestedSegmentResponse' are only flags (Required, Optional, Other).

[Dennis-Brandl]

Agreed