restaurant01

Come dine with me

Controlling and optimising Business Intelligence applications can be a dry topic even for some of us who work in the domain of BI & Analytics.  This shouldn’t limit consideration of the problem area as there can be significant challenges for organisations with associated costs if the challenges are not addressed.  When we think of various analogies that could be used by way of illustration one scenario to consider involves an imaginary restaurant, “Chez Metrique”, from inception to maturity.

OK, following the commitment to invest in Chez Metrique and a period of concentrated effort by the team to design, develop & prepare, the restaurant launch has gone well; customer reviews are positive and bookings are encouraging.  Looking beyond the bright, busy dining room into the kitchen the stations are pristine and organised and processes well-defined.  The staff are appropriately skilled, have a clear understanding of their roles and communicate effectively with each other.  The output is of high quality, delivered promptly by front-of-house and well received by appreciative diners.

So far so good. Chez Metrique is buzzing.

Of course, from this point in time there are many possible outcomes.  For this scenario, let’s take the common path and peer through the restaurant windows 5 years hence.

Unfortunately, it’s not an encouraging sight.  Only a few people are dining – and with a long spoon.  The once-bright and appealing décor has faded and the buzz has gone.  Pan through to the kitchen and there’s a picture of disorganised endeavour.  The remaining cooks, although doing their best, are working without method or direction and producing meals that should carry a health warning.  Regulators (Environmental Health), if aware, would close the place down in a heart-beat. The once-promising enterprise has turned sour through a managerial inability to adapt to shifting demands and sustained under investment.  Chez Metrique is done.

What a waste of potential, resources, effort & time.

There’s a good chance that another restaurant / café will start up on the same site within a few short months.  Will they repeat the journey of Chez Metrique?

And so to the parallel with Business Intelligence & Analytics programmes.  Often there is an initial directed focus with the aim of supporting a strategic business initiative.  The capability is promoted by positive executive sponsorship and transitioned successfully into business-as-usual (BAU) for on-going support & maintenance.  However, all too often that team is under-resourced and, over time, with the pressure of new initiatives being prioritised the quality levels degrade.  Inconsistencies creep-in to data, metrics, reports & dashboards, it becomes harder for BI consumers to locate, understand and trust the integrity of the information they need. The catalogue of objects expands with increasing duplication and redundancy.  Control slips away and what was a key information asset is now a liability.

Most BI applications start out like this restaurant kitchen.

Many are somewhere in between... could benefit from a deep clean, revised menu and restoration of trust rather than being left unvisited and destined to be shut down.

The application may persist for some time as the effort and cost to regain control, clean-up & optimise is judged to be too great; but it’s in a fugue state.  At some point though, after long-term decline, the zombie app will be replaced with a shiny new set of tools at not inconsiderable expense.  Will the organisation’s approach change to investing in people and resources too?  In many cases, not.

It’s clear that chronic technical debt and poor governance contribute to bad outcomes, be it a promising start-up restaurant or an organisation seeking to use BI & analytics for competitive advantage.  Rinse, repeat & fail.  It’s a path followed by many; but, thankfully, not all.

What are your experiences as a consumer of BI or analytics, developer, analyst or manager? What kind of fayre is being served up in your organisation? I welcome your thoughts.

Inspect

This page provides a developer or analyst with the facility to inspect all captured information relating to an element and is available within the Analysis module.

Inspect is comprised of the following panes:

Selection Options

Explore

Compare

Visualize

Annotations

Usage

Selection Options

Explore

Compare

Visualize

Annotations

Usage

Editing or Deleting an Instance | Product Module

Editing or Deleting an Instance | Product Module

Edit

Follow these steps to edit an existing Instance | Product Module:

  1. move the mouse-pointer over the edit link on the appropriate table row and click.
  2. amend the Instance Name and/or Instance Description and click on Save to commit or Cancel to return to the Instances tab.

Delete

Follow these steps to delete an existing Instance | Product Module:

  1. move the mouse-pointer over the delete link on the appropriate table row and click.
  2. a confirmation dialog box will be displayed with "Yes" and "No" buttons. Click on Yes to proceed with deletion of selected Instance | Product Module or No to return to the Instances tab.

Tip: exercise caution when deleting as this change cannot be undone.

Adding a new Application Instance | Product Module

Definition: An Application Instance is a specific occurrence of an application of a Vendor's software in a distinct environment. For example, there may be a SAP BusinessObjects "Sales & Marketing" BI application that is implemented in 3 environments, e.g. Development, Test and Production. Each application + environment combination is referred to as an "Instance".

A Product Module is a module within a BI or Analytics software product, e.g. SAP BusinessObjects Web Intelligence Documents, SAP BusinessObjects Universes or Power BI Service, amongst many examples.

Adding an Instance | Product Module

Follow these steps to create an Application Instance with relevant Product Module:

  1. first select a relevant Product Module for which meta data will be captured.
    Tip: the values listed in the Product Module control are populated based on available adaptors. The concatenations of <Vendor | Product | Product Module | Version> are distinct.
  2. next, enter a unique name into the Instance Name field, e.g. "Sales & Marketing (Prod)"
  3. enter a meaningful description
  4. click on the Save button
  5. the adjacent table Current Instances | Product Modules will be updated with the new addition.

Persisted Data Refresh

NB: once a change has been applied to an Instance | Product module it is important that the application data is refreshed. To do this, position the mouse-pointer over the data refresh icon in the top right corner of the page and click.

Explore

This page enables an analyst or developer to search all of the captured meta data associated with a selected Product Module and one or more Instances.

Selection Controls:

This is where the scope of the initial search is set.

Figure 1: selection controls

To select the scope of search, undertake the following tasks:

  1. select a single a Product Module from the dropdown control. The Instance dropdown will be populated with valid values.
  2. select one or more Instances from the dropdown control using the checkboxes. The table underneath the Instance control will be populated with Parts that are present in the selected Instances.
  3. select one, more than one or all Parts using the checkboxes.
    Note: by positioning the mouse-pointer over a column header and right-clicking the mouse button, a local column filter will be displayed which enables a search to be applied to the Parts table. Click away from the table to hide the filter.

Analysis Overview

The Analysis module is designed to enable the exploration of captured meta data in order to achieve rapid insights. Accessed via the topline tab menu or through guided navigation from the Home page, the following pages are available:

Figure 1: Tabs available under "Analysis"

Explore: enables retrieval of nodes, attributes and values from multiple instances of a selected Product Module. For example, search for all occurrences of a key word (e.g. "discount") or object type (e.g. query) across SAP BusinessObjects instances for Finance and Sales & Marketing.

Inspect: provides a facility to view captured meta data, usage data and applied annotations relating to a single selected Part (e.g. dashboard, analysis, report or semantic layer). Furthermore, visualizations are available to view the Object Model of the selected Part or view as a hierarchical tree or treemap. It is also possible to view the similarity of the selected Part against all other parts within the relevant Instance.

Query: this is where a user can write, save and re-use their own SQL queries to interrogate the meta data repository.

Visualize: a range of chart and diagram types are available to support insights into lineage, hierarchical relationships and structures between and within BI & Analytics Parts.

Installation Guide

To install Metoscope, you will need the following:

  • a valid license key
  • a minimum of 10 Gb free disk space
  • a minimum of 2 Gb free memory
  • Windows 7 operating system or above
  • an internet browser such as Chrome, Firefox or IE
  • Administrator privileges on target PC

 

Once the pre-requisites are met, carry out the following steps:

  1. Download the Installation package from the Download Center at: Click to open installation packages folder
  2. Double-click the downloaded installation package file to start the Wizard.

Contact Us

Want to keep the conversation going?  Just share your details and we'll send you our latest insights and trends in the Data and Analytics Governance space.

Metonomy-logo-wide-white

Copyright 2026 Metonomy Ltd. ©

All Rights Reserved

Follow Us