Kovair is now part of SurgeONE.ai | Same experts, even more power.

Month: December 2020

About TCS

TCS

TCS ensure the highest levels of certainty and satisfaction through a deep-set commitment to our clients, comprehensive industry expertise and a global network of innovation and delivery centers. Our mission is to help customers achieve their business objectives by providing innovative, best-in-class consulting, IT solutions and services and to make it a joy for all stakeholders to work with us.

We function as a full stakeholder to business, offering a consulting-led approach with an integrated portfolio of technology led solutions that encompass the entire Enterprise value chain. Our Customer-centric Engagement Model defines how we do engage with you, offering specialized services and solutions that meet the distinct needs of your business.

We build bespoke teams around your domain and technology requirements drawn from our talent pool of over 453,540 global professionals including 36.4% women from 147 nationalities. Our domain expertise has been built upon decades of experience working across industries and this knowledge underpins our suite of solutions.

Our organization structure is domain led and empowered to help provide Customers a single window to industry specific solutions. Agile industry units have embedded capabilities to enable rapid responses that provide a competitive edge to our Customers. This is coupled with a unique Global Network Delivery Model™ (GNDM™), spanning 40 global locations, that is today recognized as the benchmark of excellence in technology deployment.

We have made significant investments in Digital platforms and products spanning Technology Products, Horizontal Platforms and Products, Vertical Platforms and Products.

 

About Boozallen

boozallen

Boozallen are a global firm of approximately 27,600 diverse, passionate, and exceptional people driven to excel, do right, and realize positive change in everything we do.

We bring bold thinking and a desire to be the best in our work in consulting, analytics, digital solutions, engineering, and cyber, and with industries ranging from defense to health to energy to international development.

We celebrate and value diversity in all its forms; it’s something we truly value as a multicultural community of problem solvers. We believe in corporate and individual citizenship that make our communities better places for all.

We have one guiding purpose—to empower people to change the world. Our founder, Edwin Booz said it best: “Start with character… and fear not the future.” We bring a ferocious integrity to not only train our clients to tackle the problems they face today, but to help them change the status quo for tomorrow. Each day, we imagine, invent, and deliver new ways to better serve our employees, our clients, and the world.

 

Integration of ServiceNow & Azure DevOps for a Major Global Bank

 

Download eCopy
In the current DevOps ecosystem, the choice of platform and collaboration between cross-functional teams is critical for an organization. Response to Incidence and Change management is the key to DevOps collaboration. ServiceNow is a market leader for IT service management and Azure DevOps is being adopted by more and more enterprises. For those reasons, this case study for Kovair’s work for a major global bank adoption is a good example for other enterprises contemplating to follow in their path.

Unique Integration Implementation

Kovair Team along with the Bank implemented some of the unique as well as very complicated scenarios through Omnibus. These kinds of implementations are utmost challenging and could only be achieved through a rich and robust ESB platform like Kovair Omnibus. The platform needs to support both Correlation and Aggregation data patterns. Some of the Unique complicated scenarios are as follows
  • Populate Change request in ServiceNow based on Azure DevOps Work Item or Pipeline generation
  • Email sent activities in ServiceNow Item are synched into Discussions in Azure DevOps work item. The email content can be with header and content as Click link
  • Activating potential scheduling conflicts for a change request based on the configuration items (CIs), “planned start date”, and “planned end date” in scope for the change.
  • Syncing composite data – Change Request and the Link(s) attached (User Story, Task, Issue) from Azure DevOps Work Item to ServiceNow Change Request
Data is extremely valuable for an Organization like Bank, then extracting that data, interpreting it and orchestrating between two diverse system is of utmost challenge! This implementation at this global bank is far beyond normal data integration done through normal ESB platform.

Business Value

The ServiceNow Change management integration with Azure DevOps will help the Bank to delegate appropriate changes to the IT environment effectively and much faster than before. Moreover, this ecosystem will also ensure that all day to day scheduling conflicts for a change request based on the configuration items (CIs) are mitigated through automation. The tracking and honoring the Change management workflow helps the bank to bring the changes in the end system effectively which otherwise may have experienced delays before their work can be deployed to production. Kovair Omnibus platform helps to achieve these end-to-end relationships cutting across the tools. It also provides complete data for management reporting highlighting all the insights – that will help development and operations work more closely together as part of their journey to DevOps.

Ecosystems and the bridge between them

ServiceNow solution for Change Management helps an organization to understand the risk and work on it to minimize risks of changes to the IT environment. Overall, it is the process responsible for managing all changes to the production operations environment from inception to completion. These days, Change Management is viewed as an essential organizational process. Azure DevOps is a platform for Development and Collaboration. It helps to connect different products, projects and teams associated with product development from testing to deployment. Typically, the internal teams manage User Stories at the early stages of development and Change request for the live production system in Azure DevOps. Managing Integration between two ecosystems, where at each end there are complex workflows, rules and data is a big challenge. It requires a very deep level data integration where data flow across tools will create virtual workflow across the tool to achieve the business goals. Kovair team worked with the bank for a few weeks and have achieved an optimum integrated system using Kovair Omnibus. The integrated system manages ServiceNow workflow, conflicts scheduling detection and configuration items resolution completely from Azure DevOps.
Ecosystems and the bridge

Complex Business Cases

Managing ServiceNow Template based on Azure DevOps CR TypesManaging ServiceNow Template based on Azure DevOps CR TypesBoth the systems – Azure DevOps and ServiceNow are deeply integrated, and as a result dynamic Change Request types are mapped with ServiceNow Change Management templates like Standard, Emergency and Normal. Moreover, Change Request when synced with ServiceNow as a Change Request – the additional fields that are populated as part of the dynamic template are synced back to Azure DevOps so that the internal team understands the Change Request type in ServiceNow and its related priority data. Kovair Omnibus provides complete support for sync back for any number of rich data to the source data smoothly.

Data Sync with Traceable Link Data Sync with Traceable Link Change Request from Azure DevOps Sync to ServiceNow contains all the related User Stories and Task to ServiceNow in tabular structure to provide 100% visibility to the ServiceNow user and help them understand the impact of a Change Request which has been synced to ServiceNow. Syncing rich traceable data needs a rich platform to implement the complex traceable data.

Detecting Conflict and Mitigation through automationDetecting Conflict and Mitigation through automationConflict detection in ServiceNow identifies potential scheduling conflicts for a change request based on the configuration items (CIs), “planned start date”, and “planned end date” in scope for the change. If a scheduling conflict occurs, conflict detection also checks for any related blackout or maintenance schedules and other active change requests to determine the scheduling conflict. Kovair Omnibus provides complete automation of raising conflict in ServiceNow from Azure DevOps.

Realtime Syncing of Work notes and CommentsRealtime Syncing of Work notes and CommentsServiceNow supports a rich set of end user attributes like Additional Comments, Work Notes, Email etc. as Journal attributes. ServiceNow Work notes attributes can be updated only by users with a specific role, whereas the Additional comments field can be updated by any user. This creates a separation between notes that are meant to communicate back and forth with the Azure DevOps. Kovair Omnibus supports all the different types of notes and Comments with its rich data.

Conclusion

Digital Transformation is driving many organizations to adopt deep level integration between heterogenous complex platforms to achieve organization of business flow. The bank being a very large organization adopted Kovair Omnibus based on its capabilities to gain significantly from these two systems and aligned themselves to achieve organization goal of rapid mitigation of complex changes in the production system and benefit their customers tremendously. The Bank holistically wants to ensure that changes are recorded and evaluated, and that authorized changes are planned, prioritized, verified, implemented and documented in a controlled manner.
Download eCopy

Jile is an Enterprise Agile Planning & Delivery product with DevOps capabilities in a single platform to help manage the end-to-end software delivery value stream from ideation to deployment.

Kovair JILE Integration Adapter

The Kovair Omnibus Adapter for JILE provides full scope of collaboration between multiple teams. When each team has the comfort of using the tools of their choice, greater efficiency and productivity can be achieved. Kovair Omnibus JILE adapter supports bidirectional flow of data between JILE and other tools.

The integration between JILE and other Portfolio Management tools provides real-time visibility into development progress for the required top-level requirements. Moreover, product teams will be able to link all user stories, task and test cases associated with the top-level Epics. This facilitates the collaborators to see the same data in the ecosystem, irrespective of what application they use.

Features & Benefits

  • Get faster feedback at every stage of the lifecycle and take corrective action to resolve problems proactively.
  • Better management of Scrum and Kanban projects to achieve business goals.
  • Managing stories, features, iterations and defects through integrations with other ecosystem tools.
  • Improves team efficiency through better collaboration across different teams and data synchronization between different tools.

Why Integrate JILE with Kovair?

  • Managing Portfolio – The integration between Kovair and JILE would enable enterprises to manage a portfolio of projects. It helps teams define and manage high-level strategy and business goals through processes such as Large Scale Scrum (LeSS), Agile Portfolio Management and more. The working team can link work based on the high-level goals.
  • Team Collaboration – The Kovair adapter for JILE was developed understanding the fact that every software development and delivery team is different and need a customizable approach. Thus, the integration between Kovair and JILE is a flexible, generic solution that meets the needs of every team. Teams pick the high – priority user stories, drill them down into small tasks, estimating the tasks and stopping when they’ve reached the amount of work to which they can commit for that time period. Instead of planning the iteration in advance, Kanban teams define how many user stories they can work on at any given time.
Entities Exposed Events Collected Actions Supported Relations Supported
  • Story
  • Feature
  • Initiative
  • Task
  • Release
  • Iteration
  • Issue
  • WorkItem (Available in Kanban Type Work Areas)
  • Story
  • Feature
  • Initiative
  • Task
  • Release
  • Iteration
  • Issue
  • WorkItem
  • Story
  • Feature
  • Initiative
  • Task
  • Release
  • Iteration
  • Issue
  • WorkItem
  • Story to Features
  • Story to Release
  • Story to Iteration
  • Feature to Release

Use Case Example – Integration between JILE and JIRA

Kovair Omnibus JILE integration allows seamless collaboration between JILE and JIRA, and provide complete visibility to the management, across multiple projects. For example, an Epic is created in JIRA and is broken down into features. The epic along with its relationship with features will get synchronized to JILE. In JILE, an iteration, along with a story will get created against the Feature. Once the user story is finalied, the newly created user story will be assigned to the iteration. Next, the Story along with its relationship with Feature and iteration will get synced to Jira and will be related to the sprint in JIRA. Once the story is synched to JIRA, it will be assigned in JIRA by creating a Task for the story. Finally, this task of JIRA along with its relationship with the Story will again get synced to Jile.

Kovair Omnibus JILE