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

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

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

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

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

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

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

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

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

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

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

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

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

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

15. The Goal (Continued) Retire… happy