Unit of competency Outline
Date retreived
23/07/2026 5:43 AM AWST
23/07/2026 5:43 AM AWST
Whilst all efforts are made to provide accurate and timely information from the relevant source/documentation, please be aware that the information supplied may not be the most current version. The accuracy of the detail has not been confirmed by the Department and therefore should not be relied upon without first confirming the contents.
Facilitate the use of planning software systems in a work area or team
Facilitate the use of planning software systems in a work area or team
Unit of competency
National Code
MSS404060A
MSS404060A
State Code
WD540
WD540
TGA Status
Replaced
Replaced
DTWD Status
Replaced
Replaced
State Implementation and Classification
Approved Date
24/10/2014
Field of Education
080317 - Quality Management
Original Release Date
24/10/2014
Nominal Hours
50
Description
This unit of competency covers the skills and knowledge required to facilitate the use of planning software in an organisation in a person’s work area or team. These systems are known by various generic names, such as Enterprise Resource Planning (ERP), Materials Resource Planning (MRPII, MRP III etc.) or by proprietary names.
Notes
Elements and Performance Criteria
1 Identify scope of planning software
- 1.1 Identify categories of information held by planning software
- 1.2 Identify information categories relevant to team and area processes
- 1.3 Identify range of information able to be provided to planning software by team or work group
- 1.4 Identify range of information able to be provided to team or work group by planning software
2 Communicate using the planning software system
- 2.1 Send and receive information using planning software
- 2.2 Send and receive messages using planning software
3 Make decisions using planning software
- 3.1 Interrogate the planning software system to find required current, historical or predicted information
- 3.2 Take actions appropriate to the information in accordance with procedures
4 Monitor the use of planning software
- 4.1 Routinely monitor planning software information
- 4.2 Review performance and use of planning software with team
5 Support others to use planning software
- 5.1 Regularly communicate with team or other work group members, both using planning software and face to face
- 5.2 Identify improvements required
- 5.3 Take appropriate actions to implement improvements
The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.
Competitive systems and practices
Competitive systems and practices may include, but are not limited to:
lean operations
agile operations
preventative and predictive maintenance approaches
monitoring and data gathering systems, such as Systems Control and Data Acquisition (SCADA) software, ERP systems, MRP and proprietary systems
statistical process control systems, including six sigma and three sigma
Just in Time (JIT), kanban and other pull-related operations control systems
supply, value, and demand chain monitoring and analysis
5S
continuous improvement (kaizen)
breakthrough improvement (kaizen blitz)
cause/effect diagrams
overall equipment effectiveness (OEE)
takt time
process mapping
problem solving
run charts
standard procedures
current reality tree
Competitive systems and practices should be interpreted so as to take into account:
the stage of implementation of competitive systems and practices
the size of the enterprise
the work organisation, culture, regulatory environment and the industry sector
Planning software
Planning software is a general term applied to a number of software systems which integrate a range of business information, such as:
sales/order taking
finance/accounting
logistics
maintenance
human resources
production
It is frequently referred to by names such as ERP or MRP/MRPII. In some cases it can be integrated with engineering applications, such as SCADA systems. In such cases the unit MSS402061A Use SCADA systems inoperations may also be required
Information and messages
Information and messages able to be sent and received via the planning software will vary between programs and organisations. This unit assumes that a range of discretion is available to the team leader over the information and messages that can be sent or received. Examples of information and message categories include:
orders
production/operations processes
scheduling (e.g. daily/weekly)
finance and accounting
human resources (e.g. rosters, reserves, training completed and scheduled)
quality requirements
customers
suppliers
Value stream
The value stream begins with the customer and includes all actions (both value-adding and non-value added) by both internal sections/departments and external organisations to meet a customer requirement.
Depending on the operations and the customer requirement stages where value stream actions may occur include:
sales outlet/representative
information gathering, data analysis and research
product design
raw material sourcing
intermediate processing
final assembler/collation/preparation
support services (e.g. accounting, finance and legal)
storage and delivery to customer
after market support
Competitive systems and practices
Competitive systems and practices may include, but are not limited to:
lean operations
agile operations
preventative and predictive maintenance approaches
monitoring and data gathering systems, such as Systems Control and Data Acquisition (SCADA) software, ERP systems, MRP and proprietary systems
statistical process control systems, including six sigma and three sigma
Just in Time (JIT), kanban and other pull-related operations control systems
supply, value, and demand chain monitoring and analysis
5S
continuous improvement (kaizen)
breakthrough improvement (kaizen blitz)
cause/effect diagrams
overall equipment effectiveness (OEE)
takt time
process mapping
problem solving
run charts
standard procedures
current reality tree
Competitive systems and practices should be interpreted so as to take into account:
the stage of implementation of competitive systems and practices
the size of the enterprise
the work organisation, culture, regulatory environment and the industry sector
Planning software
Planning software is a general term applied to a number of software systems which integrate a range of business information, such as:
sales/order taking
finance/accounting
logistics
maintenance
human resources
production
It is frequently referred to by names such as ERP or MRP/MRPII. In some cases it can be integrated with engineering applications, such as SCADA systems. In such cases the unit MSS402061A Use SCADA systems inoperations may also be required
Information and messages
Information and messages able to be sent and received via the planning software will vary between programs and organisations. This unit assumes that a range of discretion is available to the team leader over the information and messages that can be sent or received. Examples of information and message categories include:
orders
production/operations processes
scheduling (e.g. daily/weekly)
finance and accounting
human resources (e.g. rosters, reserves, training completed and scheduled)
quality requirements
customers
suppliers
Value stream
The value stream begins with the customer and includes all actions (both value-adding and non-value added) by both internal sections/departments and external organisations to meet a customer requirement.
Depending on the operations and the customer requirement stages where value stream actions may occur include:
sales outlet/representative
information gathering, data analysis and research
product design
raw material sourcing
intermediate processing
final assembler/collation/preparation
support services (e.g. accounting, finance and legal)
storage and delivery to customer
after market support
The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria, required skills and knowledge, range statement and the Assessment Guidelines for the Training Package.
Critical aspects for assessment and evidence required to demonstrate competency in this unit
A person who demonstrates competency in this unit must be able to provide evidence of the ability to:
identify team or work group area information requirements and relate to planning software categories
lead and motivate others in using planning software
ensure information sent to planning software is accurate and appropriate
obtain regular and one-off information from planning software
make decisions using planning software generated information.
Context of and specific resources for assessment
Assessment of performance must be undertaken in a workplace using or implementing one or more competitive systems and practices.
Access may be required to:
workplace procedures and plans relevant to work area
specifications and documentation relating to planned, currently being implemented, or implemented changes to work processes and procedures relevant to the assessee
documentation and information in relation to production, waste, overheads and hazard control/management
reports from supervisors/managers
case studies and scenarios to assess responses to contingencies.
Method of assessment
A holistic approach should be taken to the assessment.
Competence in this unit may be assessed by using a combination of the following to generate evidence:
demonstration in the workplace
workplace projects
suitable simulation
case studies/scenarios (particularly for assessment of contingencies, improvement scenarios, and so on)
targeted questioning
reports from supervisors, peers and colleagues (third-party reports)
portfolio of evidence.
In all cases it is expected that practical assessment will be combined with targeted questioning to assess underpinning knowledge.
Where applicable, reasonable adjustment must be made to work environments and training situations to accommodate ethnicity, age, gender, demographics and disability.
Guidance information for assessment
Assessment processes and techniques must be culturally appropriate and appropriate to the oracy, language and literacy capacity of the candidate and the work being performed.
Critical aspects for assessment and evidence required to demonstrate competency in this unit
A person who demonstrates competency in this unit must be able to provide evidence of the ability to:
identify team or work group area information requirements and relate to planning software categories
lead and motivate others in using planning software
ensure information sent to planning software is accurate and appropriate
obtain regular and one-off information from planning software
make decisions using planning software generated information.
Context of and specific resources for assessment
Assessment of performance must be undertaken in a workplace using or implementing one or more competitive systems and practices.
Access may be required to:
workplace procedures and plans relevant to work area
specifications and documentation relating to planned, currently being implemented, or implemented changes to work processes and procedures relevant to the assessee
documentation and information in relation to production, waste, overheads and hazard control/management
reports from supervisors/managers
case studies and scenarios to assess responses to contingencies.
Method of assessment
A holistic approach should be taken to the assessment.
Competence in this unit may be assessed by using a combination of the following to generate evidence:
demonstration in the workplace
workplace projects
suitable simulation
case studies/scenarios (particularly for assessment of contingencies, improvement scenarios, and so on)
targeted questioning
reports from supervisors, peers and colleagues (third-party reports)
portfolio of evidence.
In all cases it is expected that practical assessment will be combined with targeted questioning to assess underpinning knowledge.
Where applicable, reasonable adjustment must be made to work environments and training situations to accommodate ethnicity, age, gender, demographics and disability.
Guidance information for assessment
Assessment processes and techniques must be culturally appropriate and appropriate to the oracy, language and literacy capacity of the candidate and the work being performed.
Replaces
| State Code | National Code | Title | Type |
|---|---|---|---|
| W9008 | MSACMT460A | Facilitate the use of planning software systems in manufacturing | Unit of competency |
Replaced By
| State Code | National Code | Title | Type |
|---|---|---|---|
| BAK11 | MSS404060 | Facilitate the use of planning software systems in a work area or team | Unit of competency |