Examination


The Process

The Examination topics in the help system give detailed information on the examination process, and provide insights into how PlanTest works. There are often more than one way something can be done, and ultimately, we hope to cover nearly all the possible options. The topics follow the designed purpose of PlanTest as a decision support tool for cadastre.

Window Standard Tools

An examination will generally follow a path similar to the diagram above. We will describe the goals and actions of the following steps:

  1. Start - begin the exam
  2. Analysis (run tests)
  3. Review - view test results
  4. Investigate - fabric, results and errors found by tests
  5. Decide - make decisions where required
  6. Review Status - check the status of the exam
  7. Finish - complete exam, message other systems

We added two additional steps to the conceptual diagram, because we need to describe to tools you use to investigate errors, and the check the status of the examination. Of course, an examination may not be quite so linear.


The Start

There is more than one way to start an examination in PlanTest. If started from job control or command line, the start parameters can accomplish quite a lot. PlanTest will usually be initiated by a job control application, as part of a complete jurisdictional workflow. When initiated by job control, all data, services and necessary permissions will be set up automatically.

When you start PlanTest without parameters, you need to use PlanTest menus and controls to:

  1. Load data
  2. Select the subject plan
  3. Execute analytic tests.
Progress window

Once data is loaded, the data decides the workflow that is used. The imported data contains properties that define the type of plan or submission. Depending on the type, the associated workflow is loaded and is visible then in the Workflow Control window.

For a more in-depth discussion of startup options read more...


Analysis - Running Tests

Analytic tests can save a lot of time and effort, and in some cases perform analysis you could never do manually. Every site will have its own set of analytic tests allocated across any number of workflows, with some tests used in nearly all workflows.

You can run tests by three methods:

  1. On startup - all
  2. From the Analysis Menu - all or undecided
  3. From Workflow Control - one at a time

On Startup

As discussed in the start section, you can automate execution of all tests on startup. The progress window, shown below, will be displayed depending on your options settings.

Analysis Menu

If you are working ad hoc, or simply want to rerun a group of tests, the main menu Analysis submenu lets you choose to run all tests, or only those which have no decision. Progress can be shown depending on option settings.

Depending on your option settings, you will see the same progress window as above.

Workflow Control

If a step has an associated test method, you can run the test by double clicking the text of the leaf node of the workflow control.

Basic Use

  1. double-click text to right of checkbox.
  2. The analysis will be executed, and the results shown in the Test Results window.
  3. Execution of the test will also update the map to the step views, and any analytic graphics.

Review Analytic Results

Analytic tests may produce the following types of results:

  1. An analytic "Pass/Fail" result, these are often associated with requisition codes stipulated in the workflow document.
  2. Informational messages of use to examiners, but not indicating problems or issues with the data.
  3. Error messages are specific error messages indicating non-compliance with regulation or practices.
  4. Tabular results specific to the test; often highly detailed on select cadastral features or analysis products.
  5. Graphics created during analysis and related to tabular results records.

Each analytic test will have its own specification for fail conditions, when and what messages are recorded, and the records shown in tables. In particular, table columns are specific to each test, the test's records may have complex groups, and each test may define specific record to map feature and or graphic associations.

There are two main windows for viewing results, each with their own help section:

  1. The Results and Decisions window. This is the best way to quickly review the analytic results and messages for all executed tests, and as a control to open each test's results. read more...
  2. The Test Results window. This gives access to all of the analytic results for a test, and has table record to map navigation. read more...

Investigation

Most of the time using the standard review methods will be enough. The analytic results point directly to the data that caused a fail condition, and the standard use of the Test Results window and map navigation from table records to features is a quick way to see faults. Sometimes you need to search for context using other data, or use tools to make ad hoc calculations.

The windows, tools and reports available will depend on your data models as jurisdictional adaptation and customization. The detail pages for the suggested items below tipically contain notes on specific techniques of use.

  1. Fabric Window and Tools jump to section...
    1. Joins - validate proper connections between surveys.
    2. Residuals - find areas or specific points that have lower accuracy.
  2. Cadastral Tools - to calculate measurements within and between surveys. jump to section...
    1. Identify Tool
    2. Closing Line Tool
    3. Internal Angles Tool
    4. Intersecting Line Tool
    5. Line from Points Tool
  3. If available, data load reports to indicate data issues.
  4. If available, fabric reports (analytic tests w/o decision requirements) to investigate fabric elements and relationships
    1. Lines report - all line properties
    2. Parcels report
    3. Hulls report
    4. Points report
    5. Controls report

Refer to these tools and reports for methodologies to use in your investigations.


Decisions

Most steps require a decision before the exam can be finalized. PlanTest provides several ways to make decisions efficiently, for both analytic tests and .

Decisions can be made in three work areas:

  1. The Workflow window tree control - "check" decisions, (group and individual steps). read more...
  2. The Results and Decisions window (analysis result groups) read more...
  3. The Test Results window (individual steps - analytic or check). [read more...]

For an in-depth discussion of Decisions in PlanTest, see Decisions...

Status Review

The current status of decisions on the examination are always readily visible in PlanTest in one of two windows: the Workflow window, or the Results & Decisions window. The Workflow window shows the decision status by checkboxes and color coding the nodes and leaves of the workflow tree. read more...

The Results & Decisions window represents workflow steps as table records - rows are color coded by the decision states. The R&D window shows more information than the Workflow control. Columns show examiner comments, analytic messages, as well as the analysis result and decision.read more...

There are also special reports under the Review Menu: the Examination Review Report which shows a complete table of the status of all steps for an ongoing examination, and the Summary Report which shows high level examination statistics.


Finish

Once all workflow steps have been completed, the plan either has passed or has not. The specifics of finalization depend on the jurisdictional customization, so are not detailed. Generally, the first steps of finalization will include checks to determine the status of the examination, and provide an opportunity to complete necessary steps or resolve issues prior to calling other processes.

There may be automated steps to push rejected plans into a messaging system that will convey the results along with comments and suggestions for remedy to be sent to the interested parties. If the plan passes, then the results of the examination may be archived, and the final steps of the transaction handed over to a manual or automated title system, while the survey data may be inserted into a digital cadastre database.