Steps - You may right click and print this page as your process checklist
Step 1 - Meet with the DEQMS Team
Please contact the Defence Estate Quality Management System Team (DEQMS Team) to:
publish new information on the Defence Estate Management System (DEQMS);
amend information, upload new information/document(s) and/or delete information or documents on the DEQMS as per the agreed Version Control Process and/or;
add/update hyperlinks associated with your information.
The DEQMS Team will discuss your initial ideas and offer advice on the correct process to follow to make the DEQMS publishing process as efficient and user-friendly as possible.
Step 2 - Amend/Create the Process/Document as required using the DEQMS Style Guide Templates (Advice will be provided by the DEQMS Team).
achieve visual uniformity for business processes and business support tools published on the DEQMS intranet and internet sites
assist all Technical Authorities (TA), Subject Matter Experts (SME) and any personnel responsible for mapping business processes and/or drafting business tools for upload onto the DEQMS; and
Please note: Minor editorial updates to Business Process/Documents can be provided directly to the DEQMS Web Manager via email or alternatively, you can mark your changes on a hard copy and deliver to BP3-2-A068.
1. New Processes / Documents
For advice on drafting processes and/or documents for NEW processes/documents, the DEQMS Team provides advice on the standard DEQMS templates including;
2. Existing Processes / Documents
For advice on drafting processes and or/documents for EXISTING processes/documents, the DEQMS Team provides advice on how to:
update the process and/or documents using the following options:;
you can save off the documents, amend and send back to the DEQMS Team for re-loading;
you can copy and paste the contents of a page into MS Word and send updates to the DEQMS Team for re-loading;
you can printout the page and red pen minor updates and give to the DEQMS Team for re-loading;
develop alternative process mapping tools to enhance process user understanding (this includes flowcharts).
Web formatting will occur by the DEQMS Web Manager in line with the DEQMS Style Guide. Advice can be provided by the DEQMS Team.
Step 3 - Circulate the Process/Document for comment as appropriate
Consider internal distribution to:
personnel in the Infrastructure Division (where relevant);
appropriate DSRG Divisions; and
appropriate Groups and Services.
Please note – If the Process/Document impacts upon the operations of other Divisions or Groups, it is the responsibility of the Sponsor/TA/SME to source approvals from appropriate areas and involve them in reaching an optimal solution.
Step 4 - Incorporate feedback and obtain acceptance of the Process/Document Upon acceptance of the document content and intended purpose, the Sponsor/TA/SME should incorporate all feedback into the draft document.
Recirculate the draft document to relevant customers for final review
if possible, all key customers involved in drafting the content of the process/document should be included in the final review process (this includes internal customers potentially impacted by the process/ document).
Step 5 - Seek approval
The person responsible for publishing the content of the process/document should seek approval from the relevant Director and then (if required) from the relevant Branch Head(s).
Relevant Director
Branch Head(s)
Step 6 - Provide Process/Document to the DEQMS Team
Upon final approval, provide the document to the DEQMS Team via email. A Quality Assurance (QA) check will occur on templates useability if the DEQMS Team was not involved in the review process as per steps 3 to 5 above.
The DEQMS Team will provide assistance and advice.
DEQMS Team will conduct a QA check on template useability.
Please note - all relevant approval sought and obtained in the consultation process must be included in the email to the DEQMS Team.
Step 7 - DEQMS Web Manager will update in development
The document will be provided to the DEQMS Web Manager to update the Process/Document on the development site to reflect the changes identified in consultation with the relevant TA/SME. The Version Control Process will then apply for the document (including the requirement for annual content reviews) as per the DEQMS Review Schedule.
The TA/SME is emailed the development site link for checking and ongoing development by the DEQMS Web Manager.
The DEQMS Team will provide advice if applicable.
Step 8 - DEQMS Web Manager will liaise with sponsor and further develop until approved
Once the development site is complete and aligns with internal approvals, the DEQMS Team should receive final approval from the TA/SME.
The DEQMS Team liaises with the SME for minor changes to the development site.
The DEQMS Team liaises with the TA for major amendments to the development site.
Step 9 - DEQMS Team will update Verson Control
Understanding the importance of Version Control.
The DEQMS Team will:
update the Version Number as per Major or Minor change requirements. For example: Major changes for V2.1 will become V3; and Minor changes for V2.1 will become V2.2.
if a document is received a Version No and date should be added to the name and footer;
saves all TA/SME supporting information into the appropriate QMT folder in Objective.
Version Control Process
The agreed DEQMS Version Control Process (in conjunction with the DEQMS Review Schedule) enables the DEQMS Team to uphold Clause(s) 4, 4.1 4.2, 4.2.1, 4.2.2, 4.2.3 and 4.2.4 of the AS/NZ ISO 9001:2008 Quality Management Standard.
To support clause(s) 4.2 Documentation Requirements, and in particular clause(s) 4.2.3 Control of Documents and 4.2.4 Control of Records, the DEQMS team actions items 1 – 4 below:
Version numbers | details and control
The DEQMS Team will update the Version Number of any DEQMS document or web page as per Major or Minor change requirements (see Version Control – Sponsor Responsibilities).
For example, Major changes for Version 1.1 (document or DEQMS webpage content) will become V2 and Minor changes for Version 1.1 (document or DEQMS webpage content) will become V1.2.
If a new or revised document or MAJOR webpage content changes are sent to the DEQMS Team by a TA or SME , the following details should be noted in the footer (or body) of the word document or internal correspondence:
Version number | Creation date | SME name | TA name | Process Name | Author if different from the SME/TA | relevant OBJECTIVE Reference(s)
DEQMS Latest Updates page
The DEQMS Web Manager updates the DEQMS Latest Updatespage to track DEQMS content and document versions.
QMT records may note the relevant OBJECTIVE folder(s)/file(s) that contain document(s) versions, DEQMS content revisions and stakeholder correspondence (i.e. TA/SME supporting information).
Pending the complexity of updates and/or new processes, a dedicated QMT Task number will be raised with a corresponding OBJECTIVE folder
All TA/SME supporting information will be saved to the appropriate QMT OBJECTIVE folder to assist with future updates and continuous improvement of the content and processes published on DEQMS
Every published page on DEQMS should display a heading bar as per Figure 1.1. This heading bar assists the DEQMS team to meet documentation, record keeping and version control requirements as per Clause 4 (and sub-clauses 4.1, 4.2, 4.2.1, 4.2.2, 4.2.3 and 4.2.4) of the AS/NZ ISO9001:2008 Quality Management Standards.
Figure 1.1 – Banner Bar example on each DEQMS page
Version No: eg. 3.2 Issue Date: eg. Nov 12 Review Date: eg. April 13
Figure 1.1 defines the currency of each business process, tool and resource as it displays key dates, TA/SME details and trigger dates for internal reviews and validation processes undertaken by the DEQMS Team. Figure 1.1 - An explanation
Individual web pages within the DEQMS have a designated Sponsor.
The Sponsor is also referred to as the TA.
The SME is responsible for developing and maintaining published content within the DEQMS structure.
Fig 1.1 provides an example of required SME, TA details alongside version control information for each DEQMS page.
The Version Number
The version number will change when major changes and updates to content occur as the DEQMS Team will update the file number as per Major or Minor change requirements.
For example major changes for V1.1 will become V2; and Minor changes for V1.1 will become V1.2.
The Issue Date
The issue date defines the date any amendments were made.
The issue date will include minor and major changes made to both the content and the web related structure.
The Review Date
The review date aligns with the DEQMS Review Schedule as defined within the DEQMS Management area.
The DEQMS Review Schedule outlines the Compliance Review process as per AS/NZS ISO 9001:2008 management requirements.
The review process allows for the DEQMS processes and tools to be assessed against actual projects.
When you become a Sponsor for information published on DEQMS, you will be notified via email when your Review Date is due.
Once the Sponsor/TA/SME accepts the proposed Review Date, the DEQMS Team will arrange a meeting to discuss Major or Minor amendments.
In preparation for the review, the Sponsor/TA/SME is responsible for reviewing their published content for currency.
Step 10 - DEQMS Team will publish and notify sponsor that it's done
The DEQMS Team publishes changes to the live Intranet site and also to the Internet if required.
DEQMS Team informs TA/SME all changes are complete and published live
TA/SME inform all relevant business areas about changes and published documents
TA/SME to develop training if required for relevant users
DEQMS Web Manager references any new or existing processes/documents in the DEQMS on-line update.