This page (revision-19) was last changed on 26-Nov-2021 10:22 by jmyers

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
19 26-Nov-2021 10:22 6 KB jmyers to previous
18 26-Nov-2021 10:22 6 KB jmyers to previous | to last
17 26-Nov-2021 10:22 6 KB jmyers to previous | to last
16 26-Nov-2021 10:22 6 KB jmyers to previous | to last
15 26-Nov-2021 10:22 6 KB jmyers to previous | to last
14 26-Nov-2021 10:22 6 KB jmyers to previous | to last
13 26-Nov-2021 10:22 7 KB jmyers to previous | to last
12 26-Nov-2021 10:22 7 KB jmyers to previous | to last
11 26-Nov-2021 10:22 7 KB jmyers to previous | to last
10 26-Nov-2021 10:22 7 KB jmyers to previous | to last
9 26-Nov-2021 10:22 7 KB jmyers to previous | to last
8 26-Nov-2021 10:22 7 KB jmyers to previous | to last
7 26-Nov-2021 10:22 6 KB jmyers to previous | to last
6 26-Nov-2021 10:22 7 KB jmyers to previous | to last
5 26-Nov-2021 10:22 9 KB jmyers to previous | to last
4 26-Nov-2021 10:22 9 KB jmyers to previous | to last
3 26-Nov-2021 10:22 4 KB JEscott to previous | to last
2 26-Nov-2021 10:22 4 KB JEscott to previous | to last
1 26-Nov-2021 10:22 4 KB JEscott to last

Page References

Incoming links Outgoing links
LIFE AND WORK EVENT OE PROCESS FLOW
LIFE AND WORK EVENT OE PROCESS FLOW

Version management

Difference between version and

At line 1 removed 2 lines
[{TableOfContents }]
!!!LIFE AND WORK EVENT OE PROCESS FLOW
At line 9 changed 2 lines
!!Steps
!Step 1 - Life or Work Event is Recorded
!Step 1: Life or Work Event is recorded
At line 13 removed 2 lines
'Event Descriptions', not 'Event Types' are listed in alphabetical order for the employee to review and select the event that best describes their situation. If a URL was provided, the link will be available to the employee.
At line 17 changed 5 lines
If no proof of the event is required, the initial status is set to “Submitted”. If proof is requested, the status is set to “Pending Proof”. When the Benefit Administrator has reviewed the information, they may change the status to “Pending Info” or “Processed”. The status of the event will be changed to “Processed” once the Open Enrollment itself has been processed.
The employee can see a history of the events they have recorded via the Life And Work Event History tab.
!Step 2 - Record or Maintain Life / Work Events in IBEV
!Step 2: Record or Maintain Life / Work Events in IBEV
At line 24 removed 2 lines
New life or work events can be created here on behalf of the employee if necessary.
At line 28 changed one line
!Step 3 - Create Open Enrollment Record
!Step 3: Create Open Enrollment Record
At line 45 removed 2 lines
!Step 4: Employees Review Their Elections via WEBOEE.
The employee would then review their elections in [WEBOEE].
At line 48 removed one line
Using this form the employee may review their benefit election options in the Open Enrollment. The employee may make changes to their current enrollments, elect new coverages, update or remove recipients and upload documentation.
At line 50 changed one line
Once the employee has submitted all of the required information they are able to submit their elections.
!Step 4: Employees review their elections via WEBOEE.
The screen [WEBOEE] is a scroll view of the employee’s elections. Using this form the employee may review their benefit election options in the Open Enrollment. The employee may make changes to their current enrollments, elect new coverages, update or remove recipients and upload documentation.
At line 52 removed 4 lines
A workflow trigger may be defined to notify the Benefit Administrator that elections have been submitted and are ready for validating/processing.
For more information on [WEBOEE], please see "Step 3 - Employees Review Their Elections" in [Mass Open Enrollment Process Flow|MASS OE PROCESS FLOW#MASSOPENENROLLMENTPROCESSFLOW]
At line 57 removed one line
Once the employees have submitted their elections, the Benefit Administrator would then review, ensuring the required information has been received and approve the employee's benefit elections using [IBPOE].
At line 42 added 2 lines
Once the employees have submitted their elections, the Benefit Administrator would then review and approve the employee's benefit elections using [IBPOE].
At line 53 added 2 lines
!Step 6: Process Open Enrollment
The Benefit Administrator may process the employees’ elections using either [IBPOE] or [UBPOE].
At line 69 changed one line
If approvals have been defined for Open Enrollment, the approver would have to approve the open enrollment in [IBPOE].
!Step 7: Close Open Enrollment Period
After the elections have been processed, the Benefit Administrator must close the Open Enrollment period via [IBOE].
At line 71 removed 2 lines
Once approved, the Benefit Administrator would validate the data and then process the elections via [IBPOE].
For more information on processing the Open Enrollment, please see "Step 5 - Employees Review Their Elections" in [Mass Open Enrollment Process Flow|MASS OE PROCESS FLOW#MASSOPENENROLLMENTPROCESSFLOW].
At line 74 changed 2 lines
Step 6: Close Open Enrollment Period
After the elections have been processed, the Benefit Administrator must close the Open Enrollment period via [IBOE].
----
![Notes|Edit:Internal.LIFE+AND+WORK+EVENT+OE+PROCESS+FLOW]
[{InsertPage page='Internal.LIFE+AND+WORK+EVENT+OE+PROCESS+FLOW' default='Click to create a new notes page'}]
At line 77 removed 2 lines
!!HR Changes Creating Open Enrollments
HR changes entered in the system may trigger a Life or Work event and an Open Enrollment to be automatically created, based on workflow triggers.
At line 80 changed one line
For example, a new hire is entered in [IEQH] or someone gets married and the Married Date is entered in [IEPI]. These types of changes will create the event but the Open Enrollment period will only be created if the 'Allow Auto Open Enrollment' toggle is checked ON for their event types in [IBET] and there is a workflow action and UserCalc defined.
Life or Work Event Enrollment Process Flow
Step 1: Life or Work Event is recorded
An employee records a life or work event via the WEBEV screen.
Event Descriptions, not Event Types are listed in alphabetical order for the employee to review and select the event that best describes their situation. If a URL was provided, the link will be available to the employee.
If the employee wishes to create an event, they would click on the appropriate event and then press “I want to create this event”. A dialog appears requesting when the event took place and provides the employee with an option of adding comments.
If no proof of the event is required, the initial status is set to “Submitted”. If proof is requested, the status is set to “Pending Proof”. When the Benefit Administrator has reviewed the information, they may change the status to “Pending Info” or “Processed”. The status of the event will be changed to “Processed” once the Open Enrollment itself has been processed.
The employee can see a history of the events they have recorded via the Life And Work Event History tab.
At line 82 changed 4 lines
For further information on how one could set up a workflow to do this, please see the Workflow Starter Kit.
----
![Notes|Edit:Internal.LIFE AND WORK EVENT OE PROCESS FLOW]
[{InsertPage page='Internal.LIFE AND WORK EVENT OE PROCESS FLOW' default='Click to create a new notes page'}]
Step 2: Record or Maintain Life / Work Events in IBEV
IBEV provides a listing of all life and work events for all of the employees.
New life or work events can be created here on behalf of the employee if necessary.
If the Benefit Administrator is waiting for proof of the event, they may come in here to change the status of the event from ‘Submitted’ to ‘Pending Proof’. Once proof has been received, they would check the Proof Received toggle and then change the status to ‘Processed’. This status has no bearing on the open enrollment status or the elections.
Step 3: Create Open Enrollment Record
If proof is not required for the event, and if the Allow Auto Open Enrollment toggle in IBET is checked ON, then an Open Enrollment period is automatically created for the employee.
If proof is not required and the Allow Auto Open Enroll is not checked ON, then an OE period will not be automatically created.
If proof is required for the event, when the event is created in WEBEV / IBEV a message will be displayed stating proof is required. The event will still be recorded; however the Open Enrollment period will not be created even if Allow Auto Open Enroll is checked ON.
It is up to the Benefit Administrator to check the Proof Received toggle in IBEV once the proof has been received. Once this has been checked ON, the Create Open Enrollment button will be available to create the OE period for the employee.
If an employee records an event that took place in the past beyond the event’s number of days open, then a warning message is displayed to the employee. The event will still be recorded, however the OE period will not be. It is up to the discretion of the Benefit Administrator to manually create the OE period.
When the OE period is automatically created for a life / work event, the period is determined by adding the number of days open defined in IBET to the event date.
If no days have been specified in the Days Open field in IBET, then no date validation is performed.
Workflow actions may be defined to notify the Benefit Administrator when events are recorded and when proof is submitted. A workflow action may also be defined to notify employees when an Open Enrollment period is created.
Step 4: Employees review their elections via WEBOEE.
The employee would then review their elections in WEBOEE.
Once the employee has submitted all of the required information they are able to submit their elections.
A workflow trigger may be defined to notify the Benefit Administrator that elections have been submitted and are ready for validating/processing.
For more information on WEBOEE, please see Step 3 in the Mass Open Enrollment Process Flow section.
Step 5: Process Open Enrollment
The Benefit Administrator reviews the elections, ensuring the required information has been received.
If approvals have been defined for Open Enrollment, the approver would have to approve the open enrollment in IBPOE.
Once approved, the Benefit Administrator would validate the data and then process the elections via IBPOE.
For more information on processing the Open Enrollment, please see step 5 in the Mass Open Enrollment Process Flow section.
Step 6: Close Open Enrollment Period
After the elections have been processed, the Benefit Administrator must close the Open Enrollment period via IBOE.
At line 104 added 4 lines
HR Changes Creating Open Enrollments
HR changes entered in the system may trigger a Life or Work event and an Open Enrollment to be automatically created, based on workflow triggers. For example, a new hire is entered in IEQH or someone gets married and the Married Date is entered in IEPI. These types of changes will create the event but the Open Enrollment period will only be created if the Allow Auto Open Enrollment toggle is checked ON for their event types in IBET and there is a workflow action and usercalc defined. For further information on how one could set up a workflow to do this, please see the Workflow Starter Kit.
This page (revision-19) was last changed on 26-Nov-2021 10:22 by jmyersTop