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.
I agree, and it isn't really placed entirely on my shoulders. However, the
IT security person has never worked on a diagram of this type and doesn't
have a clear vision of what it should contain.
Sean
No offense, but this doesn't sound like the kind of a job that should be
placed entirely on the shoulders of a writer. I would expect it to be
guided by some sort of a network security expert, who would probably have
some idea how the finished diagram should look. Am I misunderstanding
something here?
SRH
> I've just been assigned the task of creating a network security access
> point
> diagram that displays all of the various access points and potential
> security risks to our corporate network. This is my first time creating a
> diagram of this type and I was hoping to locate something similar, as an
> example. Does anyone have any advice or suggestions?
PG&E Energy Trading and any other company referenced herein which uses the PG&E name or logo are not the same company as Pacific Gas and Electric Company, the California utility. These companies are not regulated by the California Public Utilities Commission, and customers do not have to buy products from these companies in order to continue to receive quality regulated services from the utility.
