Following on the heels of a successful implementation for Advancement, Financial Aid is the next office scheduled to go live with Production Banner 9. Tentatively, that is scheduled for early November.
During the implementation for Advancement, an issue was discovered with the way Banner 9 works in Microsoft Internet Explorer (IE). The project team is working on finalizing a new schedule that moves up the installation of BDM Xtender V8 to help with the IE issue.
On time, on budget. The Advancement and IT Services team working on Miami’s Banner 9 project can claim success on both!
The Advancement office staff are now actively using the four Banner 9 modules (Advancement, Banner Document Management System (BDMS), General, and Student) moved to the production server earlier this month.
This milestone is critical to the Banner 9 project in two ways. The BDMS, General, and baseline Student modules support each of the implementations to follow. This engagement also serves as a “proof of concept” of the project core team’s testing and training process.
So kudos to the Advancement implementation team. You hit it out of the park!
The Banner 9 project is a big, complex beast with many moving parts. In formal project management lingo, we call it a “program” made up of many “projects.” Some of the work we are doing is for the “program” – like setting up the Dev, Test, and Prod versions. (See earlier post to learn what Dev/Test/Prod means.) That work supports all of the individual projects. However, each project has a unique timeline, a team of staff, and work to be completed. Issues and questions may be related to the full program or directly to one of the projects.
With an undertaking of this size, it is inevitable that questions and problems will arise. Instead of asking you to keep all of this straight, the Support Desk (513.529.7900 or ITHelp@MiamiOH.edu) is always a correct method to get attention to an issue. It is the most actively monitored support vector, and is used by all of IT Services.
If you are working with an IT development team on an active implementation, feel free to work out an effective method with the team, but the Support Desk is always a good option.
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!!
At Miami we have 99 “mods” or modifications to Banner. In conversation with other Banner schools, we have learned that our mod count is really very modest. A number of schools we talked to have thousands of mods!
During this adventure, you will hear reports about Banner “mods” and Banner “modules”. These are not the same thing.
“Mods” is short for modifications. Many Miami-specific customizations have been written over the years. IT Services uses the term “mods” to refer to customizations that have been created by rewriting pieces of baseline Banner code.
“Modules” is how Ellucian/Banner refers to the various parts of Banner. There are Banner Financial, Banner Student, Banner Workflow, and many more Banner modules that are or could be part of Miami’s Banner environment.