The SRA Symposium - College of Medicine
The SRA Symposium - College of Medicine
The SRA Symposium - College of Medicine
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Papers<br />
process than an end product; as an enabler, not an objective. Each leading institution continually<br />
looks at ways to use technology to improve research administration, and their process is<br />
iterative and responsive rather than aimed at a specific end product. <strong>The</strong>y see an opportunity, do<br />
something, refine it, and then do something else. This iterative approach is at odds with the more<br />
“classic” approach to business process re-engineering and systems development, which is normally<br />
characterized by a more formal, and strategic planning process and step-wise action plans.<br />
Overall Approach. Another unexpected finding is that leading institutions do not view eRA as<br />
“electronic submission”, and it is not their major focus. <strong>The</strong>y are driven primarily by data and information<br />
needs first – all three institutions started by defining data requirements first, and developing<br />
a database. Officials at all three institutions indicated that developing data requirements and<br />
a database was the first thing they did before even thinking about how they could use the database<br />
to automate business processes. Thus, their vision for eRA is as a data-driven, grants management<br />
system rather than an electronic proposal submission system. We think this finding has significant<br />
implications.<br />
Leading institutions understand the importance <strong>of</strong> data in improving the efficiency and effectiveness<br />
<strong>of</strong> their business processes. Yet, many institutions do indeed view eRA as primarily a way to<br />
submit proposals and other types <strong>of</strong> information electronically, rather than as part <strong>of</strong> an overall<br />
and integrated grants management strategy. We think this view leads inevitably to a reactive approach<br />
to eRA, which is dependent on what sponsors provide in terms <strong>of</strong> e-grants capability (e.g.<br />
FastLane, grants.gov, NIH Commons, etc). We think that a “system-to-system” transfer <strong>of</strong> data<br />
between institutions and sponsors best helps institutions realize the benefits <strong>of</strong> eRA in an integrated<br />
way, rather than the prevailing government model which relies on a “person-to-government<br />
system” web interface. Our previous research indicates that electronic submission will work best<br />
when data is generated and controlled locally and then transmitted as part <strong>of</strong> a system-to-system<br />
process. Thus, we think government eRA <strong>of</strong>ficials should be encouraging the use <strong>of</strong>, and citing the<br />
advantages <strong>of</strong>, systems that foster sound “cradle to grave” grants management, including electronic<br />
submission. <strong>The</strong> grants.gov concept <strong>of</strong> “one stop shopping” for all submissions is an important and<br />
desirable development. Nevertheless, the current emphasis on “person-to-system” proposal transactions<br />
decouples the submission <strong>of</strong> data from the business processes that generate it and the local<br />
systems that track it. We think this decoupling is undesirable from a local business management<br />
perspective, as well as unnecessary. <strong>The</strong> challenge for service providers is make the business case<br />
for the value <strong>of</strong> system-to-system solutions for both government and institutions.<br />
COMMUNITY INVOLVEMENT AND USER ACCEPTANCE<br />
We found little commonality among the three institutions in how they approached building community<br />
involvement and user acceptance <strong>of</strong> their eRA systems. However, based on our discussions<br />
with institutional eRA <strong>of</strong>ficials, we have formed some observations and tentative findings.<br />
As previously noted, eRA systems at all three institutions were initially focused primarily on the<br />
internal <strong>of</strong>fice <strong>of</strong> sponsored programs information and processing needs. Thus, the initial customers<br />
and users <strong>of</strong> the systems were primarily internal to OSP and external community involvement<br />
in system development and deployment was not a focus in moving forward.<br />
2 It should be noted that we did not interview faculty or many departmental administrators at any <strong>of</strong> the institutions,<br />
and therefore could draw no conclusions about the acceptance or satisfaction with any <strong>of</strong> the institutions’ systems.<br />
Thus, our findings are based on the perceptions and experience <strong>of</strong> each institution’s eRA <strong>of</strong>ficials.<br />
148 2005 <strong>Symposium</strong> Proceedings Book