Guidelines for CIOs to Get Started on Their IoT Journey


IoT projects can often times be more complex than what one thinks. Reason being that its still a relatively unchartered territory for most CIOs. The real life implementations that one can find for their specific industry and use case would be few and far between. When there is not much to fall back on, it always helps to hear some sane advice from those who have experienced it first hand.

                                    

Atul Govil, Chief Transformation Officer, India Glycols shares some key learnings from his IoT journey. Refer to these guidelines to figure out a good starting point for your IoT initiative.

 

 

-       Before venturing out into an IoT project create a case for why it makes sense. First understand what are the key inputs and outputs as well as the areas that need to be measured. Just because one wants to go for IoT one can’t have sensors everywhere. One should get some idea from the production and operations team to understand what is important and what crown jewels are there whose data needs to be brought to the central IT system.

 

 

-       An IoT project has to be driven along with business. It requires reaching out to the production, operations, maintenance, control, instrumentation and various other business teams, and having a dialogue with them. Hence, the CIO should come out from the ‘IT only’ frame of mind and be able to understand and speak the business language. The CIO should avoid speaking technical jargons and be ready to talk in a manner which the business teams can understand and appreciate, willing them to have a dialogue.

 

 

-       Sit across the business teams to get the groundwork done. Start off by asking them the following questions - what production systems are there; what sort of process control setups are there; what legacy they are carrying, what support they have in place for the systems; how the different things like productivity, safety, etc. are getting measured today; what type of predictive and preventive maintenance is being currently done; what is important and which are those crown jewels whose data needs to be captured into the central IT system; how often should the data be captured?

 


-       Once the groundwork, measurements and gathering of internal requirements is done, it is time to start looking at the prospective vendors. Start by first reaching out to experts in the Operations Technology (OT) domain. Once the OT part is taken care of and a good partner enlisted there, then start looking at the IT aspect. If one starts off by looking at IT aspects before OT, then there are chances that the project will fail to scale beyond a particular point.


 

-       When choosing an IoT vendor/partner, make sure they have good experience and some reference success stories to share. Most partners one speaks to would have cases to share wherein they would have put temperature and humidity sensors in the datacenter that they would be monitoring or would have built some GPS vehicle tracking system. Make sure to look beyond these for some real case studies. Once you understand that a partner has done work with 2-3 organizations, go back and reach out to these organizations directly to understand their experience, how they started the project, what they had envisaged, what they achieved, what were the pitfalls, precautions, etc.


(Image courtesy: Pixabay.com)

Categories: Internet of Things

About Author

Write a Comment

Your e-mail address will not be published.
Required fields are marked*

*

Recent Comments