HMS faced challenges with their manual deployment process that was time-intensive and error-prone, especially for Informatica objects. They worked with CA to create custom actions for CA Release Automation to automate their deployments of Java, DB2, and Informatica. This improved efficiency by reducing deployment times by over 50% on average and increased quality by automating approvals and providing full logs.

1. World®
’16
HMS Delivers Sleek Deployments
via CA Release Automation
Tim Gaston - Director, Change Management - HMS
Lionel Bailey - Lead Release Engineer - HMS
D05X14S
DEVOPS

2. 2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type
of warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.
For Informational Purposes Only
Terms of this Presentation

3. 3 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Abstract
Organizations are increasingly challenged to deliver applications quickly
and precisely, necessitating production code deployments take place
faster than ever before. The same holds true for HMS, a healthcare cost
containment solutions company that helps payers improve
performance.
Using innovative technology, as well as powerful data services and
analytics, HMS solutions cover the entire payment continuum from
eligibility verification to payment accuracy to fraud identification,
prevention, and education. This session will cover how HMS pioneered
an automated deployment alternative using CA Release Automation
driven by the need to counter the time and labor-intensive nature of
traditional deployment approaches, particularly for Informatica objects.
Tim Gaston
HMS
Director, Change
Management
Lionel Bailey
HMS
Lead Release Engineer

4. 4 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Agenda
ABOUT HMS
HMS’S DEPLOYMENT CHALLENGES
INFORMATICA-SPECIFIC DEPLOYMENT CHALLENGES
INNOVATIVE APPROACH OF CA AND HMS
RESULTS
1
2
3
4
5

5. 5 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
HMS offers the broadest range of
cost containment solutions in healthcare to
help payers prevent fraud, waste, and abuse;
save money; and improve performance.

6. 6 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Federal Programs
§ Centers for Medicare and
Medicaid Services
§ U. S. Department of
Veterans Affairs
§ Department of Defense
Health Plan Programs
§ Medicaid Managed Care
Organizations
§ Medicare Advantage plans
§ Group and individual plans
§ Self-funded employers
State Programs
§ Medicaid agencies
§ CHIPs (Children’s Health
Insurance Programs)
§ State employee health
benefit plans
Who We Serve
Healthcare Payers

7. 7 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
§ Eligibility verification
§ Payment Accuracy
§ Fraud identification and prevention
§ Cost savings
§ Performance improvement
§ Provider education
Results
HMS Drives

8. 8 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
HMS’s Deployment Challenges

9. 9 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Build and Deployment Challenges
Manual
release
process
Problematic
Informatica
deployments
Disconnected
Java, DB2, and
Informatica
for same
application
Multiple build
for the same
app across
different
environments
Artifacts
stored in file
system

10. 10 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Informatica-Specific Deployment
Challenges

11. 11 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Informatica-Specific Deployment Challenges
Three Conventional Approaches and Inherent Risks
Informatica CLI
§ Supply commands and
credentials manually or via
pre-defined script
§ Not ideal for credential
security
§ Increased error risk due to:
§ Repeat all steps for each
deployment
group/component
§ Manual intervention
§ No visual representation of
scripts obfuscates process
Informatica GUI
§ Manual execution
increases risk of error
§ Unpredictable, lengthy
deployment time
§ Advisable to create
exclusive lock on repository
to prevent repository
conflicts (Undesirable since
it prevents other services
and processes from
updating non-related
objects)
XML Export/Import
§ Prone to errors since all
inputs explicitly provided at
time of deployment
§ Required input:
§ ID export location
§ Import
§ Choose export folder
§ Resolve conflicts
§ Indicate workflow
reusability
§ Assign integration services

12. 12 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Innovative Approach of CA and HMS

13. 13 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
CA Release Automation and New Actions
§ CA Release Automation could interact with Informatica’ s
CLI, but had no pre-defined actions
§ CA and HMS worked hand in hand to create actions that
simplify Informatica deployments
HMS selected CA Release Automation to streamline Java, DB2,
and Informatica deployments

14. 14 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Key Workflow Highlights
HIGHLIGHT BENEFITS
Generic workflow for
Java, Informatica, DB2
Unified app deployment across technologies and generic enough that all apps
comply with common deployment process
Simple new app set-up
Prep two manifest XMLs and user group permissions (as opposed to developing
environment & app-specific build and deploy scripts)
Pre-promotion flow
Build, CA Workbench approval, Change Request approval (ServiceNow) tightly
coupled
Artifacts maintenance
Build artifacts are stored in the CA Release Automation repository, simplifying
rollbacks

15. 15 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
App Deployment Process via CA Release Automation

16. 16 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Sample Workflow in CA Release Automation

17. 17 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Results

18. 18 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Results
Category Metrics
Baseline
Before CARA
Results After
CARA
% Improvement
Efficiency Weekly Thursday release process time (Avg 20 Apps) 7 Hours 3 Hours 93%
Number of deployment scripts for 100+ applications 450+ 80 82%
Time to deploy one Informatica deployment group 10 Minutes 3.6 Minutes 64%
Average time to deploy single Java application 23 Minutes 10 Minutes 57%
Time to stage DB2 deployments for production release 1.5 Hours 30 Minutes 67%
Time to create weekly Harvest Package Approval (SCM) report 45 Minutes 5 Minutes 94%
Quality Validate name and number of packages to deploy Manual Automated
Verify approvals & dependencies, build & deploy release Manual 15% Manual 85%
Deployment log reporting 1 truncated log
Full build &
deploy log

19. 19 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Questions?

20. 20 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Recommended Sessions
SESSION # TITLE DATE/TIME
DO5T19S
GM Financial Builds a Sustainable, Holistic, Continuous
Delivery Practice
11/17/2016 at 04:30 pm

21. 21 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Must See Demos
Modernize
App Delivery
Integrated CD
Theater 5 - DOV501P
Deliver Test
Data Faster
Test Data Manager
Theater 5 - DOV511P
Deliver
Better Apps
Service Virtualization
Theater 5 - DOV507P
Orchestrate
Your Release
Release Automation
Theater 5 - DOV513P

22. 22 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Thank You!
Stay connected at communities.ca.com

23. @CAWORLD #CAWORLD © 2016 CA. All RIGHTS RESERVED.23 @CAWORLD #CAWORLD
DevOps – Continuous Delivery
For more information on DevOps – Continuous Delivery, please
visit: http://cainc.to/PiTFpu