SyncRouting schema, example, validation rules, validation stylesheet

SyncRouting type: SyncRouting

The purpose of the SyncRouting is to communicate to a business application component or system the need to create a new Routing or to update an existing Routing structure. This BOD may be necessary to address the Make to Order, Assemble to Order, and Finished Goods business ordering scenarios in a Logistics to Manufacturing application integration scenario.

SyncRouting extends: BusinessObjectDocument
Structure:
Elements:
Name Type Description
DataArea SyncRoutingDataArea

Is where the information that the BOD message carries is provided, in this case SyncRouting. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (Routing).

SyncRoutingDataArea extends: DataArea
Structure:
Elements:
Name Type Description
Routing reference
Sync reference

SyncRouting Scenario Diagram

Sync schema

Sync type: Sync

The Sync verb is used when the owner of the data is passing or publishing that information or change in information to other software components. This is to be used when the receiver of the SyncBOD does not own the data. This verb is commonly used when mass changes are necessary or when a publish and subscribe mechanism is used in the integration architecture.The purposes of this verb include application integrity and ease of data entry for the business user by enabling a single point of input.

Sync extends: ConfirmableVerb
Structure:
Elements:
Name Type Description
SyncCriteria SyncExpressionCriteria

SyncExpressionCriteria
Structure:
Elements:
Name Type Description
SyncExpression
Attributes:
Name Type Usage Description
action required
expressionLanguage
Enumerations:
Add
Change
Delete
Replace

Routing schema

Routing type: Routing

Routing is the description of all of the resources, steps, and activities associated with a path or routing associated with a manufacturing or production process. Typically, a routing contains people, machines, tooling, operations, and steps.

Header type: RoutingHeader

AssignedOperationGroups type: OperationGroup

Information specifying a grouping of operations and their relationships.

RouteOperation type: RouteOperation

Information specifying the operations and there order for the specified routing.

PreviousOperation type: PreviousOperation

Information specifying the previous operation. This provides the immediate preceding operation of the current operation defined in RouteOperation. The RouteOperation of the operations of the potential first operations will not have an associated PreviousOperation, however all others must contain one.

GroupMember type: GroupMember

Information specifying the occurrence of the operations within an OperationGroup. At least one occurrence of the GroupMember component is required for each occurrence of the OperationGroup component. Except for the request BODs which use the verbs Get and GetList.

GroupMember
Structure:
Elements:
Name Type Description
OperationId OperationId

Is the identifier of a specific operation. Possible examples of use are in the Manufacturing Routing or the Maintenance Order. or WorkINProcessOperation.

Uniquly identifies an operation.

OperationName OperationName

Is the name of the operation.

Is the formal name of a Manufacturing Shop Floor Operation.

OperationSequence OperationSequenceCode

Identifies the operation sequence.

Is the sequence code associated with a operation.

UserArea reference

OperationGroup

In a manufacturing environment where a CNC Lathe or a Manual Lathe may be alternative operations used in the production of a finished good. In the example above the Manual Lathe OperationGroup Name would be Alternate OperationGroupType.

Structure:
Elements:
Name Type Description
GroupMember reference
OperationGroupName OperationName

Identifies a grouping of Operations together.

Is the formal name of a Manufacturing Shop Floor Operation.

OperationGroupType OperationGroupType

Identifies the grouping of operations.

Is the operational grouping type. Examples: Alternate – any of these may be used, Parallel – non-sequential – all must be done but order does not matter, Sequential – these items must be done one after the other and time is critical

UserArea reference

PreviousOperation extends: WIPOperationBase
Structure:
Elements:
Name Type Description
PlannedOverrunPercent Percent

Is the percentage of the planned number of items that can be produced. Typically, in a manufacturing environment stopping the manufacturing of an item at an exact number is difficult this allows the specification that an operator may overrun the planned number by a certain percentage.

Indicates the percentage.

Status reference
TimeInQueue Duration

Is the duration of time that a job may remain in the queue before being run.

UserArea reference

RouteOperation extends: WIPOperationBase
Structure:
Elements:
Name Type Description
ItemData reference
PreviousOperation reference
UserArea reference

Routing extends: Noun
Structure:
Elements:
Name Type Description
Header reference
Operation reference

RoutingHeader
Structure:
Elements:
Name Type Description
AssignedOperationGroups reference
Charges reference
Description Description

Description of the Routing.

Free-form text description of the Noun or Componenet in which the description occurs. The lang attribute indicates the language the description is in. Owner inidcates the user or entity that provided teh description..

Distribution reference

A distribution identifies how monetary amounts are distributed accross an organization.

DocumentId RouteIdType

Is the contains the unique routing document identifier information.

EffectivePeriod TimePeriod

Indicates the effectivity of the Routing Document.

Item reference

Is the Item Identifier in which the Routing is being used to create.

RouteOperation reference
Site reference
UserArea reference

Verb Common Files

Verb.xsd schema

AcknowledgableVerb extends: ConfirmableVerb
Structure:
Attributes:
Name Type Usage Description
acknowledge AcknowledgementType

AcknowledgementType restricts: xs:NMTOKEN
Enumerations:
Always
Never
OnChange

ConfirmableVerb extends: Verb
Structure:
Attributes:
Name Type Usage Description
confirm ConfirmType

ConfirmType restricts: xs:NMTOKEN
Enumerations:
Always
Never
OnChange

Expression restricts: xs:string

ExpressionCriteria
Structure:
Elements:
Name Type Description
SelectExpression Expression

Allows the 1-n number of selection expressions for the information to be returned.

Attributes:
Name Type Usage Description
expressionLanguage xs:string optional

RequestVerb extends: ConfirmableVerb
Structure:
Elements:
Name Type Description
ReturnCriteria

Allows the initator of the BOD to indicate the information (down to the field level) that is requested to be returned. The expressionLanguage indicates the expression language being used.

VerbBase.xsd schema

Verb type: Verb

Verb
Structure:

Noun Common Files