The Need for Digital Asset Governance
Over time, digital assets of different types can grow extensively. In a typical organization, engineering teams could be split into sub-teams and units to better manage individual pieces of work. When teams work parallelly to speed go-to-market strategies, each team would take measures to deliver their tasks by implementing applications and complex internal technology modules.
These could comprise APIs, services, microservices, events, policies, and many more. These assets will often have dependencies and other forms of relationships. Multiple teams in the enterprise could be using the same technology platform for each of their products, their own installations on infrastructures of choice, or even different multi-vendor platforms. The latter could well be the case especially in medium- and large-scale enterprises, where there are multiple teams, business units, and other types of team segregations that span across different countries and regions. In such instances with wider distribution, it becomes challenging to keep track of what is being developed, what has already been developed, as well as the dependencies and associations of various artifacts. Enterprise architects and development managers should be aware of these details to make prudent decisions on new developments.This is illustrated below.
Figure 1: Asset distributions across multiple teams
How can you maintain these details? How can you keep track of the states of currently developed artifacts?
Clearly, there is a need for a central location to access this valuable information. Does a spreadsheet solve this problem? Well, it could; however, it would quickly become increasingly difficult and tedious. How could such a central document be managed to make sure the entries are consistent, integrity is maintained, and the values are up to date?
It is also in the best interest of the enterprise to avoid redoing the same work and efficiently architect the assets so that duplication is avoided. If this is not done correctly, over time, an enterprise will incur ‘technical debt’—i.e., costs associated with additional rework caused by choosing an easy (limited) solution now instead of using a better approach that would take longer. How can you address this and modernize the platform if the right information is not within your reach?
A governance solution can solve this problem. It can be the center of excellence (CoE) for an enterprise’s digital assets. It will undoubtedly unfold the challenges that enterprises have in finding all the metadata of these large numbers of assets in one place. Moreover, it will bring in a unified view of all the assets across all the teams. The return on investment (ROI) in a governance solution will be in the form of maximizing asset reusability, streamlining the asset architecture, and saving time in finding details of assets, which would otherwise be scattered. On average, a governance tool could bring in 30% ROI year-on-year by reducing precious time spent by managers in finding details and by reducing duplication of work. This results in improved efficiency.
A governance solution thereby helps execute key business drivers, including speeding go to market by reducing repetitive work and enhancing the quality of work via the governance mechanism in the development process. Development managers and enterprise architects—who want to make decisions based on statuses of currently built digital assets and who want to know how to leverage existing assets—would greatly benefit from such a powerful tool to make quick decisions compared with scrolling through lengthy documents and sheets.
Merely cataloging asset metadata is not the only requirement here. The governance solution should have capabilities to maintain dependency details, association views, and categorize assets for easy filtering. It should also be extensible to define new asset types that can be used as data models and business objects. The solution should also allow operational extensibility to add, modify, read, or delete assets. When an asset’s state changes, taking additional steps would give pragmatic agility to the solution. Thus, a good asset governance solution should provide means to architect this extensibility to open up programmability.
A distributed asset ecosystem, as shown above, will have a large number of assets and the challenges mentioned above will be applicable to it. An enterprise using such a platform will eventually create a large number of services, APIs, event streams, business processes, schemas, policies, and many more such ‘digital assets’. Multiple teams may work parallelly and could also be using different deployments. The problem of ‘technical debt’ and inefficiency, owing not being able to view the overall picture, would only worsen unless there is a unified place to view these assets and govern them
The following diagram illustrates how a central governance tool can provide a 360-degree view of an enterprise’s assets.
Figure 2: A distributed asset ecosystem with a unified governance solution
The Value of WSO2 Digital Assets Governance
WSO2 Digital Assets Governance is a modern enterprise digital asset governance solution that is tailor-made to work across multi-vendor systems in a more pragmatic style without cohesive boundaries. This loosely coupled way of seeing an enterprise's assets mitigates risk for other products. The tool has minimal dependencies for its deployment and availability. WSO2’s offering is a cloud-hosted on-demand solution that can easily work together with different systems.
WSO2 Digital Assets Governance is an ideal solution for product managers, development managers, and enterprise architects. Typically, product managers want to have a clear view of what the product consists of. For example, a software product may require APIs, services, streams, and even libraries. In a technology ecosystem, these artifacts will reside in different multi-vendor products. Product managers should have the details within reach to make the right choice for the product they are responsible for. A central repository of metadata information is key to that, and this is a vital component of WSO2’s governance solution.
A development manager needs to keep track of the dependencies of a module and ensure timely delivery of a development asset with quality in mind. A development manager must ensure that developers follow guidelines, such as documentation for completed features and committing test codes before promoting the code to the testing state. Ensuring quality releases, with strict governance mandating documentation and test codes, will reduce many hours of bug fixes and save considerable support costs. This, in turn, will lead to increased ROI in the future. The lifecycle tool in a governance solution can be used to make sure the lifecycle transition only happens when the required checklists are in order. Furthermore, the lifecycle tool can help keep track of asset contract renewals and end-of-life (EOL) and could lead to lowering support costs by more than 20% year on year.
An enterprise architect can find existing assets and utilize existing systems to solve higher-level business problems or make decisions to bring in new vendor systems; this can be the case if there is no existing system that can address present architectural needs. In the longer run, decisions made by enterprise architects will have a drastic effect on the the overall business architecture’s efficiency. To make decisions, they need to have information in a central location.
Imagine the case of a newly hired architect who wants to know about the entire platform’s assets, vendor systems, APIs, and details about what they provide, with documentation linked to document management systems. With a governance solution, an architect can get up to speed in half the time. The solution can also help to advise developers to utilize some assets and take appropriate decisions about new architectural requirements.
WSO2 Digital Asset Governance could thus leverage the governance requirements of multi-vendor integration ecosystems. It can sit in the cloud and can be used to onboard assets by leveraging REST APIs. Enterprises can make use of external tools such as CI/CD pipelines or other integration means to extract details from any vendor system, which often have REST, SOAP, or other interfaces, to extract metadata details and populate WSO2 Digital Assets Governance using the solution APIs. This is shown in Figure 3.
Figure 3: Onboarding assets to and from the governance solution
As highlighted above, a governance tool provides a birds-eye view of assets and helps reduce ‘technical debt’. It can help save USD10k-USD20k or even more in a year depending on how the digital assets are scattered and linked to form a formidable output. WSO2 Digital Asset Governance helps an enterprise to achieve this goal and does much more than cataloging data. Of course, the unified view itself is a great advantage and it unfolds the challenges of having the data documented elsewhere. Once the metadata is in place, a number of tasks around these metadata instances of each asset can be accomplished.
WSO2 Digital Assets Governance also provides the following key capabilities to support common governance requirements.
- Custom asset types for business objects and data modeling
The solution can capture metadata of most widely used assets. These include REST APIs, Open API specifications (Swagger documents), SOAP services, Web Service Description Language (WSDL) files, XSDs, and XML Policy files. However, it is often the case that we do not know some artifact types and their attributes beforehand. Thus, a governance tool should provide a powerful way to model business objects to define their attributes and minimize the work to generate an interactive UI to make users capture these details. This will be a powerful approach to define whatever the new type of assets that need to be defined and quickly start using it. WSO2 Digital Asset Governance provides a comprehensive XML-based model to model new asset types.
- An extensible lifecycle model to attach assets
A lifecycle state of an asset is a variable. Based on different use cases, different lifecycle states could be applicable. Thus, a governance tool should provide a way to define lifecycles and attach that to a defined asset to keep track of states. This way, the tool does not need to predefine states and restrict designers to adhere to what the tool provides. This is a powerful mechanism to define dynamic state charts. WSO2 Digital Assets Governance provides an authorization model to tie permissions on promotions and demotions that can be performed on the asset lifecycle. Only authorized personnel would be able to make changes. Also, it provides a way to dynamically plug logic while the state is transformed. This capability opens up an integration point to extract details from the asset data together with the lifecycle state and initiate a meaningful data population to other systems.
- Associations and dependencies for impact analysis
Associations and dependencies are two more functionalities that can be defined and be used to visualize the impact of asset changes, which in other terms is called ‘impact analysis’. The solution should provide ways to define new dependencies and also control defining meaningful dependencies. Once these design-time dependencies are defined, a user can easily visualize the associations to draw insights about the impact on changing one of those assets.
The following diagram illustrates the dependency view of WSO2 Digital Assets Governance.
Figure 4:: Visualizing dependency
- Powerful search capability
When assets are cataloged, there should be easy ways to quickly search for them. WSO2 Digital Assets Governance provides a comprehensive search capability. A user can search assets by asset content or a particular attribute value. A powerful yet easy to use syntax can be used in the search bar to filter out assets easily. This is essentially useful when enterprises have hundreds of thousands of assets in the asset portfolio.
- Taxonomy for asset categorization
Categorizing assets will make filtering easy. It would also be ideal if the solution could also provide means to define how that categorization hierarchy should be. WSO2 Digital Assets Governance allows XML models to define such a directory, such as a hierarchy, and assign it to assets. Subsequently, when an asset is added or modified, a user can assign the asset to one or more of the categories. This will generate a user interface in the store portal for users to easily filter assets. This could be combined with the search to quickly narrow down what users are looking for. Enterprises can come up with their own taxonomies or adhere to commonly used ones that suit their industry.
In addition to the taxonomy, the solution also provides easy tagging of assets, which can also be used to filter out assets quite easily.
Today, enterprises are striving hard to stay ahead of the competition by engaging in digital transformation efforts. In medium and large-scale organizations, using multi-vendor technologies will create a large number of digital assets. As these numbers grow, it becomes difficult to know, search, and make decisions for future assets and projects.
A vendor-neutral governance solution—which can work across multi-vendor systems to bring asset catalogs and present a unified view—is advantageous as it enables development managers, product managers, enterprise architects, and even CxOs to draw useful insights about the hard work that has been put into an enterprise’s digital transformation. Such a solution helps to minimize technical debt and efficiently reuse assets, which, in turn, will save time and money. WSO2 Digital Asset Governance is a tailor-made solution to address all these needs.