Archive for the ‘VoIP’ Category

Healthcare – Integrated communication services

Friday, March 19th, 2010

The use of data cable and infrastructures within healthcare premises to carry information to and from the bedhead opens up the possibility of using the data cable for other facilities.Where data cables (for example Cat 5e, fibre-optic) are used to carry communication and control information to and from the bedhead, or other nursing position, in support of IP (Internet protocol)-based nurse call, patient/nurse speech, telephony, Internet and entertainment services etc, these should be capable of fully supporting the required computer network technologies as directed by the healthcare facility’s IT manager. Examples of computer network technologies include 10Base-T, 100Base-T, 1000Base-T (Gigabit) Ethernet, and Token Ring.

Utilising a common data highway may, however, impact upon business and clinical risk. Therefore, careful consideration should be given to the extent to which provisions are incorporated into the system to ensure adequate reliability and resilience of the various services so as to minimise such risks.

Data cables used for bedhead services will normally be independent of the main healthcare facility’s primary IT network (unless otherwise directed by the healthcare facility’s IT manager), but they will interface with the network at appropriate strategic points.

Relevant protocols and test procedures to achieve the required functional transparency and resilience should be agreed between the bedhead services’ equipment supplier(s) and healthcare facility’s IT manager before the interface(s) is/are installed.

Entertainment (radio and TV) and communication (telephony and Internet access) services may be provided through a low-energy digital device at each bedhead. Such devices should not be used as the primary control for any patient and staff calls, but should be capable of being used for patient health education and for menu-ordering in addition to other services as described in the list at the bottom of this page. When required, the device should also be capable of being interfaced with the hospital information systems and IT network for use by hospital staff and to reduce installation and maintenance costs.

Prior to installation, all facilities that utilise common data infrastructure systems should be adequately assessed with regard to their potential effect on other hospital systems, particularly in respect of any capacity, security and safety implications. Suitable provisions should be incorporated to ensure that such systems operate safely and reliably, with no unwanted interference being incurred sufficient to cause operational difficulties between systems.

Appropriate input and output interfaces should be provided as necessary to ensure a fully operational system in compliance with manufacturers’ requirements and with functionality as specified elsewhere in the project specification.

Once installed, the capacity of a data cable is potentially considerable, so expansion of facilities in the ward or nursing area becomes possible with the appropriate input and output interfaces.

Some features that may be developed are:

  • Bed status: to indicate whether the bed is occupied, vacant, in the course of preparation or out of commission.
  • Patient monitoring: to allow the output signals from medical apparatus to be multiplexed onto the data line. This may take the form of a simple on/off medical alarm or a constant reporting of varying analogue signals to indicate a changing medical condition.
  • Menu selection: to enable the patient to view and select their choice of meal.
  • Patient details: to enable the entry of a patient’s name, address and all relevant personal information at the bedside.
  • Medication requirements: to display all medical details to the nurse or doctor at the bedhead.
  • Patient entertainment: Internet etc.
  • Communication: Voice over Internet Protocol (VoIP) telephony.
  • Patient administration systems: to provide full clinical access to the healthcare facility’s clinical data IT network at the bedside.
  • Door access and security: to allow the nurse-call system to be integrated with CCTV and door-access systems.
  • Clinical report displays: to enable laboratory results, X-rays and computed tomography (CT) scans to be displayed to clinical staff at the bedside.
  • Administration of drugs: to facilitate the accurate discharging and recording of drugs administered at the bedside.

Convergence Solutions – Explained

Thursday, November 12th, 2009

Convergence Solutions.

There is a lot of discussion about the merits of Voice over IP—or IP Telephony—at a technical level, but less about the business issues associated with a converged solution.

Black Box is a major supplier of infrastructure systems and is well placed to help you decide what is the best option for your business.

Black Box has experience from the largest to the most basic network. Whether this is the infrastructure for the latest generation network for a mobile operator or Motorola, or a budget network for a small business or even a complete voice installation for one of America’s biggest retailers, we have a solution.

Convergence
Convergence means having one common system to carry all forms of information (namely voice, data, video, etc.). Traditionally, each service has had its own network and associated technology. Voice utilised expensive PBX or exchange equipment with dedicated wiring to telephones. Data used a completely different set of cables and equipment, most commonly based on Ethernet. With technological advances and the growth of the Internet though, it is now possible to have one network carrying all the services.

So is it right for you, either now or for the future? Black Box can help you decide, plan your network and install the system; however, the solution will depend on a wide variety of factors. What you have now will influence the path you take.

Cost
It is a fact that a converged solution can save you money. The real savings, costs and benefits, however, are far less clear because the choices will be dictated by the need to move seamlessly to new systems without interruption of service or loss of quality. Depending on the age, facilities and performance of the existing voice equipment, you may want to consider conversion rather than replacement. Simply use a converter or special interface to allow some or all of the existing connections to utilise low-cost IP call facilities. Having one system simplifies management and support, reducing costs. Modern systems can be accessed and managed remotely, allowing the number of specialist staff on site to be minimised.

Compatibility
Any new system needs to integrate and offer compatibility both with the internal and external networks. There are international standards for IP telephony, so selecting the right equipment becomes easier. The two major techniques used are H323 and SIP. H323 is more established, especially when ISDN is used for the communication network. SIP is newer, but it is supported by major players such as Cisco and Microsoft®. Both will co-exist for some while, and work is under way to allow interoperation between them.

Capacity
Data packets can be delayed and, if necessary, retransmitted in the event of errors or problems. This is not a possibility with voice communication. Overlaying voice traffic on an old data network can create bottlenecks and delays, resulting in poor quality voice and slow data traffic. The network design needs to be checked and, if required, upgraded to support the extra traffic and ensure priority to the most critical types of traffic. If video is part of the system, this will place even greater demands on capacity.

Conversion
Starting with a clean sheet and scrapping all existing systems is an ideal unavailable in all but a few special cases. The need to provide paths to migrate from old legacy systems and procedures toward convergence is therefore paramount. Black Box has long been acknowledged as a specialist provider of products and technology that solves the problem of mismatch. Whether it’s a special cable, an interface converter or a complete change of protocol, Black Box is renowned for coming up with a solution.

Continuity
If all communication is taking place over a single converged network, then this could be considered a single point of failure. In reality, networks can be designed to be fully resilient; however, this has to be planned carefully and tested to make sure that everything continues to work smoothly in the event of problems. Having a converged network will make it considerably easier to establish disaster recovery procedures for a major critical event, such as a fire destroying an entire building. The requirements of new legislation on corporate governance also has an impact on communications, security and integrity of networks. Consolidating all systems under one management enables better control and eases problems of compliance with the requirements of legislation such as Sarbains Oxley, etc.

Confidence
Any system that involves access from the Internet has to be secure. Users have to be sure that they will not be overheard and that confidential information is not available to the outside world. Building in firewalls and other security procedures should be part of the design process, not a late fix to a leaky system. Support should be rapidly available when required and delivered in the most suitable and flexible manner to match the needs of the situation. Black Box provides on-site and on-line Technical Support on a local and global basis 24 hours a day, 365 days a year.

How to Approach IPTV Solution Integration – A Framework Based on Lessons Learned

Thursday, June 25th, 2009

End-to-end solution integration (E2E SI) is essential when creating a business plan for IPTV service offerings. Rather than taking a piecemeal or partial approach to integration—which often results in unacceptable end-user quality of experience — operators need a comprehensive method that addresses all aspects of the IPTV implementation. The approach discussed in this white paper is derived from experience gained from actual IPTV implementations over a number of years.

Introduction

IPTV technology is now mainstream. Many service providers have already launched or are in the process of launching consumer IP video services in an attempt to maintain or gain market share in a fast moving, end-user focused competitive arena. Their initial approach has been to offer service bundles of voice, video and data (triple play). These same service providers are contemplating providing their customers with blended VoIP, video and data services (rather than bundling traditional voice), as well as with quadruple play, which includes mobile services. Some typical current strategic, tactical and operational IPTV-related service provider issues include:

 

  • Media aggregation, management, and distribution solutions
  • Content negotiation
  • Existing network and network component capabilities
  • Broadcast and multicast delivery capabilities
  • Capacity to perform realistic trials
  • Enhancing and streamlining business operations
  • Management and billing capabilities
  • Quality of experience (e.g., spectrum utilization index design, interactivity, and User Interface (UI) responsiveness)
  • Quality of service (e.g., video/audio stability, scalability, and redundancy)
  • Home networking components, deployment and maintenance
  • Differentiated applications integration
  • Personalization of existing applications
  • Security and digital rights management
  • Understanding the impact of offering video services on the organization

The challenge of integrating new technologies, features and services into the service provider’s network is complex and demanding. The transformation process usually involves maintaining existing services while developing and migrating to the new service environment. To cope with this level of complexity, many service providers turn to a partner they can trust to help them transform not only their network and services, but also their business operations. This usually includes a combination of professional consulting and integration/deployment services.

Experienced solutions integration (SI) partners have developed the capabilities to address the real issues that service providers face when implementing IPTV or triple play. The SI either takes on turnkey end-to-end projects as the prime integrator and trusted advisor, or it can provide consulting advice in targeted areas such as:

 

  • Network integration
  • Performance
  • Security
  • OSS/BSS integration, and/or operations analysis
  • Rapid integration of new revenue generating, enhanced applications

The SI partner should have specialized lab environments that allow it to pre-integrate end-to end solutions with its own best-in-class partners. The labs are also used to develop the stringent processes required to carry out realistic proof of concept, trial, and commercial deployments for the service provider.

This paper describes how to perform IPTV solution integration, blending end-to-end IPTV component technical knowledge with a strong business-focused approach to create closely integrated work packages that are strung together via a “golden thread” that ties together all deployment lifecycle phases for maximum efficiency and consistency, making IPTV deployments and enhancements predictable, reliable and successful. The golden thread is a proven formula and methodology based upon many years of lessons learned in the field.

 

Components of an IPTV Solution

The key components of an IPTV solution that are typically deployed as part of a video services solution include:

Head-end and head-end subsystems – Includes broadcast service components with relevant redundancy and management capabilities. These components include all the equipment needed for content ingestion, encoding, encapsulation, and encryption, as well as DVB data extraction components.

Edge-QAM subsystem – For cable operator deployments, the SI partner must have the expertise to perform supplier management and integrate the selected edge-QAM hardware within the end-to-end solution.

Content management system – Enables the content providers and the operator to self-manage the full content lifecycle from offline encoding, via ingestion and metadata management, pricing, packaging, bundling, marketing campaigns, through distribution and storage management. The CMS solution is a collection of integrated components covering the required lifecycle functionality of all content types.

Content protection: conditional access /digital rights management (DRM) – A suite of integrated components covering all aspects of content encryption/decryption. Tight integration between all solution components and the CA/DRM vendor components is required.

Video on demand (VOD) server and back-office systems – Video (or streaming) servers are responsible for pushing the content over IP via standardized protocols. Integration of the streaming servers with the head-end, CA, middleware and content management is required. Video services middleware platform – Central IPTV component carrying all the business logic of the IPTV service and responsible for interfacing and managing all solution components and players – e.g., underlying network, head-end, CA, video servers, back-office legacy systems (e.g., OSS, BSS, Customer Relationship Management [CRM]), Content Management Systems (CMS), Integrated Access Device (IAD), set-top box (STB), and end user.

Transport and access networks – the characteristics and capabilities of which bear heavily on service levels delivered to end users. The network is an integrated part of the overall end-to-end video solution and should be considered as such throughout the entire process of strategic planning, design and deployment.

Customer premises equipment: residential gateway (RG)/IAD and STB – The RG/IAD enables the operator to perform end-user provisioning and home device management. The STB is the main component the end-user interfaces with. The STB typically interfaces with the middleware either via a native client or web browser.

An experienced SI should be able to perform vendor evaluation for all solution components selection, including proof of concept, interoperability tests, benchmarking, and “shootouts.” Once the solution component is selected, the SI directly interfaces with and manages the supplier on behalf of the operator.

A Business-Focused Project Approach

A business-focused approach implies that the SI must be aligned to the service provider’s deployment journey from the initial services concept through commercial launch and beyond. Figure 1 below shows the typical phases an operator undertakes when launching a video services solution.

Click here to enlarge Figure 1

Moving through these phases provides the operator with maximum confidence in the service’s readiness in terms of stability and functionality. This approach also minimizes risks while receiving user feedback prior to commercial launch.

The schematic indicates several phases of market scanning along with one or two “friendly user” trials. Following commercial launch there are usually growth and solution extensions and enhancement phases. Eventually, a product enters a “steady state” period. At this stage, the solution is not frequently enhanced or extended, user growth is predictable, and at some point a decision is usually made to reinvent or retire the product. Due to the emerging nature of the IP video business and the ubiquity of IP, many of the current commercial IP video offerings are more likely to be enhanced into new products rather than retained in their current state.

Because service providers are historically very experienced in product introduction, an internal methodology usually exists – albeit focused on a different type of end-user product. Every provider has a different focus, experience, requirements, and way of working, which results in a well understood internal methodology. Usually this methodology is a set of traditional processes that the organization adopts when deploying new services that fit the organization’s structure, behavior and culture.

These processes and procedures – down to the smallest details – have become an integral part of the organization and constitute a methodology that the organization’s team members are accustomed to working with. The SI must take this internally developed methodology into account when assisting in an IPTV deployment.

Application of a Project Methodology

Experienced solution integrators have developed a project lifecycle methodology to guide their integration services. They also have created methodologies specific to individual solutions such as IPTV. The more experience the integrator has, the more its methodology will be end-to-end focused and complete. Superior methodologies, which can take years to build, should be flexible enough to align with the service provider’s internal processes and existing methodologies as highlighted above.

At a high level, professional solution integrator methodologies include five focus areas/phases that are executed in a cyclic fashion. These are:

 

  • Consult
  • Design
  • Integrate &Validate
  • Deploy
  • Maintain and operate

Simply adopting the integrator’s generic methodology may not be the optimum way to achieve the desired project results. The integrator should work with the service provider in order to understand the organization, culture and current methodology being applied to new service introductions. This allows the integrator and provider to collaborate on creating the optimal methodology for introducing video services – a methodology that best fits the service provider’s organizational structure and culture. In addition, it will thoroughly cover relevant video service solution areas, ensuring that all high-level criteria required for such a deployment are met.

Translating the Methodology to a Timeline

This resulting methodology has to be translated into a meaningful timeline. First, activity subjects are defined for each high-level step (i.e., consult, design, integrate, deploy, maintain and operate). Once defined, each activity subject (or “workstream”) is broken down into “boxed set” of activities called “work packages,” or, more formally, “professional services solution integration modules.”

The work packages are defined to meet specific customer business and technical needs. They also take into account the organization’s operational structure and include an estimated effort in time and resources. Adding all work packages and workstream timelines provides the overall project duration.

The figure below shows typical solution integration project subjects (workstreams) that fall into the high-level steps described above. When drawn in a linear fashion, the timeline provides an initial idea of the entire project’s duration and scope.

Click here to enlarge Figure 2

The work packages building the work streams are addressed as independent but correlated sub-projects. Each work package has its own scope of work duration, and associated resources for execution.

An experienced SI’s portfolio for IPTV should be constructed on a set of carefully selected field-proven work packages. Furthermore, the design of each work package should allow execution individually or in conjunction with others, depending on actual project requirements.

The Secret Behind Professional SI Framework Execution

A typical IPTV solution integration project involves many work packages. These work packages not only function as stand-alone modules, but also must be able to integrate with all other work packages. The ability to deal with the complexity required to bring all the work packages together as an E2E solution is the key characteristic of a successful, professional SI. As indicated in Figure 3, each work package may consist of dozens of subtasks and activities, and is usually handled as a project on its own with a dedicated project manager and team. However, the golden thread methodology applied by professional sis ensures that the single work package is closely linked to all other work packages associated with the project.

Click here to enlarge Figure 3

As indicated in Figure 4, each work package goes through a series of high-level methodology steps to ensure that all required information is available, that nothing is hidden from the team and that work package activities truly reflect all aspects of the project.

Click here to enlarge Figure 4

In a typical service provider project, work packages move through the consult, design, integrate, deploy and maintain cycles. When mapping the work packages to the five-step high-level methodology, the SI may find that some work package subtasks are already in process or partially complete. It is the job of the integrator to identify where each work package is in the five-step process, to verify that the steps already completed actually meet the required criteria, and to continue the process for the work packages as defined.

Fast Facts About Work Packages

In order to assist definition and project planning, work packages should;

 

  • Be clearly distinguishable from all other work packages in the project
  • Have a scheduled start and finish date
  • Be the responsibility of a team leader
  • Have specific resources assigned from the integrator, service provider and third parties
  • Be scoped from design to delivery
  • Be completely documented in the project book
  • Be flexible enough to adapt to service provider’s internal needs and allow tight cooperation between service provider, solution integrator, and other third parties
  • Be designed to work in tandem with other work packages as required to achieve the desired project outcomes
  • Have the ability to run standalone, allowing a specific offer (statement of work) to be produced for each work package

A Word on Program Management

For complex end-to-end IPTV solution integration projects, strong focus on program management is one of the keys to ensuring the fluidity and interaction between work packages, as well as overall program tracking and communication. It is advisable to have highly experienced program and solution managers as solution implementation integration and deployment leads.

The solution manager role typically involves making sure that all input is gathered, performing an overall status analysis, and consolidating the issues and risks associated with all project teams, including third parties. Specifically for third-party management, the solution manager should have access to all relevant information on the technical and operational aspects of the suppliers solutions.

The solution manager initially manages the project organization setup and resource assignment involving the SI, service provider, and third-party organizations as mentioned above. Subsequently, the manager actively steers the project organization; this encompasses all work-package leaders and teams involved. In order to do this, the manager should be closely aligned with peers in the service provider’s organization, as defined at the start of the project.

Multilevel Discipline

A multilevel project management discipline is recommended to ensure deployment success. This typically involves a program management office structure that is responsible for taking the project from service description through commercial deployment. The project organization should include key service provider personnel who will steer and manage the project.

A time-tested approach, depicted in Figure 5, is to create three project levels: project steering committee, project management and project operational. For smaller projects, only the project management and operational levels are required.

Click here to enlarge Figure 5


Project Steering Committee Level

This level includes representatives of the sponsor and enabler of the project. They articulate the project’s business-related goals and provide the project management level with the authority to manage the project as the leading team. The representatives meet at intervals determined by the business’s size and relevance of the project – typically once per quarter or, for very large projects, on a monthly basis.

Because the steering committee is comprised of executives from the involved parties in the project, it is the highest level of escalation in case of disputes. This approach also ensures executive participation in risk assessment, investment alternatives and project roadblock management.

Project Management Level

The project management team usually consists of program managers, sales managers, contract administrators, financial controllers and technical project managers responsible for field operations and third parties. Depending on project’s overall scope of work – i.e., the number of work packages and their contents — this team can be extended by adding personnel associated with specific functions. These specialized team members can work either full or part-time depending on project requirements and planning.

The project management team, led by a global project manager, acts in a matrix function on top of the standard line organization. This project manager is also responsible for actively managing the project work packages.

Project Operations Level

Project operations are under direct control of the project management level and usually consist of teams gathered from the service provider, SI, and third parties. Depending on the project phase, the operational level teams usually consist of tender, operational, and installation and commissioning staff, as well as business consultants, legal specialists, and engineering staff. Also included are staff with other technological competencies needed by the project management team to achieve specific project objectives. The project operations teams are responsible for delivering project-specific, predetermined deliverables by executing the statement of work defined for their assigned work package.

Conclusion

For a complex implementation such as IPTV, the negative consequences of deployment errors and implementation shortcuts underscore the need for a well-designed project delivery methodology aligned with the service provider’s business goals. Lessons learned based on global implementations have led experienced solution integrators to develop an IPTV solution integration approach that is flexible and also mitigates the most common risks and pitfalls that service providers are likely to encounter.

Most effective is a business-focused approach that breaks down typical project methodologies into specific work packages. These work packages are carefully developed and aligned to the service provider organization and capabilities. They are then executed under strict control from a multi-tier program management organization. Assigning specialists with specific expertise to each work package, and supporting the entire effort with resources such as in house lab facilities, provides both the solution integrator and service provider with a high level of confidence that they will achieve a successful IPTV integration and implementation.