Académique Documents
Professionnel Documents
Culture Documents
IT Strategy | 2014
to establish a scalable and cost-effective infrastructure that meets not just the
current needs but also the future needs of Fortis. Also, we as a company, were
about to take up a whole host of new initiatives, which meant that the load on IT
would go up further. Increasing overhead was another problem we faced. We had to
be on our toes just to keep the lights on and thats not the situation I wanted my
team to be in, says Sood.
Sood saw no sense in throwing more people and money at the problem. He instead
decided to start with a clean slate. We were open to all types of options---public
cloud, private cloud, hosting or on-premise, says Sood. With news of Sood scouting
for cloud vendors, he quickly became the most popular CIO in town. He was
approached by 19 vendors in the coming days, who opened out their long list of
specs and benefits on the table. Not the one to get misled easily, Sood prepared a
list of business priorities that needed to be met. Business was agnostic to the model
of the cloud IT would use, says Sood. The business wanted performance,
availability, and security. From the IT point of view, we needed scalability, flexibility,
and lower TCO and the public cloud met all these requirements, he says.
But one question lingered on: Who in their right minds would move
completely to the public cloud? This was the same question that was bothering
Soods team members. Tech professionals typically have a hardware-centric
mindset. They dont understand why you are telling them to stop worrying about
things like adding more servers or more memory. People are used to seeing
servers and having the latest and greatest tech and the best specs. It was this belief
that needed to change, he says. Sood badly wanted the teams support as they
were the ones who were eventually going to execute the project. He worked with
them closely and kept them motivated. Once he won that support, Soods
confidence doubled. Along with the hardware infrastructure, Sood and team moved
the bulk of the core applications to the cloud. Fortunately, for Sood, most of the
applications used by the company were already built for a virtual environment. That
made the migration easier. But it certainly was not trouble-free. The support from
OEMs and ISVs was a challenge. But the results were worth all the trouble, says
Sood. But ask him about how happy the end users are, Sood quickly turns into a
philosopher. User expectation is a moving target. Their benchmarks keep moving
Page 2
IT Strategy | 2014
up, he says. Today, users dont have to worry about the size of attachments while
sending an e-mail or the delay in opening an app during busy hours. But nobody
notices when you turn on the switch and the room is lit up. But people do get
disappointed when it does not happen, he says. But for the IT team, the move to
the public cloud was worth all the debate and effort. Sood says his team does not
really spend much time on mundane tasks like capacity planning and infrastructure
monitoring anymore. They are able to focus on factors that drive business and
growth. The time spent on keeping the lights on reduced drastically. The economic
benefits of the public cloud were significant. With the savings achieved, IT could
take up other new projects that were crying for attention--without increasing
budget. Sood is able to allocate significant portion of his IT budget to newer and
innovative projects now. A team that once looked at the public cloud with disbelief
now is fully is confident in the fact that there was no other way to do it.
IT Strategy | 2014
standardization framework. This framework included even the most basic yet often
neglected pieces of data security protocols like how paper used during work hours
should never be left unattended.
Both Pawar and Puliakottu spent the first three months for the initial
preparations and creating a standard ISO 27001 framework. This included external
audits, risk assessment, profiling, and closing gaps in processes. But the time of
implementation came along with the need to make some strategic calls. With four
plant locations and offices scattered across India, Puliakottu had to figure out a way
to conduct security training and implement policies at all locations. The real
challenge was completing the entire process in as little time as possible. It took us
totally 15 months to go live at all locations. Individually, each plant would have
taken about eight months instead of 12, but the collective time frame would have
been larger as well, says Puliakottu. Another challenge was to get employees
enthused and serious about security. We realized that information security in itself
is a boring topic and people might not be enthusiastic to attend training sessions,
says Pawar. However, the duo had other plans. Puliakottu roped in the HR team and
initiated a fresh round of training in various enterprise applications for employees.
The security guidelines were plugged into these training sessions as part of the
larger scheme of things. Just the kind of sugar-coated pill the employees needed.
The impact of the newly acquired certification on Sterlites image wasnt hard
to see. Notably, the company finalized a deal with a UAE-based customer within just
a few days of acquiring the certification. Earlier, the client would come with a
checklist and conduct an audit before signing a deal with us. Now, almost 90
percent of the general questions on most checklists are automatically answered
because we adhere to ISO 27001, says Puliakottu. He expects that as a result of
this, Sterlite will be able to generate about Rs. 100 crore more than what it would
have earlier made over a stipulated period of time. Having assured quality and
security for its customers, Sterlite Technologies can now expect to connect more
countries.
IT Strategy | 2014
Page 5
IT Strategy | 2014
1. Executive Summary
1.x [summary/synthesis of the strategic plan including vision, mission, goals,
drivers, key programs and initiatives etc.]
2. Current Position:
2.x [a snap shot of the current information technology environment]
3. IT Strategy
3.x [Strategic goals, objectives & planning]
4. Governance:
4.x [details the IT Governance structure and links it to the strategic plan]
5. Alignment:
5.x [details current and proposed programs and initiatives in support of the
proposed strategy]
Page 6