E.H. Pechan & Associates, Inc.

Slides:



Advertisements
Similar presentations
ASIAES Project Overview Satellite Image Network for Natural Hazard Management in ASEAN+3 region Pakorn Apaphant Geo-Informatics and Space Technology Development.
Advertisements

AOC Services EPA Analytical Operations/Data Quality Center August 14 th, 2001 US Navy/NAVSEA Training Session.
Attribution of Haze Workgroup & Technical Support System Report Fire Emissions Joint Forum Meeting July
Attribution of Haze Phase 2 and Technical Support System Project Update AoH Meeting – San Francisco, CA September 14/15, 2005 Joe Adlhoch - Air Resource.
TRI State Data Exchange …The Best Thing Since ….!.
ICS (072)Database Systems: A Review1 Database Systems: A Review Dr. Muhammad Shafique.
Chapter 6 Database Design
17-Oct-07 Spatial Engineering, Inc.1 Installation Management Agency Korea Region Office KOROGIS CADD/GIS Interoperability Presented By: Anna Austin, GISP.
16 months…. The Visibility Information Exchange Web System is a database system and set of online tools originally designed to support the Regional Haze.
RIAS PHASE II Oracle General Ledger, Financial Reporting and Data Warehouse 6/27/2015.
Western Regional Air Partnership Emissions Database Management System CERR Workshop San Francisco May E.H. Pechan & Associates, Inc.
ArcGIS Workflow Manager An Introduction
Business Processes and Workflow How to go from idea to implementation
Western Regional Air Partnership Emissions Database Management System January 2004 WRAP Technical Summit Phoenix, Arizona E.H. Pechan & Associates, Inc.
1 July 12, 2006/10a Fire Emissions Tracking System White Paper Fire Emissions Joint Forum July 11-12, 2006 Portland, OR Dave Randall, Air Sciences Inc.
Western Regional Air Partnership Emissions Database Management System Presentation to Fire Emissions Joint Forum Las Vegas, Nevada December 09, 2004 E.H.
Fall Technical Conference Regional Haze SIP Development Snowbird, Utah September , 2002.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
IST 210 Database Design Process IST 210 Todd S. Bacastow January 2005.
Week 4 Lecture Part 3 of 3 Database Design Samuel ConnSamuel Conn, Faculty Suggestions for using the Lecture Slides.
Needs Assessment for Evaluation and Design of an Emissions Data Reporting, Management, and Tracking System.
Tribal Air Quality “Tools of the Trade” Lydia Scheer, ITEP.
Oracle9i Performance Tuning Chapter 1 Performance Tuning Overview.
Emissions Inventory Case Study Kris Ray, Confederated Tribes of the Colville Reservation.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
4 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved. Computer Software Chapter 4.
Traffic Management Transit Management Emergency Management Fixed Point-to-Fixed Point Communications Roadway Toll Administration Remote Traveler Support.
Response to WRAP Air Managers Committee Memo “Request for Cost Estimates” April 6, 2009 WESTAR Council.
Presented by: Eastern Research Group, Inc. September 27, 2005 Status Report to the WRAP Emissions Forum EDMS Testing.
1 Brian Finneran, Oregon DEQ WRAP IWG Meeting, Portland August 2006 Suggested Changes to IWG Section 308 SIP Template.
Condor Technology Solutions, Inc. Grace Performance Chemicals HRIS Intranet Project.
Emission Inventory Input Format Eastern Canadian Premiers/New England Governors Conference Data Exchange Workgroup Gregory Stella U.S. Environmental Protection.
E.H. Pechan & Associates, Inc. 1 EDMS Purpose Regional Haze Rule Implementation Performance Monitoring Region-Wide Emission Inventory Analysis of Collected.
Western Regional Air Partnership Emissions Database Management System Community Modeling and Analysis System Center Models – 3 User’s Conference October.
TSS Project Update WRAP Technical Analysis Forum Boise, ID May 22, 2007.
WRAP Activities Overview §308 Technical Work Outline June 3, 2003.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
IST 210 Database Design Process IST 210, Section 1 Todd S. Bacastow January 2004.
E.H. Pechan & Associates, Inc. Emissions Data Management System for the Western Regional Air Partnership Presentation to the WRAP Emissions Forum April.
Emissions Forum 2003/2004 Budget July 2, Emissions Forum 2003/2004 Budget Review status of 2003 projects Completed In process Not started Thoughts.
Architecture Review 10/11/2004
Overview of WRAP Emissions Projections
Computer Applications
Database Development (8 May 2017).
ITEC 3220A Using and Designing Database Systems
Inter-RPO Emissions Inventory Warehouse System Update
ISO/IEC Software Testing
Database Systems: Design, Implementation, and Management Tenth Edition
Developing Information Systems
EIN 6133 Enterprise Engineering
Chapter 6 Database Design
Sponsored by the RMS Center
An EDI Testing Strategy
David Holoman E.H. Pechan & Associates, Inc.
Tim Roman, College of Continuing Education Bob Rubinyi, UM Extension
Experience with an IT Asset Management System
TEISS Case Project Introduction
Model Information Exchange System - MIXS
Model Information Exchange System - MIXS
Database Administration
WP 4 - Revision of Natura 2000 dataflow
Western Regional Haze Planning and
Presenting Results using TEISS and Emission Inventory Reports
EIDE System Requirements and Specification Documents
CAD DESK PRIMAVERA PRESENTATION.
Air Resource Specialists, Inc. July 23, 2004
Reportnet 3.0 Database Feasibility Study – Approach
Fire Emissions Joint Forum February 9, 2005
Technical Review Workshop
Web Service Requirements for WISE Data Exchange
Presentation transcript:

E.H. Pechan & Associates, Inc. Western Regional Air Partnership Emissions Database Management System CERR Workshop San Francisco May 11-12 2004 E.H. Pechan & Associates, Inc.

Project Design and Status

Organization

Software/Hardware Development Plan Organization Purpose Scope Schedule Communications Software/Hardware Development Plan

Purpose

Region-Wide Emission Inventory Analysis of Collected Data Purpose Regional Haze Rule Implementation Performance Monitoring Region-Wide Emission Inventory Analysis of Collected Data Emissions Comparisons Emissions Trends Analysis

Scope

Database Organization Web-Based Analysis Interface Batch Data Take On Scope Database Organization Web-Based Analysis Interface Batch Data Take On Outputs/Data Extracts Administrative Module/DBA Functions

Database Organization All Sectors Multiple Years Multiple Types Scope Database Organization All Sectors Multiple Years Multiple Types Data Versioning

Web-Based Analysis Interface Public Scope Web-Based Analysis Interface Public GIS Query/View of Locked Data Preformatted Reports Preformatted Data Extracts Secure GIS Query/View of Working Data Ad-hoc Reports/Extracts Data Import/Export

QA/QC Procedures (QAPP) Scope Batch Data Take On NIF Version 3.0 WRAP EDMS Format TEISS QA/QC Procedures (QAPP) Recursive QA/QC Gap-Filling/Data Adjusting

Scope Outputs/Data Extracts NIF Version 3.0 SMOKE IDA Ad-Hoc Tables/Summaries

Administrative Module/DBA Functions User Management/Security LISTSERV Scope Administrative Module/DBA Functions User Management/Security LISTSERV Ad-Hoc Functions QA/QC Report Development Analysis

Multiple Deliverables One Year Timeline Scope Project Attributes Nine Tasks Multiple Deliverables One Year Timeline

Scope/Project Flow Systems Analysis and Design QA/QC Processes Reports Hardware - Home Location Routine Operations Training Build and Document Maintenance and Support Test and Refine Initial Data Load

Schedule

Communications

Software and Hardware Development Plan

Software and Hardware Development Plan Introduction Data Requirements Functional Requirements Hardware Development Plan Implementation Plan Administration

SWHWDP – I. Introduction System Requirements Pollutants

SWHWDP – II. Data Requirements Conceptual Model

SWHWDP – II. Data Requirements Sources

SWHWDP – II. Data Requirements Biogenic/Dust Overrides

SWHWDP – II. Data Requirements Point, Area, On-Road Mobile, Non-road Mobile: Covered by NIF submittal

SWHWDP – II. Data Requirements Fire Five Fire types Emissions Calculated in EDMS EDMS-specific reporting format Episodic data Geographic data

SWHWDP – II. Data Requirements NAR/County Emissions Accounting Two overlap types EDMS Method to report type Default handling Accommodate EPA’s modifications to NIF

SWHWDP – II. Data Requirements Data Versions

SWHWDP – II. Data Requirements QC – Edits Consistent with NIF Tracking of EDMS-specific EDITS QA – Five-step process Generate QA Plan Overview ID and Define Methods Develop Strawperson for gap-filling Define data access and operational management Develop Phase II project list

SWHWDP – III. Functional Requirements Architectural Overview

SWHWDP – III. Functional Requirements Import Now Access Text Soon XML CDX

SWHWDP – III. Functional Requirements Interface

SWHWDP – III. Functional Requirements GIS Interface

SWHWDP – III. Functional Requirements Fire Calculation

SWHWDP – III. Functional Requirements Reporting Standard Reports Summary Top 10 CAC Pre-trigger SO2 Ad-Hoc Reports

SWHWDP – III. Functional Requirements Exporting Query/Report-Based Model-Ready Special Analysis RPO Data Exchange Format

SWHWDP – III. Functional Requirements Security Login-based Public/Data Provider Special Access DBA User’s Manual

SWHWDP – IV. Hardware Requirements Sizing 18 GB? Bandwidth MB/day vs. GB/day Processing Oracle Server has 64 CPUs and 64GB of RAM Back-Up Recovery, Physical Security “Best Practices” organization

SWHWDP – V. Implementation Plan Test Plan – Functional Accuracy and Usability Testing Levels Program, function, subsystem, system Testing Categories Objective, Stress, Volume, etc. Specification of Elements Purpose, Environment, Assumptions, etc. Economy

SWHWDP – V. Implementation Plan Training Lecture + Hands-on Specific to User-class Data Providers, Planners, Viewers Covers Feature Set Login, Submission, Analysis, Reporting

SWHWDP – V. Implementation Plan Maintenance Support Web-based E-mail Telephone

SWHWDP – V. Implementation Plan Data Take-on July 1, 2004 Acceptance Testing Strategy Three-month review Critical Success Factors Oversight DBA, DA EDMS Oversight Committee

SWHWDP – VI. Administration, Appendices Progress Reports A - Data Dictionary and Validations B – Fire White Paper C – Standard Report Layouts D – Sample Use Cases E – Sample Features F – Phase II Concepts G – EDMS Input H – NIF / IDA Data Translation I – RMC Biogenic Mapping J – RPOX Mapping Strategy

End of Presentation