Organizational position is never sufficient. Effective grant, qualification, scope, assignment, and program context are evaluated independently.
Organization lifecycle
Organization activation, suspension, and archival require a separate authenticated platform-security operator workflow.
Branches
Invitation lifecycle
Create a customer organization, enable its portal, then invite an approved portal user. The customer sets a first password through the existing /reset-password email and signs in at the Customer Portal. This does not create employee membership or maintenance authority.
Customer organizations
Portal status
Portal users
Assigned aircraft
Employee directory
Membership administration
Lifecycle behavior
Membership suspension revokes sessions.
Assignments and company grants end.
Open work must be transferred first.
Maintenance and audit history is retained.
Configured templates
Credential records
Training status
Active and recorded grants
Aircraft list
Select an aircraft to view its record foundation.
Selected-aircraft history
Timeline
Installed components
Configuration
Legacy aircraft attachment links
Controlled technical documents
Maintenance records
Operational lifecycle only. Customer authorization is commercial evidence; inspection results are not regulatory approval, signing, or return to service.
Requests and estimates
Work-order dashboard
Select a work order to view tasks, findings, parts, labor, inspections, and timeline.
Findings and corrective actions
Select a finding to view troubleshooting, corrective actions, verification, and history.
Parts and availability
Select a part to view its authorized component availability.
Component list
Select a component for its event history.
Related technical documents
Traceability boundary
History is append-only and actor-attributed. Installation and removal remain atomic aircraft transactions.
This module does not determine airworthiness, approve installation, sign records, or release an aircraft to service.
Positions
Installation history
Removal history
Digital component passport — a unified evidence and lifecycle record for a serialized component. It does not determine airworthiness, approve part eligibility, authorize installation, or enable return to service. A complete evidence record is never proof of airworthiness, and missing evidence is never proof of ineligibility. Sign and release-to-service remain disabled.
Classification
Condition
Evidence completeness
Life limits
Remaining life (deterministic evidence calculation only)
A published classification policy version is permanently immutable. Publishing a new version never edits an older one — the most recently published version for a code is simply treated as current.
Human-controlled operational quality workflow only. Inspection acceptance and internal sign-off do not determine airworthiness or authorize return to service.
Pending inspections0Assigned inspections0Rejected work0Awaiting corrections0Resubmitted work0Awaiting final sign-off0Overdue0Open exceptions0
Inspection detail and complete cycle
Select an inspection request.
Deterministic scheduling and due-status calculations only. Nothing here determines airworthiness, approves an inspection, or generates a binding return-to-service due date — humans authorize deferrals and close out maintenance-program requirements through the existing controlled work-order workflow.
Due soon0Overdue0Deferred0Active bays0Scheduled work orders0
Recent utilization — selected aircraft
Due-item planning & close loop
Work Order administrative closure alone does not accomplish a due item. Create a satisfies planning link, then explicitly record accomplishment using canonical aircraft utilization evidence.
Planning work links
Accomplishment history
Bays
Bay planning timeline
Shift allocations — selected schedule
Human-controlled inventory workflow only. Receiving acceptance and issue do not determine airworthiness, installation eligibility, inspection approval, or return to service.
Available stock0Reserved stock0Quarantined stock0Receiving inspections0Low stock0Shelf-life alerts0Open requests0AOG shortages0Transfers in transit0Discrepancies0
Parts-request queue
Warehouses and bins
Current stock
Selected inventory record
Receiving-inspection queue
Transfer queue
Destination receipt uses the shipped quantity unless a reconciled quantity is entered. Explain every discrepancy.
A document relationship or library presence does not establish applicability, approved technical data, inspection authority, or return-to-service authority. Attachment presence is never an airworthiness determination.
Items requiring attention
Canonical attachment pipeline states and inventory/document-review conditions that need a human look. Malware quarantine, inventory receiving quarantine, and component-passport quarantine remain distinct.
Attachment scan / quarantine
Statuses from attachment_uploads.status: quarantined, scanning, clean, rejected, failed.
Inventory document review
Receiving rows waiting on documents or held for document review — not malware quarantine.
Passport condition and evidence completeness only. Complete evidence is not proof of airworthiness or installation eligibility.
Document library
Loading documents…
Selected document
Select a document.
Revision history
Applicability and relationships
Access history
Metadata, history, and version downloads create append-only access and audit evidence.
My sessions
Current hosted identity links
Evidence-grounded maintenance knowledge assistant — retrieves authorized technical
documents and internal maintenance history and cites its sources. It does not determine
airworthiness, diagnose conclusively, select or approve a repair procedure, approve an inspection,
approve return to service, or sign any record. Sign and release-to-service remain disabled. Always
verify against current approved technical data and authorized personnel before performing or
approving maintenance.
The maintenance assistant is not currently
enabled or configured for this organization.
Ask a question
Answer
Sources
Source index status (administrators)
Append-only administrative audit
Operational reporting computed live from canonical Work Order, scheduling,
quality/inspection, inventory, customer-authorization, procurement, commercial, component,
and platform records. Counts, sums, and durations only — not a prediction,
airworthiness determination, or regulatory-performance statement. Operations Home remains
the action-oriented entry point; these reports are for deeper analysis.
Overview — current state (counts, as generated)
Snapshot as of —. Not date-ranged.
Open findings by severity & status (count)
Work Orders by status (count)
Work Order aging & turnaround — period (count, seconds, days)
Period —. Opened/closed counts and average turnaround are bounded to this date range; aging below is current open Work Orders ordered oldest first.
CSV export carries the branch, aircraft, status, and date filters above.
It is the only canonical report shaped as a row list, so it is the only report the
server exports as CSV.
Scheduling & due items
Current due-item state and bay load by branch. This report is not
date-ranged: the server reports present due status, not a historical window.
Due-soon, overdue, and deferred are the canonical due-item statuses.
Select this report to load it.
Quality & inspection
Inspection queue depth and in-period request outcomes. Acceptance here
is operational inspection acceptance as already recorded — it is never an
airworthiness determination or a return-to-service approval.
Select this report to load it.
Inventory & parts
Receiving, quarantine, and parts-demand counts, plus stock by
warehouse. Statuses are the canonical inventory receiving and operational states.
Select this report to load it.
Customer authorization
Authorization response volume and current work waiting on a customer
decision. Authorization is a commercial approval and never implies inspection
acceptance or release to service.
Select this report to load it.
Procurement & supplier
Requisition, RFQ, quote, award, and receipt counts and timings. Every
figure is a plain count, average, or rate. No supplier score is computed, and nothing
here determines whether a part is fit to fly or approved for installation.
Select this report to load it.
Commercial billing, warranty & core
Unbilled work, invoice and credit values, warranty claim exposure, and
core obligation exposure. Plain counts, sums, and averages — not an audited
financial statement.
Select this report to load it.
Component & asset evidence
Component passport evidence completeness, quarantine and scrap counts,
and life limits recorded in the period. Evidence completeness describes recorded
documentation only — it never labels a component airworthy or unairworthy.
Select this report to load it.
Background job health
Scheduled job definitions and the last 24 hours of runs. The server
bounds this report to a rolling 24-hour window and accepts no filters.
Select this report to load it.
Integration exchange
Connection health plus inbound, outbound, exception, and delivery
counts for the period. Narrow to one connection with the filter above.
Select this report to load it.
Data migration & import
Import batch lifecycle counts, validation-issue severity, and
reconciled execution outcomes. Narrow to one import project with the filter above.
Select this report to load it.
Maintenance assistant usage
Assistant query volume, abstentions, citation-validation failures, and
evidence-status distribution for the period. Reporting only — it does not change
what the assistant is allowed to answer or cite.
Select this report to load it.
Operational coordination for shift handoffs, branch-to-branch transfers, AOG events, escalations, and aircraft/Work-Order discussions. Acknowledgment here means a message or status was received and reviewed — it never implies inspection acceptance, maintenance approval, regulatory sign-off, or return-to-service approval. Sign and release-to-service remain disabled.
Handoffs
Branch transfers
Accepting a transfer records operational responsibility only. It does not create technical or return-to-service authority.
AOG events
AOG status reflects operational coordination only — it is never an airworthiness determination.
Escalations
A discussion message is not an official maintenance record. Use promotion to create an attributed finding, corrective-action draft, handoff item, or technical document from a message.
In-app notifications and operational alerts surfaced from work orders, scheduling, findings, quality/inspections, inventory, customer authorization, compliance gates, and shift/branch/AOG coordination. Acknowledging or archiving a notification means it was received and reviewed — it never implies inspection acceptance, maintenance approval, regulatory sign-off, airworthiness determination, or return-to-service authority. Sign and release-to-service remain disabled.
Summary
Total—Unread—Requires acknowledgment—Critical—
Notifications
Outstanding alerts (organization/branch)
Supervisory view across the branches you can access, plus organization-wide alerts. Run the alert evaluator to scan for new due-item, work order, finding, inspection, inventory, customer-authorization, and compliance-gate alerts.
My notification preferences
Per-category severity threshold and delivery settings for your own inbox.
Rule versions
A draft may be edited freely. Once published, a rule version is permanently immutable.
Automates the existing alert evaluator (Notifications & alerts) on a recurring schedule using a PostgreSQL-native background-job worker — no external queue or cron. Every run is leased so at most one worker process executes a given job definition at a time, and every run is recorded here with its evaluation window and outcome. This automates evaluation and delivery only; it never signs, releases to service, or grants any authority beyond what the underlying alert evaluator already has. Sign and release-to-service remain disabled.
Job definitions
Run history
Select a job definition above to view its recent runs, including the evaluation window each run covered and how many alert events/deliveries it produced.
Controlled, admin-only bulk import of legacy-system data (CSV/JSON only) into this
platform's canonical records. Every import is staged, validated, duplicate-checked, dry-run, and
requires a different person to approve than the one who prepared it before any canonical record is
created — execution runs asynchronously through the same background-job worker used elsewhere.
This never fabricates a signature, verified credential, or airworthiness determination from source
data; imported claims are recorded as unverified until an authorized person reviews them.
Import projects
Mapping versions
Only a fixed, non-extensible set of field operations is supported (trim, case,
enum_map, date_parse, timezone_convert, unit_convert, boolean_normalize,
part_number_normalize, registration_normalize) — no formulas, scripts, or expressions.
A published mapping version is immutable; publish a new version to change it.
Batches
Lifecycle actions
Each action only succeeds when the batch is in the matching lifecycle state; the
server enforces every transition and reports why an action was refused.
Validation issues
Duplicate-candidate matches
Fuzzy matches are never auto-merged — every match here requires a human
resolution before the batch can leave review.
Reconciliation report
Machine-to-machine connections for external systems to submit signed aircraft
utilization evidence. A connection is a non-human service principal — it never inherits an
employee's role, title, certificate, or technical authority, and it can never sign or release an
aircraft to service. Every submitted reading is validated and only ever recorded through the same
canonical utilization service used everywhere else in this system.
Overview
Connections
Connection detail
Scopes for selected connection
Credentials
A rotated credential's plaintext secret is shown exactly once, immediately below,
and never again — store it securely now.
Aircraft mappings
Deterministic matches only — nothing here is ever auto-selected from a fuzzy
or probabilistic match. Activation requires human approval before any submitted reading can be
accepted against the mapped aircraft.
Inbound events
Exceptions queue
Exception detail
Outbound subscriptions
Deliveries are signed the same way inbound submissions are verified, sent only to
validated public HTTPS endpoints (no loopback, link-local, private, or metadata-service
addresses), and retried with bounded exponential backoff before moving to dead-letter.
Outbound events
Delivery attempts
Controlled procurement workflow: maintenance/inventory demand becomes a
requisition, buyers source from organization-approved suppliers, multiple supplier quotes
are captured and compared, an authorized human awards the business, and a controlled
purchase order is released. This system does not determine part airworthiness,
installation eligibility, approved interchangeability, supplier regulatory status,
inspection approval, or return-to-service authority. Supplier approval below means
"organization-approved" for procurement purposes only.
Supplier directory
Supplier detail
Qualification history (selected supplier)
Requisitions
Requisition detail
RFQ rounds (selected requisition)
RFQ detail & recipients
Quotes (selected RFQ version)
Deterministic quote comparison
Facts only — lowest quoted cash commitment and earliest stated arrival are labeled;
nothing here is an automatic award or a "best supplier" recommendation.
Purchase orders
Purchase order detail
Commercial, billing, and warranty-recovery workspace. Approving, issuing, or voiding a commercial record never determines airworthiness, inspection status, or return-to-service authority -- those remain reachable only through maintenance sign / release-to-service, which stay disabled here.
Read-only operational summary for administrators. Extends this same administration
application and reuses the liveness/readiness checks, background-job observability, and security-event
classification already built elsewhere in this console — this is not a second monitoring
dashboard or a separate observability system. Never displays secret values, connection strings, file
paths, or raw error detail; a status of "healthy" here always means every checked dependency actually
confirmed healthy, never a default assumption.
Overview
Dependencies
Background jobs
Integrations & AI assistant
Schema & build
Recent security events
Bounded counts only, grouped by severity and category — see Audit history and
Account security for individual records.