top of page

Enterprise Architecture & Roadmap for Service Providers

From legacy to target architecture according to eTOM-model

  • IT Business Alignment

  • Vendor selection

  • Best of Breed vs Custom Build

  • Migration Plan Analyses (from Current Architecture to Target Architecture)

Enterprise architecture (EA) is a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy.

Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes.


The benefits of enterprise architecture are achieved through its direct and indirect contributions to organizational goals. It has been found that the most notable benefits of enterprise architecture can be observed in the following areas:

  • Organizational design – Enterprise architecture provides support in the areas related to design and re-design of the organizational structures during mergers, acquisitions or during general organizational change.

  • Organizational processes and process standards – Enterprise architecture helps enforce discipline and standardization of business processes, and enable process consolidation, reuse, and integration.

  • Project portfolio management- Enterprise architecture supports investment decision-making and work prioritization.

  • Project management – Enterprise architecture enhances the collaboration and communication between project stakeholders. Enterprise architecture contributes to efficient project scoping, and to defining more complete and consistent project deliverables.

  • Requirements Engineering- Enterprise architecture increases the speed of requirement elicitation and the accuracy of requirement definitions, through publishing of the enterprise architecture documentation.

  • System development – Enterprise architecture contributes to optimal system designs and efficient resource allocation during system development and testing.

  • IT management and decision making – Enterprise architecture is found to help enforce discipline and standardization of IT planning activities and to contribute to a reduction in time for technology-related decision making.

  • IT value – Enterprise architecture helps reduce the system’s implementation and operational costs, and minimize replication of IT infrastructure services across business units.

  • IT complexity – Enterprise architecture contributes to a reduction in IT complexity, consolidation of data and applications, and to better interoperability of the systems.

  • IT openness – Enterprise architecture contributes to more open and responsive IT as reflected through increased accessibility of data for regulatory compliance, and increased transparency of infrastructure changes.

  •  IT risk management – Enterprise architecture contributes to the reduction of business risks from system failures and security breaches. Enterprise architecture helps reduce risks of project delivery.

The total approach includes 2 phases, A and B:

Phase A – Current- & Target Systems Architectures

  • Determine the scope, strategy and business targets – via management interviews;

  • Determine via electronic inputs (in advance) and interviews the current situation – processes, systems, functionalities and PIE (Problems, Issues, Expectations);

  • Establish the current business & IT BSS-OSS architecture;

  • Collect high-level Business & IT requirements for the desired situation;

  • Establish the Target BSS-OSS Architecture, including relevant Best Practices recommendations;

  • Highlight & Analyze Gap between current and target architectures.

Phase B – Transition to Target Architecture

  • Transition Plan – a 3 year-plans, in 6 parts of 6 months each, containing roadmap of projects in order to transit UTS-IT from current to target situation, incl. priorities, constraints, sequence, etc.

  • For each new / upgraded system: RFI, Determine solutions requirements, RFP, Procurement, Implementation and migrations.

The Target Architecture will cover the domains (in eTOM level 1 terminology): CRM, Fulfillment, Operations Support & Readiness (OSR), Assurance, Billing & Revenue Management, and (Telecom specific) Enterprise.

  • LinkedIn
bottom of page