MIYOQA
Contact Request a demonstration

MIYOQA / Platform

One model for product, process and quality.

Kizuna gives each record one identity. More than 30 work surfaces build on it, from the DFMEA to the part submission warrant.

KizunaWork surfacesEngineering BoardSubmission and PPAP

kizuna · a lasting bond

Kizuna: one record, one identity.

Each part, characteristic, operation, workstation, lot, inspection and nonconformance is declared once in the data model, with one identity.

  • One declared data model for product, process and quality records.
  • Versioned bills of process, manufacturing BOMs and plant layouts.
  • Released versions are never edited; a change is a new version. A bill of process is released only after approval by an engineer who neither authored nor proposed the change.
Example dataCharacteristic H2 · Face flatness
Critical characteristic
Characteristic Spine0.05 mm maximum, from drawing DEMO-HOUSING-10 revision BSame characteristic
Control PlanLine 22, CMM, 1 part per hourSame characteristic
MSAGauge G-CMM-02, study on recordSame characteristic
NCRExternal leak rejects, lot PM-2216Same characteristic
ReleasedBill of process revision 3 · Approved by a second engineer, not its author

Kizuna in the product

Released records, kept as they were approved.

A bill of process release block: revision 1 released for pre-launch, revision 2 proposed for production and awaiting approval, with the people who may and may not approve it and who authored each change.
Release. Revision 2 waits for approval. Everyone who proposed it or authored part of the change is listed as unable to approve it, the people who may approve are named, and each change since revision 1 shows its author. Demonstration data, on a second demonstration part.
Operation rows of a bill of process: each operation with its kind, the step it follows and the station it runs on, including a rework path and a reinspection.
Operations. Each operation keeps its kind, the step it follows and the station it runs on, including a rework path and the reinspection after it. Demonstration data, on a second demonstration part.

Platform

Each quality discipline on one model.

Product

  • Product Structure
  • Characteristic Spine
  • Design Analysis
  • DFMEA Worksheet

Process

  • Process Designer
  • Process Flow Studio
  • PFMEA
  • Control Plan
  • Sim Studio

Quality

  • Engineering Board
  • NCR Queue
  • 8D Problem Solving
  • Chart Studio
  • Calibration and Events
  • Quality System

Programme

  • Lifecycle Home
  • Program Schematic
  • Program Portfolio
  • Compliance Grids
  • Document Studio
  • Executive Dashboard

Operations

  • Shop Floor
  • Station terminal
  • Production Monitoring
  • Material
  • Supplier and customer portals

Engineering Board

Investigations built from evidence, not memory.

The Engineering Board draws quality investigations as structured diagrams. Each card on the board refers to a record of the part; it is not a copy.

  • A card can follow its record or hold a fixed revision. When the record is corrected, the board shows what is now out of date.
  • Each cause is marked by how far the records support it: partly supported, assumption, or no evidence found. A category with nothing on record says so.
  • Each person sees only the records their role permits. A board exports as a report or an editable presentation.
Fishbone5-WhyIs / Is not8D reportA3PDCAFault treeValue stream mapSIPOC5W2HAffinity
A fishbone on the MIYOQA Engineering Board for housing face flatness drift and external leak rejects. Measurement causes cite face flatness and bore diameter out of statistical control and a depth micrometer overdue for calibration; Machine causes cite the PFMEA rows for fixture chip buildup and tool wear; Method cites gas entrapment; People, Material and Environment show that no evidence was found.
The board's engines read the whole part and drew this fishbone for housing face flatness drift on the demonstration coolant pump. Each cause cites the record behind it and is marked by how far the records support it; categories with nothing on record say so. Demonstration data.

Engineering Board

The same problem, developed as a 5-Why.

MIYOQA Intelligence, running on Claude Sonnet 5.5, drafted the whys, the root cause and the countermeasure from the part's records: one task, 11 steps, 13 cents. It stopped at three whys because the records supported no more. An engineer read every cited record and accepted the four proposals they support.

A 5-Why analysis on the MIYOQA Engineering Board for housing face flatness drift and external leak rejects, from the recorded problem through each why to the root cause and countermeasure.
Each step cites the corrective actions and audit finding it rests on: chips on the OP20 fixture face, a cleaning interval that was not enforced, and an enforced interval with a sign-off check as the countermeasure. Demonstration data.

Submission

From records to a submission, without retyping.

MIYOQA reads the documents you already have, checks them against the record, and assembles the submission your customer expects.

Import

Your files, checked before they count

FMEA and control plan workbooks, BOMs, MSA and dimensional results, and Q-DAS files. Each upload is shown as parsed and verified, failed, or stored without parsing. Drawing recognition proposes characteristics; a person confirms them.

PPAP

All 18 elements, with the objections first

The compliance grid shows each PPAP element and the questions a supplier quality engineer would raise, before the customer raises them.

Package

Customer requirements, versioned

Customer-specific requirement profiles are kept as approved revisions. The PPAP package is exported in the format the customer portal expects.

Review your own part on MIYOQA.

Bring one part's BOM, PFMEA and control plan. We will show what is connected and what is missing.

Request a demonstrationcontact@miyoqa.com