IC-Specific Data Addressing individual needs in an enterprise manner.

Slides:

Advertisements

Similar presentations

AS Level – Week 11 Theory Module 1 Learning and Performance.

Advertisements

Executional Architecture

Chapter 12 Array Processing and Table Handling. Defining Series of Input Fields Coding record with 24 independent hourly fields is cumbersome 01Temp-Rec.

File Management Chapter 12. File Management File management system is considered part of the operating system Input to applications is by means of a file.

File Management Chapter 12. File Management A file is a named entity used to save results from a program or provide data to a program. Access control.

Conducting systematic reviews for development of clinical guidelines 8 August 2013 Professor Mike Clarke

Retrieving and Analyzing Data Using the QVR System Scientific Program Staff.

Planning a Ketso Workshop plus hints and tips. Basic structure of a Ketso workshop A trunk – the core focus, which is written on the centrepiece. What.

Congestion Pricing: Competitive Locational Prices of Power Stoft (2002)

Data Structures Hash Tables

The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.

Motivation for IDEF1X Simplicity Common Standard Useful when relational model is target Air Force 1985 or thereabouts.

Planning the Audit EPA Regions 9 & 10 and The Federal Network for Sustainability 2005.

1 Ad Hoc Query & Reporting Thread Tool Recommendation Ad Hoc Query & Reporting Thread March 26, 2002.

OPERA Electronic Submission of Administrative Supplement and Change of Institution Requests David Curren and Emily Linde Office of Policy for Extramural.

1 Age Distributions of NIH Research Project Grant Investigators and Medical School Faculty, September 2007.

©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 31 Slide 1 Service-centric Software Engineering 2.

Real Options in Equity Partnerships Author: Timothy B. Folta & Kent D. Miller Source: Strategic Management Journal (2002), Vol. 23, pp Presented.

Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,

STRATEGIC MANAGEMENT ACCOUNTING Product Profitability Product costing has been a mainstay of cost and management accounting for many years. Very sophisticated.

The sun is setting on IMPAC I (now known as the Legacy system), and, as we prepare to retire IMPAC I in October 2002, it is fitting that the NIH pay tribute.

Chapter #2: Motor Learning for Effective Coaching and Performance

Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.

Evaluation of software engineering. Software engineering research : Research in SE aims to achieve two main goals: 1) To increase the knowledge about.

MIS 301 Information Systems in Organizations Dave Salisbury ( )

An Introduction to Design Patterns. Introduction Promote reuse. Use the experiences of software developers. A shared library/lingo used by developers.

1 Pre-Programmed Thread Tool Recommendation Pre-Programmed Thread February 12, 2002.

NIH Workshop: Extramural Enterprise and Extension Systems Overview of Plans.

Software cost estimation Predicting the resources required for a software development process 1.

The Query/View/Reporting System (QVR) Overall Plan for Incorporating IC-Specific Data IC-Specific Data Committee April 23, 2002 IC-Specific Data Committee.

Data warehousing and online analytical processing- Ref Chap 4) By Asst Prof. Muhammad Amir Alam.

DIMENSIONAL MODELLING. Overview Clearly understand how the requirements definition determines data design Introduce dimensional modeling and contrast.

Software Function, Source Lines Of Code, and Development Effort Prediction: A Software Science Validation ALLAN J. ALBRECHT AND JOHN E.GAFFNEY,JR., MEMBER,IEEE.

Methodology - Conceptual Database Design. 2 Design Methodology u Structured approach that uses procedures, techniques, tools, and documentation aids to.

 Three-Schema Architecture Three-Schema Architecture  Internal Level Internal Level  Conceptual Level Conceptual Level  External Level External Level.

Richard Nakamura, Ph.D. October 2014 CSR Goals and Philosophy.

MIS2502: Data Analytics The Information Architecture of an Organization.

Module 2: Information Technology Infrastructure Chapter 5: Databases and Information Management.

Combining Theory and Systems Building Experiences and Challenges Sotirios Terzis University of Strathclyde.

1 File Management Chapter File Management n File management system consists of system utility programs that run as privileged applications n Concerned.

CE Operating Systems Lecture 14 Memory management.

ARC New Business Office (NBO) 1) NBO Introduction Wendy Dolci, Chief of NBO 2) Update on NSPIRES and External Funding Sources Ken Galal, NBO 3) Ames Instrumentation.

1 NIH eRA Database Resource Plan Last Updated: 6/19/2003 by eRA Operations for Techrep Meeting “Doing more with less”

©Ian Sommerville 2000Software Engineering, 7th edition. Chapter 26Slide 1 Software cost estimation l Predicting the resources required for a software development.

Homework due Test the random number generator Create a 1D array of n ints Fill the array with random numbers between 0 and 100 Compute and report the average.

Logical (Information Level) Design of Relational Databases.

Chapter 18 IP: Internet Protocol Addresses. Internet protocol software used to make the internet appear to be a single, seamless communication system.

Chapter 4 Logical & Physical Database Design

Multi Dimensional Variance: How to make ultra flexible software!

T. Trimpe Science Scramble Science Experiments T. Trimpe

Funding Opportunities for Investigator-initiated Grants with Foreign Components at the NIH Somdat Mahabir, PhD, MPH Program Director Epidemiology and Genetics.

Proposed Future for the ECB, CAM, & QVR Electronic Council Book (ECB) Council Administration Module (CAM) Query/View/Report (QVR) eRA Project Team July.

1 IP Routing table compaction and sampling schemes to enhance TCAM cache performance Author: Ruirui Guo, Jose G. Delgado-Frias Publisher: Journal of Systems.

The Query/View/Reporting System (QVR) Proposed Screens for Incorporating IC-Specific Data Functionality Presentation to IC-Specific Data Committee June.

1 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.

General Architecture of Retrieval Systems 1Adrienn Skrop.

Scientific Method The 7-step process to scientific investigations.

Phases of ERP Implementation Lifecycle By ControlERP

Rigor and Transparency in Research

Building a Quality management System First question is: - Is the Certification Body part of a legal entity? Most CB’s are in fact part of another organisation.

IT Architecture Technical blueprint for evolving a corporate infrastructure resource that can be shared by many users and services processing systems hardware.

The Scientific Method in Psychology

Requirement Prioritization

Physical Database Design and Performance

Data Warehouse—Subject‐Oriented

OGSA Data Architecture Scenarios

ENTITY RELATIONSHIP DIAGRAM

Measures of Central Tendency

Stages of Succession October 6, 2005

INDEXING TECHNIQUES The process of constructing document surrogates or document representations is called as Subject Indexing. Indexing has to specify.

Presentation transcript:

IC-Specific Data Addressing individual needs in an enterprise manner

The Issue There is no single NIH process that all the ICs use for their grant-related activities  ICs each have their own unique activities and data related to grants For example, grant coding (or indexing) is done quite differently within different ICs Not only is the process different, but even the codes themselves vary

A miracle has occurred… IMPAC II data and applications successfully address most NIH-wide grant processing needs. However, the ICs are still independent entities…

Individuality is a wonderful thing, but it comes at a price Internal IC grant handling processes vary widely – each has separate workflow and coding schemes. This makes it difficult to address the ICs’ internal grant processing requirements with a single NIH-wide application or set of data.

Thus… The ICs each download IMPAC II data, combine it with their internal data, then continue with their separate business processes

What can we do? Find IC processes and associated data requirements that are similar (e.g., common data needs) and work directly with the ICs to acquire and use these data from a single, central source This will allow NIH to gradually move to fewer dissimilar ways of doing business

Extramural Business Architecture – An IC View IC IMPAC II - OLTP Selected IMPAC II Data Plus IC-specific Data IMPAC II - IRDB eRA Suite of Applications Selected IMPAC II Data Plus IC-specific Data Areas of Focus

IC #9IC #8IC #10IC #11IC #nIC #7 The Bigger Picture IC #1IC #6IC #2IC #4IC #3 IMPAC II - IRDB IMPAC II - OLTP IC #5 Data Center

IC #9IC #8IC #10IC #11IC #nIC #7 The Downloads IC #1IC #6IC #2IC #4IC #3 IMPAC II - IRDB IMPAC II - OLTP IC #5 IMPAC II - IRDB IMPAC II - OLTP

On careful analysis a different view emerges Internal IC grant handling processes vary in the details – All ICs use the same general workflow. Each IC either has or wants a scientific indexing scheme for analyzing and reporting their science. The overall workflows used by the ICs are similar enough that a consensus developing process has a high likelihood of being successful in developing an NIH-wide database and application.

Specific Steps Needed Obtain a composite view of the “external” data needed by ICs for their extramural business processes  Identify the IMPAC II data (OLTP and IRDB) that’s being downloaded by each IC and determine how it is used  Identify other data sources required

Specific Steps Needed (Continued) Determine the local (i.e., IC-specific) data needed by each IC for their extramural business processes  Identify grant coding/indexing data and techniques used by each IC  Identify other IC-specific data needed

Specific Steps Needed (Continued) Work with each IC to begin using this common, centrally-stored data base structure Design and develop an Oracle database structure to accommodate the IC-specific data Provide applications as required to supplement existing IC applications

IC #9IC #8IC #10IC #11IC #nIC #7 The Goal IMPAC II - IRDB IMPAC II - OLTP eRA Suite of Applications Selected IMPAC II Data Plus IC-specific Data IC #5IC #6IC #4IC #3IC #2IC #1

The Goal (Continued) Retire… happy