MOAFDITO
type: Ontology
contributor: Bige Tuncer
creator: Arghavan Akbarieh
description: The MOAF-DiTO ontology is Wip. It provides a semantic model for representing manufacturing operations in printed circuit board (PCB) production. The ontology captures work orders, operation executions, material requirements, machines, departments, personnel roles, and quality tests. MOAF-DiTO is designed to support monitoring, analysis, and decision-making on the operational floor with an outlook for reporting. It enables consistent representation of routing structures, operational sequences, material consumption, and test outcomes, allowing traceability of products and resources throughout the manufacturing process. The ontology is intended to serve as a semantic backbone for knowledge graphs, AI and digital twin applications. It is extensible by design and aligns with open manufacturing and Industry 5.0 principles.
license: http://creativecommons.org/licenses/by/4.0/
label: MOAF-DiT project
version info: 1.0

adjacent To
type: ObjectProperty
type: SymmetricProperty
domain: Department Location
range: Department Location
descriptions: Spatial location description of departments on the floor's operational area

belongs To Board Family
type: ObjectProperty
inverse of: has Board Type
domain: Board Type
range: Board Family

belongs To Department
type: ObjectProperty
domain: Class
  union of: Process
  union of: Process Step
range: Department
descriptions: Each department has specific tasks that is disjoint from tasks of other departments

belongs To work Order
type: ObjectProperty
domain: WIPEntity
range: Work Order
descriptions: This helps to identify which Wip entities belong to what work order

executes Route Step
type: ObjectProperty
domain: Execution Step
range: Route Step

for WIP Board
type: ObjectProperty
domain: Execution Step
range: WIPEntity

has Board Type
type: ObjectProperty
domain: Board Family
range: Board Type

has Department
type: ObjectProperty
inverse of: located On Operational Area
domain: Operational Area
range: Department
descriptions: Operationa Area (or Floor) may have one or more department. Each department has its own goal and set of processes.

has Location
type: ObjectProperty
sub property of: topObjectProperty
domain: Department
range: Department Location

has Next Execution Step
type: ObjectProperty
domain: Execution Step
range: Execution Step
descriptions: ExecutionStep links a work-in-progress board to the route step it is currently executing, enabling real-time tracking and reasoning

has Next Route Step
type: ObjectProperty
inverse of: has Previous Route Step
domain: Route Step
range: Route Step
descriptions: This route step is followed by the next route step.

has Next Step
type: ObjectProperty
inverse of: has Previous Step
domain: Process Step
range: Process Step

has Operator
type: ObjectProperty
domain: ManualMachines
range: Role

has Previous Route Step
type: ObjectProperty
domain: Route Step
range: Route Step
descriptions: This route step comes after the previous route step

has Previous Step
type: ObjectProperty
domain: Process Step
range: Process Step

has Process
type: ObjectProperty
domain: Department
range: Process

hasProcessStep
type: ObjectProperty
domain: Process
range: Process Step
descriptions: A general relationship for Process to be connected to a ProcessStep.
comment: TAG:PROCESS
see also: has Process Step

has Role
type: ObjectProperty
domain: Person
range: Role

has Route
type: ObjectProperty
domain: Board Type
range: Route

has Route Step
type: ObjectProperty
inverse of: is Route Step Of
domain: Route
range: Route Step
descriptions: A route consists of several route steps

has Same Operational Area
type: ObjectProperty
type: SymmetricProperty
type: TransitiveProperty
type: ReflexiveProperty
domain: Department Location
range: Department Location

has Operational Area
type: ObjectProperty
domain: Factory
range: Operational Area
descriptions: A Factory has operational areas, in which certain operations are carried out.
comment: TAG:SPATIAL

has Work Order For Board Family
type: ObjectProperty
domain: Work Order
range: Board Family

has Work Order For Board Type
type: ObjectProperty
domain: Work Order
range: Board Type

is Route Step Of
type: ObjectProperty
domain: Route Step
range: Route

located On Operational Area
type: ObjectProperty
type: FunctionalProperty
domain: Department Location
range: Operational Area

performed By Role
type: ObjectProperty
domain: Process Step
range: Role

processed In Department
type: ObjectProperty
domain: Board Type
range: Department
comment: a bit explanatin: If a BoardType hasRoute some Route, and that Route routeHasStep some Step, and that Step inDepartment some Department, then the BoardType processedInDepartment that Department.

refers To Process Step
type: ObjectProperty
domain: Route Step
range: Process Step
descriptions: This propert helps to explain that at this position in the route, the board enters and completes this process

requires Machine
type: ObjectProperty
domain: Process Step
range: Machine

requires Material
type: ObjectProperty
sub property of: topObjectProperty
domain: Class
  union of: Board Type
  union of: Process Step
range: Material Type

requires Resources
type: ObjectProperty
domain: Process Step
range: Resources

Requires Role
type: ObjectProperty
domain: Process Step
range: Role
descriptions: Each Department has several roles.

belongsToWorkOrderID
type: DatatypeProperty
domain: Board Type
range: string
descriptions: Literal reference to a work order identifier.

ended At
type: DatatypeProperty
range: dateTime

has Board ID
type: DatatypeProperty
sub property of: topDataProperty
domain: WIPEntity
range: string

has Department Code
type: DatatypeProperty
domain: Work Order
range: string
descriptions: Each orderID has a departmentCode (Source: EDA by Miren)

has Equipment ID
type: DatatypeProperty
type: FunctionalProperty
domain: Resources
range: string

has Lable ID
type: DatatypeProperty
type: FunctionalProperty
domain: WIPEntity
range: string

has Material ID
type: DatatypeProperty
domain: Material Type
range: string
descriptions: Each type of material has an ID (most likely already recorded in the ERP system)

has Material Quantity Per Board
type: DatatypeProperty
domain: Board Type
range: integer
descriptions: Each board type requires specific material with a certain quantity. This property helps calculate how much material is needed for each board and subsequqntly each work order.

has Name
type: DatatypeProperty
domain: Department
range: string

has Operation Code
type: DatatypeProperty
range: string

has Operation Description
type: DatatypeProperty
domain: Process Step
range: string
descriptions: Each task have a description that can be recorded

has Operation Sequence Number
type: DatatypeProperty
range: integer

has Personnel ID
type: DatatypeProperty
type: FunctionalProperty
domain: Person
range: string
descriptions: Each employee has an ID

has QR Code
type: DatatypeProperty
domain: Board Type
range: anyURI

has Work Order Description
type: DatatypeProperty
domain: Work Order
range: string
descriptions: This is a descritptin of the order that client has made

has Work order ID
type: DatatypeProperty
domain: Work Order
range: string
descriptions: Each Board belongs to a specific Work Order (and batch)

has Work Order Quantity
type: DatatypeProperty
domain: Work Order
range: int
descriptions: Each work order has a quanity of the board type requested by client

started At
type: DatatypeProperty
range: dateTime

Actor
type: Class
descriptions: A superclass for personnel-related concepts

Assembly department supervisor
type: Class
subclass of: Supervisor
comment: The team leader responsible for organizing tasks before production, preparing barcodes, and distributing the work.

Board Family
type: Class
subclass of: Restriction
  on class: Board Type
  min qualified cardinality: 2
  on property: has Board Type
descriptions: This class shows that an order can come for multiple board types

BoardMaterialRequirement
type: Class
comment: Maybe the name can be changed. But in essence, we need a class to say for which board type we need what materials.

Board Type
type: Class
subclass of: Restriction
  on class: Material Type
  min qualified cardinality: 1
  on property: requires Material
comment: Should we create 37 boards here?Update: according to the new report, there are 65 unique board types

Camera
type: Class
subclass of: AutomaticMachines
comment: The system that performs visual quality control using a camera.

Card
type: Class
subclass of: PortableFurniture
comment: AKA Wheeled transport cart

Department Location
type: Class

Execution Step
type: Class

Material Type
type: Class

Material preparation personnel
type: Class
subclass of: LineWorker
comment: Personnel who checks the materials required for assembly and delivers them to the line workers.

Operational Area
type: Class
descriptions: Operational area or the floor
comment: equaivalent to BOT:storey

Operator
type: Class
subclass of: LineWorker
comment: Personnel who operate manual machines and perform resistor shaping processes.

Process
type: Class
descriptions: department-level workflow

Process Step
type: Class

Responsible technician
type: Class
subclass of: LineWorker
comment: The technical personnel who delivers barcode labels to the First Line Worker.

Route Step
type: Class

Supervisor
type: Class
subclass of: Role
comment: People who manage people and processes

Test
type: Class
descriptions: Each board needs to go through one or more tests to certify its health before it is sent to client

Tool
type: Class
subclass of: Resources
comment: Maybe call them tools

Wave soldering entry personnel
type: Class
subclass of: LineWorker
comment: The person who sets up the machine and places the boards into the masking pallet.

Wave soldering exit personnel
type: Class
subclass of: LineWorker
comment: Aybar has Inspector entity. should this person be inspector or not?
comment: The personnel who visually inspects the boards exiting the soldering machine and intervenes if necessary.

Work Order
type: Class
descriptions: Each work order signifies the board type(s) ordered by the client

Workstation
type: Class
subclass of: ComputerisedSystems
comment: AKA Computer