Skip to main content

Next Generation IT Service Model Shift

We are witnessing a major shift in the Enterprise App Paradigm. This is going to dictate how IT service providers are design / refine their offering. Gone are the days when IT Service are pure resource body shops, gone are the days when IT services are big ERP resellers, gone are the days when IT seller are hear and build (bespoke) application developers. Now, gone are the days when IT seller are service integrators. Today customer are looking at IT services provides to provide more than just value driven services. Customer are looking for true innovation delivery. For this to happen, IT service providers need to shift their focus and re-emphasize on customer centric (customized) innovation delivery in their offering messaging.

This is not a simple thing that is said and done. For an IT service company to competitive, they need to reinvent themselves and overhaul their operational model. The current model service delivery to me rebuilt on an agile factory based models where in standard service catalogs needs to be replaced with generic service components which can be assembled to suite the needs of different customers.

Here are some of the thoughts around it.

 

Tone down

Emphasize

Talking about "standard" offerings

Generic solution components from which customer centric solutions can be built (at easy with better Time To Market)

Promoting sales "catalogs" and "catalog selling"

Engineering component repositories and agile solution manufacturing (following a factory based approach)

Advocating "off the shelf" answers to client problems

Imagining and developing appropriate answers to client problems and challenges in their context, not the IT service provider

80% standard and 20% customization

Ability to integrate, adapt and innovate using components to create client-specific value. (Innovative models in collaboration with partner and other clients would be the key)

Matching exercises between client requirements to catalog line items

Listening and interpretation of client requirements, population of an architecture for the client need and solution with selected generic components

Relying on partners to provide an architecture

Developing standard architecture patterns around service offering which can help in assembling components quickly (at easy)

Standardizing the offer in the hope of selling it

Standardizing delivery approach to realizing any needed solution - standard method, not standard outcome

Limiting the range of offerings to clients

Be willing to take on global, industry and client's most pressing, complex, challenging and unique “first of a kind” work

Commoditization via supply of standard utility

Service innovations and supply of custom amenity

Labels:

Comments

Post a Comment

Popular posts from this blog

Just Buzz... Where is AI?

Speaking to Recode’s Kara Swisher and MSNBC’s Ari Melber, Pichai said AI is “one of the most important things that humanity is working on. It’s more profound than, I don’t know, electricity or fire,” adding that people learned to harness fire for the benefits of humanity, but also needed to overcome its downsides, too. Pichai also said that AI could be used to help solve climate change issues, or to cure cancer. We are seeing some exciting things in the industry, Samsung’s massive 8K TVs apparently use AI to upscale lower resolution images for the big screen. Sony has created a new version of the Aibo robot dog, which this time promises more artificial intelligence. Travelmate’s robot suitcase will use AI to drive around and follow its owner wherever they go.  Kohler has invented Numi, a toilet that has Amazon’s Alexa voice assistant built in etc., But despite all this, it does leave me wondering: is artificial intelligence really what we should be calling this revolution?...
1 comment
Read more

Feasting your programming appetite with microservices

I have been coding for more than 25 years and have used more than 18 different programming languages (and their associated frameworks), spanning every programming style from simple scripting to procedural, to objected-oriented, to dynamic and functional — which is more attractive to the software engineering community these days. Let me confess, every time I switch to a new language or style I always think, “Oh, hope I can also do  that .” Trust me, no language is complete; no style is perfect. So, the only way to feast your programming appetite is to try something different which gives more flexibility. I honestly think the microservices style of application is the one that best delivers that needed flexibility…and the fun that most of us are seeking. Read complete blog at HyperThink of CSC Ingenious Minds
Post a Comment
Read more

Effective Pattern Identification Model for DDoS Attack Detection

Abstract: Distributed Denial of Service (DDoS) attacks are one of the major challenges to Internet community. Attackers send legitimate packets with often changing information from various compromised systems at random and at a very high frequency, rendering the target non-responsive for normal traffic. DDoS attacks are difficult to detect with traditional detection methods and standard Intrusion Detection Systems (IDS). Standard IDS tries to analyze the network traffic or system logs trying to identify emerging patterns on the network traffic. But due to randomness of the package origins it is difficult segregate true, false positive and normal traffic. This paper proposes a model based on Artificial Neural Networks to identify anomalies and detect DDoS patterns. In the proposed system sets of known characteristic features, which can separate attacks from normal traffic, are fed to the system to train the Artificial Neural Networks (ANN). This self learn system improves with each n...
Post a Comment
Read more