Infor Lawson Analytics for Healthcare Administration Guide. Version 10.0.x Published August 7, 2014

Transcription

1 Infor Lawson Analytics for Healthcare Administration Guide Version 10.0.x Published August 7, 2014

2 Copyright 2014 Infor. All rights reserved. Important Notices The material contained in this publication (including any supplementary information) constitutes and contains confidential and proprietary information of Infor. By gaining access to the attached, you acknowledge and agree that the material (including any modification, translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or interest in the material (including any modification, translation or adaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solely in connection with and the furtherance of your license and use of software made available to your company from Infor pursuant to a separate agreement, the terms of which separate agreement shall govern your use of this material and all supplemental related materials ("Purpose"). In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain such material in strict confidence and that your use of such material is limited to the Purpose described above. Although Infor has taken due care to ensure that the material included in this publication is accurate and complete, Infor cannot warrant that the information contained in this publication is complete, does not contain typographical or other errors, or will meet your specific requirements. As such, Infor does not assume and hereby disclaims all liability, consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or omissions in this publication (including any supplementary information), whether such errors or omissions result from negligence, accident or any other cause. Without limitation, U.S. export control laws and other applicable export and import laws govern your use of this material and you will neither export or re-export, directly or indirectly, this material nor any related materials or supplemental information in violation of such laws, or use such materials for any purpose prohibited by such laws. Trademark Acknowledgements The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other company, product, trade or service names referenced may be registered trademarks or trademarks of their respective owners. Publication Information Release: 10.0.x Publication date: August 7, 2014 Document Number: HCAAG_10.0.x_W_04

3 Contents Chapter 1: Overview...5 What is Analytics for Healthcare?...5 What is BPW?...6 What is a BMM?...8 What is an OLAP database?...9 User roles...9 Chapter 2: Administration setup...10 Data sources...10 Infor Lawson data source...10 External data definition...13 Defining variables in BPW...21 Chapter 3: Cube settings...25 SQL Server Analysis Services (SSAS)...25 Default cube settings...26 Customizable cube settings...27 Chapter 4: Additional information...29 Settings, flags, and switches...29 Exception handling...30 Adding a table to a BPW model...30 Updating the BMM...31 Infor Lawson Analytics for Healthcare Administration Guide 3

4 Contents Analytics for Healthcare drill through...31 Index Infor Lawson Analytics for Healthcare Administration Guide

5 Overview 1 This chapter provides an overview of the Infor Lawson Analytics for Healthcare Suite, the applications included in the suite, and other related topics: "What is Analytics for Healthcare?" on page 5 "What is BPW?" on page 6 "What is a BMM?" on page 8 "What is an OLAP database?" on page 9 "User roles" on page 9 What is Analytics for Healthcare? Built specifically for healthcare organizations, Analytics for Healthcare helps improve the quality and efficiency of business performance. It addresses the need for greater visibility into detailed information from identification of possible savings opportunities, performance monitoring, and role-based insight. Analytics for Healthcare also enables organizations to quickly access key financial metrics and performance indicators. Analytics for Healthcare includes four applications. Each application comes with customized calculations and key performance indicators. Healthcare Financial Management Analytics This helps organizations achieve their business goals by providing quick access to key financial metrics and performance indicators through predelivered content. Some examples are: Budget to Actual Analysis Expense and Labor costs by Department Operating Indicators Profitability and Price Patient Volumes Infor Lawson Analytics for Healthcare Administration Guide 5

6 Overview Length of Stay Efficiency Financial Indicators Cost per Discharge Profitability and Liquidity Ratios Capital Structure Ratios Asset Efficiency Indicator Healthcare Human Capital Management (HCM) Analytics This extracts data from Infor Lawson systems, such as enterprise resource planning applications, and external sources, including workforce management systems from other vendors, helping hospital administrators, clinical managers, and other authorized users to measure, monitor, and find ways to improve financial and operational performance. Healthcare Project Accounting Analytics This addresses the need for greater visibility into detailed project and expense tracking activities, identification of possible savings opportunities, performance monitoring, and role-based insight. Healthcare Supply Chain Analytics This provides the ability to slice into data to analyze the movement of Inventory, Item Usage, Supplier Performance, Buyer Performance, Purchasing trends and the visualization of spending patterns both at a high level and in detail. Where are you spending more or less than forecast? What Suppliers are not meeting expectations? Where can process improvements be made to optimize productivity and create further savings opportunities? All of these and more are available using the tools provided. What is BPW? Built on Infor Business Performance Warehouse (BPW), Analytics for Healthcare is designed to include both Lawson and external information. With BPW, you can implement data warehouse solutions that satisfy the information requirements of your users. It can be used to build a data warehouse from any relational data source but is also delivered with predefined metadata to make design faster and easier. A data warehouse consolidates and integrates data from dispersed functional systems. When large volumes of data are handled by different systems, a data warehousing application, such as BPW, can organize the data and make information available for decision making and analysis. Without a data warehouse solution, data in operational databases is normalized and the relational joins place an unacceptable load on the system when these databases are queried for reporting purposes. 6 Infor Lawson Analytics for Healthcare Administration Guide

7 Overview In the data warehouse solution, the data is denormalized and moved to a data warehouse where online analytical processing (OLAP) cubes are created as the source for multidimensional data analysis and reporting. See "What is an OLAP database?" on page 9 for details on the OLAP database. BPW database Operational data is updated to the data warehouse using extract, transform, and load (ETL). The term extract applies to the process of extracting operational data from the data sources to the staging database. The data is then transformed and filtered, if necessary, using compiled BPW designer components created and stored in the BPW catalog database. The transformed data is loaded into a data mart database in the warehouse. Using Microsoft SQL Server Analysis Services (SSAS), OLAP cubes are created to provide user-requested views of the data. Staging The staging table names reflect the name of the source table. Filters are sometimes used to filter records by a date or a value of a field. Catalog The catalog table names are made up of several types of designers, so the names created reflect the designer. There are six main types represented by the following naming convention: Main catalog names NR - Normalizers MG - Mergers BC - Basic Composers DC - Dimension Composers FC - Fact Composers NC - Nested Composers Source data names Source data is identified by the following naming convention: LBR - Labor (exclusive to Human Capital Management) SCM - Supply Chain (exclusive to Supply Chain) FIN - Finance (exclusive to Finance and Project Accounting) BSE - Base (part of base model) SRC - Source (tied to a source table) Data mart The data mart table names reflect what is used by SSAS in the cubes. Fact tables are made up of measures, while dimension tables consist of dimensions. Infor Lawson Analytics for Healthcare Administration Guide 7

8 Overview For additional information, see the Infor Lawson Business Performance Warehouse Administrator Guide. What is a BMM? Created in BPW, a Business Measurement Model (BMM) is a template star schema that extracts and transforms the source data into an analytical data model that contains fact and dimension tables. Star schema A star schema contains a fact table and one or more dimension tables. Fact and dimension tables can be graphically represented in a star-like formation, hence the name. Figure 1. A star schema Fact table A fact table contains at least two types of columns: Keys relate rows in the fact table to a row in each keyed dimension table Measures business metrics required for analysis by the users Dimension table A dimension table contains two types of columns: Keys relate a row in the dimension table to zero or more rows in the fact table 8 Infor Lawson Analytics for Healthcare Administration Guide

9 Overview Dimension Attributes provide context or meaning to each keyed fact What is an OLAP database? OLAP cubes summarize data along defined dimensions and hierarchies. Each of the Analytics for Healthcare applications retrieves data stored in Lawson relational databases as well as external sources and transforms it into a multidimensional database, or data mart, and stores it in an OLAP database. OLAP databases are made up of one or more cubes. OLAP is an efficient way to aggregate data. OLAP works with facts, and facts are numbers. OLAP cubes are efficient at counting, summing, and averaging. Facts can be grouped and organized into dimensions. OLAP databases store data differently than relational databases. Relational databases store data in two dimensions (rows and columns); OLAP databases store data in multiple dimensions. An OLAP database is: Fast Flexible Interactive User roles This list shows the typical user roles in Analytics. Administrator - users that can read and write data and process cubes. All data read-only - users that have read-only access to all data in the cubes. Dimension data security role - users with restricted access to data in the cubes. For example, you could create a role which is only able to view data for specific company or accounting units. Security role management Roles are used in Microsoft SSAS to manage security for Analysis Services objects and data. A role associates users to have specific access rights and permissions and is stored in each of the applications. The primary purpose of establishing roles is to provide an easy way to manage access rules for groups of users. Several roles can be defined and end-users are assigned to the appropriate roles. For additional information on defining roles in SSAS, see the Microsoft Developer Network site. Infor Lawson Analytics for Healthcare Administration Guide 9

10 Administration setup 2 This chapter provides information on the setup administration of Analytics for Healthcare. The data source connections need to be established before installing the BMM. The BPW variable definition and data input into the external data sources should be completed before the extract, transform, and load (ETL) process. See the Infor Lawson Analytics for Healthcare Installation Guide for detailed instructions. "Data sources" on page 10 "Defining variables in BPW" on page 21 Data sources Analytics for Healthcare works with both Lawson and external data sources. Installation during server setup and connections to these sources must be established before you can import data. Infor Lawson data source Analytics for Healthcare built on BPW and BPW is delivered with the metadata used to extract the Infor Lawson database tables. A connection to the database needs to be defined and will be done as part of the installation but no other steps are required before the connection is made. The connection instructions are found in "Establishing connection to the Infor Lawson data source" section of the Infor Lawson Analytics for Healthcare Installation Guide. External data source Analytics for Healthcare provides the capability to use data from external sources through the use of flat files or a Microsoft Access database. Delivered with Analytics are MS Access and CSV metadata that is included in the zip file. The list of the tables and files by application are detailed below. The steps required to create connections to the metadata are found in the Infor Lawson Analytics for Healthcare Installation Guide. For information on the data definition, see "External data definition" on page 13. The following are the templates provided as part of the install. 10 Infor Lawson Analytics for Healthcare Administration Guide

11 Administration setup Table 1. Microsoft Access source tables Application Templates All Applications ALL_Organization Custom_GL_Account_Rollup Financial Management FIN_FB_Budget_Reference FIN_KPI_Goals FIN_KPIs FIN_Measures_Detail FIN_Measures_Header FIN_Measures_Non_Lawson Infor Lawson Analytics for Healthcare Administration Guide 11

12 Administration setup Application Human Capital Management Templates LBR_Actual_Hours LBR_Unit_of_Service LBR_Wait_Time LBR_Budget_Annual LBR_Budget_Fixed LBR_Budget_Flexed LBR_Budget_Mode LBR_Budgeted_FTE LBR_Budgeted_UOS LBR_Budgeted_Wage_Rate LBR_Employee LBR_Employee_Experience LBR_Employee_Position LBR_Hour LBR_Incidents LBR_Position_Job_Custom_Groups LBR_Position_Job_Custom_Groups LBR_Productivity LBR_Requistions LBR_Schedule LBR_Survey LBR_Survey_Questions LBR_Timecard Project Accounting AC_Budget_By_Organization AC_Budget_Reference 12 Infor Lawson Analytics for Healthcare Administration Guide

13 Administration setup Table 2. CSV source tables Application Human Capital Management Templates LBR_Actual_Hours.csv LBR_Unit_of_Service.csv LBR_Wait_Times.csv LBR_Budgeted_FTE.csv LBR_Budgeted_UOS.csv LBR_Budgeted_Wage_Rate.csv LBR_Employee.csv LBR_Employee_Experience.csv LBR_Employee_Position.csv LBR_Incidents.csv LBR_Requistions.csv LBR_Schedule.csv LBR_Survey.csv LBR_Survey_Questions.csv LBR_Timecard.csv Supply Chain SCM_IC_Calendar.csv SCM_KPI_Goals.csv SCM_KPIs.csv External data definition Analytics for Healthcare has the capability to use data from external sources through Microsoft Access or flat files. Input into the Infor Lawson Analytics external data sources can begin once the setup and connections are completed. The Microsoft Access tables are delivered with field types appropriately defined for processing to simplify data input and editing. Inputting data into the tables is optional but in order for the data to populate it needs to be added before an ETL job is scheduled to begin. Flat file tables must be created in.csv format, comma delimited with double quotes around each table field. When using flat files in.csv format do not edit or save these files in Microsoft Excel. Users may open the files in Excel for easier error checking but again do not save them since Excel will remove the double quotes, which are required for the.csv to be processed. Infor Lawson Analytics for Healthcare Administration Guide 13

14 Administration setup All Suites There are Microsoft Access tables available in the external data source database All Suites.accdb. These tables are available to customize some of the shared dimensions. Table 3. All Suites tables Table name ALL_Organization Custom_GL_Account_ Rollup Table description Used for entering an Organization structure not defined in the General Ledger. Enables the definition of a custom GL Account hierarchy. Up to 5 levels can be custom-defined and will need an assigned sequence number to display in the desired order. Each new definition within a level must have a unique sort order number. Financial Management There are multiple Microsoft Access tables available in the external data source database Finance.accdb. All of these tables are available to tailor the General Ledger cube with data specific to your organization. Table 4. Financial Management tables Table name Table description FIN_Budget_ Reference FIN_KPIs FIN_KPI_Goals FIN_Measure_Header FIN_Measure_Detail Budget information from up to four budgets can be used in the Finance General Ledger cube. Enter a defined budget number from the Lawson Flex Budgeting system in each of the Budget 1-4 columns for each company/ year. A budget number is not required in every budget column. The General Ledger cube contains more than 50 predefined key performance indicators (KPIs). If a new KPI is defined in Microsoft Visual Studio by your organization, it should be added to the Microsoft Access table. The FIN_KPI table stores the available KPIs. Each of these KPIs can have a goal assigned using this table. For each KPI you want to use, enter a new record for each Company/Accounting Unit combination. The KPI Yellow From and Yellow To % columns define the criteria for displaying the yellow traffic light status. All of the KPI's values are based on the General Ledger cube dimension called Finance Measure Names. All of the Measure Names are defined using this table. For each measure name, enter the data source to populate the measure value. For KPI measures that have a data source of Lawson, enter the GL account numbers where the amounts or units are stored. If the accounts are not sequential, enter a new record for the same measure name. 14 Infor Lawson Analytics for Healthcare Administration Guide

15 Administration setup Table name FIN_Measure_Non_ Lawson FIN_Budget_Non_ Lawson Table description For KPI measures that have a data source of Microsoft Access, use this file to enter the data that makes up this measure for each period. Used to define external budget values, the data in the Microsoft Access table for company, accounting unit, account and sub Account number must be verified to the Lawson source tables. If the entered data is not a valid member, an unassigned (orphan) record will be created. For examples of each table, see the Infor Lawson Healthcare Financial Management Analytics User Guide. Human Capital Management Infor Lawson Healthcare Human Capital Management Analytics provides the capability to use data from external sources through the use of flat files or a Microsoft Access database. Files for the flat file tables may be created in.csv format, comma delimited with double quotes around each table field. Use the information in the following tables to define Labor Productivity external source templates. Table 5. Required table mappings Table name Table description LBR_ Position_Job_ Custom_ Groups To provide a roll-up of jobs and positions into a grouping for analysis, charting, and graphing, you may use a CustomGrp field. Infor Lawson Human Capital Management users may use the Job Group already in place in the Lawson system to fill CustomGrp or create groups specific to analytics. Use the most recent version of the JobName and/or Position Description per job or position code for consistent trending over time. Each Position can link to only one Job Code. A Job Code can link to only one Custom Group. A record per Company number with 0 Position and Job_Code should be included as a default for use when no Position or Job Code is included in the source data. Infor Lawson Human Capital Management users may leave Position Description and JobName blank. The most recent values from the Lawson table will be used by the system. Infor Lawson Analytics for Healthcare Administration Guide 15

16 Administration setup Table name LBR_Hour Table description The Hour table breaks 30-minute increments into parts of the work day.the template is prefilled with the time breaks. The following fields can be updated: Hour Code: Update this field to 1 to reflect the payroll shift starts. 8 Hr Shift and 12 Hr Shift: Fill these fields with a custom shift description. LawsonShiftEquiv:This should be filled with a number that matches the Shift number in Lawson Payroll. Add the correct Shift number to each corresponding row. Midnight is reflected as 0:00. An extra record with the 24-Hour HH:MM value of 24:00 is added to reflect "Past 24 Hrs". Measures, such as Patient Visits (Units of Service), that require a time span between midnight to midnight or Scheduled time, such as paid time off (PTO), where the actual time of day may not be tracked, should use 24:00 as the Hour value. Note: Hour attributes are sorted from 00:00 23:30. 00:00 marks the beginning of a new date. LBR_ Productivity In order to compare Budgeted Hours to Scheduled Hours to Actual Paid Hours, a hierarchy of Productivity groupings is created to map pay codes and rate types from different systems into Productivity categories. Due to different levels of detail or granularity that systems may cover, direct comparison may not be possible at all levels but only at the lower levels of granularity. Table 6. Supplemented Staffing tables Table name Table description LBR_Employee LBR_Employee_Positions This requires one record per employee. All data per Company and Employee is overwritten with the most recent information. This enables historical tracking of changes in Employee Position information for employees not in Lawson HR. There is one record per date range of any change in field per Company, Employee, and Position Level. Table 7. Staffing Budgets tables Table name Table description LBR_Budget_Fixed Set number of hours required per day of week; usually a position that would be replaced if the employee called off. 16 Infor Lawson Analytics for Healthcare Administration Guide

17 Administration setup Table name LBR_Budget_Annual Table description Annualized hours can be assigned as a total to one date, such as the first date of the fiscal year, or divided up to the first date of the fiscal quarter or start of each month. Annualized hours may also be divided up to each date in the period so that the hours are accrued on a daily basis. If a unit is closed for weekends or holidays, the record may be omitted. Note: Annualized data should be analyzed using Year-To-Date time frames because they are not required to be used on certain days. LBR_Budget_Flexed Hours that are adjusted based on actual unit of service (UOS). Staffing ratios should be converted to hours per UOS. Only jobs or positions that flex both up and down per UOS should be considered flex. Positions that only flex down do so to improve productivity, not to meet budget. HPUS Use the following calculation to convert staffing ratios to HPUS: Hours in time period / number of UOS in ratio Example: 1 A 4:1 RN staffing ratio for the 8-hour day shift. The flexed HPUS would be 8/4 = 2 HPUS. 2 For an 8-hour day shift with a 5:1 ratio, 8/5 = 1.6 HPUS. 3 For a 24-hour staffing ratio of 5:1, 24/5 = 4.8 HPUS. LBR_Unit_of_ Service (required for Flex Budgets) Each Accounting Unit may track a UOS used for measuring productivity. A description of the UOS being used is required. UOSs from different descriptions should not be summed together because they may produce misleading results. For instance, units with Patient Visits should not be summed with units with Patient Census. Likewise, UOSs measured at different time breaks or for different numbers of times per day should not be summed. For example, a UOS at three time breaks per day should not be summed with a UOS measured at eight time breaks per day. The LBR_Unit_of_Service value will be used to determine the target budgets. Infor Lawson Analytics for Healthcare Administration Guide 17

18 Administration setup Table name LBR_Budgeted_ UOS (required for Flex Budgets) LBR_Budgeted_ Wage_Rate (required for Budgeted Dollars) Table description Unit of Service Fact table will join the budgeted and actual UOS on Dist_ Company, Accounting Unit, Date, Time, Workload, and UOS_Description. An accounting unit may track more than one type of UOS by using the UOS_ Description to differentiate. The flex budget will join on matching Dist_Company, Accounting Unit, Date, Time, Workload, and UOS_Description. The budget measures are based on flexing the budgeted Hours Per Unit of Service (HPUOS) to the Budgeted UOS, while the target measures are based on flexing the budgeted HPUOS to the Actual UOS. The Forecasted UOS will equal the Budgeted UOS value until the Actual UOS is entered. Forecasted UOS will then be overwritten with the Actual amount. LBR_Budgeted_Wage_Rate is used along with LBR_Budget_Fixed, LBR_ Budget_Flexed, and LBR_Budget_Annual to calculate the Budgeted Dollars in the Productivity Cube. It is only necessary to provide a BudgetedAvgWage for Accounting Units and PayCategories that are included in those budgets. Table 8. Schedules, Timecards, and Payroll tables Table name Table description LBR_Schedule LBR_Timecard LBR_Actual_ Hours This is used to track staff schedules, schedule changes, and assignment methods. Schedules for any number of days forward and back can be added during the ETL process to ensure changes to the schedule are captured. variable in BPW should match the number of days forward of schedules. variable in BPW is the number of days back that are included in the LBR_Schedule table. The existing schedule data in the data mart will be deleted number of days back, and the new LBR_ Schedule data will be added. This is used to track timecard hours, wages, and comments. variable in BPW may be set to override the Lawson TIMERECORD table and use the Microsoft Access or.csv version of timecard data. This is used to track external payroll hours. Note: If both Lawson and external actuals are used, the ETL for the Actual Hour fact table must be customized as "Add New, Update Changing". 18 Infor Lawson Analytics for Healthcare Administration Guide

19 Administration setup Table 9. Human Capital tables Table name LBR_Budgeted_FTE LBR_Requisitions Table description This is for external Employee Budgets. This is for external Requisitions. Table 10. Staffing Effectiveness tables Table name Table description LBR_Incidents LBR_Wait_Times LBR_Survey_Questions LBR_Survey Quality indicators analyzed by counting the number of occurrences. Quality indicators measured by an average amount of time. Quality indicators measured as survey results. Survey information is collected in two tables. The tables are joined using the Survey_ID field. Survey information is collected in two tables.the tables are joined using the Survey_ID field. Responses should be computed to the Survey, Survey Time Level, and Accounting Unit basis before the data is entered into the table. Data is not tracked at the individual response level. For examples of each table, see the Infor Lawson Healthcare Human Capital Management Analytics User Guide. Project Accounting There are multiple access tables available in the external data source database Project Accounting.accdb. Table 11. Project Accounting tables Table name Table description AC_Budget_ Reference This table enables for up to three additional budgets per activity to be included in the cube to provide the ability to compare multiple versions of budgets defined in the Project Activity Lawson tables. The Project Activity column of the table needs to match the activity code defined in the Lawson table in order to create a match. The rest of the columns are for the other budget IDs to include in the cube. The budget defined as the active budget will already be included, and adding it into this table is not necessary. Infor Lawson Analytics for Healthcare Administration Guide 19

20 Administration setup Table name AC_Budget_By_ Organization Table description This table enables for one budget defined at the company and accounting unit levels. This is useful when activities belong to multiple accounting units or companies. In the Microsoft Access table, data in each of the fields is required. If there are no values needed for amounts or units, "0" is a valid input. The data in the Microsoft Access table for company, accounting unit, activity, and account category must be verified against the setup in the Lawson source tables. If the entered data is not a valid member, an unassigned (orphan) record will be created. For examples of each table, see the Infor Lawson Healthcare Project Accounting Analytics User Guide. Supply Chain All CSV files consumed by BPW are quoted, comma delimited. Use the information in the following table to define Supply Chain external source templates. Table 12. Supply Chain tables Table name SCM-IC_Calendar.csv This is for the Inventory cube. SCM_KPI_ Goals.csv This is for the Buyer Supplier, Inventory, Requisition, and Spend cubes. Table description The SCM-IC Calendar.csv file provides a calendar of period beginning and ending dates for the Inventory History fact table. The file must be populated for any years, including current, the client wants to analyze. The Lawson table ICCOMPANY holds current year period end dates; however, Lawson Analytics also requires begin dates which are not present in ICCOMPANY. The dates in this file are used in the Inventory cube to define the periods in the Inventory History fact table. The layout for SCM-IC Calendar.csv is: "Company", "Year", "Quarter", "Period", "Begin-Date", "End-Date" Clients may define their periods as months, or much less commonly as quarters/weeks. If periods are months, then Quarters will all be zero and will look something like this: "1", "2001", "0", "1", "1/1/2001", "1/31/2001" A single table, SCM_KPI_Goals.csv, stores the available KPIs for all Supply Chain cubes: Buyer Supplier, Inventory, Requisitions, and Spend. Each KPI can have a goal assigned using this table. The KPI Yellow From and Yellow To % columns define the criteria for displaying the yellow traffic light status. For examples of each table, see the Infor Lawson Healthcare Supply Chain Analytics User Guide. 20 Infor Lawson Analytics for Healthcare Administration Guide

21 Administration setup Defining variables in BPW A BPW variable represents a value. Use BPW variables to update and maintain commonly used values. These variables need to be defined before BMMs can be compiled. During the BPW installation process, several variables can be set to customize the ETL of related data. Variables should be set before an ETL job is scheduled to begin. For additional information, see the Infor Lawson Analytics for Healthcare Installation Guide. System setup variables System setup variables are variables that need to be defined and applied regardless of the application(s) installed in BPW. Table 13. System setup variables Variable CalendarPeriod##End_MMDD CalendarStartYear CalendarEndYear Description Defines what months should be assigned to each calendar period. For example, if the first month of your fiscal year is April, then CalendarPeriod01End_MMDD would be April (defined in BPW as 0430). Defines the first year of data you want included in the cubes. Defines the last year of data you want included in the cubes. Note: When setting this variable, once the end year value has passed, new data will not be included until it is changed. For example, if it is 2014 and the end year was set as 2013, no data for 2014 will be included. CalendarLockAdjustments CalendarQuarterPrefix DateFilter POUser If you have manually changed the begin and end dates of your fiscal months after the initial calendar build, subsequent builds of the calendar will preserve these changes by setting this value to "1". If set to "0", the fiscal months' begin and end dates will follow your Period01 through Period12 settings. Define the alpha value to prefix a calendar quarter, for example, "Q" or "Qtr" to display 3rd quarter as "Q3" or "Qtr 3", respectively. This variable defines the begin date of records to be extracted from the source tables. Only transactions whose required dates are on or after the DateFilter value will be pulled. If set to 01/01/ 1900, all records will be extracted. Defines the user(s) who run(s) PO100. To enter a list of user IDs, place an ampersand between each user ID, for example, "joes &janed&johnd". Infor Lawson Analytics for Healthcare Administration Guide 21

22 Administration setup Variable EReceipt GL_ ReverseIncomeStatmentAmounts Description Defines the Operator who runs PO529 and / or MA531 for electronic receipts. To enter a list of Operator IDs, place an ampersand between each user ID; for example, "PO529&EDIEH". Enter "Yes" to display Income Statement values with a reversed sign. For example, if an expense account has been defined to display with a negative sign, enter "Yes" to display the value without the minus sign. This variable will only be applied to amount and budget values. Attribute variables These are attributes from Lawson Attribute Matrix system. Put spaces in the value column where attributes are not used. Table 14. Attribute variables Variable AC Account Category Attributes AC Activity Attributes GL Accounting Unit Attribute Buyer Attribute GL Account Attribute Item Attribute Item Location Attributes Requesting Location Attributes Vendor Attributes Description AcAcctCatAttrib## (01-20) Account Category Attribute AcActivityAttrib## (01-20) Project Activity Attribute AcActivityGroupAttrib## (01-20) Project Group Attribute AuAttrib## (01-20) Accounting Unit Attribute BuyAttrib## (01-05) Buyer Attribute GLAccountAttrib## (01-20) General Ledger Account Attribute ItemAttrib## (01-20) Item Attribute ItemLocAttrib## (01-05) Item Location Attribute ReqLocAttrib## (01-05) Requesting Location Attribute VenAttrib## Vendor Attribute 22 Infor Lawson Analytics for Healthcare Administration Guide

23 Administration setup Strategic Ledger variables Table 15. Strategic Ledger variables Variable Description SL_Segment_Group SLSegmentValueDim## (1-10) LastSLTransObjId The Strategic Ledger cube is designed to use only one User Analysis Group that has been defined in User Analysis Group. Enter the User Analysis Group value. Enter up to 10 User Analysis values that have been defined for the entered SL_Segment_Group. This value will be set by the ETL process to the last SLTRANS OBJ-ID that was extracted in the SLTRANS staging data source table. If a full refresh is required, it should be reset to 0 (zero). If a full refresh is to be done, delete the data from the Strategic Ledger fact table. Human Capital Management variables Table 16. Human Capital Management variables Variable Description LbrTopPosition LbrDateFilter LbrCatDateFilter PayPeriodNumberOfDays PayPeriodStartDay PayPeriod PayPeriodCycle XFTimeCardSource The highest level Supervisor Code. All employees with empty supervisor codes, including the highest level person in the organization, will report to this Supervisor in the Reports To attribute of the Supervisor Dimension. The begin date for Labor Data. Follow the format of YYYYMMDD for Oracle and MM/DD/YYYY for SQL Lawson databases. The date used in LbrDateFilter in the YYYYMMDD format. Seven- or fourteen-day pay period. Valid values are either 7 or 14. The day, 1 through 14, in the pay period January 1st the CalendarStartYear represents. The Pay Period, 1 or 2, January 1st of the CalendarStartYear represents. The number of days between the first day of a pay period and the pay day of that pay period. L for Lawson TIMERECORD. If extracting timecard data from a external system into LBR_Timecard, use a letter other than L so that the TIMERECORD data is not used in the data mart in addition to the external time records. Infor Lawson Analytics for Healthcare Administration Guide 23

24 Administration setup Variable FEmpPositions HRSource LbrEEOCategory LbrPerfReview Description The number of days into the future the Employee Position information should be projected. Typically, this will match the number of days into the future Schedules are brought in so that a schedule can be tied to an employee position. Use TM to use Talent Management as the source instead of Infor Lawson Used to filter TM Job Country Attribute Category for EEO codes Used to filter Infor Lawson to Review.Code to codes for the Performance rating 24 Infor Lawson Analytics for Healthcare Administration Guide

25 Cube settings 3 This chapter discusses: "SQL Server Analysis Services (SSAS)" on page 25 "Default cube settings" on page 26 "Customizable cube settings" on page 27 SQL Server Analysis Services (SSAS) SQL Server Analysis Services is where the Analytic cubes are deployed and processed. There are a few key areas to highlight in SSAS. When a SSAS project is opened, the Solution Explorer will be available. This section contains all the components that make up an Analysis Services project such as: Data Sources connects the project to the BPW Datamart using the data source designer. Data Source Views visibility to the Star schema for the entire project. All dimensions and fact tables and how they relate to each other are shown here. Cube view of all the cubes for the project. Cubes Individual cubes are opened from solution explorer to view the detailed components of each cube with several tabs of information. Some of the tabs are: Cube Structure tab This has the fact table and dimension tables used for a particular cube. It includes: Measures contains the values, amount, unit, percent, etc. These measures are from the BMM (fact table). Dimensions contains the different hierarchies and attributes available. Data Source View acts as a dashboard and allows you to view the fact and dimension tables used for a particular cube, including its keys and columns. Infor Lawson Analytics for Healthcare Administration Guide 25

26 Cube settings Calculations tab This is where you find the calculated measures. Definitions of the predefined calculated measures can be found in the Infor Lawson Analytics user guides. Browser tab This tab is where you can browse the members of the tables in the cube. Dimensions Individual dimensions are opened from solutions explorer to view the detailed components of each dimension with several tabs of information. Some of the tabs are: Dimension Structure tab This tab allows you to view the hierarchies and attributes for the dimensions. It includes: Attributes - contains the utilized columns in the selected dimension. Hierarchies - displays the currently created hierarchies. Within each hierarchy are the attributes that make up the levels of the hierarchy. Data Source View contains all the available columns in the dimension table. Browser tab This tab is where you can browse the members of the dimension attributes. Default cube settings The groupings were created using Named Calculations and may be edited to suit clients' needs by editing the Named Calculation in the Data Source View. It is recommended that edits to Named Calculations should be documented since they will be overwritten when an update is taken. Please visit the Microsoft site to get the version of your SQL Server. The following Named Calculations are in the Employee Positions table: Age Range CASE WHEN [Age] < 20 THEN 'Under 20' WHEN [Age] < 30 THEN '20-29' WHEN [Age] < 40 THEN '30-39' WHEN [Age] < 50 THEN '40-49' WHEN [Age] < 60 THEN '50-59' WHEN [Age] < 70 THEN '60-69' WHEN [Age] < 100 THEN '70 and Over' ELSE 'NA' END LOS 26 Infor Lawson Analytics for Healthcare Administration Guide

27 Cube settings CASE WHEN [LengthofService] IS NULL THEN 'NA' WHEN [LengthofService] < 1 THEN '< 1 Yr' WHEN [LengthofService] <= 2 THEN '1-2' WHEN [LengthofService] <= 5 THEN '3-5' WHEN [LengthofService] <= 10 THEN '6-10' WHEN [LengthofService] <= 20 THEN '11-20' WHEN [LengthofService] <= 30 THEN '21-30' WHEN [LengthofService] <= 40 THEN '31-40' ELSE 'Over 41' END Time In Job CASE WHEN [TimeinJob] IS NULL THEN 'NA' WHEN [TimeinJob] < 1 THEN '< 1 Yr' WHEN [TimeinJob] <= 2 THEN '1-2' WHEN [TimeinJob] <= 5 THEN '3-5' WHEN [TimeinJob] <= 10 THEN '6-10' WHEN [TimeinJob] <= 20 THEN '11-20' WHEN [TimeinJob] <= 30 THEN '21-30' WHEN [TimeinJob] <= 40 THEN '31-40' ELSE 'Over 41' END FTE Group CASE WHEN [FTE] IS NULL THEN 'NA' WHEN [FTE] <.25 THEN '<.25' WHEN [FTE] <.50 THEN '<.50' WHEN [FTE] <.75 THEN '<.75' WHEN [FTE] <= 1 THEN '<=1' END Customizable cube settings You can modify an OLAP cube to fit your business requirements. During an update, cube customizations will need to be reapplied. Be cautious when customizing measure and dimension names because it can cause calculations to no longer work or to work incorrectly. As with any customization, it is recommended that changes and additions are well documented. Here are the typical cube settings that can be customized. Field display names for Attributes used to rename the attributes to a meaningful name versus leaving them as "Attribute 01", "Attribute 02", and so on. Hierarchy creations in Dimension tables creates hierarchical rollups to meet specific requirements. Additional MDX formulas adds calculations unique to a business need. It is recommended that you make a copy of the calculated measures before making changes to MDX formulas. This is done in the Calculations tab using script view. Hide Dimension Attributes hides unused fields for well-organized lists. Hide Measures hides unused fields for well-organized lists. Show Dimension Attributes shows fields that were hidden. Infor Lawson Analytics for Healthcare Administration Guide 27

28 Cube settings Show Measures shows fields that were hidden. Additional KPIs adds KPI calculations unique to a business need. 28 Infor Lawson Analytics for Healthcare Administration Guide

29 Additional information 4 This chapter provides additional important information about setting up Analytics for Healtchare. "Settings, flags, and switches" on page 29 "Exception handling" on page 30 "Adding a table to a BPW model" on page 30 "Updating the BMM" on page 31 "Analytics for Healthcare drill through" on page 31 Settings, flags, and switches This section includes information on the settings, flags, and switches in all Analytics applications. All applications Transaction records that have not been posted will not be included in the ETL process and therefore not included in the cube. Financial Management GL Company Calendar definitions that do not correspond with the calendar defined in the BPW variables will not populate data in the month period expected. For example, if period 1 in the GL calendar equals June but period 1 is defined as January in the BPW variable, the data in period 1 will populate into January, not June. Project Accounting AC Calendar definitions that do not correspond with the calendar defined in the BPW variables will still populate data in the month expected. For example, if period 1 in the AC calendar equals April, the data will populate in the period defined as April in the BPW variable. Infor Lawson Analytics for Healthcare Administration Guide 29

30 Additional information Supply Chain The Spend cube has been designed to display data based on the APDISTRIB records and their Distribution Date. Unposted records will not appear in the cube. The APDISTRIB record contains both summarized and detail data. In order to display cube results for specific Item, Agreement Reference, and Cost Details, APDISTRIB must contain detailed information from the Purchase Order and Invoice lines. The match process needs to use a Detail Match rule for PO Invoices and the Invoice needs to post in detail to the General Ledger. The "Summarize Distributions" flag on the Match Company controls how invoices post to GL when matched at that company. The settings on the General Ledger Chart of Accounts and Accounting Unit Account Options determine the interface posting options for each account. You may need to adjust these settings to display detailed information in the Spend cube. For more information, see the MA and GL User Guides. Exception handling Typically, every foreign key in a fact table should reference a natural key in the related dimension table. However, in certain scenarios, such as during the fact table load process, a natural key could be encountered that cannot be found in a dimension table. For example, an accounting unit posted in a transaction table may not be found in the Organization dimension table. These exceptions are handled in the fact table load process, so if a natural key is not found in the related dimension, a new row is inserted into the dimension table using the missing natural key. Certain fact tables are known to need exception handling and when known, they can be handled to prevent or reduce the exceptions. For example, there are a number of fact tables in the Supply Chain - Supplier and Buyer Performance model that are by Company but not by accounting unit. In order to link those fact tables to the Organization dimension table, additional records were created. Each Company in the Organization dimension table has one additional record added to include an accounting unit with a value of "0". The fact can then link to the proper company. Adding a table to a BPW model 1 On the BPW Designer, click the Data Warehouse tab. 2 Expand Data Marts and Models. 3 Expand Default Datamart for BPW. 4 Expand the Model group requiring the table. 5 Right-click at the Model level and select Properties. The Model Properties window appears. 6 Click the Tables tab. 30 Infor Lawson Analytics for Healthcare Administration Guide

31 Additional information 7 In the Available Tables list, select the table you want to add to the model. 8 Click the right arrow, found between Available Tables and Tables in Model, to move the selected table. 9 Confirm the table was added to Tables in Model list. 10 Click OK. Updating the BMM The installation of an updated BMM can add or make changes, but can not be deleted. An update may add new tables, add new fields to an existing table, or change the name of an existing table or field. It does not remove existing tables when no longer used. Instead, the table is ignored. The defined BPW variables will not be impacted by an update. Customizations may or may not be impacted. It is recommended all customizations are thoroughly documented and testing performed after the update to verify that the customizations work as designed. Analytics for Healthcare drill through Analytics for Healthcare delivers a drill through feature which allows users to dig further into the details of the data shown in the cubes. To enable this feature, there are setup items to verify. Users will need read-only access, at a minimum, to the four BPW databases in SQL server using their Windows Authentication login in addition to the standard cube access to be able to use the drill through. The BPW profile prefix will need to match the BPW profile prefix in the drill through query. The steps to verify and change the name are: 1 Open the project in SSAS. 2 Open the cube with the drill through. 3 Select the Actions tab. 4 Locate the Action expression section in this window there will be a query such as: 5 Compare the highlighted text in the above query to the BPW profile prefix to the prefix entered during BPW server setup. 6 If they match, no further steps are required. Infor Lawson Analytics for Healthcare Administration Guide 31

32 Additional information 7 If they don t match, change the highlighted text to the BPW profile prefix to the prefix entered during BPW server setup. 32 Infor Lawson Analytics for Healthcare Administration Guide

33 Index Index A Analytics for Healthcare, 5 drill through, 31 B Business Measurement Model (BMM) about, 8 dimension table, 8 fact table, 8 star schema, 8 updating, 31 Business Performance Warehouse (BPW) about, 6 adding a table, 30 attribute variables, 21 database, 6 defining variables, 21 human capital management variables, 21 strategic ledger variables, 21 system setup variables, 21 C cube settings customizable, 27 default, 26 D data source, 10 E exception handling, 30 external data definition All Suites, 13 financial management, 13 human capital management, 13 Microsoft Access tables, 13 project accounting, 13 supply chain, 13 H Healthcare Financial Management Analytics about, 5 Healthcare Human Capital Management Analytics about, 5 Healthcare Project Accounting Analytics about, 5 Healthcare Supply Chain Analytics about, 5 O OLAP database about, 9 S settings, flags, and switches about, 29 SQL Server Analysis Services (SSAS) about, 25 Infor Lawson Analytics for Healthcare Administration Guide 33

34 Index cubes, 25 dimensions, 25 U user roles, 9 security role management, 9 34 Infor Lawson Analytics for Healthcare Administration Guide