ptagis - tds tag distribution system doug clough 2 december 2008

PTAGIS - TDSTag Distribution System

Doug Clough

2 December 2008

Database Overview

• Core tables + TPA (TDI)– Tagging and Interrogation Data

• ALRS– Where Tagging & Interrogation take place

• PPO– Who receives the tags

WHAT PTAGIS does

WHERE it happens

WHO is involved

Database Overview

• Core tables– Tagging and Interrogation Data– Site Configuration

• TPA (TDI)– Distributing PIT tags to projects

• ALRS– Where Tagging & Interrogation take place

• PPO– Who receives the tags

REARING

TAGGING

RELEASE

INTERROGATION

RECAPTURE

MORTALITY

What Goes On At A PTAGIS Site?

ALRS Schema: Modeling PTAGIS Activities

INTERROGATION TAGGING RECAPTURE MORTALITY

Proposed ALRS Schema

Existing PTAGIS Tables

Restrict queries by:hucriver_namesite_type

(activity_code shown in red)

‘Core’ Tables: “What” ALRS: “Where”

WQB = PTAGIS Web Query Builder

Greater convenience and flexibility for PTAGIS user community

How would this help? ALRS Schema

Original PTAGIS Tables

But where do the tags come from

?!!?

But where do the tags come from

?!!?

Distributing

The missing activity!!

Distributing PIT Tags• TDI (Tag Distribution & Inventory)

– Used for over 10 years– New requirements arose (ISRP)

• Maintain history of project personnel through time• Provide linkage between people, projects, and

activities

– Business process changed• BPA now purchases PIT tags

– New technology gave new opportunities

Distributing PIT Tags• TDS (Tag Distribution System)

– Production deployment September 2008– Interacts with PPO tables to help …

• Maintain history of project personnel through time• Keep linkages between people, projects, and

organizations up to date

– Supports streamlined business process• Requests and approvals entered on-line• Eliminates PDRF forms

– TDI data will be copied into the TPA tables

TDS Automates the Tag Distribution Process

TDS Automates the Tag Distribution Process

PPO Schema: Modeling PTAGIS Participants

NWPCC / BPA / CBFWAPSMFCCOEBioMarkChelanPUDNOAAWDFWDigitalAngelNez Perce TribeIDFG

organization

PK org_id

org_code name descrip org_status

project

PK proj_id

description

activity

PK activity_code

activity_category

activity_location

PK,FK2 site_codePK site_idPK,FK1 activity_code

project_activity

PK,FK1 proj_idPK,FK2 activity_code

coord_id

project_activity_location

PK,FK1 proj_idPK,FK1 activity_codePK,FK2 site_code

from_date to_date

<activity>_hdr

<activity>_data

project_activity_role

PK,FK2 person_idPK,FK1 role_idPK proj_idPK activity_codePK site_code

from_date to_date

office

PK office_id

addr1 addr2 city state zip phone fax

work_space

PK office_idPK,FK1 person_id

from_date to_date

person

PK person_id

f_name m_name l_name phone_pager phone_cell phone_home

person_role

PK role_id

description

p_a_l_event

PK,FK1 org_idPK,FK1 proj_idPK,FK1 activity_codePK,FK1 site_codePK site_idPK date_timePK event_type

event_guid

p_a_l_data

PK,FK1 event_guid

data_name data_value

COTRtag shippertag receivertag supervisortagging techdata ownerelectronics techsite biologist

Administration tag purchase tag distribution tag re-sell tag return field O&M data centerHandsOn rearing tagging recaptureRemote interrogation s by cNatural predation mortality

coord_id Examples: DMM – ‘tagging’ activity coord DMM – ‘recapture’ activity coord DMM – ‘mortality’ activity coord PTOC – ‘interrogation’ activity coord PTOC – ‘field O&M’ activity coord PTOC – ‘data center’ activity coord

New Implementation

Use domain_enumeration

Conceptual Only

Existing Implementation

tag_hdrmort_hdrrecap_hdr

tag_datamort_datarecap_data

obs_data

PTAGIS Data Sets

“Field Data Files”

“Interrogation Data Files”

Key

<coord_id>YYDDD.zzz

<site_id>YYDDD.n

organization_role

PK role_id

description

org_project_role

PK,FK1 org_idPK,FK2 proj_idPK,FK3 role_id

org_proj_nbr

funding sourceadmin sponsorfunding recipientsub-contractor

description Examples: PIT tagging wild Chinook PTAGIS

location_in_segment

PK site_id

loc_id seg_id

Include site_id = “NONSPEC” to model “Not location-specific”

Include site_code = “NONSPEC” to model “Not location-specific”

org_office

PK,FK1 org_idPK,FK2 office_id

name descrip from_date to_date

org_2_org

PK org_1_idPK org_2_idPK org2org_type

from_date to_date

project_note

PK proj_idPK note_id

comment date_time

PPO Tables Associate …

• Offices with addresses and organizations

• People with offices

• Organizations with people and projects

• People with project-specific roles

Relationships are tracked through time

PPO Tables …• Populate drop-down lists

– Participant names– Addresses for selected person

• Capture participant roles– Tag Requester– Tag Recipient– Any number of roles for one person– Tracked through time

(In TDS – Other uses in other sub-systems)

TDS Automates the Tag Distribution Process

TPA Schema: Models PIT Tag Distributing

project

PK proj_id

proj_code sub_basin name description start_date end_date

procurement_calendar

PK year_nbrPK month_nbr

month_seq_nbr month_abbrev month_name

procurement_activity

PK,FK2 year_nbrPK,FK2 month_nbrPK,FK1 proj_idPK activity_codePK tag_nominal_type

tag_quantity activity_state state_datetime l_f_name

procurement_event

PK,FK1 year_nbrPK,FK1 month_nbrPK,FK1 proj_idPK,FK1 activity_codePK,FK1 tag_nominal_type

tag_quantity activity_state state_datetime l_f_name

pit_tag_vial

PK,FK1 box_codePK vial_code

tag_type tag_quantity distributed_by_org box_seq vial_seq

pit_tag

PK tag_id

tag_typeFK1 box_codeFK1 vial_code

pit_tag_transport

PK,FK1 proj_idPK,FK1 year_nbrPK,FK1 month_nbrPK,FK1 activity_codePK,FK1 tag_nominal_typePK transport_seq

tag_quantity from_org_code from_office_code from_l_f_name to_org_code to_office_code to_l_f_name not_before_date not_after_date send_clip_files extra_instructions carrier_org_code tracking_code shipping_cost activity_state state_datetime

transported_vial

PK,FK1 proj_idPK,FK2 box_codePK,FK1 year_nbrPK,FK1 month_nbrPK,FK1 activity_codePK,FK1 tag_nominal_typePK,FK1 transport_seqPK,FK2 vial_code

presence_confirmed

Current State

State Change History

Attributes From PPO SchemaSufficient To Identify Address, Phone, E-mail Address

organization.org_code

office.office_code

person.l_f_name

Textual identifier

Textual identifier

Concatenation of last name,_first name_optional suffix

activity_code

REQUESTINGAPPROVINGRECEIVINGSHIPPINGRETURNINGREGISTERING

pit_tag_transport ?

NoNoYesYesYes

Virtual

activity_state

Open > Decided > FulfilledOpen > DecidedExpected > Received > ConsumedOpen > Decided > Packaged > Sent > ReceivedOpen > Decided > FulfilledNotified > Registered

pit_tag_type

PK tag_type

tag_nominal_type provider_org_code tag_order_code description tag_length tag_diameter unit_cost from_date to_date

transport_event

PK,FK1 proj_idPK,FK1 year_nbrPK,FK1 month_nbrPK,FK1 activity_codePK,FK1 tag_nominal_typePK,FK1 transport_seq

tag_quantity activity_state state_datetime from_l_f_name

temp_to_address

PK,FK1 transport_seq

contact_name organization address_1 address_2 address_3 city state country zip telephone email

bpa_tag_purchase

PK po_numberPK release_number

tag_order_code tag_quantity price_per_tag need_by_date message_date

initial_tag_custody

PK,FK2 transport_seq

FK1 po_numberFK1 release_number shipment_seq po_qty_remaining sender_order_number tag_type tag_quantity recipient_org_code message_date

tag_vial_hist

PK,FK1 tag_idPK box_codePK vial_code

from_date why_moved

pit_tag_box

PK box_code

FK1 tag_type box_seq vial_count next_vial_seq

The missing activity!!

TPA Tables Capture …• PIT tag requests

– Quantity by month and type– Recipient names and addresses

• PIT tag purchases and initial custody – PTAGIS inventory– Other: USACE

• PIT tag approvals• PIT tag distributions to projects• User interaction with TDS identifies

– Who requests tags– Who receives tags

TPA Tables Capture …• PIT tag requests

– Quantity by month and type– Recipient names and addresses

• PIT tag purchases and initial custody – PTAGIS inventory– Other: USACE

• PIT tag approvals• PIT tag distributions to projects• User interaction with TDS identifies

– Who requests tags– Who receives tags PPO TPAproj_id

TDS Automates the Tag Distribution Process

Project POC enters anticipated tag quantities …

3 RolesBasic, Approval, Inventory

Project POC enters anticipated tag quantities …

Project list populated from PPO tables

Project POC enters anticipated tag quantities …

Note: This project has been “pre-approved”

Project POC enters anticipated tag quantities …

Click here if no tags are required

Approvals can be entered before or after requests …

Exercising the Approval Role

Approvals can be entered before or after requests …

Blue highlighting indicates un-saved

changes

Project POC Identifies Recipients (last names beginning with ‘mar’) …

Exercising the Basic role again PPO tables provide

names and addresses

Corresponding Addresses, Plus ‘Other’ …

Select an address, then click the button …

Initially, all tags assigned to one recipient …

Two assigned recipients, red arrows mean incomplete details …

Details expanded, incomplete items in red …

Stored in TPA tables

Stored in TPA tables

Shipment details complete; SaveChanges Enabled …

Blue highlighting goes away when changes have been saved …

(Before or after) BPA administrator approves requested quantities …

Project POC checks approval and adjusts quantities as necessary …

Exercising the Inventory Role: Distribute tab …

Exercising the Inventory role

Number of shipments (Number of tags in ‘tool tip’)

No project is selected

List of recipients and tag quantities; read-only …

Click a ‘cell’ to seeshipment details

Shipment details for one of the recipients; read-only …

List of recipients and tag quantities; read-only …

Check the checkbox

Click the button

30,000 Tags; 3 full boxes …

Pick list generated from data in TPA tables

Pick List: “Retrieve from Inventory” …

Shipment is Packed; Must save changes …

Packing lists showing “Ready for Shipment” …Shipment containing

boxes and vials

Inventory Role: Distribution “Packed” and “Sent” …

P – PackedS – SentR – Received

Basic Role: Distribution “Packed” and “Shipped” …

Exercising the Basic role again

P & S – Read-onlyR can be ‘checked’

Anticipating arrival of tags from DestronFearing …

Receiving tags into PTAGIS inventory …

But wait! There’s more …

• Automated registration of tag shipments– Backbone is built and in use– Need to build e-mail enabled driver

• Email alerting of significant events– IMMEDIATE alert of approval and shipping

• Built and in use

– LAZY alert of request / recipient changes• Built and undergoing pre-deployment tests

TDS Automates the Tag Distribution Process

Email

(and just a little more) …

• Automated registration of tag shipments– Backbone is built and in use– Need to build e-mail enabled driver

• Email alerting of significant events– IMMEDIATE alert of approval and shipping

• Built and in use

– LAZY alert of request / recipient changes• Built and undergoing pre-deployment tests

Questions?