曝光臺(tái) 注意防騙 網(wǎng)曝天貓店富美金盛家居專(zhuān)營(yíng)店坑蒙拐騙欺詐消費(fèi)者

In selecting the form of the procedure, consider the airline’s overall policy and approach to standardization. For example, some airlines place a greater emphasis on specific checklist items, and, consequently, that may be a good format to consider. Another airline may place greater emphasis on the flows and, for that airline, consider introducing a CRM element into the flows.
In a few cases, departing from an airline’s policy will actually improve crew performance. When an airline places an emphasis on a specific format but that format is heavily used at the needed point in time, then consider integrating the CRM procedure into another form.
Once the form and location are set, the content of the procedure needs to be developed. For the first pass, all that is required is a verbal description of the procedure with examples of the type of wording that should be considered. In the next step, actual prototypes are developed.

Refining CRM Procedures and Media
Preparing Prototypes of Procedures
At this point, the CRM procedure development team has a written description of the preliminary CRM procedures. However, clear examples or prototypes are needed to communicate those procedures to other parts of the organization. The prototypes are more than just a written description of the procedures; the development team should prepare mockups of the sample checklists, guides, or parts of manuals to clearly show what these procedures will look like.
Prototype development is an important part of the refining process, where the development team interacts with a range of users to determine the best form and content for the CRM procedures. This last step should be iterative, with the feedback from each review being incorporated into the design to achieve one or more CRM procedures that will be adopted by the users to improve performance.
What is required for this step is a paper prototype of the actual checklist, brief guide, QRH, or other form of CRM procedure (see Appendix I for Sample QRH and Briefing Guide). Even if the final form will be an electronic display, such as the electronic checklists, it is not necessary to develop the prototype in the final media unless it can be done relatively easily and efficiently. The prototype should reflect the content and format of the proposed CRM procedure and, in some cases may include alternative representations. Documentation for the prototype should also include an explanation of why the CRM procedure is being proposed and what performance problem is being addressed.
. When reviewing a prototype, ask reviewers to give feedback in whatever form they are comfortable with

Sample Prototype of Arrival Brief Procedure
The sample prototype does not have to be the finished product, but it does need to be presented in sufficient detail so that the development team can obtain meaningful feedback from instructor/evaluators and other important groups within the organization.
The following prototype was an earlier version of the Arrival Brief presented on page 3 of this Manual. In comparing the two, it can be see that a number of items were eventually added and the order of items to prioritize were changed. All of those changes were due to comments from those who had carefully reviewed the prototype. Encourage reviewers to mark directly on the prototype or generate a new example. In other words, give the reviewers freedom to provide feedback in whatever form they are most comfortable with.
　
中國(guó)航空網(wǎng) www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：Developing Advanced Crew Resource Management (ACRM) Training: A Training Manual(33)