1. VDOT’s Environmental Data Management System 2 Environmental Division August 10, 2015.
-
Upload
amice-hart -
Category
Documents
-
view
221 -
download
3
Transcript of 1. VDOT’s Environmental Data Management System 2 Environmental Division August 10, 2015.
3
Introduction of Representatives
Environmental Staff:Angel Deem – Division Director
Geraldine Jones – Data Management, System Administrator, GIS Coordinator
IT Staff/Applications Groups:David Choi – Data Management, Programmer
Systems Engineering Enterprise GIS
Development History
6
1997-98 – Environmental GIS Analysis
2001 – GIS Integrator Deployed
2002 – CEDAR Requirements Analysis Begins
2003 – CEDAR Phase 1 Deployed
2004 thru Present – Maintenance & Enhancements
2006 thru 2008 – CEDAR Phase 2
2011 – GIS Integrator 2.0 deployed
Overview of Functional Capabilities
Common tool for managing/documenting environmental activities, decisions & commitments
Centralized “place” for environmental staff to enter and retrieve data
Tool to find information on environmental progress & involvement on a project
Integrates use of GIS dataCaptures project historyHandles all project types – construction, maintenance, capital outlay, etc.
Standard and ad-hoc reporting• Through application screens – project file, search screens, query panels
7
CEDAR’s Benefits
• One tool for all environmental activities
• Increased accountability
• Satisfaction of mandates (Strategic Plan, Commission on Transportation Policy, etc.)
• Streamline interagency coordination
• Documentation of environmental decisions
• Communication of environmental commitments
• Communication of project status
• Consolidate/integrate applications (IPM, GIS, Data Warehouse)
• Support more accurate project estimates
• Provide basis for program management and trend analysis• Reduce time for advancing projects
8
CEDAR Time Savings
9
Activity Code
ActivityFY 03Hours/Proj
FY 11Hours/Proj
Hours Saved
FY 03Hours/Proj
FY 11Hours/Proj
Hours Saved
34301 PCE 5.6 5.5 34302 CE 105 85
34322
State Environmental Review Process (SERP)
25 19
25 19
35405
Biological Assessment /Endangered Species Surveys
56.9 20
56.9 20
35501Environmental Permit Determination
3.6 3.4
3.6 3.4
36007
Cultural Resources Quick File Check/ Clearance of Projects with Minimal Impact
4.1 2.75
4.1 2.75
39500
Hazardous Materials Review of SERP and SERP-Exempt Projects
5.3 3.75
5.3 3.75
100.5 54.4 46.1 199.9 133.9 66
Hours per project FY03 and FY11 by Environmental project activity showing time saved in hours for project with PCE and CE.
SPR Expenditures
10
Year Expenditures
2003 $124,304.90
2004 $651,759.64
2005 $246,096.04
2006 $137,482.63
2007 $122,551.61
2008 $162,233.19
2009 $3,005.82
Year Expenditures
2010 $45,427.07
2011 $109,093.05
2012$0.00
2013 $118,180.00
2014 $16,052.50
2015 $12,000.00
$2,000,000
SPR (State Planning & Research Funds)
Active Directory
DataWarehouse
CEDAR
App ServerJRUN4/IIS
DB Server Oracle
GIS Integrator
Spatial DataFrom ENV Resource Agencies
Spatial Data from VDOT
Spatial Data from web services
Project Details and Schedule
VDOT IPMProject ManagementActive Directory
used for contact information and Windows Authentication
CEDAR
App ServerJRUN4/IIS
DB Server Oracle
• JAVA Web Based Application• Build in 2003 • Receive regular enhancements/update• Using the following
• JSP, Servlets, HTML, XML, XSL, Javascripts• Data Access
• Oracle store procedures• Oracle UDT (User define types)• OCI client
• Build in DMS• All documents are store in database as BLOB
CEDAR
App ServerJRUN4/IIS
DB Server Oracle
• 3rd Party Software• ITEXT – PDF Generation• RoboHelp – HTML Help• JSpell – Spell checker
• JavaScript Libraries• AJAX• MooTools• JQuery• Knockout.JS
• Client• IE 5 and above
CEDAR
App ServerJRUN4/IIS
DB Server Oracle
• Database• Oracle 11G Enterprise Edition Release 11.2.0.3.0 - 64bit • Linux Server with 4 processors and 32 GB RAM
• Application Server• JRUN4/IIS• JAVA – JDK 1.5• Windows Server 2003
• Next Step: upgrade to Windows Server 2008 R2• Current Production configuration - On Virtual Server – Quad-Core AMD Processors with
4 GB RAM.
Sharing CEDAR
Status of CEDAR and sharing the concept Agreement Process for packaging/LOE/requirements
19
Process for packaging/LOE/requirements
1. Take back up of production database and application 2. Setup a new instance of the application3. Setup a new instance of the database4. Remove all of the data not being shared
Approximately 240 tables in the system currently not including history5. Replace Integration MV and Views to with temporary tables
This is so that packages would compile6. Disable all nightly jobs for integration 7. Disable non-core functionality in the application8. Create example projects9. Test and make sure system is functioning correctly10. Have SE take a backup copy of the updated database11. Make backup copy of the application12. Create Installation documentations
20
Sharing the code
Package • Database• Source code• Software
• Eclipse• Java JDK• JRun4• Sqldeveloper
• Docs
LOE• 2 weeks
21
Sharing the code
Requirements• Database
– Oracle version – 11.2.0.3• Application
– Window Server 2003 R2 or 2008 R2» 2 or more Gigs of Ram
– JRun4 with updater 7– IIS 6 and above– JAVA 1.5 or 1.6– Oracle Client
22
CEDAR Demo August 10, 2015
3:00 to 4:45
Geraldine JonesCEDAR AdministratorVDOT EnvironmentalPhone: 804-786-6678
23
David ChoiCEDAR Programmer
VDOT ITPhone: 804-371-7865
Demonstration of CEDAR (Virginia)Geraldine Jones and David Choi, VDOT
24
CEDAR User interface: contracts, admin (roles/permissions/assignments), projects, etc. CEDAR Project workflow GIS analysis Environmental Review System Administration
Enhancing/maintaining CEDAR Change management > process/tools/challenges
CEDAR User Interface – Video 1
CEDAR UI• Announcements• Alerts• Project search• Common Functions• Links• Projects • GIS • Reports• Documents• Contracts• Admin • Help
GIS• VDOT admin boundaries • Basic functionality
ADMIN • Managing user account• Roles/Permissions• Default assignments• LOV’s
26
CEDAR Projects – Video 2
Projects • Process of creating a new project• Saving• Digitizing a project shape• Submitting• Activating
27
GIS Analysis – Video 3
GIS Analysis/Reporting• Opening a project shape• System wide buffers• Reporting• Mapping• Exporting the shape
28
Environmental Review – Video 4
• IPM Activities • Tasks• Forms list
• Example: NEPA CE Form• Document Management System
• Distribution list• Journal• Assets
29
Administration – Video 5
• LOV’s• Distribution Lists• Logs• DB Reports• Project Status – IPM• Document Retention
30
Enhancing/maintaining CEDAR
Process• User submits a change request with CEDAR’s change request form.• Change request is sent to the CEDAR Inbox• CEDAR Admin reviews the request and enters into Quality Center(defects
and enhancements management tool)• Defects/enhancements get assigned to a developer for evaluation and
LOE estimate• Depending on LOE, the defect is approved by CEDAR Admin or go through
CMB process for approval• Developer begins work once item is approved
Environments• Development• Test• UAT• Production
32
Enhancing/Maintaining CEDAR
Release schedule• About once every couple months• Unless emergency patches are needed
Maintenance• Database/Application backup schedule
– Database: preform a nightly hot backup– Application: NG backup VM nightly– All source codes and database scripts are also store in TFS
• Storage– Due to DMS documents store in database, dba have to monitor disk
space and add data files as necessary.» Database: 400 Gigs» 360 Gigs used by DMS
– Benefits» Less IO errors» Ease of transaction handling
33
Enhancing/maintaining CEDAR
Reliability• System is very stable• Required little maintenance other than your normal enhancements/bug
fixesDevelopment Tools
• IDE: Eclipse, Sql Developer• Web: Fiddler and other script debuggers• Change Request: HP Quality Center• Source Control: CVS, TFS
Challenges• Required working knowledge of all different technologies being
implemented• JRun4 doesn’t integrate with Eclipse, it make debugging more difficult• Need to be aware of dependencies in the application, because of
information being share between modules• Standards not strictly enforced• Do not have direct access to production server makes debugging difficult
34
Questions?
Geraldine JonesCEDAR AdministratorVDOT EnvironmentalPhone: 804-786-6678
35
David ChoiCEDAR Programmer
VDOT ITPhone: 804-371-7865
Where CEDAR is in 2015
• Maintenance• Small enhancements• Commitments tracking functionality completed• Rewriting
• .NET• Request funding• Organizing rewrite planning groups/User Advisory
Committee/Steering Committee
36
Questions?
Geraldine JonesCEDAR AdministratorVDOT EnvironmentalPhone: 804-786-6678
37
David ChoiCEDAR Programmer
VDOT ITPhone: 804-371-7865