By delivering a comprehensive portfolio of software and services that spans the customer lifecycle, Amdocs enables service companies to deliver an intentional customer experience TM, which results in stronger, more profitable customer relationships. Service providers also benefit from a rapid return on investment, lower total cost of ownership and improved operational efficiencies. For more information, visit Amdocs at www. Although we believe the expectations reflected in such forward-looking statements are based upon reasonable assumptions, we can give no assurance that our expectations will be obtained or that any deviations will not be material. Such statements involve risks and uncertainties that may cause future results to differ from those anticipated. These risks include, but are not limited to, the effects of general economic conditions, Amdocs' ability to grow in the business segments it serves, adverse effects of market competition, rapid technological shifts that may render the Company's products and services obsolete, potential loss of a major customer, our ability to develop long-term relationships with our customers, and risks associated with operating businesses in the international market.
|Published (Last):||6 September 2014|
|PDF File Size:||10.98 Mb|
|ePub File Size:||4.43 Mb|
|Price:||Free* [*Free Regsitration Required]|
This project was completed for a major European telecom operator that provides cellular and landline telephone services, cable TV, Internet services, etc. The old API offered an ability to automatically manage only a small portion of services and products from the company's stack. Most of the offered services were documented in Amdocs Cramer OSS manually using the Wizards or pieces of documentation were shared between the systems.
In other words, there was no unified data storage. Having studied all the weak and strong points of the old API, it was decided to design and implement a brand new application programming interface new API that exposes high-level operations and conforms to modern enterprise standards and trends. The most challenging part of the project is related to deep analysis of company's business processes, which cover customer orders and network inventory management activities.
The business processes had to be investigated carefully, classified and then reflected to API operations, domain model and states of its objects. The project was coupled to the beginning of transition to new API on all dependent 3rd party systems. Which led to more activities for project timeline and phase planning activities. During the analysis phase of the project, we designed entities representing the domain model affected by the project scope , and it was decided to represent the business process for documenting services as set of atomic operations subprocesses.
Each operation is responsible for a small part of business process flow. Once the operation is completed, it moves all associated objects to certain state, while the next subprocess uses them as input objects. Thus, sequential and sometime parallel execution of the subprocesses leads the planned result.
For instance, in order to document a new service, which has been sold to a customer, the following sequence of sub-processes was extracted and designed: reservation of physical network resources on the company's side, documentation of the customer premises equipment, reserve IP addresses from the pool and VLAN ID on demand , document logical inventory to provide access to service ready network.
For each atomic operation we estimated the amount of activities to fulfill the subprocess. As a result, the following classification was designed: automatic subprocesses — closed loop operation which can be accomplished without any activities on engineer's side, semiautomatic — has to be served manually at some step for instance, a physical port has to be chosen manually , manual — complied fully by an engineer via Cramer OSS Task Engine.
Changes made by subprocesses can be adjusted or rolled back via "release" and "change" operations provided by the new API. For instance, when service is no longer required for a customer, it can be deleted from Cramer OSS as well as all associated objects.
This technology was chosen because it is a de facto standard for enterprise application and wide range of systems support it out of the box. Essentially, the web service acts as a buffer proxy tier. Once this phase is complete, all concerned 3rd party systems are going to be switched to the new implementation, access to the old API will be smoothly switched off.
On-site Analysis — the initial phase of the project involved a face-to-face meeting with the client and its project team to discuss the challenges, gather requirements, design the solution, and finally develop the high-level solution HLS document.
Cramer Customization — since the project touches business process, Amdocs Cramer OSS also had to be customized so as to meet new requirements. The documentation for the services is shared between several enterprise applications, and had to be extracted before the load. The Client This project was completed for a major European telecom operator that provides cellular and landline telephone services, cable TV, Internet services, etc.
The Challenge The most challenging part of the project is related to deep analysis of company's business processes, which cover customer orders and network inventory management activities. The new API has to cover the following key features Allow management reserve, release and change physical ports, nodes, etc. Provide by request 3rd party systems details about documented services, as well as physical and logical network inventory associated to them.
Client-server exchanging based on the SOAP protocol. Expose utility public operations which allow to retrieve object instances from the Cramer OSS object model. The new API and back-end solution has to meet high performance requirements. The Solution During the analysis phase of the project, we designed entities representing the domain model affected by the project scope , and it was decided to represent the business process for documenting services as set of atomic operations subprocesses.
The new API has to reach the following key points Significant increase in the amount and speed of processed data, thanks to wide range of automatic operations and high performance.
More accurate and precise documentation of the company's network inventory in Amdocs Cramer OSS, as a result more efficient customer support service. Support large portion of products from the company's stack which can be managed via the new API. Provide flexible solution for the cases of launching a brand new product: set of operations provided by the new API can be extended, and business-logic changed without significant efforts. Sub-Projects On-site Analysis — the initial phase of the project involved a face-to-face meeting with the client and its project team to discuss the challenges, gather requirements, design the solution, and finally develop the high-level solution HLS document.
Cramer Systems Unveils Cramer4 | Amdocs
Brian Buggy, Senior VP of Product Strategy at Cramer will present on the subject 'Inventory-centric OSS: removing the revenue log-jam' on Wednesday 7th February, illustrating how service providers are facing revenue 'log-jams' as a result of difficulties in converting complex service requests into billable returns. Outlining a number of customer case studies, Cramer will show how, by applying an inventory-centric approach and placing resource management at the heart of OSS, service providers can gain major returns on their network infrastructure. Having recently opened an office in Washington D. OSS World is the largest of the seven conferences TeleStrategies sponsors each year and is attended by over 3, people.
Cramer to Telecom Service Providers: | Amdocs
In August Amdocs announced the completion of the acquisition of the company. The company name is a combination of three letters from the names of Craton and Farmer, which they found to be a better option than the alternative combination of Farton. The company produced the "Cramer OSS Suite", a set of applications built around Resource Manager, an inventory of a company's telecommunications network infrastructure and configuration. Originally developed to administer networks such as SDH and PDH , the product grew to encompass almost all modern telecommunications technologies. A key feature of the product was being 'service aware': not only knowing what equipment is installed, the system knows what each system, module, card, interface or cable can do, which circuits or connections are configured on the network and which customer services use these connections. The latest two versions of the OSS suite uses Java as middleware platform for the GUI and some interfaces or adapters between the suite and external systems.
Cramer Systems to address OSS industry leaders | Amdocs