For teams responsible for operating and maintaining aviation infrastructure, maintenance documentation needs to keep pace with changes to the equipment it covers. In an October 2019 notice, the Federal Aviation Administration (FAA) outlined its intent to make a major revision to the RMLS maintenance handbook, the Maintenance Technical Handbook (MTHB) for the Remote Monitoring and Logging System. The notice sought field input to help align the handbook with equipment and maintenance changes introduced during the systemâs sustainment phase.
The document was a notice of intent, not the revised handbook itself. Its central message for Airway Transportation System Specialists and other affected offices was to provide specific recommendations grounded in operational and maintenance experience.
Why the RMLS maintenance handbook was due for revision
The FAA said the MTHB needed to reflect new RMLS components, equipment changes, and maintenance directives introduced with sustainment phase I, identified as SSM-RMLS-063. The notice specifically named National Logging Network (NLN) and National Remote Maintenance Monitoring (NRN) network database servers, storage, and application servers among the equipment involved.
It also stated that the new equipment was sized to accommodate new interfaces to RMLS. For maintenance documentation, that kind of change makes accurate equipment coverage important: procedures, checks, and schedules need to address the system configuration that technicians are expected to support. The notice did not provide the revised procedures; instead, it asked practitioners to help shape them through recommendations.
The background also cited Configuration Control Decision (CCD) N37005, titled âRemote Monitoring Logging System (RMLS) Technical Refresh.â This connected the planned handbook update to the technical refresh work described in the notice.
What operational teams were asked to contribute
The FAA requested input from personnel concerned with equipment operation, maintenance, or training. Recommendations could come from the recipientsâ own activities or other sources, but the notice emphasized that actual field experience should support suggested changes to existing requirements.
Requested areas included:
- Standards and tolerances
- Key inspection elements
- Daily performance check requirements
- Maintenance schedules and procedures
Recommendations were to be stated in specific terms. For example, rather than asking generally for an inspection procedure to be changed, a useful submission would identify the inspection element at issue and describe the proposed adjustment and the field experience behind it. The notice did not require contributors to use the handbookâs exact format; that formatting would be handled during the resolution process.
This approach placed emphasis on actionable technical feedback. For maintenance teams, documenting the operational context behind a recommendation can help reviewers understand how a proposed change relates to equipment use, inspection work, or maintenance practice.
How the FAA organized feedback
The notice assigned different collection and submission responsibilities to groups of offices. Atlantic, Pacific, Mid-States, and National Operational Control Centers; Data Repository Operations; Air Route Traffic Control Centers; Southern California TRACON; and Honolulu Center Radar Approach Control were directed to arrange for recommendations and submit them to the Remote Maintenance Systems Engineering Team (RMSET) by November 8, 2019.
Other offices not listed in that group were asked to collect, consolidate, and provide their input to RMSET by November 23, 2019. The notice cautioned that recommendations received after that date might be held for future revisions. It set a goal of distributing the revised handbook during the first quarter of fiscal year 2020.
For consolidating comments, recipients were directed to review a draft of Order JO 6140.17E and use the associated comments matrix. A separate instruction asked them to submit the completed matrix to the Office of Primary Responsibility, AJW-175, by November 1, 2019. The notice said there was no need to report deviations from standard order format, typographical errors, or common spelling mistakes, since the OPR would address those during review.
Practical considerations for maintenance documentation
Although the notice concerned a specific FAA handbook revision, its process offers a clear view of what makes technical-documentation feedback useful. Contributors were not asked simply to endorse or criticize the draft. They were asked to identify changes in defined maintenance topics and support those changes with experience.
For organizations preparing similar input, a disciplined review can help keep recommendations clear:
- Connect comments to equipment: Identify the relevant component, system element, or interface when possible.
- Describe the maintenance topic: Specify whether the comment concerns a standard, tolerance, inspection, performance check, schedule, or procedure.
- Explain the field basis: Include the operational or maintenance experience that supports the recommendation.
- Use the requested review process: Follow the designated matrix and submission route, while keeping comments focused on technical substance.
These points reflect the noticeâs instructions rather than additional requirements imposed by it. In particular, the FAA stated that recommendations did not need to match the handbookâs format, while asking that they be specific.
Conclusion
The 2019 FAA notice framed the RMLS MTHB revision as a response to sustainment-phase equipment and maintenance changes, including new server, storage, and application components and interfaces. It also made field experience central to the update process, requesting concrete recommendations on standards, inspections, daily checks, schedules, and procedures.
For technical decision-makers, the practical lesson is that maintenance documentation is most useful when it reflects the equipment configuration and the work performed in the field. Clear, specific feedback gives handbook reviewers a more actionable basis for aligning technical guidance with the system being maintained.
Access Official Technical PDF