Download PDF
Amica reduces software deployment times by 95 – 98 percent
Technology Category
- Application Infrastructure & Middleware - API Integration & Management
Applicable Functions
- Discrete Manufacturing
Use Cases
- Predictive Maintenance
Services
- Software Design & Engineering Services
The Challenge
Amica, a mutual insurer providing auto, home, and life insurance, was facing issues with its software deployment processes. The company's environment included numerous web services, multiple web apps, and core applications. With dozens of developers checking in code, deploying the correct version of each service and application to multiple test, production, and backup environments had become extremely difficult. The process of ensuring the proper version of the right code was installed correctly on each environment had become a logistical nightmare. When issues arose with the deployment, they were often caused by application inconsistencies, rather than a code defect.
About The Customer
Amica is a mutual insurer that provides auto, home, and life insurance. The company's environment includes numerous web services, multiple web apps, and core applications. Dozens of developers were checking in code, which the company then had to deploy to multiple environments. The process of making sure that it deployed the correct version of each service and application to numerous test, production, and backup environments had become extremely difficult.
The Solution
Amica created an Application Configuration Management (ACM) team, which implemented IBM UrbanCode Deploy software, integrating it with the company’s existing open source tools. The team worked with the Client/Server Infrastructure (CSI) team to use the IBM UrbanCode software to create repeatable deployment processes that help it deploy the correct versions of each web service and application, along with the correct version of all the dependent code, which significantly reduces compatibility issues. Using IBM UrbanCode Deploy software, the team can then re-create a deployment quickly. As part of a more comprehensive DevOps approach, the ACM also embedded static code analysis tools into its build and deploy processes. The tools analyze code every time it’s checked into the company repository, and if it doesn’t meet a certain quality threshold, the tools reject it. This process helps prevent defects from being deployed in the first place.
Operational Impact
Quantitative Benefit
Related Case Studies.
Case Study
Remote Monitoring & Predictive Maintenance App for a Solar Energy System
The maintenance & tracking of various modules was an overhead for the customer due to the huge labor costs involved. Being an advanced solar solutions provider, they wanted to ensure early detection of issues and provide the best-in-class customer experience. Hence they wanted to automate the whole process.
Case Study
Predictive Maintenance for Industrial Chillers
For global leaders in the industrial chiller manufacturing, reliability of the entire production process is of the utmost importance. Chillers are refrigeration systems that produce ice water to provide cooling for a process or industrial application. One of those leaders sought a way to respond to asset performance issues, even before they occur. The intelligence to guarantee maximum reliability of cooling devices is embedded (pre-alarming). A pre-alarming phase means that the cooling device still works, but symptoms may appear, telling manufacturers that a failure is likely to occur in the near future. Chillers who are not internet connected at that moment, provide little insight in this pre-alarming phase.
Case Study
Aircraft Predictive Maintenance and Workflow Optimization
First, aircraft manufacturer have trouble monitoring the health of aircraft systems with health prognostics and deliver predictive maintenance insights. Second, aircraft manufacturer wants a solution that can provide an in-context advisory and align job assignments to match technician experience and expertise.
Case Study
Integral Plant Maintenance
Mercedes-Benz and his partner GAZ chose Siemens to be its maintenance partner at a new engine plant in Yaroslavl, Russia. The new plant offers a capacity to manufacture diesel engines for the Russian market, for locally produced Sprinter Classic. In addition to engines for the local market, the Yaroslavl plant will also produce spare parts. Mercedes-Benz Russia and his partner needed a service partner in order to ensure the operation of these lines in a maintenance partnership arrangement. The challenges included coordinating the entire maintenance management operation, in particular inspections, corrective and predictive maintenance activities, and the optimizing spare parts management. Siemens developed a customized maintenance solution that includes all electronic and mechanical maintenance activities (Integral Plant Maintenance).
Case Study
Asset Management and Predictive Maintenance
The customer prides itself on excellent engineering and customer centric philosophy, allowing its customer’s minds to be at ease and not worry about machine failure. They can easily deliver the excellent maintenance services to their customers, but there are some processes that can be automated to deliver less downtime for the customer and more efficient maintenance schedules.
