Three State Data Warehouse 1 Cassie Archuleta Shawn McClure Tom Moore June 20,

Slides:



Advertisements
Similar presentations
Making the System Operational
Advertisements

State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Compare and contrast the terms ‘phases’, ‘steps’, ‘techniques’, and ‘deliverables’ as used in systems analysis & design.
Attribution of Haze Phase 2 and Technical Support System Project Update AoH Meeting – San Francisco, CA September 14/15, 2005 Joe Adlhoch - Air Resource.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Summer IAVA1 NATIONAL INFORMATION ASSURANCE TRAINING STANDARD FOR SYSTEM ADMINISTRATORS (SA) Minimum.
Three-State Air Quality Study (3SAQS) Three-State Data Warehouse (3SDW) 3SAQS Technical Scope of Work: Tom Moore, WESTAR/WRAP on behalf of University.
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Chapter 3: The Project Management Process Groups
Western Air Quality Data Warehouse Website Development, Documents, Projects 3SAQS Technical Workshop, CIRA, Fort Collins, CO Feb 25, 2015.
OHT 6.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Development plan and quality plan objectives The elements of the development.
3SAQS Data Warehouse Update October 10, 2014 CIRA - Fort Collins, CO.
Development plan and quality plan for your Project
3SDW Project Workflow and Inventory Management
System Implementation
Dissemination of Haze Data, Data Products and Information Bret Schichtel, Rodger Ames, Shawn McClure and Doug Fox.
3SAQS Technical Workshop May 29-30, 2013 Data Warehouse Update, Assessment, and Work Plan Review Zac Adelman (UNC-IE) Shawn McClure (CSU-CIRA) Tom Moore.
What is Business Analysis Planning & Monitoring?
RUP Requirements RUP Artifacts and Deliverables
UML - Development Process 1 Software Development Process Using UML (2)
Pacific Northwest Aquatic Monitoring Partnership (PNAMP) A Presentation for: Columbia Basin Fish and Wildlife Authority Anadromous Fish Advisory Committee.
Three State Data Warehouse Tom Moore Shawn McClure, Rodger Ames, Dustin Schmidt
SIUE Injury Tracking System Project Plan. Team Members: Robbie Marsh Robbie Marsh –Project Manager/Webmaster Ken Metcalf Ken Metcalf –Lead Programmer.
RUP Implementation and Testing
Rational Unified Process Fundamentals Module 4: Disciplines II.
Problem Identification
UQ Drupal Support Service and Transition
 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.
MRC Water Utilisation Programme 20 May 2003 Knowledge Base & DSF Software Presenter: Dr Jon Wicks, Software Integration Specialist in association with.
3SAQS Technical Committee Workshop Overview of updated schedule / deliverables related to ongoing 3SAQS technical work October 31, 2013 Tom Moore.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
2004 Workplan WRAP Regional Modeling Center Prepared by: Gail Tonnesen, University of California Riverside Ralph Morris, ENVIRON Corporation Zac Adelman,
Module 7 Session 7.3 Visual 1 Module 7 Planning and Scheduling with the Critical Path Method Session 7.3 The computer and project management.
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
November 7, 2013 WRAP Membership Meeting Denver, CO Tom Moore WRAP Air Quality Program Manager WESTAR Council.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
National Information Exchange Model Update for the Global Advisory Committee Spring 2008 Meeting April 10, 2008 NIEM Technical Architecture Committee (NTAC)
Three State Data Warehouse 1 Cassie Archuleta Tom Moore May 6, 2014 Progress Update for 3SDW Development.
July 2008 CPS2 Waiver SDT Technical Workshop for Draft BAL-001-TRE-01 Judith A. James Reliability Standards Manager TRE.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Harnessing the carbon market to sustain ecosystems and alleviate poverty Monitoring of AR Projects Monitoring of AR Projects BioCarbon Fund Training Seminar,
An Integrated Systems Solution to Air Quality Data and Decision Support on the Web GEO Architecture Implementation Pilot – Phase 2 (AIP-2) Kickoff Workshop.
Shanghai Jiao Tong University 上海交通大学软件工程中心 Object Oriented Analysis and Design Requirements Overview.
Three-State Air Quality Study (3SAQS) Three-State Data Warehouse (3SDW) Status of 3SAQS Air Quality and Emissions Modeling University of North Carolina.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Consultant Advance Research Team. Outline UNDERSTANDING M&E DATA NEEDS PEOPLE, PARTNERSHIP AND PLANNING 1.Organizational structures with HIV M&E functions.
The principles of an object oriented software development process Week 04 1.
TSS Database Inventory. CIRA has… Received and imported the 2002 and 2018 modeling data Decided to initially store only IMPROVE site-specific data Decided.
Online Submission and Management Information -- Authors AMS Annual Conference / AMS WMC Click on play to begin show.
Status Organization Overview of Program of Work Education, Training It’s the People who make it happen & make it Work.
Patterns in caBIG Baris E. Suzek 12/21/2009. What is a Pattern? Design pattern “A general reusable solution to a commonly occurring problem in software.
IWDW-WAQS Technical Committee Status Call, December IWDW Update IWDW-WAQS Technical Committee Status Call.
Intermountain West Data Warehouse Update WAQS Technical Committee WAQS Technical Committee Call, July 23, 2015.
The GridPP DIRAC project DIRAC for non-LHC communities.
2012 TELPAS Online Testing & Data Collection. Disclaimer  These slides have been prepared by the Student Assessment Division of the Texas Education Agency.
Consumers, Health, Agriculture and Food Executive Agency 3rd Health Programme The Electronic Submission System (JA 2015) Georgios MARGETIDIS.
Systems Analysis & Design David Walkiewicz March 31, 2012.
3SAQS Data Warehouse Update September 30, 2014 CIRA - Fort Collins, CO.
Shawn McClure, Rodger Ames and Doug Fox - CIRA
Fundamentals of Information Systems, Sixth Edition
IWDW-WAQS Technical Committee Status Call
CLINICAL INFORMATION SYSTEM
5 Steps to file your objections/ suggestions on KUDA Master Plan 2041
ESS.VIP VALIDATION An ESS.VIP project for mutual benefits
Open Source Software Development Processes Version 2.5, 8 June 2002
Portfolio, Programme and Project
Tribal Data WG Fire and Smoke WG Oil and Gas WG
WSAQDW planning documents
Presentation transcript:

Three State Data Warehouse 1 Cassie Archuleta Shawn McClure Tom Moore June 20, 2014 Progress Update for 3SDW Development Project

Development Tech Team WESTAR – Tom – Project lead CIRA – Shawn – Oversight and lead CIRA developer – CIRA fulltime DB programmer - will join in late July 50% FTE programmer/DW development coordination – will join around July 1 ARS – Cassie – Facilitation assistance through August (transition to CIRA) UNC – Zac – Support for website design elements, modeling data generation, access and evaluation needs. ENVIRON – Ralph – Support for modeling data generation, access and evaluation needs. 2

Major Project Elements Modeling Package Download/Upload Tools – Progress update today focuses on NEPA modeling package download Download/Upload permissions/tracking tools for project managers Model Results Evaluation Tools Emissions Inventory Viewing Tools Monitored Data Viewing Tools? – Not currently in the design documents, but there has been some discussion of incorporating existing/new monitoring data summary tools 3

NEPA Data Package Download Current Status: Several stakeholders volunteered on 5/6 call to participate in process to refine identification of data package interface needs Every other week “Design Team” calls have alternated with “Technical Team” calls Interface needs identified by these groups have been incorporated into a NEPA data package download use-case scenario Test cases for implementation are NEPA data package requests from ENVIRON (internal test) and AECOM (external test) – Committed to providing data packages manually ASAP – Will continue to develop 3SDW test cases around these packages after initial delivery 4

Some elements of the NEPA Data Package Download use-case scenario: Register Accept site terms and conditions Browse and select available projects and associated data packages Fill out and submit a data request form – User completes a form identifying proposed modeling protocol elements and other important considerations, including: Project information (e.g. project sponsor and proposed use) Proposed model methodology – Description will contain metadata for available 3SDW “package” (e.g. model versions, grid domain, emissions scenarios, etc.) – User must either verify use of 3SDW configuration or describe any differences in proposed use Wait for permissions – Need to develop details for an automated/manual permission process that involves project sponsors/managers 5 NEPA Data Package Download

Some elements of the NEPA Data Package Download use case scenario (continued): Download data package/enter mailing information Configure model run – For NEPA examples, data package for model run will include Input and output files that support a “no-action” scenario User would run same package in a comparable manner with emissions modifications representing “proposed action” and “alternative action(s)” Run a benchmark test – Need a QA/QC test to determine that user model run configuration is comparable to 3SDW configuration – User instructions to run a benchmark test and submit/evaluate results are under development Complete model runs 6 NEPA Data Package Download

Model Results Evaluation After model runs are complete, the 3SDW will support some model evaluation tools. Current status – Modelers have defined 5 key visualization tools for model results evaluation Time series plots Scatter plots Soccer plots Fraction bias spatial maps Mean bias spatial maps – For existing 3SDW packages, flat files of visualization products have already been generated – First iteration of 3SDW will allow user to navigate through and view existing flat files Future implementation – User uploads their own modeling results for evaluation purposes – 3SDW facilitates generation of model evaluation plots/products dynamically 7

Near-term goals Continue to develop and implement NEPA data package download/evaluation use-case scenarios Implement model evaluation tools that navigate flat files Develop detailed use-case scenarios for – Project manager access E.g., log-in and see who accessed your project, what files were requested/provided, QA/QC results, etc. – Model evaluation (dynamic tools) – Emissions scenario visualization tools – Monitoring data visualization tools Determine if other websites provide adequate tools to avoid duplicating efforts 8