Multi-state maintenance of employee benefits data in a benefits administration domain model
In embodiments of the present invention improved capabilities are described for a human resource management platform that includes applications targeted to solve a variety of human resource and benefits administration management problems. Applications of the human resource management platform include business applications such as benefits administration that may provide a single solution for facilitating employee benefits management and organizational efficiencies through automation of benefit management functions, measurement of benefit provider effectiveness, and the like.
1. A method of maintaining employee benefits data in a benefits administration management domain model, comprising:
receiving a change related to an employee benefit;
calculating with a processor a first impact on portions of the domain model that include a first state of the employee benefit;
calculating with a processor a second impact on portions of the domain model that include a second state having a different effective date of the employee benefit than the first state, the portions of the domain model that include a second state comprising a pending delegate that is created on-demand when a pending change is processed, the pending change being handled by the pending delegate; and
updating the domain model so that the employee benefit is adjusted based on the first impact and the second impact, wherein the portions of the domain model that include a first state are accessed by a business application through a first execution thread that accesses the domain model only in a current state of the domain model and the portions of the domain model that include a second state are accessed by a business application through a second execution thread that accesses the domain model only in a pending state of the domain model, the second execution thread including an effective date of the pending delegate.
2. The method of claim 1 , wherein updating the domain model includes modifying a domain object representing the first state of the employee benefit.
3. The method of claim 1 , wherein updating the domain model includes modifying a domain object representing the second state of the employee benefit.
4. The method of claim 1 , wherein the change related to an employee benefit is a change in rules.
5. The method of claim 1 , wherein the change related to an employee benefit is a change in employee indicative data.
6. The method of claim 5 , wherein employee indicative data includes one or more of an employee residential address, an employee zip code, and a union membership.
7. The method of claim 1 , wherein the change related to an employee benefit is a newly declared event.
8. The method of claim 1 , wherein calculating the first impact and the second impact is based on the received change.
9. The method of claim 1 , wherein calculating the first impact and the second impact is based on the received change and at least one of the first state and the second state.
10. The method of claim 1 , wherein the second state is a pending state of a domain object.
11. The method of claim 10 , wherein the pending state is captured in a pending delegate.
12. The method of claim 1 , wherein the second state is accessible via an effective dated domain object.
13. The method of claim 1 , wherein the domain model comprises effective dated domain objects.
14. The method of claim 1 , wherein the first execution thread and the second execution thread are executed simultaneously.
15. The method of claim 1 , wherein the updated domain model comprises a domain object that represents at least one of the first state of the employee benefit and the second state of the employee benefit.
16. The method of claim 1 , wherein the received employee benefit-related change is selected from the list consisting of: rules change, employee indicative data, employee address, employee zip code, employee union membership, and a newly declared event.
17. The method of claim 1 , wherein the pending delegate concerning the employee benefit is visible only when an application specifically requests information concerning the pending delegate.
18. The method of claim 1 , wherein the domain model includes multiple execution threads of employee benefit data, each execution thread kept separate from all other execution threads.
19. The method of claim 1 , wherein the first execution thread and the second execution thread are executed sequentially.
20. The method of claim 1 , wherein the pending delegate automatically becomes the first state of the employee benefit on the effective date of the pending delegate.