Create a New SPM Plan

<< Click to Display Table of Contents >>

EQuIS 7  >>  SPM > SPM Desktop > Plans >

Create a New SPM Plan

A Plan in SPM is like a folder to organize a task or a group of tasks (e.g., groundwater and/or surface water monitoring, measuring water levels, collecting soil samples, other field activities, etc.) that have to be performed.

 

Create New Plan

 

When the database has no existing SPM plan, the SPM welcome window opens upon connecting. Click Create Plan.

 

20004_Plan_Selection_Screen

 

When a Plan is already open, click New Plan on the Plan tab of the EQuIS SPM home ribbon,

 

20004_New_Plan_button

 

or click the SPM Application button and select New Plan from the drop-down menu.

 

20004-NewPlanFromDropDown

 

Enter Plan Code and Information

 

All bold fields are required. Enter a unique Plan Code and any other desired fields. The Start Date defaults to today’s date, and the End Date defaults to one year later. Tasks may be planned with End Dates sooner than the Plan End Date, but they cannot be planned with End Dates after the Plan End Date. The Plan End Date can be deleted to allow for open-ended planning.

 

Note: If more than one plan is to be created, it is helpful to refer to the project name or client name in the Plan Code to help identify the plan when listed in the Open Plan window.

 

The full list of Plan Parameters can be found at the end of this article.

 

20004_New_Plan_Details

 

Enter Naming Schemas

 

The Task Code and Sample Code Naming schemas are required. These become the default naming schemas for Planned Tasks and Samples, but can be changed during the planning step.

 

20004_Default_Naming_Schemas

 

The Task Code must be unique within a facility. For convenience, a default naming schema is included with SPM. Users may choose to customize it or to create a new naming schema.

 

The Sample Code must be unique within a facility, and is used to link the samples with results via DT_SAMPLE.SYS_SAMPLE_CODE. For example, a sample code schema may be [Matrix_Date_Sample#], or GW_051710_001. The Date format can be changed once added to the schema. The example used mmddyy.

 

The Sample Name naming schema is optional, allowing the sample to be referenced by a name other than the Sample Code. Laboratories do not see this name.

 

The QA/QC Sample Code and QA/QC Sample Class are optional and may be used if samples of a specific sample class (such as a Field Quality (FQ) sample) are to use a different naming schema than the normal environmental field samples. If a QA/QC Sample Code is chosen, a QA/QC Sample Class must also be chosen. The QA/QC Sample Class drop-down lists all values used in RT_SAMPLE_TYPE.SAMPLE_TYPE_CLASS, except for a special "LQ" class reserved for lab quality samples. As the cursor hovers over the QA/QC Sample Class box, a pop-up message describes the function of these optional fields.

 

For more information on naming schemas, please review Naming Schemas, and Create or Edit a Naming Schema.

 

Default units for Currency may also be entered.

 

Note: If a unit is missing from RT_UNIT, click the Currency drop-down to open the RT_UNIT table. Click Add to create new unit records, then click OK to save and close the window.

 

The full list of Plan Parameters can be found at the end of this article.

 

Create the Plan

 

Click Create to save the Plan Information.

 

20004-CreatePlan

 

Edit Plan Details

 

Plan information can be edited by clicking the Details button on the Plan tab of the menu ribbon.

 

20004-EditPlanDetails

 

Plan Parameters

 

PLAN CODE

oPrimary Key

oRequired

oText (40)

oThe unique identifier of the Plan.

DESCRIPTION

oText (255)

oThe description of the Plan.

CLIENT

oLookup: RT_COMPANY.COMPANY_CODE

oThe department or company responsible for the task.

START DATE

oDate

oThe start date of the Plan.

oPlanned Tasks created under the current Plan will be constrained by this date. Planned Tasks cannot begin before this date.

END DATE

oDate

oThe end date of the Plan.

oPlanned Tasks created under the current Plan will be constrained by this date. Planned Tasks cannot end after this date.

REMARK

oText (2000)

oAny additional information pertaining to the Plan.

TASK CODE

oRequired

oTASK_CODE values are limited to 40 characters. This value should be configured to result in TASK_CODE values of 40 characters or less.

oThis value defines the default for the Plan, but can be further defined at the Planned Task level.

SAMPLE CODE

oRequired

oSYS_SAMPLE_CODE values are limited to 40 characters. This value should be configured to result in SYS_SAMPLE_CODE values of 40 characters or less.

oThis value defines the default for the Plan, but can be further defined at the Planned Task level or in EDGE.

SAMPLE NAME

oThis value defines the default for the Plan, but can be further defined at the Planned Task level.

QA/QC SAMPLE CODE

oSYS_SAMPLE_CODE values are limited to 40 characters. This value should be configured to result in SYS_SAMPLE_CODE values of 40 characters or less.

oThis value defines the default for the Plan, but can be further defined at the Planned Task level or in EDGE.

QA/QC SAMPLE CLASS

oRequired if QA/QC SAMPLE CODE is defined.

oThis value defines the default for the Plan, but can be further defined at the Planned Task level or in EDGE.

CURRENCY

oLookup: RT_UNIT.UNIT_CODE

oThe currency for the Plan.

oThis value defines the default for the Plan, but can be further defined at the Contract level.