Real Time Communications Featured Article

Why Real-Time Communications Relies on Standardization

December 30, 2014

A lack of change is often considered boring. It stalls the mind, stifles creativity and leaves the audience yearning for more. It is the reason why innovation continues to capture attention; the driver behind long lines each time a new iPhone is released. We yearn for change and progress, yet we thrive when the consistency we abhor is protected behind the scenes.




This consistency is the foundation necessary in real-time communications. In the IT world that is supporting our desire to stay connected, standardization is an absolute necessity to ensure communications are supported at every end point. A recent Sys-Con Media post highlighted that this standardization enables the model driven architecture, helping to provide stakeholders with varying views of the same information.

Why does this matter? One of the challenges in the IT world is the way information tends to be presented: huge description documents that are difficult to understand and a challenge to validate. IT architects tend to spend more time behind the scenes understanding the current state of the enterprise instead of creating new designs that could help move them forward. There is no collaboration as the maturity model is still elusive.

This maturity model takes IT from the non-standard architecture description where documentation practices are lacking and information is in textual form to the standardized modeling that provides a baseline for elements and attributes within the modeling. The next step is the shared repository for models and views, enabling the search and reuse of information. Finally, mature organizations arrive at collaboration and document automation where teams work together on models, document creation and publishing are automated and patterns are created and reused.

If you apply the same theory to communication, you have a clear difference between the need for consistency. Where creativity might be hampered, communication is enabled. When real-time communications continue to be a primary demand within the business market, settling for anything less than the standard means collaboration and automation cannot be achieved. When consistency in notations and process is enabled, communication barriers are reduced, or eliminated, and assets are easily reused to optimize the investment.

To get to this stage, the Enterprise Architecture tool must be enabled to ensure the use of a shared asset repository. To select this tool, however, you must establish the methods and standards. This gives you the choice in the tool and allows for the adoption of a streamlined approach to reaching maturing. By doing so, real-time communications is not only enabled, but readily supported with a standardized infrastructure. 




Edited by Maurice Nagle

Article comments powered by Disqus


Home
  Subscribe here for RTCW eNews