TBM Framework & Taxonomy

 View Only

  • 1.  TBM to CSDM mapping - Where to put Identity and Access Management?

    Posted 01-26-2023 03:17
    Hi All,
    We have adopted TBM on ServiceNow using CSDM.

    We have mapped as follows:

    Business Service Portfolio (customer facing)
    • Workplace
    • Business (here we are using TBM Extension for Insurance Industries)
    • Shared & Corporate

    Technical Service Portfolio (reserved for IT only - not customer facing)
    • Delivery
    • Platform
    • Infrastructure

    The above works perfectly except when it comes to some service/offerings in:  Delivery > Security & Compliance > Identity & Access Management

    We obviously don't want to hide this from our business customers.  Access management is definitely something we need to cater for on the business side.

    Everything else splits cleanly .. any suggestions for where we should put this or have I missed something.

    Any input would be welcome - thanks!

    ------------------------------
    Mark Smith
    Snr It Specialist
    Old Mutual
    0823074079
    ------------------------------


  • 2.  RE: TBM to CSDM mapping - Where to put Identity and Access Management?

    Posted 01-26-2023 03:36
    I have thought of two possible solutions:

    1) Business Service Portfolio > Workplace > Connectivity & Access Management (expand existing connectivity)

    Why here?
    Connectivity is for your device to connect to the company network and access is for the user to authenticate using that device.

    OR

    2) Business Service Portfolio > Business Services > Identity & Access Management (new)

    Why here?
    Most of the access requests are for Business Applications.

    ------------------------------
    Mark Smith
    Snr It Specialist
    Old Mutual
    0823074079
    ------------------------------

    Original Message


  • 3.  RE: TBM to CSDM mapping - Where to put Identity and Access Management?

    Posted 01-27-2023 11:55
    If you must place some TBM "Business" Type​ solutions (eg Workplace, Business, Shared & Corporate) into the CMDB's Technical Service Portfolio or "Technical" Type solutions (eg Delivery, Platform, Infrastructure) into the CMDB's Business Service Portfolio, that should still allow you to roll-up the offerings into your TBM-managed Solutions taxonomy as long as the entry placed into the Portfolio table has a 1-to-1 match to your TBM Solution Name to roll-up to its proper Solution Category and onto Solution Type.

    The above approach should accommodate any extensions since all Solution Names are unique and roll-up to one Solution Category. If you happen to create any custom Solution Names, be sure to maintain the uniqueness for Solution Names.

    This approach will also cause a conflict of Solution classification/reporting between TBM and the CMDB. In other words, the CMDB will represent some as Business solutions while TBM represent them as Technical and vice versa. Not a show-stopper, but may cause some communication issues later.

    Regardless, the TBM program should be positioned as "king" when representing the true classification of all solutions.

    ------------------------------
    Matt Temple
    Transformation Excellence Manager
    Accenture US - Partner
    Long Beach CA
    (714) 349-6102
    ------------------------------

    Original Message


  • 4.  RE: TBM to CSDM mapping - Where to put Identity and Access Management?

    Posted 01-30-2023 03:59
    Hi Matt,
    Thanks for taking the time to respond.  Much appreciated.  We shall proceed cautiously.

    ------------------------------
    Mark Smith
    Snr It Specialist
    Old Mutual
    0823074079
    ------------------------------

    Original Message


  • 5.  RE: TBM to CSDM mapping - Where to put Identity and Access Management?

    Posted 03-24-2023 03:58
    Edited by Svein Selstø 03-27-2023 03:37

    Hi  Mark,

    I think this is a question about how you understand services. In our adoption of TBM to CSDM we have acknowledged that technical services are representations of technical domains or describing the IT basics in a technical context. Technical services are IT Towers described in a service context. In the TBM taxonomy you find the following introductions:

    Delivery solutions are those to build, deploy, support, and operate the Workplace solutions, Business solutions, and Shared & Corporate solutions. Development services create and change business-facing services, typically through projects. Additional support and operations services assist users and ensure the availability of the business-facing services.

    Infrastructure solutions include the core infrastructure - facilities, compute, storage, and network services - that are required to deliver any technology automation. Typically, these are not directly consumed by users. However, for some IT operating models, a shared "infrastructure and operations group" may directly provide these Infrastructure Services to their customers.

    Platform solutions include the application infrastructure (database, middleware, etc.) that enables business-facing applications and services. Typically, these are not directly consumed by users. They are components required by the end user, business application and shared application services (see below for the latter two types). However, for some IT operating models, the shared "infrastructure and operations group" may directly provide these Platform Services to their customers.

    From this we have taken the approach that technical services are building blocks for Business Services. A technical service may support another technical service (e.g. Data Network supporting Physical Compute in a Data Center) but can never become a Business Service. This lies in the nature of the definition of a technical service - it is defined in a technical context.

    A business service should be defined in a business context - in other words - focusing on business outcomes and business value. So therefore we define new services capturing the business outcomes and value perspective of the service and place them in a business service portfolio. We also acknowledge that although the main component of this new service is the technical service we also need to add in other technical services as building blocks (e.g. Service Desk for support issues). 

    An example:

    The technical service 'Compute on Demand' could support a business service named 'Cloud Server on Demand' with a service offering 'Azure on Demand'. This service also includes support - the Service Desk delivery service. In the Business service portfolio the 'Cloud Server on Demand' needs to be defined in  a business context with business outcomes and value it supports.

    In the CMDB you are able to build models supporting the technical services (using ci relations and dynamic ci groups) bundling it all nicely into an application service an relate to one or more business service offerings.

    So - I think key is; technical services are defined in a technical context and are building blocks for business services defined in a business context. 



    ------------------------------
    Svein Selstø
    Senior Business Consultant
    Sopra Steria - Norway
    Oslo
    004791796593
    ------------------------------

    Original Message


Related Content