|
() |
|
| 05.PR002 BINDT Training Management |
2.2 Make sure students have adequate travel and support information
Travel and location information will be provided in the curriculum / course outline. However, to help ensure attendance and minimal disruption; Provide each student with dates of the course and travel directions to Metron’s site (our website has a map and directions).
Specific travel directions are provided for Train, Car, Bus and can be found on SharePoint .
If requested, download local transport timetables and send to students.
Local taxis can also be arranged if required. Advise students that Metron can assist with accommodation booking or recommendations, if required.
Advise students that the course will be classroom based.
Advise students on any potential safety concerns (such as site activities that may be ongoing at the time of the course), and that Metron can provide PPE, if required. Any prescription safety specs or similar should be brought by the student.
Advise students that Metron will provide all the necessary course notes,
training equipment and will have textbooks available for reference. However, advise students that they are welcome to bring their own texts though.
Advise students to contact the Project planner and controller, for any additional information.
Provide name, e-mail and phone contact details.
Advise students to bring photo ID (passport, driving license, student card etc.)
Advise students of the equipment to be used and whether they should bring any equipment.
|
|
| |
2.4 Course Enrolment
Enroll each allocated Student on the relevant course. Upon enrolment, joining instructions are to be sent to the email address supplied.
The requirements for courses are located on SharePoint and can be used as a reference through this process.
|
|
| |
3.3 Book training room
Book the training room for the duration of the course and send Outlook calendar invites to;
Course instructor (BINDT approved trainer)
Operations Manager
Business Systems Manager
Training Coordinator
|
|
| |
3.9 Check IT Facilities
Ensure the Business Systems Manager carries out the IT facilities check the day before the course is due to start. |
|
| 10.PR003 Information Systems Backup, Archive and Audit Management |
1.1 Update backup and archive schedule
Each service provided by the ISD should have a Risk Priority Number (RPN) assigned.
The schedule should be reviewed on an annual basis to reflect changing business needs.
If a significant change is made to the information systems such as new network drives, systems, VMs etc.. the schedule should be reviewed.
Depending on the RPN the information systems backup and archive schedule is updated to fit the business needs. |
|
| |
2.1 Configure backup software
Configure the network drives and VM backup software to automatically carry out backups ensuring the backup schedule is complied with.
The backup software should be configured to send email notifications with the status of the backup - success / failure. |
|
| |
2.2 Test configuration
Any new backup configurations should be checked for errors on completion of the first backup. |
|
| |
3.1 Archive network drives and VMs
Archives of the network drives and VMs should be carried out according to the backup and archive schedule. |
|
| |
4.1 Confirm backups and archives have been carried out
Login to the network drive and VM backup software to confirm backups and archives have been carried out according to the backup and archive schedule
go to 4.2 if the backups and archives have been carried out as expected.
go to 4.4 if the backups and archives have not been carried out as expected |
|
| |
4.4 Log non-conformities / improvement opportunities
Any failures should be logged.
This should capture and resolve any network drives / VM backup issues.
Once the conflicts have been resolved, manually run the backup/archive task.
Once complete go to 4.1. |
|
| 10.PR006 ISD Risk Management |
2.1 Identify ISD services
Identify, categorise and document services provided by the ISD. |
|
| |
2.2 Identify assets and support service items
Identify ISD assets and ISD support service items |
|
| |
3.1 Identify hazards
Identify hazards which may affect the network, connecting information technology and ISD provided services, such as security issues, physical issues etc.. |
|
| |
3.2 Identify failure effect
Identify the internal and external impacts these hazards will have on the business. |
|
| |
3.3 Identify severity
Identify the severity of the failure (SEV). |
|
| |
4.1 Identify cause of failure
Identify what could be the cause for the failure to happen. |
|
| |
4.2 Identify frequency of occurrence
Identify the frequency of the failure occurring (OCC).\ |
|
| |
5.1 Identify controls
Identify current preventive or mitigation actions to address each risk that is likely to occur. |
|
| |
5.2 Identify probability of detection
Identify the probability of the process controls detecting the failure (DET). |
|
| |
6.1 Prioritize risks
Prioritize the risks by calculating the risk priority number (RPN):
SEV x OCC x DET = RPN
The higher the RPN, the higher a priority the improvement activities will have. |
|
| |
7.1 Identify recommended actions
Identify further preventative or mitigation actions to reduce the likelihood of the risk occurring and limit its impact and the person responsible for implementing the action. |
|
| |
8.1 Implement recommended actions
Implement the identified recommended actions to reduce the likelihood of the risk |
|
| |
9.1 Document actions taken
Document the improvement activities taken to reduce the risk occurring |
|
| |
9.2 Identify probability of detection
Identify the probability of the new process controls detecting the failure (DET). |
|
| |
9.3 Review impact of improvement actions
Review the improvement activities by recalculating the risk priority number (RPN):
SEV x OCC x DET = RPN |
|
| |
10.1 Update controls and detection
Update the current preventive or mitigation actions to reflect the improvement activities now in place.
The RPN number should now match the post-improvements recalculated RPN number. |
|
| |
11.1 Re-assess FMEA
The FMEA should be re-assessed periodically to:
-ensure ISD services are up to date
-severity, occurrence and detection numbers are up to date. |
|
| 12.PR001 Create Software Release |
1.1 Confirm functionality of software release has been successfully tested.
|
|
| |
1.2 Create Release media.
This may be compiled code, files and instructions etc. It’s the media which someone would use to put this release live and should not rely on having access to R&D source code or resources. |
|
| |
1.3 Test install with Release media
|
|
| |
1.4 Test uninstall with release media
|
|
| |
2.1 Create & Use Software Release Checklist.
Use Software Release Creation Checklist Template. Follow this checklist |
|
| |
2.2 Create new revision number for this release.
See 12.PL001 Source Control & Revisioning Policy for details of revisioning system. |
|
| |
2.3 Update R&D Software Revisions Sharepoint List.
New entry with new revision number and description. |
|
| |
3.1 Create mandatory Release Notes document
Based on 12.TM029. |
|
| |
3.2 Create support documents are required
1st Line Support - use 12.TM030
2nd Line Support - use 12.TM031 |
|
| |
4.1 Confirm software project is checked into SVN.
|
|
| |
4.2 Create tag in SVN for this release
Reference the release revision number. |
|
| |
4.3 Create release folder in SVN for this release.
Referencing revision number, and with Documentation sub-folder. |
|
| |
4.4 Place Release media in SVN release folder
|
|
| |
4.5 Place Release documentation in SVN release documentation folder
|
|
| |
5.1 Inform ISD that release is available
ISD decide if / when to put the release live. |
|