IB-OR-2004-069 - Re-establishment of ARIMS User Requirements Team
UNITED STATES DEPARTMENT OF THE INTERIOR
BUREAU OF LAND MANAGEMENT
Oregon State Office
P.O. Box 2965
Portland, OR 97208
In Reply Refer to:
6720/1262 (OR-932) P
January 29, 2004
EMS TRANSMISSION 02/03/2004
Information Bulletin No. OR-2004-069
To:
All District Managers and Field Managers
From:
Deputy State Director for Resource Planning, Use and Protection
Subject:
Re-establishment of Aquatic Resources Information
Management System (ARIMS) User Requirements Team
DD:02/06/2004
As the Bureau of Land Management enters a new era of Geographic Information System technology, the ARIMS
database will be upgraded to ArcGIS. This will make it more user friendly and easier and less expensive to maintain.
The old user requirements for the fish module are also being revisited, because needs and inventory methods have
changed since they were originally identified. It is now time to re-establish a standing User Requirement Team (URT)
which can help the State Office ARIMS Data Stewards with evolving user requirements, field protocols, application
beta-testing, and other data management-related issues. A two-part team will be identified, one part for fisheries and
one part for water quality. The two groups may work or meet separately from each other or, occasionally, work and
meet together. The most logical members should generally be the District ARIMS Data Stewards or their designees.
An estimated workload for FY 04 is approximately ½ to 1 work month for Fisheries URT members, and ¼ to ½ work
month for Hydrology URT members. Travel for meetings will be minimized to the extent possible by using
conference calls.
The purpose of this Information Bulletin is three-fold:
1. Formalize the Fisheries URT made up of fisheries biologists who participated in the Fisheries User Requirements
meeting on November 5-6, 2003. District Managers are requested to allow those team members to formally
become ARIMS Fisheries URT members, or to designate an alternative person from their district.
2. Request that the URT members review and comment on the attached draft Fisheries User Requirements.
3. Request that each District Office identify a hydrologist to serve on an ARIMS Water Quality URT. No work has
been identified for the near future, but there will be some later in the year.
To elaborate on item no. 2, the State Office ARIMS Fisheries Data Steward, Al Doelker, and other ARIMS
development team members held a meeting with representative fisheries biologists from across the state to identify
updated Fisheries User Requirements. The results of the meeting are attached, and comments from the Fisheries URT
members are requested. Specific areas which especially need clarification and feedback are identified. Comments are
welcomed on all requirements or to point out anything that was missed.
Feedback is needed by February 6, 2004, on:
1. Formal (written response, not e-mail) designations of Fisheries URT members
2. Comments on Fisheries User Requirements
3. Formal designations of Water Quality URT members
IB-OR-2004-069 - Re-establishment of ARIMS User Requirements Team
Districts with Unions are reminded to notify their unions of this Information Bulletin and satisfy any bargaining
obligations before implementation. Your servicing Human Resources Office or Labor Relations Specialist can provide
you assistance in this matter.
Signed by
George R. Buckner
(Acting)
2 Attachments
1 - Fisheries URT meeting attendees (1p)
2 - Draft ARIMS Fish Module User Requirements (5pp)
Distribution
OR-931 (Al Doelker)
OR-932 (Rosemary Mazaika, Janis VanWyhe)
OR-955 (Georgia Bosse, Daniel Wickwire)
Titan (GeGe Coleman)
Authenticated by
Heather Gisch
Computer Specialist
A
B
C
1 ReqI ARIMS MoCategory
37 AV_ARIMS Analysis Tools
D
E
F
SubCategory Component ShortDescription
Habitat Quality
Redefined ODFW Summary Reach Tool
G
H
DateEntered
DateCompleted
12/16/2003
I
LongDescription
Tool: the ability to identify an upstream and
downstream point, the tool then finds all of
the ODFW habitat units on that stretch, uses
the ODFW criteria to redefine the summary
reaches.
J
M
Comments
Reviewer Comments
Need Input: 1. Is an output report
needed? If so, an example of the
output is needed and a list of data
elements. 2. Also need to
investigate differences in the ODFW
criteria between Westside/Eastside.
2
2 AV_ARIMS Analysis Tools
Report/Map
Stream Miles Table
12/16/2003
The ability to produce a table that
summarizes stream miles for a selected set
of reaches. The summary should be grouped
by reach levels.
Redefined ODFW Summary Reaches
12/16/2003
The ability to insert the redefined ODFW
summary reaches into ARIMS. The new
reaches should have a Level 1 value of
Habitat Quality.
The ability to spatially overlay fish
distribution data with habitat data.
The ability to create a map displaying
Presence and Absence by species.
The ability to overlay Fish Distribution with
barriers to determine what species are
affected by the barrier.
The ability to map fish distribution by
species.
3
38 AV_ARIMS Create Tools
Habitat Quality
4
79 AV_ARIMS Display Tools
Report/Map
Fish Distribution Overlay
12/16/2003
80 AV_ARIMS Display Tools
Report/Map
Fish Distribution Spatial Display
12/16/2003
21 AV_ARIMS Display Tools
Report/Map
5
6
12/16/2003
7
8
9
78 AV_ARIMS Display Tools
Reach Type
Report/Map
Fish Distribution
12/16/2003
103 AV_ARIMS Display Tools
35 AV_ARIMS Display Tools
Reach Types
Report/Map
Report/Map
Display Fish Use
Display Habitat Quality
12/16/2003
12/16/2003
46 AV_ARIMS Display Tools
Report/Map
Display Reports
12/16/2003
3 AV_ARIMS Display Tools
Virtual Table
Map Product
12/16/2003
10
11
12
The ability to map Fish Use reaches.
The ability to spatially display the Habitat
Quality reaches symbolized by the good, fair,
poor rankings.
The ability to link to one or more PDF reports Need Input: 1. Are the reports
related to a reach/site or a whole
and display them.
stream? 2. What is the maximum
size of the filename (character
length)? 3. Are all the files in PDF
format, or do other file formats
need to be supported? 4. Do the
users want to access the files from
ArcView or from the data entry
forms? 5. There should be a central
(district) location for reports.
District must specify the location. 6.
There needs to be a process for
ensuring no duplicate filenames. 7.
Sample reports should be provided.
The ability to add a table to a map that
contains: Presence/Absence, Habitat,
Population Strength, and Habitat Quality
(Good, Medium, Low).
Need Input: Is this basic ArcView
beyond needing the table?
Clarification is needed for the
element: Population Strength.
A
B
C
1 ReqI ARIMS MoCategory
22 Fish
Fish Use
13
23 Fish
Fish Use
D
SubCategory
Reach Type
E
F
Component ShortDescription
Fish Use
G
H
DateEntered
DateCompleted
12/16/2003
Reach Type
Informational Fish Use - Use Not Verified
12/16/2003
Informational Fish Use - Use Verified
12/16/2003
Fish Use, Use Verified is described as "use
field verified/observed by reputable fish
biologist."
14
I
LongDescription
Comments
The reach type Fish Spawning Habitat should
be changed to Fish Use.
Fish Use, Use Not Verified is described as
"best professional judgment suggests use."
24 Fish
Fish Use
Reach Type
26 Fish
Fish Use
Reach Type
Fish Use Level 2
12/16/2003
The level 2 values for Fish Use reaches
should be: Migratory, Winter Migratory,
Spawning, Rearing, Spawning & Rearing, and
Holding.
27 Fish
Fish Use
Reach Type
Fish Use Level 3
12/16/2003
The level 3 values for Fish Use reaches
should be: Use Verified and Use Not Verified.
28 Fish
Fish Use
Reach Type
Fish Use Level 4
12/16/2003
The level 4 value for Fish Use reaches should
be species code.
29 Fish
Fish Use
Reach Type
12/16/2003
Fish Use is reach based data. To represent
point data (ex. Spawning, Holding), the user
should create very small reaches.
106 Fish
Fish Use
Reach Types
74 Fish
General Survey
All
Data Elements General Survey Data Elements
12/16/2003
48 Fish
General Survey
All
Data Elements Linking Field
12/16/2003
A text field to reference to indicate the
location of additional information.
89 Fish
General Survey
All
Picklists
Method Picklist
12/16/2003
82 Fish
General Survey
All
Informational Method: Other
12/16/2003
The pick list for the field Method is:
Electroshocking (Single Pass),
Electroshocking (Multi-Pass), Hand Seining,
Hook and Line, Long Standing Natural
Barrier, Screw Trap, Snorkeling, Using
Spawning Survey, Visual, Weir Adult Trap,
Other.
If a user selects "Other" for Protocol, the
Method should be noted in the comments.
This process should be described in the
ARIMS data dictionary and User's Handbook.
15
J
16
17
18
Informational Fish Use Points
19
Fish Use Level 1
20
21
The system shall support entry and update
for Fish Use reaches by type of use,
verification status and species.
System shall support entry and update of the
following data elements pertinent for all fish
surveys: LLID, Beg Index, End Index,
Method 1, Method 2, Reach No (user
assigned), Reach ID (system assigned),
Comments, Investigator, Source, Purpose,
Survey Begin Date, Survey End Date.
22
23
24
Need Input: Is it acceptable to
the user group to use the
comments field for this information?
M
Reviewer Comments
A
B
C
1 ReqI ARIMS MoCategory
91 Fish
General Survey
D
SubCategory
All
E
F
Component ShortDescription
Picklists
Survey Method/Protocol Pick list
G
H
DateEntered
DateCompleted
12/16/2003
I
LongDescription
The ability at the State Office Data
Steward/team level to add new protocols to
the Survey Method/Protocol pick list after
standing user group approves the request.
J
Comments
25
111 Fish
Habitat Quality
Reach Type
Habitat Quality Level 1
31 Fish
Habitat Quality
Reach Type
Habitat Quality Level 2 Values
32 Fish
Habitat Quality
Reach Type
Informational Habitat Quality Level 3 & 4 Values
12/16/2003
There are no Level 3 or Level 4 values for
Habitat Quality reaches.
34 Fish
Habitat Quality
Reach Type
Informational Habitat Quality Reaches - Description
12/16/2003
Habitat Quality reaches are qualitative
assessments made for fish purposes. They
are based on quantitative habitat survey data
and are determined by using the ODFW
The Fish module shall be designed to
streamline data entry and minimize duplicate
data entry.
The Fish module shall be designed to be user
friendly.
Ability to get data from other sources.
Need Input: What functionality is
needed: data import, manual entry
or the ability to link? More specific
information is needed on what the
users would like to import from or
link to.
26
12/16/2003
27
The system shall support entry and update
for Habitat Quality reaches by quality
ranking.
Habitat Quality reaches should have the
following Level 2 values: Good, Fair, and
Poor.
Need Input: Does there need to
be a Level 4 value for Species?
28
29
112 Fish
Misc
Streamlined Data Entry
113 Fish
Misc
User Friendly Interface
5 Fish
Population MeasuAll
External Data Sources
6 Fish
Population MeasuAUC-Redd Count Excel SpreadshHatchery/Wild on spreadsheet
12/16/2003
7 Fish
Population MeasuAUC-Redd Count Data Element Jacks
12/16/2003
9 Fish
Population MeasuAUC-Redd Count Data Element Number of Disturbed Redds
12/16/2003
8 Fish
Population MeasuAUC-Redd Count Informational Process for counting
12/16/2003
71 Fish
Population MeasuAUC-Redd Count Informational Westside Method
12/16/2003
49 Fish
Population MeasuMultiple Pass
12/16/2003
30
31
12/16/2003
32
33
Ability to record Origin (hatchery or wild) on
the spreadsheet. Data element will not be
stored in the database and it is not used in
any calculation.
The ability to record the number of jacks, but Need Input: Should this be on the
they should not be included in the AUC
spreadsheet only or should the data
population.
element be added to the database?
Al to re-check on whether Jacks are
used in the AUC calculations.
34
35
36
37
38
Calculation
Multiple Pass Calculations
Redd Count should provide the ability to put
a field on the excel spreadsheet for noting
the disturbance type and count.
For AUC Redd Count, each redd should be
counted once and flagged. This follows the
current handbook for AUC Redd Count.
For Population Measures, AUC is done
exclusively on the Westside.
On the multiple pass there are some
Multiple pass deferred to later
calculations that could be supported in
release
ARIMS. Same for some snorkeling that is
backed up by some electroshocking. (Note:
This needs follow-up investigation).
M
Reviewer Comments
A
B
C
D
E
F
1 ReqI ARIMS MoCategory
SubCategory Component ShortDescription
47 Fish
Population MeasuOne Day Survey Informational Eastside Method
39
Population MeasuOne Day Survey
Field Conditions
41 Fish
40
Population MeasuOne Day Survey Data Elements One Day Survey Data Elements
12 Fish
G
H
DateEntered
DateCompleted
12/16/2003
12/16/2003
12/16/2003
41
42
43
42 Fish
Population MeasuOne Day Survey Informational One Day Surveys
12/16/2003
43 Fish
11 Fish
Population MeasuOne Day Survey Informational Reach Based
Population MeasuOne Day Survey Informational Redd Count Survey
12/16/2003
12/16/2003
13 Fish
Population MeasuOne Day Survey Informational Redd Count Survey Purpose
12/16/2003
55 Fish
Population MeasuPopulation
Data Elements Population Measure Data Elements
12/16/2003
56 Fish
Population MeasuPopulation
Population Measure Data Elements
12/16/2003
57 Fish
Population MeasuPopulation
Population Measure Data Elements
12/16/2003
58 Fish
Population MeasuPopulation
Population Measure Data Elements
12/16/2003
59 Fish
Population MeasuPopulation
Population Measure Data Elements
12/16/2003
60 Fish
Population MeasuPopulation
Population Measure Data Elements
12/16/2003
61 Fish
Population MeasuPopulation
Informational Relative Abundance
12/16/2003
63 Fish
Population MeasuPopulation
Relative Abundance
12/16/2003
66 Fish
Population MeasuPopulation
Informational Survey Duration
12/16/2003
70 Fish
Population MeasuPopulation
Informational Weirs & Traps
12/16/2003
44
45
46
I
LongDescription
For Population Measures, Redd Count is done
occasionally on the Eastside.
System shall provide the ability to record
Field Conditions for all surveys.
Data elements applicable for One Day
Surveys include: Peak (timing code), Redds
(intact, disturbed, total), Adults, Males (by
Hatchery or Wild), Females (by Hatchery or
Wild), Jacks (by Hatchery or Wild), Carcass,
Species.
Peak Surveys should be referred to as One
Day Surveys. The fish handbook should be
updated to reflect this.
One day surveys are reach based.
Redd Count is a part of AUC, but there is
also a separate Redd Count survey. The
Redd Count is done at peak or after peak.
The purpose of the Redd Count is to get a
count of redds along a reach. The data is
typically used to compare density of redds on
a reach from year to year.
For Population Measure Surveys, the ability
to record density per habitat unit (derived
value).
For Population Measure surveys, the ability
to record spawning density (derived value).
J
Comments
Need Input: 1. Is age class
needed? 2. Protocols are needed
for One Day Surveys.
Functionality deferred.
Functionality deferred.
47
48
For Population Measure Surveys, the ability
to record biomass (derived value).
For Population Measure Surveys, the ability
to record population (derived value).
Functionality deferred.
Functionality deferred.
49
50
For Population Measure Surveys, the ability
to record abundance.
For Population Measure Surveys, the ability Functionality deferred.
to calculate length frequency (derived value).
51
52
53
54
55
Abundance is defined as a one time count
(single effort). Repeated efforts over time to
the same stream would provide relative
abundance. Can also compare two different
streams on the same day to provide relative
abundance.
The ability to compare relative abundance
Need Input: What is the output
population numbers between two streams.
needed? A report, a map, a table,
other?
Population Surveys may have duration of one
or more days.
Raw legacy data for weirs and traps will be Functionality deferred.
kept at ODFW; ARIMS should only hold the
summary data.
M
Reviewer Comments
A
B
C
D
E
F
1 ReqI ARIMS MoCategory
SubCategory Component ShortDescription
16 Fish
Population MeasuSpawning SurveyInformational Spawning Surveys
G
H
DateEntered
DateCompleted
12/16/2003
I
LongDescription
Spawning Survey types include: Area Under
the Curve (AUC) including AUC Redd counts
(multiple days), and ODFW Redd Counts
(peak or after-peak - one day).
J
Comments
56
93 Fish
Population MeasuSpawning SurveyInformational Survey Method
12/16/2003
There are four reach based survey types for Need Input: 1. Protocols are
needed for all types except AUC. 2.
Spawning Surveys: Redd, AUC, Emap
Are these the correct survey types?
(OWEB), and One Day Surveys.
97 Fish
Population MeasuWeirs
Informational Sites
12/16/2003
98 Fish
Population MeasuWeirs
Data Elements Surveys
12/16/2003
44 Fish
Population Measures
Data Elements Other Pop Survey Data
12/16/2003
54 Fish
Population Measures
Data Elements Population Measure Data Elements
12/16/2003
Weir data is site based data that pertains to
a sub-watershed or reach.
The ability to store the summary data from
adult and juvenile traps.
The system will support the entry of other
population survey data.
For Population Measure Surveys, the ability
to record length/weight (measured value).
72 Fish
Presence AbsenceReach Type
Informational Absence Not Verified
12/16/2003
Absence Not Verified is described as "best
professional judgment suggests absence."
73 Fish
Presence AbsenceReach Type
Informational Absence Not Verified
12/16/2003
108 Fish
Presence AbsenceReach Type
Fish Anad/Verification/Run/Species
107 Fish
Presence AbsenceReach Type
Fish Resident/Verification/Species
110 Fish
Presence AbsenceReach Type
Pres Abs Run Codes
109 Fish
Presence AbsenceReach Type
Pres Abs Verification Status Codes
84 Fish
Presence AbsenceReach Type
Informational Presence Not Verified
12/16/2003
Absence Not Verified is not protocol
dependent. Value for protocol should be
"Other."
System shall support entry and update of
anadromous populations reaches by
run/season and species (including
Ecologically Significant Units).
System shall support entry and update of
resident population reaches by verification
status and species.
The run codes for Anad Fish are Spring,
Summer, Fall, Winter and Other.
The verification status codes for Presence
Absence reaches are: Presence Verified,
Presence Not Verified, Absence Not Verified,
Absence Verified.
Presence Not Verified is described as "best
Need Input: Approval is needed
professional judgment suggests presence." for the Presence Absence protocols
from field office fish biologists.
85 Fish
Presence AbsenceReach Type
Informational Presence Not Verified
12/16/2003
Presence Not Verified is not protocol
Need Input: Approval is needed
dependent. The value for protocol should be for the Presence Absence protocols
"Other".
from field office fish biologists.
86 Fish
Presence AbsenceReach Type
Informational Presence Verified
12/16/2003
Presence Verified is described as "field
verified/observed by a reputable fish
biologist."
87 Fish
39 Fish
Presence AbsenceReach Type
Presence AbsenceSite Type
Informational Presence Verified
Incidental Data
12/16/2003
12/16/2003
Presence Verified is protocol dependent.
A site type is needed to represent incidental
data.
57
58
59
60
Functionality deferred.
Functionality deferred.
Functionality deferred.
61
Need Input: Approval is needed
for the Presence Absence protocols
from field office fish biologists.
62
63
64
65
66
67
68
69
70
71
72
Need Input: Approval is needed
for the Presence Absence protocols
from field office fish biologists.
Follow up needed: Is this really
needed? If so, more details are
needed.
M
Reviewer Comments
A
B
C
1 ReqI ARIMS MoCategory
94 Fish
Study Site
D
SubCategory
E
F
Component ShortDescription
AREMP Study Sites
G
H
DateEntered
DateCompleted
12/16/2003
73
95 Fish
Study Site
EMAP Study Sites
12/16/2003
100 Fish
FWS/NOAA Fisheries Matrix
12/16/2003
105 Fish
Telemetry Surveys
12/16/2003
New Surveys
12/16/2003
15 Site MainteSite Type
Redd Sites
12/16/2003
17 Site MainteSite Type
Revise Fish Barrier Site Type
74
75
76
40 ODFW
Data Import
77
78
79
96 Water Qua Temperature
80
Data Element Spawning Time Period
12/16/2003
I
LongDescription
The ability to determine where AREMP data
has been collected (study sites).
J
M
Comments
Reviewer Comments
Need Input: The user group
needs to confirm this is a business
need.
The ability to record a Study Site type of
Need Input: Need confirmation
OWEB Coho Monitoring (EMAP). The result is that this is a business need.
redds per mile.
The ability to complete the FWS/NOAA
Follow up needed: the details for
Fisheries matrix.
this requirement need further
investigation.
Deferred
The ability to record summary data for
telemetry surveys.
Ability to enter new ODFW surveys
Follow up needed: the details for
(completed by BLM employees) into ARIMS. this requirement need further
investigation.
A site type is needed to mark location of
redds.
To be determined.
Follow up needed: User group
needs to review and possibly revise
existing fish barrier site types in
ARIMS.
The ability to record if a Water Temperature Will be part of expected
Temperature revision.
Survey is completed during spawning time
period.
IB-OR-2004-069-Attachment 1
ARIMS FISH USER REQURIREMENTS MEETING ATTENDEES/INVITEES
District Attendees:
Al Doelker
State Office
Chip Clough
Roseburg
Scott Lightcap
Roseburg
Aimee Hoefs Coos Bay
Scott Snedaker
Klamath Falls RA
Brent Ralston
Prineville
Cynthia Weston
Burns
Invitees not able to attend:
Bill Hudson,
Leo Poole,
Alan Munhall
Bob Bessey
Bob Ruediger
Joe Kelly
Cynthia Tait
Coos Bay
Eugene
Lakeview
Medford
Salem
Spokane
Vale