Release 6.1 [In Development]

Overview

The following information provides the computation business rules.

Computation Trigger Business Rules

Computation occurs:

• On Save in Govern
• On Condition in the Batch Compute:
  • If modif stamp of detailed record different than detail record modif stamp
  • If force compute of components selected in the batch process
  • If roll forward to other years
• if MA Audit record is Finalized

Computation does not occur:

• If Parcel Inactive – MA Records are deleted when inactivated
• if Building inactive
• if Parcel Linking inactive
• if Building Linking inactive for the other linked buildings

History Only

• If the history only is set to true (-1 or 1), it will be skipped when the computation is done using the Batch Computation program.
• It will be ignored when a record is saved and computation will occur.

Parcel Linking

A parcel can receive values from other parcels or provide a portion of its value to others. Contrary to the VB6 version, we will only load the values provided by other parcels and it is assumed the parcels that are providing the values have been previously computed.
If possible, if the parcels to be loaded have a MA_MASTER.MODIF_STAMP set to NULL, we should be calling this compute (recursive call) for these parcels prior to complete this step. (to be verified)

IMPORTANT: A parcel cannot receive and provide a value at the same time. Parcels having the MA_MASTER.exclude_from_roll = <> 0 are providing values to other parcels and therefore they are not computed. However the modif stamps to all linked parcels are reset.

• MA_MASTER.exclude_from_roll = -1 – The parcel provides all types of values to other parcels
• MA_MASTER.exclude_from_roll = 1 – The parcel provides only a land value to other parcels (to be validated)
• MA_MASTER.exclude_from_roll = 2 – The parcel provides only a misc. and a building value to other parcels.

Troubleshooting of Computation Errors

In case of errors during the computation process (for example, parameters not configured), all the system columns will be set to 0 and no timestamp will be attached to the appraisal records. (verify if at detail level only?)

TIP: Setup the console

Rounding Business Rules

General Rounding Method

OpenForms uses the standard Microsoft XXX rounding methodology.
Full column precision for type and sized is used at the database level

Appraisal Rounding Parameters

The following parameters impact rounding at different levels:
Final Appraisal Values
MA Round Table [ma_round]

• Building, Land, Misc, Income, MRA [code = bldg., inc, land, misc, mra, sale]
• Total Property Value [code = appval]

General Tax Parameters

• Personal Property Round Total or Detail value

Linked Records

• MA_SITE.LK_LAND_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘land’) – (to be validated)
• MA_SITE.LK_LAND_AG_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘land’).
• MA_SITE.LK_MISC_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘misc’).
• MA_SITE.LK_BLDG_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘bldg’).
• MA_SITE. LK_INC_GRM_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘inc’).
• MA_SITE. LK_INC_DIR_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘inc’).
• MA_SITE. LK_MRA_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘mra’).
• MA_SITE.PP_LK_VALUE is rounded to 0 decimal.
• MA_SITE. LK_COMP_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘compval’).

MA Round Table [ma_round]

• Building Area
• Building Look-up Area
• Market Living Area [code = lareamk]

General Appraisal Parameters

• Quality Points number of digits
• Building Size
• Land? (verify)
• Drawing Area Code Rounding (deprecated in 6.1)

Field Level

• Column precision and size

 

See Also

• Roll Forward Business Rules 101-std-fea-011 / Mass Appraisal Business Rules 101-ma-brules and Modif Stamp Rules
• Mass Appraisal Batch Compute 101-ma-bp-002