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 MEM20008A, 'Develop and implement a masterkey system'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Develop and implement a masterkey system' 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. Assess customer requirements | 1.1. Physical characteristics of existing locks and other security devices are considered and requirement for additional site inspection is determined. 1.2. Customer access and task requirements are discussed and clarified according to organisational procedures. 1.3. Customer requirements are evaluated with respect to current capacity, and recommendations are made for the design of new/expanded system. 1.4. Personal limitations in assessing requirements for masterkey system are identified and assistance is sought from appropriate person(s) in accordance with organisational procedures. |
2. Design masterkey system and system modifications | 2.1. Commercial masterkey system is designed to meet customer complex access requirements. 2.2. System is checked for interchange. 2.3. Principles and processes of masterkeying are applied in accordance with industry practice and organisational requirements. |
3. Finalise system design | 3.1. Final system design and keying requirements are reviewed and confirmed with appropriate person(s) in accordance with organisational requirements. 3.2. Documentation is prepared to allow for future interpretation and design requirements. 3.3. Documentation is accurately prepared and processed and stored in accordance with client, legislative and organisational requirements. |