Frequently Asked Questions

We know there are a lot of questions about how we can do the things you've seen on the site. We also know that a claimstaker might not appreciate a super-detailed technical explanation in the same way a network person might so, we provide the same answer tailored to different groups. 


How can a Benefits system work on "the cloud"?

Claimstaker: The fact is that in today's world more and more companies and even state and federal agencies are moving toward the cloud. We might even forget the concerns that used to be around with something that we wouldn't worry about at all today like "Internet Claims". 


All the same features are built into the Netacent Benefits System that are in your current system plus some real cool features that can only be accomplished on the web and specifically on the cloud. 

Benefits: Similar to the claimstaker answer, besides maybe how you sign on/in to the Data Station, you couldn't even tell that your system was on the cloud. It will look and feel the same as if it was housed on servers in your state. That fact that the servers where it is housed are in the cloud makes it more secure than in your state and, the could gives us the capability to scale up in times of high demand and scale down in times of low demand. It's pretty neat!

IT: Techncial mumble jumbo...

Administrators: How long would it take your state to decide if it needs a new server? Add on to that the time it takes to buy, ship, and install it and you've got a long time between the moment you realize you need more capicity and the moment you can add that capacity. Also, what happens when demand diminishes? Then you're stuck with another server that isn't being used. On the cloud, your system can react instantly to demand; it can scale up and scale down automatically based on actual use. 


How does the Test Suite work?

Claimstaker: The best way to understand how it works is to take a simple situation like that of a basic claim (one with no issue or problems on it). When that type of claim is filed, you expect it to be processed without any problem. What the test suite does is it takes the variables of that basic claim and the processes it over and over again to ensure that no changes made to the system ever mess up that basic claim.

Benefits: Take a basic Combined Wage Claim (CWC). When it is filed in your state and the claimant is requesting wages from another state you know that your system needs to send an IB4 Request to that state. We know what pieces of information that the ICON part of the system needs in order to generate and send that IB4 Request so we "write a test case" that has that information in it. We then run that test case through the same code that would do it in productioin and see what happens. If everything works correctly then we see that after the basic CWC was filed, the system would send an IB4 Request to the appropriate state. 

IT: Technical mumbo jumbo...

Administrators: We know what a situation looks like going into your system and we know what it looks like coming out of your system and we write test cases for as many of the situations as possible. All the test cases are continually ran to ensure that changes to the system never break anything in the system. Basically, if there is an issue and we don't have a test case for it one will be made and added to our test case list. In a way, we won't see the same mistake twice because if it is a mistake we'll address it with a test case that is run continually and we won't push any code that breaks any of the test cases.