Week 35


I. PRELIMINARY INFORMATION:


A. CLASS: Networking

B. TITLE OF UNIT: Networks and Networking

C. TITLE OF LESSON: Writing Formal Procedures

D. COMPETENCIES ADDRESSED: None

E. DATE & TIME:         

F. WEEK OF INSTRUCTION: 35

G. INSTRUCTOR: R Dorsey





II. OBJECTIVES:


A program manager once asked me if I had done any technical writing. I answered no and he responded with “you will now”. Boy did I ever have to write and write and write. You see, I was the only one in that company that knew the equipment at the time. These procedures I began writing essential were used to teach my replacement how to do my job. Talk about eating my lunch – SHEEEEESH


III. TEACHING METHODS AND TECHNIQUES:


Lecture

Other:       



IV. RESOURCES REQUIRED:


Other:      



V. INTRODUCTION:


This week is to be spent in the process of generating a final networking manual.



VI. CONTENT:


The process of creating a personal notebook that contains ones own reference information and tips that one has learned through experience is a very valuable aid to the technician.

This week is to be spent in the creation of formal procedures and technical tips for troubleshooting methods involved in the networking world.




VII. SUMMARY:


Paperwork is both the worst part of a technicians job and the best. It is essential to maintain an accurate and complete reference library of things such as cable pinouts, etc. It is also very nice to be able to recall a particular problem and how it was solved in the past.



VIII. ASSIGNMENTS:




IX. LESSON/COURSE EVALUATION:


     The evaluation for the various procedures comes in the form of self testing. The procedures are to be performed by other members of the class and not graded so much as redlined detailing the discrepancies between what has been written on the paper in the procedure and any steps or clarifications required to make the procedure doable.