Modernizing Legacy Applications Boosts Efficiency and Business
公司规模
Large Corporate
地区
- Europe
国家
- Ireland
产品
- Branch Policy System (BPS)
- blive
- Natural Productivity Package
- Natural Engineer
- Adabas
技术栈
- J2EE
- MQ middleware
- Natural's API
实施规模
- Enterprise-wide Deployment
影响指标
- Cost Savings
- Productivity Improvements
- Customer Satisfaction
技术
- 应用基础设施与中间件 - API 集成与管理
适用功能
- 商业运营
- 销售与市场营销
用例
- 服务备件管理
服务
- 软件设计与工程服务
- 系统集成
关于客户
Hibernian General Insurance of Ireland, established in 1908, is one of Ireland’s largest and most respected insurers. The company has a business philosophy of providing competitive products and excellent service to customers. Consequently, the organization is constantly striving to improve operations. One of Hibernian’s key applications is its Branch Policy System—a character-based application used by internal administration and call center staff to service insurance brokers and policy holders. The company processes 800,000 policies representing 2 million transactions per year, with applications that support a Web channel but still take advantage of the legacy investment. About 2,000 users, in 400 brokers’ offices, use blive.
挑战
Hibernian General Insurance, one of Ireland's largest and most respected insurers, was facing challenges in serving insurance brokers and policy holders while reducing the time and cost to administer insurance policies. One of Hibernian’s key applications is its Branch Policy System (BPS)—a character-based application used by internal administration and call center staff to service insurance brokers and policy holders. To improve response times to these customers and reduce the costs of administering insurance policies, Hibernian decided to take a service-oriented approach and create a Web-based, easy-to-use interface that leverages and reuses existing key functionality contained within the business-critical Branch Policy application. Initially, Hibernian planned to replace its legacy application with an off-the-shelf general insurance package. However, over the years, there has been a large investment in this system which has provided users with a very high-level of functionality. This was found extremely hard to replace with an off-the-shelf general insurance package.
解决方案
Hibernian decided to extend the capabilities of BPS by creating a Web-based interface, blive, which takes advantage of key features of the existing application. The Web interface could reduce the costs of administering insurance policies by providing self-administration capabilities to brokers and give brokers and policy holders the ability to access information using the Internet. Hibernian also wanted to retain a single processing system with one view of the truth. To ensure flexibility to support these and future requirements, Hibernian took a service-oriented approach to extend the BPS application. First, Sinnott and his team decided to separate the BPS presentation layer and the database access layer from the business logic stored in the application. To achieve this, Hibernian used Software AG’s Natural Productivity Package, a set of tools for developing and maintaining Natural applications using a single, remote Windows-based development environment. Complementing the package is Natural Engineer, a maintenance and reengineering tool that let Hibernian restructure its existing application and reuse essential business logic.
运营影响
数量效益
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
相关案例.
Case Study
Developing Cutting-Edge Wireless Technology with NuCurrent and Altium Concord Pro
NuCurrent, a company known for its patented wireless inductive technology, faced a significant challenge as it grew. The company's technology is found in a variety of everyday essentials, from PopSockets® to smart basketballs and kitchen countertops. However, as the company expanded, it became clear that they needed a professional solution for PCB component library management and version control. Their existing system, GitHub, was proving to be inadequate for their growing needs. The lack of synchronization in GitHub made it difficult to reuse parts across multiple projects and changes were not getting propagated. This often resulted in issues being caught later in the development cycle, causing delays and inefficiencies. Furthermore, the company was using Google Drive and emailing files to clients, which created serious version control issues.
Case Study
High-Volume Service Parts Management Success with IBM and SAP
The case study revolves around the challenge of managing high-volume Service Parts Management (SPM) requirements in a competitive environment that demands greater efficiencies. Companies with complex SPM requirements are under pressure to integrate their manufacturing, inventory, and logistics systems more effectively to achieve significant cost savings. The challenge is further compounded by the need for a solution that can adapt to a dynamic, constantly changing environment, provide worldwide accessibility and visibility of information, and support operations ranging from small to very large service parts. The case study also highlights a specific request from a major German automotive manufacturer with a critical load requirement for order fulfillment.
Case Study
A German social services organization implements social program management solution to help protect children
The social services organization for a German city was facing challenges in managing child welfare services as demand grew in size and complexity. Much of its case management work was still paper-based so if a child moved, or a case manager left the organization or went on vacation, paperwork might not be transferred, or the case could be lost. Service provider selection was based on case manager experience and intuition rather than on systematic matching of providers with children’s needs. A lack of integration between case management and provider payment systems meant that payments might continue long after service provision stopped or after a child had moved or left the system.
Case Study
Streamlining Spare Parts Management: A Case Study on Cerapedics and eMaint
Cerapedics, a global bone-graft technology company, was facing a significant challenge in managing their inventory of over 750 spare parts. The company needed a system that would allow for efficient and strategic spare parts management. The existing system was time-consuming and labor-intensive, with workers spending valuable time navigating the inventory to find the right part for the right equipment. The company recognized the need for part tagging, location tracking, and a central organizing system for the storeroom. The challenge was to develop a system that would not only streamline the process but also ensure that critical spares were readily available during maintenance emergencies.
Case Study
Heavenly Cool Boosts Productivity and Efficiency with Commusoft
Heavenly Cool, a residential appliance repair service provider based in Parkville, Maryland, was struggling with a paper-based approach to dispatching. This traditional method was inefficient and lacked the flexibility required to handle last-minute cancellations and emergency call-outs. The company also faced challenges in managing their parts inventory and dispatching workflows. The lack of a streamlined process resulted in technicians making multiple trips to the warehouse, which affected the company's ability to add and tackle more appointments per day. Furthermore, the absence of a real-time vehicle tracking system made it difficult for the company to track the location of their technicians, which was crucial in case of a call in a specific area.
Case Study
Camunda BPM at DB Cargo
DB Cargo, the most productive freight railway in Europe, faced a significant challenge in long-distance, cross-border traffic - ensuring the reliable and on-schedule transport of cargo. As part of the European production alliance Xrail, DB Cargo aimed to optimize cross-border interoperability through a central broker and agreed process models. However, the initial architectural approach to connect DB Cargo to the Xrail production alliance proved inefficient. The business logic and technical functions required for the Xrail processes had to be distributed across all involved systems, leading to increased complexity in service orchestration and transformation functionalities.
