TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
> To adequately answer this question, you first need to know how many
> departments exist in the company.
>
> I'm assuming the following entities at a minimum are present:
>
> * Document Control
> * Engineering
> * Finance
> * Human Resources
> * Marketing
> * Purchasing
> * Quality Assurance
> * Receiving Inspection (not the same as Shipping and Receiving!)
> * Shipping and Receiving
> * Stockroom
>
> Each department is going to have its own special needs. Here's a
> barebones look:
>
> 1) Doc Control:
>
> How to get drawings, procedures and ECOs successfully processed.
> How to conduct Change Control Board (CCB) meetings and who should
> attend them.
> How to archive legacy documentation and test programs.
> How to add new product code categories to the part numbering system.
> How the part numbering and document numbering systems work.
>
> 2) Engineering
>
> How to develop and process test plans for new products.
> How to develop workmanship standards for the assembly, fab, test and
> production floors.
> How to develop programming standards for test programs written for
> internal use only.
> How to resolve Returned Material Authorization (RMA) problems.
>
> 3) Finance
>
> How to perform the accounts payable, accounts receivable and payroll
> functions.
> How to process capital expenditure requests from Engineering.
> How to reimburse customers who sent back defective product via the RMA
> route.
>
> 4) Human Resources
>
> How to develop and implement corporate personnel policies.
> How to administer corporate benefits plans to employees.
>
> 5) Marketing
>
> How to develop business plans to introduce new products.
>
> 6) Purchasing
>
> How to process approved purchase requests.
> How to return substandard goods failing to meet company standards for
> compliance.
>
> 7) Quality Assurance
>
> How to make sure outgoing product actually meets company testing
> standards.
> How to conduct sample process control (SPC) programs for the product
> lines to ensure compliance at all stages of the Manufacturing process.
>
> 8) Receiving Inspection
>
> How to inspect and test incoming parts and subassemblies for
> compliance with company standards (which can actually be more than a
> little complicated if you need to use a video inspection system to
> actually measure received goods, especially for incoming substrates
> and glass-and-titanium wafers).
>
> How to send incoming goods to the Stockroom.
>
> 9) Shipping and Receiving
>
> How to package and ship specific products to meet the customer's
> specific Receiving Inspection requirements.
> How to process and forward incoming shipments to Receiving Inspection.
> How to process shipping labels and bills of lading.
>
> 10) Stockroom
>
> How to process approved lots forwarded from Receiving Inspection.
> How to create production kits for use on the Assembly, Fab,
> Manufacturing and Test floors.
>
> I'm sure I'm leaving something out, but this will get most people
> moving in the right direction. :D
>
> And no, there's no reference books or style guides *yet* that
> specifically address how to write this type of documentation that I
> know of. Supposedly, there's a book on procedure writing out, but
> I've yet to read it.
>
> Just another one of those things I imagine tech comm programs at the
> university level don't yet cover. Most colleges don't have to deal
> with Manufacturing issues due to a lack of assembly lines being
> located on campus.
>
> I could be wrong, but I seriously doubt it. :D
> George
>
> -----Original Message-----
> From: Leslie Harmon [SMTP:Leslie -dot- Harmon -at- MCI -dot- COM]
> Sent: Wednesday, July 29, 1998 4:50 AM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: SOP (Standard Operating Procedures) Manual
>
> Hello listserv subscribers,
> I am developing a SOP (Standard Operating Procedures) manual on my
> current
> project for a telecommunications company. Can anyone point me to any
> content and style guidelines for this type of manual?
> [George Mena] snip
>
>
>
>
