Documentation Automation Work Group (DAWG)

Publishers must acquire branch approval for reprint or special print job before processing any reprints.

In most case the Status Accounting paragraph is not applicable for a SDR. However, there can be special cases when the SDR is making changes to the SSM and will require new status accounting information in the SDR and creation of LEM entries.

Notices for MTHB Page Changes releases interim changes or procedures to a Maintenance Handbook. A permanent change must be made to the applicable Maintenance Handbook prior to the one year expiration date of the notice.

A record of decision is a proposed change to a baseline configuration item. If a change is approved, a CCD directs the action required implementing the decision.

If you are reusing an SRM from a previous package you must get with the SRM coordinator so they can verify and update the SRM as needed.

There are two types of priority the originator can choose from in SCM: Routine and Blue Print Goal. Blue Print Goal packages should be moved to the publisher’s top priority.

Starting March 1, 2017, any packages still in the create state that is for interim guidance notice needs to use new template. The template is in SCM under templates current: notice_interim_page_change_6xxx_xx_n_dxxx.doc

In the Clearance Phase, technical documentation and modification kits (if applicable) are evaluated in the field. The Originator's Section Manager determines which documents require field testing.

To make page changes for corrections to a System Support Modification (SSM) that has been released use a System Documentation Release (SDR). SDRs are used to deliver limited-scope changes to previously issued System Support Directives (SSD).

Do not update DMS records, unless absolutely necessary; DMS records are linked to records in SCM and any modifications can alter the data in unexpected ways.