Heartland Network Data Management in the Heartland Network Background –Centralized staff –Protocols developed and implemented primarily in-house –12 of.

Slides:



Advertisements
Similar presentations
Do we need a GN of NGOs? Yes! (as far as participation in the GN does not reduce/affect involvement in the GP/DRR) The GN should build on existing networks.
Advertisements

Distributed Data Processing
The Anticipated Response: an essential element in end-to-end, community-early warning systems Topics: 1.Frameworks. 2.Trends: operational and institutional.
 DB&A, Knowledge Management Within and Across Projects June 15, 2012 INNOVATION for a better world.
Chandler Gilbert – Estrella Mountain – GateWay – Glendale – Mesa – Paradise Valley – Phoenix – Rio Salado – Scottsdale – South Mountain 21 st Century Maricopa.
Network Management Overview IACT 918 July 2004 Gene Awyzio SITACS University of Wollongong.
Background Example Implementations Challenges Lessons learned Protocol Deployment - SECN.
Chapter 8 Managing IT Project Delivery
1 BGS Customer Relationship Management Chapter 6 Technology and Data Platforms Chapter 6 Technology and Data Platforms Thomson Publishing 2007 All Rights.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
Introduction to Database Development. 2-2 Outline  Context for database development  Goals of database development  Phases of database development.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Enterprise Architecture
Strategic Approaches to Outsourcing to Clinical Research Organizations Kate Giovino Director of Clinical Operations.
Compliance System Validation - An Audit Based Approach December 2012 Uday Gulvadi, CPA, CIA, CISA, CAMS Director - Internal Audit, Risk and Compliance.
Cloud Computing. 2 A division of Konica Minolta Business Solutions USA Inc. What is Cloud Computing? A model for enabling convenient, on-demand network.
Solution Overview for NIPDEC- CDAP July 15, 2005.
The Evergreen, Background, Methodology and IT Service Management Model
INFO425: Systems Design INFORMATION X Finalizing Scope (functions/level of automation)  Finalizing scope in terms of functions and level of.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
CALIFORNIA DEPARTMENT OF WATER RESOURCES GEOSPATIAL TECHNICAL SUPPORT MODULE 2 ARCHITECTURE OVERVIEW AND DATA PROMOTION FEBRUARY 20, 2013.
New Role Models for the EDC Study Team Training, workflow and service provision DTI Conference Centre 1 st November 2005 Emma Banks Datatrial Limited.
Archived File The file below has been archived for historical reference purposes only. The content and links are no longer maintained and may be outdated.
1 Table of Content 1.Business Diagnostic - Establishing a case for change –Changes in demand –New opportunities –Emerging threats 2.Vision Creation - Defining.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Regulatory Information Management System in support of the Mackenzie Gas Project February 3, 2010.
Assignment 2 Project: Sea Urchin Sporting Goods Team Members: Gwn Hannay, Debbie Carlton, Susan Dalgleish Daniel Barnes, David Cooper.
Participatory research to enhance climate change policy and institutions in the Caribbean: ARIA toolkit pilot 27 th meeting of the CANARI Partnership January.
Geospatial Technical Support Module 2 California Department of Water Resources Geospatial Technical Support Module 2 Architecture overview and Data Promotion.
Plain Language: A Case Study Plain Language A case study at the British Columbia Securities Commission.
ZLOT Prototype Assessment John Carlo Bertot Associate Professor School of Information Studies Florida State University.
Workflow Description Roles and Responsibilities DEVA Data Management Workshop Devil’s Hole Pupfish Project Project Managemen t!?!
© 2007 by Prentice Hall 1 Introduction to databases.
Lecture 19 Chapter 10 A Portfolio Approach to Managing IT Projects.
Effectiveness in Review & Oversight of Human Subjects Research Steven Joffe, MD, MPH Assistant Professor of Pediatrics.
ROLE OF INFORMATION IN MANAGING EDUCATION Ensuring appropriate and relevant information is available when needed.
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
C6 Databases. 2 Traditional file environment Data Redundancy and Inconsistency: –Data redundancy: The presence of duplicate data in multiple data files.
Engin Ali ARTAN Industrial Engineering
Microsoft Operations Framework Morten Lauridsen Engagement Manager Microsoft Consulting Services Morten Lauridsen Engagement Manager.
QUALITY ASSURANCE MANAGEMENT CONTROLS Chapter 9. Quality Assurance (QA) Management is concerned with ensuring: 1) The information system produced by the.
© 2005 ESP Solutions Group Max Yield Data™ Max Yield Data™ (MYD) simply means “data that everyone agrees are worth the effort.” Max Yield Data™ have been.
The Move from Planning to Implementation John Boetsch - NCCN / Olympic NP 2009 I&M Data Management Conference Tucson, Arizona – April 2009.
Collaborative Networks for Conducting Comparative Effectiveness Research Tuesday September 9, :00 – 9:30 am.
Lecture 4. IS Planning & Acquisition To be covered: To be covered: – IS planning and its importance Cost-benefit analysis Cost-benefit analysis Funding.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 1: Introduction to Systems Analysis and Design Alan.
Kathy Corbiere Service Delivery and Performance Commission
The system PROBLEM 1 FEIO Poor loading Insufficient number of facilities Small number of parameters Unaccountable methodology for taxes calculation Poor.
Guidelines Recommandations. Role Ideal mediator for bridging between research findings and actual clinical practice Ideal tool for professionals, managers,
Key Findings from May & July 2008 WRAP Technical Workshops September 30, 2008 Steve Arnold, Colorado DPHE & Bob Kotchenruther, EPA R10 (Co-Chairs, WRAP.
Lecture 15 Chapter 8 Managing IT Project Delivery.
Organizing and leading the IT function Two set of tensions guide policies for developing, deploying and managing IT systems. 1.Innovation and control a.How.
Faculty Economics & Business EBS 2033 Systems Development Lecture 1 The Systems Development Environment Lecturer: Puan Asleena Helmi.
1 CASE Computer Aided Software Engineering. 2 What is CASE ? A good workshop for any craftsperson has three primary characteristics 1.A collection of.
Chapter 1 The Systems Development Environment
Identification of Business Needs Visualizing the Service Offering
Porter’s Competitive Forces
Chapter 1 The Systems Development Environment
File Systems Vs Database Systems
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
MBI 630: Systems Analysis and Design
Helene Skikos DG Education and Culture
Knowledge Management Strategies to Improve Business Performance
5/12/2019 2:57 PM © Microsoft Corporation. All rights reserved.
Chapter 1 The Systems Development Environment
Presentation transcript:

Heartland Network Data Management in the Heartland Network Background –Centralized staff –Protocols developed and implemented primarily in-house –12 of 15 network parks are fairly small and represent places and events of historic and cultural significance –Integrated with prototype

Heartland Network What Have We Learned? Data management is hard work!

Heartland Network Revisiting Priorities –Data mining –NPSpecies and other service-wide databases –Data management planning –ATR/COR on protocol development projects –GIS/GPS support to monitoring projects In –Data management needs assessment with project leads –Managing data work flow and security –Database development and maintenance –Writing data management SOPs

Heartland Network Establishing Clear Roles and Responsibilities Our approach –DM is shared responsibility among Project Manager and Data Manager –Project Manager is expected to have working knowledge of relational databases and ability to independently conduct basic data queries and exports Implications –Platform and design complexity are constrained –Increases risk of data loss –Creates some redundancy in database skills –Increases PI interaction and ultimately results in a better customized product

Heartland Network Managing Work Flow Idealized protocol development time line Pilot sampling Internal review Methodology Finalize SOPs Preliminary analyses Objectives Peer review Final protocol T – 1 yr T –2 yr Final version DB Beta version of DB Write DM SOP Database development times should be short, for each version, about 120 days. Keep PIs' involved and the initial database design simple. Add to the complexity later.

Heartland Network Minimizing Complexity By Considering Return on Investment The Subprime Syndrome Database Complexity Efficiency/Usability Ratio to Development/Maintenance Effort High Low High Low

Heartland Network Get The Data In! Find a balance between data security, ergonomics, efficiency, and data management capacity

Heartland Network Get The Data Out! Find a balance between automated data analyses and simple data export routines

Heartland Network Inspirational Message Albeit Poorly Crafted Data management is hard work! Yes You Can!