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.
Spatial location description of departments on the floor's operational area
Each department has specific tasks that is disjoint from tasks of other departments
This helps to identify which Wip entities belong to what work order
Operationa Area (or Floor) may have one or more department. Each department has its own goal and set of processes.
ExecutionStep links a work-in-progress board to the route step it is currently executing, enabling real-time tracking and reasoning
This route step is followed by the next route step.
This route step comes after the previous route step
A general relationship for Process to be connected to a ProcessStep.
A route consists of several route steps
A Factory has operational areas, in which certain operations are carried out.
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.
This propert helps to explain that at this position in the route, the board enters and completes this process
Literal reference to a work order identifier.
Each orderID has a departmentCode (Source: EDA by Miren)
Each type of material has an ID (most likely already recorded in the ERP system)
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.
Each task have a description that can be recorded
This is a descritptin of the order that client has made
Each Board belongs to a specific Work Order (and batch)
Each work order has a quanity of the board type requested by client
A superclass for personnel-related concepts
The team leader responsible for organizing tasks before production, preparing barcodes, and distributing the work.
This class shows that an order can come for multiple board types
Maybe the name can be changed. But in essence, we need a class to say for which board type we need what materials.
Should we create 37 boards here?Update: according to the new report, there are 65 unique board types
The system that performs visual quality control using a camera.
Personnel who checks the materials required for assembly and delivers them to the line workers.
Personnel who operate manual machines and perform resistor shaping processes.
The technical personnel who delivers barcode labels to the First Line Worker.
Each board needs to go through one or more tests to certify its health before it is sent to client
The person who sets up the machine and places the boards into the masking pallet.
Aybar has Inspector entity. should this person be inspector or not?
The personnel who visually inspects the boards exiting the soldering machine and intervenes if necessary.
Each work order signifies the board type(s) ordered by the client