|
1 Addressing the Transformational Needs of Telecommunications Operators |
|
|
1 | (16) |
|
1.1 What Is the Structure of This Book? |
|
|
2 | (1) |
|
1.2 What Are the Major Findings of This Book? |
|
|
3 | (6) |
|
1.3 Which Sources Were Used? |
|
|
9 | (2) |
|
1.4 Who Could Benefit from This Book? |
|
|
11 | (1) |
|
1.5 How Is the Content Used in Real-Life Projects? |
|
|
12 | (5) |
|
|
13 | (4) |
|
2 Understanding Today's Telecommunications Industry |
|
|
17 | (38) |
|
2.1 Telecommunications Market |
|
|
20 | (19) |
|
2.1.1 Price Decrease and Cost Pressure |
|
|
21 | (3) |
|
2.1.2 Emergence of Over-the-Top (OTT) Providers |
|
|
24 | (3) |
|
2.1.3 Growth Potential in Vertical Markets |
|
|
27 | (8) |
|
2.1.4 A New Role for Regulators |
|
|
35 | (4) |
|
2.2 Telecommunications Products and Services |
|
|
39 | (5) |
|
2.2.1 Interrelation Between Commercial Products and Technical Services |
|
|
39 | (3) |
|
2.2.2 Customer Experience Management |
|
|
42 | (2) |
|
2.3 Telecommunications Value Chain |
|
|
44 | (11) |
|
2.3.1 Erosion of the Traditional Telecommunications Value Chain |
|
|
45 | (2) |
|
2.3.2 The Operator Partnering Imperative |
|
|
47 | (3) |
|
|
50 | (5) |
|
3 Understanding the Methodical Principles |
|
|
55 | (48) |
|
3.1 Fundamentals of Information Systems Modeling |
|
|
57 | (3) |
|
3.2 Enterprise Architecture |
|
|
60 | (10) |
|
3.2.1 Introduction to Enterprise Architecture |
|
|
61 | (2) |
|
3.2.2 Enterprise Architecture Frameworks |
|
|
63 | (4) |
|
3.2.3 Enterprise Architecture Management |
|
|
67 | (1) |
|
3.2.4 The Open Group Architecture Framework |
|
|
68 | (2) |
|
|
70 | (8) |
|
3.3.1 Introduction to Reference Modeling |
|
|
71 | (1) |
|
3.3.2 Types of Reference Models |
|
|
72 | (2) |
|
3.3.3 Development and Usage of Reference Models |
|
|
74 | (4) |
|
3.4 Reference Models in the Telecommunications Industry |
|
|
78 | (14) |
|
3.4.1 TM Forum Business Process Framework (eTOM) |
|
|
80 | (5) |
|
3.4.2 TM Forum Information Framework (SID) |
|
|
85 | (3) |
|
3.4.3 TM Forum Application Framework (TAM) |
|
|
88 | (3) |
|
3.4.4 IT Infrastructure Library (ITIL) |
|
|
91 | (1) |
|
3.5 Introduction to Enterprise Transformation |
|
|
92 | (11) |
|
|
95 | (8) |
|
4 Designing the Architecture Solution |
|
|
103 | (100) |
|
4.1 Overview of Reference Architecture |
|
|
105 | (18) |
|
4.1.1 Layers of Reference Architecture |
|
|
107 | (8) |
|
4.1.2 Defining Architecture Domains |
|
|
115 | (4) |
|
4.1.3 Defining Reference Process Flows |
|
|
119 | (4) |
|
4.2 Structuring the Architecture Solution |
|
|
123 | (18) |
|
4.2.1 Structuring the Process Layer |
|
|
125 | (4) |
|
4.2.2 Structuring the Organizational Mapping |
|
|
129 | (5) |
|
4.2.3 Structuring the Data Layer |
|
|
134 | (3) |
|
4.2.4 Structuring the Application Layer |
|
|
137 | (4) |
|
4.3 Detailing the Customer-Centric Domain |
|
|
141 | (20) |
|
4.3.1 Reference Process Flows of the Customer-Centric Domain |
|
|
141 | (4) |
|
4.3.2 Organizational Mapping of the Customer-Centric Domain |
|
|
145 | (8) |
|
4.3.3 Data Layer of the Customer-Centric Domain |
|
|
153 | (2) |
|
4.3.4 Application Layer of the Customer-Centric Domain |
|
|
155 | (5) |
|
4.3.5 Summary of the Customer-Centric Domain |
|
|
160 | (1) |
|
4.4 Detailing the Technology Domain |
|
|
161 | (23) |
|
4.4.1 Reference Process Flows of the Technology Domain |
|
|
162 | (4) |
|
4.4.2 Organizational Mapping of the Technology Domain |
|
|
166 | (8) |
|
4.4.3 Data Layer of the Technology Domain |
|
|
174 | (4) |
|
4.4.4 Application Layer of the Technology Domain |
|
|
178 | (4) |
|
4.4.5 Summary of the Technology Domain |
|
|
182 | (2) |
|
4.5 Detailing the Product Domain |
|
|
184 | (13) |
|
4.5.1 Reference Process Flows of the Product Domain |
|
|
184 | (2) |
|
4.5.2 Organizational Mapping of the Product Domain |
|
|
186 | (4) |
|
4.5.3 Data Layer of the Product Domain |
|
|
190 | (3) |
|
4.5.4 Application Layer of the Product Domain |
|
|
193 | (2) |
|
4.5.5 Summary of the Product Domain |
|
|
195 | (2) |
|
4.6 Detailing the Customer Domain and the Support Domain |
|
|
197 | (6) |
|
4.6.1 Reference Process Flows of the Customer Domain |
|
|
197 | (1) |
|
4.6.2 Reference Process Flows of the Support Domain |
|
|
198 | (1) |
|
|
199 | (4) |
|
5 Planning and Implementing the Architecture Solution |
|
|
203 | (46) |
|
5.1 Architecture Solution Map |
|
|
205 | (21) |
|
5.1.1 Map Element 1: Architecture Diagnostics |
|
|
209 | (3) |
|
5.1.2 Map Element 2: Strategic Alignment |
|
|
212 | (2) |
|
5.1.3 Map Element 3: Architecture Framework |
|
|
214 | (2) |
|
5.1.4 Map Element 4: Architecture Ownership |
|
|
216 | (2) |
|
5.1.5 Map Element 5: Architecture Design |
|
|
218 | (2) |
|
5.1.6 Map Element 6: Training and Awareness |
|
|
220 | (2) |
|
5.1.7 Map Element 7: Change Management |
|
|
222 | (1) |
|
5.1.8 Map Element 8: Architecture Implementation |
|
|
223 | (3) |
|
5.2 Transformation Types and Organizational Responsibility |
|
|
226 | (5) |
|
5.3 Transformation Project Examples |
|
|
231 | (7) |
|
5.4 Detailed Example Cases |
|
|
238 | (11) |
|
5.4.1 Case Study 1---Introduction of an OSS (Customer Orientation) |
|
|
238 | (3) |
|
5.4.2 Case Study 2---Introduction of an OSS (NGN-Based) |
|
|
241 | (2) |
|
5.4.3 Case Study 3---Introduction of a CRM System |
|
|
243 | (2) |
|
5.4.4 Case Study 4---Introduction of Process Architecture |
|
|
245 | (2) |
|
|
247 | (2) |
Index |
|
249 | |