Skip to main content

HyperIntelligence and its Architecture

HyperIntelligence and its Architecture

When you open a web page the extension automatically scans web pages in your browser and underlines keywords that you can hover over to trigger cards. Cards present predefined KPIs associated with a selected keyword sourced securely from MicroStrategy.

This feature is similar to what we see in web pages particularly stock related web sites. 
MicroStrategy introduced HyperCards, a new object that is built, managed, and deployed using MicroStrategy Workstation(Not by using Developer or Desktop as far as I know). Cards can be consumed in a web browser via the MicroStrategy HyperIntelligence Chrome extension and on iOS devices via the MicroStrategy HyperMobile app. This feature can help the users to inject Zero-Click Intelligence (as it requires the users to hover only and no need to click!) about customers, products, people, and more directly onto words within websites or web application or emails. This feature can display the content through the mobile devices to bring answers through relevant, context-based analytics.
HyperIntelligence assists the users to find a report without logging into the environment and then allows to locate relevant information. It brings answers directly to you through contextualized text analytics that is as simple as hovering over a highlighted word.
HyperIntelligence can be an interesting and exciting feature for all levels of report/analytics users as they can see the reports as they type on in emails as below:

Salient features of HyperIntelligence:
  • Enables the text analytics that is as simple as hovering over a highlighted word in your email or web browser.
  • HyperIntelligence automatically scans every web page and underlines relevant keywords. Hover over a highlighted word to see insights in real-time.
  • Each card can seamlessly combine information from multiple enterprise assets and applications.
  • The extension supports multiple cards for different use cases. Each card can point to a different keyword. Simply click the extension icon to see the list of available cards or toggle individual cards on or off.
  • By default, the extension will work with any web-based content, however it is possible to blacklist individual websites - disabling the extension's functionality.
Microstrategy 2019 enhances the HypeIntelligence features further by introducing vision voice screen etc with the the new features like Hypevoice, Hyperscreen and Hypervision.

Hypervoice:

This feature allows the users to ask questions to get instant answers through voice commands in a similar fashion as you interact with Alexa. MicroStrategy integration with Amazon Alexa or Google Home (Not sure about Apple Homepod integration) to turn analytics applications into a voice-enabled personal coach. Which could boost productivity by blending insights into existing workflows. Developers can leverage MSTR APIs to integrate with voice-controlled applications like Amazon Alexa and Google Home. With MSTR-developed NLG and voice recognition mechanisms, it could be easy to get answers to the business questions on the way to the next meeting. By integrating with voice technology or chatbots, it’s easy to deliver the right data, fast.
No alt text provided for this image

Hyperscreen:

Hyperscreen enables the personalized insights on every wall(screen) you walk through. It can turn a screen into a dynamic, intelligent display that presents a personalized view of information based on who is standing nearby. It uses the new feature called Digital Identity to transform offices and facilities into spaces that inspire data-driven collaboration and action.

Hypervision:

Here, the magic comes by embedding analytics with virtual reality. Hold up your device for an augmented reality experience that overlays insights on objects and surroundings. Use image recognition to scan products and check inventory, or use GPS location to get an instant customer brief as you walk into your meeting.

Architecture 

The above workflow can be described as:
  • HypeIntelligence extension from Google Chrome browser submits a REST API request to MicroStrategy cubes by requesting topic(attributes!) and metrics.Data received from MSTR cubes to the browser is cached.
  • When the user open the browser and opens a web page or types text in emails or open emails. 
  • The extension finds matches and highlights those matching keywords.
  • Users hovers the highlighted keyword.
  • Extension displays the hypercard as designed.
  • Once the extension gets the data it caches the data and display the data in Hypercards whenever a user hovers on the key word highlighted.
 Deliver Zero-Click Intelligence
 Combine Information from Multiple Systems
 Support Multiple Cards
 Blacklist Individual Websites

The architecture for HyperIntelligence is similar to MicroStrategy Library. MicroStrategy Library is a client application running on a desktop browser or a mobile device, whereas HyperIntelligence is currently only available as a Chrome browser extension. 
If we compare this architecture with the old Microstratgey architecture we see the additional component of MicroStrategy Library which makes all the magic of HyperIntelligence.
 Single node architecture: 

Multi Node Architecture:

Comparison between Single node i-server and multi node i-server:

HyperIntelligence Workflow 

Hover effects won’t work on mobile devices because there’s no mouse cursor. To overcome this MSTR has handled mobile links with high color and shape contrast on them so that user will know where to tap. So that it displays the cards.
I have not yet explored this feature when the email goes to external users and the data level security(security filters) work as we are not passing any security filters.Handling of row level security on the cards is still a mystery!
Labels:

Comments

Post a Comment

Popular posts from this blog

Microstrategy Custom number formatting symbols

Custom number formatting symbols If none of the built-in number formats meet your needs, you can create your own custom format in the Number tab of the Format Cells dialog box. Select  Custom  as the Category and create the format using the number format symbols listed in the table below. Each custom format can have up to four optional sections, one each for: Positive numbers Negative numbers Zeros Text Each section is optional. Separate the sections by semicolons, as shown in the example below: #,###;(#,###);0;"Error: Entry must be numeric" For more examples, see  Custom number formatting examples . To jump to a section of the formatting symbol table, click one of the following: Numeric symbols Character/text symbols Date and time symbols Text color symbols Currency symbols Conditional symbols Numeric symbols For details on how numeric symbols apply to the Big Decimal data type, refer to the  Project Design Guide . ...
4 comments
Read more

Slowly Changing Dimension Types 0, 4, 5, 6 and 7

Slowly Changing Dimension Types 0, 4, 5, 6 and 7 Ralph introduced the concept of slowly changing dimension (SCD) attributes in 1996. Dimensional modelers, in conjunction with the business’s data governance representatives, must specify the data warehouse’s response to operational attribute value changes.  Core SCD approaches:  Type 1 (overwrite),  Type 2 (add a row), and  Type 3 (add a column).  Since legibility is a key component of the Kimball mantra, we sometimes wish Ralph had given these techniques more descriptive names, such as “overwrite” instead of “type 1.” But at this point, the SCD type numbers are part of our industry’s vernacular. We have written about more advanced SCD patterns, such as the 2005 article entitled “ Slowly Changing Dimensions are Not Always as Easy as 1, 2, 3. ” However, we’ve not consistently named the more advanced and hybrid techniques. With the third edition of  The Data Warehouse Toolkit  (Wiley, 201...
Post a Comment
Read more

Internationalization Design Technics

Microstrategy Internationalization Design Technics MicroStrategy supports data internationalization through two different techniques. You can either provide translated data through the use of extra tables and columns, or you can provide separate databases to store your translated data. These techniques are described below: You can support data internationalization in your database by using separate tables and columns to store your translated data. You can use various combinations of tables and columns to support and identify the translated data in your database. To support displaying the name of each month in multiple languages, you can include the translated names in a separate column, one for each required language, within the same table. Each column can use a suffix to identify that the column contains translated data for a certain language. The same LU_MONTH_OF_YEAR table with translated data for the Spanish and German langua...
Post a Comment
Read more

Personalizing file locations, email and file subscriptions using macros in Microstrategy

Personalizing file locations MSTr allows to dynamically specify the  File Location  and  Backup File Location  in a file device using macros.  For example, if you specify the  File Location  as  C:\Reports\{&RecipientName}\ ,  all subscriptions using that file device are delivered to subfolders of  C:\Reports\ . Subscribed reports or documents for each recipient are delivered to a subfolder with that recipient’s name, such as  C:\Reports\Jane Smith\  or  C:\Reports\Hiro Protagonist\ . The table below lists the macros that can be used in the  File Location  and  Backup File Location  fields in a file device: Description Macro Date on which the subscription is sent {&Date} Time at which the subscription is sent {&Time} Name of the recipient {&RecipientName} User ID (32-character GUID) of the recipient {&RecipientID} Distribution Services add...
Post a Comment
Read more

Prompt-in-prompt(Nested Prompts) in Microstrategy

Prompt-in-prompt(Nested Prompts) in  Microstrategy Nested prompts allows you to create one prompt based on the other and other bases on another, nested prompts allows us to prompt the highest level(Like year) to middle level(like Quarter, then to the low level(like Month). Here you can see how to  create a 3-level deep nested prompt that will prompt the user to select a year, then a quarter within that year, then a month within that quarter. Prompt-in-prompt is a feature in which the answer to one prompt is used to define another prompt. This feature is only implemented for element list prompts . The following procedure describes how to achieve this: Create the highest level filter. This is a filter which contains a prompt on an attribute element list. Create a filter on the attribute "Year." Click "prompt on attribute element list" and click "Next" through the rest of the screens to accept the default values. Do not set any additio...
3 comments
Read more

The logical table size calculation in Microstrategy

The logical table size calculation in Microstrategy The logical table size is an integer number that represents the granularity or level of aggregation of a particular table. It is called 'logical' because it is not related to the physical size of the tables (number of rows). It is calculated according to the attribute IDs that are present in the table and their level in the system hierarchy.   Even though, the number does not reveal the actual number of rows in the table, it is an accurate way of measuring a table size without having to access its contents.   MicroStrategy Engine utilizes an algorithm based on attribute keys to calculate the Logical Table Size (LTS):   Given the following tables:     The algorithm that calculates the table sizes performs the following steps: Calculate the number of levels per hierarchy: Hierarchy 1: 3 Hierarchy 2: 4 Calculate each attribute individual weight according to the level in the hierarchy (level in hierarchy/number of ...
Post a Comment
Read more

Fact tables levels tables in Microstrategy explained

Fact tables levels in Microstrategy: Fact tables are used to store fact data. Fact tables should contain attribute Id's and fact values which are measurable. All the descriptive information about the fact tables should stored in Dimension tables either in Star Schema fashion or Snow Flake Schema fashion which is best suited to your reporting solution. Since attributes provide context for fact values, both fact columns and attribute ID columns are included in fact tables. Facts help to link indirectly related attributes using these attribute ID columns. The attribute ID columns included in a fact table represent the level at which the facts in that table are stored. So the level of a fact table in the Fact_Item_Day_Customer can be the attribute Id's which is at Day, Item & Customer Id level. For example, fact tables containing sales and inventory data look like the tables shown in the following diagram: Base fact columns ver...
2 comments
Read more

Configure Connection Mapping in Microstrategy

Configure Connection Mapping in Microstrategy The following steps demonstrate the second scenario where two different data warehouses are used within the same project: Create two different database connections -                                                                                        One that points to the data warehouse for the European users                                                                 and the other that points to the data warehouse for USA users as shown below: Select Europe as the default database connection for the database Instance as seen below: Go to P...
Post a Comment
Read more
Star schemas and aggregate (or summary) fact tables Aggregate tables can further improve query performance by reducing the number of rows over which higher-level metrics must be aggregated.  However, the use of aggregate tables with dimension tables is not a valid physical modeling strategy. Whenever aggregation is performed over fact data, it is a general requirement that tables joined to the fact table must be at the same attribute level or at a higher level. If the auxiliary table is at a lower level, fact rows will be replicated prior to aggregation and this will result in inflated metric values (also known as "multiple counting"). With the above Time dimension table, a fact table at the level of Day functions correctly because there is exactly one row in DIM_TIME for each day. To aggregate the facts to the level of Quarter, it is valid to join the fact table to the dimension table and group by the quarter ID from the dimension table. Sql select DT...
1 comment
Read more

Uniquely identifying data using Compound Key in Microstrategy

Uniquely identifying data in tables with Compound Key attribute: The types of keys that can be assigned to a table include: • Simple key requires only one column to identify a record uniquely within a table. • Compound key requires multiple columns to identify a unique record. . The following diagram shows how the different key structures can be used to identify a cal...
Post a Comment
Read more