•Enter Plan Code and Information
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
After connecting to a database and there are no plans or there is no open plan, the SPM welcome screen is displayed. Click Create Plan.
When a plan is already open, click New Plan on the Plan group of the SPM Plan ribbon.
The New Plan dialog opens.
Enter Plan Code and Information
Enter a unique Plan Code and any other desired fields. Do not include SQL commands (e.g. 'UPDATE', 'DELETE') in the name, as this will cause errors. The full list of Plan Parameters can be found at the end of this article. All bold fields are required.
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 easily identify the plan when listed in the Open Plan window. |
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.
The Task Code and Sample Code Naming fields are required. These become the default naming schemas for Planned Tasks and Samples, but can be changed during the planning step.
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. |
Click Create to save the plan information.
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.