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.
Quality management for manufacturing
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.
Ø124 H7 Limits 124.000 to 124.040 mm
Non-conformance drafted from the reading.
Sheet 02 · Parts list
Twelve modules that share one set of people, parts, suppliers and records. Raise something in one and it is already linked in the others.
Sheet 03 · Traceability
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.
GR-26-0112Steel bar arrives against the order. The lot is made, and held until it is inspected when your rules say so.
HT-2219Every later record can name this lot, so the question “where did it go?” has an answer.
WO-8841Machined on a named machine, against a named control plan revision.
IPI-26-0387A reading fails. It must be acknowledged or raised. It cannot be left.
NC-26-0042Raised from the reading, naming the affected lot, with containment and a disposition.
CAPA-000019Root cause verified, actions done, effectiveness checked, then closed.
Example references. Yours follow your own numbering.
Sheet 04 · Revision history
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.
C. Boateng NC-26-0042
Severity Minor → Major
“Customer escalated the complaint”
A. Patel CAPA-000019
Step D4 completed
“Root cause verified by trial run”
S. Ellis CAL-26-118
Gauge G-0447 quarantined
“Out of tolerance as found”
M. Rowe SOP-014
Revision C made effective
“Approved for today”
L. Novak AR-26-0031
Finding AF-26-0058 raised
“Guard interlock not tested”
Example entries
Sheet 05 · Security
Quality records are evidence. The controls around them are not an add-on.
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.
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.
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.
Roles, sites and departments decide who can see and change what. Seats decide which parts of the product each person can use.
Evidence, certificates and procedures sit in private storage and open through short-lived links, never public addresses.
The database, the files and the API all run in London, so your quality records stay in the UK.
Sheet 06 · Interfaces
You do not start from a blank screen. Import what you already have, and keep it in step with the systems that stay.
A small connector agent sits inside your network and only ever dials out, so you open no inbound firewall ports.
Preview the whole import before anything is written. Fix the source, run it again, and rows that have not changed write nothing.
Each record remembers where it came from. You choose, per field, whether the source or Fortress wins when they disagree.
Sheet 07 · Release
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.