One of the challenges of maintaining Cloud based or Software as a Service (SaaS) TEM solutions is about keeping data in the service up to date. This is especially true in environments where large volumes of data are kept in disparate systems. When information about users and devices are maintained inside of HR systems, the maintaining of the same information inside other services that depend on that information leads to double work. And often leads to errors. SaaS solutions often advertise standard web service integration points where this information can be sent automatically when there are information changes in the source HR system. This can bring the data in both systems in synchronization in regular intervals, or even near real-time. But that requires an investment on the source system side to implement SOAP messaging. An alternative method could involve automated loading of data from spread sheets or flat-files which can be exported from the source at regular intervals.

A handy extension on the traditional TEM solution is asset management. In this extended scenario, the TEM solution is no longer only a consumer of data. The process of managing the lifecycle of assets frequently touches on other domains. For instance, placing an order for new assets involve registering the order at a supplier as well as entering it in the asset management system; leading to double work and the potential of errors. Asset management workflows that handle the authorization of orders could require the fulfilment party to work on the same system. But more and more the operators and resellers are starting to advertise their capabilities as web services. It is fast becoming a necessity to integrate the asset management solution with the fulfilment providers.

Nowadays, there are so many services and websites that is, oh so, handy. Every website used to require a separate login name and password. Thankfully, many of the modern websites, especially social media sites, allow you to login by using your Twitter or Facebook account names. Behind the scenes, there is a technology called Single Sign-On (Single Sign On); and there is many references to OpenID in this area. In the Business to Business environment we have the big brother of SSO, called Federated SSO. Companies that already have active directory based authentication in place, typically have everything inside the company wired in such a way that the end users do not even notice the seamless switching between different applications. This same seamless switching can be extend to some modern cloud services, with little effort on the side of the company or the service.

In an overly (inter-) connected  world, security has to be taken very serious. A number of measures has to be implemented to keep the hackers out and keep the honest folks honest. Every message that arrives at the web service interface needs to be encrypted, in the same way we expect from trusted web sites, by means of SSL. On top of that, some form of access control needs to ensure that every sender only gain access to the correct services and data. Web services security (WS-Security) requires a digital signature on every message. The combination of these measures protects the parties involved in the transactions from a wide range of vulnerabilities, including: identity theft and unauthorized access to confidential information.

Integration is the glue that will help build cloud computing solutions that is less isolated, while enforcing high levels of security.

• 27% growth YoY in smart phone shipments shows the increasing popularity of smartphones;
• The Apple iPhone shipments represent over 17% and even overtakes RIM in popularity;
• Nokia retains its leading position but looses 12.4% market share;
• The charts will look differently with Android and Storm on its way in Q4. 

Adoption of Smartphone takes place with professionals in enterprises first as business users like the Apple iPhone for the obvious reasons, as is shown in the recent customer-satisfaction survey taken by J.D. Power.

What does this mean for the enterprise?

• More unique platforms to support, more complex devices……….expect support cost to increase, as it takes experts to fully understand the different platforms and expect end users to ask more device specific questions;
• Devices are geared for high mobile data usage…….will the operators keep promoting “all you can eat” or “fair usage policies” once adoption is there or will they eventually move to an usage based model, how to deal with mobile data roaming…..expect mobile data cost to increase. Ezwim has seen 100% growth of mobile data cost in recent years through its Ezwim Telecom Monitor;
• Device are becoming more open and powerful……end users will put their own software on devices……what about security (Trojan horse, etc.) and what about interoperability issues…..enterprises will need to spend more in establishing and enforcing corporate policies by means of the right tools.
• Devices are becoming more expensive and have a shorter life span…….in the past a simple voice centric device of 100 Euro with a write off in 24 months would be sufficient, today a Smart Phone of 220 Euro with a write off in 14 months will become the standard……

Does the above sound familiar? Yes, it is like watching the life cycle of Desktop Management Services 20 years ago.
Enterprises should start managing the baseline cost and assets, set-up and enforce a corporate policy, and introduce service management.