MicroStrategy ONE
Badge Resource Hierarchy
The attributes related to resources are specific to Identity transactions. Some of these attributes share common elements. For example, a door authenticated through the Identity server can be a Gateway as well as a Space. Sample reports at the end of the section explain the data.
lu_gateway
A Gateway is an access point that requires the authentication of an account. A gateway is a unique physical, logical, or Badge desktop resource into which the account authenticates. It is the consolidation of the data from the Application, Space, and Desktop tables. The columns are populated by the PACS system configured in Network Manager, the Logical Applications configured in Network Manager, or when a user configured the Badge Desktop client for unlocking personal machines.
If the transaction does not correspond to accessing a resource (for example, uploading a new badge photo or running a report in MicroStrategy) a default value of Not Applicable is assigned.
|
Column |
Description |
Data-Type |
|---|---|---|
|
gateway_id |
The numeric ID of the gateway generated by Identity server. |
bigint(20) |
|
gateway_desc |
The name of the individual physical, logical resource, or desktop machine. For example, Elevator A Office 365 MAC-JSMITH |
varchar(255) |
|
gateway_status |
The current status of the gateway. A gateway status can be: Active Deleted – deleted from Network Manager |
varchar(25) |
|
creation_timestamp |
The UTC timestamp when the gateways was first created. |
datetime |
|
modification_timestamp |
The latest UTC timestamp of the gateway modification. The value will continually change as the properties/configuration of the gateway changes. |
datetime |
|
logical_physical_flag |
A flag to indicate if the gateway is a physical, logical or desktop resource. This column is specific for the ETL and not included in the reporting schema. |
int(11) |
|
gateway_category_id |
The numeric ID of the corresponding gateway category. |
tinyint(4) |
|
network_id |
The numeric ID of the Network. All gateways are stored at the level of Network. |
bigint(20) |
lu_gateway_category
A Gateway Category is an automated categorization of the gateway populated through the Platform Analytics ETL. If the transaction does not correspond to accessing a Badge resource, for example, uploading a new badge photo or running a Report in MicroStrategy, a default value of Not Applicable is assigned.
|
Column |
Description |
Data-Type |
|---|---|---|
|
gateway_category_id |
The numeric ID of the gateway category. |
tinyint(4) |
|
gateway_category_desc |
A categorization of the gateway. Physical - PACS system Logical - logical web applications Desktop - Mac or Windows |
varchar(25) |
lu_application
An Application is a logical web application that requires the authentication from an account. For example, an Application could be Salesforce, Office 365, or Rally. For a full list of web application that can be configured with Badge, see Signing into Web Applications.
If the transaction does not correspond to accessing an application i.e. opening a door or running a report a default value of Not Applicable is assigned.
|
Column |
Description |
Data-Type |
|---|---|---|
|
application_id |
The numeric ID of the application generated by Identity server. |
bigint(20) |
|
application_desc |
The name of the logical application that an account authenticates into. For example, Rally Office 365 |
varchar(255) |
|
application_status |
The current status of the application. An application status can be Active or Deleted. |
varchar(25) |
|
creation_timestamp |
The UTC timestamp when the application was configured through Network Manager. |
datetime |
|
modification_timestamp |
The latest UTC timestamp of the application modification. The value will continually change as the properties/configuration of the application is updated. |
datetime |
|
network_id |
The numeric ID of the Network. All applications are stored at the level of Network. |
bigint(20) |
Campus > Facility > Floor > Space
The physical resource hierarchy is intended to provide a categorization for enriched analysis of the PACS system. The Space attribute elements are populated directly from values in the PACS system. The higher level attributes are manually added by the customer by following the steps to create a hierarchy of your Physical resources. The categorization is elective. If no categorization is found, default values will be provided.
lu_space
A Space is a physical building access point that requires the authentication of an account. The Space desc form is populated directly by the values in the PACS system. The PACS system is configured through Network Manager (see Configuring PACS).
|
Column |
Description |
Data-Type |
|---|---|---|
|
space_id |
The numeric ID of the space generated by Identity server. |
bigint(20) |
|
space_desc |
The name of the PACS access point. This value is imported directly from the PACS system. For example, Elevator A Parking Garage Door 3 |
varchar(255) |
|
creation_timestamp |
The UTC timestamp when the PACS space was first imported through Network Manager. |
datetime |
|
modification_timestamp |
The latest UTC timestamp when the space was modified. The value will continually change as the properties/configuration of the space are updated. |
datetime |
|
space_status |
The current status of the space. A space’s status can be Active or Deleted. |
varchar(25) |
|
floor_id |
The Floor ID to which the space corresponds. The relationship with Floor is configured through Network Manager. If no Floor is mapped, the default value is Not Applicable. |
bigint(20) |
|
network_id |
The numeric ID of the Network. All spaces are stored at the level of Network. |
bigint(20) |
lu_floor
A Floor is the grouping of spaces. For example, Lobby, 10th Floor, Parking Garage, etc.
|
Column |
Description |
Data-Type |
|---|---|---|
|
floor_id |
The numeric ID of the Floor generated by Identity server. |
bigint(20) |
|
floor_desc |
The name of the Floor to which the space is mapped to and created in Network Manager. |
varchar(255) |
|
creation_timestamp |
The UTC timestamp when the Floor was first created through Network Manager. |
datetime |
|
modification_timestamp |
The latest UTC timestamp when the Floor was modified. The value will change as the mapping to spaces or names of the Floor are updated. |
datetime |
|
floor_status |
The current status of the Floor. A Floor’s status can be Active or Deleted. |
varchar(25) |
|
facility_id |
The facility id to which the floor corresponds. The relationship with floor is configured through Network Manager. |
bigint(20) |
|
network_id |
The numeric ID of the Network. All floors are stored at the level of Network. |
bigint(20) |
lu_facility
A Facility is the grouping of floors, such as Headquarters or London Office, and is representative of a building. Each Facility has a Facility Address associated with the location of the building. A network administrator can add the address of the facility which to provide an additional level of analysis of Badge transactions.
The Platform Analytics ETL stores the facility address and draws a 500-meter radius around the facility. Any Badge transaction (long/lat) that happens within the 500-meter radius is mapped to the stored facility address. Any transaction outside the radius is mapped to Not Applicable. The true location of the user is never manipulated for the Longitude/Latitude attributes.
If a user is detected within two facility radiuses, the Platform Analytics ETL will choose the facility which is the closest distance. Both the Facility and Facility Address are configured through Network Manager. The radius is not configurable.
There are multiple benefits for adding with the Facility Address. When two users perform an Badge transaction from the same location, the mobile device can send longitude/latitude data that is different. This a limitation with geo data from mobile device. The Facility Address attribute allows an analyst to compare aggregate values. By grouping all transactions to a single facility address at HQ, Platform Analytics can compare how many Badge transactions occurred in a defined area. Previously, the end user had to manually group the transactions within the dashboard or dataset in order to have this aggregate view.
Additionally, this allows an administrator to answer questions like:
- Did the user open the Space (i.e. PACS system) remotely?
- What logical Applications were accessed from my headquarters facility?
|
Column |
Description |
Data-Type |
|---|---|---|
|
facility_id |
The numeric ID of the facility. |
bigint(20) |
|
facility_desc |
The name of the facility to which the Floor is mapped. The value is added through Network Manager. |
varchar(255) |
|
facility_status |
The current status of the facility. A facility’s status can be Active or Deleted. |
varchar(25) |
|
creation_timestamp |
The UTC timestamp when the Facility was first created through Network Manager. |
datetime |
|
modification_timestamp |
The latest UTC timestamp when the facility was modified. The value will change as the mapping to Floors or name of the facility are updated. |
datetime |
|
facility_latitude |
The corresponding latitude value for the Facility Address based on the address added in Network Manager. The latitude and longitude coordinates are used to draw the radius. |
double |
|
facility_longitude |
The corresponding longitude value for the Facility Address based on the address added in Network Manager. The latitude and longitude coordinates are used to draw the radius. |
double |
|
location_desc |
The street address, city, state, country of the facility added through Network Manager. |
varchar(1096) |
|
updated_location_flag |
MicroStrategy internal use. |
int(11) |
|
address_id |
MicroStrategy internal use. |
bigint(20) |
|
campus_id |
The campus ID to which the facility corresponds. The relationship with Facility is configured through Network Manager. |
bigint(20) |
|
network_id |
The numeric ID of the Network. All facilities are stored at the level of Network. |
bigint(20) |
lu_campus
A Campus is a collection of Facilities. The campus to facility mapping is configured through Network Manager.
|
Column |
Description |
Data-Type |
|---|---|---|
|
campus_id |
The numeric ID of the campus. |
bigint(20) |
|
campus_desc |
The name of the campus to which the facilities are mapped in Network Manager. |
varchar(255) |
|
campus_status |
The current status of the campus. A campus’ status can be Active or Deleted. |
varchar(25) |
|
creation_timestamp |
The UTC timestamp when the Campus was first created through Network Manager. |
datetime |
|
modification_timestamp |
The latest UTC timestamp when the campus was modified. The value will change as the mapping to facilities change or if the name of the campus is updated. |
datetime |
|
network_id |
The numeric ID of the Network. All campuses are stored at the level of Network. |
bigint(20) |
lu_facility_address
This table is a view on the lu_facility table. Each Facility has a Facility Address associated with the location of the building.
|
Column |
Description |
Data-Type |
|---|---|---|
|
facility_address_id |
The numeric ID of the facility address. |
bigint(20) |
|
facility_address_desc |
The name of the facility to which the address corresponds. The value is added through Network Manager. |
varchar(255) |
|
facility_latitude |
The corresponding latitude value for the Facility Address based on the address added in Network Manager. The latitude and longitude coordinates are used to draw the radius. |
double |
|
facility_longitude |
The corresponding longitude value for the Facility Address based on the address added in Network Manager. The latitude and longitude coordinates are used to draw the radius. |
double |
|
facility_street_address |
The street address, city, state, country of the facility added through Network Manager. The address is used for the 500-meter-radius ETL logic mentioned previously. |
varchar(1096) |
|
network_id |
The numeric ID of the Network. Each facility address is stored at the level of Network. |
bigint(20) |
lu_beacon
A Beacon can be configured to provide access to physical gateways/spaces or identify a users location.
|
Column |
Description |
Data-Type |
|---|---|---|
|
beacon_id |
The numeric ID of the beacon generated by Identity server. |
bigint(20) |
|
beacon_desc |
The name of the beacon configured in Network Manager. |
varchar(255) |
|
beacon_status |
The current status of the beacon. A beacon’s status can be: Active Deleted Inactive |
varchar(25) |
|
beacon_uuid |
The UUID of the beacon, supplied to you by your third-party beacon provider. |
varchar(255) |
|
beacon_minor |
The minor value you assigned to this beacon using your third-party setup tool. |
int(11) |
|
beacon_major |
The major value for your beacon. If you have more than one building in your network, you can have multiple major values. |
int(11) |
|
creation_timestamp |
The UTC timestamp when the beacon was configured through Network Manager. |
datetime |
|
modification_timestamp |
The latest UTC timestamp of the beacon modification. The value will continually change as the properties/configuration of the beacon are updated. |
datetime |
|
network_id |
The numeric ID of the Network. All beacons are stored at the level of Network. |
bigint(20) |
lu_bar_code
A Barcode can represent people (such as an employee, a customer, a contractor, or a party to a transaction) and objects (such as a vehicle, computer, package, contract, or transaction receipt). Scanning a barcode links the person, place, or thing identified by the barcode with the Badge user who performed the scan.
You can scan third-party barcodes and QR codes to display the data in Platform Analytics. The barcode is scanned using the Badge app. The exact barcode string is stored in the lu_bar_code table. The string can be parsed using derived attributes in MicroStrategy.
Scanning the codes allows you to create reports and dashboards that tie the scanning transaction and the data inside the code to Badge, Identity, and telemetry features. This feature also provides a way to document a transaction or link a Badge user and another person or object, using an identity-centric and location-aware approach. For example, you can document the path of a package from its source to its destination, providing information on who, where, and when the package was handled.
|
Column |
Description |
Data-Type |
|---|---|---|
|
bar_code_id |
The numeric ID of the bar code. |
bigint(20) |
|
bar_code |
The string of the bar code. This string is series of numbers/letters that can be parsed using Derived Attributes. |
longtext |
|
bar_code_type_id |
The ID of the corresponding barcode type. |
int(11) |
lu_bar_code_type
The format type of the barcode scanned by the Badge app.
|
Column |
Description |
Data-Type |
|---|---|---|
|
bar_code_type_id |
The numeric ID of the barcode type. |
int(11) |
|
bar_code_type_desc |
The format type of the barcode the user scans. The Badge app supports scanning the following types, AZTEC CODABAR – Android only CODE39 CODE39 MOD43 – iOS only CODE93 CODE128 DATAMATRIX EAN8 EAN13 INTERLEAVED2OF5 ITF14 – iOS only PDF417 QR UPC-E |
varchar(255) |
lu_desktop
A Desktop is the name of the user’s Mac or Windows machine that was locked or unlocked using their Badge app.
|
Column |
Description |
Data-Type |
|---|---|---|
|
desktop_id |
The numeric ID of the desktop. |
bigint(20) |
|
desktop_desc |
The name of the user’s desktop (e.g. personal machine) that is paired with the Badge app. For example, MAC-JSMITH WAS-RJONES John’s MacbookPro |
varchar(255) |
|
desktop_status |
The current status of the desktop. A desktop’s status can be Active or Deleted. |
varchar(25) |
|
desktop_os_id |
Microstrategy internal use. |
bigint(20) |
|
creation_timestamp |
The UTC timestamp when the desktop (i.e personal machine) was first paired with a device using the Desktop Client. |
datetime |
|
modification_timestamp |
The latest UTC timestamp when the desktop was modified. The value will change if the desktop pairing setting is changed or a new device is paired. |
datetime |
|
network_id |
The numeric ID of the Network. Each desktop is stored at the level of Network. |
bigint(20) |
lu_desktop_unlock_setting
The Desktop Unlock Setting is configured by the end user to control the proximity that triggers the unlock feature on either a Mac or a Windows machine. This setting can be changed at any time and therefore is stored at the transactional level in the access transaction fact table.
|
Column |
Description |
Data-Type |
|---|---|---|
|
desktop_unlock_setting_id |
The numeric ID of the desktop unlock setting. |
tinyint(4) |
|
desktop_unlock_setting_desc |
The desktop unlock setting which is used to determine the range for unlocking the personal Mac/Windows machine. For example: Close Nearby Far |
varchar(25) |