101-ma-frm-099 #CAMA #MassAppraisal #valuehistory #101 #mafrm #ma #MA
CAMA Value History
Module Specification Overview, Configuration, Installation, OpenForms Reference, What’s New, R&D wiki, wiki Module Map
CAMA Value History is [ Discontinued ]
CAMA Value History
Module Specification Overview, Configuration, Installation, OpenForms Reference, What’s New, R&D wiki, wiki Module Map
CAMA Value History is [ Discontinued ]
CAMA Building Structural Elements (BSE)
Module Specification Overview, Configuration, Installation, OpenForms Reference, What’s New, R&D wiki, wiki Module Map
The Building Structural Elements
Overview
Doucmentation
Prerequisite Forms
Tooltip
Building Structural Elements and Features Icons
Inventory
Structural Element Name
Building Structural Elements Summary
Summary
Building Structural Elements Summary
Adjustments
Adding Building Structural Elements Values to MRA and Income Data Calculations
and Features (BSE) form maintains details on each structural element within the selected building. By default this form has two dividers, Inventory and Summary.
The Inventory divider lists the structural elements by description and code. The user selects codes and includes comments, as applicable, for the current building. The Summary tab displays totals for the building by area, value, and adjustments.
To access the Building Structural Elements form:
To view this information in pdf format, click on the following link:
UsrBuildingsBSE.pdf
The following forms are required:
A tooltip appears when you hover your mouse over the structural element name, as in the following screen shot.
Saving the BSE
Click the Save icon to save a new record or any modifications to an existing one.
The “ModifStamp” field is set to NULL for all properties that have the changed code. When using a Mass Appraisal function related to that code, the User is prompted with a message for saving the record, even if no changes were made.
Deleting BSE Records
Click the Delete icon to delete the current record. A confirmation message is displayed. Click Yes to continue.
The Inventory divider lists the structural elements that apply to the selected Model Code as defined in Govern Admin. The user can selected structural element codes for the structural elements, as applicable.
Site No.
Select the site number from the drop-down list (Table: MA_SITE). Refer to the Govern CAMA: General Information guide for details on defining site information.
Building Use Code:
Select the Building Use Code from the list box. See Mass Appraisal Building Use Validation Table on page for details (Table: VT_USR_BLDGUSE).
Model Code
Select the Building Model from the drop-down list. The structural element codes that apply to the selected model are displayed in the list (Table: VT_USR_MODEL).
Sub Model Code:
Select the Sub-model Code from the drop-down list. This is used for associating a secondary model with the building.
Actual Year Built (AYB):
Enter the year the building was constructed.
Effective Year Built (EYB):
In this optional field, enter the effective year that the building was built. For example, this can be used when the appraised quality and condition of the building are more typical of a building constructed in a different chronological year.
The depreciation is calculated by subtracting the Effective Year Built from the Depreciation Year entered on the Mass Appraisal General Parameters form and then taking the value for the number of years for the depreciation table selected on the Building Use Validation Codes form.
If the Effective Year Built field is left blank, the depreciation is calculated on the Actual Year Built.
The Structural Elements are listed by sequence number. By default, the column headings are Structural Element Name, Code,%, and Value.
Sequence Number
The sequence numbers are assigned to the structural elements in Govern Admin. The order is important in calculations if the value of one structural element is dependent on the value generated by another.
The short description of the structural element is displayed in this column.
Code
Scroll to the structural element that you want to update. When you mouse over an item, a dropdown list appears if you can add information. If required information is missing, when you click Save, the item is outlined in red and a red dot appears to the left of the icons at the top of the form.
Percentage (%)
This field is enabled as defined for the structural element by the administrator in Govern Admin. When you can enter a percentage value, the grid displays a different shade and the field is enabled.
For certain structural elements, multiple structural elements names may be displayed. It may be required that the total percentage value for these elements equal 100%. These elements are listed in order.
This is illustrated in the following scenario:
In this scenario, three values can be entered for the porch base of a building. For the current value, these are: 50% Screened Walls, 25% Solid Wall, and 25% Knee Wall with glass. In this case, the values must be equal to 100%.
However, in other cases it may not be important that 100% of the material or other property defined for the structural element is known.
If it is required that the percentage values equal 100% and they do not, an error message is displayed.
For some single structural elements, a percentage can be entered if the percentage field is enabled. According to the administrative setup, this percentage is applied on the computed rate or used for display purposes.
Value
After selecting the structural element codes, click Save to display the values for each structural element. The value is calculated by applying the value for the code, as defined in the Building Structural Element Validation Codes form, and any values defined by logical expressions, formulas or queries set up in the Additional Columns fields.
Additional Columns
The additional columns are used for entering additional details on the structural element. Up to three additional description and codes can be added, as well as comments, a percentage or a flat amount value, as defined on the Mass Appraisal General Parameters form and on the Building Structural Elements validation tables in Govern Admin. See page 5 and page 38 for details. Data entered in these columns are not used in calculating values unless they are logical expressions, formulas or queries and referred to by other fields.
The BSE Summary displays data for the building area, values, adjustments, and totals. With the exception of the Income and the Notes and Comments, fields, these values are automatically generated and cannot be modified from this form. However, you can select the Override option and override the Final Adjustment and Total Value.
The Summary values, Total Living Area, Total Perimeter, Total Base, Total Actual, Total Heated and Total Effective are taken from the Building Area divider of the Building Drawing form. The total is the sum of all area codes listed on the MA – Govern Sketch > Area Codes divider.
Parameter | Description | |||||||||||||||
Effective Rate | ||||||||||||||||
(also called Building Rate) | The Effective Rate is calculated from the rate entered on the Building Use validation code form and applied to either the selected area or to effective area, if no type is selected. This total is divided by the Effective Area. | |||||||||||||||
Area Type * Rate / Effective Area | ||||||||||||||||
Total Replacement Cost New (RCN) | The Total RCN is calculated for the building by multiplying the Quality Points from the Quality Points validation code form by the Effective Area; then by the Effective Rate; then by the Size Adjustment | |||||||||||||||
Quality Points * Effective Area * Effective Rate * Size Adjustment | ||||||||||||||||
Total Depreciation Percentage (Total Depr.%) | The Total Depreciation Percentage is calculated by totaling the values from all the applicable depreciation codes; these include the depreciation table selected for the Building Use Code as well as the applicable Building Structural Element Depreciation Codes, that are set up for user-defined criteria such as Economic or Functional Obsolescence or damage due to a fire or flood. | |||||||||||||||
The depreciation for the Building Use Code is based on a value, set up in the selected depreciation table, for the number of years between the Depreciation Year, entered on the Mass Appraisal General Parameters form and the Effective Year Built entered on the Building Drawing form. See the Mass Appraisal General Parameters section on page 5 for details. | ||||||||||||||||
The Building Structural Elements Depreciation Validation Codes are added, subtracted, multiplied or divided according to the value selected in the Operator field on the Validation Table form. | ||||||||||||||||
For example, | ||||||||||||||||
Number of Years + Functional Obsolescence + Fire Damage | ||||||||||||||||
Total Replacement Cost New Less Depreciation (RCNLD) | The Total RCNLD is calculated by subtracting the depreciation from the RCN value. | |||||||||||||||
RCN – DEPR |
Parameter | Description | ||||||||||||||||||
Quality Points | Total Quality Points assigned to the building as set up in the Quality Points validation codes form. | ||||||||||||||||||
Size Adjustments | To calculate the Building Size, the Building Size, entered for a standard building on the Size Adjustment Validation Codes form, is divided by the Effective Area of the selected building. This value is then multiplied by the Adjustment Ratio, entered on the same form. 1 is added and then the same Adjustment Ratio is subtracted from the total. | ||||||||||||||||||
If the final result is less than the Maximum Adjustment and greater than the Minimum Adjustment value entered on the Size Adjustment validation codes form, it is used for the size adjustment. Otherwise, the Minimum Adjustment or Maximum Adjustment value is used. | |||||||||||||||||||
Neighborhood Adjustment (NHBD Adj.) Total | The Neighborhood Adjustment is set up in the Mass Appraisal Neighborhood validation table form. Refer to the Mass Appraisal General Information guide for details. | ||||||||||||||||||
Site Adjustment Total | The Site Adjustment is taken from the Site Information form. Refer to the Mass Appraisal General Information guide for details. | ||||||||||||||||||
Override | If this option is selected, the user can enter a value in the Final Adjustment field in order to override the Total Value. | ||||||||||||||||||
Final Adjustment | This field is enabled if the Override option is selected. Enter a value. This is added to the Total Value (RCNLD + SITE ADJ. + NEIGH ADJ) | ||||||||||||||||||
Total Value | The Total Value is calculated by adding the Neighborhood Adjustment and the Site Adjustment to the RCNLD value. | ||||||||||||||||||
RCNLD + SITE ADJ. + NEIGH ADJ. | |||||||||||||||||||
Notes & Comments | Enter notes and comments in this field as applicable. | ||||||||||||||||||
You can add the building value to the MRA or the Income Data records. According to the method you are using, the value is added to the Property Information form. If you are using the Income (DIR) or Income (GRM) method, the value is added to the Income Data record. If you are using the Market Approach method, the value is added to the MRA form.
This Building Value is calculated as follows:
Total Building Value = RCNLD + Site Adjustment + Neighborhood Adjustment
Include in Income
Select the Include in Income option on the Summary divider to include the total building value from the Building Structural Elements and Features form in the income calculation.
When you select this option, the Income ID and Category dropdown list is enabled.
Income ID and Category
Select the Income ID and Category to which you want to add the total building value from the dropdown list.
You can override this value on the Mass Appraisal – Income Data form.
Include in MRA
Select the Include in MRA option on the Summary divider to include the total building value from the Building Structural Elements and Features form in the calculation for the selected MRA Model.
When you select this option, the MRA Model dropdown list is enabled.
MRA Model
Select the MRA model to which you want to add the total building value from the dropdown list.
Note: You can override this value on the Mass Appraisal – MRA form.
CAMA Mass Appraisal Module Installation
Specification Overview, Configuration, Installation, OpenForms Reference, What’s New, R&D wiki, wiki Module Map Last updated 2015-05-11 [under construction]
The following information is intended for technical personnel installing OpenForms. The source documents are on Microsoft Visual Studio so please contact R&D to make sure you have the latest information for troubleshooting.
OpenForms Setup Documents
CAMA Building Information
Module Specification Overview, Configuration, Installation, OpenForms Reference, What’s New, R&D wiki, wiki Module Map
A workflow is a series of predefined steps that make up a process. A Workflow can be used for any work process, from printing bills to completing end-of-year procedures. You can include batch processes, administrative procedures and reports. As these steps are often required to occur in a specific order, they can be set up in a queue, i.e. the order that they are required to occur or be completed. Each step in a Workflow can have tasks associated with them that will need to be defined with start and completion dates and times.
As is standard for Govern interfaces, lists are displayed on the left hand pane. As items are selected on the list the parameters and details are displayed in the central pane. Departments cannot be added in this interface, only their parameters can be modified.
Prior to creating a Category, the following are required:
NOTE: Due to the Workflow modules ability to generate unique alphanumeric keys, i.e. Applications, Numbers and Certificate ID’s, these numbers are stored as strings and not numerical values in (Table: USR_KEY_DYNAMIC), refer to the Appendix within this document for details regarding the USR_KEY _DYNAMIC table. |
The above are determined by the combinations of Kinds and Categories. In addition, the Kinds are also linked to an Account Receivable (A/R) Name and an Applicant Name.
Each Category will be linked to a Kind. In addition each Category can override the Application, Number, and Certificate ID’s.
When created, the Kind will generate a (Table: WM_KIND_<kind code>). The Category will create a (Table: WM_CATEGORY_<category code>). If requested, each table will also generate respective required Added Fields.
A/R parameters can be defined at any of the following levels:
A/R Class Default – Select the default A/R class that is linked to the department.
When defining permit numbers by department, when generating Applications, Permits, Certificates (CO & CC), Offenses, Workflows, Payment and Submission sequence numbers if you are. Otherwise, leave this field blank and enter the number on the Land Management Parameters form or the Permit Type Maintenance form as applicable.
Override Sequence – By default this option is not selected. This means that all sequence numbers for Applications, Permits, Certificates (CO & CC), Offenses, Workflows, Payment and Submission sequence numbers will follow a conventional numerical standard, i.e. starting from 1, with no prefix or padding with zeros.
When this option is selected, parameters will be displayed that will allow the modification and appearance of the following:
Prefix – Enter an alphanumeric string that will be appended at the beginning of a numerical sequence; e.g. entering ‘AMT’ will result in a numerical sequence that is always presented as follows AMT001, or AMT1234, and so on. Look under the Preview column to see a real-time example of your sequence.
Sequence (Start Number) – The value that is entered in this field will be incremented by 1. The resulting value is your starting sequence number; e.g. if 100 is entered, the next starting number is 101. Look under the Preview column to see a real-time example of your sequence.
Length – Enter the number of digits to use for the length of the sequence. This field will accept a numerical value from 1 – 12. When a value is entered, the numerical portion of the sequence number will be “padded” with zero’s from the left hand side.
Example
When the number entered in this Length field is “8”, and no additional sequence numbers are entered, the starting number displayed under the preview will be 00000001. Likewise, if “1000” is entered as a Start Number, and a Length of “8” is entered, the number that will be displayed will be 00001001
Preview – A preview of your sequence configuration is displayed under this column.
Application – This is the sequence format that will be applied to an Application number when it is generated.
Number – These parameters will modify the sequence format that will be applied to a generated Certificate number.
Certificate – Complete the parameters to modify the sequence format that will be applied to a Certificate number when it is generated.
Automatically Link Applicant Name – Select this option to automatically enter the property owner as the applicant when you create a new record, i.e. permit, license, bond, approval or offense. The applicant will appear on the Names tab of the applicable function.
NOTE: The Link A/R to Names option must be selected on the Accounts/Receivable General Parameters form if you are using this option. However, if the Link A/R to Names option is selected and this option is deselected, a message appears to notify the user to add the applicant name, manually. |
Automatically Link Owner Name – Select this option to automatically enter the property owner, on the Names tab, when you create a new permit, license, bond, approval or offense.
Automatically Link System ID’s – When creating a new Permit or Inspection, any Permits / Inspections, Hearings / Offenses, Workflow, Complaints/Request for Services/Grievances, Occupants, and Buildings record types already associated with the record, and displayed in the Dataset Treeview in Govern, can be linked when you click Automatically Link System IDs.
Display a Warning for a duplicate Type – T/C
Use the Activity Date to compute the Expiration Date from the Activities – Use activity date to compute the expiration date from the activities; when selected, the system will use the current activity start date to compute the expiration date for activities that use the expiration date automatic update (by adding “X” number of years, months or days).
Display all licenses issued to the Individual – Select this option to display all the licenses issued to the selected individual or company, when the user adds a reference name to a permit or license.
Inspection Territory – Select an inspection territory from the drop-down list.
Automatically Assign an Inspector – Select this option to automatically assign an inspector, when the inspection is generated from a System Activity.
NOTE: You can only assign an inspector to a Scheduled inspection. |
The inspector is assigned, by availability and by territory, on the Inspector’s Schedule form; i.e., the location of the requested inspection needs to be within the territory assigned to the inspector. Otherwise, if All Territories have been assigned or if an Inspector’s Schedule does not exist for the inspector, the inspector can work in any territory.
The inspector is automatically added to the Names tab of the permit or license that is associated with the inspection.
NOTE: The insp code must be present in (Table: VT_USR_PMNAME). |
Show Inactive Inspectors – When selected, this option allows the system to display inspectors that are designated as inactive.
Use Light Inspection Scheduling – This feature allows you to indicate scheduled times which bypass the system scheduling restrictions which prevent conflicts in date and time. This would be the electronic equivalent of a sticky note reminder with a manually written time on it.
You can set up fees for failed or incomplete inspections for a permit, workflow or offense. When you select one of the following options, the Reason Code and Fee Amount fields are automatically displayed. The fee is generated from the Inspections function in Govern. Refer to the Inspections guide for further details.
NOTE: You can select only one reason and apply only one amount, per department, for an incomplete or failed inspection. |
Generate Fee from Inspections – Select this option to set up a fee for an incomplete or failed inspection for an offense. Then, select a reason for charging the fee from the Reason Code field and enter an amount in the Fee Amount field.
Reason code – When an inspection is deemed incomplete or failed, a reason code may be required; select one from the combo box.
Fee Amount – Incomplete or failed inspections may have a fee associated with them. When this is the case, select the fee that is to be associated with it from the combo box.
Display a Warning for Unlinked Inspections – Select this option to display a warning flag for an inspection that has not been associated with a permit, license, approval, bond, decision, prosecution or appeal. If the user tries to access the inspection in Govern, a message will be displayed.
A/R Class items that are year based that appear in the A/R Class Default combo box will use the year that is set under the GNA Year tab, not the year from (Table: USR_DEPARTMENT).
See Workflow Activities
See Workflow Types
See Workflow Inspections
Click below to display or download the technical documentation.
103-wm-parm-301 Department Parameters.pdf
103-wm-parm-301
The Export Data form is used to export data structures from a specified database to an .XML file. The form allows you to export data settings through a step by step drill down process. The process is able to export everything from an entire database structure consisting of Modules, Module Elements (ME), and Module Element Components (MEC). The export process requires the user to select what elements of their database are to be exported. The export steps follow the Govern hierarchy. The Govern hierarchy is as follows:
Modules | Module Elements (ME) | Module Element (ME) Components |
---|---|---|
Open Form | OpenForms | All Profiles, OpenForms, Business Models (BM), Business Entities (BE), Security (Selected, or All) |
System Configuration | System Registry, Dynamic Search (Group, Styles), Logical Expressions, SQL Queries, Batch Processes, Reports, Text Styles, and so on. | |
Govern Tax | Real Property, Personal Property, Motor Vehicle, and so on. | |
Matix Client Map | Matix related Client Maps | |
NOTE: Although select Module Elements (ME’s) appear to not be present in the |
Modules | Module Elements (ME) | Module Element (ME) Components |
---|---|---|
Open Form | OpenForms | All Profiles, OpenForms, Business Models (BM), Business Entities (BE), Security (Selected, or All) |
System Configuration | System Registry, Dynamic Search (Group, Styles), Logical Expressions, SQL Queries, Batch Processes, Reports, Text Styles, and so on. | |
Govern Tax | Real Property, Personal Property, Motor Vehicle, and so on. | |
Mass Appraisal | MA Tables, Shared Lookup Group Set, BSE Templates, User Validation Entries | |
Misc. Billing | MB (Categories, Items, Recurring Batches) | |
Matix Client Map | Matix related Client Maps | |
User Validation tables | Validation Tables (Regular, A/R, MA, Workflow, and so on) | |
Workflow Management | Workflow Action Answers, Names, Status’, Inspection Type Reason Codes/Status’, | |
NOTE: Individual user Module Elements and ME Components will vary from the above depending on which Govern modules have been purchased and licensed. |
During the export process, user selections will determine what options are presented in the next step. When exporting entities, all required dependencies, i.e. tables, are also exported. The resulting exported file can then be imported to another database using the Import Data utility, see Import Data from File for details about this process.
There are no noticeable changes from previous versions of the Import, and Export utility. Navigation through the stages and steps of the process is carried out with the following navigation buttons
As an example, an administrator can design a new Profile and then wishes to export it. During the export process it will be necessary for them to make decisions as to what is to be exported. In their selection a single profile may be selected, or all profiles within the database. To demonstrate the steps involved in the export process, a single Profile will be exported. During the export, any associated security settings related to roles can be selected.
By default when a profile is selected for export, NO security settings will be exported with it. This means that any securities associated with the profile will not be exported. As a result, a profile will be accessible to all roles and users.
When new securities for roles are to be defined, then it is not necessary to select the Security option for export.
To export Module Elements without security, from the GNA ribbon…
NOTE: Unless an export filename is specified, the Export button will not become active, regardless of what selections are made. |
The presence of the Export button [>] is an indication of the end of the selection process. At any point during this process, you can select Previous [<<] to return to the last step and modify your selection.
Follow these steps to export an Open Form Model:
When the Open Form Model to be exported does not require security, or securities are to be added at a later time, do not select the Open Form Model with the Security option.
NOTE: Unless an export filename is specified, the Export button will not become active, regardless of what selections are made. |
NOTE: The presence of the Export button [>] is an indication of the end of the selection process. At any point during this process, you can select Previous to return to the last step and modify your selection. |
The length of the process is dependent upon the size and complexity of the database. When the process is complete, a dialog box is displayed.
When there is another export to be performed, click Restart to return to the beginning of the process; alternatively, click Exit to close the form.
Locate the newly created file that is to be imported from the Save to: folder.
When exporting a Business Model or Business Entity follow the above steps, i.e. steps for Exporting an Open Form Model.
Thus far, we have only exported single Module Elements (ME). Realistically, it is often needed to export more than one module element at a time. For example if multiple module elements are selected, e.g. the following ME’s:
For this type of export, there would be multiple stages of user interaction before the export option is presented. We would need to make selections for Profiles, Open Form Models, and Business Models.
To make an export of multiple Module Elements (ME’s)…
NOTE: If you click Previous, you will be returned to the previous screen, but you will no longer be able to deselect any selections. |
12. You will observe that the Next [>>] button has been changed to an Export [>] button. Click Export to generate the file.
NOTE: Unless an export filename is specified, the Export button will not become active, regardless of what selections are made. |
The methodology that is used for exporting multiple Modules or Module Elements applies to both OpenForms as well as System data structures. If a user were to export multiple System module elements, e.g. Dynamic Search groups, and Dynamic Search Styles, some Dynamic Search group items may be pre-selected, because they are part of the Dynamic Search Style.
Click here to link to the current version of the documentation.
NOTE: When enabled trace functions can be instrumental in troubleshooting system issues, likewise in assisting Technical Support to resolve them.
To display the Diagnostic Configuration console…
By default, when enabled, a trace process will immediately begin to generate data that is written to a Comma Separated Value (.csv) log file in the Trace directory of the deployment folder. The trace file will use the following naming convention:
userName_serverName_ckName_appName.csv
where…
userName = users login name
serverName = name of the server that the application is installed
ckName = the connection key name
appName = the application that is being monitored
Ex.: jdoe_JNMTL2_GOVDB_60_JNMTL2_SQL_GovernNetAdmin.csv
NOTE:The trace log file is self maintaining in that it will be deleted when it is older than 30 days – this value cannot be modified. Alternatively, users may opt to delete the file manually, it will be regenerated the next time it is enabled.
To configure a system trace, you will need to select the area of interest from the Diagnostic Configuration console.
Select Software under Load configuration from: areas that a trace can be enabled are displayed, along with parameters.
Software option
Target: The Target options allow the selection of how the trace information will be presented. The options are as follows:
File – The File option will generate the trace information as a log file. This .csv file can be opened with any application that supports the format, e.g. Microsoft Excel.
Console – When Console is selected, a console (output window) titled NLog is launched. The trace information is logged in the NLog window.
Console and File – Selecting the Console and File option will display the trace information using both of the above means, the NLog console window will be displayed and a .CSV log file will also be generated.
When the Text option is selected, A text field is displayed. The intent is that any debugging information is pasted into the field.
Minimum Reporting Type: Selecting a minimum reporting type will determine what details are logged. For example:
Info – Select the Info option to log general information about the application. This can include a list of the calls that are made by the application
Warning – The Warn minimum level will log error messages that are of the
Error – When a minimum level of Error is selected, the system will log all errors that are categorized as an Error. These are errors that will cause the application to halt its current process, but will not cause it to fail. In this situation data loss may occur.
Fatal – This option will log all errors that are categorized as Fatal. These are errors that will cause the application to fail, i.e. a crash without the chance of a recovery. In this situation data loss may occur.
The list of supported modules are presented below the Minimum Reporting Type option and pertain to the areas of the govern application, modules, and integrated 3rd party modules.
All – Selecting All logs the errors generated by all modules. This will include traces of the errors generated by installed Govern suite applications; e.g. Govern, GovernNetAdmin, BEDesigner, GovernSoftware.Security.UI.Manager, MSGovern.OFD, and so on.
DAB – Selecting DAB will log the activities that access the Govern Data Access Block (DAB)
NOTE: When the DAB option is selected, a new field called Trace commands where execution time is longer than X milliseconds will be displayed. See details below.
The text option is reserved for entering debugging information that is generated by the system. When errors are generated by the system, the debug code can be copied and reviewed for insight into the issue. To further assist, when the “Load configuration from” Text option (A) is selected, the debug code can be copied and pasted into the text field that is displayed.
If there is an incompatibility, an error window will be displayed.