‘Instant’ Messaging (IM or IMing) is an application to shoot an instant text message for ‘Quick questions and clarifications’ and enable rapid information dissemination and decision-making between one or more persons ‘collaborating’. The text is conveyed via devices (also phone) connected over a network such as the Intra/Internet. It is an informal form of knowledge exchange although the actual conversation can be saved for different purposes. IM is also less intrusive, as ‘discussions’ between co-workers are briefer compared with for example phone. Still certain IM clients today also support traditional phone capabilities (VOIP) as well as support of file sharing and webcam. There is a large variety of IM clients and Wikipedia publishes a list of these. One of the key impediments to a large usage today is the compatibility of protocols. The escape is to use a developer with a strong market presence and rich functions. Skype for example started as an internet phone capability and includes now IM as well (see also Application Sharing).
So IM is an ideal tool to quickly consult an ‘online’ coworker regarding a technical challenge. Working with companies we see this technology used as the need for effective knowledge sharing, team working and collaborative environments amongst employees has become vital, especially those teams working in geographically dispersed. Statistics further learns that Tens of millions of the consumer IM accounts in use are being used for business purposes by employees of companies and other organizations. IM adoption usually is a bottom-up evolution as employees adopt these capabilities, sometime against company (compliance) rules.

Hardware-oriented MRO systems need to cope with the accelerating complexity and velocity of change found within hardware embedded (and loaded) software on today’s aircraft, cars, ships, industrial products etc.. One of the most critical aspects that PLM can address is the coupling of hardware and its certified software. PLM Configuration Managed software can nicely sit next to an EAM/MRO application. Integration of applications concerned with management of requirements, configurations and maintenance statuses captures all of the critical information needed to assure that the software status of an asset is known at any point in time. From the MRO perspective all relevant information regarding the ‘master record’ configurations are available (See also Enterprise Asset Management category) across specific aircraft categories for example, but also the  individualized real-time status information of the current configuration for every managed tail number. We all remember the stories of software problems in cars, here the same link can be established between the Vehicle Identification Number and its software status. When integrated with problem reports, a complete closed loop failure record and action system can be operated and this would provide a full accountability from discrepancy till resolution.

Read the rest of this entry »