Operating evidence
Study operating parameters such as pressure, temperature and electrical current to identify significant changes and follow component behaviour over time.
← All projects
SCS health analysis & engineering review
A clearer picture of system condition.
Operating records, fault messages and component history brought together in one documented engineering review.
Deterministic analysisComponent historyReviewed engineering reports
The engineering question
What do the available records tell us, and which findings need a closer review?
The software reviews SAR/XSAR flight data, AIRMAN fault messages and maintenance history together. Engineers can examine recurring faults, check the supporting evidence and prepare a technical report that also explains where information is missing or uncertain.
SCS / Tool snapshots
SCS: operational and maintenance data in one analysis
By comparing operating data, AIRMAN messages and past maintenance work, the tool helps engineers assess system condition, identify repeated problems and follow the history of component replacements. The results can also help teams discuss future maintenance needs and spare-parts planning.
Fault context
Compare AIRMAN fault messages with operating measurements to understand when an issue appeared and what was happening at that time.
What was done
Review maintenance actions, component removals and installations, including part numbers (P/N), serial numbers (S/N) and links to the original records.
The objective / Spare-parts management
Better context for spare-parts planning.
Aircraft rankings, Pareto charts by part number and monthly removal trends help identify where recorded component removals are concentrated. These results can support stock reviews, replenishment plans and further engineering investigations.
Historical removal figures can support planning, but spare-parts decisions must also consider aircraft use, stock availability, repair time and delivery lead times.
Explore the dashboard, aircraft workspace, maintenance database and automatically generated report. Aircraft and airline identities are anonymised. Fleet statuses are edited demonstration values; report pages are historical examples, not current operational assessments.
Fleet health summary
Illustrative fleet: 3 degraded, 5 monitor and 3 normal aircraft. Fleet review is MONITOR; the review label is separate from component severity. Degraded findings remain visible.
SCS Engineering Agent / Interface preview
Three views.
One review workflow.
Start with the overall fleet picture, then review individual components and compare removals by aircraft, part number or selected period.
Synthetic demonstration onlyThe Agent illustrations and filterable example use invented data and DEMO identifiers. These illustrations adapt the application views shown in the presentation for public display.
Engineering Summary
Existing results, with their supporting context.
Review the aircraft and component states already produced by the analysis. Open the relevant sources without silently reassessing the recordings. This synthetic snapshot contains two assessed aircraft.
- Fleet and component detail
- Existing states and priorities
- Links to supporting evidence
Component History
Find a part. Follow its recorded history.
Select a P/N from the database, enter an exact S/N or narrow the period. Read the original event and its source references together.
- P/N dropdown and exact S/N search
- Calendar or typed date range
- Readable records and PDF / CSV exports
Removal Statistics
See where recorded removals concentrate.
Compare aircraft rankings, P/N distributions and monthly activity. A collapsible chart below the tables can open in a larger view.
- Aircraft ranking and P/N Pareto
- Monthly views and aircraft × P/N
- Selected events and statistical exports
Component history & precise selection
The record stays
close to the finding.
A removal count becomes more useful when the engineer can inspect the events behind it.
The maintenance database retains removal and installation events separately. Imported history may be incomplete, and an event in the same period does not establish a causal relationship.
Part and serial lookup
Choose from the available P/N list. Enter the exact S/N, preserving leading zeros, to follow a specific component’s documented history.
A period that stays visible
Choose dates from the calendar or enter them directly. The selected endpoints are included, and the active selection remains visible alongside the results.
Original records and clear exports
Open the readable event, maintenance text and source references. Export the selected history or statistical view as PDF or CSV for further review.
Explore a synthetic example
A closer look
at the removal history.
Try the filters on an invented six-month dataset. The totals, charts and CSV all refer to the same demonstration records.
Recorded removals94
Aircraft involved7
Part numbers5
Recorded removals by aircraft
Counts describe recorded events. They are not reliability rates or a recommendation for stock quantities. The website filters synthetic records and performs no aircraft health analysis.
View sample records
| Date | Aircraft | P/N | S/N | Reason |
|---|
Analysis first / Consultation afterward
Results that the engineer
can follow back to the evidence.
The Agent presents the existing analysis. Detailed diagnostic investigation remains available in the Engineering Workspace.
Load the inputs
Import SAR/XSAR recordings, AIRMAN fault events and component maintenance history.
Run the assessment
The established deterministic engine produces the findings and priorities.
Review in context
Consult the Agent, inspect the sources and open the Workspace for detailed engineering review.
Prepare the report
Review the conclusions, operator notes and maintenance references before sharing the PDF.
Reporting & continuity
The review continues
beyond the dashboard.
Fleet and aircraft reports bring the engineering conclusion together with the evidence needed for technical follow-up.
Structured engineering reports
Review aircraft status, prioritised findings, AIRMAN/SAR context, component trends and source traceability. Operator notes preserve the additional context supplied by the engineer.
Saved runs and Workspace access
Save a run and restore compatible saved results without repeating MAT analysis. Open the Engineering Workspace from the Agent, with the opening status and elapsed time visible in both windows.
Engineering boundary. The tool supports engineering judgement. Approved maintenance data remains authoritative. Uncertain evidence stays visible, and component history does not automatically override the flight-data assessment.
Project plan and development Gantt Dated planning snapshot · Rev05 · 18 October 2026
Development roadmap · updated 23 October 2026
Development phase completed. Next steps subject to customer approval.
The first development phase was completed on 23 October 2026, including maintenance-record reconciliation, aircraft and component-history checks, operating-data comparisons, regression tests and report reviews. The next milestone depends on the final customer’s go-ahead. Once authorised, the pilot software will proceed through digital code signing and the preparation of the customer trial.
23 October 2026 · Complete
Development and the planned technical verification activities are complete.
To be confirmed
Code signing and packaging will follow the final customer’s go-ahead.
To be confirmed
Trial dates, scope and final review will be agreed with the customer.
Status as of 23 October 2026. The first development phase and its technical checks are complete. No customer approval, signed pilot release or trial start is implied.
Project coordination: Francesco Rondinelli. The pilot will proceed only after customer authorisation. Dates remain to be agreed; engineering results do not replace approved maintenance instructions. Diagnostic rules remain deterministic.
Project status · 23 October 2026
Project development timeline
The first development phase was completed on 23 October 2026. Subsequent stages depend on final customer approval; no dates have yet been confirmed.
✓ Development complete◷ Trial pending approval
Activity and status
Aug 2026Sep 2026Oct 2026
SAR/XSAR analysis engine3 Aug 2026 – 25 Aug 2026 · Completed
Completed as part of the first development phase.
Dashboards, aircraft views and PDF reports26 Aug 2026 – 4 Sep 2026 · Completed
Completed as part of the first development phase.
AIRMAN/SAR correlation and diagnostics7 Sep 2026 – 28 Sep 2026 · Completed
Completed as part of the first development phase.
Maintenance history and removal analysis29 Sep 2026 – 17 Oct 2026 · Completed
Completed as part of the first development phase.
Reconciliation, regression and technical reviews18 Oct 2026 – 23 Oct 2026 · Completed
Completed as part of the first development phase.
◆ First development phase completed23 Oct 2026
Next stages · dates to be confirmed
Final customer approvalAwaiting customer decision
To be confirmed
Digital signing and pilot build preparationAfter approval
To be confirmed
Pilot trial startTo be agreed with the customer
To be confirmed
Observation period and final evaluationTo be agreed with the customer
To be confirmed
CompletedPending customer approval
Post-development stages are planned steps, not confirmed calendar commitments. The earlier tentative dates between November 2026 and February 2027 are no longer applicable.
View milestone register
| Milestone | Date | Status |
|---|---|---|
| First development phase | 23 Oct 2026 | Completed |
| Final customer approval | To be confirmed | Pending |
| Digital signing / pilot build | To be confirmed | Dependent on approval |
| Pilot trial start | To be confirmed | To be agreed |
| Final evaluation | To be confirmed | To be agreed |
Engineering collaboration
Discuss a system health
or maintenance-data project.
For a technical discussion about the tool, its workflow or a related engineering application, contact Francesco Rondinelli.