1 ... 9 10 11 12 13 Previous Next

Articles

182 Posts tagged with the article tag

by Elizabeth M. Ferrarini

 

Robert Mitchell jumped into "fire-chief mode" three weeks after he was promoted from senior director of strategic business analysis and strategic business implementation to CIO and vice president of operations at GTSI in Chantilly, Virginia. The go-live deployment of a $10 million PeopleSoft supply chain system, integrated into the company's current PeopleSoft HR system, disrupted operations at GTSI, a $1 billion provider of IT infrastructure solutions to government agencies. Because the first three months of the troubled deployment kept GTSI from delivering products and services to customers, the revenues for the publicly held company were jeopardized. Meanwhile, the company shelled out $1 million to fix the PeopleSoft problems.

 

Mitchell sat down with enterpriseleadership.org to discuss candidly how he perceives his leadership role, how he was able to get his arms about a negative situation, contributing  factors to what went wrong, and what he learned from the experience.

 

EL: You moved up from senior director of strategic business analysis into the role you have now. How did all of this prepare you for the CIO role?

 

RM: The CIO role is about being a business leader who adds value to the company, not about being an IT project manager. Looking at it from this perspective, my past job at GTSI and my previous positions were critical to my success as a CIO. They were about understanding the strategy, understanding the financials, and understanding the business process. They were almost always about having good relationships throughout the business and being able to know who to go to.

 

Most people associate PeopleSoft with human resources. We use PeopleSoft for all of our internal business operations, everything from human resources to our entire supply chain. Even our sales people use PeopleSoft to generate sales quotes.

 

EL: Several trade press articles talked about the major operational problems you had with a PeopleSoft supply chain deployment. What went wrong?

 

RM: As CIO, I inherited the PeopleSoft supply chain deployment, which had been run as an isolated IT project, not as process improvement for the company. IT was unsuccessful at getting the business involved in the deployment. It slowed everyone down and certain departments ground almost to a halt. The problems ranged from training in general, to this specific implementation. In addition, we brought in too many contractors. We should've hired employees to fill functions that required passing knowledge on to other employees. We didn't think through some of the required test plans and business acceptance issues associated with it.

 

The momentum to go live with the system by a certain date meant no turning back. I knew it was going to be very problematic when we went live. However, I also had a clear idea of how we were going to fix the problems, and how I was going to minimize them. If I hadn't jumped in and did some of the things I did on the business side, it would taken longer than 90 days to fix the problems.

 

EL: What did you do first?

 

RM: I had to engage the business in what was going on. They needed to understand that IT is basically a set of mechanics and a custodian of the system. They had to take ownership of the system and to learn how it works for them.

 

On my second day on the job, I got representatives from every department in the company to come to our board room, to sit down in front of the CEO, and to give him an overview of what the system meant to them. We built a council of people, our version of a governance board, to make decisions about system changes.

 

We set up a war room where IT people would come and get answers immediately, and we could prioritize and enter change tickets right away. We really made sure we had a clean process for addressing the most critical issues first.

 

EL: Was this the most challenging IT initiative of your career?

 

RM: Absolutely. There was an interesting twist to it. While it was challenging on one level, I found it easy to resolve because I knew what to do. Think about it for a minute. If the executive team thinks they need to make big changes to gain efficiencies, you have tremendous amounts of resistance throughout the company. On the other hand, if a badly designed system doesn't allow people to do their job, then everyone supports changing the system.

 

Creating a forum of people who were willing to take responsibility for their  system made the situation easier to manage.

 

EL: What other things did you learn?

 

RM: You have to deal with many aspects of change management. Specifically, you have to work through a variety of communications levels -- everything from executive, down to user community -- at the same time. You have to be very clear about who own the business process and who owns the IT automation process. Many people like to start with, "What does this system do for me?" If you don't change that attitude from the start, you're going to run into problems.

 

EL: As result of this experience, what formal IT best practices have you put in place, and how have you improved alignment with the business?

 

RM: We have a well documented, disciplined software lifecycle process. As a publicly held company, we have processes compliant with Sarbanes-Oxley. We've used many different sources to document, and to develop, these very processes.

 

As for alignment, we've created a synergistic environment in which the skillsets overlap between business analysts and IT functional analysts. For example, in IT, I have functional analysts with extensive PeopleSoft expertise who understand functions such as purchasing. Likewise, I have people indirectly reporting to me who manage the process and who also report to the functional department head. These people work hand-in-hand with their IT counterparts to make sure the proper implementation and requirements get done.

 

EL: What was your relationship like with PeopleSoft during your troubled  deployment?

 

RM: We didn't have a good relationship with PeopleSoft at that time. Both parties were at fault. Because it was trying to fend off acquisition attempts from Oracle, PeopleSoft didn't want to have negative press about a bad deployment. I made sure we kept focused on solving the problem rather than complaining to the trade press. This strategy helped to improve our relationship and gain access to some good people within PeopleSoft.

 

EL: Now that PeopleSoft is part of Oracle, what is your relationship like  with Oracle?

 

RM: Large companies, such as PeopleSoft, don't do a good job of being held accountable for what happens. You have to find a method to protect your interests. I started building relationships and getting conduits to certain Oracle vice presidents who can smooth out any problems. In turn, we've provided Oracle with architects who served on a leadership committee to define the future of PeopleSoft.

 

EL: Why did you eventually go public with the trouble PeopleSoft  deployment?

 

RM: We were approached by a reporter who heard about the situation. Because we had just come through the toughest part of the deployment, we thought it would be a good chance to talk about how we got our hands around the problem. After all, we took a beating on this. Out customers had experienced negative delivery ramification. We also had to satisfy our shareholders.

 

EL: Undoubtedly, you've reflected on this deployment. What conclusions  have you come to?

 

RM: Because I took over the deployment a few weeks before in went live, I had no trouble taking the high road and not pointing fingers at any one. If I had been spearheading the project right along, then everyone would have been pointing fingers at me.

 

Our president believes in being forthright. From the start, he acknowledged that we were having a problem with the deployment and talked openly about it. I operate the same way. I've pulled all of the skeletons out of the closet so they can be fixed. That's why it's important to leverage all the relationship you have.

 

--

 

Elizabeth M. Ferrarini is a freelance technology writer based outside  of Boston, Massachusetts. Reach her at elizabethferrarini@yahoo.com.

| More
200 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

by Elizabeth M. Ferrarini

 

Ben Salzmann is proof that a CIO can have a career as a C-level executive. After eight years as a CIO at Acuity, a property and casualty insurer that operates in 15 states, Salzmann was promoted to CEO. His leadership has brought a plethora of outstanding achievements to Acuity, which manages $1.8 billion in assets and writes $800 million in premiums. For three straight years in a row, the company has made the Great Place to Work Institute's list of the top mid-size companies to work for, and InformationWeek magazine's list of the top 500 most innovative users of IT in the U.S. That's not all: Acuity has received about 32 technology awards from ACORD, an insurance industry association. AARP also has named Acuity one of the best places for people over 50 to work.

 

Enterpriseleadership.org sat down with Salzmann to get his view of what it takes to prepare for the CEO spot, how he has created a great place to work, and how he has made smart decisions about using leading-edge technology. Here's what he had to say.

 

EL: As a former CIO, what helped you the most to take over the helm  at Acuity?

 

BS: As a CIO and a company officer, you see and interact with just about every department. You have a chance to develop a broad perspective about the business. However, you need to have the business inclination and an interest in becoming a CEO.

 

Some CIOs say "no" every time managers suggest a new way of doing something. From day one, the CIO has to listen to managers, to come up with  approaches that work, and then to provide them as plausible solutions. The CIO has to continue to find ways to make things work better.

 

A CIO who has come up the IT ranks has both a profession and an occupation. You're profession is as a technologist, be it systems or applications. The organization you work for determines your occupation within a certain industry. To climb the corporate ladder, you need to make a commitment to the organization, and to master both the organization's industry and business.

 

EL: If you're going to move up to become a CEO, you can't have a lot of adversaries. How does the CIO transition to being more of a colleague or business manager?

 

BS: First, the CIO needs to get him-, or herself, invited to important business meetings. For example, every time our underwriting field force comes to our headquarters, we make sure the CIO is present. He's viewed as part of the organization and can speak with underwriters during breaks and at lunch. If a CIO wants to earn recognition and get a sense  of ownership, he or she needs to demonstrate knowledge about what's going on in the business unit. Managers need to see this.

 

Also, CIOs should sit in on financial department meetings to hear everything that is coming. It gives them more ammunition for developing strategies about how to get things done.

 

EL: What is the biggest mistake some CIOs make during their  careers?

 

BS: Some of them take on massive mountains to climb, not realizing how long it takes to get to the top. A mountain climber goes up the mountain one step at a time. So, if you're constantly under a tremendous number of project deadlines, perhaps that's because your projects were poorly designed to begin with. Even if you have a large project, you're better off taking a baby-step approach and having a constant stream of deliverables you can provide on time and on budget. This approach might prolong the project a little; on the other hand, the IT team learns as they install smaller pieces.

 

EL: Does it matter to whom a CIO reports?

 

BS: It certainly does. I hope all of my competitors have their CIOs report to someone who isn't a company officer. This is a good way to hamstring the entire IT department. The CIO should report to the CEO and should be considered a company officer.

 

EL: How do you feel about outsourcing IT?

 

BS: Likewise, I hope all of my competitors outsource a major part of their IT organization. Our technologists built our claims system, our underwriting system, and our policy processing system. We wouldn't want to outsource a commercial underwriter. Yet, some insurance companies will turn around and outsource the development of their major systems. How many outsourcing firms really know the in's and out's of all phases of insurance? When you outsource IT, you pay them a small fortune to develop a moderate knowledge of your business, to use this knowledge to build a mediocre system, and then to move on to the next project!

 

EL: Should the CIO role be designed as a temporary, rotational  role?

 

BS: No. That type of model is an extreme belittlement of the  technology deployed in the organization. It's like having a  CIO-de-jour. Again, not employing this type of model helps my organization be more competitive. Good CIOs needs to have a technology background and business acumen. Their jobs aren't to explain the difference between a mainframe system and a network-based system, but to look at the organization and know how it fits into an enterprise technology model.

 

EL: For three years in a row, your company has been named as a great place to work. What are doing to make it such a great place?

 

BS: You have to first meet employees' basic needs; next, to listen to and communicate with your employees; and then, to provide them with a great working environment.

 

For example, since 2001, we haven't increased the health insurance premiums our employees pay, but we've improved their health insurance benefits each year. We contribute eight percent to their 401K plans, even if they don't put in a dime. We give them an additional 401K bonus so they will hit 10 percent of their annual income, even if they don't put in a dime.

 

We have an awesome suggestion committee, which goes over each suggestion submitted by employees. They can get a bonus for a suggestion. And, we hold town hall meetings where we bring in all the employees so they can get updates from the company officers.

 

Then we have our fun side. We've done everything from mechanical bull contests to chocolate fountains to Acuity's version of "American Idol." We hold our Christmas Party at a five-diamond establishment.

 

EL: You are one of the first companies in the insurance industry to  go paperless. Can you discuss the process?

 

BS: We started going paperless 16 years ago. We began with our personal lines, which insures houses and cars. As the file retention dates passed, we didn't have any paper to file. We worked with regulators and governmental bodies on how they can audit a paperless insurance company. Next, we went paperless in our commercial business lines, and in our claims systems. The advantages have been outstanding.

 

Wherever employees are in the world, they can use the Internet to not only check their email, but to go right into the personal lines system, the  commercial lines system, or claims system. They can read what's going on for a specific account, and then turn things around. For example, we can have 40 people at a time looking at the same system in 40 different locations. They all can be deciding on how to handle a multimillion-dollar business account.

 

By harnessing this technology, things happen fast, and we have no linear flow. Our work management system orchestrates all of the various reports we need to give to an underwriter. This way, the underwriter sees the entire picture at once and can make a better decision than if he or she were seeing bits and pieces over a few weeks.

 

EL: What's the biggest mistake insurance companies make when they go  paperless?

 

BS: Installing a workflow system at the same time as an imaging system can spell trouble for an organization. You end up imaging too many documents and making paper into intangible paper. For example, your computer can't calculate rates for an image of an insurance application: you need stored data. Many insurance companies have carried out their work management system in parallel with their imaging system.

 

In contrast, we did our work management system with our data collection systems and then brought in our expert system. We needed to put in the expert system before we put in our imaging system. If you put in the imaging system first, you're data-starving your expert system because your expert system can't read intangible paper or images.

 

EL: Because of your paperless environment, how have you improved the  quality of your transactions?

 

BS: We have world-class service levels based on rapid processing and very high quality ratios. We track every transaction for an entire year, and we announced that we have a 99.7 percent accuracy rate in a given transaction.

 

EL: You've won dozens of technology awards from ACORD --  can you  explain the significance of these awards?

 

BS: We've received more ACORD awards than any other insurance company in the country. ACORD is an insurance industry association vital to accelerating and advancing technology and setting standards for it. ACORD promotes the interface between insurance agents and insurance companies by standardizing  data and by promoting technology. The awards are to recognize technology leaders our industry.

 

At the ACORD LOMA Insurance Systems Forum in May 2006, we received seven national technology awards, including the Business Integration Enable award, the Early Adopter award, and the Greatest Number of Transaction Implementations award. For example, we received an ACCORD award for the way we download policy changes to our agencies' computer system, which automatically trigger the databases to update.

 

--

 

Elizabeth M. Ferrarini is a freelance technology writer based outside  of Boston, Massachusetts. Reach her at elizabethferrarini@yahoo.com.

| More
216 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

by Elizabeth M. Ferrarini

 

CIOs in corporate America worry about how IT is going to make their organizations more competitive. In healthcare, demographics, not IT, help hospitals to, for example, expand into new markets. To this end, healthcare CIOs view IT as a critical underpinning for process improvements that can help patient care and safety.

 

Dennis L'Heureux has firsthand experience finding the right technology to fit a hospital's strategic initiatives, as well as its tight budgets. He wears two hats as both CIO and vice president of planning hat at Rockford Health System, a 400-bed tertiary healthcare provider and the second largest specialty health care group in Illinois. His exemplary technology leadership has earned him a place on Computerworld's list of Premier 100 IT leaders.

 

Enterpriseleadership recently sat down with L'Heureux to talk about some of the ways technology has improved some key functions and to discuss how he's dealt with an influx of new C-level peers.

 

EL: How do you deal with the challenges of spending on technology while  keeping the cost of healthcare down?

 

DL: I can't draw a direct line between those. There's always an incentive to keep the cost of healthcare down. We struggle with this all the time because of the new government mandate for more price transparency.

 

Our business is very complicated. For example, each insurance company we do business with might reimburse us differently for the same procedure. If someone wants to pay cash, the price will be different, to. This entire situation continues to vector downward as the government and insurance companies want to pay less. Meanwhile, the cash consumer wants to pay less.

 

We have constant pressure to provide the same types of services with better  quality and safety for less and less money.

 

EL: Can you talk about situations where IT has helped the hospital saved  money?

 

DL: A basic assumption in healthcare is that the use of IT over the long run will reduce costs. This is very hard to quantify across the board; however, I can cite some tangible cost savings. Because we've put in electronic medical records system, we've saved on file room clerks and don't have film expenses anymore.

 

And, I can say that technology is helping a radiologist come up with a diagnosis in less time than he or she did before, for example.

 

EL: What process improvements have you made at Rockford Health  System?

 

DL: We've eliminated the need to go looking through old film files trying to compare a patient's X-rays taken today with those taken three weeks ago.

 

We also centralized the scheduling of outpatient routines. Previously, physicians had to call a specific lab to make an appointment for an outpatient. The new system now allows physicians to call one number for all of these procedures. It also allows physicians to identify where any combination of those tests can be done for the patient. That's a pretty significant process improvement.

 

Finally, each year, our employees have to select their medical coverage for the following year. At one time, we mailed each employee a thick paper packet. Now, we have all of the information online.

 

EL: How automated are your medical records?

 

DL: We've automated a significant part of the records, including histories, physicals, all lab tests, all EKGs, all radiology tests, all surgical notes, all mammograms, and all cardiology tests. We haven't automated our nursing notes. That a big project.

 

EL: What are some of the best practices you have put in place for  IT?

 

DL: For the past 12 years, we've had a decent governance structure for how we use IT and the investments we make in it. Our Information Management Services Advisory Council consists of representatives from the physicians practice, nursing, administration, finance, and IT. This is a key best practice.

 

We also see our technology resource center as a best practice. If we'd had to outsource it, we wouldn't have pulled off the service levels that we now provide. We are proud of that.

 

EL: In some healthcare organizations, the CIO reports to the CFO. How do  you feel about that?

 

DL: The data suggests that if you report to a CFO, you have less flexibility and less investment in IT than if you reported to a CEO. You have the challenge of making sure you invest in the right things.

 

I'm fortunate to report to the CEO. In fact, I have survived five CFOs.

 

EL: How do you deal with the changing of the guard in C-level peer  positions?

 

DL: A new CFO may come in and ask questions -- why don't you do this and why didn't you do that? The answers can be simple. However, a lot of times, solutions and decisions have been made along a very complicated set of criteria. It's difficult to explain all that.

 

You have to retell your story constantly, not recreate history. You need to get the new CFO to understand where you are today and why. I like to sit down with the new person and go through all of my governance structure. Then, I list out all of the inventory of things we have, and talk about the investments we have made and what I think is still deficient. This tactic has worked very well for me.

 

You need to build good relationships with your C-level peers. These relationships help you to have an amicable conversation about crucial topics. If you don't have these good relationships, you'll cross swords every time you meet to discuss an important topic.

 

EL: How do you align IT with the hospital's business objectives?

 

DL: Because I was promoted to senior vice president, I am also in charge of strategic planning. It's easy for me to connect those dots. When we created our strategic plan for our company, we had six drivers. My schematic charts shows IT as the foundation for each one of them; IT doesn't sit as the seventh driver. We view IT as a support function, not as a way to create new markets.

 

New markets in healthcare come about by things such as demographics, unemployment, and employment. As we try to capture the market share for good paying customers, we try to leverage IT.

 

EL: What's the most pressing priority you have right now as far as a  project goes?

 

DL: Right now I'm working on using technology to provide better patient safety between the pharmacy and the nursing departments, which order, confirm, and dispense medications. We've mislabeled it as a "bar coding project," but it has many more components and processes than just bar coding.

 

At the time, the vendor we purchased the product from didn't have RFID. We're still months ahead of this implementation, so we've delegated someone to look into RFID and to see if it makes sense for us. I wrote the contract for bar coding, but if RFID is the way to do, then I'll have to reopen the contract and say I'd prefer RFID.

 

Prototyping often leads to two separate processes. That can be dangerous. We want to play it save and to stick with standard processes.

 

EL: What professional organizations help you to network with other  CIOs?

 

DL: I participate actively with the College for Healthcare Information Management or CHIME. About three times each time, I check with my CHIME colleagues to see how they are doing things, and what issues they are having.

 

--

 

Elizabeth M. Ferrarini is a freelance technology writer based outside  of Boston, Massachusetts. Reach her at elizabethferrarini@yahoo.com.

| More
228 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

by Elizabeth M. Ferrarini

 

Dr. B. Joseph White has studied and practiced leadership for more than 30 years. Since January 2005, he has been president of the University of Illinois, an academic institution with 28,000 faculty members and staff, 70,000 students, 21 Nobel laureates, and an operating budget of $4 billion per year. Dr. White has also gotten to know notable leaders, including Steve Jobs, Madeleine Albright, and Archbishop Desmond Tutu. In his new book, The Nature of  Leadership: Reptiles, Mammals, and the Challenge of Becoming a Great  Leader, Dr. White shares what he has learned about the blend of capabilities it takes to lead successfully -- and the secret to truly great leadership.

 

The Nature of Leadership reveals the dichotomy at the core of every effective leader: being part reptile -- analytical, rational, and tough as nails -- and part mammal -- nurturing, participative, and warm as toast. The book also has a leadership pyramid that shows the traits of a great leadership at the summit, and the traits of the reptile and mammal next to each other.

 

Enterpriseleadership.org recently talked with Dr. White about his book and his views about how CIOs, especially, can become great leaders.

 

EL: How would you rate the leadership abilities of most CEOs of the  Fortune 1000 companies?

 

BJW: Today, executives are under a lot of pressure to achieve high performance; to deliver top-line growth and bottom-line growth; to provide strong returns on investment, and most importantly, to grow the share value of their companies. Such performance includes a combination of good leadership and good luck.

 

Unfortunately, CEOs often don't have a lot of time to turn weak performance around or to improve on good performance. Their abilities to do so are extremely varied. The average tenure of CEOs has gone down to less than six years. Many boards and owners figure that if the CEO hasn't achieved strong performance after a couple of years, he or she isn't going to do it. Some CEOs have 18 to 24 months to prove themselves. To this end, CEOs need to have great leadership abilities and the wind at their back, too.

 

EL: Most of the executives profiled on Enterpriseleadership.org represent technology leaders in large organizations. These people are usually chief information officers (CIOs). What would you recommend they focus on if they want to become CEO of a company?

 

BJW: Information executives who want to become CEOs should focus on three areas: make sure their financial ability is first rate, make sure their people skills are excellent, and make sure they know how to develop a track record of making substantial consequential change.

 

The ability to change sits at the top my great leadership pyramid. A leader's success today depends on his or her ability to make consequential change, such as turning around an under-performing company. For CIOs, this type of change usually means leading the migration from one major system to another without missing a beat. For CEOs, it means doing things to foster internal growth, containing costs, and making smart acquisitions. All of these things will help to grow the market value of the company.

 

Most CIOs have strong change-making leadership skills. They've acquired years of experience taking their organization through generation after generation of new technology.

 

On the other hand, CIOs need to develop their financial skills. Often, CIOs function as budget managers, lacking first-hand experience dealing with the corporate profit-and-loss, and cash flow. And, some CIOs who are very good technically might also need to hone their people skills.

 

EL: In your book, you define five qualities you define for great leaders, and you mention having a "helicopter view" of the past, future, and current events. How can executives, especially CIOs, develop this helicopter view so they don't get a cloudy picture?

 

BJW: They need to learn all of the business's dimensions. CIOs who want to become CEOs need to be able to go from being professional heads of an organization to being general managers. GMs have a broad perspective, or, the helicopter view, which is knowledge of the business's past, its present, its future, and its functions, and how they fit. This view is also called strategic thinking. This is what boards look for.

 

EL: How do you feel about rotating CIOs through the business so they  can develop a helicopter view?

 

BJW: I first saw that being done 30 years ago with big Japanese companies. Executives in Japanese companies often rotate through operational areas such as finance, manufacturing. This is how you learn about the business and all of its dimensions. CIOs would get a lot from the experience. For example, going into the corporate planning function would help a CIO become more of a strategic planner.

 

CIOs, as well as CEOs, should never stop learning by reading good business  books. Tom Friedman, the author of The World is Flat, has become very  popular with executives because the book helps them to develop a helicopter view  of things.

 

EL: Some companies have programs to encourage innovation. How should  these programs be structured?

 

BJW: Because leaders are responsible for making change successfully, they need to have a great interest in new ideas. This applies to everyone from CEOs down to managers of small workgroups. Innovation begins with the process of turning these ideas into reality.

 

In my book, I share some of my experiences leading innovation efforts. I developed a concept called "the presumption of yes." lf someone comes forward with a new idea, there is the presumption of yes that we will carry it out.

 

Leaders need to have creative ways to encourage employees to come forward with good ideas about doing things better. Often, employees hear everything from "it's too expensive," to "we've tried that before and it didn't work." "The presumption of yes" helps a leader promote the value of innovation in an organization.

 

EL: Your "great leadership pyramid" ranks risk-taking at the top. What happens when a leader takes a risk that doesn't benefit the organization?

 

BJW: Every leader needs to understand that risk-taking involves a batting average. No one always bats 1000 -- not in baseball, and not in leadership. If you're batting 1000, you're probably not taking enough risk. If you're batting 250, you're probably taking too much risk, or you're not managing your risks very well. If what you try fails, there's nothing inherently wrong with that; you need to look at your batting average over time. A good leader should be batting about 650. In other words, one out of the three things you back, or attempt to back, ought to end up being successful.

 

EL: Some great leaders, like Steve Jobs of Apple and Larry Ellison of Oracle, are known to be tough on their employees. Should you admire a great leader, but avoid working for one?

 

BJW: You have to distinguish between great leaders and people whom you would personally select to work for. Keep in mind, there are a lot of paths to success in businesses. Some executives advocate that, you either  perform, or you're out of here. Some of us might not want to work in that kind of culture. It doesn't mean the organization won't be successful. Executives like Ellison and Jobs rate high at the top of the pyramid skills. They're very innovative, like to take risks, have the helicopter view, and sizzle with a lot of sparkle. They also attract the most talented people. They're also very good on the reptile side of the pyramid. However, they aren't very good on the mammal side of the pyramid, which explains why you might not want to work for them. Because I've spent some time consulting with Steve Jobs, I saw up close how he gets great people to work for him, even though he is rough on them: He makes them rich. It's the same with Ellison. A lot of us would opt to work for more nurturing leaders, but that's not the only way to be successful.

 

EL: Where does governance belong in a company?

 

BJW: The number one task of a board of directors -- the chief governance committee -- is to select a person to lead the organization. This person is either a great leader, or is someone who has the ability to become a great leader in a short period of time. If a governance committee does just that, things will go just fine. If they don't, they can do everything else, and the organization will not perform very well.

 

--

 

Elizabeth M. Ferrarini is a freelance technology writer  based outside of Boston, Massachusetts. Reach her at elizabethferrarini@yahoo.com.

| More
201 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy
by Elizabeth M. Ferrarini

JackStahl.jpg

 

Jack Stahl has all of the right qualifications to write his book, Lessons  on Leadership -- The Seven Fundamental Management Skills for Leaders at All  Levels (Kaplan). During his 22-year at mega-brand marketer Coca Cola, Stahl held many executive positions including chief financial officer, chief operating office, and president. In 2002, he left Coca Cola to become CEO of Revlon, a well-known consumer company struggling to deal with a $1.76 billion debt load. For five years, he led the company through a critical period of strengthening Revlon's market share, profitability, balance sheet, and brand awareness.

 

Stahl left Revlon in 2006. He has lectured at HEC, an elite graduate business  school in Paris, and at New York University.

 

Enterpriseleadership.org recently sat down with Stahl to talk about his book and his leadership experiences at both Coca Cola and Revlon. Here's what he had to say:

 

EL: You took Revlon through a difficult financial phase. Why did you  decide to leave?

 

JS: I joined Revlon to help the executive team stabilize the company's financial situation and to accelerate the growth of the Revlon brands. We completed both goals. After five years, I had accomplished most of the things I set out to do. I also brought in about six people, one of whom was very well prepared to take the company to the next level. I was fortunate to have had a good leader behind me. I wanted to finish my book, to teach, and to serve on some corporate boards. It just seemed like the right time to leave.

 

EL: As a member of the executive team at both Coca Cola and Revlon, what type of a governance model did you have for getting strategic initiatives done?

 

JS: Companies undergoing a lot of fast-moving changes, such as Coca Cola and Revlon, need to have senior people who understand every aspect of the business. We had an executive operating committee that focused on, not only the strategic direction of the company, but at all the details of important projects. This committee met weekly for a minimum of three hours, and we dug deep into key projects at every level possible. Our important decisions could change the environment. I would call it a very active, hands-on approach by a team of very experienced people. We expected other leaders in the organization to follow that same model, so they would be actively involved in projects they were accountable for.

 

EL: How did you drive innovation at either company?

 

JS: In both cases, driving innovation has to start by hiring people who are  intellectually curious, who are open to new ideas both from inside and outside the company, and who are aware of what's happening in the world as a whole.

 

You also need to do good market research focused on the needs of your customers. For example, at Coca Cola, we studied the lifestyle habits of consumers from the time they got up to the time they went to sleep. This research provided us with a good understanding of their beverage needs, which we translated into beverage marketing opportunities for us. Because people are spending so much time in their car, we created a resealable package that would fit in a cup holder.

 

EL: In your book, you talk about how Coca Cola helped one customer who was going public and another customer become more competitive. What benefit did Coca Cola get from doing this?

 

JS: At Coca Cola, we felt that selling beverages was an important aspect of our customer relationship. If we had knowledge or expertise that could help a customer's business, then we wanted to offer it. We followed the same philosophy at Revlon. By exposing customers to different types of functions, you can bring them a lot of value that goes beyond traditional approaches.

 

EL: You learned a lot from Robert Goizueta, the former CEO of Coca Coca Cola. In your book, you say that "he knew not only how to assess employees, but also the positions they inherited." What advice would he give to CIOs who want to move into higher C-level roles?

 

JS: Although CIOs focus on information technology, they use many leadership skill sets, which include identifying problems and opportunities, planning against these, executing and getting things done, and communicating and developing an organization. These same skill sets are important in any executive leadership role -- whether it's as a CEO or the director of a business unit. My advice would be to remember those skills that allowed you to be successful in the world of information. Many of those same skills translate over to general management.

 

EL: In your book, you talk about information reporting tools, links to strategic plans, and health of the organization. Did you do anything with the Balanced Scorecard or Six Sigma at either company?

 

JS: Although I've never worked directly with those best practices, I'm quite familiar with their methodology. In the book, I outline some of the key approaches we used to manage very large projects and work efforts. You first need to start with having a clear set of goals and objectives, aligning resources and people around those goals, and building very detailed timetables. As you go about tracking execution, you can't make any assumptions. You always need to follow up and to ensure that people are communicating when they see issues and land mines. They need to bring up issues and problems so they can get solved. You can argue that these are fairly basic models and approaches. They certainly worked inside of Coca Cola as we developed products, and took companies public.

 

EL: Besides the former CEO of Coca Cola, are there any management  practitioners who have become your role models?

 

JS: I like author and management consultant Rom Chiaran, who has written numerous books on leadership topics. He takes a very thoughtful approach to the topics he covers. I talk to him periodically. He's provided good coaching for me. I also like the work of Stephen Covey, who wrote the Seven  Habits of Highly Effective People. His book is terrific.

 

EL: Have you worked a lot with IT people? What areas of IT needed  improvement?

 

JS: When I was the COO at Coca Cola, I was responsible for IT. I needed my IT staff to focus on being able to understand the business need and then to help the business partners make resource choices. The days of IT professionals encouraging their business clients to pull off service and IT resources as they wanted don't exist anymore. We're in an era of prioritization and focus. The most effective IT professionals help their business clients and partners prioritize and make those important choices about what areas are critical to the business.

 

--

 

Elizabeth M. Ferrarini is a free-lance technology and  business writer from Boston, Massachusetts. Reach her at elizabethferrarini@yahoo.com.

| More
197 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy
by Elizabeth M. Ferrarini

 

The Harvard Business Review article (May 2003), "IT Doesn't Matter," by Nicholas G. Carr, caught the attention of CIOs at Fortune 500 companies, academics at Ivy League universities, and executives for major computing vendors. While Carr isn't claiming that IT doesn't matter, he, on the other hand, asserts that IT has diminished as a source of strategic differentiation for an organization. Carr says that extracting value from IT requires innovations in business practices. For example, he says that organizations need to manage large portions of their IT infrastructures more rigorously to reduce capital investment requirements and operating costs.

 

No one knows the value of doing what Carr suggests than Kin Lee, senior vice president of IT infrastructure at Honeywell in Tempe, Arizona, and a graduate of Harvard Business School. Lee oversees the global voice network and data network infrastructures for the $20 billion diversified technology leader's four business groups: aerospace, automated control systems, specialty materials, and power systems. Last year, Lee reduced IT expenses for the infrastructure from $650 million to $510 million -- a $90 million cost savings.

 

"IT isn't about technology any more. It's about how do you run this organization as a business." Lee says. "If you need to provide more bandwidth to a business unit, then you have to provide an expected payback. You also have to sell your ideas, not only to corporate management, but to each business unit, which might have ideas that differ from another business unit. You have to know how to bridge these gaps so you can deploy your agenda." Lee's strong technical and strong business background have well prepared him to run his organization. He has a technical undergraduate degree, a master's degree in operations research from Northwestern University, a master's in business in finance from the University of Chicago, as well as the Harvard credential.

 

Lee recently took some time to discuss his organization's IT model, to describe the use of best practices such as Six Sigma, and, of course, to comment on the Harvard Business Review article. Here's what he had to say.

 

EL: What does the infrastructure you manage consist of?

 

KL: My organization oversees and owns 6,000 servers worldwide and five mainframes. Most of the servers are midrange AIX servers. The rest are either Novell or Windows servers. We also manage 1,000 engineering workstations, and 85,000 global workstations at 1,000 locations. We manage the wide area network, the local area networks, and all of the voice communications, and consumable communications devices, such as cell phones. About 120 employees, as well as employees from our two major outsourcing suppliers -- IBM and AT&T -- manage the entire IT infrastructure.

 

EL: Tell me why you became a shared services IT organization and how  you've driven down IT costs throughout the company?

 

KL: In 1999, we began to centralize our services as a result of Honeywell's merger with Allied Signal. Before that, each business unit provided its IT support and its equipment. Our distributed model evolved into a centralized model, which enabled us to become a shared services provider. We outsource our computing maintenance requirements to IBM Global Services and our voice communications networks to AT&T.

 

The business units have IT professionals who support business applications, not the infrastructure. We work with these folks to understand if there are any unique business reasons why they need to do something a certain way. For the shared services model, we referred to Gartner Group's technology road map, as well as called upon other industry groups.

 

We reduced costs by re-negotiating our two major outsourcing contracts based on adding volume, such as the integration and consolidation, as part of the baseline services, and redefining service level agreements.

 

EL: How have you established costs for your services?

 

KL: We have a very detailed cost structure for our services. For example, we offer several graduated types of support for servers. The enhanced support is for servers requiring 7 by 24 availability and redundancy. The base support is fine for servers that need 8 by 5 support. Naturally, the enhanced support will cost more than the base support. The business decides what type of support it will need for each class of servers and their applications.

 

EL: Every aspect of your company uses Six Sigma. However, does your organization have any experience with the international best practices for delivery of IT services, called the IT Infrastructure Library (ITIL)?

 

KL: We adopted many of the elements of the ITIL service delivery framework, such as the service desk and capacity planning, and combined them with the Six Sigma discipline as a way to measure what we do.

 

For example, many companies measure performance at a component level -- a server's uptime. This type of metric doesn't mean a lot of things to business units. They want to know if we can get the job done. A lot of components form the user's experience. So, we have to monitor the end points for business computing, and then measure critical business computing.

 

EL: What does the Six Sigma training consist of?

 

KL: Six Sigma has three levels of certification. Everyone in my organization must achieve Green Belt certification. Mastery of this expert level consists of going through the training program, forming a project team, and carrying out a specific project to demonstrate use of the appropriate tools and the ability to obtain business results.

 

The tools consist of a cause and effect matrix, and a lot of control charts, which we use to report results to the business units. We use many Six Sigma tools to report our performance measurements, as well as to show the variation of performance. Perhaps, we need to reduce some of this variation.

 

EL: What projects are you currently working on that concern the  business units?

 

KL: We're still integrating all of our business acquisitions through projects such as service domain integration, and data center integration. We have a major initiative to go global by locating many transactional servers in regions such as Eastern Europe or Asia Pacific. Some of these servers will be doing network monitoring. We're increasing the amount of bandwidth to those areas. To date, we moved several U.S. data centers to our headquarters, and consolidated two data centers in Europe.

 

EL: Can you give me an overview of how your organization manages  storage growth?

 

KL: Over the years, we have cut the cost of storage management by consolidating many storage devices on to highly available EMC Symmetrix systems, as well as on less expensive types of storage arrays. Identifying critical data is a key requirement for us. To this end, we work with the business units continuously to understand which applications are critical and where the allocated data resides for those applications. If the data doesn't need to be kept online, then we archive it either to an online device or a nearline device. The data is still available as far as the business units are concerned.

 

EL: What does your manpower requirements look like for the next  year?

 

KL: Our headcount will remain flat. On the other hand, we're changing the skill sets to put less emphasis on technical knowledge, and more emphasis on business management, program management, and supply chain management. They can demand a 100 uptime for some things, but can they afford to pay for it?

 

EL: What did you think of the Harvard Business Review article, "IT  Doesn't Matter"?

 

KL: Any one in IT would disagree with the article. If you use IT as a commodity, then the organization will loose its competitive edge. On the other hand, if IT does not provide the right type of metrics, IT can impede the organization from staying innovative. For example, we're creating a data portal that connects all of the different sets of data -- change management data, service-level performance, capacity, and financial -- onto a dashboard for each business unit.

 

EL: This is the sixth year in a row that Honeywell has received Computerworld's award for one of 100 Best Places to Work in IT. What's unique on your IT environment?

 

KL: Honeywell provides a supportive culture that enables IT professionals to have a very productive, collaborative relationship with the business units. IT professionals also work with peers from major organizations such as IBM and AT&T. These companies also have best practices they must follow. IT professionals can hone their business skills through disciplines such as Six Sigma. have to change the skill sets because our main function consists of managing our suppliers. We have a lot of people who have enhanced their technical undergraduate degrees with a master's in business administration.

 

EL: Since you service four distinct business units, how do you keep  projects straight? How do you charge for your services?

 

KL: That's always a challenge for this type of an organization. Each one of our business units has a different set of customers and requirements. When we sit down with a business unit, we always talk about their requirements from both an application and a financial perspective. Technology is a given.

 

We have a program office run by 15 individuals. They work as the liaison between IT and the business for demand planning, forecast of business growth, and specific business requirements. Once a business unit's requirements have been established, the program manager works with the engineers to create the solutions, and then communicates with the business units to make sure the solutions meet the agreed upon requirements.

 

EL: How is your organization measured?

 

KL: Our overall success gets measured based on the aggregate of how well we're doing. For example, we measure our performance by service level agreements or commitments we publish to the business units. We also have financial targets we need to meet. However, if we're meeting the service level agreements but the business units aren't happy, then we're doing something wrong. That's why were putting a lot of emphasis on managing the end-to-end user experience and expectation versus the current service level agreement.

 

We also rely on customer satisfaction surveys that allow business units to say what they like and don't like about the IT support. We try to target a rate of eight out of 10 in each of the categories on a customer satisfaction survey.

 

--

 

Elizabeth M.  Ferrarini is a freelance technology writer based in Boston,  Massachusetts.

| More
207 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

by Elizabeth M. Ferrarini

 

With annual revenues exceeding $21 billion and 80,000 employees worldwide, Raytheon Company ranks as an industry leader in defense and government electronics, space, information technology, technical services, and business and special mission aircraft.

 

With more than 27 years of experience in the defense industry, Rebecca R. Rhoads, Raytheon's chief information officer, oversees the development and implementation of company-wide information systems, as well as the company's technical direction in IT. Because of the nature of Raytheon's business, Rhoads also has the daunting responsibility of managing  risk not only domestically, but in all of the international facilities where the company does business. She recently talked to Enterpriseleadership.org about governance, best practices, and risk management. Here's what she had to say:

 

EL: How is the IT organization structured at Raytheon?

 

RR: The IT organization has 3,000 professionals, comprised of infrastructure and data center, engineering automation, and engineering computing.

 

We have three different organizational models for IT. Each of the seven divisional CIOs oversees specific business units, and each business unit has IT employees who report to the divisional CIO. These employees provide unique services to their respective business unit. We have a shared service environment for functions that need to be managed across the enterprise, such as data centers, and we have IT executives who function like a ship's rudder. They make sure we have a solid strategy, a robust architecture, and an air-tight risk management.

 

EL: What is your governance model for how you gauge the effectiveness  of it?

 

RR: The IT governance model mirrors the company's overall governance model for making decisions and managing investments. As a result, our decision model and our vocabulary are consistent with how we run the business and how we run the company.

 

This governance model has proven to be a big advantage for us. It's one that's easy to teach, and one people are familiar with. It provides a good way to make sure we're aligned with the business and the company, and they can engage in the decisions more effectively. They understand what their role is when we get to certain gate reviews or certain decision steps. We use this for our major investments.

 

The other IT governance we have in place consists of a CIO cabinet of the seven divisional CIOs and me. The cabinet enables us to manage across very different businesses.

 

EL: What are some of the best practices you use?

 

RR: Our Raytheon Six Sigma program provides us with important capabilities we've used to develop IT. In fact, Six Sigma is inherent in every new system, in every new process, and in every process improvement opportunity we take on. When the company first rolled out Six Sigma, we made sure everyone in IT had some type of Six Sigma training. Some people got qualified as specialists, while others became certified experts.

 

EL: Given that Raytheon is a global defense contractor, how is IT  making the company more competitive?

 

RR: First of all, we had to figure out what the role of IT was. We've grown as a merger of different legacy companies. From an IT perspective, we had one of each type of system connected to each other. We've done a lot of work to simplify our complex environment. Mission assurance is our way of removing all doubts about the quality or the performance we deliver to our customers.

 

We've created an environment that makes it easier for not only the company to work quickly and with agility, but also for the businesses to collaborate and work together. Because we have so many varied capabilities in the businesses, we had to integrate the different functions through common processes and through common systems. Now, things work together seamlessly. Bringing these capabilities together enables us to have the most competitive offering.

 

EL: A 2003 CIO magazine article talks about the high number  of IT project failures you were having. How did you improve things?

 

RR: The success of project management depends on how well you succeed with risk management. Getting risk management under control helped us to lower our project failure rate and helped us to achieve our cost-performance targets.

 

For IT, we used two risk management tools well established at the company -- decision tree analysis and, what we call, failure reporting and corrective action. We learned that many of our IT risks were self-imposed because our processes weren't very mature and weren't common processes. Once we got these things taken care of, we were able to manage risk in a more balanced way.

 

EL: Can you talk about some of the risks you've taken as CIO and what  you learned from each one?

 

RR: A big risk consisted of moving our IT structure and organization to mirror the company's structure and processes. Because we must keep everything running around the clock, I was concerned that we might run into a snag, such as a significant degradation in performance, if we were perceived as an operating model. In other words, a lot of people might not see the value of what we did until after we did it.

 

In 2005, we took another risk by creating a common control environment to manage Sarbanes-Oxley risk and compliance requirements. Because we didn't have common systems, our internal auditors and our external auditors didn't understand the value of having common controls.

 

We now have a common set of controls as you move from business to business. These controls have improved our overall risk management model significantly. At the front end, it took a lot of managing to get that done.

 

EL: What risk or risks are you now facing?

 

RR: We're facing a very big financial risk with our commitment to SAP. Instead of having each business unit carry out SAP, we've put together a strategy to carry out one SAP environment for all financials. This type of arrangement will tightly knit the company and the businesses. This initative took longer and was harder to carry out. Now that we're at the end of the deployment, we're seeing the advantages it will provide us.

 

--

 

Elizabeth M.  Ferrarini is a freelance technology writer based in Boston,  Massachusetts.

| More
249 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

by Elizabeth M. Ferrarini

 

CNN has expanded its reach to include nine cable and satellite television networks; two radio networks; four Web sites, including CNN.com, the first major news and information Web site; CNN Mobile and CNN Newsource, the world's most extensively syndicated news service. Turner, part of the Time Warner family of media companies, is also home to familiar cable TV networks such as TBS, TNT, Cartoon Network, and Turner Classic Movies, as well as specialized networks such as Boomerang.

 

Because of the diverse nature of the Turner family of businesses, Scott Teissler, Turner's chief information officer and chief technology officer, has the ultimate challenge of weighing technological advances versus understanding and fulfilling the needs of the advertising community. Teissler, the former senior vice president of new media strategy and chief technology officer for CNN, recently sat down with Enterpriseleadership.org to discuss how his organization pushes the technology envelope so Turner businesses always have a competitive edge. Here's what he had to say:

 

EL: Apparently, your IT organization doesn't meet the conventional structure for IT departments. Can you explain how things are set up?

 

ST: About 2,000 people report to me. What we call "IT" is organized in a consolidated technology unit, comprised of IT software development, IT infrastructure, new media software development, research and development, and broadcast technology. The entire organization shares these IT resources. The business units don't have independent technology establishments.

 

EL: Given the diverse nature of the Turner businesses, what types of customers do you have to deal with regularly and how do you make technology decisions about what's best for them?

 

ST: We have several different types of customers for our principal business, or what we call "linear networks." The primary customers consist of our distribution affiliates and satellite operators. They know how they want to evolve their services and present them to consumers. We have to be aware of their strategies, and they have to do the same.

 

Another group of customers are the ad agencies and the advertisers. They are interested in both how we're evolving our presentation capabilities within our linear products and within our networks. They're also interested in the kinds of collateral possibilities we have for presenting advertising in our new media products.

 

Our new media business has mostly advertising customers. Here, we go directly to our audience with the package through our distribution affiliates. We have a number of decisions to make about how to track the technical developments and strategies for these different groups. We also need to realize that they all have plans and notions about how their platforms will evolve. To this end, we have to stay current with those marketplaces and the technical evolutions occurring in them. We can't afford to make price decisions based on the marketplace.

 

EL: Since you have such a diverse IT organization, what does your  governance model look like?

 

ST: We're lucky at Turner. Members of the senior management team communicate very well with each other, and also trust each other. It's a stable organization. These qualities make the technology governance process more practical.

 

Most CIOs or CTOs indirectly report to everyone who runs the overall business. What you do is part of their strategy. If you over-formalize or isolate IT governance by quarter or month, you miss out on a lot of interaction with these people. The best way to handle IT governance consists of giving general management a lot of exposure to all layers of IT. Make them participants who can drill down into the IT organizations.

 

EL: Since you don't have a formal governance model, how do you gauge the  success of IT with the business units?

 

ST: You have to look at how the businesses that technology supports are doing. Our mainstream businesses tend to be number one and number two in their category, and we have an outstanding reputation for advertising support and deal stewardship. Users give high marks to our new products, such as CNN Pipeline. So, we can conclude that everyone is doing a good job, especially in the area of product development and support. Measuring problems with back-office systems requires a lot of probing. Two organizations might be delivering great support. On the other hand, one organization might be consuming more capital because it's hyper-refining some applications. It's tough to determine when the line has been crossed.

 

EL: Do you use any type of best practices, such as CobIT or Six  Sigma?

 

ST: We're aware of the science that best practices entail. However, we don't practice specific ones, chapter and verse. We're not obsessed with obtaining certification in a particular method. Why? Best practices tend to spawn industries, consisting of a software science that uses big claims to get people to use the practice uncritically.

 

We have a good program in product management discipline, we pay a lot of attention to our software development methodology, and we use cutting-edge methods. There's a positive feedback relationship between using such methods and tracking the most interesting talent in the marketplace.

 

In summary, we're trying to extract what's best intellectually from those standards and to adopt them without becoming converts to a specific one.

 

EL: You're both the CIO and CTO at Turner Broadcasting. Is this the IT  norm at the other Time Warner companies?

 

ST: Years ago we abandoned the single company-wide CIO and CTO. Each business now has a CIO and or a CTO. Our small committee of these executives meet regularly.  I chair the CTO committee; someone else chairs the CIO committee.

 

Time Warner corporate has about 100 employees who mainly engage in strategy and coordinating some activities across the companies. Operating governance occurs in each business. activities across thecompanies.  The operating governance of the company occurs in the big individual units.  Practically all of the Time Warner companies are number one or two in their industries.  That's the level each CIO and CTO has to focus on.

 

The CTO group, for example, has one challenging mission -- to make sure that general management around the company, including Time Warner and its divisions, can navigate the digital landscape ahead him or her. Digital leadership, which we call it, consists of having executives you can devise and carry out successful technology strategies.

 

To explain contingencies adequately, CTOs have the daunting task of separating policy from strategy and also from marketplace development. Many of the strategic problems don't lend themselves to consensus solutions. The CTO has to explain things to general management so it's not frustrating for both sides.

 

EL: What disruptive or innovative technologies are you considering for  your business units? Anything that really stands out?

 

ST: We have a lot of things going on. Wireless, however, ranks at the top of the list for us. For example, CNN has had a long history of product development for wireless platforms. In fact, CNN News is probably the most widely distributed wireless in the world among cellphone operators.

 

You might say that wireless will become the next generation of broadband, without a lot of broadband's current limitations. Wireless is going to be faster, less expense, and to support more programming functions than today's broadband.

 

Today's consumers turn over wireless handsets every two years. It's a completely global enterprise. There's an enormous scope still for product development and service development. All of the Time Warner businesses will use it and benefit from it. Turner has content, especially news, suited to this small form factor.

 

Something else we're looking at is how advertisers will change the nature of the selling progress. Many of the new e-commerce platforms have given us better methods for measuring the delivery of advertising-type material. Now advertisers and their agencies are finally getting smarter about how to measure their success.

 

Within the next five, to 10 years, ad-supported businesses will see a change in the way we measure our success and our ability to sell advertisers. Things are going to become more complicated, granular, and perspective. This change in how people look at advertising campaigns is going to affect a lot of big businesses.

 

EL: Do you have an innovation team or innovation centers?

 

ST: We have two parallel organizations. Platform R&D pumps knowledge into the company from external sources. This group just doesn't talk about new products, but develops and deploys prototypes. In contrast, the new products group filters ideas in order to steer resources to pre-business development efforts. Platform R&D gets ideas generated from the new products group.

 

We don't have such centers scattered around the country. Our platform R&D group will support permanent digital field trials. We'll program new content on personal video devices, and then hand them out to a panel of consumers for their review. These field trials serve as a resource to our ad sales business units, which have relationships with the advertisers and their agencies.

 

--

 

Elizabeth M. Ferrarini is a free-lance technology writer from Boston,  Massachusetts.

| More
338 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

by Elizabeth M. Ferrarini

 

As one of the world's largest producers and distributors of flooring for residential and commercial applications, Mohawk Industries operates a large and complex business made up on 19 acquisitions since 1990. The company offers its 30,000 customers a broad line of premier carpet, ceramic tile, natural stone, and home products. In 2005, the company did more than $6 billion in revenues and acquired a Belgian company, which does about $1 billion in sales.

 

Mohawk is a vertically integrated company with 56 manufacturing locations, 56 warehouses and distribution locations, 256 sales centers that distribute products to the wholesale channel, and a transportation infrastructure of 2,000 trucks and trailers. Each business line is a start-to-finish production process. For example, the laminate floor process begins with wood chips and ends with the finished product. As a result, the IT organization must actively be involved at all levels of the company's business and strategies, down from the office of the chairman to workers on the plant floor.

 

Recently, Don Riley, CIO of Mohawk Industries since 2004, sat down with Enterpriseleadership.org to discuss the creative ways he keeps IT flexible and supportive of the company's growth.

 

EL: Can you describe some of your key applications and  systems?

 

DR: The IT organization handles everything internally, except for running the mainframe -- IBM handles that. A large component of the operation runs on fully redundant AS400s. The storage area network received an award from Storage Networking World, the major enterprise storage tradeshow, and our data centers have a good base of core technologies.

 

We also have best-of-breed, core legacy applications that provide a degree of sophistication for transportation, distribution, planning, and business. We standardized by line of business and created the concept of a global infrastructure model. We commoditized the infrastructure layers and regionalized the application layers as appropriate. By migrating all of our domestic locations to AT&T, we can leverage their links, which has been very successful for us.

 

EL: How is IT keeping the company competitive?

 

DR: First, we created a support structure that integrated key personnel with the business. We worked with them on what their challenges, issues, and long-term business strategies were, and we sat in on their sessions on business strategy to find out where they're headed in the next few years. Next, we told them the areas where we could help them facilitate and achieve their goals.

 

We've already taken on several initiatives that support the sales and marketing penetration strategy that the business has for the next several years. These initiatives will help them deliver capabilities and functionalities needed to compete in a specific channel more effectively. Along a similar line, we want to get a greater return on investment for  our sales force. So, we have initiatives that will focus on sales force productivity. Similar initiatives for manufacturing will focus on working capital or cost of goods sold.

 

Once we have the strategic direction, then we can carry out day-to-day processes that help track whether we are investing the appropriate amount of time to get those things accomplished.

 

EL:  Are you doing balanced scorecard to gauge how well IT is aligned  with the business units?

 

DR: We have an IT dashboard that drives and supports the business, and we map our  strategic initiatives to support that within IT. Next, we preplan our strategic business projects tied to the overall business strategy. The dashboard shows how we are performing on a reliability and quality basis for daily work. It also tells us how we are performing relative to our strategic IT initiatives and our major projects that help to move the dial forward for the company. We share this information with both the business units and IT team to keep everyone focused on improvement.

 

EL: Do you have other best practices besides the  dashboard?

 

DR: We're carrying out a full-scale project management office. It will help to audit our large initiatives to make sure they stay on track. We're taking the applications development team through level one to level three CMMI training.

 

EL:  What is your governance model?

 

DR: For each major line of business, I've created a relationship manager who functions as a CIO for that business. These managers are responsible for ensuring that we're providing the services the business units should be receiving, and the projects are being  accomplished on time and within budget. On top of that, our executive steering committee, which consists of the chairman's direct reports, meets quarterly, and I facilitate this committee. We have monthly sessions by key line of businesses or process areas where we review priorities.

 

EL:  Have you had any significant reductions or productivity  improvements?

 

DR: We've made material improvements in productivity, quality, and overall reliability. Because we've become more cost effective, I've been able to operate more efficiently with the resources I’ve had since I took this position. In terms of manpower numbers, this is the leanest shop I've worked in. I spent 12 years with EDS and eight years in the apparel industry prior to coming here.

 

EL: What innovative technologies are you considering for the next  year?

 

DR: We're excited about what cellular carriers are trying to do with hot points, WIMAX, and 802.11, and how the PC and PDA companies are trying to take advantage of that. We see developments helping us in customer services, sales, and the support side relative to taking advantage of some of that.

 

We're also interested in business process modeling analysis and management and its relationship to the service-oriented architecture. It can help us migrate to a more agile architecture where we can adjust processes on the fly more quickly.

 

We're taken advantage of blade servers and plan to take advantage of grid  computing.

 

EL: What role does business intelligence play in your  organization?

 

DR: We've made investments in front-end sales analysis and reporting. In fact, it will also become a key component of our longer-term strategy as we become more global and enter more regions. It will enable us to tie all of these regions together in a quick, efficient manner, and to report our performance to the company and to the market.

 

--

 

Elizabeth M.  Ferrarini is a free-lance technology writer from Boston,  Massachusetts.

| More
414 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy
by Peter Armstrong

Part 1   |  Part 2

 

How Good is My Service?

Here is an interesting thing to try: Go the Web armed only with the name of your company. Now, login to your company's Web site and try and find out what your company actually does. Remember that you must not use any knowledge you already have; you must pretend to be an end user. Alternatively, ask your wife/mother/children to try this exercise, and watch what they do. You will be amazed at where they click on the screen, the paths they take, and the information they either find or fail to find.

 

I tried searching on my company's Web site a couple of years ago for a particular product. I searched by function, platform, database, and so on (I was looking for an online copy product), and found nothing. When I searched by product name (Extended Buffer Manager Snapshot Upgrade Facility), I found about 20 hits. How many customers are going to search on that name?

 

Who is using your IT systems? Why are they using them? What are you trying to sell them? Is it easy to contact you if they have problems? Is the data up-to-date? Are the systems available (and this includes performance)? What are the availability and performance requirements (some systems perform better than required, which is a waste of money)? Do you have Service Level Agreements (SLAs) in place, and are you measuring against them? Are you measuring from the end-user point of view, or from your own point of view?

 

I was visiting a major Australian university last year, and I was told that they were very happy that they had the local systems under control (which was good news as they are using my company's products). What they really wanted to know, however, was whether a potential student in South Africa was able to access their systems and apply for a place on next year's course, because this is what generated their revenue.

 

Service Measurement

Another area of concern is that of service measurement. The cornerstone of any managed services contract is the service-level agreement. This is meant to be the yardstick that measures the performance of the "service provider," but unless the agreement is written and reported with measurable and meaningful values, it can lead to very difficult situations.

 

The more vague the service-level agreement, the more chance of confusion on what should be, and has been, delivered as part of the contract. Service-level agreements need to be written with factual, measurable metrics included, and the service provider should regularly provide detailed reports based on these metrics.

 

The most common metrics tend to relate to issues such as call-response times and mean-time-to-repair faults. However, valuable as these are, they are measures after the fact. Never having to call in the first place because there are no problems is better than having a quick response rate to calls from irate users. Service-level agreements should be based on the availability and performance of the service -- not just its reaction to failure. In fact, SLAs should be based on what the business needs -- most of the time they are written from a purely technical point of view.

 

I was visiting a major customer last year, whose IT operations are outsourced to one of the major outsourcing companies. The contract is, of course, couched in terms of CPU used, number of housekeeping jobs run, number of tape mounts, and so on, and so on -- which was a totally and utterly incorrect approach, in my opinion. The bank wants a service -- how the outsourcer actually implements the service technically should be of no concern as long as it is safe, reliable, and conforms to the business SLAs. In this particular case, the bank wanted the outsourcer to install a product, which would save 20 percent CPU. The outsourcer, of course, refused, as they saw it as a means of losing money. If you stood back and looked at the bigger business picture, you'd realise that the outsourcer could provide a better service with less hardware expenditure (= no expensive upgrades, ability to handle more workload per customer, and more), and the bank would get a faster response time.

 

Reporting

Reporting is another critical area that can be overlooked. A good IT department will not only provide good service, but also prove it by providing meaningful reports. These reports should relate directly to the service being provided to the customer and should also show the value that the IT department is bringing to the equation. They should be couched in language that business people can understand -- Oracle availability is meaningless; ability to print invoices on time is significant.

 

Some More Examples

Here are a couple of examples of IT and business not coming together as well  as they should:

Example 1

I went visited a major European bank that had come to my company with a requirement to run their systems 24x7. As they were a leading-edge IT user (sysplex, sharing, dual sites, and more) we had to write some extensions to our software to cater to their environment, but it these all worked fine. I was invited in to meet the DP Manager, whom I have known for years.

 

"Do the products work?"
"Yes, no problems."

 

"Are you happy with our support and assistance?"
"Yes, brilliant."

 

"Do the products do what you require?"
"Absolutely."

 

"Are you going to sign the contract?"
"Not my decision."

 

It transpired that the salesperson had never spoken to the business manager, who had raised the 24x7 requirement in the first place and had never established what the business benefits were to the bank of a 24x7 service. I unpacked my steel-capped boots and kicked the salesperson from here to eternity. We then worked on meeting the business manager, whom we discovered had been tasked to make the bank one of the five leading banks in the world, and could not see how they could do that on an international scale without offering 24x7 services.

 

Example 2

I worked with a large European insurance company that had the requirement to extend its online day by three hours, and hence squeeze the overnight batch processes by three hours. Working with the technical staff, we determined that we could achieve this easily. I was taken in to meet the DBA manager and to explain the brilliant internals of our products and how clever we were at doing things online, which previously had to be done offline. I asked the salesperson if he knew why they needed they hours and he said he did not, so when I met the manager I asked two questions:

 

      1. Why do you need three hours?

        The DBA manager gave me six good business reasons.

      2. How much is it worth to your company?

        He had no idea, but asked if he could go and ask his boss. He came back 15 minutes later, saying that his boss did not know either, so they were going to run an internal task force and could I come back next week. One week later, we discover that the three hours are going to be worth large quantities of money to them and the IT project immediately got the blessing to proceed.

 

The Missing Pieces

Business Service vs. IT Process

BusSvcVsITProcess.gif

IT departments tend to think from the bottom up. In this diagram, they would be thinking about databases, networks, job schedules, and so on. The line of business manager, on the other hand, is thinking about whether the back-office functions are running, whether the customer-facing processes are operating efficiently, and what sort of service is being provided to the business partners.

 

A business service depends on a set of processes to ensure that it is executing and performing as expected. In not-yet-automated business services, the management is done primarily by business-side managers.; the IT organization exists to manage the infrastructure and software applications. In other words, some or all of the management of the business execution is transferred to the IT organization, and hence, businesses should understand that IT management is an integral success contributor.

 

Automated business services provide many benefits. However, they also bring with them considerable inherent risks. Computing infrastructures are extremely fragile and "dumb" by nature, and each different from the other. Due to the considerable inherent risks associated with IT-based business services, it is vitally important to the business that the environment in which the business service will execute is managed extremely well and cost effectively toward business needs and expectations. The most effective method to date to manage automated business processes is through a set of mature IT management disciplines like ITIL®.

 

IT Best Practice

No one runs technology for fun, so each component has to provide some degree of functionality to the business. Managing these components is just as critical as the components themselves, because a failure can affect the service that relies upon them. At a technical level the key issue is how the IT department actually proposes to manage the environment. The use of industry-leading solutions and best-practice methodologies should be common to all good "service providers," but they are surprisingly often absent.

 

Some IT departments see tools merely as a way of reducing their cost of operation by reducing the number of people required to manage the environment. However, the use of tools to manage technology can greatly increase the availability and performance of the infrastructure. By exploiting the functionality within the toolset and applying that functionality to best-practice standards such as ITIL, the business -- and ultimately the customer -- receives the benefits.

 

This means that not only must IT and business learn to talk to each other, but they also need new tools to make their life business-oriented. When a component fails or performs badly, you need to see the impact from a business point of view rather than a technology point of view. If you give an IT person 5 problems, they will typically work on them in a first-in-first-out order as they don't have any information to tell them not to. When you add in a business criticality view, the order of resolution of problems / performance tuning / infrastructure investment, and so on, becomes totally different and IT begins to build value for the company rather than act as a cost centre.

 

Through implementation of sensible IT processes, combined with business-related tools and methodologies, the advantage to the business is the true and correct exploitation of the IT investment. This is why the two parties need to learn to talk to one another.

 

--

 

Peter Armstrong joined IBM in 1976 and was the UK Country IMS specialist. He helped design parts of DBRC and wrote the Recovery/Restart procedures for IMS disk logging. He joined BMC Software in 1986; these days, he is a corporate strategist, responsible for the increasingly important domain of how business and information technology need to work together. Peter is also a prolific writer and has authored Database Recovery Control (DBRC) in Practice.

| More
226 Views 0 Comments 1 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

Bullish on Latin America

Posted by Tom Parish Jun 11, 2006

by Rod Amis

 

With the inauguration of Chile's first female President, Michelle Bachelet, on Saturday, 11 March, 2006, any business leader looking at Latin America over the past year sees a continent where change has been breath-taking and the prospects for future investment and development might appear murky, if not challenging. At the same time, in Peru, Bloomberg reported on 27 March, 2006, that Ollanta Humala, the Peruvian Nationalist Party candidate was leading in the polls prior to that nation's 9 April elections.

 

Does social change necessarily mean a change in economic policy? Where are the most promising sectors in which to seek business opportunities in Latin America and where are the roadblocks? Let's take a look at the picture on the ground.

 

"At the moment, every global investment firm that has launched an investment fund in euros and invested in Latin American stock markets is enjoying better results. In just one month, the HSBC GIF Brasil Equity fund rose 14 percent, the equivalent of a 40 percent return over three months. It is the best short-term fund. In the medium and long term, the results are much more spectacular. For example, the Merrill Lynch Latin America Equity fund (the most profitable three-year fund) has risen 241 percent since 2003. It is followed very closely by a similar product from JPMorgan, which has earned 229 percent. The 10 most profitable three-year funds on the stock market are investing in Latin America." from "Will 2006 Be a Happy Year for Latin America" Universia Knowledge@Wharton

 

When approaching business opportunities in Latin America, we need to take two  facts under consideration:

 

      1. New partnership configurations, including joint public-private ventures may be called for in certain countries, such as Venezuela and Bolivia, when dealing with energy industries like natural gas and crude oil.
      2. One size does not fit all. Latin America is a regional, not a single political, entity and every country's economic policies will be different despite the commonality of language.

 

In this article, we'll also explore the rise of populism in the political arena and how it addresses the impatience and dissatisfaction of people in the new democracies of the region, but does not change the need for minding the balance of payments equations. Thus, many signs -- such as those exhibited during new Bolivian president Evo Morales' tour of Europe -- point to a continuation of a healthy investment climate and sustained growth in Latin American markets.

 

Dr. Gerald McDermott of the Wharton School of Business, a recognized expert on emerging markets in Eastern Europe and Latin America, has tracked the development of the economic environment in these countries for decades. One of the things he sees in South America is a stabilization of the investment environment that has evolved since the missteps of the 1980s and 1990s.

 

"Look at what happened in Argentina," McDermott told Enterpriseleadership. "The problems of the 1980s -- low growth, volatile inflation -- was in part the confluence of several points of instability as well as missteps in economic policy. For instance, Argentina was grappling with democratization, subduing the military, rebuilding the social fabric after the infamous "dirty war," and resolving the massive debt crisis that virtually locked the country out of international capital market until 1991.

 

"While the "lost decade" damaged the role of the state and the left in managing the economy, the missteps during the Menem years in budget and regulatory management as well as the financial collapse in 2001 and 2002 damaged the legitimacy of market-based reforms.

 

"There are not a lot of roadblocks to foreign investment today because the major actors are institutionally constrained. Chile was first [in opening the economy to investment], but then Lula in Brazil added a little more nuance and became the hallmark for economic growth on the continent."

 

A Regional Prospectus

Let's begin by looking at the investment opportunities and prospects on a  country-by-country basis.

 

Brazil is Latin America's largest economy. By some estimates, 40 percent of all economic activity in the region originates in that country. While President Luiz Inacio Lula da Silva came to power as a "man of the people," his economic policies have been solidly centrist, resulting in an annual growth rate of 4 percent -- 5 percent. Though Lula's administration is now plagued by a corruption scandal that will likely lead to the resignation of his Minister of Finance, Brazil's anti-inflation economic policies will likely remain unchanged.

 

Brazil, in fact, represents an interesting case study on how pragmatic reformist social policies are recognized to be only achievable by maintaining a strong economy. Other nations in Latin America are thus watching Brazil closely and taking guidance from its example.

 

As Gerald McDermott pointed out during his conversation with Enterpriseleadership, the most significant achievement of Lula da Silva's rise to political power was that he single-handedly moved to reform the labor left. "He moved it [the labor left] from being a nationalist institutional structure, much like Peronism, into being a much more pragmatic system for economic growth," McDermott told Enterpriseleadership. "Lula represents a modern alternative for the left not only in Brazil but in other countries as well. That is, leftist movements in other countries, such as in Peru, Mexico, Bolivia, and Argentina, have Brazil and Chile as potential models to follow, and not simply those espoused by [Venezuela's] Chavez."

 

One indicator of the potency of Brazil's economic policies is the real estate boom throughout the country that began in late 2004. By 2005, three sectors in particular -- middle-income housing, tourism, and "build-to-suit" industrial warehousing were beginning to show impressive growth and return on investment. WalMart moved to Brazil during 2004 while a boom in shopping center construction was taking place in Brazil's largest cities. At about the same time, the agricultural belt of the nation was experiencing local investment due to the rise in the price of soybeans. Major American, French and Spanish hospitality chains were taking advantage of the foreign investment climate to open new hotels.

 

Chile's economy has been rated one of the most stable in Latin America by analysts for years. The climate for foreign investment is positive and, while widely known for its exports of wine, salmon, and copper, one of the most exciting investment sectors in the country is in information technology training and business-to-business transactional guidance.

 

Though Chile has the most advanced telecommunications infrastructure in Latin America, due to significant investment in the 1990s, few of its businesses have yet to move their activities to the Internet. Major businesses in neighboring Brazil and Argentina use IT for an array of their business and sales processes, but those in Chile still did not in 2004. A report from the Center for Study of the Digital Economy of the Santiago Chamber of Commerce (CCS) in 2004 stated that although 69 percent of Chilean companies were connected to the Internet, digital technology covered mainly just the fundamentals. Only 25 percent of Chilean companies had their own Web site, only 11 percent used the Web as a platform for sales, and only 16 percent used it to buy online and to connect with suppliers, the report concluded. This is despite the fact that, at the time, companies could use the Internet to pay national insurance contributions to employees and apply for bank loans.

 

Part of the resistance to adopting IT in Chile was, in fact, cultural, many believed, but part of it could be attributed to lack of local investment. In response, the Chilean government began a new initiative, the Digital Agenda. The Digital Agenda's stated goal is to "… convert Chile to a digital country by 2010." As part of the agenda, business incubators have been established at University of Chile and at the University of Adolfo Ibaiaez. The Association of Chilean Information Technology Companies has established the goal of raising the information technology sector to 3.8 percent of GDP from its current 1.2 percent of GDP.

 

Jay Bryson, an economist with Charlotte, North Carolina's, Wachovia Bank, noted at the beginning of this year that Chile had taken several major steps in the 1990s to open its economy. The country, he said, " … allowed imports to come in and exports to flow out. They also have had a fairly stable macroeconomic policy over the last few years, a relatively independent central bank and they haven't jacked up taxes. That's given foreign investors confidence, so we have seen investors increase [their holdings in Chile]."

 

Bolivia is Latin America's poorest nation. Nonetheless it has massive reserves of natural gas, which -- with the help of Spain's Repsol, Brazil's Petrobras, France's Total, Anglo-Dutch Shell, and British Petroleum -- it hopes to recover and export to its neighbors, Brazil, Argentina, and Chile. The Spanish financial institution La Caixa plans to invest $800 million to this project over the next five years. In addition, Bolivia is believed to have 70 percent of the world's iron and magnesium reserves. So extractive mining and traditional agricultural will remain the basis of its future economic growth.

 

Newly-elected President Evo Morales has been more moderate in his meetings with foreign investors, as noted above, than his rhetoric at home would have led us to believe. In that European tour, he told investors in France, Belgium (at the EU headquarters,) Spain, and Holland that "…any company that cooperates and pays its taxes can recover its investments and have the right to its profits, but under the principle of balance because the State and the people must also benefit."

 

It's very likely that Mr. Morales' government will meet these goals by using what some analysts call the "Venezuela Solution, " creating companies of mixed ownership from both government and private enterprise. Such creative solutions allow pragmatic government leaders to both appease their volatile constituencies while allowing profit taking to foreign investors.

 

Venezuela, despite the rhetoric of President Hugo Chavez and his penchant for grabbing headlines, is a major source of oil for the United States and has an ownership interest in Citgo. The relationship between foreign investment -- and particularly investment from the United States -- and national stability is unlikely to change, no matter the public pronouncements of the Chavez government or the U.S. State Department.

 

The pragmatic fact is that Venezuela means to remain a player in the global marketplace and can only do so because of its oil reserves. At the same time, the political stance of the government is to address the social agenda demanded by its citizens.

 

As the suggested in the overview of Bolivia, Venezuela is providing creative solutions, much as has Brazil, to attract foreign investment in state/private partnerships while also seemingly dealing with populist concerns.

 

The recent initiative on the part of the government to offer long-term oil contracts at below OPEC rates is also a positive sign of stabilization of the investment environment.

 

Argentina, notwithstanding the upheaval of the 1990s, has instituted economic safeguards and encouraged investment during this decade. McDermott, who has been intimately involved in development in this South American country, notes that the development of infrastructure, after the stresses of the large utilities companies were overcome, is now akin to that of Chile or Brazil.

 

Now that those stresses have been relieved by a change in governmental administration, the situation in Buenos Aires is promising.

 

The Spanish Tigers

One can look to success stories for guidance. For example, the strong influence of Spanish multinationals, the new tigers of Europe, who have established relationships in a diversity of industries from telecommunications to textiles in the region since the 1990s provide insight to the fertility of this emerging market.

 

A February 2006 feature in the Economist states: "…since the return of democracy, the Spanish have rediscovered the outside world, none more so than the country's businessmen, whose exuberant expansionism has led to them being dubbed the "new conquistadores.'" Among the areas in which Spanish companies have distinguished themselves are Telefónica, the world's fourth-largest telecommunications provider and the largest in Latin America; Repsol YPF, the ninth-largest oil company, and Iberdrola, an electrical utility that is the world's largest operator of wind generators.

 

The Spanish corporations were nimble and aggressive and, with the advantage of common language and heritage, quickly pounced in Latin America. Where a decade and a half ago, a Latin America concern might have gone to Washington, New York, or London seeking capital, today they as readily talk with financiers in Madrid. In fact, Spanish banks, like their counterparts in other countries, are now acquiring American banks. That they have bankrolled some of the major projects in Latin America over the last decade should come as no surprise.

 

Capitalizing on Emerging Markets

Whether one looks at the IT infrastructure and training opportunities in Chile or to the natural gas and mining needs of Bolivia, one thing is clear: the emerging democracies of Latin America present a wide array of investment and business development options.

 

While the political winds that have swept through the South American continent could, at first glance, seem confusing or unsettling, the astute observer will note that following pragmatic economic policies can only fulfill the social and political objectives of the new governments. Foreign investment and business growth are the underpinning of policies that will meet the expectations of their constituencies and be the benchmark for the successes of their new governments.

 

By following the examples of the Spanish tigers, the French energy concerns, and other businesses that have already established relationships on the continent, and by respecting the cultural nuances of South America, the return on investment to be accrued in this emerging market is promising.

 

As Dr. McDermott emphasizes, the key word for business leaders looking to the  emerging markets of Latin America is nuance. Each government is attempting to be economically pragmatic while dealing with an inheritance of unaddressed political demands as they move from military dominance to representative democracy. The climate for investment, in part because of populist demands, has never been stronger.

 

--

 

Rod Amis is a freelance technology writer based in North Carolina. He has written for various publications on- and offline, including IT Manager's Journal, NewsForge, Silicon.com and Access Internet Magazine. He is also the author of two books and was a newspaper journalist before going completely digital.

| More
210 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

by Deb Radcliff

 

Part  1  |  Part  2  |  Part 3

 

A "Getting-started" Policy

The first two parts of this article have shown the depth and complexity of security vulnerabilities and smart phones. Part three of this series presents the policy side of how to prevent attacks, and provides an overview of the history of mobile malware.

 

It'd be nice if organizations today could have comprehensive smart phone use policies in place and the power to enforce them, says Nick Ianelli, mobile security analyst for U.S. CERT.

 

"On company-issued phones, it'd be great to say, "No gaming," and "No software installs without the authorization of IT, and turn off Bluetooth except when synching,"" he explains.

 

It'd also be good to remotely check patch level and security software running on the device at the time of VPN connection or PC synchronization. But, we're at least a year away from standards-based vendor products delivering this level of automation. So, in the meantime, start small, say experts. They offer the following advice1:

 

      • Take a survey. Find out who's using smart phones for what type of business. Then, make a risk assessment of those applications and the data stored in them.
      • Start an awareness campaign. Educate your power users about the value of their business data, and what would happen if it were stolen or rendered inaccessible by a mobile virus. Educate all users about the dangers posed to their personal information and how they shouldn't believe what they see on their devices, just like on their PCs.
      • Don't just tell them. Show them. Make them hands-on aware of the features in their phones that are risky, and show them how to use them securely.
      • If you must issue policy around business phone usage, stick only to your power users and what you can control with today's technology. For example, all phones come with remote locking, meaning they can be shut down if they're reported lost or stolen. So that policy should be implemented on any phone containing valuable business, or regulated data.
      • Turn on encryption. Although not built to Trusted Platform specifications at this time, many mobile phone vendors have some type of built-in encryption. Third-party applications are also available. Look for easiest interface, as users will have to interact with their encryption programs.
      • Control network connections through VPN access.

 

Resources

The following comprises a brief history of mobile malware2:

 

      • Spring 2004: Mosquitos, the game infected by a Trojan, sends messages to expensive toll numbers, causing considerable economic loss to its unwitting victims.
      • June 15, 2004: Cabir.A, first Symbian worm to replicate through an active  Bluetooth connection, emerges.
      • June 16, 2004: Only one day later, Cabir.B makes an appearance, and will continue its spread mainly in China, India, Turkey, Finland, and the Philippines. To this day, this worm continues to hitchhike around the world.
      • July 2004: Duts, nicknamed the "polite virus," hits Pocket PCs for the first time and spreads to all .exe files in the directory through infected programs exchanges. When a program hit by Duts is activated, a message appears asking the user permission to proceed: "Dear User, am I allowed to spread?"
      • Aug. 2004: Brador appear. This back door creates a copy of itself in the start file on handheld devices and informs the attacker the minute the device is online. The hacker can then connect to the palmtop through the TCP door and covertly control the device.
      • Nov. 19, 2004: Skulls.A attacks Symbian-based smartphones, appearing on Web sites that allow users to download shareware applications for the Symbian operating system. If erroneously installed, the Trojan blocks the functioning of applications, allowing the user only to make or receive phone calls.
      • Nov. 29, 2004: Skulls.B emerges. As with previous Trojans, this is spread through a file called Icons.SIS, blocking the functioning of the cellular device's applications and allowing the user only to make and receive phone calls, deleting all other functions. Skulls also carries the worm Cabir.B.
      • Dec. 9, 2004: Cabir.C, D and E appear.
      • Dec. 21, 2004: Skulls.C, Cabir.F and Cabir.G appear.
      • Dec. 22, 2004: MGDropper spreads during game installs disguised as the cracked copy of the popular cellular phone game Metal Gear Solid. When launched, MGDropper installs versions of Skulls and Cabir and tries to undermine the security products installed on the phone.
      • Dec. 26, 2004: Cabir.H and Cabir.I make an appearance. Both target cellular  phones with a Symbian 60 Series operating system.
      • Jan. 11, 2005: Lasco, targeting cellular phones with a Symbian operating system and an active Bluetooth connection, combines viruses and worms and replicates the behavior of the notorious Cabir, searching for other active Bluetooth devices so it can replicate and look for .sis files to infect.
      • Feb. 1, 2005: The Locknut.A trojan (also nicknamed Gavino.A and B by some anti-virus companies) aims at phones with a Symbian 7.0 operating system. It's a Symbian SIS Trojan file that substitutes a binary file, blocking the phone and preventing any application from opening. Once hit by Locknut.A, the phone becomes unusable, even for phone calls.
      • March 3, 2005: Commwarrior.A starts creating unwanted billing for infected Series 60 users. This virus, however, adds a new layer of sophisticated intelligence, using Bluetooth during daytime for spreading and sending MMS messages at night. To become infected, the user has to accept the installation dialogue; once done, detection is difficult. The global spread of Commwarrior.A has been rapid because of the trust users have with the sender.
      • March 18, 2005: Locknut.B installs as a phony patch for Series 60 phones, rendering the operating system unusable by preventing any application to launch. It also contains Cabir V, which spreads through Bluetooth.
      • April 4, 2005: Fontal.A, a SIS file Trojan, installs a corrupted font file into an infected device, causing it to fail at the next reboot. Fontal.A also damages the application manager so that it cannot be uninstalled, and no new applications can be installed before the phone is disinfected.
      • May 9, 2005: Skulls.K replaces the system applications with non-functional versions, drops SymbOS/Cabir.M worm in to the phone, and disables third-party applications that could be used to disinfect it.
      • August 26, 2005: Doomboot.B pretends to be a utility that can be used to reboot a phone, but when a user makes use of this application, Doomboot prevents the phone from booting again.
      • Sept. 20, 2005: Cardtrap.A, a malicious SIS file Trojan, tries to disable a large number of system, and third-party applications and installs Windows malware on the phone memory card.
      • Oct. 30, 2005: Commwarrior.C installs when a user replies to a new SMS or MMS message by opening a Web page using the phone's browser, then tries to change the logo to "Infected by Conmwarrior" (observed on Nokia 660 phones).

 

Footnotes

1Sources: CERT, Kaspersky Labs, Symantec, Yankee Group

2Information provided by F-Secure

 

--

 

Deb Radcliff is an award-winning freelance writer, educator and speaker based in Northern California. She's been covering online crime and security ever since working as researcher on a book about infamous hacker, Kevin Mitnick back in 1995.

| More
440 Views 0 Comments 2 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy

by Elizabeth M. Ferrarini

 

Can an IT infrastructure help to differentiate an organization strategically from its competitors? This question, first posed in the Harvard Business  Review article (May 2003), "IT Doesn't Matter," by Nicholas G. Carr, sent IT executives everywhere whirling around on their swivel chairs. It also caused academics to do some hard thinking, and computer vendors to rally in front of their customers. But Carr, the former editor of The Harvard Business  Review, didn't stop there.

 

His 2004 book, Does IT Matter? -- Information Technology and Corrosion of  Competitive Advantage, expands the initial premise in Carr's article by asking corporations to think about IT and its role in business strategy. The book also looks at some significant implications of the emergence of the new, shared technological infrastructure for all companies.("Sharing" means that all business units use the same IT infrastructure resources, such as storage.)

 

In an interview with Nicholas G. Carr, Enterpriseleadership.org's Elizabeth  Ferrarini asked Carr to explain himself.

 

EL: Commodity public broadband services are great for consumers, but private companies will come under the gun for more IT compliance. To this end, will IT become more strategic to the organization?

 

NC: IT will start to talk more to the business units. It's a trend we're already seeing, with IT staff being required to think in more business terms than in purely technological ones. As more of the basic components of IT become commodity items and/or supplied by utility services, then it's less important for individual companies to maintain all of the specialized technical skills that they used to. Thus, IT becomes more of a translation function in bringing the right technologies to the right business processes.

 

EL: Is the IT role going to disappear?

 

NC: Most large companies will continue to have an IT role, but it's going to change and be integrated more into the mainstream of the business. It will make sense to treat the IT function the same way companies treat other departments, such as marketing and human resources, and move toward a rotational model. This model will change how IT staff is identified -- from technicians, separate from the business, to employees who serve a specific business role.

 

EL: Are you seeing kind of a two-tier approach to IT, in which the infrastructure is under a general manager, and a business IT unit is under a CIO reporting to the CEO?

 

NC: I haven't seen this type of model, but it could well be a future trend. Today, a lot of CIOs spend their time worrying about how to manage the infrastructure. They would be better off looking at how IT can help overall business operations.

 

EL: You have been doing a lot of speaking at conferences. What's the number one topic of debate you get into with IT professionals?

 

NC: The biggest issue concerns the question of innovation and whether it still pays for companies to be IT innovators. Most companies would be better off looking at IT as a cost of doing business by getting the IT capabilities they need as efficiently, inexpensively, and reliably as possible. CIOs in many companies continue to think there is a role for IT innovation, which will give the company a competitive advantage. Maybe 70, to 80 percent of their money and attention goes to basic infrastructure.

 

EL: Is what you just said true for IT professionals who are in an industry in which IT drives revenues, making innovation important to the company's success?

 

NC: Some of it is that. It's also a sense that there are many companies that may have very specialized opportunities to use IT in a very customized way that fits their processes. Most IT leaders, at this point, see a lot of the basic systems, even complex systems such as ERP, as being more and more standard, and less strategic to the business. From an innovation perspective, CIOs are looking at more highly specialized applications that fit their particular business or industry to gain an advantage from IT.

 

EL: Are there any companies you're really impressed with as far as IT innovation besides the Amazon.coms and GOOGLEs of the world?

 

NC: I'm impressed with how some big companies now are moving aggressively to adopting a utility model. Take Qantas Airlines, for example. It's closing down its data centers and moving towards hosted applications rather than maintaining its own. This strategy is driving down the cost of computing as a result, and reducing the headaches involved with maintaining all of their assets. What excites me are the companies that are really trying to capitalize on the commodity trend. Take the 70 or 80 percent of their IT activities and really streamline, consolidate, standardize them, and in many cases, offload them to utility suppliers.

 

EL: So, you think a lot more of IT is going to be  outsourced?

 

NC: I wouldn't say outsourced in a way we now define it, which is a piecemeal process using different vendors to do specific things, and then relying on the internal IT staff to integrate everything. We're going to move from today's view of outsourcing to a utility model, which enables you to buy the capabilities you need for a monthly fee from outside utilities. More of the integration of systems will be done by these utilities.

 

EL: Technologies such as grid computing are supposed to enable companies to turn their infrastructures into utilities. Are you saying companies would prefer to buy utility services rather than build them themselves?

 

NC: Grid computing is still in its infancy. Wachovia Bank is a good example of an organization that's doing grid computing internally. As this technology and others, such as virtualization, continue to improve, most companies will look to outsiders to supply these services rather than setting up their own grids.

 

EL: During the dot.com era, we saw many startups offering a variety of utility services, from storage to maintaining the entire IT infrastructure. Given that many of these companies failed, such as StorageNetworks, can you put credence in the utility model?

 

NC: If you look at the dot.com era, many new ideas were too early. And, the entire application service provider model of hosted software and serviced didn't take off. However, technologies continue to advance. We are at a point where some of the things that didn't work five years ago can work  today.

 

EL: Are you working on another book?

 

NC: I'm just starting to work on one. I plan to write about the future of the computer, looking at how computing will be done in businesses and also the way it will be done in the home. We're starting to move beyond the personal computer age to a time when computing will be distributed in and tapped into in many different ways. For example, broadband via your personal computer is becoming less expensive than wireline telephone. Even digital TV is starting to blur the line between basic consumer electronics and computing.

 

EL: The great IT jobs that were available 10 years ago may not be there in a few years. What advice would you give to IT professionals today or those coming up through the ranks?

 

NC: Here's one way to think about it. Traditionally there have been two types of IT professionals -- those who specialize in a particular technology, such as an operating system or a hardware platform, and those who are generalists. The first group will continue to shift from the user side to the supplier side. The vendor side increasingly needs these specialized skills. This generalist model of IT professionals plays a role between the technology and the business itself. There's also going to be demand for skilled, talented people who can provide this kind of bridge between IT and its application.

 

--

 

Elizabeth M. Ferrarini is a  freelance writer from Boston, Massachusetts.

| More
274 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy
by Jonathan Markworth

 

From Viewpoint:  Focus on CMDB, January 2006.

 

A federated CMDB provides a single source of critical information that enables IT to better support business goals. The right data in the right format, reconciliation capabilities, and processes to ensure quality data are the keys to making the CMDB a successful reality in your IT organization.

 

There’s a lot of excitement today about the potential of a configuration management database (CMDB) -- and, in particular, a federated CMDB -- to help organizations drive IT efficiency and truly benefit from their investment in IT assets. But there’s also a lot of confusion, misinformation, and concern about what a CMDB is and how much business value it can actually deliver. Some common questions include:

 

      • What is a CMDB, anyway? And why is federation so important? Is the CMDB a myth, reality, requirement, or just another sales and marketing ploy?
      • I already have dozens of data repositories, management consoles, and inventory databases spread throughout my organization. Can I control all the systems of record I’ll have to deal with in a federated model? Can I implement a federated enterprise CMDB without bringing my organization to its knees?
      • My people seem to be drowning in information, but they’re unable to find out what they really need to know. How will adding another tool to the mix help my staff manage the business more proactively?
      • Implementing a CMDB and maintaining configuration item (CI), attribute, and relationship data can’t be easy. Will I end up with a CMDB that propels the business forward or one that just consumes already scarce resources without a return on investment? Will the CMDB become shelfware or a powerful tool for my business?
      • Is this just going to be one more thing that my overworked staff has to deal  with?

 

What is a CMDB?

Several definitions are being offered, but it is generally accepted that the CMDB is a data repository relating to the IT infrastructure, and contains information that identifies each CI, describes attributes about each CI, and denotes the relationship between CIs. Your organization may be planning to simply deploy a CMDB as a centrally available repository of auto discovery information collected by electronic inventory tools. However, the CMDB really should be designed as a solution that enables IT to support critical business functions. As simple as this sounds, the design and implementation of the CMDB should be tailored to the goals of your organization.

 

In the context of critical business functions that are enabled by various IT services, CI information stored in an isolated data repository is virtually useless. Centralizing the repository is a good first step in deploying a CMDB. However, CMDB deployments must also have relationship information that links stored data back to the context of the business. Only then will the CMDB have the maximum effect on any anticipated process and performance improvements. Relationships are required to fully realize the benefits of a CMDB across your IT organization. It’s the relationships between CIs in the CMDB that help unravel the complex interdependencies in the IT infrastructure and link them to business services. And it’s the relationships that unite management applications and processes in a cohesive and efficient manner to drive higher levels of quality, predictability, and service impact assessment across your enterprise.

 

5 KEY BENEFITS OF A FEDERATED CMDB

  1. Achievement of a centralized view without the cost of moving all data to a  single, monolithic data repository.
  2. Ability to leverage existing investments that currently isolate critical  information.
  3. Visibility into the complex interdependencies throughout the IT  infrastructure.
  4. Greater efficiency, leading to higher productivity and lower IT costs.
  5. Enhanced ability to comply with government regulations that impact  IT.

Federated CMDB -- Myth, Reality, Requirement, or Ploy

Wouldn’t it be great to have a single, all-knowing, all-powerful, and self-maintaining tool to manage every facet of information about the IT infrastructure? Wouldn’t it be great to start over fresh -- to replace your legacy enterprise management infrastructure with tools that did everything within a fully integrated platform? The reality is that most organizations have inherited (or deployed) dozens of applications, tools, utilities, data stores, hardware platforms, and management frameworks that perform one or more of the service management functions. Each of these has a data repository that provides information to support some critical function within your current environment. In the context of the CMDB, the collection of the data repositories related to these tools contains most of the critical CI attributes that can be used to build relationship data. The key question is then how do you leverage the investments you’ve already made to build an integrated data repository such as a CMDB?

 

One method is to export the CI identification, attribute, and relationship data from each of these data sources and combine it into a single database. Over an extended period of time, this method can be very difficult to maintain and only becomes more complicated as the number of data sources grows.

 

An alternative approach is to build a CMDB that consolidates identification, attribute, and relationship data, making it readily available to all the IT processes that need it and without requiring all of the data to be copied centrally. In this federated model, the CMDB holds configuration items and a critical subset of data, but then links to other sources of related data such as service desk tickets, service level agreement definitions, or even management consoles. Deployed correctly, the federated model can facilitate the introduction of an enterprise CMDB that can span the whole IT organization, allow for a phased transition plan from legacy systems -- if that is even necessary -- and preserve the ability of the IT organization to continue day-to-day operations with fewer interruptions.

 

Too Many Screens, Too Much Data, Too Generic a Format

The volume and scope of the information stored in a CMDB can become overwhelming if not carefully managed. Providing the right information, at the right time, to the right people, and in a format that encourages the correct human or technical response is critical. Think of the user interface of the CMDB in terms of a modern fighter plane. Many years go into modeling the interaction between the pilot and the cockpit displays so that in a high-stress situation the pilot can find exactly the information he or she needs. When a virus attack hits or a major component fails, processing information from the CMDB, including the extended CMDB data, isn’t much different.

 

The technicians responding to incidents or implementing changes are the pilots of your IT environment. Give them too many screens or too much data in too generic a format and their decision-making ability and productivity will decline, and the probability of making a mistake will increase. The CMDB is no longer useful for them. The fear of crashing and burning will keep them using their old, familiar spreadsheets and databases, no matter how complete and accurate your CMDB is advertised to be. The CMDB must support views in which information is efficiently tailored for its intended use.

 

The Absolute Importance of Rules-based Reconciliation

The quality of data will vary from one source to another, and sources may have conflicting or overlapping data that use different labels for the same data. Resolving the conflicts and reconciling the data is one of the most important and most challenging aspects of maintaining the quality of a federated CMDB. In many cases, the volume of data and the number of sources make manual reconciliation impossible. So a robust, rules-based reconciliation process is a must. This is an extremely important requirement. Deploying a CMDB without an effective and efficient reconciliation engine places the entire program at risk.

 

Process Is Key to Maintaining Data Quality

When you’re using a CMDB to better support critical business functions based on configuration data, the quality of that data is crucial. Consequently, you have to define ways to measure quality. You must also consider data and data management process quality over time. An effective tool that can be used is the Roll Throughput Yield formula:

 

Bad data * Bad data * Perfect data = Less than perfect data

 

It doesn’t matter that the last step in a process produces perfect data if the steps feeding into it are of poor quality. It is critical that you are resolute and aggressive in measuring and continuously improving the processes that produce and maintain data, so that you can ensure the quality of your data. You must continue to improve quality by looking at every process to identify and eliminate redundant or error-producing steps. Lack of a structured process improvement methodology is most definitely the number one cause of poor CMDB quality that eventually results in implementation failure. Perception truly is reality in this case. The audience that receives information from your CMDB probably won’t care too much about why the data looks wrong -- just that it’s wrong.

 

The Future -- Binding Disparate Processes Together

Implementing a CMDB is complex, but the benefits are significant. A federated CMDB built on an adaptable technology enables you to start binding disparate IT systems, data sources, and processes into a cohesive environment that facilitates business goals. Having a single source of critical information accelerates the speed at which you can execute, because it provides every person in the IT organization with the information they need to work efficiently and effectively -- from the service desk agent answering the phone or the technician refreshing a router, to the mid-level manager working on next year’s budget or the CIO developing long-term IT strategies.

 

--

 

Jonathan Markworth is a managing consultant with CompuCom  Systems, Inc. (www.CompuCom.com), headquartered in Dallas, Texas. Jonathan has successfully performed a variety of functions in the IT industry during the last 20 years. He is certified in ITIL and Six Sigma, and he is a certified Project Management Professional (PMP). As part of CompuCom’s Integrated Infrastructure Management practice, Jonathan and the CompuCom Center of Excellence team are responsible for deploying effective solutions for change, configuration, release, and asset management.

| More
192 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy
| More
252 Views 0 Comments 0 References Permalink Tags: article, best_practices, compliance, governance, innovation, it_management, itil, open_source, security, strategy
1 ... 9 10 11 12 13 Previous Next

Actions