Setting Up JPAC
Once a subscription has been created, JPAC must be configured to match your organisation. This article describes the steps needed to get JPAC up and running.
JPAC is all about People and Compliance, but before you can enter data for your people or measure their compliance, there is some setup to do.
This is because each Person must be defined with a Role, an Employment Type and an Org Unit, therefore these need to be defined first. In the same way Requirements must be defined with a Requirement Type and a Category, so these also must be defined first. These form the structures used to "slice and dice" the data and are the basis for reporting on compliance.
Follow the links below to see how to add data to each resource. A csv import can be used for each of the resources below to load multiple pieces of data at once.
Groupings for People:
- Employment Types: cover the types of contract your people work under for your organisation under e.g. Full Time, Part Time, Casual, Contractor, Volunteer.
- Roles: cover the job titles for your people, e.g. Business Manager, Enrolled Nurse, Fitter and Turner, CEO, Support Worker, Store person.
- Org Units: will typically match your organisational structure, e.g. departments and sites, however they can also include projects, cases, or any other structure that you use to divide your people into groups. Org units support hierarchies, so you can create sub org units nested within other org units to match your org structure. Note: Org units do not have to be hierarchical, you can have all your org units without any nesting or a mix where some are nested hierarchies and other not.
Groupings for Requirements:
- Requirement Types: cover the types of requirements you expect your people to possess e.g. Training, Licenses, Qualifications, Checks.
- Categories: cover the other ways you categorise requirements e.g. Professional Development, Induction, Safety.
Other:
- Tags: are optional. They are a mechanism for grouping People or Requirements where the grouping doesn't fit neatly into any of the groupings you created above. One feature the tags have over the other groupings is that a tag can be linked to both People and Requirements.
People and Requirements
- Requirements: the competencies identified by your organisation as necessary for its people to have or to attain. These may include training, qualifications, experience, statutory checks and/or licenses.
- People: the resources in your organisation that JPAC is tracking compliance information about. They may be full time / part time employees, contractors / consultants, or even volunteers.
Assignments, Records and Attachments
- Assignments: requirements that can be set against people or aggregating resources (collections of people). Assignments are used to calculate the compliance of your team.
- Records: Documentation that provides evidence of a person's completion or attainment of a requirement.
- Attachments: Relevant files can be attached to a person. This can include photos, documentation of training, performance reviews, etc.
User Accounts
Other users can be created to manage the JPAC system.
Groups for User Accounts
Users can be organised into Groups to more easily manage permissions.
Permissions:
Permissions can be set against Users and/or Groups to manage the access Users have to each resource you've created.
Finding your way around
Once you've created the relevant resources above, read this article to help you find your way around the JPAC site.