The purpose of AMTS is to reduce the labour required to track recurrent
maintenance requirements. In addition, AMTS reduces error by
providing consistent, timely information that further reduces the labour
required in tracing and rectifying errors.
AMTS is a "Component Based Tracking System."
Typically, an "Airframe based tracking system" will track maintenance
requirements for components listed for a specific airframe. While this
warrants well for up to two or three airframes, it is prone to errors and
inefficiency for operations maintaining more than a few airframes of similar
AMTS defines a component as "anything that requires a maintenance action" and
then treats all components in the same manner. This means that in the
same way you can track a specific engine located on a specific airframe, you
may also track a specific turbine wheel located on a specific engine.
When, in the above example, the engine is moved to a different airframe, it will
accrue hours, cycles, etc at a rate dependant upon the new airframe. With
traditional software, you would also need to change the location of every
component being tracked, that was attached to the engine. Since, with
AMTS, each component is located with the component it most likely travels with,
each of the engine's trackable components, including the turbine wheel, is
automatically associated with the new airframe when the engine is moved.
A Component is any object that requires recurrent or non-recurrent maintenance
to be monitored or recorded. Examples of Components are; airframes,
engines, turbine wheels, etc. Components can be "attached" to other
components so that they accrue hours/cycles at the same rate as the parent
component. Once a component is attached to a new parent, then it will
accrue hours/cycles at the rate as the new parent.
Note for advanced users - Components may be tracked separately (e.g. each
turbine wheel in an engine may be tracked by itself, accruing hours as the
engine accrues hours), or as part of a group (e.g. the engine hours are
tracked, and the turbine wheels are assumed to have the same hours as the
engine, and the replacement/inspection action for the turbine wheel is
attributed to the engine).
The Component Name is the name or number that normally specifies a specific
part. For example, "C-FABC" specifies a specific airframe. "123456"
might specify a specific engine (and may also be the engine's serial number).
The "Location" field tells Alto-AMTS where the Component is Located so that it
can update each component's log correctly. For example, if you have Engine
#123456 Located (or Attached) to Airframe "C-TEST", then when the log for
C-TEST is updated, then the log for Engine #123456 will be updated as well (as
well as any other Components that are attached to Engine #123456, and so
on). This relationship is referred to as a Parent/Child
relationship. "C-TEST" is the parent, and "#123456" is the child.
Note also that "#123456" might also be a parent to other child components.
Categories are used to help sort information in order to make useful reports.
Although you may use as many Categories as you wish, good examples to
start off with are, "Airframes", "Engines", and "Propellers" for fixed wing
The Sub Category further categorizes components to help sort information in
order to make useful reports. Examples of Sub Categories for the Category
"Airframe", could be "MU-2", "SW3", and "PA-32".
The Component Log is a report that lists all the events for a specific
Component. For example, the Component Log for airframe "C-FABC" would
show all the entries made to update the hours, cycles or torque events on that
Any maintenance that is performed on a component is called a Requirement.
A Requirement in AMTS contains such information as, Name (e.g. "100 hour
inspection"), AWD#, Service Bulletin, Recurrancy period, and any applicable
notes, such as the parts required.
Requirements can be either Recurrent or Life Limiting (once only).
A Record shows information about a Requirement for a specific Component.
Each Record will show when a Requirement is due on a Component and, when the
maintenance has been completed, when it was done.
Records contains information such as component name, date/hours/cycles
completed, date/hours/cycles next due and the Requirement.