Template: SwedishDefence:PerformedMaintenance

This section specifies the template PerformedMaintenance.

The specification comprises a SysML Block that represents the template and an associated Parametric Diagram that defines the templates and PLCS PSMTemplate objects instantiated by the PerformedMaintenance template.

The specification comprises the following sections:

NOTE    An explanation of a template and its specification is provided in the Template overview
The PerformedMaintenance template describes how to represent that a maintenance has started but not necessarily finished.

No templates have been explicitly defined as being related to the PerformedMaintenance template.

NOTE    The PerformedMaintenance template may make reference to other templates as part of the Parametric Diagram. These are not listed here.

Figure 1 shows the SysML Block that represents the template. The Block is an abstraction representing a pattern of templates and PLCS PSMTemplate objects.

The properties, i.e. the SysML Block Part, Reference and Value properties, of the template's SysML Block are described in the Template Properties section.

The output ports shown on the template's SysML Block are described in the template output ports section.

The SysML Parametric diagrams for the template Block are shown in template parametric diagram section.

Figure 1 -  Template block definition diagram for PerformedMaintenance

The following SysML Part, Reference, and Value properties are defined for this template:

References:
itemConsumed [1..*] (Template: SwedishDefence:ItemQuantity)
Relationship to resources that are consumed in the maintenance.
itemInput [0..*] (Template: SwedishDefence:ItemDefinition)
Relationship to item definitions which are the input e.g. design of the spare parts for executing the maintenance.
itemOutput [0..*] (Template: SwedishDefence:ItemDefinition)
Relationship to item definitions which are the output e.g. designed of the parts are replaced when executing the maintenance.
individualInput [1] (Template: SwedishDefence:ItemIndividual)
Relationship to individual item of supplies which are the input e.g. spare parts for executing the maintenance.
individualOutput [1] (Template: SwedishDefence:ItemIndividual)
Resulting Individual.
methodUsed [0..1] (Template: SwedishDefence:TaskMethod)
Relationship to a task method that is utilized for guiding the execution of the maintenance.
workOrder [1] (Template: SwedishDefence:MaintenanceOrder)
Relationship to a maintenance order that requests for the performed maintenance.
personReporting [0..1] (Block: Ap239Ap233Psm:PersonInOrganization)
The person who executed the performed maintenance.
facilitiesUsed [0..*] (Template: SwedishDefence:FacilityDefinition)
Relationship to facilities that are utilized for executing the maintenance.
competenceUsed [0..*] (Template: SwedishDefence:Competence)
Relationship to competences that are required for executing the maintenance.
Parts:
performedMaintenanceId [1] (Template: OASIS:Identification)
Identifier of the performed maintenance.
performedMaintenanceName [0..1] (Template: OASIS:Name)
Maintenance carried out.
Values:
startTime [0..1] (Block: Ap239Ap233Psm:DateTimeString)
The time when the maintenance starts.

The following constraint, normally a uniqueness constraint, is applicable when instantiating the DateTimeString:

rule.Ap239Ap233Psm.ExternalOwlClass.ur1
Constraint: XSDDATETIME
Specification: (OCL2.0)
self.matches('[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z')
endTime [0..1] (Block: Ap239Ap233Psm:DateTimeString)
The time when the maintenance ends.

The following constraint, normally a uniqueness constraint, is applicable when instantiating the DateTimeString:

rule.Ap239Ap233Psm.ExternalOwlClass.ur1
Constraint: XSDDATETIME
Specification: (OCL2.0)
self.matches('[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z')

The following output ports are defined for this template:

PSMactivityActual (Block: Ap239Ap233Psm:ActivityActual)
Enables the Block: Ap239Ap233Psm:ActivityActual instantiated by this template to be referenced when the template is used.
OASISworkDone (Template: OASIS:WorkDone)
Enables the Template: OASIS:WorkDone instantiated by this template to be referenced when the template is used.

There are no constraints defined for this template.

This section describes the template's Parametric Diagram. The diagram details the pattern of templates and PLCS PSMTemplate objects that are required to represent the template PerformedMaintenance.

The public properties, i.e. those visible in the template's SysML block (See Figure 1) are shown on the left of a Parametric Diagram.

NOTE    Restrictions on the reference data to be set on the public properties is defined in the Template Properties section.

The output ports are shown on the right of a Parametric Diagram.

PLCS PSM objects are shaded khaki and Templates are shaded light green in a Parametric Diagram.

Figure 2 -  PerformedMaintenance

The following blocks are instantiated by this template and bound to private parts of the template as shown in the Parametric Diagram section:

Private Part Property:maintenanceDone [1] (Template: OASIS:WorkDone)
Private Part Property:inputPartVersionOrResourceItem [1] ( Constraint Block: SwedishDefence:PerformedMaintenance:PartVersionOrResourceIem)
Private Part Property:outputPartVersionOrResourceItem [1] ( Constraint Block: SwedishDefence:PerformedMaintenance:PartVersionOrResourceIem)
Private Part Property:inputIndividualsAndItems [1] ( Constraint Block: SwedishDefence:PerformedMaintenance:IndividualAndItem)
Private Part Property:outputIndividualsAndItems [1] ( Constraint Block: SwedishDefence:PerformedMaintenance:IndividualAndItem)
Private Part Property:requiredResources [0..*] (Block: Ap239Ap233Psm:RequiredResource)
Private Part Property:combine [1] ( Constraint Block: SwedishDefence:PerformedMaintenance:combineRequiredResources)
Private Part Property:ResourceAsgn [0..*] (Block: Ap239Ap233Psm:RequiredResourceAssignment)

There are no instances that have been instantiated in this template.

Figure 3 shows the constraint blocks that have been created in the template.

Constraint Blocks are typically used to combine blocks into a collection that can then be bound to a property. For example, combining a set of identifications that can then be bound to property of type Identification.

Constraints diagram
Figure 3 -  Constraint block diagram for PerformedMaintenance

The following constraint blocks have been created:

Constraint: combineRequiredResources
Specification: (OCL2.0)
combined = input1->union(input2)
Constraint: IndividualAndItem
Specification: (OCL2.0)
individualAndItem=item->union(Set{realizedPart})
N/A
Constraint: PartVersionOrResourceIem
Specification: (OCL2.0)
partVersionOrResourceItem = partVersion->select(pv| not pv.oclIsUndefined ())->union(resourceItem->select(ri| not ri.oclIsUndefined ()))

No example data sets have been provided for this Template.

Issue reporting