Formats and tools
- Unit Description
- Reconstruct the unit from the xml and display it as an HTML page.
- Assessment Tool
- an assessor resource that builds a framework for writing an assessment tool
- Assessment Template
- generate a spreadsheet for marking this unit in a classroom environment. Put student names in the top row and check them off as they demonstrate competenece for each of the unit's elements and performance criteria.
- Assessment Matrix
- a slightly different format than the assessment template. A spreadsheet with unit names, elements and performance criteria in separate columns. Put assessment names in column headings to track which performance criteria each one covers. Good for ensuring that you've covered every one of the performance criteria with your assessment instrument (all assessement tools together).
- Wiki Markup
- mark up the unit in a wiki markup codes, ready to copy and paste into a wiki page. The output will work in most wikis but is designed to work particularly well as a Wikiversity learning project.
- Evidence Guide
- create an evidence guide for workplace assessment and RPL applicants
- Competency Mapping Template
- Unit of Competency Mapping – Information for Teachers/Assessors – Information for Learners. A template for developing assessments for a unit, which will help you to create valid, fair and reliable assessments for the unit, ready to give to trainers and students
- Observation Checklist
- create an observation checklist for workplace assessment and RPL applicants. This is similar to the evidence guide above, but a little shorter and friendlier on your printer. You will also need to create a seperate Assessor Marking Guide for guidelines on gathering evidence and a list of key points for each activity observed using the unit's range statement, required skills and evidence required (see the unit's html page for details)
- Self Assessment Survey
- A form for students to assess thier current skill levels against each of the unit's performance criteria. Cut and paste into a web document or print and distribute in hard copy.
- Moodle Outcomes
- Create a csv file of the unit's performance criteria to import into a moodle course as outcomes, ready to associate with each of your assignments. Here's a quick 'how to' for importing these into moodle 2.x
- Registered Training Organisations
- Trying to find someone to train or assess you? This link lists all the RTOs that are currently registered to deliver FPPSTM320A, 'Manage steam boiler startup'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Manage steam boiler startup' on fishpond.com.au. This online store has a huge range of books, pretty reasonable prices, free delivery in Australia *and* they give a small commission to ntisthis.com for every purchase, so go nuts :)
Elements and Performance Criteria
ELEMENT | PERFORMANCE CRITERIA |
1. Conduct pre-operational safety checks | 1.1. Pre-operational safety checks are conducted within Occupational Health and Safety (OHS) regulations, environmental and safe working requirements/practices, Standard Operating Procedures (SOP), and housekeeping requirements |
1.2. Plant status is confirmed by inspection, observations and other information | |
1.3. Potential work area hazards are identified, reported and prevention or control measures implemented | |
1.4. Work and output requirements are established | |
1.5. Pre-operational and safety checks are conducted | |
1.6. Isolations are removed | |
1.7. Availability of process supplies are confirmed | |
2. Conduct startup procedures | 2.1. Startup procedures are conducted within OHS regulations, environmental and safe working requirements/practices, SOP, and housekeeping requirements |
2.2. Pre-light conditions are established | |
2.3. Boiler condition during startup is monitored to detect abnormal conditions | |
2.4. Boiler is started and brought on-line | |
2.5. System and plant is observed for correct operational response | |
2.6. Deviations from required operating conditions are detected and corrective action undertaken to rectify | |
2.7. Responses to corrective actions are documented as required | |
2.8. Startup information is recorded and reported as required |