Aim demo


Published on


Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • AIMS went live in October 2002
  • [email_address] [email_address] [email_address] [email_address]
  • Centralizing data management protects the integrity of the data, version conformity, allows report generation on demand, speeds response to sudden requests and insures proper data recovery in event of disaster. Prior systems collected data for single purposes. Special calls for data throughout the year gathered lacking data for the Vice President Report, Federal Report and other reports.
  • NARS used a drill down approach to manage 2,500 goals, objectives, output indicators and outcome indicators. The original NARS had 10,000 questions.
  • Getting rid of these two programs was sold as a direct benefit to AIMS.
  • In addition to the two reporting applications, faculty were asked to e-mail success stories demonstrating impacts at the end of each year. These stories, often the most valuable part of our annual federal report, were under reported because the mechanism was not there to capture them when they occurred.
  • The AIMS support team were often thought to have analyst couches in their offices as they helped faculty deal with the frustrations that always accompany significant change. They quickly learned how to listen effectively.
  • Amazingly, the AIMS program worked very reliably from the beginning. However, data collection structures that worked well in theory did not work as well in practice, causing a multitude of changes that had to be made on the fly to AIMS while in production mode. Also, the Office of Staff and Leadership Development was overwhelmed in the first months with calls for help. It was not until then that the dedicated AIMS support team was put in place.
  • The GroupWise appointments can be set up to automatically accept and post to the individual’s calendar. There is also an event calendar in AIMS for those who prefer not to use GroupWise for managing their schedules.
  • A deadline of the 5 th of each month is set for entry of that month’s data. This cutoff protects the data integrity for reporting. As expected, demand on the server spikes as that data approaches each month.
  • With the development of AIMS, administration decided that those who conduct the activities should be accountable for entering the data.
  • Each year brings changes and improvements. Granting agencies have the most impact on the change schedule, but organizational changes (multi-county agents) also create new opportunities for AIMS.
  • Aim demo

    1. 1. Taking AIM: Demonstration Statewide Web-Based Planning, Reporting & Evaluation System AIMS Copyright 2002 – 2005 University of Arkansas Cooperative Extension Service
    2. 2. Taking AIM: <ul><ul><li>Presenters </li></ul></ul><ul><ul><li>Dr. Karen Ballard, Extension Evaluation Specialist </li></ul></ul><ul><ul><li>Mrs. Nina Boston, Director of Information Technology </li></ul></ul><ul><ul><li>Mr. Steve Hall, Computer Specialist </li></ul></ul><ul><ul><li>Mrs. Mary Poling, AIMS Support Manager </li></ul></ul>
    3. 3. Taking AIM: <ul><li>Administrative Vision for AIMS: </li></ul><ul><li>Web-based planning, reporting and </li></ul><ul><li>evaluation system </li></ul><ul><li>Consolidation of most reporting requirements </li></ul><ul><li>Capacity for on-demand data extraction </li></ul>
    4. 4. Taking AIM: Evaluation is the link between what we PROVIDE & what we EXPECT . . . Data can answer: Are we doing the RIGHT things & WHAT are the RIGHT things?
    5. 5. Taking AIM: Planning - Program POW -Individual IPOW Scheduling -Methods & Events Reporting -Scheduled Events -General Program Data -Benchmark Indicators Evaluation -Inputs & Outputs -Benchmark & Impact Reports
    6. 6. Taking AIM: <ul><ul><li>Value of the Logic Model for AIMS </li></ul></ul><ul><li>Shows the “chain of events” </li></ul><ul><li>Summarizes the key elements of the program </li></ul><ul><li>Clarifies differences between activities & outcomes </li></ul><ul><li>Signals “what to evaluate” </li></ul><ul><li>Builds consensus around what the program is </li></ul>
    7. 7. Taking AIM: Logic Model: AIMS Design Components: IMPACT Ultimate Benefit = -Economic -Policy -Social -Environ. -Health ACTION -Behavior -Decisions -Practice LEARNING -Knowledge -Awareness -Skills -Opinions -Attitudes Activities (Methods) -Products -Classes -Training -Mailings -Articles - Participation Program Investments -Staff time -Curricula -Volunteers -Salary Costs
    8. 8. <ul><li>Challenges: </li></ul><ul><li>Development Time Line </li></ul><ul><li>Complexity of Organization </li></ul><ul><li>Inconsistent Terminology & Definitions </li></ul><ul><li>Development Team Staffing Resources </li></ul><ul><li>Attitudes of end users </li></ul><ul><li>County computers </li></ul><ul><li>User time required to learn the system </li></ul><ul><li>Enhancements that will need to be made </li></ul>Taking AIM:
    9. 9. Taking AIM: <ul><ul><li>System Features: </li></ul></ul><ul><li>Individualized plan of work formatted </li></ul><ul><li>for all Extension programs </li></ul><ul><li>Ability to develop IPOW for any “other” programs </li></ul><ul><li>Scheduled programs automatically posted to Groupwise </li></ul>
    10. 10. Taking AIM: <ul><ul><li>System Features: </li></ul></ul><ul><li>Collection of data on development time, direct & indirect contacts </li></ul><ul><li>Viewable itinerary </li></ul><ul><li>Proxy Access </li></ul><ul><li>Reports can be pulled by end-user as needed </li></ul>
    11. 11. Taking AIM: <ul><ul><li>Evaluation System Capacity: </li></ul></ul><ul><li>Management reports for supervisors </li></ul><ul><li>Ability to view reports by employee, county, district, statewide, or program by month, quarter, and/or year </li></ul><ul><li>Real time access to process evaluation data </li></ul>
    12. 12. Taking AIM: <ul><ul><li>Nina Boston </li></ul></ul><ul><ul><li>Director of Information Technology </li></ul></ul>
    13. 13. Taking AIM: <ul><ul><li>Driving Principles </li></ul></ul><ul><ul><li>Provide one source for all reporting </li></ul></ul><ul><ul><li>Centralize data management </li></ul></ul><ul><ul><li>Roll out updates more uniformly </li></ul></ul>
    14. 14. The previous model was standalone, linear and inflexible.
    15. 15. A separate program captured civil rights data.
    16. 16. Taking AIM: <ul><ul><li>Past Reporting Was Dis </li></ul></ul><ul><ul><ul><li>Before AIMS, narrative success stories were e-mailed at the end of the year instead of when they occurred. </li></ul></ul></ul>jointed
    17. 17. Taking AIM: <ul><ul><li>What did we do right? </li></ul></ul><ul><ul><li> User support was put at the top </li></ul></ul><ul><ul><li> Faculty and staff were at the table together </li></ul></ul><ul><ul><li> We began with outputs needed and worked backwards </li></ul></ul><ul><ul><li>After rollout, the programmer received only technical calls </li></ul></ul>
    18. 18. Taking AIM: <ul><ul><li>What did we do wrong? </li></ul></ul><ul><ul><li> AIMS was rolled out in 80 days with no pilot testing </li></ul></ul><ul><ul><li> The DEMO web was a late arrival </li></ul></ul><ul><ul><li> Checkboxes would have eased benchmark selection </li></ul></ul><ul><ul><li> User support team was hired after rollout, not before </li></ul></ul>
    19. 19. Taking AIM: <ul><ul><li>Special Features </li></ul></ul><ul><ul><li> Faculty are e-mailed each month with entry reminders </li></ul></ul><ul><ul><li>When events are planned, appointments post to the faculty member’s GroupWise calendar </li></ul></ul><ul><ul><li>Development team access DEMO directly from AIMS </li></ul></ul><ul><ul><li>Reports are dynamically generated for independent retrieval of data </li></ul></ul>
    20. 20. Taking AIM: <ul><ul><li>Growing Pains </li></ul></ul><ul><ul><li>Initial home was a production server holding many other web applications </li></ul></ul><ul><ul><li>The AIMS monthly entry deadline sent traffic soaring </li></ul></ul><ul><ul><li>Constant changes to AIMS the first year affected the stability of the production server </li></ul></ul><ul><ul><li>A dedicated server was purchased in August 2003 </li></ul></ul>
    21. 21. Taking AIM: <ul><ul><li>AIMS required behavioral change </li></ul></ul><ul><ul><li> The basic computer skills of faculty were overestimated </li></ul></ul><ul><ul><ul><li>[Prior to AIMS, some agents had secretaries print their e-mails and send all responses] </li></ul></ul></ul><ul><ul><li>Secretaries previously entered data for agents </li></ul></ul><ul><ul><li>Reporting was required at least monthly </li></ul></ul>
    22. 22. Taking AIM: <ul><ul><li>The Future </li></ul></ul><ul><ul><li>Professional Development module integrates with AIMS, our accounting and training systems </li></ul></ul><ul><ul><li>Platform moving to Oracle </li></ul></ul><ul><ul><li>Centra Symposium, Educator and NetworkStreaming are tools to educate and support users </li></ul></ul>
    23. 23. Taking AIM: <ul><ul><li>Specifications </li></ul></ul><ul><ul><ul><li>Software </li></ul></ul></ul><ul><ul><ul><li>Microsoft Visual Interdev 6.0 </li></ul></ul></ul><ul><ul><ul><li>Visual FoxPro 6.0 </li></ul></ul></ul><ul><ul><ul><li>Hardware </li></ul></ul></ul><ul><ul><ul><li>Gateway 960 Series, dual 2.4GHz processors </li></ul></ul></ul><ul><ul><ul><li>2GB memory </li></ul></ul></ul><ul><ul><ul><li>36GB SCSI hard drive </li></ul></ul></ul><ul><ul><ul><li>DDS-4 tape drive </li></ul></ul></ul><ul><ul><ul><li>AIMS Copyright 2002 – 2005 University of Arkansas Cooperative Extension Service </li></ul></ul></ul>
    24. 24. Taking AIM: <ul><ul><li>Mrs. Mary Poling </li></ul></ul><ul><ul><li>AIMS Support Manager </li></ul></ul>
    25. 25. <ul><li>Shooting for the Bullseye: </li></ul><ul><ul><li>Planning </li></ul></ul><ul><ul><li>Scheduling </li></ul></ul><ul><ul><li>Reporting </li></ul></ul><ul><ul><li>Results </li></ul></ul>Taking AIM:
    26. 26. Taking AIM: Creating Plan of Work
    27. 27. Select Food Stamp Nutrition Education (FSNE)
    28. 28. Select Goal
    29. 29. Staff Days
    30. 31. Preview IPOW prior to notifying supervisor
    31. 32. Taking AIM: Scheduling & Reporting
    32. 33. Scheduling & Reporting Events
    33. 36. Select School to Report
    34. 39. Select Teachers
    35. 45. Taking AIM: Retrieving Results
    36. 46. Select Program Results
    37. 58. Detail Report by Individual or Unit Name
    38. 59. Unit Summary Report
    39. 65. Taking AIM: Reporting Impacts
    40. 73. Taking AIM:
    41. 75. Taking AIM:
    42. 77. Taking AIM: <ul><ul><li>Questions? </li></ul></ul>