|
() |
|
| 05.PR004 Preparation of an Acceptance Test Procedure |
1.1 Check Test Procedure Database
Check that a previously approved acceptance test procedure does not already exist in the Test Procedure Database. Even if a procedure does not exist for the specific item to be tested, a procedure for a similar item may exist that would serve as a valuable reference document for the remainder of this process. |
|
| |
1.2 Literature Search
Locate all sources of relevant information to be used when researching the functional requirements of the equipment. This should include (where available) product manuals, drawings and schematics. If insufficient information is available, the project technical lead should be consulted before proceeding. |
|
| |
1.3 Prepare Draft Functional Requirements Specification
Review identified information sources and prepare draft Functional Requirements Specification in accordance with the FRS template. |
|
| |
1.4 Obtain Functional Requirements Specification Approval
Obtain approval of the draft Functional Requirements Specification. This should be in accordance with the document control standard, from the appropriate approver as identified in the Functional Requirements Specification template and/or project plan. |
|
| |
1.5 Prepare Draft Acceptance Test Procedure
Prepare draft acceptance test procedure in accordance with the Acceptance Test Procedure Template. |
|
| |
1.6 Obtain Acceptance Test Procedure Approval
Obtain approval of the draft Acceptance Test Procedure This should be in accordance with the document control standard from the appropriate approver as identified in the Acceptance Test Procedure template and/or project plan. |
|
| |
1.7 Update Test Procedure Database
Update the Test Procedure Database with an entry to cover the new approved Acceptance Test Procedure for future use. |
|
| 11.PR001 Development of Metron Training Courses |
1.1 Need Identified
A need for a new online training course is identified.
The following information should be obtained:
-Training Course Name
-Client
-Author(s)
-Approver
-Due Date
|
|
| |
1.2 Setup folder structure
Setup training course folder structure using the following layout:
>{Ref#} - {Course name}
>>Build Notes
>>Completed Course
>>>v1 etc...
>>Flash Pages
>>>v1 etc...
>>Images
>>>v1 etc...
>>>>page1 etc...
>>Reference Material
The reference number should be obtained from the Metron Training Course Register
|
|
| |
2.1 Obtain technical training course information
Complete section 2 and 3 of the build notes template with relevant course information such as objectives, voiceover text, graphics and any developer notes to assist the Graphic and Multimedia Developer in creating the training course. |
|
| |
2.2 Obtain build notes approval
Review build notes to ensure they fit the training course purpose and requirements.
|
|
| |
2.3 Review build notes
Review the approved build notes prior to creation of the training course for any design or content aspects that require further clarification from the author. |
|
| |
3.2 Create slide animations
Create the slide animations using the build notes, saving each animation in the following naming convention: {page_X}
Graphics and photos used in Metron training courses should either be owned/created by Metron or be royalty free. These images should be stored in both raw format (.ai, .ps etc.) and exported format (.jpg, .png etc.) by individual page folders depending on which page they are for. |
|
| |
4.2 Upload training course contents
Upload the SCORM package to the training course page on the LMS and add both the author and the approver as "learners" of the training course. See notes for setting completion criteria.
Quiz:
Set the completion criteria by ""pass grade""
Presentation:
Set completion criteria by ""Passed/Completed"" |
|
| |
4.3 Upload supporting reference material
If reference material has been supplied, this should be uploaded to the LMS training course page.
|
|
| |
4.4 Review training course
Review the training course page ensuring the training course matches with the approved build notes and training course requirements.
Go to 3.1 if design changes are required.
Go to 2.1 if content changes are required. |
|
| |
4.5 Obtain training course approval
Review the training course to ensure the training course purpose and requirements have been achieved.
Go to 3.1 if design changes are required.
Go to 2.1 if content changes are required. |
|
| 13.PR001 Creating a Document / drawing |
1.1 Identify Need
Inputs to this process are 05.PR001 - Project delivery and 13.PR008 - IMS change management.
Identify the need for a new document or drawing. |
|
| |
2.1 Allocate Reference
Allocate a new document reference in accordance with the Company Document Control Standard and, if necessary, update the relevant Company Document Register.
For IMS documented information, refer to the IMS registers to obtain a new reference number.
The document status should be set as 'DRAFT'. |
|
| |
2.2 Create the Document
Create the document using the current approved document template. If in doubt, seek assistance from the Business Systems Manager. |
|
| |
3.1 Distribute for review
Distribute the document to the checker(s) for review. Provide any supporting documentation to allow the reviewer to verify the document content.
Checkers for document types are listed below:
INTEGRATED MANAGEMENT SYSTEM DOCUMENTS
Documents are to be checked and, if accepted, signed by the Manager responsible for the relevant business function. Where necessary the Manager should consult relevant staff members who may be impacted by the document.
PROJECT DOCUMENTS
Documents and drawings are to be checked by a member of the project team assigned to the project. Where necessary the checker should consult relevant staff members who may be impacted by the document.
The level of checking will be dependent on a number of factors including:
-Experience and competence of the author
-Complexity
-Project size
If necessary, the document content, layout and formatting should also be checked by someone other than the author.
ALL OTHER DOCUMENTS
Documents are to be checked and, if accepted, signed by the relevant departmental manager/director. Where necessary the reviewer should consult relevant staff members who may be impacted by the document. As well as reviewing the suitability and accuracy of the content, the reviewer should also be checking the spelling, grammar, formatting and presentation of the document |
|
| |
3.2 Review Document
Review the document and provide feedback to the Author on any amendments required.
If changes are required, proceed to 3.3
|
|
| |
3.3 Amend Document
Update document to incorporate checker's amendments. Return to 3.1 to resubmit changes for checking. |
|
| |
4.1 Set up a workflow request in Sharepoint
Approvals for documents are now performed via the embedded workflow processes within SHAREPOINT. If required, seek assistance from the Business Systems Manager.
Note - this approval process is for Operational /Project documents only. Refer to 5.0 for approval of IMS documents.
The required checkers are listed below:
PROJECT DOCUMENTS
Once checked, the document must be reviewed and approved by the project technical lead or the Director with responsibility for that area of the business (or the Managing Director).
The approver is making a final commercial assessment, considering whether the document meets the project or client's requirements, including any commercial considerations.
Depending on the requirements of the project, the Account Manager may be the approver.
ALL OTHER DOCUMENTS
Once checked the document must be reviewed and approved by the relevant business unit Director.
Using Workflow to approve documented information.
Note: Because Metron produces documents in high volume, within a fast paced delivery environment, it is recommended that once the document has been checked, it is verbally approved PRIOR to uploading the document to the workflow approval within SharePoint. This increases efficiency and multiple revision numbers. The Approver can still reject the document when in workflow, if deemed necessary.
Ensure revision number is X.0 prior to starting the workflow.
1. Upload the document to the relevant project site on Sharepoint.
2. 'Check in' the document to ensure it is deposited within Sharepoint.
3. Start a workflow
4. Complete the workflow information and the approvers will be notified by e-mail.
It may be necessary to provide supporting documentation to the approver. |
|
| |
4.2 If changes are still required, discuss with Author.
Suggest any changes if required.
If changes are required, revert to 4.1 as necessary.
|
|
| |
5.1 Use Document Approval forms for IMS documents
INTEGRATED MANAGEMENT SYSTEM DOCUMENTS
Once checked the document must be reviewed and approved by the person responsible for the Integrated Management System. This is currently the Business Services Director.
Complete the Document Approval Form 13.TM006. This will already have been used for the checking stage.
|
|
| |
5.2 If changes are required, discuss with Author.
Suggest any changes if required. If changes are required, discuss with Author and revert to 5.1. Re-checking may be required. |
|
| |
5.3 Upload Document Approval Form to Share
Approvals for IMS documents (processes, policies etc.), are stored in section 13 - Quality Assurance/Documents/Document Approval Forms.
It is recommended to attach the documents to the approval form.
Store in the format xx.xxxx- Approval - Rx.pdf
|
|
| |
5.4 Documents approved - Update registers.
IMS Documents
If this is part of an IMS Change Mangement process (13.PR008), ensure that this process is completed as required.
Link to IMS Change Management process - 13.PR008
Update the following IMS register as required:
|
|