|
|
Line 1: |
Line 1: |
| == Problem & Motivation == | | == Problem & Motivation == |
− | <p>After the successful resolution of the 2014 kidnapping at GAStech’s Abila, Kronos office, GAStech officials determined that Abila offices needed a significant upgrade. At the end of 2015, the growing company moved into a new, state-of-the-art three-story building near their previous location. | + | <p>St. Himark has been hit by an earthquake, leaving officials scrambling to determine the extent of the damage and dispatch limited resources to the areas in most need. They quickly receive seismic readings and use those for an initial deployment but realize they need more information to make sure they have a realistic understanding of the true conditions throughout the city. |
− | The new office is built to the highest energy efficiency standard, but as with any new building, there are still several HVAC issues to work out. Each zone is instrumented with sensors that report building temperatures, heating and cooling system status values, and concentration levels of various chemicals such as carbon dioxide (abbreviated CO2) and hazium (abbreviated Haz), a recently discovered and possibly dangerous chemical. Staff members are also given proximity cards which will register their movements in the building by fixed proximity sensors in each zone and Rosie, a robotic mail delivery system equipped with proximity sensors. </p>
| + | |
− | <p>With the huge amount of data collected by the various sensors installed in the building, there is a need to build an interactive data visualization tool to help the management efficiently identify typical patterns and issues of concern in building operations.</p> | + | In a prescient move of community engagement, the city had released a new damage reporting mobile application shortly before the earthquake. This app allows citizens to provide more timely information to the city to help them understand damage and prioritize their response. In this mini-challenge, use app responses in conjunction with shake maps of the earthquake strength to identify areas of concern and advise emergency planners. Note: the shake maps are from April 6 and April 8 respectively. </p> |
− | <p>The interactive visualization can be targeted at employees from the following departments:</p> | + | <p>With emergency services stretched thin, officials are relying on citizens to provide them with much needed information about the effects of the quake to help focus recovery efforts. |
− | * Security Department: To track movement of employees within the building so as to ensure that employees are not entering prohibited zones/areas | + | </p> <p> By combining seismic readings of the quake, responses from the app, and background knowledge of the city, help the city triage their efforts for rescue and recovery. |
− | * Facilities Department: To understand building operations and the respective building data elements so that anomalies can be spotted quickly | + | </p> |
− | * Executive Department: To understand power usage of the new building so as to properly plan ahead on possible policies to implement (e.g. campaigns to save power consumption) | + | |
| + | <p>Tasks and Questions:</p> |
| + | * Emergency responders will base their initial response on the earthquake shake map. Use visual analytics to determine how their response should change based on damage reports from citizens on the ground. How would you prioritize neighborhoods for response? Which parts of the city are hardest hit? Limit your response to 1000 words and 10 images. |
| + | * Use visual analytics to show uncertainty in the data. Compare the reliability of neighborhood reports. Which neighborhoods are providing reliable reports? Provide a rationale for your response. Limit your response to 1000 words and 10 images. |
| + | * How do conditions change over time? How does uncertainty in change over time? Describe the key changes you see. Limit your response to 500 words and 8 images. |
| | | |
| == Dataset Analysis & Transformation Process == | | == Dataset Analysis & Transformation Process == |
− | Before the analysis began, the dataset given is analysed to identify its respective format and attributes. There were 6 different zip files provided in the assignment and each has its own unique ways to process and make sense of the data to bring value to the analysis. This section will elaborate on the dataset analysis and transformation process for each dataset in order to prepare the data for import and analysis on an interactive visualization.
| + | Data Analysis |
| | | |
− | === Fixed/Mobile Proximity Data & Employee List === | + | === Dataset XXX === |
− | <p>There are 2 main types of proximity detectors installed in the building to enhance the safety and security of its employees. These detectors include fixed proximity sensors installed in each zone of the building and a mobile proximity sensor that is attached to Rosie, a robotic mail delivery system. Data will be captured when employees, holding their own proximity card, pass a proximity sensor in the building.</p> | + | <p>xxx.</p> |
| | | |
− | <p>The formats of the captured data by both the fixed proximity sensor and mobile proximity sensor are similar. However, the fixed proximity sensor provides the zone in which employees pass through while the mobile proximity sensor provides the exact coordinates of the employee’s location. The following shows the main differences between the two different types of data captured:</p> | + | <p>XXX:</p> |
| [[File:Fixed Mobile Original Data Formats GwendolineTanWanXin.png|600px|center]] | | [[File:Fixed Mobile Original Data Formats GwendolineTanWanXin.png|600px|center]] |
− | <p>The following section illustrates the issues faced in the data analysis phase leading to a need to transform the data into a specified format.</p> | + | <p>XXX.</p> |
− | <p>'''Issue:''' Because of the differences in the types of data captured, the data cannot be correlated with each other for display in the same chart. For example, one can plot employee’s exact location using the X/Y coordinates (from the mobile proximity sensor) but the zone coordinates (from the fixed proximity sensor) were not known and hence, could not be plotted. This will present an issue during the analysis since we are unable to clearly identify which area the employees are present on the map.</p> | + | <p>'''Issue:''' WHY.</p> |
− | <p>'''Solution:''' To resolve this issue, the coordinates for each zone has to be identified. This is done using an online tool that allow analysts to get coordinates for custom polygons on a map. By plotting these custom polygons on a map, we will be able to get the centre point coordinates of the zone. This will then allow us to plot the employees’ location on each zone. The following details the process of getting individual zone coordinates.</p> | + | <p>'''Solution:''' SOLVE.</p> |
− | # Download the online tool from the link: https://github.com/bryantbhowell/tableau-map-pack/blob/master/draw_tableau_polygons_on_background_image.html | + | # Online Help |
− | # Open the tool and choose the map to be plotted. In the zone maps given, there were white spaces and additional text that were not part of the map itself. As such, the map has to be cropped to get the actual map itself only. The following shows the cropping of maps and this process is repeated for each of the 3 levels. <p>[[File:Cropping of Maps GwendolineTanWanXin.png|500px|center]]</p> | + | # Like this <p>[[File:Cropping of Maps GwendolineTanWanXin.png|500px|center]]</p> |
− | # Open the map using the online tool and plot each of the custom polygons. During the process of plotting, the following assumptions were made:<br/> | + | # Then:<br/> |
− | ## For some areas with multiple zones separated on the map, a small area of the zone is being selected. For example, zone 4 have 3 different segments in level 1. However, they all refers to the elevators and stairs. By plotting only one of the zones, we will still be able to know that the employee is taking the stairs/elevators. There isn’t a need to identify which stairs or elevators they took. As such, for zone 4, only one of the custom polygon is drawn.
| + | |
− | ## For areas that were too big, only a small segment of the zone was plotted. For example, zone 1 encompasses the entire corridor spaces. If all the corridor spaces are drawn, the centre point will not be situated in zone 1. Therefore, only one part of the zone is drawn. As long as employees are within the same zone, they are in the corridor areas.<br/>The outcome of plotting these polygons will result in the following display on the online tool. The same process is repeated for each of the 3 levels.<p>[[File:Plotting of Zones GwendolineTanWanXin.png|500px|center]]</p> | + | # Then<p>[[File:Individual Zone Coordinates GwendolineTanWanXin.png|500px|center]]</p> |
− | # After the polygons have been plotted, the results can be exported into a .csv file format for analysis in Tableau. Once the data has been imported into Tableau, the centre coordinates of each zone can then be retrieved. The following shows the centre points that were plotted on the chart and the ability to export the data. This will then allow us to retrieve the coordinates for each zone to be plotted onto the map.<p>[[File:Individual Zone Coordinates GwendolineTanWanXin.png|500px|center]]</p>
| + | # Then <p>[[File:Error In Centre Point GwendolineTanWanXin.png|600px|center]]</p> |
− | # However, in level 2 and 3, shapes of each zones were not consistent and this has resulted in errors in the centre point of the zone. The following shows the errors that has been encountered during the process. <p>[[File:Error In Centre Point GwendolineTanWanXin.png|600px|center]]</p> | |
− | # In order to resolve this error, a manual task has to be performed to get the coordinate point of each erroneous zone coordinate. This can be performed in Tableau using the annotate function. The following shows an example of how the annotate function can provide the X/Y coordinate values. The process is repeated for each of the erroneous centre points. <p>[[File:Annotate Area With Point GwendolineTanWanXin.png|600px|center]]</p>
| |
| # After the completion of this process, the issue of lacking individual zone coordinates will be resolved. | | # After the completion of this process, the issue of lacking individual zone coordinates will be resolved. |
| <br/> | | <br/> |
− | <p>'''Issue:''' Currently, the data for the fixed proximity sensors and mobile proximity sensors are in 2 separate spreadsheets. This makes the analysis process difficult with the need to blend or join data in Tableau.</p> | + | <p>XXX:</p> |
− | <p>'''Solution:''' To simplify the process of analysis, both the data from the fixed and mobile proximity sensors are combined into one single file. With the above process completed, we are also able to get the coordinates for each of the zone to be plotted on the chart. However, we do not have the zone information for the mobile proximity sensor. In this analysis, it does not matter as we are only interested in plotting the zone coordinates onto the chart. The following shows the data format of the transformed data:</p> | + | [[File:Fixed Mobile Original Data Formats GwendolineTanWanXin.png|600px|center]] |
− | <p>[[File:Combined Proximity Data Format GwendolineTanWanXin.png|500px|center]]</p> | + | <p>XXX.</p> |
| + | <p>'''Issue:''' WHY.</p> |
| + | <p>'''Solution:''' SOLVE.</p> |
| + | # Online Help |
| + | # Like this <p>[[File:Cropping of Maps GwendolineTanWanXin.png|500px|center]]</p> |
| + | # Then:<br/> |
| + | |
| + | # Then<p>[[File:Individual Zone Coordinates GwendolineTanWanXin.png|500px|center]]</p> |
| + | # Then <p>[[File:Error In Centre Point GwendolineTanWanXin.png|600px|center]]</p> |
| + | # After the completion of this process, the issue of lacking individual zone coordinates will be resolved. |
| <br/> | | <br/> |
− | <p>'''Issue:''' During the process of correlating the zone data and the coordinates, the dataset has a zone that stated “Server Room”. However, there is no point coordinate for this zone on our generated polygons.</p> | + | <p>XXX:</p> |
− | <p>'''Solution:''' To resolve this issue, the annotate function is also used to help us get the centre point coordinate of the server room. This result is then, updated into the file for analysis.</p> | + | [[File:Fixed Mobile Original Data Formats GwendolineTanWanXin.png|600px|center]] |
| + | <p>XXX.</p> |
| + | <p>'''Issue:''' WHY.</p> |
| + | <p>'''Solution:''' SOLVE.</p> |
| + | # Online Help |
| + | # Like this <p>[[File:Cropping of Maps GwendolineTanWanXin.png|500px|center]]</p> |
| + | # Then:<br/> |
| + | |
| + | # Then<p>[[File:Individual Zone Coordinates GwendolineTanWanXin.png|500px|center]]</p> |
| + | # Then <p>[[File:Error In Centre Point GwendolineTanWanXin.png|600px|center]]</p> |
| + | # After the completion of this process, the issue of lacking individual zone coordinates will be resolved. |
| <br/> | | <br/> |
− | <p>'''Issue:''' With the zone coordinates and the X/Y coordinates from the mobile proximity sensor, the data can be plotted onto a map to identify where employees are located. However, with only the proximity ID in the captured data, we are unable to correlate the employee with each proximity ID. The employee list provided in the dataset also does not show the mapping between their name and the proximity ID.</p>
| |
− | <p>'''Solution:''' Upon close observation of the employee name and the proximity ID, a correlation can be identified. The proximity ID is derived from the first letter of the employee’s first name and the entire string of the last name. The last three numbers refer to the number of times each employee request for a new pass. By default, the count starts from 001. The following formula is then applied to identify a correlation between the employee and the proximity ID:</p>
| |
− | <p>[[File:Employee and Proximity ID GwendolineTanWanXin.png|650px|center]]</p>
| |
− |
| |
− | === Building Data Elements (HVAC Sensor Readings & Status Information) ===
| |
− | <p>The building data elements provide multiple readings collected from different sensors in the entire building. However, the data is not structured in a way that allows for flexibility in the choice of sensor readings to be analysed and to apply filters by different floors and zones. As a result, there is a need to reshape the data to provide for this flexibility.</p>
| |
− | <p>There are 3 main categories of data in the building data dataset:</p>
| |
− | * Overall Building Data (e.g. Drybulb Temperature, Pump Power etc.)
| |
− | * Floor Data (e.g. Air Loop Inlet Temperature, Cooling Coil Power etc.)
| |
− | * Floor/Zone Data (e.g. Reheat Coil Power, CO2 Concentration etc.)
| |
− | <p>To better analyse the data using Tableau, the following is being done:</p>
| |
− | # The entire building data dataset is grouped into different Excel Spreadsheet as follows:<p>[[File:Building&Floor Data Spreadsheet GwendolineTanWanXin.png|500px]] [[File:Floor Zone Data File GwendolineTanWanXin.png|500px]]</p>
| |
− | # Tableau provides an Excel plugin that allow one to reshape data into a format for easy processing especially if multiple attributes were present for selection. With the use of the tool, the following is then performed to each of the grouped datasheet:
| |
− | ## For the building data spreadsheet, a data reshape is performed to obtain the following result: <p>[[File:Building Data Reshape GwendolineTanWanXin.png|650px|center]]</p>
| |
− | ## For the floor data spreadsheet, a data reshape is performed. The output of the reshaped data is similar to the building data, with the exception of the difference in attributes between the overall building and each floor attributes.
| |
− | ## For the floor/zone data spreadsheet, a data reshape is also performed on its attributes. However, due to the volume of the data generated, additional processing needs to be done as follows:<p>[[File:Process Floow Zone Data GwendolineTanWanXin.png|650px|center]]</p>
| |
− | <p>With the reshaped data, it can then be imported into Tableau for analysis.</p>
| |
− |
| |
− | === Hazium Readings ===
| |
− | The sensor readings for hazium concentration level were saved as 4 different files in the given dataset. These readings are consolidated into one single file. The result is similar to the building dataset elements. As such, similar processing techniques were used to process the data - Excel Tableau’s plugin for data reshape. The following illustrates the steps taken to achieve the final transformed dataset.
| |
− | <p>[[File:Hazium Data File GwendolineTanWanXin.png|650px|center]]</p>
| |
| | | |
| == Dataset Import Structure & Process == | | == Dataset Import Structure & Process == |
| With the dataset analysis and transformation phase completed, the following files will have to be imported into Tableau for analysis: | | With the dataset analysis and transformation phase completed, the following files will have to be imported into Tableau for analysis: |
| <p>[[File:Data Sources GwendolineTanWanXin.png|900px|center]]</p> | | <p>[[File:Data Sources GwendolineTanWanXin.png|900px|center]]</p> |
− | <p>Each of the data file is added as a data source in Tableau. The relationships defined between each data source is the timestamp, floor and zone. This will allow analysis to be conducted across all the data sources at any one point.</p> | + | <p>RELATIONS.</p> |
− | <p>Additional processing is performed to the first data source - Proximity Data and Employee List.</p> | + | <p>ADDITIONAL DATASET.</p> |
− | * Import the proximity data as a data source. | + | * Import |
− | * Add new data connections to the proximity data source. The new data connection file will be the Employee List. | + | * Add new data connections to XXX. |
− | * Perform a left join between the proximity data and the employee list to correlate the employee ID together. This will allow us to identify the employee with the captured proximity card ID. The following shows the configuration of the join: | + | * Perform a left join between the XXX and the XX to correlate the XXX together. XXX The following shows the configuration of the join: |
| <p>[[File:Tableau Data Join Of Proximity Data GwendolineTanWanXin.png|300px|center]]</p> | | <p>[[File:Tableau Data Join Of Proximity Data GwendolineTanWanXin.png|300px|center]]</p> |
− | <p>To process and display the dates in a readable format for the analyst, each of the data sources will have a new calculated field to derive the date and day of the week. This will convert the date from the format “31/5/2016” to a format of “31 May (Tuesday)”.</p> | + | <p>To process and display XXX</p> |
| <p>The formula used is as follows: </p> | | <p>The formula used is as follows: </p> |
| ''STR(DATEPART('day', [Date/Time])) + " " + DATENAME('month',[Date/Time]) + " (" + DATENAME('weekday', [Date/Time]) + ")"'' | | ''STR(DATEPART('day', [Date/Time])) + " " + DATENAME('month',[Date/Time]) + " (" + DATENAME('weekday', [Date/Time]) + ")"'' |
| | | |
| == Interactive Visualization == | | == Interactive Visualization == |
− | <p>The interactive visualization can be accessed here: https://public.tableau.com/views/Assignment3_145/Home?:embed=y&:display_count=yes</p> | + | <p>The interactive visualization can be accessed here: TABLEAU LINK</p> |
− | <p>For the best experience, adjust your screen resolution to 1366x768 and enable full screen on the browser. Adjust the dashboard so that all elements can be clearly visible without the need to scroll up/down.</p>
| |
| <p>Throughout all the different dashboards, useful guides/tips are provided to help users navigate through the different filters and actions so that their analysis can be performed smoothly. The following interactivity elements are also used throughout all the dashboards to maintain consistency:</p> | | <p>Throughout all the different dashboards, useful guides/tips are provided to help users navigate through the different filters and actions so that their analysis can be performed smoothly. The following interactivity elements are also used throughout all the dashboards to maintain consistency:</p> |
| {| class="wikitable" | | {| class="wikitable" |
Line 81: |
Line 80: |
| ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps | | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps |
| |- | | |- |
− | | <center>'''Filter dates with the use of time range slider''' <br/>[[File:Filter by Date GwendolineTanWanXin.png|200px|center]]</center> | + | | <center>'''XXX''' <br/>[[File:Filter by Date GwendolineTanWanXin.png|200px|center]]</center> |
− | || <center>To provide flexibility for analysts to choose the time period that they are interested to analyse. <br/>The use of checkboxes or dropdown list requires the analyst to check/uncheck each date manually which is time-consuming. As such, a time range slider is preferred.</center> | + | || <center>WHY.</center> |
| || | | || |
− | # The date/time field have to be duplicated with its data type set to “date” | + | # Step 1 |
− | # Add the new field to be filtered. | + | # Step 2 |
| |- | | |- |
− | | <center>'''Filter each floor/zone using a single selection drop down list''' <br>[[File:Drop down list GwendolineTanWanXin.png|200px|center]]</center> | + | | <center>'''XXX''' <br/>[[File:Filter by Date GwendolineTanWanXin.png|200px|center]]</center> |
− | || <center>To allow analysts to concentrate on the data collected from each level with the use of a single selection. | + | || <center>WHY.</center> |
− | <br/>Use of a drop down list also allow analysts to easily choose the building level that they are interested to analyse.</center>
| |
| || | | || |
− | # Configure the filter selection to be a single selection drop down list | + | # Step 1 |
| + | # Step 2 |
| |- | | |- |
− | | <center>'''Change and zoom of floor plans based on each floor filter''' <br>[[File:Dynamic Floor Plan GwendolineTanWanXin.png|200px|center]]</center> | + | | <center>'''XXX''' <br/>[[File:Filter by Date GwendolineTanWanXin.png|200px|center]]</center> |
− | || <center>To allow for easy reference of mapping each building data elements with each zone. <br/> | + | || <center>WHY.</center> |
− | When a user filters from one floor to another, the floor plan also changes to provide for quick and easy reference. Due to the space constraint, each floor plan has to be zoomed for users to identify and see the zone areas clearly.</center>
| |
| || | | || |
− | # Create calculated fields for the x and y axis. | + | # Step 1 |
− | # Put the 2 calculated fields into the worksheet view. | + | # Step 2 |
− | # To hide the mark, set the colour as transparent.
| |
− | # Navigate to Maps > Background Images. Add the floor plans into the background images and configure it according to the filter condition.
| |
− | # Put the “floor” attribute as a filter.
| |
| |} | | |} |
| | | |
| The following sections elaborates on other interactivity techniques are integrated into each of the individual dashboard. | | The following sections elaborates on other interactivity techniques are integrated into each of the individual dashboard. |
| | | |
− | === Home Dashboard === | + | === Dashboard X === |
− | <p>There is a large amount of data attributes captured in the dataset provided. As such, it will not be possible to display all the attributes for a proper analysis in a single dashboard. At the same time, although many of these attributes are interrelated to each other, there is no clear and correct order in which data attributes should be analysed. Therefore, use of a story point does not seem plausible in this context. To resolve this issue, flexibility has to be provided for users to navigate between different dashboards. To do so, a homepage is created with 3 different data categories in mind – employee movement, HVAC Control System/Chemical Levels and power consumption. Each of these categories are further broken down into its respective sub-categories for users to conduct their analysis. This allow users to choose the analysis that they are interested to look in.</p>
| + | <p>The following shows the XX dashboard: </p> |
− | <p>The following shows the home dashboard: </p>
| + | [[File:Dashboard Power Consumption GwendolineTanWanXin.png|850px|center]] |
− | [[File:Dashboard Home GwendolineTanWanXin.png|800px|center]]
| |
− | <p>To allow for flexibility in navigation, the following interactive techniques have been employed:</p>
| |
− | {| class="wikitable"
| |
− | |-
| |
− | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;width: 20%;" | Interactive Technique
| |
− | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;width: 40%" | Rationale
| |
− | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps
| |
− | |-
| |
− | | <center>'''Navigate across dashboards with buttons'''</center>
| |
− | || <center>To provide users the flexibility of moving from one dashboard to the other, with an easy and simple to use interface </center>
| |
− | ||
| |
− | # Create images of the buttons and placed these images into the folder directory as follows: My Tableau Repository > Shapes.
| |
− | # In Tableau, create a new calculated field.
| |
− | # Drag the new calculated field into the “Shapes” mark. Configure the shapes that you want to use by selecting the Shape Palette loaded into the folder previously.
| |
− | # In the dashboard, drag the worksheet with the button into an empty area. Configure the action, with the use of the filters action.
| |
− | |-
| |
− | | <center>'''Display tooltips when users hover over each button'''</center>
| |
− | || <center>To provide users with contextual information about the dashboard and the expected charts that they will look at after the button click</center>
| |
− | ||
| |
− | # Configure the tooltips information on the marks shelf
| |
− | |}
| |
− | | |
− | === Employee Movement Dashboard ===
| |
− | <p>The following shows the employee movement dashboard: </p> | |
− | [[File:Dashboard Employee Movement GwendolineTanWanXin.png|800px|center]] | |
| | | |
| <p>The following interactive techniques have been employed in this dashboard:</p> | | <p>The following interactive techniques have been employed in this dashboard:</p> |
Line 142: |
Line 112: |
| ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps | | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps |
| |- | | |- |
− | | <center>'''Traverse through an hourly time series by clicking on the arrows'''</center> | + | | <center>'''XX'''</center> |
− | || <center>To analyse and draw connections between employees and their movement in the building over a series of time</center> | + | || <center>XX</center> |
− | || | + | || XX |
− | # Drag the date/time field into the “Pages” shelf
| |
− | # Change the field to “Hour” to enable the animation on an hourly basis
| |
− | The following shows a screenshot of the configuration:
| |
− | [[File:Pages Shelf GwendolineTanWanXin.png|150px|center]]
| |
− | |-
| |
− | | <center>'''Filter data source types based on fixed or mobile proximity type'''</center>
| |
− | || <center>To allow the analyst to understand the fixed and mobile proximity data</center>
| |
− | ||
| |
− | # Add a checkbox filter into the dashboard
| |
− | |-
| |
− | | <center>'''Highlight department upon selection'''</center>
| |
− | || <center>To highlight departments that are of interest to the analyst</center>
| |
− | ||
| |
− | # Add the shape legends for each department
| |
− | # Select the new object and check “Highlight selected items”.
| |
− | The following shows a screenshot of the configuration:
| |
− | [[File:Enable Highlighting GwendolineTanWanXin.png|150px|center]]
| |
| |} | | |} |
− | To help analysts get started with the analysis of the data, a typical pattern of GAStech employees have also been identified and included in the dashboard.
| |
− |
| |
− | === HVAC Control System & Chemical Levels (Heating) ===
| |
− | <p>The following shows the HVAC Control System (Heating) dashboard: </p>
| |
− | [[File:Dashboard Heating GwendolineTanWanXin.png|850px|center]]
| |
| | | |
− | <p>The following interactive techniques have been employed in this dashboard:</p>
| + | === Dashboard X === |
− | {| class="wikitable"
| + | <p>The following shows the XX dashboard: </p> |
− | |-
| + | [[File:Dashboard Power Consumption GwendolineTanWanXin.png|850px|center]] |
− | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;width: 20%;" | Interactive Technique
| |
− | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;width: 40%" | Rationale
| |
− | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps
| |
− | |-
| |
− | | <center>'''Highlight temperature type, upon selection'''</center>
| |
− | || <center>To enable analysts to visualize the differences between the water temperature and its respective set-points, all 3 lines have been placed on the same chart. However, situation arises when there is a need to look at one single attribute only. Therefore, the use of highlighting will help analyst to perform its tasks better.</center>
| |
− | || The implementation steps are similar to the use of highlighting in the “Employee Movement” dashboard.
| |
− | |-
| |
− | | <center>'''Highlight across all the different charts'''</center>
| |
− | || <center>To allow analysts to see how one data point is correlated to another data point in another chart, given the same date/time</center>
| |
− | ||
| |
− | # Navigate to Dashboard > Actions > select “highlight”.
| |
− | # Configure the source and target sheets for the highlighting of charts in the dashboard.
| |
− | |}
| |
− | | |
− | === HVAC Control System & Chemical Levels (Natural Ventilation) ===
| |
− | <p>The following shows the HVAC Control System (Natural Ventilation) dashboard: </p> | |
− | [[File:Dashboard Natural Ventilation GwendolineTanWanXin.png|850px|center]] | |
| | | |
| <p>The following interactive techniques have been employed in this dashboard:</p> | | <p>The following interactive techniques have been employed in this dashboard:</p> |
Line 198: |
Line 128: |
| ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps | | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps |
| |- | | |- |
− | | <center>'''Highlight across all the different charts'''</center> | + | | <center>'''XX'''</center> |
− | || <center>To allow analysts to see how one data point is correlated to another data point in another chart, given the same date/time</center> | + | || <center>XX</center> |
− | || The implementation steps are similar to the use of highlighting in the “HVAC Control System & Chemical Levels (Heating)” dashboard.
| + | || XX |
− | |-
| |
− | | <center>'''Link filter with “Mechanical Ventilation” dashboard'''</center>
| |
− | || <center>To allow analysts to conduct their analysis smoothly such that when one filters for level 2 data in mechanical ventilation dashboard, they will also use level 2 data when they go into the natural ventilation dashboard.<br/> | |
− | The rationale is that both ventilation elements are related to each other and analysts might be interested to analyse both elements one after the other.</center>
| |
− | ||
| |
− | # When configuring the filters, select the worksheets that will be affected by the filters.
| |
− | # Other than selecting the worksheets in the dashboard, show all the worksheets in the workbook and check those that applies.
| |
− | The following shows an example of the configuration:
| |
− | [[File:Apply Filter to other Worksheets GwendolineTanWanXin.png|450px|center]]
| |
| |} | | |} |
| | | |
− | === HVAC Control System & Chemical Levels (Mechanical Ventilation) === | + | === Dashboard X === |
− | <p>The following shows the HVAC Control System (Mechanical Ventilation) dashboard: </p> | + | <p>The following shows the XX dashboard: </p> |
− | [[File:Dashboard Mechanical Ventilation GwendolineTanWanXin.png|850px|center]] | + | [[File:Dashboard Power Consumption GwendolineTanWanXin.png|850px|center]] |
| | | |
| <p>The following interactive techniques have been employed in this dashboard:</p> | | <p>The following interactive techniques have been employed in this dashboard:</p> |
Line 223: |
Line 144: |
| ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps | | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps |
| |- | | |- |
− | | <center>'''Highlight across all the different charts'''</center> | + | | <center>'''XX'''</center> |
− | || <center>To allow analysts to see how one data point is correlated to another data point in another chart, given the same date/time</center> | + | || <center>XX</center> |
− | || The implementation steps are similar to the use of highlighting in the “HVAC Control System & Chemical Levels (Heating)” dashboard. | + | || XX |
| |} | | |} |
| | | |
− | === HVAC Control System & Chemical Levels (Air-Conditioning) === | + | === Dashboard X === |
− | <p>The following shows the HVAC Control System (Air-Conditioning) dashboard: </p> | + | <p>The following shows the XX dashboard: </p> |
− | [[File:Dashboard AirCon GwendolineTanWanXin.png|850px|center]] | + | [[File:Dashboard Power Consumption GwendolineTanWanXin.png|850px|center]] |
| | | |
| <p>The following interactive techniques have been employed in this dashboard:</p> | | <p>The following interactive techniques have been employed in this dashboard:</p> |
Line 239: |
Line 160: |
| ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps | | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps |
| |- | | |- |
− | | <center>'''Highlight temperature type, upon selection'''</center> | + | | <center>'''XX'''</center> |
− | || <center>To enable analysts to visualize the differences between the thermostat temperature and its respective set-points, all 3 lines have been placed on the same chart. However, situation arises when there is a need to look at one single attribute only. Therefore, the use of highlighting will help analyst to perform its tasks better.</center> | + | || <center>XX</center> |
− | || The implementation steps are similar to the use of highlighting in the “Employee Movement” dashboard. | + | || XX |
| |} | | |} |
| | | |
− | === HVAC Control System & Chemical Levels (Chemicals) === | + | === === |
− | <p>The following shows the HVAC Control System (Chemicals) dashboard: </p> | + | === Dashboard X === |
− | [[File:Dashboard Chemicals GwendolineTanWanXin.png|850px|center]] | + | <p>The following shows the XX dashboard: </p> |
| + | [[File:Dashboard Power Consumption GwendolineTanWanXin.png|850px|center]] |
| | | |
| <p>The following interactive techniques have been employed in this dashboard:</p> | | <p>The following interactive techniques have been employed in this dashboard:</p> |
Line 255: |
Line 177: |
| ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps | | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps |
| |- | | |- |
− | | <center>'''Show different views of the Hazium data in the dashboard'''</center> | + | | <center>'''XX'''</center> |
− | || <center>To provide different perspectives for an analyst to conduct his investigation. <br/> | + | || <center>XX</center> |
− | For example, the line graph allows analysts to view the change in hazium concentration level overtime while the heatmap allow analysts to easily view the concentration levels of hazium based on colours representation.</center>
| + | || XX |
− | || -
| |
− | |-
| |
− | | <center>'''Highlight across different charts'''</center>
| |
− | || <center>To show the correlation between the same set of data that has been represented in 2 different chart layouts</center>
| |
− | || The implementation steps are similar to the use of highlighting in the “HVAC Control System & Chemical Levels (Heating)” dashboard.
| |
− | |-
| |
− | | <center>'''Configure safe range of CO2 level'''</center>
| |
− | || <center>To provide a clear view for the analysts to see if the level of carbon dioxide concentration exceeds a safe range
| |
− | <br/>
| |
− | To provide flexibility for analysts to configure a safe range, as defined by the organization</center>
| |
− | ||
| |
− | # Switch to the “Analytics” view and choose to add a “Reference Band” into the chart.
| |
− | # For the value, choose to add a new custom parameter. The following shows a screenshot of the new parameter created: [[File:Defining Parameters GwendolineTanWanXin.png|250px|center]]
| |
− | # To create a band, define two parameters that is the typical safe range level to a maximum safe range level. This will help to create a reference band. The following shows the configuration of a reference band: [[File:Defining Reference Band GwendolineTanWanXin.png|250px|center]]
| |
− | # Add both of these parameters onto the dashboard and analysts will be able to configure the values based on the organization’s preference.
| |
− | |-
| |
− | | <center>'''Click on data point to explore ventilation elements that might lead to variations in CO2 level'''</center>
| |
− | || <center>To allow co-referencing of carbon dioxide levels with the ventilation elements and analyse possible reasons that led to the changes in carbon dioxide concentration</center> | |
− | || To ensure that the filter applied in the dashboard is linked with the “HVAC Control System Ventilation Elements” dashboard, similar steps were taken as mentioned previously to link filters across different dashboards.
| |
− | <br/>To allow clicking of the chart to another dashboard, actions were defined based on the following configuration: [[File:Action to Link Dashboard GwendolineTanWanXin.png|350px|center]]
| |
| |} | | |} |
| | | |
− | === Power Consumption in Kronos Office Building === | + | === Dashboard X === |
− | <p>The following shows the Power Consumption dashboard: </p> | + | <p>The following shows the XX dashboard: </p> |
| [[File:Dashboard Power Consumption GwendolineTanWanXin.png|850px|center]] | | [[File:Dashboard Power Consumption GwendolineTanWanXin.png|850px|center]] |
| | | |
Line 291: |
Line 193: |
| ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps | | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Brief Implementation Steps |
| |- | | |- |
− | | <center>'''Click on data point to explore possible causes of variations in HVAC power demand'''</center> | + | | <center>'''XX'''</center> |
− | || <center>To allow analysts who are interested to identify reasons as to why the HVAC control system is consuming so much power with just a single click on a data point</center> | + | || <center>XX</center> |
− | || The implementation steps are similar to the use of linking technique used in the “HVAC Control System & Chemical Levels (Chemicals)” dashboard. | + | || XX |
| |} | | |} |
− | == Interesting & Anomalous Observations ==
| |
− | Using the dashboard as a platform for investigation and analysis, the following aims to provide answers to the questions posed.
| |
| | | |
− | === Q1: Typical Patterns In Proximity Card Data & Typical Day Of GAStech Employees === | + | === Q1: Emergency responders will base their initial response on the earthquake shake map. Use visual analytics to determine how their response should change based on damage reports from citizens on the ground. How would you prioritize neighborhoods for response? Which parts of the city are hardest hit? Limit your response to 1000 words and 10 images. === |
− | '''Typical Patterns in Proximity Card Data'''<br/> | + | ''ZZ'''<br/> |
− | Based on the data captured by the proximity sensors, the following shows a typical pattern in the proximity card data.
| + | Ans |
− | # For the fixed proximity sensors, readings are collected for 24hours during the weekdays, except for 1am and 4am. From 12midnight to 6am, only level 1 fixed proximity sensor will collect data. This can possibly mean that there is no employee movement from 12midnight to 6am on level 2 and 3. | + | # Ans1 |
− | # For the mobile proximity sensor, Rosie (the mobile robot) travels the halls at 9am and 2pm daily. On 4, 5, 11 and 12 June, the robot does not collect any readings. One possible reason is that these are weekends (Sat/Sun) and therefore, Rosie will not be required to travel along the hallways. | + | # Ans2 |
| | | |
− | '''Typical Day for GAStech Employees'''<br/> | + | '''Ans'''<br/> |
− | <p>The following lists a typical day for GAStech employees, in all departments:</p> | + | <p>Ans1:</p> |
− | # Employees start arriving in the office at 7am. By 9am, majority of the employees would have already arrived in the building and settle in their own office space. | + | # Ans2 |
− | # Lunch time is usually between 12nn to 2pm. | + | # Ans3 |
− | # At around 2pm, many employees will be back in their office and that’s when we can see lots of activities going on in the different levels.
| |
− | # Employees typically end work at around 5pm, though some may leave slightly earlier.
| |
− | # After 6pm, majority of the employees in the office are from the Engineering, Facilities and IT department.
| |
− | # After 7pm, employees working in level 3 would have left the office.
| |
− | # At 12midnight, most of the employees would have left the building and only people in the facilities team will be present in level 1.
| |
− | # People in the facilities department will be available in the building 24 hours and its always the same people patrolling around the area.
| |
− | # Other than the facilities personnel, IT and engineering employees often stay in the office and will only leave at around 12midnight.
| |
| | | |
− | <p>The following lists some activities that is part of a typical day pattern for employees in a specific department:</p>
| |
| {| class="wikitable" | | {| class="wikitable" |
| |- | | |- |
− | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;width: 20%;" | Department | + | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;width: 5%;" | Col1 |
− | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Activities | + | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;width: 48%;" | Col2 |
| + | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Col3 |
| + | |- |
| + | | <center>'''1'''</center> |
| + | || Row |
| + | || Row |
| + | <br/> Row |
| + | |- |
| + | | <center>'''2'''</center> |
| + | || Row |
| + | || Row |
| + | <br/> Row |
| + | |- |
| + | | <center>'''3'''</center> |
| + | || Row |
| + | || Row |
| + | <br/> Row |
| |- | | |- |
− | | <center>'''Engineering'''</center> | + | | <center>'''4'''</center> |
− | || | + | || Row |
− | # Between 2pm and 3pm, employees seem to appear around the meeting and training room.
| + | || Row |
− | # After 6pm, only Clemencia Whaley, Penney Bueno and Twana Quiroz will remain in the building. They will leave around 11.40pm.
| + | <br/> Row |
| |- | | |- |
− | | <center>'''Executive'''</center> | + | | <center>'''5'''</center> |
− | || | + | || Row |
− | # At around 12nn, CEO Sten Sanjorge Jr. will be moving around the building. At around 1pm, other executives start leaving for lunch.
| + | || Row |
| + | <br/> Row |
| |- | | |- |
− | | <center>'''Facilities'''</center> | + | | <center>'''6'''</center> |
− | || | + | || Row |
− | # Shift work is being done throughout the day as we can see some pattern for employees in the facilities department:
| + | || Row |
− | ## Varro Awelon and Emile Earpa will always be in level 1 from 12mn to around 7.30/8am.
| + | <br/> Row |
− | ## Dylan Scozzese and Chi Staley will always be in level 1 from 8am onwards.
| |
− | # At approximately 9am, some employees from the facilities department will proceed to the deli.
| |
| |- | | |- |
− | | <center>'''Information Technology'''</center> | + | | <center>'''7'''</center> |
− | || | + | || Row |
− | # At around 10.30am, all employees from the IT department will gather at the meeting room area on level 2.
| + | || Row |
− | # Out of all IT employees, Erminia Bello seems to be always staying in the office till late.
| + | <br/> Row |
| |- | | |- |
− | | <center>'''Security'''</center> | + | | <center>'''8'''</center> |
− | || | + | || Row |
− | # Employees do not typically move around the building. The data captured had shown that they always stay within their own office.
| + | || Row |
| + | <br/> Row |
| |} | | |} |
| | | |
− | === Q2: Interesting Patterns & Its Significance In Building Data === | + | === Q2: Use visual analytics to show uncertainty in the data. Compare the reliability of neighborhood reports. Which neighborhoods are providing reliable reports? Provide a rationale for your response. Limit your response to 1000 words and 10 images. === |
− | The following identifies some interesting patterns and the significance of the pattern to GAStech.
| + | Ans: |
| + | |
| {| class="wikitable" | | {| class="wikitable" |
| |- | | |- |
− | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;width: 5%;" | S/N | + | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;width: 5%;" | Col1 |
− | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;width: 48%;" | Interesting Pattern | + | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;width: 48%;" | Col2 |
− | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Significance | + | ! style="font-weight: bold;background: #536a87;color:#fbfcfd;" | Col3 |
| |- | | |- |
| | <center>'''1'''</center> | | | <center>'''1'''</center> |
− | ||The water heater temperature set-point is set at around 60C. This is approximately similar to the water heater outlet temperature. From this, we can deduce that water entering the heater is always heated to the set-point temperature, regardless of the temperature of water entering the heater. | + | || Row |
− | <br/>During weekdays, the temperature of the water entering the heater slowly falls after 5am but will increase slowly after 12nn. Similar pattern is observed over the weekends, but at a smaller difference in the inlet temperature. However, the supply inlet mass flow rate remains the same.
| + | || Row |
− | <p style="font-size:11px">''[Source: HVAC Control System & Chemical Levels (Heating) Dashboard]''</p>
| + | <br/> Row |
− | || A consistent pattern of a change in inlet temperature is observed over the different days. However, the flow rate of water remains unchanged. This meant that there are other reasons as to why the inlet temperature always changes throughout the day. | |
− | <br/>The management needs to identify the reasons for the temperature difference to prevent wastage of energy in heating up the water, especially during the weekdays where temperature difference is vast. | |
| |- | | |- |
| | <center>'''2'''</center> | | | <center>'''2'''</center> |
− | ||The lower the supply inlet temperature, the higher the rate at which the water heater burns natural gas. From this, we can infer that the burning of natural gas is used as a way to heat up the water so as to maintain the outlet temperature. | + | || Row |
− | <br/>The building also has a hot water system pump to heat up the water. Despite of the difference in the inlet temperature throughout each day, the amount of power used by the hot water system pump remains constant throughout the 2 weeks.
| + | || Row |
− | <p style="font-size:11px">''[Source: HVAC Control System & Chemical Levels (Heating) Dashboard]''</p>
| + | <br/> Row |
− | || Based on the data collected, we can deduce that the building provides for 2 different methods to heat up the water – burning of natural gas and using the hot water system pump. | |
− | <br/>Through the pattern identified, we can see that the burning of natural gas is used more often than the hot water system pump to heat up the water.
| |
− | <br/>Natural gas is a non-renewable resource. As such, burning of natural gas for water heating is a poor practice and does not adhere to energy efficiency standards, as claimed by the company. It is important for the management to look into the issue and make use of the hot water system pump for heating of water instead. | |
| |- | | |- |
| | <center>'''3'''</center> | | | <center>'''3'''</center> |
− | || The supply fan seems to consume higher levels of power from 7am to 10pm. The outlet mass flow rate also seems to be consistent across the days, when the supply fan is operating correctly. | + | || Row |
− | <br/>The timing in which the supply fan is consuming higher levels of power is similar to employees’ working hours, including the IT/Engineering department. | + | || Row |
− | <p style="font-size:11px">''[Source: HVAC Control System & Chemical Levels (Mechanical Ventilation) Dashboard]''</p>
| + | <br/> Row |
− | || Through this pattern, we can infer that the building seems to be following energy efficiency standards by using more energy only when required, such as only during working hours.
| |
| |- | | |- |
| | <center>'''4'''</center> | | | <center>'''4'''</center> |
− | || On level 1 and 2, the bathroom exhaust fan seems to be consistently turned on throughout the days. However, on level 3, the bathroom exhaust fan power is only consuming power between 7am to 10pm. | + | || Row |
− | <p style="font-size:11px">''[Source: HVAC Control System & Chemical Levels (Mechanical Ventilation) Dashboard]''</p> | + | || Row |
− | || Through this pattern, we can see that the use of the bathroom exhaust fan on level 1 and 2 does not seem to adhere to the energy efficiency standards. The practice of using energy only when required can be seen on level 3. However, as mentioned previously, employees in level 3 will be gone by 7pm. Despite so, the bathroom exhaust fan continues to generate power until late at night. This shows that the building is not following energy efficiency standards, as claimed.
| + | <br/> Row |
| |- | | |- |
| | <center>'''5'''</center> | | | <center>'''5'''</center> |
− | || The level of carbon dioxide concentration typically falls within a safe range of 350 to 1000 ppm for both level 2 and 3. However, the level of carbon dioxide concentration in level 1, especially zone 5 (Conference room) and zone 7 (loading area/server room) often falls outside of the safe range. | + | || Row |
− | <p style="font-size:11px">''[Source: HVAC Control System & Chemical Levels (Chemicals) Dashboard]''</p> | + | || Row |
− | || The air ventilation system in the building is performing its expected functions in level 2 and 3, on a normal day. However, more needs to be done to improve the ventilation on level 1, to ensure that it remains a conducive working environment for all employees. This is especially important in the conference room, where employees conduct meetings. If the level of carbon dioxide falls in the unhealthy range, employees may experience discomfort and may not be able to perform up to standards.
| + | <br/> Row |
| |- | | |- |
| | <center>'''6'''</center> | | | <center>'''6'''</center> |
− | || In the afternoon, the outdoor air mass flow rate is generally higher. However, during this period of time, the outside air temperature is generally warmer. When the outside air temperature is warmer, the percentage of outside air delivered by the HVAC system is generally lower. This pattern is generally observed across all the 3 levels. | + | || Row |
− | <p style="font-size:11px">''[Source: HVAC Control System & Chemical Levels (Natural Ventilation) Dashboard]''</p> | + | || Row |
− | || This is a good sign that the building is adhering to the energy efficiency standards. When the outside air is warmer, it takes more power to cool down the air so as to maintain a conducive temperature. As such, by restricting flow of warmer outdoor air, it helps the company to save on energy and power.
| + | <br/> Row |
| |- | | |- |
| | <center>'''7'''</center> | | | <center>'''7'''</center> |
− | || Level 1 has the highest outdoor air mass flow fraction. However, it has the lowest flow rate of air returning back to the HVAC system. | + | || Row |
− | <br/> On level 3, the outdoor air mass flow fraction can go as low as 6%. However, it has high flow rate of air returning back to the HVAC system.
| + | || Row |
− | <p> With the difference in outdoor air mass flow rate, the temperature of the air returning back to the HVAC system is higher in level 1 as compared to level 3. However, more energy is used on level 3 as compared to level 1.</p>
| + | <br/> Row |
− | <p style="font-size:11px">''[Source: HVAC Control System & Chemical Levels (Natural Ventilation) Dashboard]''</p>
| |
− | || From this pattern, we can clearly see the exchange of air between the outside air and the internal building. When the amount of outdoor air flowing into the floor is high, the rate of air returning back to the system is lower. This shows that the building is adopting good air-conditioning/ventilation system. | |
− | <br/>However, with higher flow rate of warmer outside air, there is a need for the cooling coil to use more energy in level 1 as compared to level 3. This will help to maintain a conducive temperature by cooling the warmer air. Despite so, the cooling coil in level 3 used more power than level 1 instead. This made the already cool level 3 cooler but level 1, which is hotter remains at a higher overall temperature. | |
− | This indicates possible issues with the HVAC control system which needs the attention of the operations staff.
| |
| |- | | |- |
| | <center>'''8'''</center> | | | <center>'''8'''</center> |
− | || The night cycle control status in level 3 is always off. In contrast to the night cycle control status in level 1, the status will be turned on after normal working hours of the company and during Sunday. | + | || Row |
− | <p style="font-size:11px">''[Source: HVAC Control System & Chemical Levels (Air Conditioning) Dashboard]''</p>
| + | || Row |
− | || There is a need for the operations staff to check as to why the night cycle manager is not working on level 3. Although there is no direct evidence to show the consequences of the night cycle control manager being off, it may potentially cause wastage of energy especially when the set-point temperature is not set appropriately.
| + | <br/> Row |
− | |-
| |
− | | <center>'''9'''</center>
| |
− | || Across all the three levels, the corridor spaces have constantly been using high levels of power.
| |
− | <p style="font-size:11px">''[Source: Power Consumption in Kronos Office Building Dashboard]''</p>
| |
− | || This is bad for the company as the corridor spaces do not contribute greatly to improving employees’ productivity or efficiency. Spending 80% of their energy in these areas are considered as energy wastage and potential measures have to be employed to reduce energy use in these areas.
| |
− | |-
| |
− | | <center>'''10'''</center>
| |
− | || Level 3 Zone 9 (server room) has been constantly using large amounts of equipment power. | |
− | <p style="font-size:11px">''[Source: Power Consumption in Kronos Office Building Dashboard]''</p>
| |
− | <br/>Temperature of the air in this zone is also constantly kept at a lower temperature than other zones. | |
− | <p style="font-size:11px">''[Source: HVAC Control System & Chemical Levels (Air Conditioning) Dashboard]''</p>
| |
− | || It is normal for the server to consume the largest amount of equipment power. At the same time, knowing that the server room have to be turned on 24 hours a day, measures have been taken to ensure a cooler temperature in the zone. This is notable for the company as it shows that they did deployed their resources properly.
| |
| |} | | |} |
| | | |
Line 472: |
Line 359: |
| <br/> Row | | <br/> Row |
| |} | | |} |
− |
| |
− | === Q4: Emergency responders will base their initial response on the earthquake shake map. Use visual analytics to determine how their response should change based on damage reports from citizens on the ground. How would you prioritize neighborhoods for response? Which parts of the city are hardest hit? Limit your response to 1000 words and 10 images. ===
| |
− | Ans:
| |
− |
| |
− | <p></p>
| |
− | <p></p>
| |
− | #
| |
− | #
| |
− | <p></p>
| |
| | | |
| == Comments == | | == Comments == |
| Please input your comments here! | | Please input your comments here! |