Evaluation of Existing Fire Tracking Systems FEJF Meeting Day 1, 945a – Seattle, WA.

Slides:



Advertisements
Similar presentations
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
Advertisements

1 WRAP Fire Emissions Tracking System for Air Quality Planning, Tracking, & Decision Support December 6, 2007 Tom Moore | Shawn McClure | Dave Randall.
Attribution of Haze Phase 2 and Technical Support System Project Update AoH Meeting – San Francisco, CA September 14/15, 2005 Joe Adlhoch - Air Resource.
Chapter 2.
Mapping Flowchart. Frame the Goal: Identify key elements Identify Need/Goal Form a Team Budget impact? Identify Roles within the Team Set Goals Who will.
EURIDICE project Evaluation of image database use in online learning environment 11/
1 California State University, Fullerton Chapter 13 Developing and Managing Information Systems.
Effective systems development requires a team effort from stakeholders, users, managers, systems development specialists, and various support personnel,
Systems Development. Systems Development Life Cycle (SDLC) A “baseline” process for the development of application systems Contains a comprehensive set.
1 Info 1409 Systems Analysis & Design Module Lecture 5 - Feasibility HND Year /9 De Montfort University.
Fundamentals of Information Systems, Second Edition
Systems Development Life Cycle
7.2 System Development Life Cycle (SDLC)
Keys Chapter 8 Database Design for Mere Mortals. Why Keys Are Important They ensure that each record in a table can be properly identified. They help.
WRAP Technical Support System Project Update AoH Call October 19, 2005.
Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher (2009) with material from: IEEE Standard, Daniel Amyot.
Conducting Market Research Teresa Anthony Level II PIP September 9, 2004.
1.Database plan 2.Information systems plan 3.Technology plan 4.Business strategy plan 5.Enterprise analysis Which of the following serves as a road map.
COCOMO-SCORM: Cost Estimation for SCORM Course Development
Overview of the Database Development Process
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Environmental and Cultural Data Products
SYS364 Evaluating Alternatives. Objectives of the Systems Analysis Phase determine, analyze, organize and document the requirements of a new information.
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.
MSS Technologies and the AIIM Grand Canyon Chapter present: Electronic Document Management System Needs Analysis.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
PHASE II PROJECT Day 1 – 3:15p PHASE II PROJECT -- Ag Burning – Integration of QC responses -- NIF Format -- Plume Characteristics Update -- Next Steps.
1 WRAP Fire Tracking Systems Draft Intent of WRAP FTS Policy – Assist states/tribes to address emissions inventory and tracking associated with fire in.
1 WRAP Policy Fire Tracking Systems Draft December 9, 2002 FEJF Meeting December 10-11, 2002 Jackson, WY.
WEB-BASED DEAL LOG DATABASE PROJECT REVIEW Presented to SHEPHERD VENTURES By Sylvia Szubrycht.
Together.Today.Tomorrow. The BLUES Project Karen C. Fox, PhD Chief Executive Officer.
Module 13 Implementing Business Continuity. Module Overview Protecting and Recovering Content Working with Backup and Restore for Disaster Recovery Implementing.
Systems Analysis and Design
COMP 208/214/215/216 – Lecture 8 Demonstrations and Portfolios.
Systems Life Cycle A2 Module Heathcote Ch.38.
Water Resource Monitoring for Assessment and Adaptation to Droughts: California Central Valley and Africa Nile Basin Norman Miller 1, Charles Brush 2,
1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
REGIONAL COORDINATION GUIDANCE DOCUMENT Status Report Debra Wolfe November 30, 2005 WRAP FEJF Meeting Seattle, WA.
November 2, 2005San Diego, California1 Calculation Tool for Estimating Projected Emissions - Methods Roll Out – (Day 2 – ) Phase III/IV Project.
1 Evaluation of Existing Fire Tracking Systems FEJF Meeting Day 1, 1030a – Albuquerque, NM.
Copyright © 2014 by Educational Testing Service. All rights reserved. Influencing Education: Implementing Online Reporting Systems to Support Assessment.
Overview of WRAP FEJF Work Products WRAP Workshop on Fire, Carbon, and Dust May 23-24, 2006 Sacramento, CA Darla Potter (WDEQ) & Mark Fitch (USFS)
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Renewable Energy Transmission Initiative 2.0 Organizational Structure and Work Plan California Energy Commission and California Public Utilities Commission.
1 Incorporating Smoke Management Plans into SIPs: THE OREGON 309 SIP Brian Finneran Oregon Department of Environmental Quality Smoke Management Planning.
Denver 2004 TGP1 PM2.5 Emissions Inventory Workshop Denver, CO March 2004 Thompson G. Pace USEPA Emissions Estimation for Wildland Fires.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Test 2 Review Chapters 5, 6, 7, 8, 10 & Project Mgt.
309/308 Technical & Policy Overview Fire Emissions Joint Forum March 10-11, 2004 San Diego, CA.
Fundamentals of Information Systems, Third Edition2 An Overview of Systems Development: Participants in Systems Development Development team –Responsible.
IFS310: Module 9 Systems Design - Procurement Phase - Software Design.
Status Report on the Role of Ammonia in the San Joaquin Valley December 11, 2003 Air Resources Board California Environmental Protection Agency.
Data Management Alternatives. Available Options Online data collection tool (available in August) Data management system formerly known as AFI 2 Other.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
CHAPTER ELEVEN Information System Development and Programming Languages Copyright © Cengage Learning. All rights reserved.
Systems Development Life Cycle
IS Development Methodology
Software Development Center California Scotland Benchmark Report 2016
Fundamentals of Information Systems, Sixth Edition
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
Systems Design, Implementation, and Operation
Product Name.
Annual Emission Goals for Fire
Phase 1 – 2002 Fire Emissions Inventory
Product Name.
Systems Development Life Cycle
Information Systems Development (ISD) Systems Development Life Cycle
Andy Ginsburg, Oregon DEQ
Presentation transcript:

Evaluation of Existing Fire Tracking Systems FEJF Meeting Day 1, 945a – Seattle, WA

Project Overview Is there an existing FTS system, with few or minor modifications, will satisfy the WRAP’s requirements for an FTS. Web-based and historical systems (e.g., wildfire systems) to be reviewed. Primary emphasis of this project is on real- time data import and export capabilities. Evaluation will be made from the perspective of an FTS user.

Project Goals Evaluate existing FTS and provide: –A feasibility assessment of existing systems. –An analysis of modifying each system to include WRAP needs. –Estimate resources needed to modify the system to meet the required elements for tracking prescribed fires.

Systems to Evaluate San Joaquin Valley Smoke Management System - California Airshed Management System (formerly RAZU) - Montana/Idaho Smoke Management Database - New Mexico Nez Perce Tracking System South Carolina Florida USDA Smoke Management System

Project Methodology Develop evaluation chart that includes: –Basic data elements –System information –Front- and Back-end applications –Indexing and reporting –Optional modules –Interface/exchange of data Conduct interviews with current FTS users/managers. Feasibility assessment of 7 systems. Shortlist and assess 2 systems –Necessary modifications –Cost to modify & host

Cost Estimate Primarily based on input from FTS managers. Cost estimate to include: –Development hours –Additional hardware costs –Ongoing system costs

Recommendations What existing FTS would work best “as-is” for the WRAP’s FTS? What existing FTS would require the least amount of modification to work well as the WRAP FTS?

Recommendations What combination of existing FTS, technical modifications, and exceptional features from other FTS would comprise a WRAP FTS with the most complete set of features and capabilities? Rather than starting from an existing FTS, is there a better way for the WRAP to proceed with building the WRAP FTS?