|
Once we understand the objectives of a training course we can start to design a course with a logical flow from start to finish. This is often called the "Education Flow". To achieve a good education flow analyse what basic steps are required to take the delegate from start to finish. A decision will need to be as to which order those steps should occur to logically take the student through the subject matter in simple incremental steps. Information should be delivered in incremental steps to build in stages on the knowledge gained in previous sections. An example of this for a level 2 engineer product course would be as follows: 1. Generic Technology Theory Training Courses - Where appropriate training should be given on the generic technology on which the product is based. This should be targeted to cover all required elements of the technology needed for the following product training. Depending on the product line some customers are reluctant to send their personnel on this type of course as they think they already have the knowledge required, this however is not always the case. The generic technology elements which occur later in the training will act as a reminder of the key principles specific to the topic or configuration they are working on at that stage of the course. 2. Product and Technology Positioning - This should show the student how the product fits into the telecoms world. It should position products, protocols, services and technologies to enable the student to see how these fit together. This approach allows the student to understand the bigger picture so when troubleshooting or configuring a product they can identify other products with which they may be interacting and the type of interactions that will occur. 3. Hardware Description - A description of the physical elements of the product and its capabilities. 4. Basic Product Configuration - This should get the product up and running and get it to the point where services can be configured. This may include configuration file management, CLI or NMS connectivity and basic IP addressing. 5. Specific Generic Technology Theory. - The elements of generic technology theory that relate to the specific product or topic should be taught. This does not necessarily require the teaching of a complete course on each technology as long as the student understands the general overview of the topic and the specifics which relate to the product or topic being taught. This acts as a reminder for people who have taken the generic technology training and should relate directly to the product specifics they are currently working on. 6. Vendor Specific Technology Theory - All products include some proprietary technologies or vendor specific implementation of a standard which needs to be understood to enable a student to perform configuration and troubleshooting. 7. Configuration Principles - These are not configuration steps but configuration principles i.e. an understanding of the theory behind the configuration. 8. The configuration commands and steps 9. Configuration lab exercises 10. Troubleshooting Note: steps 4 - 9 may be repeated many times during the course, perhaps once for each topic. If students have a good understanding of the theory on which the product is designed then fault finding is a logical extension of their understanding of the product and protocols on which it is based. If all a student has is a recipe book of scripts to use they will not be capable of creating new configurations for themselves or even understanding what is happening when things start to go wrong. |