1 / 11

Three State Data Warehouse

Three State Data Warehouse. Progress Update for 3SDW Development Project. Cassie Archuleta carchuleta@air-resource.com Tom Moore tmoore@westar.org. May 6, 2014. Development Partners. WESTAR – Tom – Project lead CIRA – Shawn – Technical lead and primary developer

lark
Télécharger la présentation

Three State Data Warehouse

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Three State Data Warehouse Progress Update for 3SDW Development Project Cassie Archuleta carchuleta@air-resource.com Tom Moore tmoore@westar.org May 6, 2014

  2. Development Partners • WESTAR – Tom – Project lead • CIRA – Shawn – Technical lead and primary developer • ARS – Cassie – Facilitation assistance • ARS – Wendy and Scott – Web interface and database development support • UNC – Zac and colleagues – Support for website design elements, modeling data generation, access and evaluation needs. • ENVIRON – Ralph and colleagues – Support for modeling data generation, access and evaluation needs.

  3. Project Elements • Design Document – outlines project needs • Project tracking spreadsheet (new) – online tool identifying necessary steps and assigned parties • Current updates- • Setting up an environment to share development support • CIRA/ARS/UNC • Development of a “manual” modeling file download process • Offer near-term access for stakeholders before 3SDW is fully implemented • Better define concepts (e.g. modeling “packages”) and user case scenarios/permissions for more automated implementation • Generate/refine web interface mock-ups • Translate design documents to concept pictures to better define/identify development needs, and better communicate concepts to stakeholders

  4. “Manual” File Download System • Shawn has developed a template, with the following steps: • Set up account • Log-in • Accept user agreement • Select modeling “package” (in progress) • Email copy of request sent to administrator (currently Tom) • User receives script and instructions to download files (in progress) • Zac has identified several modeling “packages” currently available, and provided scripts and instructions which can be integrated with data request forms • Tom is working with stakeholders to better define user access cases and “data user tiers” which define permissions • Data use tiers will be associated with user login, and will define files and interfaces available for individual users

  5. “Next Generation” File Download System and Additional Connections • Increase automation of initial “Manual” File Download System • Add: • Build access levels as data are reviewed and opened to others – end point is Technical Support results on-line for Record of Decision • Notification system for access to project results as Cooperators review, comment, and discuss • Documents and review spaces: • Project summary “working doc” and “final doc” • Comments and discussions docs • All with connections to emissions data inputs and model results • Flowback mechanism for model results to come back into 3SDW and track to original outflow of model inputs and data – a “project” • Tracking information for 3SDW technical team

  6. Web-interface mock-ups • Started using a mock-up sketching tool to better define concepts and prompt questions/discussion • Goal is to get general developer/stakeholder agreement on concepts to better focus development tasks/time in near-term • Current site available at http://views.cira.colostate.edu/tsdw/ • Mock-ups available for preview at https://moqups.com/wminer/0pStVSby/p:a555e89e9 • With editing permission, can add comments directly to mock-up • Let Cassie/Wendy know if you would like access to mock-up editing tools Current Site Mock-up

  7. Data User / File Download mock-up Data download page • Concepts taken from preliminary “download design” document (UNC) • Different download options based on selection • Project • Data type • NEPA • File Browser

  8. Model evaluation mock-up Modeling Toolbox page • Offer tools to evaluate models • Need sub-committee to identify appropriate needs/tools?

  9. Emissions Browser mock-up Emissions browser • Some work has already been done on a template • Need to better define user needs • Display individual sources within categories? • User modification/uploads/display?

  10. Near-term goals • Overall 3SDW effort through Sept. 2014 • Finish manual project download design • Refine “use case” scenarios for stakeholder feedback • Refine mock-ups for additional stakeholder feedback • Continue steps to implement shared development support • Better define development needs amendable to tasking/delegating • Share the work across the development team

  11. Next Steps • Data Warehouse functionality + “look and feel” through Sept. 2014 • Volunteers from Technical Committee to: • Engage in small working groups on specific topics • Data User / File Download • Model Results Evaluation • Emissions Browser • Others? • Refine “mockups” before coding, formally / informally • Working Groups would meet by phone every 2 weeks to review development mockups and refine • Continue steps to implement shared development support • Better define development needs amendable to tasking/delegating • Take some pressure off of Shawn!

More Related