Monday, December 23, 2013

What is a ‘Digital Strategy’? Unlocking the ‘Enterprise Potential’ - Taking a different view with MobileFirst in 2014


Folks,

This has indeed been a busy year, with new product launches, new acquisitions, and new business models seems like every company is trying to reinvent itself and in process claiming innovation, thought leadership and market leadership. To this, I spend sometime in pondering over  what’s next? Does a new mobile app, which is cool, and has generated a buzz and that albeit may extend an existing business process – validate the claim on “innovation”? Or mere product rejuvenation? Will this trend continue in 2014? I would like to share some thoughts on my last post of 2013, thereby, reflecting on 2013 and pondering on what is to come in 2014. I think our conversation ought to be much different in 2014 – especially on Innovation landscape.

I’d like to start with “Digital Strategy” as a conversation starter? Do our clients understand what it is? Do we understand what is a  “Digital Strategy”?  Investment into IT strategy be it in Cloud, Big Data, Business analytics and even enterprise mobile platforms can be construed as Digital Strategy but it is NOT! Let me explain. The new era of business, client interaction and simple transaction, be it selling, commerce, client care will be pervasive, much like how we interaction with our connection in social media (on-line or in person), it is context aware, relevant and pervasive! This means an enterprise strategy that relies on various data points from various sources about the:

a.     person (customer/employee),
b.     Things (inventory, item, UPC) and
c.     Place (Location)

i.e. -->Intelligent, instrumented and Interconnected.

Much like a Smarter Planet campaign launched by IBM about 5 or so year ago.  This type of permeating ‘interaction of systems’ requires an overhaul of the “systems Thinking” from an IT Strategy to a “Digital Strategy”. IT Strategy suggested a model that treated technology in isolation, project based deployment that has evolved into a Services oriented design. Digital Strategy on the other hand focuses on  harnessing all-encompassing amalgamation of individual technologies such as a cloud, big data, Mobile, Business analytics etc, to provides us with a unified and contextual view of an Object (person, things, place). An enterprise should thus “focus their strategy on digital transactions based on automating and substituting physical resources for digital will only feel digital. Such digital substitution strategies create virtual copies of the real world, creating e-channels, e-stores and other e-surrogates for physical processes”1.  How much of this “Digital Strategy” do our client’s capitalize on?  How much of an ‘enterprise potential’ can this unlock for our clients? --- Something to ponder upon!

Now, Mobility/Mobile Application as a medium is most certainly disruptive to the enterprise computing platforms, as it imposes several technical challenges (such as scalability, security and new computing models) which can be expensive and time consuming to be meaningful, but Mobility/Mobile application also provides organizations, small and large alike, to exploit the possibilities presented by this new digital model with relative speed – this is possible due to community defined standards (Frameworks, standards etc), data source in public domain (social media) and shifting the computing (processing)focus ( and data entry) to the end consumer. So this is fundamental shift in consumer driven computing, processing (and data) model.  I think this trend will continue to dominate in 2014 and beyond and we simply need to understand and find avenues to adapt and exploit this shift as it related to an enterprise digital strategy.

I would also like to touch upon how these digital touch point’s fare in Mobility/Mobile Application paradigm. To this I would like to broadly classify touch points as follows. ( Please note this is broad category to explain the digitization not ONLY Mobility):

1.        User Specific data (Instrumented) – This includes all user specific data including user profile, preferences, user data owned (co-owned) by user in social media (public and private). This can be B2C or B2E depending on the context.

2.        Security (Intelligent) – This related to context and risk based access, user credentials, shared security domain and trusts (OAuth/SAML etc).

3.        Location specific data (Instrumented) – This relates to Location i.e. place specific data includes GPS coordinates, Cartesian coordinates, and in-building location via access points. This also include the location of transaction i.e. place of transaction execution, range, geo fencing etc.

4.        Enterprise Messaging (Interconnected) – This include bi-directional communication with users, things and places.  Messaging also include receiving messages from sensors, events, users and their devices.


5.        Enterprise Intelligence (Intelligent) – Enterprise intelligence refers to our digital strategy discussion. The ability for an enterprise to collectively harness, Analyze and digitize the invest into physical assets, IT systems and People.

Technically Speaking:

I. Mobile Security:  I think Mobile Security will be part of every true enterprise mobile conversation. With security breach at “Target Stores” during peak holidays season followed by media coverage has brought security into focus, and I think Mobile security should be on every CIO/CMO’s radar.  So I suggest we better understand the Mobile security landscape to better prepare for 2014




Broadly speaking we categorize Mobile security into 3 aspects:

1. Security (App and data) on Device: This includes everything on the device including (but not limited to):

a. B2E (in some cases B2B) -- MDM -- Device management such as a Device signature/device registration (trusted)/Jailbreak detection etc.
b. B2C - Application tampering/Malware related exploits/data on the device etc

Broad range of solution to address many of these facets:
(i) Containerization – Aim to address separation of work and play, secure containers or protected sandbox for secure and trusted (signed) application/data and resulting traffic security.

(ii) Securing the application -- Malware injection/tampering/Application auth tests/Data exfilteration -- AIM to make sure that the app and related data is secure. 

(iii) Securing the data on the device and prevent leakage --- goes back to on device data encryption, transport encryption (enforced by enterprise security), access control etc.

2. Security (Data) in Transit/ Transport

This is to ensure that data is securely transported AES/SSL/TLS -- mostly enforced by protocol over public network and enforcement is burden of the enterprise -- Tools such as a ISAM for Mobile (with integration with SIEM for reporting), Datapower - for AAA etc, Edge and reverse proxies etc.

Now this has been business as usual we now begin to see Mobile and context awareness requirements in the edge and a more intelligent ways to provide access control (OTP/MOTP etc)

3. Security (Data) in Enterprise:

This is also business as usual for many enterprises with securing enterprise application/services and data and access to it. Things like AAA, trust interceptors and role based enterprise security access with PAP/PDP/PEP concepts at play. Here also we now begin to see Mobile and context awareness requirements.



Reference:




Thoughts on 2014:

Let us focus on conversation and design around Enterprise “Digital Strategy” which is pervasive and all encompassing. Mobility will certainly dominate “Digital Strategy” discussion, and mobility is not just Mobile application but includes M2M (Machine to Machine), sensor data and implicit interaction between systems that needs to be captures and analyzed. Above all I believe 2014 will kick off a new era in Digital Evolution – and we all have a tremendous opportunity to contribute and lead.

As Always I welcome critique and thoughts.

Have a Great Holiday Season, Merry Christmas and Happy New year – 2014!

:)
Nitin

Monday, December 16, 2013

Mobility in Travel and Entertainment - Shipping and Cruise Lines - Industry Imperatives



Team,

 This week I will focus on  an interesting set of use cases I discussed with a ship builder and Ship operator and some innovative IBMers. Below is a  Summary of discussion I have had last week.

I have discussed in the past on reasons why Our customers invest in Mobility, let us revisit that:

So looking at the reasons on why our clients and enterprise will invest into mobility is broadly categorized into 3 areas:

1.     To Monetize – Simply put, a Mobile application/platform will generate new revenues, and becomes strategic go to market strategy. Example  retail, cruise lines etc.
Constituents – B2C and B2B in some cases.

2.     To make people productive – This includes ensue that employees in office and field, be is sales or oil rigs can do their job and add to efficiency factor.

Constituents: B2E or B2F(ield)

3.     To provide better customer service – This category, the enterprise may not be able to monetize or have direct impact on bottom line, but need to provide a channel that is in tune with times. This is simply cost of doing business. At times it is hard to put numbers behind good customer service.

Constituents: B2C or even B2E

Now looking at Shipping Industry we have 3 Players:

 In the section below I explore the various players, their motivation to invest into mobility and collaborative platform where each players can provide a value add capability that will enable the other to either exploit the platform capability or build upon it.

1.     Ship Builders
Ship Builders are the one that build ships that are used by the Ship Operators such as cruise liners, and other defense installations.  Ship builders have a consideration including on-board network planning, bandwidth estimation, application frameworks and re-tooling and maintenance.

Motivation:
a.     Provide Value add:  by providing infrastructure such as an access points, messaging infrastructure, and other infrastructure on the ship.

b.     Provide an environment: which enabled the operators to “bring their application” and a drop in scenario. This is value add to operators but the software ownership is ship builders burden.


c.     Data ownership: this implies that the ship builders own the data, and while many operators may not agree to this model the ship builder will be now responsible to support application design, development, deployment, management of the infrastructure and introduce a “Bring your Application” model”. This model implies a transformation that includes a data induced business model.

Technical Considerations:
a.     Network Infrastructure planning
b.     Messaging and Application infrastructure
c.     Long term maintenance and technology Re-tooling

2.     Ship Operators
Ship operators are the entities that operate ships such as cruise liners, defense installations such as Navy and other Merchant Navy organization, which carry freight. In case of defense installations such as Navy and other Merchant Navy organization the demands for security and application may differ and may be limited by regulation and policies but the ubiquity of mobile application remain.

Motivation:
a.     New Marketing channels: The ship operators have an avenue to exploit an untapped opportunity to connect with on board guests in real time. Some new marketing opportunity include on board network to enable person-to-person connectivity, On board service and ad-hoc offers, on-board location based services, real time messaging of on-board events and a channel to introduce partner services such as a content and concessions.

b.     Better customer services: Mobile specific services such as a on board real time messaging will allow for better crowd control and management, events notification and suggestive analytics. This also include Emergency services such as an alerts, location-navigation and on-board security services.

c.     Business services integration: Due to availability of on board network and in-roads into the mobile device via a Mobile application various business services such as content by a content provider (DirectTV/Amazon/Netflix etc), Games, coupons and promotions by the contracted concessions on-board.

 Technical Considerations:
a.     Application and Middleware Considerations
b.     Application Store infrastructure
c.     Integration – existing billing systems, back end system and analytics platforms.




Example:

a. Enabling employees -- Use of Mobile device as a POS systems -- Point of sales system  on the ship. -- this includes integration of Company issued ruggedized devices with an APP and on board point f sale system. The device can wither have a  swipe option or be specially ordered with credit card or key swipe feature.

The business drivers here are  costs saving of POS maintenance and dynamic updates to these with MDM ( mobile device management) integration, since the device is issued by the company.

b. Use of Mobile device for person to person communication -- this include on board app store  provided app store and on board connectivity. Two components here -- on board network this is provided by closely connected access points that helps with basic 802.11 type connectivity -- think of this as self contained network system. And Application to provide VOIP ( Voice Over IP) capability to make person to person ( UA to UA) call based on registration  --- this functionality to be enabled by SIP services ( Session initiation protocol) which exploits the 802.11 network.

Business Drivers -  Application sales will generate new revenues and negate the need to maintain way phones which is "in-cabin" communication system. Also provide avenues to absorb other mobile services.
Caveats: Costs - the most expensive part was the "on-board" network  and the Infrastructure to enable this application framework.

3.     Partner Services (Business Partners)
These are business partners that offer services in partnership with Ship operators. This includes on-board vendors, concessions and on-board service providers that are providing or have an avenue to provide services on ships. Some examples include but are not limited to  vendors such as a entertainment and content providers, concessions, gambling and like services.

Motivation:
a.     Integration with On-board service orchestration: this includes partner offers capitalizing on impulse purchase behavior and captive consumer audience.

b.     Real time offer management: Based on triggers such as a crowd density, promotional considerations and combo offers, gamification and rewards, entertainment and engagement with activity and on-board mobile messaging infrastructure.


c.     Access to Mobile and other e-services: Ability to provide services such as an e-mail (disconnected mode) and other e-services such as voice (over IP) and integration with satellite services (for fee service). Other online services include  “circle of friends communication”, person to person communication and suggestive analytics with services, offers, activities and reservations.

Technical Considerations:

a.     Application and Middleware Considerations
b.     Partner Gateway Services
c.     Integration – existing billing systems, back end system and analytics platforms

 Have  a a Great week!

:)
Nitin