EZSPM Format

<< Click to Display Table of Contents >>

Navigation:  SPM > SPM > Formats >

EZSPM Format

Format Name: EZSPM

File Name: EZSPM.zip

Software: EQuIS SPM

Source: SPM install

Export(s): No export

 

Description: The EZSPM format is a simplified version of the SPM format. The EZSPM format allows users to easily create multiple planned and scheduled tasks, samples, results, containers, and activities with limited manual data entry. This format assumes the plan already exists in SPM and the SPM_CONTRACT_MAG information is already setup.

 

Installation Instructions: This format requires a licensed SPM and the SPM Schema applied to the database.

For SPM usage, no additional steps are necessary.

For Enterprise and Professional usage of the export, this format should be published to the database. The export will be available for selection as a report once it has been published.

 

Overview: The Analysis_Request_General, Analysis_Request_Detail, and Activity_Request_Detail sections automatically create multiple Task, Sample, and Activity rows, respectively, on EDD load. The Task, Sample, and Activity sections can then be reviewed and modified before creating and commiting. The Analysis_Request_General, Analysis_Request_Detail, and Activity_Request_Detail sections do not map to any database tables—these sections just create rows in other sections of the EZSPM format.

 

A potential workflow could be:

1.Open the EZSPM format in EDP.

2.Add one row to the Analysis_Request_General section. This will correspond to one Task row. Note that each EDD can only have one Analysis_Request_General row.

3.Add one or more rows to Analysis_Request_Detail section. Each row in Analysis_Request_Detail will create one to many Sample rows.  
Analysis_Request_Detail.location_group or Analysis_Request_Detail.location dictates how many Sample rows will be created. One Sample row will be created for every location within the location_group, or individual location listed.  The Sample section creates samples, results, and containers when committed. One container per SPM_CONTRACT_MAG will be created.

4.Add one or more rows to Activity_Request_Detail. Each row in Activity_Request_Detail will create one to many Activity rows.  
Activity_Request_Detail.location_group or Activity_Request_Detail.location dictates how many Activity rows will be created. One Activity row will be created for every location within the location_group, or individual location listed.

5.Save the EDD.

6.Clear EDP, or reopen the EZSPM format.

7.Open the EDD saved in Step 5.

8.Review the Task, Sample, and Activity rows for errors.

9.Add Collect_Members rows as desired. This section allows users to add specific user_names to exisiting Collect groups.

10.Create and Commit.

 

 

Note: Task, Sample, and Activity rows will be automatically created each time an EZSPM EDD is loaded with Analysis_Request_General, Analysis_Request_Detail, and Activity_Request_Detail information. If there needs to be changes to the Analysis_Request_General, Analysis_Request_Detail, or Activity_Request_Detail sections after opening the EDD (e.g., Step 7 above, which automatically populated Task, Sample, and Activity), ensure that Task, Sample, and Activity are cleared before saving the EDD. Not doing so will result in duplicate Task, Sample, and Activity rows when the EDD is opened again.

 

 

The tables below provide detailed automatic population information for the Task, Sample, and Activity sections. Blank cells indicate that the field is not automatically populated.

 

Task

Populated By

plan_code

Analysis_Request_General.plan_code

planned_task_code

Analysis_Request_General.task_code

planned_task_name


scheduled_task_code

Analysis_Request_General.task_code + _+ Analysis_Request_General.start_date

start_date

Analysis_Request_General.start_date

end_date

Analysis_Request_General.end_date

remark

Analysis_Request_General.other

task_type

Analysis_Request_General.activity_type

company_code

Analysis_Request_General.company_code

max_turnaround_days

Analysis_Request_General.max_turnaround_days

task_desc


recurrence

n

custom_field

Analysis_Request_General.use_collect

create_scheduled_tasks

Analysis_Request_General.create_scheduled_tasks

include_dates

Analysis_Request_General.start_date + | + Analysis_Request_General.start_date + ||

naming_schema_task


 

 

Sample

Populated By

plan_code

Analysis_Request_General.plan_code

lab_code

Analysis_Request_Detail.lab_code

contract_start_date

dt_spm_contract where contractor_code = Analysis_Request_Detail.lab_code and plan_code = Analysis_Request_General.plan_code or is null

method_analyte_group_code

Analysis_Request_Detail.method_analyte_group_code

spm_contract_mag

Analysis_Request_Detail.spm_contract_mag

sys_sample_code

Analysis_Request_Detail.location (or location from Analysis_Request_Detail.location_group) + _ + Analysis_Request_Detail.matrix_code + _ + Analysis_Request_General.start_date + _ + an incremental three-digit number

sample_name


scheduled_task_code

Analysis_Request_General.task_code + _+ Analysis_Request_General.start_date

parent_sample_code


sys_loc_code


start_depth


end_depth


depth_unit


matrix_code

Analysis_Request_Detail.matrix_code

sampler


sampling_company_code


sample_class


sample_source


sample_type_code

Analysis_Request_Detail.sample_type_code

sample_method


medium_code


composite_yn


fraction

Analysis_Request_Detail.total_or_dissolved

sample_remark


hold_YN


hold_release_date


 

 

Activity

Populated By

plan_code

Analysis_Request_General.plan_code

scheduled_task_code

Analysis_Request_General.task_code + _+ Analysis_Request_General.start_date

sys_loc_code

Activity_Request_Detail.location (or location from Activity_Request_Detail.location_group)

activity_code

Activity_Request_Detail.activity_code

equipment_code

Activity_Request_Detail.equipment_code

sampler


sampling_company_code


remark


task_type


activity_type

Activity_Request_Detail.activity_type

activity_order


count


unit