--- title: "Operations and Quality" url: "https://hurukan.com/modules/operations-and-quality" description: "Planning, work queues, scheduling, hours and subcontracting, with inspections, non-conformances, release and certificates on the same record as the orders." --- # Operations and Quality Operations covers the work a company delivers — planned, queued, scheduled and recorded in hours — and quality covers whether it was done right: inspections, non-conformances, release and the certificates that go with it. Both sit on the same record as the orders they serve. [Talk to us](https://hurukan.com/contact) An engineer checking a tablet beside a machining centre and a robotic arm in a clean production hall Module - Planning, work queue and scheduling - Operations, hours and subcontracting recorded against orders - Inspections, non-conformances and release - Certificates produced from the record ## The work and whether it was right Operations is deliberately generic. A company may assemble products, deliver projects on a customer’s site or provide a technical service; in each case there is work to plan, people and equipment to schedule, hours to record and a result someone must check. Hurukan treats all of that as one record, linked to the customer order and milestone that caused it, rather than a separate production system with its own copy of the orders. ## Plans that react Work enters the queue from orders and milestones in **Commerce**. It is scheduled against the people and equipment available and the materials in **Inventory and Logistics**. When something changes — a late delivery from a supplier, a sick colleague, an urgent order — an agent proposes a new schedule and lists what it affects. A person approves it, and the new dates reach commerce and customer service at once. ## Quality on the same record Inspections are planned with the work, not after it. Results, measurements and non-conformances are recorded against the operation and the item, with the actions taken to resolve them and who closed them. When finished work is released, the certificate the customer receives is produced from what was actually recorded, so the document and the record always agree. ## How it fits with what you run This module plans and records the work; machine-level control stays in the systems built for it, and Hurukan exchanges data with them. Release is a decision by a named person, and recurring non-conformances are linked to their suppliers in **Procurement**, where they count towards each supplier’s risk status. ## What the module covers 01 ### Planning Work derived from customer orders and milestones, with the capacity, materials and people it needs, so a promise to a customer can be checked against what is possible. 02 ### Work queue and scheduling One queue of work ready to start, scheduled against available people and equipment, and rebuilt when something changes. 03 ### Operations and hours Each operation recorded with who did it, how long it took and what it consumed, against the order it belongs to. 04 ### Subcontracting Work sent to outside partners tracked like work done in-house: what was sent, when it is due back and what it costs. 05 ### Inspections and non-conformances Inspection plans, results and non-conformances recorded against the work and the item, with the actions taken and who closed them. 06 ### Release and certificates A person with release rights approves the result, and the certificate that goes to the customer is produced from the record rather than typed. ## Works with [Three people around a large touch table in a glass meeting room, one pointing at a flow of cards ### Agentic Logic Domain agents that act within written limits, with people deciding on critical steps. → ](https://hurukan.com/system/agentic-logic)[A hand placing a block on a white architectural model of a campus, with threads linking the buildings ### Ontology The company's digital model: objects, relations and rules, versioned and growing with the business. → ](https://hurukan.com/system/ontology)[A technician's hand plugging a cable into a neatly routed fibre-optic patch panel ### Data Connectors and one data model: imports, sync, documents, e-invoicing and office suites in one record. → ](https://hurukan.com/system/data)[A tall warehouse aisle with high racking and a mobile robot carrying a tote ### Inventory and Logistics Item master, stock, receipts, issues, reservations and counts; delivery planning and carriers. → ](https://hurukan.com/modules/inventory-and-logistics)[Two people reviewing a tablet at a loading dock beside stacked crates and a truck ### Procurement Requisitions, a supplier register with risk status, RFQs, offer comparison, approved purchase orders, deliveries and returns. → ](https://hurukan.com/modules/procurement) ## Questions How does it relate to machine control systems? It plans and records the work, whatever that work is; machine-level control stays in the systems built for it, which Hurukan exchanges data with. What happens when a schedule breaks? An agent proposes a rebuilt schedule and lists the orders and customers it affects, with the reasons. A person approves it, and commerce and service see the new dates. Who releases finished work? A person with release rights. An agent can gather the inspection results and documents and flag anything missing, but release is a decision recorded against a named person. [← PreviousCustomer Service](https://hurukan.com/modules/customer-service)[Next →Procurement](https://hurukan.com/modules/procurement) ## Build the company's operating system with us Hurukan is pre-launch. If you run a company and want a sovereign, agentic system rather than another suite, we would like to hear what you need. [Talk to us](https://hurukan.com/contact)