Tag Archives: Planning

Fun With Forms

Last week we talked about fun with mods – this week the project core team is looking at Oracle standalone forms we use in Banner. 126 of these forms have been identified and Jeff Toaddy is playing Sherlock, sleuthing out all the relevant information needed to make decisions about the future of each form. Jeff has had a series of Watson’s – partners from the client offices – helping him understand which clues are useful and which are just red herrings.

To date, 69 forms have been labeled “retire” – that’s nearly 55%. Ten will be rebuilt or replaced, three are part of a mod that has already been evaluated, and the rest are still in “investigation mode.” Watch for more Fun with Forms updates!!

Wading through the mods and forms

Over the past 18 years, we have generated lots of ways to make Banner give us the information we want in the format we want. Some of those have been created via Banner mods (modifications – see Glossary) and some via Oracle forms. Because Banner 9 is so different, we need to be sure any needed mods or forms will work the way we expect – and that may mean rewriting.

The project team tackled the mods first – business office team members leading the discussions. Here is what we found:

Keep: Will Require Project Resources Keep: No Update Needed  Other Retire Totals
Advancement 0 2 0 0 2
Financial Aid  1 2 0 2 5
Finance 2 2 0 1 5
General 1 28 1 6 16
HR 7 4 1 6 18
Student 12 13 1 14 40
Bursar 4 7 0 2 13
Grand Total 27 38 3 31 99

Currently, the teams are looking at the 130 plus Oracle forms that will need attention. Like the mods, the approach will be first to determine who owns or uses the form, is it still needed, and, if needed, what is the estimated cost of rewriting. Watch for more info on Banner forms soon!

Banner 9 Update: 4/10/17


  • Business analysts and client subject matter experts are in the final stages of reviewing mods to determine the appropriate disposition: retire, rewrite, keep with no change.
  • Preparing a presentation of the mods recommendations for the IT governance group, the CCIC (Continuous Improvement and Change Committee). This group owns the final decisions regarding the direction each mod will take
  • Began scheduling process for Mods Review with Ellucian


  • Received a statement of work (SOW) from a potential vendor (SIG) for Extension Training.


  • Received and applied feedback from committee and staff feedback on Charter


  • Continued breakdown of high-level timelines
  • Continued work on draft Communication Plan
  • Interviewed Application Architect candidates
  • Placed Action Item Log on Google for all team members to review/update