ENGINEERING PROCEDURES HANDBOOK

by

Phillip A. Cloud

("p1

NOYES PUBLICATIONS
Westwood, New Jersey, U.S.A.

Copyright 0 1997 by Phillip A. Cloud No part of this book may be reproduced or utilized in any form o r by any means, electronic or mechanical, including photocopying, recording or by any informat i o n storage and retrieval system, without permission in writing f r o m the Publisher. Library of Congress Catalog Card Number: 97-26403 ISBN. 0-8155-1410-7 Printed in the United States Published in the United States of America by Noyes Publications 369 Fairview Avenue Westwood New Jersey 07675 10 9 8 7 6 5 4 3 2 1

Library of Congress Cataloging-in-Publication Data Cloud$ Phillip k Engineering procedures handbook / by Phillip k Cloud. p. an. Includes index. ISBN 0-8155-1410-7 1. Fngineering--Management. 2. Engineering--Documentation. I. Title. TA19O.C62 1997 651.5'0426--dc21 97-26403

CIP

ABOUT THE AUTHOR

Philip A. Cloud is a freelance writer with over forty years of industrial experience. He founded his own company in 1984, Cloud Publishing Co., specializing in hardware and software documentation with specific expertise in document development, release, change control, reproduction, and distribution. He has written over 25 administrative and technical manuals for industry.

Previously, he was Configuration Management Manager, Engineering Documentation Manager, and Drafting Manager. He has also been a Configuration Management Engineer, Technical Writer, Standards and Procedure Writer, Software Quality Engineer, Engineering Analyst, Design Engineer, Engineering Drafter, Tool Design Engineer, Validation Specialist. He has worked with corporation such as: Geneva Pharmaceuticals, Inc., Storage Technology Corp., Miniscribe Corp., Micro Motion, IBM (contract writer), Beech Aircraft Corp., The Boeing Co.,Gates-Lear Jet, and Cessna Aircraft Co. He has personally guided the development of the engineering documentation control process at several cargorations and has made significant Contributions toward improving the product release process at several other companies. He has implemented Material Requirement Planning systems as well as a variety of other projects in his field.

Notice
T o the best of the Publisher's knowledge the information contained in this publication is accurate; however,
the Publisher assumes no responisibility nor liability for errors or any consequences arising Itom the use of the information contained herein. F i n a l determination of suitability of any information, procedure, or product for use contemplated by any user, and the manner of that use, is the sole responsibility of the user. The book is intended for informational purposes only. The reader is wamed that caution must always be i t h products, or procedures which might be considered hazardous. Expert advice exercised when dealing w should be obtained at all times when implementation is being considered Mention of trade names or commercial products does not constitute endorsement or recommendation for use by the Publisher.

vi