Welcome to the ROCS Online Community
The Recruitment, Onboarding and Classification System (ROCS)is a new recruitment, hiring and onboarding tool, currently being implemented university-wide at Rutgers, The State University of New Jersey. Once implementation is complete, ROCS will serve as an integrated job-posting and application system, serving as a one-stop for individuals interested in employment in any facet at the university.
This blog was created to share information, tips and best practices with the Rutgers community members who work within the ROCS system. If you represent a business unit or hiring department within Rutgers and would like additional information about this new system, or would like to suggest content ideas for the blog, please contact the ROCS system administrator.
The Applicant Reviewer role has the ability to perform ‘Bulk Actions’ in ROCS. A Bulk Action gives the Applicant Reviewer the ability to move multiple applicants in the workflow at one time. However, there are several helpful tips when using the Bulk Actions feature.
In ROCS the orange ‘Take Action’ buttons transition a request from one user to the next.
There are several indicators that the request has been sent off successfully, and that the next user in line receives the request.
There has been a recent change to the ROCS posting process based on feedback received during ROCS training sessions. Departments currently working in ROCS will now only be responsible for creating a request on the Position Management Module (orange banner) of ROCS. The previous process was set up so the departmental initiator would have the task of returning to ROCS in order to create the posting request after a position description was approved by the UHR Consultant. However, the posting process will now be handled by an UHR Employment Coordinator.
In ROCS there will be a new workflow state titled UHR – Case Manager. When an ‘Authorizer 02’ submits a request they are now going to see the option ‘UHR Case Manager (move to UHR Case Manager)’ with the UHR Consultant Jim Venner automatically selected. Reference Image:
ROCS Tip: How to view all applicants who applied to a posting.
When reviewing an applicant pool in ROCS the system is set up to show only active applicants. This feature makes it easier for the applicant reviewer to manage an applicant pool with many candidates. However, when reviewing an applicant pool the user can change their search parameters to display every applicant who applied.
How far we’ve come! As we move towards university-wide implementation of the ROCS system for all full-time, regular Rutgers staff employees, we wanted to provide some information on the implementation timeline, as well as how the system is currently being used at the university.
Eventually this system will be extended to faculty hires as well as temporary employees. But as you can see from the below infographic, in just a short amount of time, ROCS has grown by leaps and bounds!
Starting on Friday, August 28th, 2015 the UHR ROCS team will be hosting ‘Open Work Lab Sessions’ in the computer lab in ASBII (http://rumaps.rutgers.edu/location/administrative-services-building-ii). These Open Work Sessions present an opportunity to get hands-on experience using the ROCS system, while one of our trainers assists you in entering position requests into ROCS. The UHR staff will help guide you through entering a CARF/SPTF, initiating a posting request, or starting a hiring proposal within the new system. Participants will have a chance to work on actual business unit, department or school recruitment and hiring needs while getting assistance from our system specialists.
The sessions will occur every Friday from 9:30 a.m. to 11:30 a.m. To register for an Open Work Lab Session, please follow this link https://hrapps.rutgers.edu/profdev/CatalogTree.aspx, select ‘Human Resources Development,’ and click on ‘ROCS Open Work Lab Session’. (If the page does not open – Click: http://ssl-vpn.rutgers.edu Enter your Rutgers credentials, then copy & paste: https://hrapps.rutgers.edu/profdev/ into the URL address.)