websiteADMINFADLIWIRYA

Channel Listings for Kansas City All channels available in HD unless otherwise noted. SD Channel available in SD only ES Spanish language channel Sports Package◊ ESPN ClassicSD 212 ESPN Goal Line/ 220 Bases Loaded* FOX College Sports Atlantic*SD 226 FOX College Sports Central*SD 227 FOX College Sports Pacific*SD 228 FOX Soccer Plus* 225 FOX Sports Arizona* 266 FOX Sports Detroit* 265 FOX Sports Florida* 260 FOX Sports Ohio* 264 FOX Sports San Diego* 271 FOX Sports South* 262 FOX Sports Southeast* 263 FOX Sports Southwest* 268 FOX Sports Sun* 261 FOX Sports West* 269 FOX Sports Wisconsin* 273 GolTV English*SD 243 Havoc* 246 Longhorn Network* 230 MavTV* 275 MLB Network Strike Zone* 218 NFL RedZone* 223 Outside TV* 255 Outdoor Channel* 413 PAC-12 Arizona* 236 PAC-12 Bay Area* 232 PAC-12 Los Angeles* 233 PAC-12 Mountain* 237 PAC-12 Network* 231 PAC-12 Oregon* 234 PAC-12 Washington* 235 Prime Ticket* 270 Ride TV* 245 Sportsman Channel* 415 TVG2*SD 259 TVG Network* 258 Willow Cricket* 244 World Fishing Network* 256 YES Network* 272 STARZ IndiePlex East* 565 IndiePlex West* 566 MoviePlex East* 563 MoviePlex West* 564 RetroPlex East* 567 RetroPlex West* 568 Starz East* 535 Starz West* 536 Starz Cinema East* 537 Starz Cinema West* 538 Starz Comedy East* 539 Starz Comedy West* 540 Starz Edge East* 541 Starz Edge West* 542 Starz Encore East* 547 Starz Encore West* 548 Starz Encore Action East* 549 Starz Encore Action West* 550 Starz Encore Black East* 551 Starz Encore Black West* 552 Starz Encore Classic East* 557 Starz Encore Classic West* 558 Starz Encore Espanol 553 East* ES Starz Encore Espanol 554 West* ES Starz Encore Family East* 555 Starz Encore Family West* 556 Starz Encore Suspense 559 East* Starz Encore Suspense 560 West* Starz Encore Westerns 561 East* Starz Encore Westerns 562 West* Starz in Black East* 543 Starz in Black West* 544 Starz Kids & Family 545 East* Starz Kids & Family 546 West* Cinemax 5-StarMax East* 594 ActionMax East* 588 ActionMax West* 589 Cinemáx East* ES 593 Max East* 584 Max West* 585 MoreMax East* 586 MoreMax West* 587 MovieMAX* 592 OuterMax East* 595 ThrillerMax East* 590 ThrillerMax West* 591 Family Package Aspire* 435 Baby First* 433 BabyTV* 432 DuckTV 437 FidoTV* 436 Game Show Network (GSN) 352 Showtime East 510 Showtime West 511 Showtime Family East* 518 Showtime Family West* 519 UP* 434 UP Faith & Family* VOD HBO HBO East* 570 HBO West* 571 HBO2 East* 572 HBO2 West* 573 HBO Comedy East* 580 HBO Comedy West* 581 HBO Family East* 576 HBO Family West* 577 HBO Latino East* ES 578 HBO Latino West* ES 579 HBO Signature East* 574 HBO Signature West* 575 HBO Zone East* 582 HBO Zone West* 583 Latino Package Bandamax*SD ES 490 De Pelicula*SD ES 484 De Pelicula Clasico*SD ES 485 FOROtv*SD ES 463 FOX LifeSD ES 464 GolTV Espanol* ES 471 History en Espanol*SD ES 475 Nat Geo MundoSD ES 473 Telehit Urbano* SD ES 491 Telehit* ES 492 Univision tlnovelas*SD ES 493 Movies Package Flix East* 530 Flix West* 531 IndiePlex* 565 MGM* 601 MoviePlex* 563 Reelzchannel* 605 RetroPlex* 567 Shorts* 603 Sony Movie Channel* 600 UP Faith & Family* VOD SHOWTIME Flix East* 530 Flix West* 531 SHO2 East* 524 SHO2 West* 525 Showcase East* 512 Showcase West* 513 Showtime Beyond East* 514 Showtime Beyond West* 515 Showtime East* 510 Showtime Extreme East* 516 Showtime Extreme West* 517 Showtime Family East* 518 Showtime Family West* 519 Showtime Next East* 520 Showtime Next West* 521 Showtime West* 511 Showtime Women East* 522 Showtime Women West* 523 The Movie Channel East* 526 The Movie Channel Extra 527 East* The Movie Channel Extra 528 West* The Movie Channel West* 529

websiteIOADMIN Mei 21, 2020 Admin Bandung Indonesia

CHANNEL TV GOOGLE REGIST

Dive Into DESIGN PATTERNS v2020-2.14 DEMO VERSION Buy the full book: https://refactoring.guru/design-patterns/book A Few Words on Copyright Hi! My name is Alexander Shvets. I’m the author of the book Dive Into Design Patterns and the online course Dive Into Refactoring. This book is for your personal use only. Please don’t share it with any third parties except your family members. If you’d like to share the book with a friend or colleague, buy and send them a new copy. All profit from the sale of my books and courses is spent on the development of Refactoring.Guru. Each copy sold helps the project immensely and brings the moment of a new book release a little bit closer.  Alexander Shvets, Refactoring.Guru, 2019  support@refactoring.guru  Illustrations: Dmitry Zhart  Editing: Andrew Wetmore, Rhyan Solomon I dedicate this book to my wife, Maria. If it hadn’t been for her, I’d probably have finished the book some 30 years later. Table of Contents Table of Table of Contents How to Read This Book This book contains the descriptions of 22 classic design patterns formulated by the “Gang of Four” (or simply GoF) in 1994.

INDONESIAN : Menyelam POLA DESAIN v2020-2.14 DEMO VERSION Beli buku lengkapnya: https://refactoring.guru/design-patterns/book A Sedikit Kata-kata tentang Hak Cipta Hai! Nama saya Alexander Shvets. Saya penulis buku Dive Into Design Patterns dan kursus online Dive Into Refactoring. Buku ini hanya untuk penggunaan pribadi Anda. Tolong jangan membagikannya dengan pihak ketiga mana pun kecuali anggota keluarga Anda. Jika Anda ingin berbagi buku dengan teman atau kolega, beli dan kirimkan salinan baru kepada mereka. Semua keuntungan dari penjualan buku dan kursus saya dihabiskan untuk pengembangan Refactoring.Guru. Setiap salinan yang terjual sangat membantu proyek dan membawa momen peluncuran buku baru sedikit lebih dekat.  Alexander Shvets, Refactoring.Guru, 2019  support@refactoring.guru  Ilustrasi: Dmitry Zhart  Editing: Andrew Wetmore, Rhyan Solomon Saya mempersembahkan buku ini untuk istri saya, Maria. Jika bukan karena dia, saya mungkin telah menyelesaikan buku itu sekitar 30 tahun kemudian. Daftar Isi Daftar Isi Cara Membaca Buku Ini Buku ini berisi deskripsi 22 pola desain klasik yang dirumuskan oleh "Gang Empat" (atau sekadar GoF) pada tahun 1994.

Each chapter explores a particular pattern. Therefore, you can read from cover to cover or by picking the patterns you’re interested in. Many patterns are related, so you can easily jump from topic to topic using numerous anchors. The end of each chapter has a list of links between the current pattern and others. If you see the name of a pattern that you haven’t seen yet, just keep reading—this item will appear in one of the next chapters. Design patterns are universal. Therefore, all code samples in this book are written in pseudocode that doesn’t constrain the material to a particular programming language. Prior to studying patterns, you can refresh your memory by going over the key terms of object-oriented programming. That chapter also explains the basics of UML diagrams, which is useful because the book has tons of them. Of course, if you already know all of that, you can proceed to learning patterns right away. 6 How to read this book INTRODUCTION TO OOP Basics of OOP Object-oriented programming is a paradigm based on the concept of wrapping pieces of data, and behavior related to that data, into special bundles called objects, which are constructed from a set of “blueprints”, defined by a programmer, called classes. Objects, classes Do you like cats? I hope you do because I’ll try to explain the OOP concepts using various cat examples. This is a UML class diagram. You’ll see a lot of such diagrams in the book. 8 Introduction to OOP / Basics of OOP Say you have a cat named Oscar. Oscar is an object, an instance of the Cat class. Every cat has a lot of standard attributes: name, sex, age, weight, color, favorite food, etc. These are the class’s fields. All cats also behave similarly: they breathe, eat, run, sleep and meow. These are the class’s methods. Collectively, fields and methods can be referenced as the members of their class. Data stored inside the object’s fields is often referenced as state, and all the object’s methods define its behavior. Objects are instances of classes. 9 Introduction to OOP / Basics of OOP Luna, your friend’s cat, is also an instance of the Cat class. It has the same set of attributes as Oscar. The difference is in values of these attributes: its sex is female, it has a different color, and weighs less. So a class is like a blueprint that defines the structure for objects, which are concrete instances of that class. Class hierarchies Everything fine and dandy when we talk about one class. Naturally, a real program contains more than a single class. Some of these classes might be organized into class hierarchies. Let’s find out what that means. Say your neighbor has a dog called Fido. It turns out, dogs and cats have a lot in common: name, sex, age, and color are attributes of both dogs and cats. Dogs can breathe, sleep and run the same way cats do. So it seems that we can define the base Animal class that would list the common attributes and behaviors. A parent class, like the one we’ve just defined, is called a superclass. Its children are subclasses. Subclasses inherit state and behavior from their parent, defining only attributes or behaviors that differ. Thus, the Cat class would have the meow method, and the Dog class the bark method. 10 Introduction to OOP / Basics of OOP UML diagram of a class hierarchy. All classes in this diagram are part of the Animal class hierarchy. Assuming that we have a related business requirement, we can go even further and extract a more general class for all living Organisms which will become a superclass for Animals and Plants . Such a pyramid of classes is a hierarchy. In such a hierarchy, the Cat class inherits everything from both the Animal and Organism classes. 11 Introduction to OOP / Basics of OOP Classes in a UML diagram can be simplified if it’s more important to show their relations than their contents. Subclasses can override the behavior of methods that they inherit from parent classes. A subclass can either completely replace the default behavior or just enhance it with some extra stuff. 12 Introduction to OOP / Basics of OOP 19 page from the full book are omitted in the demo version SOFTWARE DESIGN PRINCIPLES Features of Good Design Before we proceed to the actual patterns, let’s discuss the process of designing software architecture: things to aim for and things you’d better avoid. Code reuse Cost and time are two of the most valuable metrics when developing any software product. Less time in development means entering the market earlier than competitors. Lower development costs mean more money is left for marketing and a broader reach to potential customers. Code reuse is one of the most common ways to reduce development costs. The intent is pretty obvious: instead of developing something over and over from scratch, why don’t we reuse existing code in new projects? The idea looks great on paper, but it turns out that making existing code work in a new context usually takes extra effort. Tight coupling between components, dependencies on concrete classes instead of interfaces, hardcoded operations—all of this reduces flexibility of the code and makes it harder to reuse it. Using design patterns is one way to increase flexibility of software components and make them easier to reuse. However,  33 Features of Good Design this sometimes comes at the price of making the components more complicated. Here’s a piece of wisdom from Erich Gamma 1 , one of the founding fathers of design patterns, about the role of design patterns in code reuse: I see three levels of reuse. At the lowest level, you reuse classes: class libraries, containers, maybe some class “teams” like container/iterator. Frameworks are at the highest level. They really try to distill your design decisions. They identify the key abstractions for solving a problem, represent them by classes and define relationships between them. JUnit is a small framework, for example. It is the “Hello, world” of frameworks. It has Test , TestCase , TestSuite and relationships defined. A framework is typically larger-grained than just a single class. Also, you hook into frameworks by subclassing somewhere. They use the so-called Hollywood principle of “don’t call us, we’ll call you.” The framework lets you define your custom behavior, and it will call you when it’s your turn to do something. Same with JUnit, right? It calls you when it wants to execute a test for you, but the rest happens in the framework. There also is a middle level. This is where I see patterns. Design patterns are both smaller and more abstract than “ 1. Erich Gamma on Flexibility and Reuse: https://refactoring.guru/ gamma-interview 34 Features of Good Design / Code reuse Extensibility Change is the only constant thing in a programmer’s life. • You released a video game for Windows, but now people ask for a macOS version. • You created a GUI framework with square buttons, but several months later round buttons become a trend. • You designed a brilliant e-commerce website architecture, but just a month later customers ask for a feature that would let them accept phone orders. Each software developer has dozens of similar stories. There are several reasons why this happens. First, we understand the problem better once we start to solve it. Often by the time you finish the first version of an app, frameworks. They’re really a description about how a couple of classes can relate to and interact with each other. The level of reuse increases when you move from classes to patterns and finally frameworks. What is nice about this middle layer is that patterns offer reuse in a way that is less risky than frameworks. Building a framework is high-risk and a significant investment. Patterns let you reuse design ideas and concepts independently of concrete code. „  35 Features of Good Design / Extensibility you’re ready to rewrite it from scratch because now you understand many aspects of the problem much better. You have also grown professionally, and your own code now looks like crap. Something beyond your control has changed. This is why so many dev teams pivot from their original ideas into something new. Everyone who relied on Flash in an online application has been reworking or migrating their code as browser after browser drops support for Flash. The third reason is that the goalposts move. Your client was delighted with the current version of the application, but now sees eleven “little” changes he’d like so it can do other things he never mentioned in the original planning sessions. These aren’t frivolous changes: your excellent first version has shown him that even more is possible. There’s a bright side: if someone asks you to change something in your app, that means someone still cares about it. That’s why all seasoned developers try to provide for possible future changes when designing an application’s architecture. 36 Features of Good Design / Extensibility Design Principles What is good software design? How would you measure it? What practices would you need to follow to achieve it? How can you make your architecture flexible, stable and easy to understand? These are the great questions; but, unfortunately, the answers are different depending on the type of application you’re building. Nevertheless, there are several universal principles of software design that might help you answer these questions for your own project. Most of the design patterns listed in this book are based on these principles. 37 Design Principles Encapsulate What Varies Identify the aspects of your application that vary and separate them from what stays the same. The main goal of this principle is to minimize the effect caused by changes. Imagine that your program is a ship, and changes are hideous mines that linger under water. Struck by the mine, the ship sinks. Knowing this, you can divide the ship’s hull into independent compartments that can be safely sealed to limit damage to a single compartment. Now, if the ship hits a mine, the ship as a whole remains afloat. In the same way, you can isolate the parts of the program that vary in independent modules, protecting the rest of the code from adverse effects. As a result, you spend less time getting the program back into working shape, implementing and testing the changes. The less time you spend making changes, the more time you have for implementing features. 38 Design Principles / Encapsulate What Varies Encapsulation on a method level Say you’re making an e-commerce website. Somewhere in your code, there’s a getOrderTotal method that calculates a grand total for the order, including taxes. We can anticipate that tax-related code might need to change in the future. The tax rate depends on the country, state or even city where the customer resides, and the actual formula may change over time due to new laws or regulations. As a result, you’ll need to change the getOrderTotal method quite often. But even the method’s name suggests that it doesn’t care about how the tax is calculated. BEFORE: tax calculation code is mixed with the rest of the method’s code. You can extract the tax calculation logic into a separate method, hiding it from the original method. 1 method getOrderTotal(order) is 2 total = 0 3 foreach item in order.lineItems 4 total += item.price * item.quantity 5 6 if (order.country == "US") 7 total += total * 0.07 // US sales tax 8 else if (order.country == "EU"): 9 total += total * 0.20 // European VAT 10 11 return total 39 Design Principles / Encapsulate What Varies AFTER: you can get the tax rate by calling a designated method. Tax-related changes become isolated inside a single method. Moreover, if the tax calculation logic becomes too complicated, it’s now easier to move it to a separate class. Encapsulation on a class level Over time you might add more and more responsibilities to a method which used to do a simple thing. These added behaviors often come with their own helper fields and methods that eventually blur the primary responsibility of the containing class. Extracting everything to a new class might make things much more clear and simple. 1 method getOrderTotal(order) is 2 total = 0 3 foreach item in order.lineItems 4 total += item.price * item.quantity 5 6 total += total * getTaxRate(order.country) 7 8 return total 9 10 method getTaxRate(country) is 11 if (country == "US") 12 return 0.07 // US sales tax 13 else if (country == "EU") 14 return 0.20 // European VAT 15 else 16 return 0 40 Design Principles / Encapsulate What Varies BEFORE: calculating tax in Order class. Objects of the Order class delegate all tax-related work to a special object that does just that. AFTER: tax calculation is hidden from the Order class. 41 Design Principles / Encapsulate What Varies 29 page from the full book are omitted in the demo version CATALOG OF DESIGN PATTERNS Creational Design Patterns Creational patterns provide various object creation mechanisms, which increase flexibility and reuse of existing code. Factory Method Provides an interface for creating objects in a superclass, but allows subclasses to alter the type of objects that will be created. Abstract Factory Lets you produce families of related objects without specifying their concrete classes. 72 Creational Design Patterns Builder Lets you construct complex objects step by step. The pattern allows you to produce different types and representations of an object using the same construction code. Prototype Lets you copy existing objects without making your code dependent on their classes. Singleton Lets you ensure that a class has only one instance, while providing a global access point to this instance. 73 Creational Design Patterns FACTORY METHOD Also known as: Virtual Constructor Factory Method is a creational design pattern that provides an interface for creating objects in a superclass, but allows subclasses to alter the type of objects that will be created. 74 Creational Design Patterns / Factory Method Problem Imagine that you’re creating a logistics management application. The first version of your app can only handle transportation by trucks, so the bulk of your code lives inside the Truck class. After a while, your app becomes pretty popular. Each day you receive dozens of requests from sea transportation companies to incorporate sea logistics into the app. Adding a new class to the program isn’t that simple if the rest of the code is already coupled to existing classes. Great news, right? But how about the code? At present, most of your code is coupled to the Truck class. Adding Ships into the app would require making changes to the entire codebase. Moreover, if later you decide to add another type of transportation to the app, you will probably need to make all of these changes again.  75 Creational Design Patterns / Factory Method As a result, you will end up with pretty nasty code, riddled with conditionals that switch the app’s behavior depending on the class of transportation objects. Solution The Factory Method pattern suggests that you replace direct object construction calls (using the new operator) with calls to a special factory method. Don’t worry: the objects are still created via the new operator, but it’s being called from within the factory method. Objects returned by a factory method are often referred to as “products.” Subclasses can alter the class of objects being returned by the factory method. At first glance, this change may look pointless: we just moved the constructor call from one part of the program to another. However, consider this: now you can override the factory method in a subclass and change the class of products being created by the method.  76 Creational Design Patterns / Factory Method There’s a slight limitation though: subclasses may return different types of products only if these products have a common base class or interface. Also, the factory method in the base class should have its return type declared as this interface. All products must follow the same interface. For example, both Truck and Ship classes should implement the Transport interface, which declares a method called deliver . Each class implements this method differently: trucks deliver cargo by land, ships deliver cargo by sea. The factory method in the RoadLogistics class returns truck objects, whereas the factory method in the SeaLogistics class returns ships. The code that uses the factory method (often called the client code) doesn’t see a difference between the actual products returned by various subclasses. The client treats all the products as abstract Transport . 77 Creational Design Patterns / Factory Method As long as all product classes implement a common interface, you can pass their objects to the client code without breaking it. The client knows that all transport objects are supposed to have the deliver method, but exactly how it works isn’t important to the client.  Structure 78 Creational Design Patterns / Factory Method 1. The Product declares the interface, which is common to all objects that can be produced by the creator and its subclasses. 2. Concrete Products are different implementations of the product interface. 3. The Creator class declares the factory method that returns new product objects. It’s important that the return type of this method matches the product interface. You can declare the factory method as abstract to force all subclasses to implement their own versions of the method. As an alternative, the base factory method can return some default product type. Note, despite its name, product creation is not the primary responsibility of the creator. Usually, the creator class already has some core business logic related to products. The factory method helps to decouple this logic from the concrete product classes. Here is an analogy: a large software development company can have a training department for programmers. However, the primary function of the company as a whole is still writing code, not producing programmers. 4. Concrete Creators override the base factory method so it returns a different type of product. 79 Creational Design Patterns / Factory Method Note that the factory method doesn’t have to create new instances all the time. It can also return existing objects from a cache, an object pool, or another source. Pseudocode This example illustrates how the Factory Method can be used for creating cross-platform UI elements without coupling the client code to concrete UI classes. The base dialog class uses different UI elements to render its window. Under various operating systems, these elements may look a little bit different, but they should still behave consistently. A button in Windows is still a button in Linux. The cross-platform dialog example.  80 Creational Design Patterns / Factory Method When the factory method comes into play, you don’t need to rewrite the logic of the dialog for each operating system. If we declare a factory method that produces buttons inside the base dialog class, we can later create a dialog subclass that returns Windows-styled buttons from the factory method. The subclass then inherits most of the dialog’s code from the base class, but, thanks to the factory method, can render Windowslooking buttons on the screen. For this pattern to work, the base dialog class must work with abstract buttons: a base class or an interface that all concrete buttons follow. This way the dialog’s code remains functional, whichever type of buttons it works with. Of course, you can apply this approach to other UI elements as well. However, with each new factory method you add to the dialog, you get closer to the Abstract Factory pattern. Fear not, we’ll talk about this pattern later. 1 // The creator class declares the factory method that must 2 // return an object of a product class. The creator's subclasses 3 // usually provide the implementation of this method. 4 class Dialog is 5 // The creator may also provide some default implementation 6 // of the factory method. 7 abstract method createButton():Button 8 9 // Note that, despite its name, the creator's primary 10 // responsibility isn't creating products. It usually 81 Creational Design Patterns / Factory Method 11 // contains some core business logic that relies on product 12 // objects returned by the factory method. Subclasses can 13 // indirectly change that business logic by overriding the 14 // factory method and returning a different type of product 15 // from it. 16 method render() is 17 // Call the factory method to create a product object. 18 Button okButton = createButton() 19 // Now use the product. 20 okButton.onClick(closeDialog) 21 okButton.render() 22 23 24 // Concrete creators override the factory method to change the 25 // resulting product's type. 26 class WindowsDialog extends Dialog is 27 method createButton():Button is 28 return new WindowsButton() 29 30 class WebDialog extends Dialog is 31 method createButton():Button is 32 return new HTMLButton() 33 34 35 // The product interface declares the operations that all 36 // concrete products must implement. 37 interface Button is 38 method render() 39 method onClick(f) 40 41 // Concrete products provide various implementations of the 42 // product interface. 82 Creational Design Patterns / Factory Method 43 class WindowsButton implements Button is 44 method render(a, b) is 45 // Render a button in Windows style. 46 method onClick(f) is 47 // Bind a native OS click event. 48 49 class HTMLButton implements Button is 50 method render(a, b) is 51 // Return an HTML representation of a button. 52 method onClick(f) is 53 // Bind a web browser click event. 54 55 56 class Application is 57 field dialog: Dialog 58 59 // The application picks a creator's type depending on the 60 // current configuration or environment settings. 61 method initialize() is 62 config = readApplicationConfigFile() 63 64 if (config.OS == "Windows") then 65 dialog = new WindowsDialog() 66 else if (config.OS == "Web") then 67 dialog = new WebDialog() 68 else 69 throw new Exception("Error! Unknown operating system.") 70 71 // The client code works with an instance of a concrete 72 // creator, albeit through its base interface. As long as 73 // the client keeps working with the creator via the base 74 // interface, you can pass it any creator's subclass. 83 Creational Design Patterns / Factory Method Applicability Use the Factory Method when you don’t know beforehand the exact types and dependencies of the objects your code should work with. The Factory Method separates product construction code from the code that actually uses the product. Therefore it’s easier to extend the product construction code independently from the rest of the code. For example, to add a new product type to the app, you’ll only need to create a new creator subclass and override the factory method in it. Use the Factory Method when you want to provide users of your library or framework with a way to extend its internal components. Inheritance is probably the easiest way to extend the default behavior of a library or framework. But how would the framework recognize that your subclass should be used instead of a standard component? 75 method main() is 76 this.initialize() 77 dialog.render()      84 Creational Design Patterns / Factory Method The solution is to reduce the code that constructs components across the framework into a single factory method and let anyone override this method in addition to extending the component itself. Let’s see how that would work. Imagine that you write an app using an open source UI framework. Your app should have round buttons, but the framework only provides square ones. You extend the standard Button class with a glorious RoundButton subclass. But now you need to tell the main UIFramework class to use the new button subclass instead of a default one. To achieve this, you create a subclass UIWithRoundButtons from a base framework class and override its createButton method. While this method returns Button objects in the base class, you make your subclass return RoundButton objects. Now use the UIWithRoundButtons class instead of UIFramework . And that’s about it! Use the Factory Method when you want to save system resources by reusing existing objects instead of rebuilding them each time. You often experience this need when dealing with large, resource-intensive objects such as database connections, file systems, and network resources.   85 Creational Design Patterns / Factory Method Let’s think about what has to be done to reuse an existing object: 1. First, you need to create some storage to keep track of all of the created objects. 2. When someone requests an object, the program should look for a free object inside that pool. 3. … and then return it to the client code. 4. If there are no free objects, the program should create a new one (and add it to the pool). That’s a lot of code! And it must all be put into a single place so that you don’t pollute the program with duplicate code. Probably the most obvious and convenient place where this code could be placed is the constructor of the class whose objects we’re trying to reuse. However, a constructor must always return new objects by definition. It can’t return existing instances. Therefore, you need to have a regular method capable of creating new objects as well as reusing existing ones. That sounds very much like a factory method. How to Implement 1. Make all products follow the same interface. This interface should declare methods that make sense in every product.  86 Creational Design Patterns / Factory Method 2. Add an empty factory method inside the creator class. The return type of the method should match the common product interface. 3. In the creator’s code find all references to product constructors. One by one, replace them with calls to the factory method, while extracting the product creation code into the factory method. You might need to add a temporary parameter to the factory method to control the type of returned product. At this point, the code of the factory method may look pretty ugly. It may have a large switch operator that picks which product class to instantiate. But don’t worry, we’ll fix it soon enough. 4. Now, create a set of creator subclasses for each type of product listed in the factory method. Override the factory method in the subclasses and extract the appropriate bits of construction code from the base method. 5. If there are too many product types and it doesn’t make sense to create subclasses for all of them, you can reuse the control parameter from the base class in subclasses. For instance, imagine that you have the following hierarchy of classes: the base Mail class with a couple of subclasses: AirMail and GroundMail ; the Transport classes are 87 Creational Design Patterns / Factory Method Plane , Truck and Train . While the AirMail class only uses Plane objects, GroundMail may work with both Truck and Train objects. You can create a new subclass (say TrainMail ) to handle both cases, but there’s another option. The client code can pass an argument to the factory method of the GroundMail class to control which product it wants to receive. 6. If, after all of the extractions, the base factory method has become empty, you can make it abstract. If there’s something left, you can make it a default behavior of the method. Pros and Cons You avoid tight coupling between the creator and the concrete products. Single Responsibility Principle. You can move the product creation code into one place in the program, making the code easier to support. Open/Closed Principle. You can introduce new types of products into the program without breaking existing client code. The code may become more complicated since you need to introduce a lot of new subclasses to implement the pattern. The best case scenario is when you’re introducing the pattern into an existing hierarchy of creator classes.      88 Creational Design Patterns / Factory Method Relations with Other Patterns • Many designs start by using Factory Method (less complicated and more customizable via subclasses) and evolve toward Abstract Factory, Prototype, or Builder (more flexible, but more complicated). • Abstract Factory classes are often based on a set of Factory Methods, but you can also use Prototype to compose the methods on these classes. • You can use Factory Method along with Iterator to let collection subclasses return different types of iterators that are compatible with the collections. • Prototype isn’t based on inheritance, so it doesn’t have its drawbacks. On the other hand, Prototype requires a complicated initialization of the cloned object. Factory Method is based on inheritance but doesn’t require an initialization step. • Factory Method is a specialization of Template Method. At the same time, a Factory Method may serve as a step in a large Template Method.  89 Creational Design Patterns / Factory Method 321 page from the full book are omitted in the demo version

websiteIOADMIN Mei 21, 2020 Admin Bandung Indonesia

DESIGN PATTERNS E-BOOK

indonesia NKRI 1945-1993

nissa sabyan dan wirya ( fadli wirya wirawan ) kiwil

i LOVE U AJAH SEKEDAR HAL BIASA PERJUANGAN SENJA

SEARCHING ME

https://www.google.com/search?q=fadli+wirya+wirawan&safe=strict&rlz=1C1CHBD_enID897ID898&sxsrf=ALeKk02S8AVDtK7SAJHnps1khZP-uJe4Lw:1590010079723&ei=36DFXvHhK__bz7sP7IqCsAI&start=10&sa=N&ved=2ahUKEwixzfaPscPpAhX_7XMBHWyFACYQ8NMDegQIFhBC&biw=1164&bih=480

CERITA KASMARAN 2009-2017

Assalamualaikum  ... 
sebuah Nama yg seringkali  kerap kami sebutkan DI sebuah media,  pertemuan kami singkat,  Berikut  ini  cerita  kami: 

wirya : disebuah  tempat  DIMANA Aku  Dan dikau  dipertemukan  " BANDUNG ciater"  
Nissa : DIMANA kami saling  dipertemukan  Untuk berpandang Mata yg saling  meratap  satu  Sama lain. 
wirya: disebuah  Danau  kecil disamping emperan  senja  aku sedang  bermain  dengan  sebilah  bambu  kicit  , ku ayunkan bambu itu Diatas air, lalu sobat menghampiri  DENGAN sebutan  Nama Kiwil.  wil Bernama "ainul yaqin" . will mau Gak ane  kenalin   Sama perempuan  yg sedang  duduk  Manis  Bersama ibunya  didekat panggung  Gambus  , lalu wirya ucap : ngapain kesana  ane orgnya pemalu , ainul yaqin: ikut ane aja, Ente Lg shalawatan  pinggir  Danau  Ada yg Suka  Tuh Sama Suara Ente,  wirya ucap: " Okelah null Hayooo, sambil ditariklah kedua lengan  tangan,  
nissa: sambil tersenyum enyah  pipi merah  merona , si perempuan  kicit pemberani  .. 
ibunya mendekatkan kepada SI lelaki tersebut  Bernama wirya(kiwil),  "kedua nya berjabat  tangan" Antara  wirya &nissa 
lalu ucap ibunya nissa: 💏💝 kalian Sudah saling berkenalan  ,"jangan lupa yaa ketika dewasa Nanti,  setelah sukses Bertemu  kembali" 
ainul Yaqin sobatku ucap: Tuh will dengerin  jangan  DI sia"in . 
sampai dumandangkannya Azan..  kami wirya & ainul  yaqin  bergegas  Ke sebuah SURAT dipingir Kali barbatuan " shalat  dzuhur"  wirya berdoa" ucap : yaa Allah ku bertemu Dgn seorang perempuan  yg diperkenalkan Dan disetujui oleh ibundanya, pertemukanlah kami sampai  kami menuju " I will be a success  .

WIRYA : SMP YAYASAN NURUL IMAN YANOERY  90 & NISSA SDN BANDOENG.  
Almat pertemuan  senja  CIATER BANDOENG.  💋💞💕 NEXT CERITA MERANJAK USIA SMK BORCESS  .  SAMPAI WIRYA KULIAH pamulang  university

Hingga kau saat ini sudah menemukan  jati diri.   11 september  1993 & 23 mei 1999
Salam CINTA DAMAI

Start a New Zend Framework 2 Project

English – indonesia

Tutorial

MEMULAI FRAME KERJA PROJEK 2 BARU

XAMPP makes it easy to start developing with PHP, and Zend Framework 2 is one of the most popular PHP

development frameworks. This guide walks you through the process of initializing a new Zend Framework 2

project with XAMPP.

XAMPP dunakan dengan mudah untuk memulai deloper dengan php , dan zend frame cara kerja di sebuah popularitas php , developer frame kerja ini . ini berkenaan yang ingin kamu proses dalam sebuah inisial baru dalam projek dengan xampp .

This guide assumes that you have already downloaded and installed Git for Windows, and

that the git binary is in your Windows PATH. If you don’t have Git for Windows, you can

download and install it from here. It also assumes that the new Zend Framework 2

application will be accessible at the URL http://localhost/myapp/.

Mengasumsikan kamu mempunyai apa yang kamu pelajari , donload dan isntall git untuk windows , dan path dalam sebuah windows , jika kamu tidak memiliki GIT untuk sebuah windows kamu dapat mengakses sebuah aplikasi dalam alamat url http://localhost/myapp/.

Ikuti langkah demi langkah

2. Within your XAMPP installation directory (usually C:\xampp), create a new directory named apps\ (if it

doesn’t already exist). Then, within this new apps\ directory, create a directory to hold your Zend

Framework 2 application and its related XAMPP configuration files. In this example, call the directory

myapp\.

Dengan instalasi dalam xampp derektori penyimpanan ( C:\xampp)

Tambahan saya akan menmyampaikan dalam langkah demi langkah masuk ke direktori cmd

Text hitam windows :

3. Extract the contents of the ZIP archive to the myapp\ directory. This will produce a zendframework-

ZendSkeletonApplication-[xx]\ subdirectory in the myapp\ directory. Rename this newly-created

subdirectory to

3. mengkompres konten dalam bentuk ekstensi zip di sebuah my app\deirektori htdocssebuyah produksi menunjukan ke zendframe cara kerjanya. Menamakan direktori folder baru

websiteIOADMIN Mei 20, 2020 Admin Bandung Indonesia

MEMULAI FRAME KERJA PROJEK 2 BARU

Start a New Zend Framework 2 Project

English – indonesia

Tutorial

MEMULAI FRAME KERJA PROJEK 2 BARU

XAMPP makes it easy to start developing with PHP, and Zend Framework 2 is one of the most popular PHP

development frameworks. This guide walks you through the process of initializing a new Zend Framework 2

project with XAMPP.

This guide assumes that you have already downloaded and installed Git for Windows, and

that the git binary is in your Windows PATH. If you don’t have Git for Windows, you can

download and install it from here. It also assumes that the new Zend Framework 2

application will be accessible at the URL http://localhost/myapp/.

Ikuti langkah demi langkah

2. Within your XAMPP installation directory (usually C:\xampp), create a new directory named apps\ (if it

doesn’t already exist). Then, within this new apps\ directory, create a directory to hold your Zend

Framework 2 application and its related XAMPP configuration files. In this example, call the directory

myapp\.

Dengan instalasi dalam xampp derektori penyimpanan ( C:\xampp)

Tambahan saya akan menmyampaikan dalam langkah demi langkah masuk ke direktori cmd

Text hitam windows :

3. Extract the contents of the ZIP archive to the myapp\ directory. This will produce a zendframework-

ZendSkeletonApplication-[xx]\ subdirectory in the myapp\ directory. Rename this newly-created

subdirectory to

3. mengkompres konten dalam bentuk ekstensi zip di sebuah my app\deirektori htdocssebuyah produksi menunjukan ke zendframe cara kerjanya. Menamakan direktori folder baru

Inventory Management System

The network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunicationsThe network registration system for the telecommunications

PRODUCT DESCRIPTION

2017 Version 7.3

VC4 B.V.

IMS Product description

Table of Content

1. Introduction ....................................................................................................................................... 7

2. General functionality ......................................................................................................................... 8

2.1 Search functionality ..................................................................................................................... 8

2.2 Right mouse menus and double click option .............................................................................. 8

2.3 Data export functionality ............................................................................................................. 8

2.4 Network Status ............................................................................................................................ 9

2.5 Object reminder ........................................................................................................................ 10

2.6 History........................................................................................................................................ 11

2.7 Business rules and validation checks ......................................................................................... 11

2.8 Naming convention ................................................................................................................... 11

3. Locations .......................................................................................................................................... 12

3.1 General information .............................................................................................................. 12

3.2 Locations / sites ..................................................................................................................... 13

3.3 Floor Plan and Racks .............................................................................................................. 14

4. Equipment ....................................................................................................................................... 15

4.1 Equipment types.......................................................................................................................... 15

4.2 Equipment ................................................................................................................................. 16

4.2.1 General info ........................................................................................................................ 16

4.2.2 Graphical layout .................................................................................................................. 16

4.2.3 Physical and logical ports .................................................................................................... 17

4.3 Cards .......................................................................................................................................... 17

4.3.1 Card names and types ........................................................................................................ 17

4.3.2 Ports with related information ........................................................................................... 18

4.3.3 Card relations...................................................................................................................... 18

4.3.4 Card per slot ....................................................................................................................... 18

4.3.5 Card in card ......................................................................................................................... 19

IMS Product description

4.4 Node template ........................................................................................................................... 19

5. Distribution Frames ......................................................................................................................... 20

6. Connections ..................................................................................................................................... 23

6.1 Connection types ....................................................................................................................... 23

6.2 Connection speeds and types: .................................................................................................. 24

6.3 General information related to connections: ............................................................................ 25

6.4 Layering ..................................................................................................................................... 25

6.5 Ports ........................................................................................................................................... 25

6.6 Protections ................................................................................................................................. 26

6.7 Planning of connections ............................................................................................................ 26

6.7.1 Manual planning ............................................................................................................ 26

6.7.2 Automatic planning ....................................................................................................... 26

6.8 Test results ................................................................................................................................. 26

7. Graphical Circuit Path ...................................................................................................................... 27

8. GIS, Outside Plant and Network Map functionalities ...................................................................... 28

8.1 Interactive map ..................................................................................................................... 28

8.2 Geographical background ..................................................................................................... 30

8.3 Network Map functionalities ................................................................................................. 30

8.4 Outside Plant ............................................................................................................................. 33

8.4.1 OSP objects .................................................................................................................... 33

8.4.2 GIS Functionalities ......................................................................................................... 34

9. Network Rings .................................................................................................................................. 35

10. Customers ...................................................................................................................................... 35

10.1 Customer information ............................................................................................................. 35

11. Leased Lines and Interconnects ..................................................................................................... 36

11.1 Leased Lines ........................................................................................................................... 36

11.2 Interconnects ......................................................................................................................... 38

IMS Product description

12. Base station, Cell, RF & Antenna details ........................................................................................ 39

13. Vendors and contracts ................................................................................................................... 40

14. Platforms ....................................................................................................................................... 42

15. Domains ......................................................................................................................................... 43

16. IP Management ............................................................................................................................. 44

17. Network Planning and Change Management ................................................................................ 45

17.1 Manual and Automated Planning ......................................................................................... 45

17.2 Change Management ............................................................................................................ 46

18. Capacity Management ................................................................................................................... 47

19. Workflow Management................................................................................................................. 49

19.1 Order queues ........................................................................................................................... 49

19.2 Order type ............................................................................................................................... 50

19.3 Order fields and attachments .................................................................................................. 51

19.4 Order Reports .......................................................................................................................... 52

20. Trouble Tickets .............................................................................................................................. 53

20.1 General .................................................................................................................................... 53

20.2 Impact calculation ................................................................................................................... 53

20.3 Fault Management .................................................................................................................. 53

21. Planned Works impact analysis ..................................................................................................... 54

21.1 General Planned Work info ..................................................................................................... 54

21.2 Planned Work analysis ............................................................................................................. 54

21.3 Planned Work Email Notification ............................................................................................ 54

22. Single Point of Failure calculation ................................................................................................. 55

23. Warehouse Management .............................................................................................................. 58

23.1 Materials .................................................................................................................................. 58

23.2 Material list .............................................................................................................................. 60

23.3 Material template .................................................................................................................... 60

IMS Product description

23.4 Order list .................................................................................................................................. 61

23.5 Material actions ....................................................................................................................... 61

23.6 Reserve equipment .................................................................................................................. 61

23.7 Materials ready to be picked up .............................................................................................. 61

23.8 Book out Materials .................................................................................................................. 61

23.9 Cable Management ................................................................................................................. 62

23.9.1 Cable types ....................................................................................................................... 62

23.9.2 Other actions around cables ............................................................................................. 62

23.10 Warehouse to Network Inventory ......................................................................................... 62

23.11 Network Inventory to Warehouse ......................................................................................... 63

23.12 Reports .................................................................................................................................. 63

24. Spares Management ...................................................................................................................... 63

25. Reports .......................................................................................................................................... 64

26. Bulk changes .................................................................................................................................. 65

27. Flexible fields and tabs .................................................................................................................. 66

28. Interfaces to other systems ........................................................................................................... 67

28.1 Network Management System Interfaces................................................................................. 68

28.1.1 Types of Interfaces ....................................................................................................... 68

28.1.2 Network Reconciliation ................................................................................................ 68

28.1.3 Auto provisioning from IMS into NMS/EMS or NE ....................................................... 70

28.1.4 Service Fulfillment ........................................................................................................ 70

28.2 BSS/OSS interfaces .................................................................................................................... 71

28.2.1 Alarm Management System Interfaces ......................................................................... 71

28.2.2 Customer Resource Management System (CRM) Interfaces ........................................ 71

28.2.3 Interface between IMS and Financial Systems .............................................................. 72

28.2.4 Interfaces to other types of applications and databases .............................................. 72

28.3 IMS Webservice API’s ................................................................................................................ 73

IMS Product description

29. User-groups and permissions ........................................................................................................ 74

29.1 Users and User groups in IMS ............................................................................................... 74

29.2 Database domains ................................................................................................................. 74

30. IMS Architecture ............................................................................................................................ 75

30.1 Database and application ...................................................................................................... 75

30.2 High Availability ..................................................................................................................... 75

30.2.1 Architecture ................................................................................................................... 75

30.3 VPN ........................................................................................................................................ 76

IMS Product description

1. Introduction

IMS is a powerful multi-user application that offers fast and user-friendly facilities for registering and managing a wide range of telecommunication networks and platforms. This includes networks such as MPLS/IP, SDH, SONET, WDM/OTN, Fiber/FTTx, Ethernet, Mobile Core, Backhaul and RAN (2G, 3G, 4G), Microwave, xDSL, WIFI, Broadcasting, Subsea cable, VSAT, ATM, Voice, DCN and Synchronisation.

IMS can be used across the entire organisation. This means that the needs of the technical departments, sales through to senior management are all well catered for. Main benefits of IMS:

• Complete and accurate asset overview, full life cycle of materials

• Platform and vendor independent

• End to end views of network services, cross platform

• Perform daily tasks faster and smarter resulting in shorter lead times in service delivery and fault handling

• Improvement of Service Level

• Accurate view of physical asset values representing depreciation and return on investment

• Integration with other systems, like NMS, CRM, Financial & Billing Systems, etc.

• Automatic discovery and synchronization of live network assets with NMS

• Optimized Network Capacity Management, saving CAPEX by avoiding unnecessary network spend.

• Pro-active network build initiated by threshold reporting

• Significant OPEX cost savings due to Leased Line invoice checks

• Can be used by complete organisation, including engineers, Customer Service, Management & Sales.

• Easy build of new equipment and connection types

• Less network outages due to Single Point of Failure calculations

This document describes all functionalities of the IMS application from a high level.

Live demo of the IMS system may be requested via sales@vc4.nl

IMS Product description

2. General functionality

2.1 Search functionality

Search fields have been implemented throughout the system, so that all information stored can be found.

Most are pull down fields, others are free text search fields, or both.

Free text fields search with a “like” and over multiple fields.

After a search with multiple results, these results can

be filtered to fine-tune the search.

2.2 Right mouse menus and double click option

Special Right Mouse Click Menus can be used to find information about a specific object.

On network items (such as circuit names, equipment names, locations) users can double click to find more details of the specific item.

2.3 Data export functionality

Every table (grid) in the different IMS screens can be exported to Excel or CSV via a right mouse option.

Specific features, like Network Rings and Network Map support export to PDF.

Other export types are supported at the server side, such as XML and txt.

A full set of webservice API’s is also supported, so that external applications can extract information from the system.

IMS Product description

2.4 Network Status

Network items such as connections, nodes, shelves and locations, always have a status in IMS. An explanation of each status is detailed below:

Status Description Explanation PL Planned A planned item is planned/designed, but is not built in the network yet. RFS Ready for Service An item with RFS status has been built in the actual network, but is not operational yet. IS In Service The item is in use/operational MI To be Migrated This status is applicable when the item is still in service, but will be migrated soon. After the migration is completed, the object status will be set to “In Service (IS)” again. RFS Ready for Cease With this status, the network object is marked as still in use, but will be dismantled soon. OOS Out of Service The network item is not in use anymore

Business and technology rules have been implemented in the IMS system. Before a status change is being executed, IMS will validate if the status change can be done.

Example: a connection cannot be set “in service”, when the card or equipment related to the connection is still in “planned” or “ready for service” status.

IMS Product description

Warehouse and Spares statuses When equipment is in the IMS Warehouse and not in the network, the materials can have statuses related to the warehouse: Status Explanation In Stock The material is stored in a warehouse location. Ordered The material is being ordered at the equipment vendor and is not in a warehouse location yet. To be returned The material is dismantled/removed from the network and is on its way back to a warehouse location Lay Out The equipment is being prepared/packed to be picked up. It will leave the warehouse any moment. Out Stock Material is not in warehouse anymore. Ready for Sale The material is in warehouse and will not be used in network anymore. It will be sold. Sold The material has been sold to an external party. Returned Something is wrong with the material and is returned to vendor. Defect The material is defect and needs to be fixed or replaced.

2.5 Object reminder

A user-friendly object reminder is available for the users to quickly find recent objects created and highlighted.

Objects can be set in focus to highlight the objects in the specific screen that is open.

Objects in focus can be related to other objects.

For example connection to port or layered into another connection.

IMS Product description

2.6 History

All IMS user and interface activities and changes on the network are stored in the IMS database with related username, batch name or interface application name, date/time and description of the activities.

Those history records can be viewed per inventory object.

2.7 Business rules and validation checks

Many business rules and validation checks have been implemented. These rules and validation checks are technology specific, IMS specific or based on rules specific to the customer's organisation.

Some examples are:

- Check the status of its parent objects before changing the status;

- Check the port type (speed) with the connection type when connecting a connection to a port;

- Check related Leased Line (from other operator) when changing connection status to “Out of Service”;

- Check if there is a SPOF (Single Point of Failure) in the connection when changing the connection status;

- Before changing the speed/bandwidth/type of a connection/service, check if the change can be done;

- Before changing a card (manually or via network reconciliation), check if change can be done.

2.8 Naming convention

IMS complies with the naming convention standards implemented by our customers.

Business rules will be implemented to ensure a correct naming convention for new objects.

Auto naming convention can be set for the different attributes, such as:

- Locations

- Active and passive equipment

- Connections and services

- Order numbers

- Trouble Ticket numbers

- Planned Work references

IMS Product description

3. Locations

3.1 General information

The following location types can be registered in IMS, in hierarchy:

- Countries

- Provinces/States/Regions

- Cities

- Buildings/Sites/other locations

- Rooms

A city must be related to a country and optionally to a province/state/region and/or a district.

One building can have several sub locations (rooms) related. Each location (like building, room) has a unique identifier in the IMS database.

Below example of the City form - Geo map in IMS:

IMS Product description

3.2 Locations / sites

The sites/buildings and related rooms have related information like:

- General information, like

o Address details

o Room/floor name (in case of room location)

o Status

o Phone number

o Longitude/ Latitude

o Access Description

o Owner

o Contact person(s)

o General description

o Location type (list of types can be defined)

- Connections beginning or ending at a location

- Equipment installed

- DDF, ODF, Patch-Panels in the location

- Location alias names (different names for same location)

- Cabinets/Racks in the location

- Free/available ports in the location

- Geographical Maps (to view location in OpenStreet Maps, Google and/or Bing)

Special location naming convention rules can be implemented on request.

IMS Product description

3.3 Floor Plan and Racks

The Floor Plan Management functionality supports the management of the sites. Via a graphical view of the site users can easily manage the floor space. It includes:

- Floor plan details, like

o Floortiles:

o Tile height

o Tile width

o Flexible labeling of the floortiles

o Racks/Cabinets

o Node/Power/DDF/ODF shelves in the rack/cabinet

o Walls, entrances

- Rotation of objects in floor plan

- Drag and drop functionality

- Zoom in/out

Example above (on the left) is a graphical layout of a location

On the right is a cabinet/rack opened from the floorplan with equipment placed at certain heights within the cabinet.

Rack types can be models by users with appropriate user permissions.

IMS Product description

4. Equipment

4.1 Equipment types

VC4-IMS has the capability to model all different kinds of equipment, such as MPLS/IP, Ethernet, WDM/OTN, SDH, SONET, PDH, Voice/VoIP, Mobile 2G-3G-4G-5G RAN & Core, Microwave, FTTx/xPON, Broadcast, SubMarine, Satellite/vSAT, WiFi, SDN, Servers (physical and virtual) and many more.

IMS is vendor independent, so all types of all vendors can be created and modeled using the IMS GUI by users with appropriate permissions.

For each shelf/sub-shelf the front and back layout can be modeled in a graphical representation.

Other functions related to equipment type:

- Set up shelves

- Set up dimensions of equipment shelves

- Set up slots and slot dimensions

- Set up cards and cards per slot

- Set up card pluggables (FSPs/XFPs)

- Link an equipment type to a platform (such as MPLS, WDM)

- Link an equipment type to a management system (NMS/EMS). ‘

- Set an icon, so that each type has a specific icon on the IMS Network Map.

- Relate equipment type picture

- Copy equipment type

IMS Product description

4.2 Equipment

Equipment (network elements) with related information can be stored in IMS.

The following information can be stored.

4.2.1 General info

- Nodename

- Status

- Type of equipment

- Location where equipment has been installed

- Loopback address

- Management System

- Order details

- Hardware/Software version

- Serial number

- Barcode

- UPS info

- General comments

- Customized fields (see customized fields and tabs)

4.2.2 Graphical layout

A graphical representation is given for the piece of equipment.

IMS Product description

4.2.3 Physical and logical ports

In the equipment form, at the bottom of the screen all the ports, physical and logical, are visible.

The following info is available:

- Port name

- Interface

- IP address

- DDF/ODF position

- Circuitname (connection on port)

- Status of connection

- Status of port

- Type of port (bandwidth/speed)

- Uni / bi (directional)

- Comment

- Domain

- Reservation number

- Reserved by

- Reserved date

- Blocked yes/no

Equipment with specific functions can have additional port information.

Additional fields can be added using customized fields by admin users (see customized fields and tabs).

4.3 Cards

4.3.1 Card names and types

Cards will be visible in the slots. From the screen the cards can be opened to see more card details like:

- Card name

- Card code (if applicable)

- Parent card (if applicable)

- Serial number

- Barcode

- Status

- Software release

- Software revision

- Hardware version

- Protection card (yes/no)

- Date fields (like creation date, in service date)

- Extra info

- Order details

Each card type can have one or multiple card codes related.

Examples:

- Cisco card name “PA-4E1G/120”, card code “73-2250-04”

- Ciena card name “CN-M6-FLEX” card code “B-966-0013-011”

- Nortel card name “8 X OC-3/12/STM-1/4 VT1.5/LO SFP”, card code “NTK513DA”

Users with appropriate permissions can create, change and delete cards in the IMS system.

IMS Product description

4.3.2 Ports with related information

All ports related to the cards will be shown in the equipment form, with information such as:

- Port name

- Interface

- IP address

- DDF/ODF position

- Circuitname (connection on port)

- Status of connection

- Status of port

- Type of port (bandwidth/speed)

- Uni / bi (directional)

- Comment

- Domain

- Reservation number

- Reserved by

- Reserved date

- Blocked yes/no

Users with appropriate permissions can create, change and delete ports on cards and equipment.

4.3.3 Card relations

Relations between cards can be made. For example, relation between front cards and back cards.

4.3.4 Card per slot

Business rules have been implemented to allow only certain cards in a specific slot. Users with the appropriate user permissions can add and change these business rules on “cards-per-slot”.

Also cards that occupies multiple slots can be handled.

IMS Product description

4.3.5 Card in card

IMS supports the “card in card” model, where a carrier card has one or more sub-cards inserted.

The carrier card will have sub-slots (graphical visual on the screen).

Sub-cards in sub-cards are supported as well.

4.4 Node template

In many occasions a configuration of a node (cards in the equipment) will be like previous configurations.

When creating a new piece of equipment IMS users can choose a template with cards already inserted in the correct slots. With the same functionality, a copy of an existing equipment can be done as well.

IMS Product description

5. Distribution Frames

Distribution frames (like DDF, ODF, Patch Panels, Splice panels) can be registered in IMS.

Cables (patches, jumpers) can be made between:

- Frame and equipment (e.g. pre-wiring)

- Frame and Frame

- Frame and leased line

Cables can be layered into a main cable.

Splices can be registered and splice schemas can be viewed.

Graphical views can be drawn to show the end to end cable routes. Below an example of cable route starting on WDM equipment (lowest rectangle) towards an ODF and another ODF, routing further to fiber network (OSP).

IMS Product description

All types of frames can be modeled in IMS.

Users can create the digital and optical distribution frames with location as starting point. DDF/ODF shelves and patch panels can be positioned in a rack.

Each frame has a front and a back. Per frame position a connection/patch can be made to equipment (pre-wiring) or other frame.

Below a screenshot of an ODF with its positions (filtered on back side positions).

Also splice schema (splices made within a splicebox) can be generated in the same way:

IMS Product description

Schematic drawing of the splices can be viewed in a graphical way:

IMS Product description

6. Connections

6.1 Connection types

Numerous kinds of connections can be stored on IMS. Some examples are shown below:

- Transport connections, like

o SDH

o SONET

o PDH

o WDM, OTN

o Cables, (Sub)Seacables

o Trenches, Ducts, Fiber cables, fibers

o GPON

o DSL

o Microwave

- Ethernet connections, like

o Carrier Ethernet, including:

o E-Lines (Ethernet service connecting two customer Ethernet ports over a WAN)

o E-LAN (a multipoint service connecting a set of customer endpoints, giving the appearance to the customer of a bridged Ethernet network connecting the sites)

o E-tree (a multipoint service connecting one or more roots and a set of leaves, but preventing inter-leaf communication)

o Metro Ethernet

o Ethernet over SDH/SONET

o Ethernet over MPLS

o Ethernet over Microwave

o GPON

- Data connections, like

o MPLS

o IP

o Frame Relay, ATM

- Voice like

o Customer voice connections

o Voice interconnects (to other telcos)

o Voice core and access links

o Signal links

o Voice routes

- Mobile

o Mobile Core 2G, 3G, 4G, 5G

o Mobile RAN 2G, 3G, 4G, 5G

o Mobile Backhaul

o National and international Interconnects

- Broadcast Network Connections, such as

o Trunks

o xGBE

o Source Routes

o VLANs

o Unicast

o Multicast

o ETS

o Services

IMS Product description

- WiFi, WiMax connectivity

- Radio connections

o Microwave connections

o Sub connections

- Satellite/vSat connections

- Power connections

- DCN connections

- Synchronization connections

All connection rules (such as layering rules, sub-channel configurations, default data entry values, etc.) can be set up in the GUI of the system.

6.2 Connection speeds and types:

All circuit speeds/types can be modeled on IMS.

Examples:

- OTS, OMS, OTU, ODU0, ODU1, ODU2, ODU3, ODU4

- 2.5Gb, 10Gb, 100Gb, 400Gb, 480Gb, etc

- 10Mb, 100Mb, 1Gbe, 10Gbe

- STM1, STM4, STM16, STM64

- VC4, VC4-4C, VC4-16C, VC4-64C, VCgroup

- OC3,OC12, OC48, OC192

- STS1, STS3, STS12, STS48, STS192

- 45MB/VC3/T3

- 34Mb/VC3/E3

- 2Mb/VC12/E1

- 1.5Mb/VC11/T1

- 64k, 128k, 512k, etc.

- PVC, VCC, VPC

- VPN, VLAN, VRF, L2VPN, L3VPN, Service Tunnel, Pseudowires (PWE)

- VCG, E-Line, E-LAN, E-Tree

- GPON

- Radio/Microwave/RF

- Mesh Tunnels, Mesh Protection tunnels

- WIFI connections

- 2MHz, 5Hz, 20MHz, etc

- Power

- Trunks, xGBE, Source Routes, VLANs, Unicast, Multicast, ETS, Services

- etc.

IMS Product description

6.3 General information related to connections:

Different kinds of information can be associated with each connection, such as:

- Connection name

- Location A-end

- Location Z-end

- Speed

- Status

- Customer/Platform

- Order information

- Product code/Service

- Platform

- Extra information

- Framing/Line coding

- Dates

- Protection settings

- etc

6.4 Layering

The complete network hierarchy can be modeled on IMS.

Examples:

- A physical ethernet connection will have V-LANs. A VLAN can have services (e.g. L2VPN, L3VPN) or other VLANs.

- A physical WDM connection with have OCH (optical channel) on a frequency and have ODUx connections that can carry other ODU connections or client connections (e.g. MPLS, SDH, etc)

- A physical SDH connection (STMx) can carry VC4x connections, which can have sub-connections (e.g. E1, E3).

IMS supports all technologies and all network layers up to and including customer services.

The user can easily click through this network hierarchy.

6.5 Ports

All ports related to a connection are visible on the connections screen. The following data is shown:

- Port name

- Card interface

- IP address

- DDF/ODF position connected to port (pre-wiring)

- Name of the connection that is connected to port

- Port status

- Port type

- Port speed

- Comment field

- Platform

- Reservation info

IMS Product description

6.6 Protections

All different kinds of circuit protection mechanisms can be stored in IMS. Some examples being:

- MSP

- MSPRING / BLSR

- SNCP / UPSR

- Twin connections

- DNI

- 1+n card protection

- Mesh/ASON

6.7 Planning of connections

Connections can be planned in IMS before built in the actual network.

6.7.1 Manual planning

IMS allow users to manually assign the connections to specific channels and ports. Protections and specific settings to connections can be stored as well.

6.7.2 Automatic planning

The IMS Automatic Trail Engineering functionality allow network operators to automatically plan connections in IMS. This functionality is based on “least cost routing”. Rules to define the “costs” can be implemented based on customer requirements (for example shortest distance, least hops, least financial costs or combination).

If so required IMS can link this automatic planning with the workflow engine of IMS, so that workflows can be fully automated.

See also Network Planning and Change Management.

6.8 Test results

After connections or services have been tested, test results can be saved against the connection/service.

If so required the testing process can be managed using the IMS Workflow, see chapter 19.

IMS Product description

7. Graphical Circuit Path

A graphical overview can be drawn for each connection. This is done “on-the-fly”, calculated from the information held within the database. All details of the worker and protect route is given, including leased line details.

The user can decide what kind of information is visible on the screen like location details, card details, DDF/ODF information, etc.

IMS Product description

8. GIS, Outside Plant and Network Map functionalities

The Network Map provide users with a graphical and geographical representation of the network.

Different kinds of network objects can be viewed in a map, such as

- Equipment

- DDF/ODF

- Manholes and splice-boxes (joints)

- Connections / services

- Link to other maps

8.1 Interactive map

Each object is an object from the database. IMS will draw the connectivity automatically based on the information stored in the database.

The Network Map is interactive, so that the objects can be opened directly from the map.

Example of Network Map, graphical:

IMS Product description

Example Network Map, geographical.

Right mouse menu is available on each object to find more details or to do certain actions:

IMS Product description

8.2 Geographical background VC4-IMS works with different GIS/geo background data providers, such as Openstreet Maps, Google and Bing. Other type of layers can be supported as well.

8.3 Network Map functionalities

Below a short explanation of different functionalities and options in the Network Map: Connection types A user can decide what types of connections needs to be drawn per Network Map. For example, in a MPLS map, only show MPLS type of connections, in a fiber map, only fiber network connections, etc.

IMS Product description

Highlighting connections Connections can be highlighted in the map. This is done with a thick line. All network connection layers can be highlighted. For example VLAN, L2VPN, 2MB, etc. Work paths are highlighted in green, protection path with a thick red and dotted line. Add objects Objects are placed on the network map automatically when a user creates those objects using the Network Map. Additionally, objects can be added to a network map using a menu option. KMZ Export Network Maps can be exported in KML/KMZ format. Turn on/off objects Users can make objects (per type) visible or invisible. Multi-create functions To help VC4-IMS users to quickly engineer new networks, the system has multiple functions to create multiple object in one action. Examples: - Multi create sites including automatically retrieve address + latitude/longitude information. - Multi create sites, and use templates for automatically implement equipment, ODF’s, and/or spliceboxes. - Multi create connections and auto connect to ports. - Multi “patch” connections from one ODF/Splicebox to multiple ODFs. For example for FTTH usecase: to connect multiple households to one splicebox in a manhole) - Create in multiple sites new equipment/DDF’s/ODF’s

IMS Product description

Auto routing VC4-IMS has auto routing capabilities for automatically finding the optimum route through the network. Line color settings The colors of the lines (connections) on the network Map can have different functions: - Status of the connection (blue is planned, green is in service, purple is “ready for service”, etc). - Type of connection (product code). Users can set a color per type of connection/product. - Used capacity. IMS calculates the used capacity and show green (enough capacity available), yellow (medium full) or red (full or almost full). Show additional information With tick-boxes within the menu, users may switch on/off additional information on the screen like:

All lines

In case there are multiple connections between two nodes, the IMS user can decide to see it as one line or see it as separate connections

Navigation

The map can be moved, zoomed in and out in normal graphical view, but also in geographical view.

Objects

Once a user has appropriate user permissions, the user can add, move/position and delete objects.

Free draw

Users can draw a new connection from starting node +port towards a second node. IMS will show automatically the available ports. In case of fiber trench, the geo route can be drawn directly on the map.

IMS Product description

Measure distance

Users can measure the distance within a map using point and click functionality.

8.4 Outside Plant

The physical inventory, Outside Plant (OSP), can be planned and maintained within the VC4-IMS application. Typically, the OSP functionality is used for fiber & copper network registration, Mobile RAN (2G, 3G, 4G, 5G), Microwave/Radio networks, WiFi, Wimax and Subsea cables. Since VC4-IMS also manages the active and logical networks (with the relation to the physical network), the logical connections and services can be seen in a geographical view. This unique combination makes it possible to perform different analysis to reduce network outages (Single Point of Failure calculations) and improve the sales activities.

8.4.1 OSP objects Examples of OSP objects that can be registered: - Trenches - Ducts - Fiber and copper cables - Fiber and copper connections - Manholes/Handholes locations - Cable entries (building, manhole, BTS site) - Poles - DDF/ODF’s - Spliceboxes / enclosures - Cassettes within spliceboxes - Splitters - Any other passive equipment/component - Active equipment, such as: o OLT, ONT/ONU o Mobile RAN (2G/3G/4G), Core o Transmission, MPLS/IP o Microwave o WiFi o Microwave o etc

IMS Product description

8.4.2 GIS Functionalities The following main functionalities around OSP/GIS are built in the system: - Network planning (locations, active and passive equipment, connections/services) - Network change management - Fault handling - Capacity management - Sales support (sell close to network) - Switch between geo-background and graphical view - Easy fiber/copper cable trench routing on the map (street level) - Auto routing over fiber/copper/logical layers - Registering the z-positions of cable routes (depth, height) - Single Point of Failure checks (e.g. worker and protection path configured in same fiber cable) - Planned Work impact analysis (which services go down due to fiber cut) - KML export - Splicing schemas - Full asset management of fiber/copper networks - Graphical and geographical end-to-end paths - Full point-to-point FTTx & PON network support - Reporting - Network Map functionalities as listed in paragraph 8.3

IMS Product description

9. Network Rings

Some networks, like WDM, Ethernet, SDH, SONET, can be built in a ring structure. In IMS you can create rings for these networks. Per ring the ring name, abbreviation, protection mechanism and in service date can be stored.

10. Customers

10.1 Customer information

Customer details are stored in the customer form. Customer data can be registered via the IMS Graphical User interface (GUI) or imported/linked via interface to a CRM application. The following information can be registered:

o Customer abbreviation

o Customer full name

o Customer related information, like

o Customer address

o Customer contact persons

o Customer connections/services

o Customer locations

o Customer equipment

o Customer orders

o Planned Works impacted to customer

o Trouble tickets impacted to customer

o Customer Contract and SLA information

These items can be opened directly from the customer page.

IMS Product description

11. Leased Lines and Interconnects

11.1 Leased Lines

A complete or part of a network connection can be leased via another telecom provider

(so called “leased line”).

Any leased lines can be registered and managed in the IMS application.

Information captured and managed

• General Attributes of the leased line, such as:

- Name

- Bandwidth

- Bandwidth up

- Bandwidth down

- Supplier

- Product (service name) of supplier

- Status

- Type (e.g. leased line, interconnect, telephone line)

- Distance

- Ratio (overbooking)

- Creation date

- Protocol

- Demarcation point

- protection information

- Order and cease number

- additional extra information (customizable by IMS Admin users).

IMS Product description

• Vendor and SLA (Service Level Agreement) information:

- Agreed Order lead times

- Agreed Fault repair time

- Agreed to be on-site

- Main time to repair

- Contact persons + details

- Connections bought from operator

- Product names

- Special Arrangements

- Escalation procedure

In case IMS workflow and IMS trouble ticket functionality are being used the agreed SLA’s can be checked with the actual SLA’s.

• Leased Line Contract information:

- Contract number

- Start date contract

- End date contract

- Related End date customer contract

- PO number

- Account number

- Internal cost center number

- Installation costs (+currency)

- Monthly costs (+currency)

- Contract term

- Extension term

- Costs related to extension

Automatic invoice check can be performed to audit the invoices from the leased line provider(s).

IMS Product description

11.2 Interconnects

An interconnect in IMS is a connection that connects your network with another operator, for example a 10Gbe or 1Gbe towards another operator delivering your service to the end-customer.

Other examples are: STMx/OCx interconnect delivering VC4/E3/E1 or STS3/1, T3,T1 circuits to end customers or Voice interconnects.

Interconnects to other networks can be managed from one page.

IMS gives a quick overview of all interconnects or just the interconnect to a specific network or telecom provider, including the available capacity per interconnect.

Information captured and managed

• the interconnect name

• status of the interconnect

• name of the domain the interconnect belongs to

• product code/service related to the interconnect

• name of the interconnect used by the other service provider

• used/occupied capacity in the interconnect

• name of the service provider of the other end of the interconnect

• A-end and Z-end, node + port details of the interconnect

IMS Product description

12. Base station, Cell, RF & Antenna details

For Mobile 2G, 3G, 4G, MW and WIFI networks physical and logical parameters can be stored against the base stations.

Antennas are modeled as sub-shelves of the BTS.

When an interface is built towards the NMS/EMS, IMS data will be automatically synchronized every night.

Specific forms have been created to manage the planning of the parameters.

Below some example screenshots for Mobile BTS’s (2G, 3G and 4G) parameters. VC4-IMS supports multiple future situations. Differences are highlighted in orange color.

Above screenshot of antenna details.

Below Cell details.

IMS Product description

Via network reconcile, all actual parameters can be viewed in the IMS Node form, see example screenshot below. The data will be grouped in different tab pages.

13. Vendors and contracts

All equipment and Leased Line vendors can be managed in IMS. Equipment vendors: IMS is vendor independent, so all equipment types of all vendors can be managed. Per vendor information can be stored such as: - Description - Equipment types - SLA on site - SLA MTTR (main time to repair) - Website/link - Special arrangements - Escalation description - Contacts with contact details - Maintenance Contracts When IMS Workflow, IMS Trouble Tickets and/or IMS Warehouse are being used, the system can support the management of the performance and SLA’s of your vendors.

IMS Product description

Leased Line vendors: Also all Leased Line vendors can be managed when Leased Lines are used in your network. Per vendor information can be stored such as: - Leased Line Products - Leased lines of this vendor/provider - Description - SLA on site - SLA MTTR (main time to repair) - Website/link - Special arrangements - Escalation description - Contacts with contact details When IMS Leased Lines, IMS Workflow and/or IMS Trouble Tickets are being used the system can support the management of the performance and SLA’s of your Leased Lines vendors.

IMS Product description

14. Platforms

IMS Network Planning and Inventory Solution is platform independent. This means all network platforms can be registered, such as (but not limited to): - MPLS / IP - MPLS-TP - WDM - OTN - SDH - SONET - Ethernet - Mobile Core 2G, 3G, 4G - Mobile RAN 2G, 3G, 4G - Microwave - Broadcast networks - PDH - ATM / Frame Relay - Subsea - Satellite - Synchronization - DCN - IT networks

A network item can be linked to a platform name. Related items can be viewed and opened via the platform form. For each platform relevant information can be stored, such as:

- Equipment

- Connections

- IP range.

IMS Product description

15. Domains

In IMS a domain refers to a group of network items, which is separated from another domain. Examples where network domains are often used: - IP management - V-LAN management - Voice networks After creating the domain name, this name can be related to network items, such as: - Equipment - Ports - Connections - IP addresses

IMS Product description

16. IP Management

IMS is designed to help telecom administrators automate the task of maintaining data about the assignment of IP addresses on a network. IMS manages the process of identifying in-use IP addresses and IP addresses that are not or no longer assigned to any device. IMS eliminates IP conflicts by using network domains. Within one domain an IP address must be unique.

It fully supports both IPv4 as well as IPv6.

As a first IP address ranges need to be created.

The system allows the creation of subnets, and sub of subnets (multiple layers).

IP addresses can be related to network items, like equipment (loopback address), ports, cards and connections (like VLAN’s).

IMS Product description

17. Network Planning and Change Management

Network Planners can use IMS to plan new or change network before it is built in the actual network.

Every network item, such as location, equipment, shelf, card and connection has a status to identify in which phase in the delivery or planning process it is, see also: network status.

IMS Network Planning can be used seamlessly with IMS Workflow (see IMS Workflow), so that planners follow the right process. In case IMS Workflow is not used, IMS can be linked to another workflow/order management system if so desired.

All kinds of handy tools have been built in to help the planner to plan their network in IMS, such as:

o Automatic Trail Engineering

o Equipment templates

o Duplicate circuit

o Copy routing

o Ring and network overviews

o Available routes from node

17.1 Manual and Automated Planning IMS allow users to manually create, change or delete network items and circuit routes. The Automatic Trail Engineering functionality allow network operators to automatically plan connections in IMS. This functionality is based on “least cost routing”. Rules to define the “costs” can be implemented based on customer requirements (for example shortest distance, least hops, least financial costs or combination). If so required IMS can link this automatic planning with the workflow engine of IMS, so that workflows can be fully automated.

IMS Product description

17.2 Change Management

Network Planners can plan new network in IMS such as new equipment, new cards, new connections, etc. Also existing networks may be subject for change. Those changes can be planned on forehand so that all departments (like NOC, Customer services) are aware of these changes. After changes have been implemented successfully, status can be changed to “In service” again. Old information, such as old routing and port info, will be stored in the IMS history.

The following changes can be managed: o Different network statuses used in the change management process; (see also: network status) o Migration (MI) status for connections which will be subject to change; o Future ports for ports that are currently occupied and will become available in the future; o Actual and future situations of connection and equipment/ports; o Actual and future situations on timeslot/channel level; o Capacity Management on actual network and future network; o Graphical Circuit Path for actual and future routing; o Planned dates for changes; o Change Management business and validation rules.

IMS Product description

18. Capacity Management

In the IMS Graphical User Interface (GUI) users can see used and available slots, ports, channels on the physical and logical network (equipment and connections).

Below example of the node form where users can see used and available slots and ports in one screen.

Example part of capacity report:

IMS Product description

The port capacity in a location can be found in the locations form, tab pages “free ports on location” and “used ports on location”.

Example of capacity in IP ranges

IMS Product description

19. Workflow Management

Workflow management is keeping track the tasks within your organisation.

This workflow management is an integrated module IMS. Every process can be created easily by users who have the correct permissions. It is not mandatory to use this functionality, IMS can also be integrated with other Workflow systems.

The IMS order management functionality supports:

- Flexible Process creation and adjustment

- Order queues

- Main and sub tasks

- Serial and parallel work streams

- Automatic tasks to queues

- Ability to accept or reject tasks

- Automatic Order Lead time management

- Report functionality

- Direct links to network items in inventory, like connections, equipment, etc.

Workflow functionality can also be used to automate certain tasks, like:

- Automatically create circuitname(s)

- Automatically relate circuit to port on equipment

- Automatically design circuit through network

- Automatically create sub interface on IP/MPLS router/switch

- Automatically relate IP address to port

- Set all related network items to "In Service"

- Automatically add card in equipment

- Auto provisioning of connections in Network

19.1 Order queues

Each department using the IMS workflow functionality will have its own order queue. A queue is a central order box where new orders are coming in and users (employees of the specific department) can pick up an order.

IMS Product description

19.2 Order type

For each process in the company (order type) a workflow can be created. For example “create new 1GBE MPLS connection”, “migrate 10GBE connection”, “build new equipment”, “cease leased line”, etc.

Users with the correct user permissions can create, modify and delete order types.

Below an example of different tasks in a process.

The workflow can be seen graphical as well.

IMS Product description

Workflow (including fields) may be adjusted any time. Open orders will not be changed, only new orders will follow adjusted process and related fields.

19.3 Order fields and attachments

Each process / order type will need to have its own kind of information.

For example:

To create a new connection, engineers need to know:

- Location FROM

- Location TO

- Bandwidth

- Number of connections

- etc.

For other kind of processes other information will be necessary.

To avoid mistakes in running orders functionality is available to define which information field is mandatory before closing a task and which field may be edited by a department.

Users with the correct user permissions can create this kind of fields and may define the business rules.

Example of order fields in a running order:

To each running order one or multiple attachments can be linked.

Those attachments will be stored on the IMS application server or any other file directory on Clients premises.

IMS Product description

19.4 Order Reports

All kind of KPI reports relating to order management are available and can be created.

Examples are:

- Department Lead time reports

- Number of orders per order type - per month - per department

- Closed orders per order type - per month - per department

- Current open orders - per department

IMS Product description

20. Trouble Tickets

20.1 General

The Trouble Ticket functionality in IMS manages and maintains lists of problems in the active network(s).

This functionality helps the organization, e.g. Customer Support Center and Network Operations Center (NOC) departments, to create, update and resolve reported customer issues and issues identified by the NOC.

A ticket can be created either, automatically via an interface to an alarm management system or manually by an IMS user.

Each ticket has a unique number in the system and contains information about the actual problem, actions performed by departments trying to solve the problem and general information, like status, severity, etc.

20.2 Impact calculation

With the Trouble Ticket functionality fully integrated in the IMS application, impact assessment can be performed directly for each network problem.

IMS will calculate the (customer) services and customers impacted. The impacted customers, connections and services, equipment and cards are all related on the trouble ticket.

Any active trouble tickets pertaining to a specific customer are directly visible from the Customer form within IMS.

20.3 Fault Management

The process to solve a network problem can be managed within the Workflow/Order Management.

For each process type, like

- Replace defect card

- Solve cable cut

- etc.

A process can be created with related responsible departments. Also, the standard lead-times can be registered, so that the Network, Customer and Vendor SLA's can be managed.

The complete Workflow functionality has been explained in chapter "Workflow Management".

IMS Product description

21. Planned Works impact analysis

Before Planned Work is carried out on the network, IMS can determine the impact of the Planned Work with regards to the customer services.

If so desired, IMS users can inform impacted customers via email. These emails can be sent from the IMS application using predefined Planned Work email templates.

21.1 General Planned Work info

In IMS a Planned Work order can be registered under a Planned Work reference with the following related information:

- Planned Work Reference number

- Planned Work engineer

- Planned Work Category

- Type of Planned Work, like

o Normal

o Emergency Planned Work

o Third Party Notification

- Status

- Description

- Begin date

- End date

- Expiry date

- Start time

- End time

- Outage time

- Related Trouble Ticket numbers

- Customer informed [yes/no]

21.2 Planned Work analysis

Planned Work engineers can import one or multiple network item(s) that are impacted by the Planned Work, for example:

- Equipment

- Card

- Connection

- Fiber/Copper cable, Duct/Span

- Leased Line

- Location

IMS will calculate all sub-connections and customer services running over the impacted network items.

The system can calculate whenever the sub-connections and customer services will have a protection switch or will go completely down.

21.3 Planned Work Email Notification

After the impact has been determined, customers can be informed via email functionality in IMS.

Responsible departments can create pre-defined email templates for different types of Planned Work.

This tool is multi-language.

IMS Product description

22. Single Point of Failure calculation

A Single Point of Failure, (SPOF), is a part of a network which, if it fails, will stop one or multiple (customer) services from working. They are undesirable in any network whose goal is high availability.

The assessment of a potentially single location of failure identifies the critical components of a complex network that would provoke a total (customer) service failure in case of malfunction. Highly reliable networks may not rely on any such individual component.

Below two schematic examples.

Scenario 1:

A service (green line) is running over a network (blue network). The service is protected on the left and right (dotted green line). In the middle, there is no protection. This is a SPOF.

The blue network is transported over the purple network. On the right, the worker and protection path run over a single link in the purple network. This is also a SPOF, because when the last purple line breaks, the service goes down.

IMS Product description

Scenario 2:

An operator sold to a customer two (2) single connections but those connections should be a protection of each other.

The two services (the green service and the orange line) run over a network (blue network). The two services should both take a unique route.

In the middle, the two connections run via the same path. This is a SPOF.

The blue network is transported over the purple network. On the right, the path of the orange and green service run over a single link in the purple network. This is also a SPOF, because when the last purple line breaks, both services go down.

The IMS SPOF functionality performs such assessments. Since IMS understands the protection schemes and the relation between the different networks, IMS will highlight SPOF’s after calculating the network topologies and the customer services.

Screenshot from SPOF analysis in IMS:

IMS Product description

Below a screenshot of an example SPOF in IMS Network Map. Two fiber cables are starting from different entries from the building, but are then going to the same manhole on the right near the building, then the fiber routes continue their own routes again, one going up, one going down. .

IMS Product description

23. Warehouse Management

The IMS Warehouse functionality primarily aims to control the movement and storage of materials within a warehouse and process the associated transactions, including receiving, put away and picking. It also directs and optimizes stock put away based on real-time information about the status of bin utilization. IMS Warehouse management involves the receipt, storage and movement of goods, to a final network or customer location. The power of real-time data in the warehouse minimizes the time spent on every task, while providing cross checks for accuracy at every step. Benefits include: • Improves overall warehouse efficiency, reducing labor costs • Reduces inventory stocking level requirements • Increases shipping accuracy • Enables efficient and accurate material tracking • Decreases the volume and cost of warehouse space

Each stock/warehouse and spares location has a unique name in the IMS database. IMS sees a difference between a warehouse and a spares location. This is because network materials used for spares in the fault-handling process may not be used by the service delivery process and vice versa.

23.1 Materials

A material is a piece of equipment (e.g. equipment shelf/chassis, card, DDF/ODF/Patch panel, etc.).

Each material has information related to it, like:

• Name: name of the material

• Description: description of the material

• Supplier: supplier of the material

• Vendor Code vendor code of the material

• Version: version of the piece of equipment

• Price: price of the material to buy this piece of equipment

• Status: Once a material is being ordered at the supplier, the material gets a status. The different statuses are listed below.

IMS Product description

• Status date: date of last status change

• PO number: number of purchase order

• Order number: order number in service delivery process

• Row/Rack/board: exact location of material in the warehouse location

• Requester: name of the person who requested the material in IMS application

• Remark: extra comment field

Barcode

At any time during the life-cycle of the material (e.g. in warehouse or in network) users can add a barcode to the material.

A barcode reader can be linked to the user machine, so that the barcode is transferred into the barcode field in IMS.

Status Explanation In Stock The material is stored in the warehouse and is not yet planned to go in the network yet. Ordered The material is being ordered at the equipment vendor. Reserved The material is in the warehouse and is reserved (for a project) to go into the actual network soon. In Stock The material is stored in the warehouse and is not yet planned to go in the network yet. Laid Out The equipment is being packed to be picked up. It will leave the warehouse any moment. Out Stock Material is not in warehouse anymore. Ready for Sale The material is in warehouse and will not be used in network anymore. It will be sold. Sold The material has been sold to an external party. Returned Something is wrong with the material and is returned to vendor. Defect The material is defect and needs to be fixed or replaced.

IMS Product description

23.2 Material list

The materials that can be ordered at suppliers and materials that are in stored in the warehouses are defined in the so called “material list”.

IMS users (with appropriate user permissions) can add/edit or delete the items in the material list.

Additional to the standard fields related to a material, the following fields are linked to a material type that can be ordered:

• Deliverable: is this material (still) deliverable at the supplier.

• Serial No. Mandatory: is the serial number field mandatory to be filled in when working with this material.

23.3 Material template

A Material Template can be used in case the same group of different kind of materials is often being ordered.

The template groups the materials together so that the group of materials can be ordered with one click instead of many.

IMS Product description

23.4 Order list

After a PO number is available (through IMS or through Financial System), equipment can be ordered at the supplier.

To select the equipment to be ordered the order list form can be used.

After materials have been selected, the order list must be committed.

23.5 Material actions

Ordered materials that are delivered by the supplier can be booked in / placed into the warehouse.

In the same form, users can also:

- Book out materials: Materials that are being picked up to leave the warehouse

- Send materials to repair: Defect materials can be sent to equipment vendor to have them repaired or

Replaced.

- Ready for Sale: Mark equipment “ready for sale” if materials are not going to be reused and

to be sold to third party.

23.6 Reserve equipment

In case equipment is needed for a service delivery order, the specific materials can be reserved from the warehouse for a project/order.

23.7 Materials ready to be picked up

After materials have been reserved, one or more materials can be selected that are ready to be picked up. Those materials will get status “Lay out”.

23.8 Book out Materials

When the materials are being picked up at the warehouse the logistics employee must “book out” the material from the warehouse.

Next to the normal process of booking out materials, materials can also be booked out without a material reservation.

IMS Product description

23.9 Cable Management

Cables are handled a little bit differently in the warehouse functionality compared to equipment.

23.9.1 Cable types

Different types of cables can be registered.

Per cable type the following information can be related:

• Supplier: Name of the supplier of the cable

• Vendor code: Code that is used when ordering the cables

• Cable type: type of cable, e.g. Multi-mode, Single-Mode, Coaxial

• Connector type A: Type of connector on one end of the cable.

(e.g. BNC, RJ45, E2000, FC/PC, SC/PC, etc.)

• Connector type Z: Type of connector on other end of the cable.

(e.g. BNC, RJ45, E2000, FC/PC, SC/PC, etc.)

• Duplex type: Type of duplex (if applicable)

• Length: Length of the cable

• Price per piece: Cost of one cable

• Minimum quantity Minimum stock level. In case quantity of cables in warehouse go below this amount, warnings will be send to logistics department to order new cables of that type.

23.9.2 Other actions around cables

The cables can be ordered like other materials under a PO number.

Cables can be booked in/out, similar as other materials.

23.10 Warehouse to Network Inventory

Network items can be moved from warehouse to the network inventory (service delivery process).

New node/equipment:

When registering new (to be) installed equipment in the inventory a pull-down field becomes selectable and will generate a list of material of the equipment type currently in stock in the warehouse.

New/change card: Right mouse clicking a node slot allows the selection of a card in stock in the Warehouse.

IMS Product description

23.11 Network Inventory to Warehouse

Network items can be moved from Network Inventory to the Warehouse (decommission process).

Dismantle equipment: Dismantle or removing node/shelf/card or other material can by “moving” the node back into stock in the Warehouse.

Replace equipment: In the Fault Handling process, defect materials can be replaced/swapped. This is normally done using the Spares Warehouse location. See also chapter 24 - Spares Management.

23.12 Reports

All different kind of reports available related to warehouse. Examples are:

o Lead time equipment supplier

o Stock levels per site

o Stock levels per equipment type

o Stock levels per cable type

o Automatic warnings when stock level drops below threshold value

Next to the standard reports, users can also create customized reports. If so desired reports can be end to email once or every period of time.

24. Spares Management

With the Warehouse functionality spare materials can be managed as well.

IMS supports:

- Spare Management locations (sites)

- Equipment list (node, cards) per vendor

- Management of spare equipment per location

- Ordering spare equipment at vendor

- Monitoring of spare equipment deliveries from vendor

- Easy swap of materials in case of defect materials

- Automatic Reports, see chapter “Reports”.

See also chapter 23 for the full warehouse functionality.

IMS Product description

25. Reports

IMS supports different kinds of reports:

- Predefined reports

- Customized reports using Report Query form

- Scheduled reports sent via email

- SQL based reports in SQL Report form

Reports can be created using all data in the IMS database, examples are - Connection capacity reports; - Port capacity reports; - Data quality reports; - Trend reports; - Workflow Order / Process / Lead time reports; - Trouble Ticket and Network Availability reports; - Planned Work reports; - SLA (Service Level Agreement) KPI reports; - Inventory / Asset reports; - User activity - and more. The reports are managed in two different report forms, Report Query form and SQL Report form.

Report Query Form

Via this form users can use preconfigured reports that have been tailored for your organization.

Users may create and customize reports so that personal or department report requirements are fulfilled. These personal reports can be saved and scheduled if so desired.

SQL Report Form

Via this form users can use preconfigured reports that have been tailored for your organization.

Users may create their own SQL reports using SQL statements. These reports can be saved and scheduled (sent via email) if so desired.

All reports can be exported to excel.

IMS Product description

26. Bulk changes

When there is need for uploading a large amount of data of the same kind (e.g. new connections, connection routing, new equipment, etc.) this uploading can be done via the “bulkloader” in IMS.

From a MS Excel (in structured format) the data can be copied into the bulkloader form.

IMS will import the data with the same business rules as implemented in the GUI.

IMS Product description

27. Flexible fields and tabs

Within minutes IMS Admin users can create extra tab pages and fields. There is no need for a new IMS version, these actions can be done in existing Graphical User Interface (GUI).

Tab parameters:

- In which form this new tab needs to be implemented

- Tab name

- Link to which table in the database

Field parameters:

- Name of field

- Field type (e.g. text, numeric, date, formula)

- Condition tab/field is shown (e.g. when speed = “2MB” or node type =”Cisco 7206VXR”

- Position of field in tab page

- Field dimension in tab page

- Combobox dropdown values (optional)

- Standard value

- Empty value allowed?

IMS Product description

28. Interfaces to other systems

IMS supports multiple types of interfaces to other systems and software applications. This chapter describes what types of interface are supported and high-level how these interfaces work.

Typical types of applications IMS interfaces with are:

- Network Management Systems

- Alarm Management Systems

- CRM systems

- Workflow / Order management systems

- GIS systems

- Billing systems

Interfaces to customer owned applications can be created as well.

IMS Product description

28.1 Network Management System Interfaces

This paragraph provides information regarding interfaces to the Network Management Systems (NMS), Element Management Systems (EMS) and directly to the Network Elements (NEs)/Equipment.

28.1.1 Types of Interfaces

VC4-IMS supports multiple types of NMS/EMS and NE interfaces. Some examples:

- CORBA (Common Object Request Broker Architecture)

- RESTful based interfaces

- MTOSI

- TL1

- Interfaces based on XML (Extensible Markup Language)

- SNMP

- CLI/Telnet/SSH;

- Flat files (txt, csv);

- Vendor Proprietary interfaces;

- Database to database interfaces.

28.1.2 Network Reconciliation and Auto Discovery

The most common purpose of an interface to a NMS, EMS or NEs is Network Reconciliation and Auto Discovery.

IMS will take a snapshot of the NMS/EMS and NE data and compare this data with the data in the IMS database.

This is normally performed once day, however this could to run more or less frequent.

Reconcile Process

Below steps describes the reconcile process:

1. Each night IMS collects data from NMS/EMS and/or NE’s.

2. The network data will be stored in the IMS Reconcile table in the database

3. Each element (e.g. equipment, connection) has a unique link ID to NMS/EMS/NE.

4. Connections running over multiple platforms can have different NMS/EMS/NE ID’s, so IMS knows exactly which part of connections should be synchronized.

5. IMS will query/compare the data in “reconcile” table with the “normal” IMS.

IMS Product description

Two options in case of differences between NMS – IMS:

1) Auto-discovery IMS corrects data automatically in IMS database.

2) IMS shows the difference in the reconcile form.

The frequency of the reconciliation process can be set by the IMS Admin user (e.g. daily at a specific time, weekly).

Auto-discovery

Some information IMS can correct the data in IMS database automatically.

Examples are:

- New equipment in actual network, but not yet in IMS

- New connections in actual network, but not yet in IMS

- New inserted cards in actual network, but not yet in IMS

- Serial numbers not (correct) in IMS database

- Software/Hardware versions

- Etc.

Customer may decide which objects will be automatically discovered or reported as a mismatch.

IMS Reconcile form

Some information cannot be corrected automatically.

A Network engineer must check first whether IMS is correct or NMS is correct.

The differences between NMS and IMS will be shown in the IMS Reconcile form.

Examples are:

- Equipment type differences

- Connections with a different routing

- Connections on different ports

- Card differences

- Cards that are deleted in NMS, but still “in service” in IMS

Users can correct these kinds of discrepancies using the IMS GUI.

IMS Product description

28.1.3 Auto provisioning from IMS into NMS/EMS or NE

VC4-IMS can also be integrated to the network to do auto-provisioning. That means the services will be planned in IMS first, then IMS pushes the information to the NMS/EMS or NE’s to build the services in the network.

Below a schematic overview.

28.1.4 Service Fulfillment

The IMS workflow can be used to automate the processes around auto provisioning to automate the Service Fulfilment.

Each type of service can have its own process (customizable by users with correct permissions), so that the workflow process can be used to decompose standard services into smaller steps and automate actions that follow a fixed rule.

See chapter 19 for more information related to IMS Workflow.

IMS Product description

28.2 BSS/OSS interfaces

External BSS/OSS systems can be linked to VC4-IMS using different kind of interfaces, such as:

- Web-service API's

- TMF RESTful Inventory

- SNMP

- Database to database interfaces;

- Flat files (txt, csv);

- Proprietary interfaces

28.2.1 Alarm Management System Interfaces

In case an Alarm Management System, such as IBM Tivoli/Netcool, HP TeMIP, Centina vSure, is being used by the operator an interface can be created to receive and maybe correlate the alarms coming from NMS/EMS or NE’s.

A simple interface could be to push the inventory data from IMS to the Alarm Management system.

A more comprehensive interface is a webservice interface between the two systems. In case of an (filtered) alarm in the NMS/EMS/NE the Alarm Management sends requests to IMS. IMS creates a Trouble Ticket automatically and performs impact analysis to identify the impacted services and customers.

IMS will send the information back to the Alarm Management System.

28.2.2 Customer Resource Management System (CRM) Interfaces

When a CRM system is being used, the customer data in this CRM system will be the master. Once an interface is created between the two systems, IMS can make use of this customer data.

This customer information can then be linked to inventory objects.

Normally this is a simple interface to extract data from the CRM and synchronize it with IMS.

Optionally the CRM system can also read from the IMS database, using the IMS web-service interface or using a simple database view.

A CRM can also start the workflow in IMS, once a customer wants a new service or a change.

IMS Product description

28.2.3 Interface between IMS and Financial Systems

To keep all the company’s assets and its related financial values up to date, it is most important to keep the network inventory, warehouse and financial systems in sync. This may sound easy, but it is not always the case. Since many people, and so many of the employees of your company, follow the path of least resistance, procedures may not be followed all the time and assets get lost.

When the financial system is not properly linked to the inventory and warehouse system, there is no asset control and multiple site surveys will be necessary to get a view of the current assets.

How to control the assets:

- Build interfaces to all the different network vendors (NMS/EMS/NE’s) to synchronize the actual active network assets in VC4-IMS. This will guarantee 100% correct asset view of all active components.

Since VC4-IMS manages the active and passive equipment and the relations between them, network reconciliation and automatic discovery will also support to control the passive equipment.

- Manage the materials in the warehouse using VC4-IMS warehouse functionality (see chapter 23)

- Build an interface to the financial system (such as Oracle Finance/ERP, or any other financial system).

Often materials have different names in network, inventory and ordering. VC4-IMS can handle multiple names for the same item to overcome this problem.

- In case there is no standard naming convention in place: introduce proper naming convention for locations and equipment.

- Make use of serial numbers and/or own barcode system or combination. Serial numbers are often used for active equipment, so that this information can be retrieved from NMS/EMS/NE without the need of pulling cards out of the equipment (and causing service interruption).

- Daily reconcile the financial system with the VC4-IMS application.

- Run data quality checks to keep also passive equipment inventory up to date.

28.2.4 Interfaces to other types of applications and databases

Most other types of OSS/BSS interfaces are customized interfaces. Examples are interfaces to existing Workflow systems, Trouble Tickets, Billing systems, GIS systems, etc.

Each company is different and uses different systems and procedures. So, what an interface to VC4-IMS needs to do, will also vary per organization. That is why our experienced team will be available to discuss with your organization how to build the most efficient interface to optimize the data flow.

IMS Product description

28.3 IMS Webservice API’s

External systems can interface with IMS using the web-service API’s.

With the IMS web-service interface any external system can:

• Read IMS data

• Create IMS data

• Edit IMS data

• Delete IMS data

Examples of existing API’s are, but not limited to:

• Create country

• Delete country

• Retrieve country data

• Create city

• Delete city

• Retrieve city data

• Create new customer

• Delete customer

• Retrieve customer data

• Create Location

• Delete Location

• Retrieve location data

• Create node

• Delete node

• Change status of node

• Retrieve node data

• Add shelf in node

• Delete shelf from node

• Change shelf status

• Retrieve shelf data

• Add card in node

• Remove card from node

• Change card status

• Retrieve card data

• Change status of connection

• Relate connection to port

• Remove connection from port

• Relate connection to bearer connection

• Remove connection from bearer connection

• Retrieve connection data

• Retrieve bearer connection data

• Create new OLO connection

• Change status of OLO connection

• Relate OLO connection to location

• Remove OLO connection from location

• Relate OLO connection to connection

• Remove OLO connection to connection

• Retrieve OLO connection data

• Create Order / Initiate Workflow (Service Fulfillment)

• Edit Order

• Create Trouble Ticket and start IMS fault impact analysis

IMS Product description

29. User-groups and permissions

In IMS a single user belongs to a so-called user group. A user group is a group of users focused on the use of one or more particular functionalities. IMS has a method of assigning permissions/access rights to these specific groups of users.

29.1 Users and User groups in IMS

A user group is used to group multiple users with same user permissions. Per user group permissions can be set per IMS screen and per part of screen. These groups are managed within the Menu Permissions form.

Examples of User groups:

o Read-only

o Equipment build

o Connection build

o Site Management

o Administrator

The IMS admin user can create/change these user groups.

One user may belong to one or more user-groups.

29.2 Database domains

Global and/or larger telecom providers might have the need to have different database domains. For example, a separated database domain per country or island.

VC4 can create such database domains, so that the organisation can have one single network planning and inventory system but with different IMS database schemas.

IMS Product description

30. IMS Architecture

30.1 Database and application

Application

The VC4-IMS software is a web-based application and can be opened using most common web browsers.

There is no need for additional client installation, a web browser is enough.

Database

IMS runs on an Oracle database. Oracle 12 is recommended, but older versions are also supported.

30.2 High Availability

The IMS solution can be built in a high available environment.

Prerequisites for High Availability

1) Redundant hardware and software at both the primary and data replication sites.

2) Provide identical hardware and software configurations at each site.

30.2.1 Architecture

This paragraph describes the architecture that is needed in an IMS environment with high availability.

Server locations In a normal availability environment, one server location is enough to install the IMS servers.

High availability: Two different server locations will be needed to guarantee high availability. One location will be the primary site. The other location the backup or Disaster Recovery (DR) site.

Connectivity

On the next page, a schematic drawing of the connectivity.

IMS Product description

Oracle Servers

The main Oracle database server must be installed on the primary site.

The backup Oracle server must be installed on the DR site.

In High Available IMS environment Oracle RAC may be used or Oracle DataGuard software to protect the data.

Application Servers

IMS users run the IMS application on the Application (web) servers or on user machines in case of client-server users.

The Application server will connect to the active Oracle server.

In a high available IMS environment minimum quantity of application servers is two.

Mediation servers

When network reconciliation towards NMS/EMS and/or NE’s, one or more Mediation Servers need to be implemented.

One server can manage between 5-10 NMS/EMS/NE interfaces. A second server is needed for redundancy purposes or in case of larger number of interfaces.

WebService servers

For OSS/BSS interfaces (like interfaces to CRM, Billing, Alarm Management, Performance Management) a separate server needs to be implemented.

30.3 VPN

To be able to provide maintenance on the application and database VPN access will be needed from VC4 office to the IMS Environment.

--- end of document ---

websiteIOADMIN Mei 20, 2020 Admin Bandung Indonesia