Quality management for manufacturing

Quality, drawn to tolerance.

Fortress QMS is the quality system for manufacturers. Non-conformances, 8Ds, inspection, calibration and audits share one traceable record, so the answer is already on file when someone asks.

  • Data held in London
  • Two-factor and SAML SSO
  • Append-only audit trail
Ø3406× Ø28 EQ SPØ0.05AAPCD Ø224124.018BORE · H7
Try it

Measure the bore

Illustration, made-up numbers

Ø124 H7 Limits 124.000 to 124.040 mm

124.018In toleranceDrag the slider past 124.040

Sheet 02 · Parts list

Everything the quality department actually does, in one assembly.

Twelve modules that share one set of people, parts, suppliers and records. Raise something in one and it is already linked in the others.

ItemModuleWhat it does
1Non-conformancesInternal, customer and supplier NCs from raise to close: containment, disposition, cost, affected lots, RMA numbers.
28D corrective actionNine steps, root-cause tools, verification that goes stale if the actions change, and a printable report.
3In-process inspectionControl plans, shop-floor jobs and sampling. The database judges every reading against limits frozen when it was taken. CMM files import.
4Process control (SPC)I-MR, X-bar/R, P, NP, C and U charts, Western Electric rules, capability indices and alerts that never raise a non-conformance on their own.
5CalibrationGauges, recall schedules, as-found and as-left readings. A failed calibration quarantines the gauge and shows what it measured.
6AuditsAudit templates with versions, schedules, records with ten answer types, and findings that become non-conformances.
7Document controlRevisions, review and approval, read-and-acknowledge, periodic review and stamped controlled PDF copies.
8Supplier qualityApproval, certifications, risk, SCARs, goods receiving, incoming inspection, material certificates and scorecards.
9Production traceabilityOrders, lots and serial numbers, traced from the supplier’s delivery to the non-conformance that named the lot.
10Risk and management reviewA 5 × 5 risk register with acceptance, quality objectives and management reviews built from live figures.
11CompetenceWho can do what: skills, positions, assessments, training sessions and a matrix that shows the gaps.
12Integrations and workflowsCSV, REST and a connector agent for your databases. Rules that tell people or give them tasks when something happens.

Sheet 03 · Traceability

One thread from the supplier’s lot to the closed 8D.

Search an order, lot or serial number and see every receipt, inspection, non-conformance and 8D that touched it, on one page you can print.

  1. 1GR-26-0112

    Goods receipt

    Steel bar arrives against the order. The lot is made, and held until it is inspected when your rules say so.

  2. 2HT-2219

    Lot

    Every later record can name this lot, so the question “where did it go?” has an answer.

  3. 3WO-8841

    Production order

    Machined on a named machine, against a named control plan revision.

  4. 4IPI-26-0387

    Inspection

    A reading fails. It must be acknowledged or raised. It cannot be left.

  5. 5NC-26-0042

    Non-conformance

    Raised from the reading, naming the affected lot, with containment and a disposition.

  6. 6CAPA-000019

    8D

    Root cause verified, actions done, effectiveness checked, then closed.

Example references. Yours follow your own numbering.

Sheet 04 · Revision history

Every change has a name, a time and a reason.

The audit trail is append-only. Nobody in the app can edit or delete it, so the history you show an auditor is the history that happened.

  • Reasons are required for the changes that matter: reopening a step, changing a source, correcting a reading.
  • Completed steps lock. Reopening one is a recorded act with its own reason.
  • If two people edit one record, the second is told who changed what, and nothing is overwritten silently.
audit.events  ·  append only
  1. C. Boateng NC-26-0042

    Severity Minor → Major

    “Customer escalated the complaint”

  2. A. Patel CAPA-000019

    Step D4 completed

    “Root cause verified by trial run”

  3. S. Ellis CAL-26-118

    Gauge G-0447 quarantined

    “Out of tolerance as found”

  4. M. Rowe SOP-014

    Revision C made effective

    “Approved for today”

  5. L. Novak AR-26-0031

    Finding AF-26-0058 raised

    “Guard interlock not tested”

Example entries

Sheet 05 · Security

Built like the part has to survive an audit.

Quality records are evidence. The controls around them are not an add-on.

S1

Walls between organisations

Every record carries its organisation, and the database itself refuses to show it to anyone else. That is enforced in the data layer, not just in the screens.

S2

Sign in your way

Two-factor sign-in, or require your company’s single sign-on (SAML). Keep a break-glass administrator for the day the identity provider is down.

S3

Know where they connect from

Limit access to your office and VPN addresses. Try it in monitor mode first and see who would have been blocked before you switch it on.

S4

The right access, site by site

Roles, sites and departments decide who can see and change what. Seats decide which parts of the product each person can use.

S5

Private files

Evidence, certificates and procedures sit in private storage and open through short-lived links, never public addresses.

S6

Held in London

The database, the files and the API all run in London, so your quality records stay in the UK.

Sheet 06 · Interfaces

Bring your data with you.

You do not start from a blank screen. Import what you already have, and keep it in step with the systems that stay.

A

Where it lives today

  • CSV or Excel files
  • A REST API
  • SQL Server, PostgreSQL, MySQL
  • Folders on your network

A small connector agent sits inside your network and only ever dials out, so you open no inbound firewall ports.

B

Map it and look first

  • Match columns to fields
  • Clean values with steps or formulas
  • See which rows would fail

Preview the whole import before anything is written. Fix the source, run it again, and rows that have not changed write nothing.

C

Fortress

  • Parts, suppliers, machines, gauges
  • Employees, production orders
  • Purchase orders and receipts

Each record remembers where it came from. You choose, per field, whether the source or Fortress wins when they disagree.

Sheet 07 · Release

Bring your quality system out of the filing cabinet.

Start a 14-day trial, set up your sites and invite the team. If you would like to see it first, tell us what you make and we will show you.

A card is needed to start the trial. You can manage or cancel it from the billing page at any time.