I started working with Banner in 1999, the same year I was married. It was a year of learning to adjust to new things: a new life, new job responsibilities, a new role as a DBA, and a new ERP. It was an exciting time. <\/p>\n\n\n\n
Banner was version 3.x; it was client\/server technology. We were transitioning from a legacy system that was character-cell-based, hosted on VMS, and in my opinion, the most solid and secure OS around. At that time, Banner was still offered on VMS, so that was our platform of choice. It had its quirks, but we made it work because that\u2019s what we did: we found a problem, fixed it, and moved on. <\/p>\n\n\n\n
Over the years, we saw Banner move from client\/server technology to what we affectionately called \u201cBanner in a browser\u201d (INB), a thin client. We all thought that wouldn\u2019t last. We experienced our first 404 errors, then mysterious 500 errors, all in the name of progress. <\/p>\n\n\n\n
The Banner technical community became stronger as we struggled through this change together. We chatted more at conferences, the Banner DBA list became active, and we shared a great deal of information. We helped each other get through the change, and we made it work.<\/p>\n\n\n\n
Along the way, we challenged each other to think outside the walls of our institutions. We became a community. <\/p>\n\n\n\n
Then came the need to change the database character set with the introduction of UTF-8. I thought this would hurt more than it did. The initial plans from Ellucian were not well-designed, but the technical community challenged the vendor to do better, and they responded.<\/p>\n\n\n\n
By the time most of us were ready to go through the process, it was relatively painless, and we moved on. The entire ecosystem improved because of the willingness to share and be open to suggestions. As a community, we have been improving the entire Banner environment for years. <\/p>\n\n\n\n
When the most recent change from Oracle Forms to Java-based applications happened, the uproar within the community was astounding.<\/p>\n\n\n\n
We went from supporting 3 servers per environment to supporting countless servers, depending on the choices we made. Our workloads increased, and we needed to learn new technology, especially if we chose Tomcat over WebLogic. It seemed like a dark time for those supporting the Banner infrastructure. <\/p>\n\n\n\n
However, just as with any other change, we embraced the task at hand, pushed each other to try even newer technologies like Docker containers, expanded into cloud technologies as a cost-saving measure and for redundancy and disaster recovery, and moved on once more. <\/p>\n\n\n\n
\u202f<\/strong>Today, Banner is evolving again.<\/strong> There is always the unknown whenever venturing into something different. It doesn\u2019t mean that it should be avoided. It doesn\u2019t mean that it shouldn\u2019t be questioned, either. We\u2019ve seen so much change over the years. We\u2019ve experienced the good and the bad. The one constant we have come to realize, however, is the power of the collective voice.<\/p>\n\n\n\n We know our voice matters. We know the technical community can make things happen if we speak up and push the envelope, because we know at the heart of everything is the well-being of our institutions. The biggest question, though, is whether we can really handle another platform change? <\/p>\n\n\n\n Change is never easy.<\/strong> My kids are terrible with change. When we got rid of our aging minivan, I had to replace it with the same make, model, and color, and still I got the response from them: \u201cIt\u2019s different! What was wrong with the old car? It was fine.\u201d It wasn\u2019t fine. It was old and costing us more in maintenance every time we took it in.<\/p>\n\n\n\n The new one had updated safety features, better gas mileage, GPS, but all they saw was the functionality of the vehicle: the ride inside from their perspective. They were not looking at the bigger picture.<\/p>\n\n\n\n Change is inevitable, and resistance to change is guaranteed. <\/strong><\/p>\n\n\n\n The first time I heard that Banner was moving to a SaaS platform, my thoughts immediately went to \u201cmy role as a DBA is over\u201d. It took me a long time to realize that my role as a DBA had been over for a long time. I haven\u2019t been \u201cjust a DBA\u201d for several years.<\/p>\n\n\n\n My daily tasks have morphed into sys admin, networking, cloud architect, problem solver, installer, Windows admin, counselor, and the list goes on. Occasionally, I get to flex my DBA muscles, and it feels good, but certainly not as often as I used to. <\/p>\n\n\n\n As I have begun working with the Ellucian SaaS platform, I have come to realize that the skills I\u2019ve developed over the years, including my DBA skills, will not go to waste.<\/p>\n\n\n\n There are ample opportunities to create new approaches to old problems. This requires thinking outside the box\u2014a skill you either have or you don\u2019t. I\u2019ve found that most DBAs just have it. We know how to work between the technology and the people. We know how to problem-solve.<\/p>\n\n\n\n We know how to make the technology work the way it needs to work. If it doesn\u2019t, we know how to \u201cencourage\u201d the vendor to make the changes we need to see happen. <\/p>\n\n\n\n \u202f<\/strong>We are a community of change makers.<\/strong> We embrace change.<\/strong><\/p>\n\n\n\n We may complain about it along the way, but in the end, we get the job done and learn a bit while doing it. The only thing we cannot do is stand still.<\/p>\n\n\n\n If there\u2019s anything I\u2019ve learned in the many years of working in higher ed, it is that change will happen whether I like it or not; whether I\u2019m on board or not; whether I agree with it or not. <\/p>\n\n\n\n The only choice I have to make is to embrace it and prepare the best I can for the ride. <\/p>\n\n\n\n The bottom line is that when the technical community faces change, I have seen amazing things happen. Ellucian Student powered by Banner is just one more change in the evolution of the Banner ERP lifecycle.<\/p>\n\n\n\n If we embrace that change and accept the challenge, I can\u2019t even imagine what the Banner Technical Community will develop and become. The possibilities are endless.<\/p>\n\n\n\n Stick with me over the next several weeks as I explore how to prepare your site for migrating to the Ellucian SaaS Platform.<\/p>\n\n\n\n It is a long road, and there is no better group I\u2019d want to travel with than the Banner Technical Community.<\/p>\n\n\n\n We got this! <\/strong><\/p>\n","protected":false},"excerpt":{"rendered":" Today, Banner is evolving again. There is always the unknown whenever venturing into something different.<\/p>\n","protected":false},"author":1,"featured_media":1872,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"insight_topic":[14],"class_list":["post-2026","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-insights"],"acf":[],"yoast_head":"\nTo Change or Not to Change<\/h2>\n\n\n\n
The Real Work Happens Between the Technology and the People <\/h2>\n\n\n\n
We Got This<\/h2>\n\n\n\n