04
Mon, Nov
1 New Articles

The Need for Better IT Management Tools

Commentary
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

As the IT departments of public corporations burn the midnight oil to meet the deadlines of Sarbanes-Oxley (SOX), many are asking the same question: "Why was this so hard?"

Indeed, the primary difficulties faced by IT have been not the individual technical requirements of SOX, but the scope of the legislative mandate. In SOX, every change to the company's data must be accounted for, and security potholes that once allowed ad hoc modifications must be filled. Moreover, changes to the software itself must be rigorously documented, along with the identities of authors of changes and the notations of the authorizations that permitted those changes. Simple things, like modifying the length of a database field to fix a problem--once a relative snap on the iSeries--have been transformed by the SOX auditing requirements into non-trivial IT management headaches.

Change Management and Documentation Management Tools

Some of the most significant tools that are helping IT managers through this nightmare are the Change Management and Documentation Management suites that IT vendors have been selling for years. These tools have evolved significantly since the days of simple source/object control. Many suites today provide a good framework for accounting for and auditing of software changes. Moreover, the implementation of these tools--on homogeneous computing platforms like the iSeries i5 or across multiple server platforms in a typical IT shop--can really help IT to better communicate the IT implications of business decisions that management makes. Today, some tools can actually assist in the estimation of change projects themselves.

I know! On first blush, this sounds like one of those calls for project management tools that chew up budget and slow down development. But consider what the real requirements for IT have become in recent years. Consider, for instance, how many organizations moved in the 1990s to the eXtreme Programming (XP) model for application development.

The XP Model--A Model of Chaos?

Under the XP model, new solutions are developed with small teams consisting of users and programmers who work together to swiftly build new applications. Each team is seen as a microcosm of the organization and an agent of change. This development model encourages the rapid implementation of new code and the ability to progressively change that code to meet the evolving demands of the users.

XP is an excellent way to get a lot of new code built quickly, but it's also a really lousy way to build a comprehensive, integrated information system. The modern application development tools place a lot of power into the hands of individuals who may or may not have the business acumen to vouchsafe the company's best interests. The best intentions of these teams may, in fact, create a system that is running counter to the fiscal requirements against which the organization may be measured by auditors.

The Parable of the Quick and Dirty Fix

An example of this was brought home to me when I worked at an apparel manufacturer. The fashion department needed a "quick and dirty" way to calculate the labor costs for building a certain line of garments. When the fashion director approached IT with his proposal, IT informed him that the project would require at least a month of study to identify the implications to IT's ERP system. That's right! A month, just to see if it could be done!

This was, of course, not the answer that the fashion director wanted to hear. So, instead, unbeknownst to IT, the fashion director hired his own IT consultant to quickly build a solution to his department's problem. By all accounts, the consultant did an excellent job coordinating the requirements: In short order, he had developed a solution that completely filled the needs of the fashion department.

Today's Hero May Be Tomorrow's Rogue

This fashion director was proclaimed to be a hero by the upper management team, and it quickly adopted the reports of the new system as an adjunct to the IT department's ERP system.

Within no time at all, many more such adjunct systems were being implemented throughout the organization. Soon, IT's entire ERP system was rapidly unraveling in a classic case of conflicting data sets. Management was asked to choose which data sets or information systems it would be using and which systems it would be integrating into IT's ERP. When the choices were made, it then took more than a year to identify how to bring all of these adjuncts into IT's control. That's right! More than a year!

The Auditor's Response

At the end of the first and second fiscal years, the company's auditors were perplexed. Where did these sales projections come from? Where did the cost projections come from? How did those numbers figure into the financial calculations that were derived from the central ERP database? No one could say! The auditors noted the problems and added their own set of requirements for fixing the problems. IT's ERP requirements grew and grew, while more adjunct systems continued to promulgate through the company.

By the end of the fourth year, the IT manager was forced out. Upper management had finally lost patience with IT's slow response to the burgeoning demands of auditors and line managers for accurate information.

But that wasn't the end of the problem. New adjunct systems continued to be built, and the ERP system continued to unravel. New IT managers came and went. New requirements by auditors continued to build in IT's backlog. Upper management had completely lost control over its own information system and was operating by the seat of its pants.

The End of the Company

In the end, upper management determined that the mess of conflicting data no longer made it economically feasible to sustain an internal IT organization. It decided to outsource all of its basic IT requirements to a large IT consulting organization. Five years later, the company was sold to a larger clothing manufacturer.

What was the cause of this IT meltdown? Was it the fault of the guerilla actions of the fashion director? Was it the fault of the XP development model? Was it the fault of upper management? Maybe!

What Went Wrong?

But maybe it was also IT's inability to provide a reasonable estimate of time to create the fashion director's initial request. Without the change management and documentation management tools available to estimate the extent of the requested changes, the IT manager had ultimately been forced to fall upon his own sword.

Today, the complexity of modern information systems requires us, as managers, to treat the software applications and networks of hardware as more than mere libraries of instructions and databases housed in racks of hardware. In order to respond rapidly to the requirements of our fellow managers, we must organize our understanding of these resources into a structure of information that we too can rapidly access and query.

We need to be able to quickly judge the impact and implications of simple changes to the information system as a whole, and we need to develop better ways to communicate those implications to our upper management. Long gone are the days when a simple IT task list would meet the needs of communication. Each change we make to a single database must now be accurately reflected throughout the entire system. Just identifying those changes can take a significant amount of analysis. Without automated tools, IT's guess at the extent of a simple change can lead to tremendous delays in the ability of the organization to respond to changes in the business model.

The Need for Better Tools

Change management tools and documentation management tools are key resources that IT must have to meet these requirements. These are analysis tools that can inform us of not only what has changed in the past, but what must be changed in response to a new initiative in the future.

The task of implementing SOX is only now making this need known to us, but that need has existed for years. As soon as we acknowledge this need--not only for IT, but for the company as a whole--the sooner we'll be able to resolve future legislative mandates that follow SOX and make our IT infrastructure meet the needs of our organizations.

Thomas M. Stockwell is Editor in Chief of MC Press Online, LP.

Thomas Stockwell

Thomas M. Stockwell is an independent IT analyst and writer. He is the former Editor in Chief of MC Press Online and Midrange Computing magazine and has over 20 years of experience as a programmer, systems engineer, IT director, industry analyst, author, speaker, consultant, and editor.  

 

Tom works from his home in the Napa Valley in California. He can be reached at ITincendiary.com.

 

 

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: