We (Tibco) have an employee that went into the system to update the commuter benefit effective 3/1/17. The event appears to be correct, but when Patrick ran the billing invoice it appears the Vision plan reverted back to the plan that was in effect for 2016 and termed it out. This plan is no longer available for 2017. I have attached a print screen of the “view history” and the commuter event (see attached)
What could possibly have caused this?
I (Tibco) had to create an event for 1/1/2017 in order to add the 2017 vision base plan in his record.
- fomin.docx
- 303 kB
- screenshot-1.png
- 413 kB
- screenshot-2.png
- 41 kB
- screenshot-3.png
- 42 kB
Hi Michelle Parker -
Can you please advise which employee you're referring to? According to your screenshots there are two different employees, Anton Fomin and Justin Osborne.
Ray
Raymond Williams Both were given as examples of the same issue.
There was a termination date of 12/31/2016 in the plan. it was change to "NULL," when services ran it re-enrolled the EE's.
Janine
Janine Calendo how do I explain to client? Is it a system generated error? Can the issue be corrected so the records shows up in the way she is expecting it to?
I cannot explain as to why the system made that change. These things happen at times with the system with no explanation. If further is needed that would be a question to DEV
Can you please provide additional explanation for the issue presented by the client?
DEV - Satya Jenni and I are trying to figure out why this EE record has a termination on the vision plan. It looks like there was additional eligibility on the vision plan but not in 2017. The EE did just a QE which terminated the vision plan as never effective. Can you please help provide an explanation to the term?
Janine
Hello Jyoti Mayne
As per our discussion,these are the below observations we have found :-
1. VSP Vision plan is contingent on medicals plans in 2016.
Medical contingent plans on VSP vision >>
1.Cigna basic 90/70
2.Cigna buy up 100/80
3.Cigna CDHP
4.Cigna plus 100/50
2.VSP vision plan effective date is 1/1/2016 and termination date is 12/31/2016
3.On 2/6/2017 4.59.59 pm termination date was set to "null" for vsp vision plan.(EE name- anton fomis) at the same time VSP Base Vision Plan was terminated
4. In view history >> 2/6/2017 4.57.39 pm status got changed to" incomplete" to complete"
5.Multiple selection allowed is set to "No"
Also tried different scenarios for EE.
(This was also reviewed by shubhankar and jaideep)
Kind request to you to please look into this issue.Thank You!
-----------------------------------------------------------------------------------------------------------
Thank you for the update, I will advise Michelle Parker to let the client know the reason.
Janine
Hi Janine Calendo,
We are working on this and will update you once it is completed.
ok thank you
I need to get the client an answer. The system should not be going back to terminated plans and enforcing contingencies. Please advise asap
Hi Debbie Kulling,
Due to UND WT-8282 and WT-7785 priority issues, we couldn't work on this. We will update you once analysis is completed.
Cc: Satya, Jaideep Vinchurkar
We could not wait anymore. I went into the terminated vision plan and removed the contingency. We need to find out they the system was looking at terminated plan contingencies. I need to get the 3Cs on this for the client asap
Hi Debbie Kulling,
Please find below our analysis details below :
Customization :
Plan Name | Plan Start Date | Plan End date |
---|---|---|
Plan A | 01/01/2016 | 12/31/2016 |
Plan B | 01/01/2017 | Ongoing |
Initially, employee had elections in Plan A and Plan B as below :
Plan Name | Election Effective Date | Election Termination date |
---|---|---|
Plan A | 09/01/2016 | 12/31/2016 |
Plan B | 01/01/2017 | NULL |
On employee data change with retro date; say 09/01/2016, election in Plan A has been changed as 09/01/2016 to NULL and terminated Plan B election with 08/31/2016 (similar to termed as never effective). Here system is not considering termination date of Plan A and changing its election with term date NULL.
We will have code change so that system will consider termination date of a Plan A and will change its election as 09/01/2016 to 12/31/2016 only and will not affect election of Plan B.
Thanks and Regards,
Vinanti Yadav
CC :Jyoti Mayne
The change was done by a retro QE. The QE was effective 1/5/2017 Can you please map out the change that is going to be made to correct this issue. I want to make sure it is not going to impact other things.
Hi Debbie Kulling,
As you have removed contingency customization so this will not be occur in TIBCO.
We are working on reproducing and fixing this issue. We will update you on this.
Thanks and Regards,
:: Umesh Kadam
CC : Jyoti Mayne, Rashmita Dudhe
Hi Debbie Kulling,
We have tried to reproduce mentioned issue but is not reproduced at our end. We tried the same scenarios happened with 'Anton Fomin' as below :
- We added back same contingencies (which was removed later) on 'VSP Vision Plan' 2016 plan.
- Before going through QE mode his status was incomplete.
- Raised 'Commuter-Transit Benefit Updates' QE from employee login with date 2/6/2017
- As per QE effective date rule, he got QE mode with 03/01/2017 effective date
- Completed QE workflow from employee login by saving demographic page and enrolled in commuter plan.
- After finishing QE mode, his status changed from 'Incomplete' to 'Complete' in system. As shown in screenshot this was the change which terminated 'VSP Base Vision Plan' election and reinstated election in 'VSP Vision Plan'.
- But even after this change, his 'VSP Base Vision Plan' election didn't got 'Terminate as never effective' and also 2016 election didn't reinstated.
We also tried all other possible scenarios that could trigger this issue e.g. changing employee data from partner and company admin login etc.but still it was not reproducible.
Hi Prasad Pise, please help to reproduce this scenario and share details.
Thanks and Regards,
:: Umesh Kadam
CC : Jyoti Mayne, Prasad Pise, Rashmita Dudhe, Alankar Chavan
HI Alankar,
Could you please try to reproduce this issue and share your findings.
We will give a try to reproduce this at our end. This is in progress
Any update?
Hi Debbie Kulling,
We tried to reproduce mentioned issue but is not reproduced at our end.
We tried same scenario as of 'Anton Fomin' as below:
-We added back same contingencies(Which was removed) on 'VSP Vision plan 2016'
-Raised 'BCC admin changed' QE event and enrolled in "VSP Vision plan 2016" from 09/01/2016 -set termination date as 12/31/2016
-Raised 'Commuter-Transit Benefit Updates' QE and enrolled in "VSP Base Vision Plan" plan with date 01/01/2017 and set termination date as 08/31/2016
-As per QE effective date rule, he got QE mode with 03/01/2017 effective date
-Employee went through his QE enrollment modes - made few elections - made some EDS change.
-After finishing QE mode, his status changed from 'Incomplete' to 'Complete' in system (shown in employee's history)
-The 2016 election in VSP Vision plan 2016 remained active till 12/31/2016 - while his 2017 election in VSP Base Vision Plan remained ON from 01/01/2017
Through all the actions performed above - we never observed the termination date set as NULL with employee's 2016 plan election.
We will try to keep an eye on such scenarios in our daily testing - if we encounter with such scenario, we will notify the same with steps to reproduce the same
Please do let us know in case of you need any further help on this.
Thanks,
Jayshree
CC; Prasad Pise Rakesh Roy Alankar Chavan Jyoti Mayne Umesh Kadam Vinanti Yadav Sumeet.Kolge Satya
Hi Prasad Pise,
This issue is not reproducing from dev and QA side. Please find QA update above and update JIRA status.
Cc: Satya