When we talk about coding a plan, the term implies writing source code using some computer language. However, in DB Precision, there is no real programming involved.

DB Precision coding instead involves creating different items in the plan that are really just building blocks. There are different types of items that you can create. Examples include Service Definitions that allow you to measure service for people or Average Earnings Definitions that are used to calculate average earnings. The values for these items then get combined using formulas usually included in Formula Derived Items. Ultimately, these values are used in a Benefit Payment Set (see below).

Each building block that you create is a self-contained item called a Definition. Coding for that item involves choosing the correct combination of parameters displayed on different plan screens.

Values are ultimately extracted from DB Precision using Export Definitions which can be used to produce output such as benefit statements or benefit election forms.

A Benefit Payment Set is the highest-level item in the Plan Document. It is used to combine different building blocks in the document into a set of benefits payable under the plan. In the Benefit Payment Set, things such as vesting, early/late payment rules, and benefit formula are defined to define an entire set of benefits.

Each item created in the Plan Document is called a Definition. It has a name and a description. This name is used to reference that item in other parts of the plan such as within a formula.

Some types of items have a single set of rules while others have rules that can change over time. For items that can change over time, the rules for each period of time is called a Provision.

Every Provision has an Effective Date and can also have a Stop Date. Rules are effective for calculations between the Effective Date and Stop Date. If a Provision does not have a Stop Date, then the rules will apply forever into the future.

For items with Provisions, you will see one or more dates listed under the Definition within the plan where each date represents the Provision's effective date.