Solved

# How can I organize this data [lots of variables and outcomes]

Posted on 2011-05-05
192 Views
Hello,

I have a algorithms for 13 different states on how to calculate insurance premiums.

For example, part of an algorithm for Nevada could be:

------------------
MANUAL PREMIUM [(Payroll / 100) * RATE]
+ Supplementary Disease [(SUBJECT PAYROLL / 100) * DISEASE RATE]
+Waiver of Subrogation factor [% applied to the portion of Total Manual Premium where waiver is applicable]
-----------------

That is just a small portion of an algorithm for a particular state.  Each line can be considered a "Premium Element".  The issue is that different states have differences in Premium Elements (i.e. TN will not have a Waiver of Subrogation factor).

The first thing I want to do, before even figuring out the best way to configure it, is compare the differences in premium elements for the various states.

Right now, I can manually look over the data for all 13 states and create 3 columns: Premium Elements, States that have it, and States that don't have it.  However, this seems very tedious and inefficient - there has to be a better way to at least present this data.

Any tips/suggestions would be appreciated!
0
Question by:Kenny537

LVL 29

Expert Comment

I see no reason to combine states' algorithms. Since the differences can be great or small, and doubtless can change on a whim, I'd keep 'em all separate.

If you have a compelling reason to share code between the states, I'd like to hear it.
0

Author Comment

Well I didn't mean to necessarily combine the code.  It's more for analysis reasons at this point.
For this type of insurance (worker's compensation), if the customer has employees in multiple states, the policy would still be applicable, however, the algorithms would be calculated differently based on the respective states (as I understand it).
But to consider combining the code or not combining the code is jumping ahead - right now I simply want to present the differences in the algorithms.

Does that make sense?
0

LVL 29

Accepted Solution

>>right now I simply want to present the differences in the algorithms.

If the sections of an algorithm are identifiable, then a column per section and a row per state sounds like a plan.
0

LVL 5

Assisted Solution

Kenny 537,

A small suggestion would be to dissect your algorithm into different cells that contain the same items.
hence you'll get 13 rows. From there, you can have an overview of what is the common/different params from each state and the end result should you have dynamic calculations coded in.
0

LVL 29

Expert Comment

Delete the question.
0

LVL 29

Expert Comment

Or not ;-)

No worries - glad to help.
0

## Featured Post

This is about my first experience with programming Arduino.
Whether you’re a college noob or a soon-to-be pro, these tips are sure to help you in your journey to becoming a programming ninja and stand out from the crowd.
This Micro Tutorial will demonstrate how to use a scrolling table in Microsoft Excel using the INDEX function.
In this fifth video of the Xpdf series, we discuss and demonstrate the PDFdetach utility, which is able to list and, more importantly, extract attachments that are embedded in PDF files. It does this via a command line interface, making it suitable …