migration strategy - traduções juramentadas tradução ... web viewthis...

Migration StrategyRadio System MPT1327 to DMR Migration for Cerrejon

Issue Draft v1 March 2017

CONTACT INFORMATION

Tait Communications Corporate Head OfficeTait LimitedP.O. Box 1645ChristchurchNew ZealandFor addresses and telephone numbers of regional offices, refer to http://www.taitradio.com.

COPYRIGHT AND TRADEMARKS

All information contained in this document is the property of Tait Limited. All rights reserved.

The word Tait and the Tait logo are trademarks of Tait Limited.

All trade names referenced are the service mark, trademark or registered trademark of the respective manufacturers.

of 28 Migration Migration Strategy Draft v1

http://www.taitradio.com/

CONTENTS

CONTACT INFORMATION................................................................................................................................. 2

PREFACE........................................................................................................................................................... 5

Purpose............................................................................................................................................................. 5Scope................................................................................................................................................................ 5Publication Record............................................................................................................................................ 5Document Status............................................................................................................................................... 5Document Approvals......................................................................................................................................... 5

1. INTRODUCTION....................................................................................................................................... 6

2. OUTLINE OF THE MIGRATION PROCESS.............................................................................................7

2.1 Migration Objectives................................................................................................................................ 72.2 High Level Migration Phases................................................................................................................... 72.3 Consultation Phase................................................................................................................................. 8

2.3.1 Consultation Workshop.........................................................................................................................................82.3.2 Understand the Business Vision...........................................................................................................................82.3.3 Assessing Constraints..........................................................................................................................................92.3.4 Assessing DMR Solution Fit.................................................................................................................................92.3.5 Assessing Migration Operational Requirements...................................................................................................92.3.6 Assessing Migration Technical Requirements....................................................................................................102.3.7 Assessing Interfaces and System Management Requirements.........................................................................10

2.4 Planning................................................................................................................................................ 112.4.1 System Integration Planning...............................................................................................................................112.4.2 Fleet Planning..................................................................................................................................................... 112.4.3 Migration Plan..................................................................................................................................................... 112.4.4 Assumptions....................................................................................................................................................... 12

2.5 Design................................................................................................................................................... 122.5.1 Radio Network Coverage....................................................................................................................................122.5.2 Site Design......................................................................................................................................................... 122.5.3 Backhaul Network Design...................................................................................................................................122.5.4 Capacity Design..................................................................................................................................................132.5.5 Spectrum Planning.............................................................................................................................................132.5.6 Fleet Design........................................................................................................................................................ 132.5.7 Terminal Configuration Design...........................................................................................................................13

2.6 Deployment........................................................................................................................................... 132.6.1 L1 Support Training............................................................................................................................................132.6.2 Fleet Migration.................................................................................................................................................... 142.6.3 Backhaul And Router Configuration...................................................................................................................142.6.4 DMR-Ready Node and Gateway Deployment....................................................................................................142.6.5 Base Station Upgrades.......................................................................................................................................142.6.6 Migration Outline.................................................................................................................................................15

Migration Migration Strategy Draft v1 of 28

2.6.7 System Commissioning......................................................................................................................................232.6.8 System Acceptance Testing...............................................................................................................................23

2.7 Change Management............................................................................................................................ 232.8 Monitoring and Support......................................................................................................................... 24

3. RESPONSIBILITIES OF CERREJON.....................................................................................................25

3.1 Level 1 Support..................................................................................................................................... 253.2 Remote Access..................................................................................................................................... 25

4. APPENDIX ONE- TERMS AND ABBREVIATIONS................................................................................27


PREFACE

PurposeThis document provides a migration strategy proposal for the migration of the existing Cerrejon TaitNet MPT1327 system to a fully digital DMR system.

ScopeThis document covers the provision of the following services to Cerrejon:

The coordination of the rollout of a new fleet of dual-mode radio terminals;

The planning and design services required to enable a successful migration from MPT1327 to DMR;

Deployment services required to enable a successful migration from MPT1327 to DMR;

Monitoring and support of the networks during the migration period.

Publication RecordAuthor Steve Kingston, Richard Winter and Jorge Luis

Issue Draft v1

Document Status Draft

Date 15 March 2017

Document StatusIssue Date Signature Comment

Document ApprovalsApprovals Position Signature Date

Jorge Luis Area Sales Manager, LATAM

Belkis Pena VP LATAM

Daniel Pranic Global Services Manager


1. INTRODUCTIONThe current TaitNet MPT1327 radio system has been in place at Cerrejon for a number of years, and while the system has performed well over that period, it is now reaching the end of its economic life. In addition, a number of key system components are no longer able to be manufactured due to the inability to source key components. This will make support of the existing system increasingly difficult and expensive. A new generation radio system based on the DMR standard would provide a number of benefits to Cerrejon:

Additional system capacity, enabling more users on the system;

The opportunity to integrate with other applications such as remote telemetry;

Lower maintenance costs and higher reliability due to a much simpler hardware architecture;

Better monitoring and management capability.

Smaller, lighter portables with better shift life.

The migration of a large, mission-critical radio system is complex and potentially risky. Tait understands the critical dependency that the Cerrejon operation has on the radio system, and the very high production cost of any radio system outages. Tait has extensive experience in migrating radio systems and has successfully supported the migration of many systems in the mining, utility, public transport and public safety sectors. Tait understands the importance of the end user experience and how successful adoption of the new system is critically dependent on involving the end users throughout the planning and implementation phases.

Tait has invested a significant amount in developing technology and processes to make the migration process safe, reliable and user-friendly. Our gateways and dual mode radios and base stations are the key technology enablers, but a successful migration is equally dependent on following a structured and well planned process. This proposal includes a description of the process and key steps that we recommend Cerrejon follow for the migration. We have also developed a commercial construct that we think will suit Cerrejon.


2. OUTLINE OF THE MIGRATION PROCESS

2.1 MIGRATION OBJECTIVESTait have developed a migration process and supporting technologies to make the MPT to DMR migration low risk, economical and painless. Our objectives for the migration are as follows:

Achieve minimal disruption to operations.

Strive for the need for minimal end-user re-training.

Allow use of existing mobiles and portables during the migration.

Allow the upgrade of existing, serviceable base station equipment rather than full replacement.

Enable remote mode change of base stations from MPT-IP mode to DMR mode, to minimize the need for multiple visits to sites during the migration process.

Re-use existing, serviceable antenna and combiner/multi-coupling equipment where possible.

Maximise re-use of existing, serviceable equipment shelters, power distribution systems, linking equipment and equipment racks or cabinets.

2.2 HIGH LEVEL MIGRATION PHASESThe following diagram summarizes the high level phases that Tait propose for the migration process to ensure a smooth and user-friendly migration:


Fig.1 – Overview of the Tait MPT to DMR Migration process.

Each of these phases is described in more detail in the following sections.

2.3 CONSULTATION PHASETait has a long relationship with Cerrejon, and has a good understanding the current network. However, Tait’s ability to plan and support Cerrejon’s radio system migration is dependent on establishing a thorough understanding of Cerrejon’s current operation and future plans. We also validate our understanding of the current network, and confirm our understanding of any relevant internal and external constraints. We will seek to do this during the Consultation Phase. Once we have confirmed our understanding, we can plan the migration applying our building blocks in a systematic way that minimizes the risk of service disruption while protecting Cerrejon’s incremental investments in DMR.

The following sections outline the broad objectives of the consultation phase, which would be initiated with a workshop held at Cerrejon’s premises, and involve a number of key stakeholders. The objectives of the Consultation Phase are used as the basis for the agenda for the workshop.

2.3.1 Consultation Workshop

In order to plan the migration, Tait will need to understand the Cerrejon operation at a detailed level, and we recommend that we commence the consultation phase with a workshop at Cerrejon. The workshop would cover the following topics:

Understanding the Cerrejon business vision

Assessing constraints, both internal and external

Assessing the fit of the DMR Solution to the business needs

Assessing migration operational requirements

Assessing migration technical requirements

Assessing interfaces and system management requirements

Each of these topics is explained in more detail in the following sections.

2.3.2 Understand the Business Vision

It is important that Tait understand Cerrejon’s high level business vision so that subsequent design and migration decisions can be made with the right context. This session seeks to answer the following questions:

What are Cerrejon’s business priorities and future plans? What are the operational goals for the new system? What are the key business processes to be supported? Who are the end users and other stakeholders? How will they measure success? What is the target completion date for the migration? What are the migration project objectives?


2.3.3 Assessing Constraints

All projects and radio systems operate under a range of regulatory, operational, resource and financial constraints. Some of these are well documented and in the public domain, whereas others are informal and private. It is important that any migration plans make allowance for these constraints. The next phase of the workshop would be to capture and understand the following types of constraints:

Regulatory, Probity and Legal Constraints Financial constraints Operational Constraints User Experience Constraints Physical Constraints Spectral / Frequency Constraints. Worker Safety Constraints Temporal Degradation in Coverage / Capacity Anecdotal Constraints

2.3.4 Assessing DMR Solution Fit

This session in the workshop will assess which DMR system capabilities best meets Cerrejon’s business goals. Based on our understanding of the radio system functionality that is currently used, we can explore what might be possible with the new system to improve safety and productivity. We will explore how the following capabilities might support the Cerrejon business objectives:

Voice Location updates Mobile IP Fixed Data M2M telemetry (GridLink) Messaging Advanced Consoles and Integrated Dispatch Capabilities Push-to-Talk over cellular (UnifyVoice)

2.3.5 Assessing Migration Operational Requirements

It is important that Tait develop an understanding of the operational requirements that need to be incorporated into the migration plan. These can be developed through an understanding of the constraints captured in section 2.3.3, along with a deeper understanding of the Cerrejon operation.

Capture the operational procedures followed by the mine and supporting functions that make use of the radio system;

Understand the radio system user groups – how they are structured into fleets and groups in the current radio system, and how each function makes use of the radio system, in some detail. This would require capturing the key use cases of each radio user group, and any critical dependencies they have on the radio system (e.g. timeliness of calls, safety procedures etc);

Understanding the dispatch environment, and how the radio system users are managed operationally.


2.3.6 Assessing Migration Technical Requirements

The next workshop session will assess the technical requirements of the migration process, to assist with developing the migration plan. Areas that will be assessed during this session are as follows:

Terminals – understanding the makeup of the current terminal fleet and users, accessories that are used, and intrinsic safety requirements etc.

Exploring if there are any critical performance parameters?

Understanding what critical functionality (other than voice calls) that must be preserved during the migration process.

Capturing existing and future radio system Use Cases, and therefore call types.

Assess the state of existing network equipment, such as antennas, feeders, multi-coupling equipment, power supplies and batteries. Is their capacity and condition adequate for the migration, or do they need augmentation or replacement? Assess space available at the sites for any additional equipment required during the migration period. Please note that this may need formal site assessments, in addition to the workshop.

Reviewing existing and understanding future coverage requirements – what will need to change as a result of business plans, changes of applications or the addition of new users?

Dispatch systems – is there an intent to retain the existing system, or upgrade to a system that is DMR native to enable access to the new features supported by DMR?

Review the current and assess the future radio system capacity and backhaul linking capacity.

Review the current node software version, to asses if there are any upgrades needed to interface to the TN9500 gateway?

What third party applications or systems might be required to support the use cases and required functionality?

2.3.7 Assessing Interfaces and System Management Requirements

It is also important to understand what external interfaces will be required for the new system, and how the system will be managed, both during the migration and once the migration is complete. Considerations for this session will be:

Dispatch and external system integrations

Existing and Future Interfaces, features

Operational Support Systems (OSS), such as network monitoring and management, and performance management and reporting. Tait proposes that we monitor the existing and new systems throughout the migration process, so that we can ensure the integrity of the system. We will also monitor and report on system performance, and manage capacity on each part of the system as the migration process occurs, so that users experience good performance throughout the migration period.

Fleet management, and the use of EnableFleet to ensure that all radios are correctly configured. Explore the potential use of OTAP for updating radio configurations when necessary.

Existing and future Incident and Problem management and reporting.


2.4 PLANNINGThe outputs from workshop and consultation phase will enable Tait to develop a comprehensive plan for the migration, which will be presented to Cerrejon for review and refinement. Once agreed, the plan can be used as the basis for a final commercial proposal and scope of works. The following sections outline the work which will be conducted during the planning phase.

2.4.1 System Integration Planning

The MPT classic and DMR networks must co-exist for an extended period of time as the migration process takes place. Therefore a composite network addressing plan must be developed across both networks.

Based on the outcomes from the consultation phase, a network topology will be developed for the DMR network, taking into account the gateway locations, the need for resilience and the capacity requirements across the gateway.

Capacity requirements at the outset, during migration and at the conclusion of the migration process will be assessed, to ensure that there are no conflicts with any architectural or regulatory constraints.

An assessment of site space, power and antenna system requirements will be made at each site, to identify if there are any additions or extensions required.

A plan will be developed for the re-use, augmentation or replacement of network assets, such as antennas, masts, power supplies and batteries, based on the age and condition of the existing assets.

A plan for the upgrade of base stations will be developed based on the existing installed base and the expected migration process.

A plan for the establishment of any additional linking or changes to the linking topology will be developed.

A plan for the establishment of new interfaces to dispatch consoles and other third party systems will be developed.

2.4.2 Fleet Planning

Cerrejon have stated that they would like the radio system to be designed to enable the organisation chart. We interpret that to mean that the fleet and group structure should align as closely as possible to the organisational structure and the key operational processes. This task will use the Cerrejon structure to develop the radio fleet and talk group structure. It is expected that this will be a consultative process and that at least two review and revision cycles will be required to finalise the structure.

2.4.3 Migration Plan

Based on the findings of the workshop, a comprehensive migration plan will be developed and documented for review by Cerrejon. For the purposes of this proposal, the migration is assumed to be structured into several distinct phases, and is described in section 2.6.

Once the migration plan is agreed, Tait will develop a fully resourced and scheduled migration project plan, which provides a baseline schedule for the migration. Tait will submit the project plan to Cerrejon for review and approval. At this time the pricing for the Managed Service can be confirmed. Once the plan is signed off, the Design phase can proceed.


2.4.4 Assumptions

Although the consultation phase will answer many questions and provide guidance on the approach to be taken for the migration, there may still be some assumptions that are built into the migration plan and system design. It is important that these are stated so that expectations of both parties are aligned from the outset. Tait will include a list of assumptions in the migration plan.

2.5 DESIGNPrior to deployment, detailed design of the new system and the elements supporting the migration must be undertaken. Tait will undertake the design work, and provide the design documents for review and sign-off by Cerrejon. The following design tasks will be undertaken:

2.5.1 Radio Network Coverage

Although there is intent to re-use the existing sites and antenna systems, we understand that mining operations result in frequent changes to the topography of the mine area. We therefore recommend that coverage design be undertaken to ensure that the DMR coverage will meet Cerrejon’s needs. A Tait Systems Engineer will use coverage simulation tools, verification tools and test equipment to plan, predict, survey and verify network coverage to confirm customer requirement. Signal strengths are measured and topographical databases compare actual against predicted coverage. Tait will provide modelling of both the mobile and portable coverage.

2.5.2 Site Design

For the purposes of this proposal, it has been assumed that existing site equipment can be re-used and does not need expansion or replacement. Given that there is a very easy upgrade process for base stations, and that existing antenna and multi-coupling systems are all compatible with DMR, it is likely that relatively little design work will be required. At a minimum, site dossier documents will need to be updated to reflect the final state of the network equipment.

If after the workshop, it becomes apparent that further design work is necessary, the design work will be re-scoped and included as part of the revised plan.

2.5.3 Backhaul Network Design

It is understood that there is an existing digital capable backhaul network available to support the DMR network. On that assumption, there will still be some IP network design work required to support the DMR network. It is important that the backhaul network performs with minimal levels of latency and jitter. Tait can provide the IP design performance requirements in a separate document.

There will be some routing design to implement routing between the various network elements, and QoS design to ensure that the voice traffic receives the appropriate priority on the backhaul network. Tait will also calculate and advise the minimum capacity that will be required on each backhaul link.

The backhaul network will carry both analog traffic (MPT Classic and MPT-IP) and digital (DMR) traffic, depending on the phase of migration. Both have similar characteristics and there should be no issues provided that the capacity, latency and jitter are all compliant with the Tait design requirements.


2.5.4 Capacity Design

Design of the starting and finishing capacity in each element of the network will be undertaken. A review of the intermediate capacity requirements will also be undertaken, to ensure that there are no instances where the capacity limitations are exceeded during the migration. Capacity will be managed during the transition by regular load analysis and performance reporting. This is described more fully in the Deployment section.

If there are short term peaks in capacity required, Tait will provide the capacity, and recover the equipment once the migration has completed. These can later be redeployed as system spares if appropriate.

2.5.5 Spectrum Planning

Where possible, the existing frequency plan for the system will be retained during the transition. A review of peak spectrum capacity requirement s will be undertaken to ensure that there are no scenarios where the overall frequencies required exceed the available allocated.

A new control channel plan will be established for the DMR network, which is independent of the MPT control channel plan. This enables the radios operating in DMR mode to roam effectively, irrespective of the state of the MPT classic network status.

2.5.6 Fleet Design

A brief review will be undertaken of the fleet design developed during the planning phase. This design will then be captured in the EnableFleet system ready for the deployment phase.

2.5.7 Terminal Configuration Design

Once the fleet and talkgroup structure is finalised, and the spectrum design is complete, the base radio configuration files can be defined for each of the main configuration groups. These configuration files will also be captured in EnableFleet ready for the deployment phase.

2.6 DEPLOYMENT

2.6.1 L1 Support Training

Prior to commencement of the migration, Tait requires that people working on DMR L1 maintenance are competent and certified. Tait will provide certification training to the Cerrejon L1 support team on DMR equipment and the use of appropriate diagnostic, maintenance and support tools. Further description of our training services is provided in section Error: Reference source not found. In this case, Tait recommends that we provide Cerejon’s L1 support team with specific training on installing, commissioning and maintaining a DMR system. A full catalog of training courses can be made available on request.

2.6.2 Fleet Migration

Assuming that Cerrejon have purchased Tait dual mode terminals in a separate transaction, the upgrade of the radio fleet can take place as a background task that is largely independent of the network upgrade and migration work. It is important that training of end users takes place before the new radios are deployed or


installed, as part of the Change Management process outlined later in this proposal. Tait will work with Cerrejon to develop a training program and course material for the end users of the radio system. Tait will provide training for Cerrejon trainers to deliver the training to their staff, and will track progress of the training to ensure that it aligns with the rollout programme of the radio terminals.

The radios will all be preconfigured for later digital operation, but when first deployed, will be configured to operate in analog mode. Tait will manage the deployment as part of the migration project, in consultation with Cerrejon. Tait will use EnableFleet to track the progress of the installations, and to manage the radio configurations.

Tait will co-ordinate Cerrejon L1 support staff to install the radios in the vehicles. Use of EnableFleet makes the installation and configuration process simple and traceable.

The only dependency between the terminals rollout and the network migration is that all radios in a workgroup must have been upgraded before they can be migrated to digital.

2.6.3 Backhaul And Router Configuration

The backhaul links and routers will be configured to support the new network and the migration. In particular, configuration of routing tables, establishment of QoS rules, and corresponding configuration of the base stations and nodes will be completed during this task.

Once the backhaul configuration is completed, some commissioning tests will be performed to ensure that the required latency and jitter performance can be achieved.

2.6.4 DMR-Ready Node and Gateway Deployment

The TN9500 gateway, MPT-IP nodes and DMR nodes will be installed and interconnected to the MPT Classic system. The voice traffic will be carried between the TN9500 and the MPT Classis system over E1/T1 cards. Call control (C plane) and management information (M plane) will be carried across the interface via the IP interface.

2.6.5 Base Station Upgrades

An upgrade kit will be used to upgrade the TB8100 base stations to TB9300 base stations. The base stations will initially operate in MPT1327 mode, but will interface to the IP backhaul network and voice traffic will be carried back as IP packets to the MPT-IP node. Each channel can later be converted to DMR operation, remotely through the management interface of the TB9300. Note that any T800 base stations still in operation will need to be replaced with TB9300 base stations.

During this phase, voice calls will be routed as required between the MPT Classic system through the TN9500 gateway to the MPT-IP system. From an end user’s perspective, there will be no discernible difference to radio operation.

2.6.6 Migration Outline

For the conversion of the existing radio system from an MPT1327 analog, trunked radio system to a fully digital, trunked radio system based on the DMR open standard, three main phases are proposed:

1. Railroad/port sites migrated directly to DMR operation.


2. Mine sites converted to run in MPT-IP mode to allow implementation of a fully digital IP network infrastructure while allowing continued use of existing mobiles and portables.

3. Mine sites switched to DMR operation once mobiles and portables are replaced with DMR/MPT dual mode capable models.

These proposed phases are based on Tait’s current knowledge of the existing system and Cerrejon’s operational needs. The migration workshops may result in variations on these steps.

Figure 1 - Current System


Stage 1 - Railroad/port sites migrated directly to DMR operation1. This first stage will upgrade the sites associated with the Cerrejon’s railroad and port operations to DMR

mode and use the Tait TN9500 Inter-Network Gateway (ING) to connect the new DMR sites and DMR nodes to the existing MPT Classic system. The main steps involved are;

1. Mobile and portables associated with the railroad and port operations will be replaced with dual mode MPT/DMR capable units – TM9300 series mobiles and TP9300 series portables.

2. The TN9500 will be installed at the current MPT Classic node location. The MPT Classic nodes will have the most recent software installed to ensure compatibility with the TN9500 ING. The TN9500 Inter-Network Gateway has been designed by Tait to provide a smooth path for system migration to DMR with minimal impact on system availability.

3. A pair of TN9300 DMR Tier 3 node controllers will be installed, operating in High Availability (HA) mode and interfaced with the TN9500 ING.

Figure 2 - Start of Stage 1

4. The IP network links between the radio sites and the DMR node controllers will be checked to ensure that they can support the TB9300 base stations.


5. Tait will use upgrade kits for upgrading existing Tait TB8100 series base stations to DMR capable TB9300 capable base stations. Channels which are running the earlier T800 base stations will be replaced with complete TB9300 base stations. The TB9300 base stations are interfaced with the DMR node controllers over the IP network links. If all Cerrejon’s railroad and port operations users are equipped with MPT/DMR capable mobiles and portables then all channels at a site can be converted to DMR operation in one site visit. If not all users have MPT/DMR capable mobiles and portables then a subset of channels may be converted to DMR so that there will be effectively two smaller sites at the same location; one providing DMR operation, and the other MPT operation. In either case the TN93500 Inter-Network Gateway allows intercommunication between the MPT and DMR radio users. The TM9300 series mobiles and TP9300 series portables automatically switch to DMR operation when a DMR site is available. No user input is required and radio operation is identical to the user.

Figure 3 - Stage 1 first site converted to DMR


Figure 4 - Stage 1 complete

Stage 2 - Mine sites converted to run in MPT-IP modeThe second major phase will upgrade the sites associated with the actual mine operations to MPT-IP operation, using the TN9500 to connect the new MPT-IP sites and MPT-IP nodes to the existing MPT Classic system. MPT-IP is a Tait system which supports the MPT1327 over-air protocols but has digital linking capability using IP networks. The TN9500 allows calls to be made between the MPT Classic, MPT-IP and DMR parts of the system. The main steps involved are:

1. A pair of TN8291 MPT-IP node controllers will be installed, operating in High Availability (HA) mode and interfaced with the TN9500 ING.


Figure 5 - Stage 2 MPT-IP High availability nodes installed.

2. The IP network links between the mine radio sites and the MPT-IP node controllers will be checked to ensure that they can support the TB9300 base stations.

3. Tait will use upgrade kits for upgrading existing Tait TB8100 series base stations to DMR capable TB9300 capable base stations which are also capable of running in MPT-IP mode. Channels which are running the earlier T800 base stations will be replaced with complete TB9300 base stations. The TB9300 base stations are interfaced with the MPT-IP node controllers over the IP network links. All channels at a site can be converted to DMR operation in one site visit. Alternatively a subset of channels may be converted which will result in two smaller sites at the same location each providing MPT operation but supported by different node controllers. In either case the TN93500 Inter-Network Gateway allows intercommunication between the MPT, MPT-IP and DMR radio users.


Figure 6 - Stage 2 first site converted to MPT-IP


Figure 7 - Stage 2 complete


Stage 3 - Mine sites switched to DMR operationThe final stage, once the mobiles and portables have all been replaced by MPT/DMR capable mobiles and portables, will be to switch the MPT-IP sites to DMR. The main steps involved are;

1. Configure new DMR sites and channels on the DMR node controller.

2. Using remote access, switch the TB9300 base stations at a site from an MPT-IP channel to a DMR channel. The base stations will then operate in DMR mode, connected to the DMR node controller. No site visit is required. If not all users have MPT/DMR capable mobiles and portables then a subset of channels may be converted to DMR so that there will be effectively two smaller sites at the same location one providing DMR operation and the other MPT operation. In any case the TN93500 Inter-Network Gateway allows intercommunication between the MPT and DMR radio users.

3. MPT-IP nodes can be converted to DMR operation, increasing the redundancy of the system infrastructure.

Figure 8 Stage 3 First site switched to DMR mode


Figure 9 Stage 3 complete - All sites DMR

2.6.7 System Commissioning

As each phase of the deployment work is completed, a Tait Engineer will coordinate and manage the commissioning of that part of the system.

2.6.8 System Acceptance Testing

Once the migration is fully completed, a System Acceptance Test (SAT) will be conducted with Cerrejon witnesses to confirm that the system meets the agreed requirements.

2.7 CHANGE MANAGEMENTAlthough Tait has a smooth and very low impact migration path, it is inevitable that some change will be experienced by the end users. A new generation of radio terminals will need to be deployed, and while they have a very similar look and feel to the existing radios, there will be some changes to menu structure and functionality. Also, there are some subjective changes associated with the change from an analog to a digital system – sometimes voices can sound different, and the audio performance at the edges of coverage is quite different.

The level of adoption of these changes is dependent on the effectiveness of the human change management program that is applied during the migration. It is understood that Cerrejon wish to use the new system to help drive some culture change through the company, and to instigate more effective management of the front line


staff. A well-structured change management programme is recommended to help improve the adoption of the new system and the organisational changes desired. Tait recommends involving the operational management and end user community throughout the migration programme, and ensuring that there is an effective communication and training programme implemented in conjunction with the migration. Tait will bring to bear a proven change management program which engages change management agents from the Cerrejon staff to evaluate the ongoing success of critical deliverables of the implementation plan.

2.8 MONITORING AND SUPPORT

Network Monitoring - TaitWatch:

Tait will use our TaitWatch service to monitor the network throughout the transition period to ensure that the migration progresses smoothly. TaitWatch is a service to monitor our clients’ radio networks on a 24x7 basis. A permanent secure connection will need to be established between the Cerrejon radio network and the Tait Service Management Centre (SMC) to enable the TaitWatch service.

Once connectivity is established, Tait will monitor the Cerrejon network using our best in class network management tools. If an alarm is received or some other incident is detected, we will notify an agreed set of contacts and log the incident. It will be the responsibility of the Cerrejon L1 support team to resolve the incident and notify Tait when it is resolved. Tait will log the resolution details of the incident. Tait will provide regular reports on events received and incidents raised by the SMC.

Performance Management

Tait will use its purpose-built performance management tools to track the traffic load on each part of the network and check that overall performance is being achieved on both the MPT and DMR networks. Tait will use the traffic loading and performance reports to recommend timely capacity rebalancing that reflects the change in network usage as users migrate across to DMR.

Support – Service Advantage

Tait will provide is Service Advantage support service to provide support for the Cerrejon networks throughout and beyond the migration process. Service Advantage is complementary to the TaitWatch service, and provides support for any incidents and problems that are escalated by the L1 Support team. Service Advantage also includes the following services:

Extended warranty Access to software updates and upgrades Access to the customer portal, including technical documentation. Support for Service Requests


3. RESPONSIBILITIES OF CERREJONThe success of the migration project is dependent upon the engagement and support of Cerrejon and its nominated partners. To ensure alignment of expectations, it is important that our expectations of the functions of these levels are outlined. This will help to ensure the effective delivery of support service by Tait. The following sections outline our expectations of Cerrejon.

Prepare for and engage fully in the consultation workshop described in section 2.3.1.

Engage and support the Change Management programme described in section 2.7.

Participate fully in the training programs provided by Tait, including the joint development of end user training material, and the provision of trainers for the end users.

Provide Level 1 support as described in section 3.1 below.

Provide full time remote monitoring and management access to the network as described in section 3.2 below.

3.1 LEVEL 1 SUPPORTIt is assumed that Cerrejon will continue to use their existing L1 support team for local support. L1 support will include the following services:

Stocking, configuration and management of critical spares to support Incident restoration as required to meet Cerrejon’s service level expectations.

Site visits to investigate, repair or replace faulty radio terminals and network equipment, including antenna systems, power supplies and backhaul linking equipment.

Site visits to upgrade software or make configuration changes to DMR terminals if for some reason OTAP is not possible.

Provide on-the-ground support for L2 and L3 investigation into problems when necessary. (E.g. investigation of interference issues, intermittent performance problems etc)

It is important that the L1 support team is adequately trained on DMR, the TN9500 gateway, and the migration and the migration process. Tait will provide training as part of this migration service to ensure that the L1 support team are prepared to provide local support. These are outlined in section Error: Reference source not found later in this document.

It is also important that the L1 support team have access to the appropriate test equipment. While Tait can provide advice on suitable test equipment, the provision of test equipment is considered outside the scope of this proposal.

It is expected that the L1 support team will handle the simple incidents and problems that are typically encountered with DMR systems, and will only escalate to L2 when their knowledge and capability is exhausted.

3.2 REMOTE ACCESSA mandatory requirement for monitoring and providing support to Cerrejon is the provision of reliable and responsive remote access to the network, to enable Tait Support staff to diagnose incidents and problems, and upgrade software. Tait recognizes the importance of robust information security and has attained ISO27001 certification for its Managed Service operation. Tait can work with Cerrejon to standardize an architecture and


access mechanism that meets Cerrejon’s information security requirements, and that can be put in place before the system is commissioned. The remote access must be fully operational before the system is transitioned to Support.


4. APPENDIX ONE- TERMS AND ABBREVIATIONS

Term Definition

L1 Support Direct local support and maintenance, such as equipment replacement, and on-site investigation, diagnosis and configuration work. L1 support is typically provided by the end customer or nominated local maintenance contractors.

L2 Support In-region support, provided by knowledgeable people who can provide a local Service Desk facility and act as a point of escalation to L1 support. In region support is typically provided by people with local language skills and good system knowledge. L2 support staff can provide information and guide L1 support staff for the resolution of the majority of incidents and problems.

L3 Support L3 Support is typically centralised and provided by specialists who have deep system knowledge and experience. L3 support can provide a point of escalation to L2 support staff, and guide the investigation and resolution of more complex incidents and problems, escalating to L4 if necessary.

L4 Support L4 support is provided by design staff who have developed the products and systems, and who can investigate the most challenging problems and make design changes if necessary.

ITIL Information Technology Infrastructure Library. A framework and body of knowledge of best practices as it applied to IT service management, which has been widely adopted across the world by IT service organisations.

Case Type DescriptionIncident An incident is any event which is not part of the standard operation of the System and

which causes, or may cause, an interruption or a reduction of the quality of the service provided by the System

Problem A condition often identified as a result of single or multiple Incidents that exhibit common symptoms. Problems can also be identified from a single significant Incident, for which the cause is unknown, but which impacts service or Product availability. A workaround has been applied to an incident and further analysis is required to identify root cause.

Service Request A request from a Client for information or advice, or for a Standard change to the scope of the Support Services

Change Request A customer has requested a change to the configuration or architecture of the system.

Enhancement Request A request from a Client for a change to existing Product functionality

Priority DefinitionsPriority 1 (P1) Conditions exist that are likely to result in life threatening or hazardous or unsafe conditions

or severely affect service (>25%), monitoring/management capability and require sustained effort using all available resources until resolved. On-call procedures are activated, Supplier support is invoked. Or classified on mutual agreement

Priority 2 (P2) Conditions exist that are likely to result in hazardous or unsafe conditions or seriously reduces system operation (<25%) maintenance, usability and administration capability; or is likely to result in complete failure and requires immediate attention as viewed by the client. Or classified by mutual agreement


Priority 3 (P3) Conditions that do not significantly impair the functions of the system and do not significantly affect service to customers. These problems are not traffic impairing or service impacting. Or classified by mutual agreement

Priority 4 (P4) There is a minor issue or an opportunity for product improvement. This issue does not affect the core functionalities or management of the system or making of calls on a network. Or classified by mutual agreement

Service Standard DefinitionsNotification Notifying an agreed set of people on an incident by an agreed communication method.

Nature of incident and initial assessment of the possible cause, impact and priority will be included in the notification.

Response Time Response is defined as the commencement of restoration or resolution activity, which may include assignment of the incident to an appropriate 3rd party resolver group.

Incident Restoration Time

Restoration is defined as resolution of service, or an otherwise satisfactory workaround that resolves the initial incident. Target resolution time is the time in which Tait expects to successfully resolve the incident.


migration strategy - traduções juramentadas tradução ... web viewthis...

Documents