Solution Toolkit data model

The Banking Solution Toolkit data model includes a banking specific data model built from IBM® InfoSphere® Banking Data Warehouse.

The following items are included in the Solution Toolkit data model:
  • 3 Catalogs, supporting hierarchies
    • Features which are the measurable or actionable things that can be done. For example, hierarchies, such as Feature Types-Main and Condition Types. IT is the main user of this catalog.
    • Sellable items which are the basic building blocks of Offers. For example, hierarchies, such as Products and Services-Main, Locations and Channels. Line of businesses are the main users of the catalog.
    • Offers which are what is presented and can be contracted. For example, hierarchies, such as Offer Types-Main, Channels, Locations, Market Segments, Products and Services. Marketing and Product Managers are the main users of this catalog.
  • Each catalog has 2 views.
    Development
    Enables editing outside of the workflow.
    Production
    Represents the expected view in a production environment where no data can be changed.
  • Each view has a set of tabs that utilize Attribute collections to control the display:
    • Compliance
    • Credit Risk
    • Eligibility
    • Feature Groups (Feature Catalog Only)
    • Features
    • General Top and Bottom
    • Legal
    • Marketing Top and Bottom
    • Pricing
    • Product Top and Bottom
    • Promotions
  • Each catalog has a set of workflows with a common structure and supporting scripts that enables these to work.
    Update {Feature/Sellable Item/Offer}
    Updates minor version of item and moves into the workflow.
    Create New Version of {Feature/Sellable Item/Offer}
    Clones item, increments the major version and 0's minor version, links clone to original, drops original from the workflow and moves clone into the workflow.
    Create New {Feature/Sellable Item/Offer}
    Creates a new item, gives it a temporary Name, saves the change, and then places it into the workflow.
    Create New {Feature/Sellable Item/Offer} from Copy
    Clones items, increments the major version by 1 and sets the minor version to 0, links the clone to the original, drops the original clone from the workflow and moves the updated clone into the workflow.

  • Each catalog has a Post Processing script that supports cross catalog activity and movements between tabs. The overall look and feel requires a Save between each tab so that the next tab can make use of any new knowledge.
  • Each of these workflows has the following common structure:
    Initial
    Scripting performs most of the functions described previously.
    Copy Rules
    For New Version, copies cloned ID to original item. If Operational Decision Manager is used, then any associated Operational Decision Manager Rule Sets are moved to the Dev branch.
    Create/Update
    Enables items to be changed.
    Approve (New items only)
    Demonstrates how approvals work. Approving moves the item to the next step, rejecting the items sends it back to the Create step.
    Merge Rules
    Moves any associated Operational Decision Manager Rule Sets to the production branch.
    Publish (Offer Catalog only)
    Publishes item to the physical MDM if this is enabled.
  • Each hierarchy has a similar set of workflows and structure.
  • The following functions were created and saved in the triggers/SharedFunctions.wpcs file.
    createID
    Generates the key for each primary spec.
    filterArray
    Removes items from a list that have already been used.
    formatDropDownValues
    Creates a common format for the categories or items. Creates a common format for when a String Enumeration Rule creates the list from either categories or items.
    getAttributeDropDownValues
    Passed an Item and the full path to an attribute that may have more then one occurrence, it returns a list of the values of the attribute in an array.
    getCategoryItems
    Returns the current version of a list of items in a tree structure.
    getHierarchyItems
    Returns the current version of a list of categories in a tree structure.
    associateMultipleHierarchyNodes
    Use the multi-occurring attribute in the attribute path to identify the Hierarchy Categories that the item is supposed to be in. Then, either add the item to that category if it is in the list, or delete it from the category if it is currently in the Category, but is not one of the multi-occurring attribute values.
    getHierarchyNodes
    Create the list of categories in an hierarchy, formatting each so that associateMultipleHierarchyNode can use it to locate the specific category. Returns the formatted category names in an array.
    updateItemWorkfow
    Executed in the INIT step of a workflow, this performs any required actions for all of the catalog workflows that update a category.
    createItemWorkflow
    Executed in the INIT step of a workflow, this performs any required actions for all of the catalog workflows that create a category.

  • Lookup Tables are also included and represent all of the tables used by the physical, virtual, and collaborative MDM, which provide the base for the consolidation.

Last updated: 5 Jan 2016