this ontology provides English language descriptions for the OWL classes used in the
Swedish Defence model
Change history:
Last editor: $Author: mikeward $
Last edit date: $Date: 2017-03-15 19:12:30 $
Contributors:
Mike Ward, Eurostep
Peter Bergström, Eurostep
Changes:
[2015-01-09] Peter Bergström, Eurostep: Stripped all older reference data classes.
Contains now only reference data for DEX 1-4.
[2015-06-26] Peter Bergström, Eurostep: Added reference data for DEX 5-7, updated
for DEX 1-4.
[2016-10-31] Mike Ward, Eurostep: added xmlns:plcs-psm-v1_1, xmlns:plcs-rdl-v1_1,
and xmlns:plcs-rdl-dmou-v1_1
[2016-11-20] Rob Bodington, Eurostep: Changed owl:imports to import http://docs.oasis-open.org/plcs/ns/plcslib/v1.1/data/contexts/OASIS/refdata/plcs-rdl-dmou
[2019-10-09] Peter Bergström, Eurostep: Changed from deprecated superclass http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Document_version_identification_code
to http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Version_identification_code.
[2015-01-14] Peter Bergström, Eurostep: class created
[2019-10-09] Peter Bergström, Eurostep: Changed from deprecated superclass http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Document_version_identification_code
to http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Version_identification_code.
[2015-01-12] Peter Bergström, Eurostep: class created
document assignment representing the assignment of a publication that is not registered or managed by
the Swedish Defence, and thus "external" to the Swedish Defence
NOTE 1:
to be used only if the fault cause is not defined as a fault mode definition in itself, in which case the relationship "causedBy" is used instead
[2020-12-08] ike Ward, Eurostep renamed from "fault effect identifier" to "fault effect
definition identifier" and moved under external item identifier
[2015-06-12] Peter Bergström, Eurostep: initial definition
fault effect definition classified by what part of the product it affects, e.g. local effect or end item
effect
Notes:
NOTE 1:
Used instead of creating a relationship to the relevant http://plcs.fmv.se/rd/SwedishDefence-rdl-en#functionalStructureElement
Examples:
EXAMPLE 1:
a punctured tire has a "local" effect on the tire, which needs repair, but also a
"next higher" effect on the wheel, which does not function properly, and also on the
bike ("end item") because the bike can't be used until the fault is corrected
[2019-10-09] Peter Bergström, Eurostep: changed superclass from http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateDefinition
to http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#State_of_functional_breakdown,
in line with physicalStructureStatus.
[2019-08-06] Mike Ward, Eurostep Limited: Class creation
[2019-10-09] Peter Bergström, Eurostep: Changed from deprecated superclass http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Document_version_identification_code
to http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Version_identification_code.
[2015-01-08] Peter Bergström, Eurostep: class created
descriptor representing the text (content) of the information element
Notes:
NOTE 1:
This may be a shorter description of the contents of an information element, or the
entire content (in which case there is no accompanying file or document).
Information defining item of supply individuals that share the same or similar design.
Notes:
NOTE 1:
The information is generated during the concept and design phases. It controls the
configuration and properties of each item of supply individual during the production phase, as well as supports the management of the item of supply individuals during the operation and maintenance phase.
Examples:
EXAMPLE 1:
All defining information for a radio equipment that is part of several weapons systems.
EXAMPLE 2:
All defining information for a type of battle tank.
EXAMPLE 3:
All defining information for a type of valve.
physical item that the Swedish Armed Forces is in need of and which must cover operational
and reserve needs, and which is therefore stored, distributed and monitored regarding
operational events and costs.
Notes:
NOTE 1:
An individual item of supply can be the top supply item as well as a contained component.
An individual item of supply can be identified by e.g. serial number or registration
number (e.g. for vehicles).
Examples:
EXAMPLE 1:
one of the boxes with machine gun ammunition on the shelf in storage.
EXAMPLE 2:
the car with registration number ABC123.
EXAMPLE 3:
the physical lavatory cistern valve that is leaking in the bathroom.
descriptor representing a Logistics Support Analysis (LSA) Control Number
Notes:
NOTE 1:
The LCN may represent either a functional or hardware generation breakdown/disassembly
sequence of system/equipment hardware including support equipment, training equipment,
and installation (connecting) hardware.
physical structure element representing a physical element that is designed to be replaced quickly typically
to undergo repair and overhaul actions in other support locations.
[2021-05-17] Mike Ward, Eurostep: moved directly under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#MeterCategory
instead of under
http://plcs.fmv.se/rd/SwedishDefence-rdl-en#meterCategory_timeCounter
[2020-04-15] Mike Ward, Eurostep: initial definition (re-creation)
[2021-05-17] Mike Ward, Eurostep: moved directly under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#MeterCategory
instead of under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#meterCategory_temperatureMeter
[2020-04-15] Mike Ward, Eurostep: initial definition (re-creation)
[2021-05-17] Mike Ward, Eurostep: moved directly under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#MeterCategory
instead of under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#meterCategory_derivativeMeter
[2020-04-15] Mike Ward, Eurostep: initial definition (re-creation)
[2021-05-17] Mike Ward, Eurostep: moved directly under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#MeterCategory
instead of under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#meterCategory_volumeMeter
[2020-04-15] Mike Ward, Eurostep: initial definition (re-creation)
[2021-05-17] Mike Ward, Eurostep: moved directly under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#MeterCategory
instead of under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#meterCategory_temperatureMeter
[2020-04-15] Mike Ward, Eurostep: initial definition (re-creation)
[2021-05-17] Mike Ward, Eurostep: moved directly under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#MeterCategory
instead of under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#meterCategory_quantityCounter
[2020-04-15] Mike Ward, Eurostep: initial definition (re-creation)
[2021-05-17] Mike Ward, Eurostep: moved directly under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#MeterCategory
instead of under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#meterCategory_quantityCounter
[2020-04-15] Mike Ward, Eurostep: initial definition (re-creation)
[2021-05-17] Mike Ward, Eurostep: moved directly under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#MeterCategory
instead of under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#meterCategory_quantityCounter
[2020-04-15] Mike Ward, Eurostep: initial definition (re-creation)
[2021-05-17] Mike Ward, Eurostep: moved directly under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#MeterCategory
instead of under
http://plcs.fmv.se/rd/SwedishDefence-rdl-en#meterCategory_timeCounter
[2020-04-15] Mike Ward, Eurostep: initial definition (re-creation)
[2021-05-17] Mike Ward, Eurostep: moved directly under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#MeterCategory
instead of under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#meterCategory_derivativeMeter
[2020-04-15] Mike Ward, Eurostep: initial definition (re-creation)
[2021-05-17] Mike Ward, Eurostep: moved directly under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#MeterCategory
instead of under http://plcs.fmv.se/rd/SwedishDefence-rdl-en#meterCategory_derivativeMeter
[2020-04-15] Mike Ward, Eurostep: initial definition (re-creation)
Class label:
physical structure element classified by mounting rule
Class alternative label: mounting rule
Description:
[physical structure element http://plcs.fmv.se/rd/SwedishDefence-rdl-en#physicalStructureElement
that is classified according to mounting rules
Notes:
NOTE 1:
ABSTRACT RD class that is not used for classification purposes.
Examples:
EXAMPLE 1:
the physical structure element "left aircraft wing" do not have a corresponding item of supply or part definition, that is ever (in the operational phase) supposed to be mounted on the aircraft.
The wing is never unmounted and mounted as one object
EXAMPLE 1:
the physical structure element "left aircraft engine" provides functionality for individual
tracking and follow-up of the physical individual that is mounted in this position,
and therefore the physical individual mounted here must be an identified individual,
e.g. by serial number
EXAMPLE 1:
the physical structure element "left aircraft wing" do not have a corresponding item of supply or part definition, that is ever (in the operational phase) supposed to be mounted on the aircraft.
The wing is never unmounted and mounted as one object
EXAMPLE 1:
the physical structure element "fuel tank meter" does not provide functionality for
individual tracking and follow-up of the physical individual that is mounted in this
position, and therefore the physical individual mounted here must not be an identified
individual with a requirement for individual follow up
[2019-10-09] Peter Bergström, Eurostep: Changed from deprecated superclass http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Physical_element_version_identification_code
to http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Version_identification_code.
[2019-10-09] Peter Bergström, Eurostep: Changed from deprecated superclass http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Physical_breakdown_version_identification_code
to http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Version_identification_code.
Selection of components for an item of supply definition, assembled in order to perform
a required function.
Notes:
NOTE 1:
Each node in those structures (the physical and functional elements) may be realized
by one or (on a type level) a choice of items of supply. For a real, individual product,
there may be no choices left in the structure at a given point in time (the individual
configuration). The nodes (elements) may also refer to task methods, thereby providing
a structure of task methods.
Class label:
part classification code classified by reference designator code
Class alternative label: REFKOD reference designator code
Description:
part classification code that represents a code that distinguishes different types of reference designations
(identifier of part that has become an item of supply)
Notes:
NOTE 1:
ABSTRACT RD class that is not used for classification purposes.
NOTE 1:
requirement area is indirectly related to requirement category but may be worded more freely, since it may be used as a heading in generated document.
Hierarchical description of requirements from a general to a more specific level.
Notes:
NOTE 1:
A requirement can be broken down into a number of more specific requirements. One
specific requirement may constitute a subset of more than one more general requirement.
[2019-10-09] Peter Bergström, Eurostep: changed superclass from http://plcs.fmv.se/rd/SwedishDefence-rdl-en#requirementBreakdown
to http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#State_of_breakdown
in line with physicalStructureStatus.
[2019-09-17] Peter Bergström, Eurostep: initial definition
Class label:
requirement breakdown classified by requirement breakdown type
Class alternative label: requirement breakdown type
Description:
requirement breakdown that represents the further categorization of a requirement breakdown in accordance
with the character of that requirement breakdown
Notes:
NOTE 1:
ABSTRACT RD class that is not used for classification purposes.
[2019-11-18] Mike Ward, Eurostep: URI in rdfs:comment corrected
[2019-09-25] Mike Ward, Eurostep: initial renamed from requirementBreakdownType_systemRequirementBreakdown
to requirementBreakdownType_technicalRequirementBreakdown
[2017-08-01] Mike Ward, Eurostep: initial definition
Textual description, including a heading, which clarifies the scope of a requirement
area and thus also the understanding of the requirements set within the area.
[2019-10-09] Peter Bergström, Eurostep: changed superclass from http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Requirement
to http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#State_of_requirement
in line with other state definitions.
[2017-08-01] Mike Ward, Eurostep: initial definition
NOTE 1:
This version may be the same through multiple releases of a software product where
the version specified in softwareVersionId is much more specific and will change for
each software release.
NOTE 1:
Product family is not used to identify that a product is part of a suite, but is instead
used when a set of products that are all related may be installed on multiple different
devices.
Examples:
EXAMPLE 1:
An Enterprise backup system may consist of a backup server, multiple different backup
systems that support mail servers, databases and ERP systems as well as individual
software items that backup client devices. In this case all software titles that are
part of the backup system would have the same productFamily name so they can be grouped
together in reporting systems.
[2019-10-09] Peter Bergström, Eurostep: comment updated from ISO-IEC 19770-2
[2019-10-09] Peter Bergström, Eurostep: Changed from deprecated superclass http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Part_version_identification_code
to http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Version_identification_code.
[2015-03-31] Peter Bergström, Eurostep: class created
[2015-01-08] Peter Bergström, Eurostep: updated definition
[2014-12-12] Peter Bergström, Eurostep: changed ID from Msg_SwedishDefence_PhysicalMaintenanceStructure_v1.0
to SwedishDefence_DEX_PhysicalMaintenanceStructure_v1.0
[2014-12-07] Peter Bergström, Eurostep: initial definition
NOTE 1:
the concluding task method is often not counted as a part of the corrective task method,
because it does not correct the fault, but it may be necessary in order to reset the
product to its normal state
NOTE 1:
a preparatory task method is often not included in the corrective task method, because
it does not correct the fault. It sets the product in the state it needs to be in
(e.g. "motor in bench") before the corrective task method can be started. It is a
preparatory task method, and a prerequisite for the referencing task method.
[2019-11-18] Mike Ward, Eurostep: URI in rdfs:comment corrected
[2019-10-09] Peter Bergström, Eurostep: Changed from deprecated superclass http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Task_method_version_identification_code
to http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Activity_method_identification_code
and http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Version_identification_code.
Theoretical method used for verification and validation using analytical or mathematical
models to secure that a requirement is fulfilled.
Notes:
NOTE 1:
Analysis is used for validation by collecting results from the verification reviews,
inspections, simulations, and tests. The analysis object is to a greater or lesser
degree a model of the real object. Analysis is also used to a great extent in early
development phases.
NOTE 2:
Analysis is used when verification and validation in real environments is not possible
or cost-effective to carry through, provided that the method can be used to ensure
that the requirement is fulfilled. Advantages with the method: Can be used for all
system levels, cost-effective, time-effective. Disadvantages: Results are limited,
not useful for dynamically complex processes.
Analytical method which means comparison and evaluation of technical data and experience-based
information with a function or property of an existing object that the Swedish Material
Defence Administration or industry are aware of, in order to, completely or partly,
secure analytically that a reuirement is fullfilled.
Notes:
NOTE 1:
An analysis should ensure that the design and usage environment for the two objects
corresponds well enough so that the previous verification and validation results can
be considered applicable before this method is employed.
NOTE 2:
The comparison method can for instance be used to avoid costly testing of an integration
product that has passed verification and validation previously, and that now is part
of the object being verified and validated. Advantages: Cost-efficient, time saving.
Disadvantages: Can only be used when two equivalent objects exists.
Presentation in order to prove required functionality.
Notes:
NOTE 1:
Demonstration are very common in the relationship between supplier and customer, and
is used e.g. to build confidence with the customer or user of the system to be delivered.
NOTE 2:
Demonstration can be used to show that the object responds as expected to stimuli.
NOTE 3:
The demonstration method may also be applicable for requirements that are expressed
statistically, e.g. Mean Time To Repair (MTTR).
Theoretical method which means review of documents, drawings, certificates, and attestations
that the supplier presented in order to theoretically prove that a requirement is
fulfilled.
Empirical method used to determine the properties of an object by subjecting it to
an environment that mimics the real environment.
Notes:
NOTE 1:
Simulation is used when verification and validation in the actual environment is not
feasible or cost-effective, provided that the method can be used to ensure the requirement
is fulfilled. Advantages with the method: Substitute for expensive and time-consuming
testing; Substitute for testing that would result in risk for human or material damages;
Can be performed as a quantity testing and provides adequate statistical information.
Disadvantages: Simulators may become expensive, both to procure and to operate; It
must always be considered how well the simulation mimics the real conditions.
Testing is carried out under controlled circumstances in order to empirically verify
or validate the required function or integration with regards to capability, availability,
environment, etc.
Notes:
NOTE 1:
Advantages: High significance in results; Can be performed on different levels;Can
be combined with training; Additional values can be identified. Disadvantages: Resource
demanding; Time consuming; Dangerous parts of the area may not be possible to test.
NOTE 2:
The testing method requires often specific resources and tools to be used for verification
and validation.
NOTE 1:
All such relationships defines thereby valid materiel in this position in the product
structure.
NOTE 2:
The validity may be limited to what is fitted in other positions (see may not be combined).
NOTE 3:
The validity of materiel is controlled by refering to the materiel definition (item
of supply or part definition), or to specific item of supply individuals.
[2019-10-09] Peter Bergström, Eurostep: Removed the reference to http://plcs.fmv.se/rd/SwedishDefence-rdl-en#PhysicalStructure
in the comment, since it does not exist.
Theoretical method used for verification and validation using analytical or mathematical
models to secure that a requirement is fulfilled.
Notes:
NOTE 1:
Analysis is used for validation by collecting results from the verification reviews,
inspections, simulations, and tests. The analysis object is to a greater or lesser
degree a model of the real object. Analysis is also used to a great extent in early
development phases.
NOTE 2:
Analysis is used when verification and validation in real environments is not possible
or cost-effective to carry through, provided that the method can be used to ensure
that the requirement is fulfilled. Advantages with the method: Can be used for all
system levels, cost-effective, time-effective. Disadvantages: Results are limited,
not useful for dynamically complex processes.
Analytical method which means comparison and evaluation of technical data and experience-based
information with a function or property of an existing object that the Swedish Material
Defence Administration or industry are aware of, in order to, completely or partly,
secure analytically that a reuirement is fullfilled.
Notes:
NOTE 1:
An analysis should ensure that the design and usage environment for the two objects
corresponds well enough so that the previous verification and validation results can
be considered applicable before this method is employed.
NOTE 2:
The comparison method can for instance be used to avoid costly testing of an integration
product that has passed verification and validation previously, and that now is part
of the object being verified and validated. Advantages: Cost-efficient, time saving.
Disadvantages: Can only be used when two equivalent objects exists.
Presentation in order to prove required functionality.
Notes:
NOTE 1:
Demonstration are very common in the relationship between supplier and customer, and
is used e.g. to build confidence with the customer or user of the system to be delivered.
NOTE 2:
Demonstration can be used to show that the object responds as expected to stimuli.
NOTE 3:
The demonstration method may also be applicable for requirements that are expressed
statistically, e.g. Mean Time To Repair (MTTR).
Empirical verification method which means ocular inspection of the design or visibel
function in the object in order to verify that a requirement is fulfilled.
Notes:
NOTE 1:
Appropriate for verification of e.g.weight, colour, measures and labelling.
Theoretical method which means review of documents, drawings, certificates, and attestations
that the supplier presented in order to theoretically prove that a requirement is
fulfilled.
Empirical method used to determine the properties of an object by subjecting it to
an environment that mimics the real environment.
Notes:
NOTE 1:
Simulation is used when verification and validation in the actual environment is not
feasible or cost-effective, provided that the method can be used to ensure the requirement
is fulfilled. Advantages with the method: Substitute for expensive and time-consuming
testing; Substitute for testing that would result in risk for human or material damages;
Can be performed as a quantity testing and provides adequate statistical information.
Disadvantages: Simulators may become expensive, both to procure and to operate; It
must always be considered how well the simulation mimics the real conditions.
Testing is carried out under controlled circumstances in order to empirically verify
or validate the required function or integration with regards to capability, availability,
environment, etc.
Notes:
NOTE 1:
Advantages: High significance in results; Can be performed on different levels;Can
be combined with training; Additional values can be identified. Disadvantages: Resource
demanding; Time consuming; Dangerous parts of the area may not be possible to test.
NOTE 2:
The testing method requires often specific resources and tools to be used for verification
and validation.
[2019-10-09] Peter Bergström, Eurostep: Reference to PhysicalStructureMeterElement
changed to a reference to a physicalStructureElement. definition edited.
[2016-08-31] Mike Ward, Eurostep: name changed to VirtualMeter and comment changed
[2015-05-22] Peter Bergström, Eurostep: initial definition
Named Individual label:
aggregated mean time between failure
Description:
instance of a context dependent property definition that represents an indication of how often an ItemDefinition may break in the current
location, regardless of fault mode, that is used for simulation and planning
instance of context dependent unit representing one of the twelve named periods into which a year is divided or a period
of time between the same dates in successive calendar months or a period of 28 days
instance of a context dependent property definition representing the number of hours required of the specific competence type in order
to perform the task
instance of a context dependent property definition that represents the desired (expected) values of the Operational Properties that
shall be followed-up for a Physical Element (pos), given the Operating Mode
instance of a context dependent property definition representing the number of times a task method should be repeated (in context of
another task method)