A system plan is a collection of all of the ProAdmin entities needed to perform a specific type of calculation or a plan, where the calculation type is defined by key fields. Typically only one system plan will be needed to do a plan’s estimate and final calculations, but sometimes additional system plans will be required such special calculations such as annual benefit statements or early retirement window calculations. System plans are most commonly defined to be added to the Plan Repository to be used by ProAdmin Server or ProAdmin Online calculations.. The Plan Repository is the file that contains all of the plan rules for plans that can be accessed by the server. System Plans are also used in the Benefit Calculator when ProAdmin is in Calculator mode.

Name is the description by which this entry will be known. All characters are permissible including spaces.  

Plan Definitions allow you to select an entry from the Plan Definitions Library. This entry would be the plan rules that are to be executed when the Key Fields are met.

Census Specifications allows you to select an entry from the Census Specifications Library. This entry would be the census specifications that are to be executed when the Key Fields are met.

Projection Assumptions allows you to select an entry from the Projection Assumptions Library. This entry would be the projection assumptions that are to be executed when the Key Fields are met.

XML Database Linkage allows you to select an entry from the XML Database Linkage Library. This entry would be the XML database linkage that populates the Data Dictionary.  

Output Definitions allows you to select an entry from the Output Definitions Library. This entry would be the output expected from the calculation when the Key Fields are met.

Click on the Keys button to define the participants for whom these benefits and assumptions are applicable. These fields are what uniquely identify the system plan in your environment. The spreadsheet on the dialog box refers to a Key Number and allows any number of key numbers. The information to which these key numbers refer is defined as part of the Plan Repository. (Click on the Manage button under Repository File Maintenance and then select Keys… to see how the keys are defined.) The System Plan must include specifications for exactly the same number of keys as are defined in the Plan Repository. If there is a mismatch between the number of keys associated with the System Plan and the number of key fields required by the Repository, you will not be able to add this System Plan to the Plan Repository. The Keys spreadsheet has columns for the key number (which cannot be edited), an Operator and a Key Value.

The Operator column allows you to select one of three conditional operators: In, Not In, and Any:

Select In if you want to provide a finite list of valid values for which the calculation applies, such as plan or location values. If desired, and asterisk (*) can be used to represent “all values”.

Select NotIn if you would prefer to provide the list of finite values for which the calculation does not apply, such as locations for which separate System Plans have been defined.

Select Any if the key value is not relevant to the selection, so you want to do the calculation regardless of the value in the XML input document. This is equivalent to using the operator In with the value of asterisk (*).

Provide the list of included or excluded values in the Key Value column. If you have multiple entries, separate them with a forward slash (/).

For example, if, in the Plan Repository, Key Number 1 was defined as the contract number and Key Number 2 was defined as the location identifier; and the plan that you want to value with this System Plan is identified by contract number 12345 and location identifier 001 or 002; then the Keys spreadsheet would have two rows (for key numbers 1 and 2), the Operator value for both rows would be “In”, the Key Value for key number 1 would be “12345”, and the Key Value for key number 2 would be “001/002”.