Staffing Standards for Aviation Safety Inspectors (2007) / Chapter Skim
Currently Skimming:
5 Conclusions and Recommendations
5 Conclusions and Recommendations
Pages 85-94
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 85... ...
In the following sections, we summarize our conclusions regarding the adequacy of current ASI staffing models, the potential afforded by models drawn from outside the FAA, and the merits of a completely new approach. Our specific recommendations follow each set of conclusions, and the final section provides an elaboration of our recommended approach.
|
From page 86... ...
The evidence of weaknesses was sufficient, however, to justify our recommendation that such a prior effort is essential. Evaluation of the ASI Staffing Models Conclusions In reviewing the two comprehensive models of ASI staffing demand -- the Automated Staffing Allocation Model (ASAM)
|
From page 87... ...
If the Flight Standards Service (AFS) were to continue to use the ASAM model without correcting the deficiencies, it would remain vulnerable to criticisms of the model's validity and suitability for supporting staffing decisions.
|
From page 88... ...
In particular, there is continuing uncertainty about future plans for the Manufacturing Inspection Management Information Subsystem and the Labor Distribution Reporting system. AIR management has told the committee that it is carefully weighing the effects of changes in FAA labor and services reporting, and it is taking action to ensure that the data needed to support its current approach to staffing are adequate.
|
From page 89... ...
While subtle, this distinction is important in the sense that an emphasis on preservation generally results in a more costly and less satisfactory end product than does starting afresh, especially when there are fundamental weaknesses in the initial structure -- as clearly there are here. Therefore, the development process should include the following phases: · Requirements definition, in which the questions that the ASI staffing model should address, data sources, and measures of effectiveness are specified; · Model specification, in which a high-level software architecture is defined, including basic data flows, algorithms, and data structures; · Model development, in which modern software engineering techniques and tools and an iterative development approach are utilized; and
|
From page 90... ...
As an example, routine tasks that have a long history of performance could most likely be modeled statistically, while new or modified tasks (like those associated with the Air Transportation Oversight System) , for which there are few historical data on work processes and task performance times, may require more detailed process modeling.
|
From page 91... ...
Cost. It was difficult for the committee to estimate the cost of designing, developing, operating, and maintaining an ASI staffing model with the information available to us, and the estimate presented here is based on assumptions about the modeling environment that may not be accurate.
|
From page 92... ...
and professionals experienced in developing and implementing staffing models and systems. The FAA could assemble such a team relying exclusively on FAA employees, or it could engage a contractor, providing FAA employees as SMEs on a part-time basis with the contractor serving in the primary model development role.
|
From page 93... ...
This will increase the likelihood that the resulting model will be easy to implement and that ASIs will become committed to the new system and be motivated to support it. Finally, as noted above, the FAA should address the human resource issues associated with changes to the ASI job and to AFS business processes before developing a new ASI staffing model.
|
From page 94... ...
Resources. The committee's sense is that past ASI staffing models required a commitment of resources for development, maintenance, and use beyond what AVS or AFS management was able or willing to provide.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.