Aviation Information Management

From Documents to Data

Barbara G. Kanki, Thomas L. Seamster, Thomas L. Seamster

• Publisher: Routledge
• Year: 2017
• ISBN:
  9781351956321
• Edition: 1
• Topic: Technologie et ingénierie
• Subtopic: Aviation

Operational information management is at a crossroads as it sheds the remaining vestiges of its paper-based processes and moves through the uncharted domain of electronic data processes. The final outcome is not yet in full focus, but real progress has been made in the transition to electronic documents providing the aviation industry with a clear direction. This book looks at a combination of industry initiatives and airline successes that point to the next steps that operators can take as they transition to fully integrated information management systems. Although the route has not been fully identified, it is evident that a key to successful long-term efficient information management is industry-wide cooperation. The chapters are authored by a range of experts in operational information management, and collectively, they outline ways that operators can improve efficiency across flight, ground and maintenance operations. Considerations and recommendations are identified and presented addressing the following priorities: Safety-critical information and procedures Human factors Information security Operational information standardization. The readership includes: Airline flight operations managers and standards personnel, Airline operating documents and publication specialists, Airline information managers, Commercial pilots, Airline maintenance managers and personnel, Manufacturers and vendors of aviation products, Aviation regulators and policy makers, Aviation researchers and developers of information technologies, and Military technical publications specialists.

Part 1
Structure of Aviation Operational Information

Chapter 2

Operator Document Systems: Structural Tradeoffs

Barbara G. Kanki and Ronald J. Thomas

Introduction

In this chapter we review the main factors that currently determine the structure of operator document systems. Industry, corporate and operational requirements provide the fundamental criteria on which document system decisions are made. Although current experience in developing and maintaining documents is largely paper-based, many high-level requirements (particularly those related to operational needs for safety- and time-critical information) pertain equally to electronic and paper-based document systems. Further, these requirements tend to call out the defining features unique to information systems in aviation operations. Information access and usability in complex, dynamic and high-risk operational environments often drive the structural tradeoff decisions that are the topic of this chapter. While the exact form of the tradeoffs changes dramatically when paper documents transition to electronic media, many key determining factors remain the same. In the following sections, we will identify the requirements and limitations that impact the development of operating document systems and discuss the evolution of structural tradeoffs as paper systems become electronic. In focusing on structural changes brought about by technology advances in information systems, we will leave the more general guidance for developing and maintaining document systems to other document design references (Adamski and Stahl, 1997; Degani and Wiener, 1994; FAA, 1994; FAA, 1995; NASA/FAA, 2000).

Developing Operating Document Systems

The operator who is developing a new document system, or reorganizing an existing system, should review the entire document system as well as the complete operating documents process. That process includes not only the planning and organization for the document system, but the design, review, production, maintenance and distribution of system manuals and publications. Each part of the process will affect the entire system (NASA/FAA, 2000, Section 1.1.1).

Figure 2.1 Operating Document Development Process as a System

The importance of clearly understanding and defining the three elements of document development as a system cannot be understated, and even at this conceptual level, one can anticipate how structural tradeoffs among system, document and production concerns can emerge. While safety-critical usability issues take precedence in some decisions, the elements must maintain a balance in order to function both smoothly and cost effectively. As an information management system that is dynamically changing, the development process is even more complex. Nevertheless, the obvious starting place is to identify the information requirements; those required through regulation, recommended by the industry, and established through corporate policy for operational purposes.

Regulatory Requirements and Guidance

The only requirements in the strict sense of the word are those required by law (e.g., the Federal Aviation Authority, The Civil Aviation Authorities). In the US, documents must contain information directly required by Federal Aviation Regulations (FARs). In addition to general requirements (e.g., FAR 121.131, 121.133, 121.135, 121.137, 121.139, 121.141, 121.315), numerous FARs contain specific information that must be included in an operation’s document system. Some FAR parts to review are FAR 21, 23, 25, 61, 91, 121 and 135 as applicable. One way to ensure you have all information required by these regulations is to use the National Aviation Safety Inspection Program (NASIP) Checklist (FAA, 1996). This is the document the FAA uses to ensure compliance with all applicable FARs or Advisory Circulars (ACs).

The Air Transportation Operations Inspector’s Handbook, 8400.10 (FAA, 1994), is used by the FAA to provide direction and guidance for certification, technical administration and surveillance of air carriers operating under FAR parts 121 and 135. As such, it also provides the operator with guidance on what the FAA is looking for. For instance, information on manuals is described in Volume 3, Chapter 15, Manuals, Procedures and Checklists. Operating specifications that are based on 8400.10 list the operations approved by the FAA. Some operators reproduce the complete operation specifications while others include only information that is pertinent to the flight crew.

Advisory Circulars (ACs) are additional sources of information applicable to operations. The title of the AC usually provides enough description to determine whether it is applicable and AC numbers start with the FAR part number they are associated with (e.g., 21, 91, 121). Finally, information contained in the Aeronautical Information Manual (AIM) (FAA, 2001a) and ATC Handbook (FAA, 2001b), while not required to be in manuals, may help clarify policies and procedures.

Supplier Information and Manuals

Suppliers, including manufacturers and other vendors, provide specific information on their products (aircraft, engines, individual systems, etc.) in flight manuals, operating manuals and flight training manuals. Operators should comply with supplier information and ensure that the resulting documents meet the needs of their user groups (see NASA/FAA, 2000, Section 2.1.2). For example, manufacturers provide basic information about the engineering of the aircraft and its subsystems, and the operator must ensure that information is compatible with their operational procedures and practices. FAR 121.141 allows a carrier to modify and create aircraft specific information to meet their operating requirements as long as it does not conflict with the manufacturer’s information.

Other chapters in this book (see Chapters 1, 4 and 5) discuss the importance of supplier-operator standards and provide more detail on how such standards should be developed.

Operator Best Practices and Corporate Philosophy

Researching the document systems of other operators is of great practical value in redesigning a document system or developing a document system for a new fleet. Through a complete review of the document system and working agreements of an operator similar to your own, best practices may be identified. Required information may be placed in many different locations, so it is important to review the entire document system and not just primary documents.

In addition to learning from the best practices of other operators, it is important to embed the corporate philosophies and policies that form the basis for your own procedures and practices. With procedures forming a significant proportion of operating manuals, an integral process for developing procedures in concert with corporate philosophies and policies is key. Philosophies and policies should address the characteristics of the operational environment, so they can be used to develop relevant and usable procedures. Operators should identify or develop a consistent, high-level philosophy stating how the operation is to function. From this, other philosophy statements may be developed to specify essential aspects of the operation. Philosophy should not be a compilation of generic statements, rather, it should highlight the unique and most positive aspects of the operation’s mission. Policies flow from philosophy and should be reviewed for consistency with other policies.

Organizing Criteria and Operational Priorities

Information Type Criteria

As information content is established, it must be organized into a document system that satisfies operational requirements when and where it is needed by various users. Because it is neither logical nor practical to place all required information into one document, grouping criteria which address the needs of your operation must be assessed in determining the contents of documents. Again, reviewing the document system of similar operators may help to identify primary groupings or information types. Useful information types include:

• Required in Flight.

• Aircraft Specific.

• Company Generic.

• Large Content.

• Route/Geographical.

• Phase of Flight.

These information types serve as practical grouping criteria. For example, information required in flight helps determine what must be included in the space- and time-constrained cockpit environment. The second information type, aircraft specific, may be used to determine how to separate information for each fleet in the operation. The Airplane Flight Manual (AFM) from the manufacturer will already contain a large portion of this information. Some operators use the manufacturer’s AFM unaltered while others modify and reorganize the contents to suit their operations. Just as it is logical to locate aircraft specific information in a separate manual, operator generic information can also be placed in its own manual. However, combining aircraft specific and corporate information into one manual may be convenient for the user if the resulting manual is not too large. When working with paper-based systems, if an information item has large content, a separate document may be advisable, as in the case of the Minimum Equipment List (MEL). When working with electronic documents, document size constraints are replaced with user interface considerations, including locating information and navigating between documents.

Information pertaining to the route of flight or certain geographic areas is another information type typically grouped together for efficient organization (e.g., departure, arrival and approach charts as well as station information). When the operational routing structure is limited, however, only a subset of information may be required in flight. As a final example of information type, phase of flight is an essential organizing criteria both within individual paper-based manuals and for the entire electronic document system (see Chapter 5). For instance, information such as take-off and landing performance data must be grouped on the basis of the phase of flight in which it is used. Phase of flight may also become one of the primary entities as operators convert information to electronic document systems (see Chapter 12).

Table 2.1 gives examples of several information types (see NASA/FAA, 2000, Section 1.4.1) that may result in grouping information in particular documents or locations bec...