z General Comments – System Requirements
z Main Menu
¾ Additional Information
z Inventory Module
¾ Inventory Data Entry
z Inspection Module
¾ Inspection Data Entry
z Investigation Module
¾ Investigation Data Entry
z Reporting Function
z Export Function
z Administration Function
Disclaimer:
This Outfall Database was originally developed for internal use only by the
Northeast Ohio Regional Sewer District. It was adapted to share with northeast
Ohio communities in 2003 to support NPDES Phase II Permit requirements and
further adapted to share as part of the IDDE Manual. The District makes no
warranties, expressed or implied, with respect to the use of this outfall database
to support NPDES Phase II Permit requirements or for any other specific purpose.
The District and its employees expressly disclaim any liability that may result from
the use of this database.
For More Information - Contact:
Mary Maciejowski or Jeffrey Duke
(maciejowskim@neorsd.org
Northeast Ohio Regional Sewer District
3900 Euclid Avenue
Cleveland, Ohio 44115-2506
(216) 881-6600
or dukej@neorsd.org)
Page 2 of 23
Outfall Database
User Guide – IDDE Manual – July 2006
General Comments – System Requirements (TOC)
ySoftware Version – The NEORSD Comprehensive Outfall Database (COD)
needs to run on Microsoft Access 2000 or later version.
yResolution/Monitor Size – The recommended screen resolution setting is
1024x768. Also, to minimize user scrolling throughout the database screens, a
17” monitor or greater is recommended.
yFile Location – The COD should be loaded onto a centralized file storage
location (hard drive or server) with at least 1 Gb of available memory. This will
allow for the addition of photos and other graphical files.
y File Structure
¾
Root Directory
¾
Subdirectories
– e.g. C:\IDDEManual_OutfallDatabase\ (User Identified)
Documentation – Required for the Main Menu to access associated
documentation files.
Extra – Required, along with file mdac_typ.exe to allow for exports
Images – Required for individual database modules to access files.
Subdirectories are automatically created by the database as the user
creates outfalls and adds images. Examples of images subdirectories
that may be created:
•
ACMB
– Abrams Creek Main Branch root subdirectory for the stream
– Abrams Creek Main Branch.
♦
ACMB0010
ACMB0020
♦
– subdirectory for outfall ACMB0010
– subdirectory for outfall ACMB0020
Storm Sewer Maps – Required for Main Menu to access storm maps –
these maps are added by the user into this specific subdirectory (PDF
Version only).
Watershed Maps – Required for Main Menu to access watershed maps -
these maps are added by the user into this specific subdirectory (PDF
Version only).
¾
User-defined subdirectories
– The user is able to create subdirectories as
necessary to store related files. These subdirectories will not be linked to
the outfall database.
OutfallDB_UserGuide_IDDEManual_V1.doc Page 3 of 23
Outfall Database
User Guide – IDDE Manual – July 2006
yAdobe Acrobat Reader – In order to access the watershed maps and database
documentation, the user will need to have Adobe Acrobat Reader (Version 5.0
or greater) installed on their computer.
yDatabase Setup – See Administration Function - Pg. 21 for information on how
to login to the database an administrator.
¾
User Setup –
The Database Administrator will need to setup users for the
database
¾
Receiving Streams –
The Database Administrator will need to setup streams
for use by the Outfall Database. See the corresponding stream naming
convention document for guidelines on how to identify (“name”) streams for
use by this database
¾
Communities
– The Database Administrator will need to add the communities
as necessary for the database. The communities will be used by the
inventory module’s data entry form
Page 4 of 23
Outfall Database
User Guide – IDDE Manual – July 2006
Main Menu (TOC)
The Main Menu (shown below) will automatically open upon launching the Outfall
Database (IDDE_OutfallDatabaseV1.mdb). This menu can be used to access the
Inventory, Inspection and Investigations modules.
Main Toolbar
The Main Toolbar (shown below) is set to show on top of the database. This
toolbar will allow the user to access all of the menus. Additional module-specific
functions will appear on this toolbar as the user navigates through the database.
Page 5 of 23
Outfall Database
User Guide – IDDE Manual – July 2006
Outfall Inventory Module (TOC)
• List all Outfalls for Stream – all users can use this function.
• List all Outfalls for Community – all users can use this function.
• Create a new Outfall Inventory record – users must have Administrator (Data
Entry) rights and login through the administrator menu – see pg. 21.
The user can access additional information from the functions at the bottom of
the Main Menu (see graphic below).
•Explore Watershed Maps – all users can use this function.
¾
Available Watershed Maps –
There are 2 example watershed map “books” to
demonstrate some of the types of maps that users can add for additional
information.
¾
Adding Watershed Maps –
Users can add a Watershed Map by placing the
map file (in PDF format) in the Watershed Maps subdirectory.
•Explore Storm Sewer Maps – all users can use this function.
¾
Available Storm Sewer Maps –
There are 2 example “storm sewer maps”
demonstrate some of the types of maps that users can add for additional
information.
¾
Adding Storm Sewer Maps -
Users can add a Storm Sewer Map by placing
the map file (in PDF format) in the Storm Sewer Maps subdirectory.
•View Data Documentation – all users can use this function.
Available Data Documentation
¾
Blank Inventory Form (for Field Data Collection)
Blank Inspection Form (for Field Data Collection)
Blank Investigation Form (for Field Data Collection)
Stream Designation Guidelines
User Guide – OutfallDB_UserGuide_IDDEManual_V1.doc
¾
Adding Data
Documentation – Users can add a data documentation files by
placing the files (in PDF format) in the Documentation subdirectory.