System Health Record "SHR©"

Connected Maintenance History

A unified health record for each Unit Under Test

The System Health Record (SHR©) provides a data integration solution for health state data across all levels of maintenance. It brings aircraft Built-In-Test (BIT) data, Automatic Test Equipment (ATE) results, and maintenance action data together for each Unit Under Test (UUT).

SHR stores, maps, and displays that information within one repository, connecting each UUT’s results and actions to its health history.

SHR brings together:

  • Aircraft Built-In-Test (BIT) data
  • Automatic Test Equipment (ATE) results
  • Maintenance action data for each UUT
  • Maintenance events and test results that build each UUT’s health history over time
  • Connections and trends across the UUT’s entire health history

How The Framework Works

How SHR connects maintenance data into one usable system history

SHR acquires, connects, processes, distributes, and manages health state data across all levels of maintenance.

By storing and mapping BIT data, ATE results, and maintenance action data together for each UUT, SHR establishes the connections and trends users need to make informed and efficient decisions using the UUT’s entire health history.

At a high level, SHR is designed to:

  • Acquire health state data across all levels of maintenance
  • Connect and process BIT data, ATE results, and maintenance action data for each UUT
  • Store, map, and display that data together within one repository
  • Distribute and manage the information so users can make informed and efficient decisions

Tell us how we can help you build a more connected maintenance history.

AI-Assisted Maintenance Investigation

Ask questions. Explore maintenance history. Review the supporting records.

GSS has integrated an AI assistant into SHR to help maintenance teams investigate available work order history, Built-In-Test (BIT) indications, and automatic test results through natural-language questions. The assistant retrieves relevant records and summarizes historical patterns, with references to supporting records and explanations of data limitations.

Explore maintenance history

Ask questions about a selected part number or unit to find relevant maintenance actions and test results.

Investigate recurring indications

Review repeated BIT codes and automatic test failures across available records to support further investigation.

Review supporting records

Follow record references to examine the information behind a response and understand gaps in the available history.

Why SHR Matters

A maintenance framework inspired by the success of healthcare records

Electronic Health Records proved that bringing fragmented events into one continuous history leads to better decisions, better outcomes, and better operational efficiency. SHR applies that same principle to aircraft and vehicle maintenance.

What healthcare established with EHR

Electronic Health Records created a secure, accessible patient history that could be referenced over time instead of recreated during every new interaction. That shift improved continuity, reduced guesswork, made care decisions more informed, and gave providers a more complete view of each patient across the full course of treatment.

Healthcare outcomes include:

  • Improved financial outcomes
  • Improved quality of care
  • Improved patient satisfaction
  • Reduced paperwork and saved documentation time

How GSS translates that model to maintenance

GSS created the System Health Record (SHR) to acquire, integrate, process, distribute, and manage health-state data across multiple levels of maintenance. SHR stores aircraft Built-In-Test data, Automatic Test Equipment (ATE) results, and maintenance actions for each UUT in one record that can be reviewed over the system’s entire history.

SHR enables maintenance teams to:

  • Track every maintenance event inside one persistent record
  • Connect diagnostics, test results, and technician observations contextually
  • Make decisions using the full operational and maintenance history
  • Share consistent health-state information across the enterprise