1.	Overview
1.1.	Purpose
1.1.1.	The purpose of this Standard is to define the layout and presentation of Standards at Acme Widget Co., Inc., Esq., Etc.; to set the procedures for submitting, approving, and revising Standards; and to define the concept and procedures for a department to enforce a Standard.
1.2.	Terms
1.2.1.	Standard
1.2.1.1.	The term ‘Standard,’ when capitalized as a proper name, is to refer to a document describing a set standardized procedure in use or proposed for use at Acme.
1.2.2.	Outline
1.2.2.1.	The term ‘Outline,’ when used in this document, refers to a hierarchal ordering of paragraphs in a document.
1.2.3.	Level
1.2.3.1.	The term ‘Level,’ when used in this document, refers to the position a Line has in the Outline heierarchy.  Line 2 is in Level 1, while Line 1.2.4 is in Level 3.
1.2.4.	Line
1.2.4.1.	The term ‘Line,’ when capitalized as a proper name, refers to a single paragraph in the Outline.  Every Line has a unique number associated with it.
1.2.5.	Height
1.2.5.1.	The term ‘Height,’ when used in this document, refers to the relative position of Lines in the Outline.  For example; Line 1.2.5.1 is a lower Level than 1.2.4, 1.2.5 and 1.2.6.  It can be described as being ‘below’ 1.2.5, but not ‘below’ 1.2.4 or 1.2.6.
1.2.6.	Subline
1.2.6.1.	The term ‘Subline,’ when used in this document, refers to a Line that is below another.  To continue the example of 1.2.5.1, Line 1.2.5.1 is a Subline of 1.2.5, 1.2, and 1.  
1.2.7.	Addition
1.2.7.1.	The term ‘Addition,’ when used in this document, refers to inserting text that was not in a previous version.
1.2.8.	Removal
1.2.8.1.	The term ‘Removal,’ when used in this document, refers to deleting text from the document.
1.2.9.	Reverse
1.2.9.1.	The term ‘Reverse,’ when used in this document, refers to Adding text that was previously Removed.  This only refers to Adding the exact same text that was previously Removed.
1.2.10.	Change
1.2.10.1.	The term ‘Change,’ when used in this document, refers to Removing a section of text and Adding a different section of text, either to correct an error or alter the meaning of a Line.
1.2.11.	Changelog
1.2.11.1.	The term ‘Changelog,’ when used in this document, refers to a list of all changes made to this document after its creation.
1.2.12.	Acme
1.2.12.1.	The term ‘Acme,’ when used in this document outside of the ID label for Standards, refers to Acme Widget Co., Inc., Esq., Etc., headquartered in Anytown, USA.
1.2.13.	Enforcement
1.2.13.1.	The term ‘Enforcement,’ when used in this document, refers to the authority to make changes to a Standard, and to request compliance to a Standard.  Each Standard is separate, in that some standards may fall under the authority of one department for Enforcement, while other standards fall under the authority of a different department.
1.3.	Enforcement
1.3.1.	Enforcement for this standard has not been determined.
1.3.1.1.	As this Standard sets procedures for certain documents, it is suggested that Enforcement authority be granted to the officer or department in charge of Document Control.
2.	Format and Revision
2.1.	Outline
2.1.1.	The Standard will be composed in Decimal Outline format.
2.1.2.	Numbering
2.1.2.1.	The first level will use Times New Roman, Bold, 12-point type.
2.1.2.2.	The second and subsequent levels will use Times New Roman, Bold, 10-point type.
2.1.3.	Body
2.1.3.1.	The first level will be formatted in Times New Roman, Bold, 12-point type.
2.1.3.2.	The second level will be formatted in Times New Roman, Bold Italic, 10-point type.
2.1.3.3.	The third and subsequent levels will be formatted in Times New Roman, Normal, 10-point type.
2.1.4.	Indenting
2.1.4.1.	The first level will have an indent of 0.0 inches for the number and 0.1 inches for the text.
2.1.4.2.	Each subsequent level shall have the number indented 0.05 inches from the level above, and the body text indented 0.1 inches from the level above.
2.1.4.3.	The separator between the number and the body text will be a single space.
2.2.	Editing
2.2.1.	Additions
2.2.1.1.	Additions from the immediately previous version will be in blue text. ( example )
2.2.2.	Removals
2.2.2.1.	Removals from the immediately previous version will be in blue text and struck through with a single line. ( example )
2.2.2.2.	If an entire line is removed, in the version immediately after the removal, the line will be marked with [Line Removed].
2.2.2.2.1.	If a Line with Sublines below it is Removed, only the highest Level needs to be marked with [Line Removed].  The Sublines below a Removed line may be deleted from the document.
2.2.2.2.2.	The [Line Removed] tag will not be deleted on subsequent revisions, unless the original removal is being reversed, or the Line above the Removed line is Removed.  This is to ensure that a line number in a Standard always refers to only one rule over the life of the Standard
2.2.2.3.	No active Sublines are allowed below a Removed line.
2.2.3.	Changes
2.2.3.1.	Changes to existing text are handled by a Removal of the old text and an Addition of the new text. ( sample example )
2.2.3.2.	This method is also to be used for correcting typos and spelling errors.
2.3.	History
2.3.1.	A Changelog will be maintained at the end of the document, to track all alterations.
2.3.1.1.	The Changlog is not part of the Outline, and does not follow the Outline numbering.
2.3.1.2.	The Changlog will start with the Final Draft and its submission for approval.
2.3.1.3.	Each entry into the Changelog will provide the date of the change, the description of the alteration, and the name of the person responsible for the change.
2.3.1.3.1.	With the description of the edits in the Changelog, it would be possible to see the entire history of the Standard, and if required, reconstruct it into an earlier version.
2.3.1.4.	No alterations to the Changelog are permitted, with the exception of correcting errors in the change reporting.  Everything that is done to the Standard is to be kept as a part of the permanent record in the Changelog, including every typo.
2.4.	References
2.4.1.	If a Standard needs to reference a document other than itself, it should provide a description clear enough to locate the referenced document easily.
2.4.1.1.	For reference to other Standards, the Standard’s ID number and pertinent Line number should be sufficient.
2.4.1.2.	For reference to a file on the server, the complete path and file name should be provided so the file can be identified unambiguously.
2.5.	Headers and Footers
2.5.1.	Each page of a Standard should have the Standard Name and ID number in the header.
2.5.1.1.	The header text should use Times New Roman, Normal, 14-point type, center justified.
2.5.2.	Each page of a Standard should have ‘Page x of y’ in the footer.
2.5.2.1.	The footer text should use Times new Roman, Normal, 8-point type, center justified.
3.	Approval
3.1.	Proposal
3.1.1.	When a new Standard is being composed, it will be given an ID number, and will be known as ‘Proposed Standard Acme-xPS,’ where x is the assigned number, and PS is the suffix to indicate a Proposed Standard that has not yet been approved.
3.1.2.	The ID numbers are sequential in nature, and will not be duplicated.
3.1.3.	The Proposed Standard will also have a brief description placed before the ‘Proposed Standard’ title. 
3.1.4.	Until the document has reached the Final Draft phase, no Changelog is required, and the document may be edited freely, without using the formality of Additions or Removals.  The nature of the Standard cannot be changed; a Proposed Standard on Vision System interfaces cannot be rewritten into a Proposed Standard on Control Panel Wiring.
3.2.	Submission
3.2.1.	Once the Proposed Standard is ready for submission, the Changelog is started with the current date and ‘Final Draft’ as the change description.
3.2.1.1.	From this point forward, all changes must follow the formal procedure of Additions and Removals.
3.2.2.	The latest version of the document is submitted to the department or officer in charge of Enforcement for the category of the Proposed Standard for review.
3.2.2.1.	After review, the Proposed Standard could be Approved, Recommended for Revision, or Denied
3.3.	Approval
3.3.1.	If Approved, the ID is changed from ‘Proposed Standard Acme-xPS’ to ‘Standard Acme-x.’  This would be recorded in the Changelog as ‘Standard Approved.’
3.3.2.	If Recommended for Revision, there is no change to the ID, and a follow-up note is sent to the Proposed Standard’s author with the suggested revisions.  This would be recorded in the Changelog as ‘Recommended for Revision.’
3.3.3.	If Denied, the Enforcing department or officer would sent a note to the author explaining the reasons for Denial.  The Changelog would receive the dated entry ‘Standard Denied,’ the Proposed Standard’s ID number would be retired, and the book would be closed on the Denied Standard.
4.	Enforcement
4.1.	General
4.1.1.	Every Proposed Standard should be assigned to a department or officer who will be in charge of Enforcement.  This should be done as soon as feasible after the ID number is assigned.
4.1.2.	ID numbers are taken from the next available slot on the Master List
4.1.3.	Departments or officers with authority to Enforce Standards are to be referenced within Standards by position or department name, not by personal name.
4.2.	Restrictions on Approval
4.2.1.	The author of a Proposed Standard cannot be on the committee to approve a Standard he has drafted.
4.2.2.	If there is no one with the authority to Approve a Proposed Standard other than the author, it would fall to the author’s immediate supervisor to handle the Approval process.
4.3.	List of Standards
4.3.1.	A Master List of Standards should be maintained to allow tracking of the standards Proposed, Approved and Denied.
4.3.2.	Maintenance of the Master List would fall to the department or officer in charge of this Standard.
4.3.3.	All Approved Standards should be kept in digital storage on the Acme mainframe, and printouts of the appropriate Standards should be available in departments where those particular Standards would be used.

Changelog
4/18/2011
-	Final Draft; Eric Adler
4/192011
-	Added Line 4.1.3. Departments or officers with authority to Enforce Standards are to be referenced within Standards by position or department name, not by personal name.
-	Added Line 2.4. References
-	Added Line 2.4.1. If a Standard needs to reference a document other than itself, it should provide a description clear enough to locate the referenced document easily.
-	Added Line 2.4.1.1. For references to other Standards, the Standard’s ID number and pertinent Line number should be sufficient.
-	Added Line 2.4.1.2. For reference to a file on the server, the complete path and file name should be provided so the file can be identified unambiguously.
-	Edits by Eric Adler
4/19/2010
-	Added Line 2.5. ‘Headers and Footers
-	Added Line 2.5.1. Each page of a Standard should have the Standard Name and ID Number in the header
-	Added Line 2.5.1.1. The headed text should use Times New Roman, Normal, 14-point type, center justified.
-	Added Line 2.5.2. Each page of a Standard should have ‘Page x of y’ in the footer.
-	Added Line 2.5.2.1. The footer text should use Times New Roman, Normal, 8-point type, center justified. 
-	Line 1.2.3.1: Added text; Line 2 is in Level 1, while Line 1.2.4 is in Level 3.
-	Edits by Eric Adler