Implement the WBS OBS View Analytics

Before you can use the WBS OBS View tab, you must complete a number of prerequisite setup tasks.

The primary prerequisite is that the wInsight database must contain the WBS-to-OBS mapping information. If the required WBS-to-OBS mapping information is not available in wInsight Analytics Administrator, you cannot use the WBS OBS View tab. In that case, either use WBS Mapper to create the mapping information, or leave WBS OBS Link in wInsight Analytics Configuration, set to N so that the WBS OBS View tab will not be displayed.

If the required WBS-to-OBS mapping information is available, the remaining tasks basically establish a common set of organizations for all contracts so that the data aggregated across multiple contracts can be compared meaningfully. This is necessary because each contract potentially uses a different OBS in wInsight, so you need to define how the OBS elements from different contracts should be consolidated.

To implement the WBS OBS View analytics, complete the following steps:

1. If you have not already done so, map WBS elements to OBS elements in wInsight Analytics Administrator.
2. In wInsight Analytics Configuration, either wait until after the next scheduled data load process, or click Run Data Load Batch File to load wInsight data, including the WBS-to-OBS mapping information.

   This process takes some time; how long it takes depends on the size of your database and how many projects and periods you are loading. When it is completed, a message displays that confirms that the data model has been updated with the current wInsight Analytics data, based on your configuration settings.

3. On the server or standalone computer on which you installed the wInsight Analytics module, use Windows Explorer to go to the <installation location>\Translate folder and open Data_Model_wInsight.qvw.
4. Do one of the following:
   • If you use the same OBS structure for all projects, copy the contents of the Method 1: Consistent OBS Mapping table.
   • If the OBS structure is not the same for all projects, copy the contents of the Method 2: Different OBS by Contract table.

   To copy the contents of either table, right-click anywhere on the table and click Copy to Clipboard > Table Data Area.

5. On the server or standalone computer on which you installed the wInsight Analytics module, use Windows Explorer to go to the <installation location>\Setup folder and open the wInsight_Analytics_Setup.xlsx file in Microsoft Excel®.
6. On the OBS_Org_Mapping sheet, click the A2 cell and paste the data that you copied from the table in Data_Model_wInsight.qvw.
7. Do one of the following:
   • If you use the same OBS structure for all projects, copy the contents of the OBS Name column of the spreadsheet and paste that in the Mapped Organization column. Make sure that the Contract Name column is empty for all rows.
   • If the OBS structure is not the same for all projects, use the Mapped Organization column to enter the organization to which you want to map data for each project-specific OBS code. The goal is to define a common set of organizations to which all project-specific OBS codes are mapped. For example, if E400 for Project A is equivalent to ENG111 for Project B, you could enter Engineering for both of those rows to map data for those two OBS codes to a single organization in the WBS OBS View analytics. If you use this method, you must make an entry in Mapped Organization for every row in the spreadsheet.

   The names in the Mapped Organization column display on the WBS OBS View tab when you display data at the lowest OBS level.

8. Save the wInsight_Analytics_Setup.xlsx file.
9. Go to the Org_Hierarchy sheet.
10. In Mapped Organization, enter or copy-and-paste each of the organization names you set up in the Mapped Organization column on the OBS_Org_Mapping sheet. Each name should only appear once on this sheet.
11. Determine how you want to roll up the OBS data from the level defined in the Mapped Organization column to two higher levels of organizational elements.
12. In Higher Level, enter the name of the second-level organizational element to which you want to assign each organization in Mapped Organization. To roll up multiple organizations in Mapped Organization into one second-level organizational element for analysis purposes, enter the same organizational element name for each organization.
13. In Top Level, enter the name of the top-level organizational element to which you want to assign each organization in Mapped Organization. To roll up multiple organizations in Mapped Organization into one top-level organizational element for analysis purposes, enter the same organizational element name for each organization.
14. Save the wInsight_Analytics_Setup.xlsx file.
15. On the wInsight Analytics Configuration tab of the Configuration application, select Y (yes) in WBS OBS Link to activate the WBS OBS View tab.
16. Click Save Settings for wInsight Analytics. When this process is completed, wInsight Analytics displays a message that confirms that the settings have been updated successfully.
17. Click on the toolbar to save the setting in wInsight_Analytics_Config.qvw. Important: If you make any changes to the configuration settings, it is very important that you both click Save Settings for wInsight Analytics and click on the toolbar to save the current configuration settings before you run the data load process. If you do not do both, the data load may not use the most current configuration settings.

The next time that the data load process runs, the data model and the Multi-Project Analytics user interface are updated to reflect the WBS-to-OBS mapping implementation. You can wait for your next scheduled data load process, or you can click Run Data Load Batch File on the wInsight Analytics Configuration tab of the Configuration application to run it yourself. To verify the implementation without having to run the data load process, open wInsight_Analytics_MultiProject.qvw in QlikView Desktop and click File > Reload. wInsight_Analytics_MultiProject.qvw is located in the <installation location>\Final folder.