The BIAN Service Landscape Timeline gives and general overview what the completion of the BIAN Service Landscape (SL) v.3.0 – v.5.0 contains.
Assessing or Implementing a Point Solution
A member case study would follow the targeted solution approach for a narrowly defined aspect of the business, covered by one or more business scenarios and a small number of associated Service Domains.
A member case study would cover a product launch in a similar manner to a Point Solution, involving a small number of business scenarios. In addition, the broader Service Landscape identifies interested, influencing and impacted areas of the business for broader launch planning and coordination purposes.
Core Systems Repurposing
A member case study covering Core or Legacy repurposing would relate to the first solution option described in the previous sub-section (Section 22.214.171.124 point 1) and would be a good confirmation of the ability to use BIAN partitions and designs as a blueprint for a legacy system wrapping solution.
Application Portfolio Rationalization
A member case study would involve matching applications to the service domain capabilities to reveal gaps, duplication and misaligned applications in the overall portfolio, then using the mapping to do like-for-like comparisons of competing applications with respect to their coverage of individual service domains.
Mergers & Acquisitions
Similar to Application Portfolio Rationalization, a member case study would involve matching applications from different organizations coming together to the service domain capabilities to reveal gaps, duplication and misaligned applications in the overall portfolio, then using the mapping to do like-for-like comparisons of competing applications within the organizations with respect to their coverage of individual service domains.
Vendor Solution Alignment
A member case study covering a vendor solution integration where the vendor offering corresponds to a targeted solution and the Service Domain and Semantic Service designs are used to develop a high level functional checklist and interface definitions. The target solution will be used differently by banks and software vendors:
For the Bank – it is used to define required functional content coverage and interfacing. Compliance with the evolving standards can also be a measure of the level of commitment a supplier has to standards.
For the Software Vendor – solutions that align to the generic BIAN Service Domains can be consistently mapped to requirements for multiple deployments, enabling better solution re-use and ease of integration.
A member case study would involve using the Service Landscape as an investment planning framework. Different service domains can be evaluated in different ways to provide a backdrop for planning and prioritization. For example, costs can be allocated across the landscape to expose the relatively high cost areas where investment to improve efficiency could have the highest impact.
BIAN Service Domains can in practice be sourced externally since Service Operation interactions can be supported. A member case study would use the Service Operations as the basis for supporting an outsourced arrangement. Outsourcing decisions can be evaluated by considering individual and groups of Service Domains across the landscape as candidates for flexible sourcing approaches.