Product — the 23 modules inside JBird

Stage 1

Define

What your organization does, who it does it for, and what it has committed to. This is where onboarding starts — and JBird starts empty on purpose, because no two organizations map the same way.

Step 1 · the landing tab

Interaction of Processes

A builder, not a fixed diagram. Add your processes, group them into categories you control, and define what flows between them. The diagram draws itself from that data — connectors are routed by measuring the real rendered boxes, so a line never cuts through an intermediate process.

Each process carries the three legs of the turtle diagram an auditor expects — Inputs, Activities, Outputs, all required — plus its owner, its applicable standards and clauses, its KPI table, its audit interval, and the training its team needs. Everything downstream reads from here.

The interaction-of-processes diagram in JBird, with Management, Core and
Support bands and labelled connectors between processes.

4.1 – 4.3

Organizational Context

Issues log, interested parties with stakeholder mapping and RACI, and the QMS scope with the 9101 not-applicable justification cross-check.

4.2 · 8.2

Requirements Register

Every customer, statutory, regulatory and internal requirement you've taken on, with where it came from and what satisfies it.

6.2

Quality Objectives

Objectives with a cascade view down to the process KPIs that actually measure them, referenced to the real SCMH 7.11.2 source.

6.1

Risks & Opportunities

Assessment and treatment, with actions that land in the master Action Tracker rather than dying in the register.

6.3

Change Management

Planned changes to the QMS with their risk assessment, so clause 6.3 isn't a paragraph in the manual with nothing behind it.

8.4

Customers & Suppliers

Both registries, with supplier approval status and scope, and bulk import when you're bringing an existing list across.

Stage 2

Resource

The clause 7 family — the people, equipment and knowledge the processes need in order to work.

7.1.3 · 7.1.5

Infrastructure & Equipment

Flag anything used to verify conformity as monitoring and measurement equipment and JBird tracks its whole calibration life: interval, method, traceability, acceptance criteria, and readings at multiple reference points for internal calibrations.

Due status is computed live from the calibration log — never a manually-set flag. Overdue equipment carries a clause 7.1.5.2 warning, an out-of-tolerance finding prompts an impact assessment on previous measurement results, and a formal out-of-service quarantine log records what was pulled and when.

The equipment register in JBird, showing an overdue torque wrench with its
gage ID, calibration method, traceability and acceptance criteria.

7.1.2 · 5.3

People

Your organization chart, plus roles, responsibilities and authorities mapped to the clause 5.3 requirements they satisfy.

7.2 · 7.3

Training

Training roles, records and effectiveness — including the per-process competency requirements defined on the process itself.

7.1.6

Organizational Knowledge

What the organization knows and how it gets it, with a repeatable review log for clause 7.1.6's "changing needs and trends".

8.5.4

Shelf-Life & Preservation

Time and condition-limited stock with expiration computed live — from an explicit date, or a manufacture date plus a shelf-life duration — using the same due/overdue discipline as calibration. Never a flag somebody remembered to set. Matters most for AS9120B stockists.

Stage 3

Document

Documented information under control — which is where a surprising share of findings start.

7.5

Documents

Procedures, work instructions, forms, policies and scope statements with revision history, approval state and links to the process they belong to.

7.5.3

Records Retention

Retention periods per document, with eligibility computed rather than tracked by hand on a schedule nobody revisits.

4 – 10

Quality Manual

Clauses 4 through 10 with the AS9100D, AS9120B and AS9110C sector requirements in place, each clause showing its linked processes and documents. Editable where your wording should differ from the template.

Stage 4

Verify

Where JBird is furthest ahead of a spreadsheet — and where the 9101 methodology actually shows up.

9.2 · IAQG 9101

Internal Audits

An audit programme with a configurable multi-year cycle, per-process audit intervals, and coverage computed from real completed-audit history — so "which processes are overdue for audit" is a fact, not a guess.

Inside an audit: a QMS Process Matrix (9101 Form 2) marking each clause Conforming, Nonconforming, Not Evaluated or Not Applicable per process, with an objective evidence summary per clause section. A PEAR (9101 Form 3) per process, whose inputs, activities, outputs and KPIs come straight from the process map. And an auditor's questionnaire generated per process from its documents, outputs and tagged clauses, with a standing clause 7.3 personnel-awareness check.

Effectiveness scored from process realization and process results
Mark a clause nonconforming and raise the NCR from the same screen
Answers auto-save as you work through the interview

A PEAR in JBird with responsibility, applicable clauses, inputs,
activities, outputs, KPI table, auditor observations, audit trail and
process effectiveness rating.

9.3

Management Review

The 9.3.2 inputs assembled from what the system already knows — customer satisfaction, external provider performance, requirements register status, objectives status, risk and opportunity effectiveness — rather than retyped into a slide deck once a year.

All

Gap Analysis

Every clause of every standard you hold, status computed from the processes and documents actually tagged to it, filterable per standard.

All

Dashboard

Readiness per sector scope, open findings against their deadlines, calibration recall, overdue audits — all computed, none of it typed in.

8.1.2 · 8.5.2 · 8.6

Release & Configuration

Configuration items tied to the requirement they're built against, with every change logged and linkable to a real Change Management record. Then one release record per decision — product, serial, work order, evidence of conformity. Only people holding an active acceptance authority can be named as releaser, and AS9110C's flight-safety attestation and AS9120B's certifying statement appear only for the standards you actually hold.

9.1.2

Customer Satisfaction

Perception monitoring as the clause actually asks for it — surveys, direct feedback, meetings, compliments, warranty claims, dealer reports — with an improvement plan on any entry showing a real deficiency. This register feeds management review, rather than a count of complaints standing in for it.

Stage 5

Improve

What happens after something goes wrong, handled in the sequence and on the timeline a registrar expects.

10.2

NCR / CAPA

Containment, root cause, correction, corrective action and effectiveness verification, each with its own due date and objective evidence. The 30 and 60-day clocks run automatically, and an item that sits too long escalates on a policy you configure.

Root cause is worked with real tools rather than a free-text box: 5-Whys, fishbone across the standard six categories, fault tree analysis, Pareto and FMEA. Part number, lot, serial and work order are captured so recurrence across related nonconformances can be detected.

Findings raised from an audit or a gage carry their clause with them
Escalation to overdue and critical on configurable thresholds
Nothing closes without a recorded effectiveness check

An NCR card in JBird showing description, clause, containment, root cause,
correction and corrective action with due dates.

All

Action Tracker

One master list of every action the system has generated — from risks, management review, audits and corrective actions — so nothing is only tracked inside the module that created it.

10.2.1

Root Cause Analysis Tools

5-Whys, fishbone, fault tree, Pareto and FMEA, attached to the nonconformance they belong to rather than living in a separate spreadsheet.

Honest scope

What's built, and what's next.

JBird was built system-level first: context, planning, resources, documentation, audit, management review and improvement. The operational clauses are being closed now, highest audit risk first. We'd rather tell you where the line is than let you find out in a demo.

Built and working today

Clause 4 (context, interested parties, scope, processes), clause 5 (leadership, roles), clause 6 (risk, objectives, change), clause 7 (people, infrastructure, calibration, knowledge, competence, awareness, documented information), clause 9 (gap analysis, internal audit with the 9101 forms, customer satisfaction, management review) and clause 10.2 (nonconformity and corrective action).

From clause 8: external provider control (8.4), configuration management (8.1.2), acceptance authority media (8.5.2), preservation and shelf-life (8.5.4), release of product (8.6), and control of nonconforming output (8.7).

On the roadmap

The rest of clause 8 — operational risk management (8.1.1), product safety (8.1.3), proactive counterfeit prevention (8.1.4, where the reactive half already works), customer communication and contract review (8.2), design and development (8.3), special process approval and first article inspection (8.5.1), customer property (8.5.3) and control of production changes (8.5.6).

Plus communication (7.4) and the remaining measurement and improvement work — monitoring-plan completeness (9.1.1), analysis and evaluation (9.1.3) and the continual improvement rollup (10.3).

Why that order

The system-level clauses are the ones every organization shares, whatever it makes. They're also where a paper QMS hurts most, because they cut across everything. The operational clauses are now being closed in order of how often they actually get sampled in an audit — release records, acceptance stamps and configuration control first, because those are the ones an auditor asks for on nearly every visit. The remainder are more specific to what you build, so they're being designed with pilot organizations rather than guessed at — which is part of what a pilot gets to shape.

Twenty-three modules, arranged the way a quality system actually works.