A buy-side client required an advisor to lead a discovery effort to identify potential business gaps and risks related to an internally-developed data warehouse architecture. This data warehouse architecture was utilized to meet a number of business use cases, including managing custodian trade communication, pre- and post-trade compliance checks, process exception notifications, managerial reporting, and cash management (including cash recon). Virtually no documentation, either business process or technical, had been developed or maintained as the data warehouse was built and evolved. In addition to identifying gaps and risks, the client required plans for implementing both immediate tactical and long-term strategic solutions to prepare for an anticipated growing business. Near- and long-term plans must include a full analysis of effort, cost, and suggested prioritization.
Analyze the internally-developed data warehouse architecture to:
- Identify all business use cases served by the data warehouse.
- Define all data warehouse objects, including batch processes, tables, functions, views, stored procedures.
- Articulate all upstream and downstream dependencies; data objects and business use cases.
- Evaluate efficacy of employing the data warehouse to solve business use cases vs. utilizing functionalities within existing transaction systems.
- Provide a recommendation, including near- and long-term goals for migration of business use cases to appropriate transaction systems, as applicable. The recommendation should include effort, cost, and prioritization suggestions.
- Defining the ‘boundaries’ of the internally-developed data warehouse architecture required an in-depth discovery period, often necessitating line-by-line code analysis to understand the relationship between data ‘objects.’
- Given the enormity of the number of ‘objects’ within the data warehouse, it was necessary for TenDelta to develop a separate database to model the relationships and interdependency of the data warehouse objects, and relate those object relationships to business use cases.
Process Change Management
- Defining a plan to migrate business use cases from the data warehouse to other transactional systems required careful planning.
- It was vital that process change choreography for business use cases minimally disrupt in-production processing.
- Plans to move business use cases to transactional systems needed to simultaneously consider the business impact as well as the data model impact. Certain business use cases were prioritized over other to create positive business impact while simultaneously setting the stage to streamline data model changes.
- Clearly articulating both the long-term vision as well as the immediate tactical benefit was important in obtaining upper management stakeholder buy-in.
- TenDelta’s approach to the client’s business need was backed by decades of syndicated loan and data modeling expertise.
- An understanding of the syndicated loan market’s history and trajectory as well as a deep knowledge of data transformation and optimization informed the analysis process and ultimate recommendation.
- TenDelta’s ‘vendor agnostic’ approach to the analysis process allowed the client to rest assured that TenDelta’s recommendation would be driven by client need, rather than by vendor feature set.
TenDelta analyzed the client’s internally-developed data warehouse architecture, and articulated near- and long-term plans to accomplish the client’s business goals. TenDelta’s recommendation provided a path to employ new integrations and streamline business processes. The client has implemented TenDelta’s recommended approach, and has engaged TenDelta’s expertise for numerous subsequent projects.