IS428 2016-17 Term1 Assign3 Yang Chengzhen

From Visual Analytics for Business Intelligence
Revision as of 23:16, 22 October 2016 by Czyang.2013 (talk | contribs)
Jump to navigation Jump to search


Description

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. Even though the employee morale rose somewhat with the excitement of the new building, there are still a few disgruntled employees in the company.
This project aims to identify the patterns and problems arose after moving to the new office building for GASTech. This is achieved by using GASTech operational data sets, including:

  • Proximity sensor data for each of the prox zone regions
  • Proximity sensor data from Rosie the mobile robot
  • HVAC sensor readings and status information from each of the building’s HVAC zones
  • Hazium readings from four sensors

Data Preparation

Create HH:MM:SS Field from timestamp

To analyse the moving pattern over each day, we need to extract time from the date since tableau does not support auto extract well.
Cz Hhmmss.png

Convert Server room to the corresponding Zone

For ProxoutMC2.csv, there are 29 records with zone name "Server Room" instead of a numeric number of majority. After checking the floor map, I found server room belongs to Floor3 Zone4, so I converted these values as following:
Cz ServerRoom.png

Covert X Y in proxMobileOut-MC2.csv to corresponding Zone

For Mobile Prox data, the position of the point is indicated by X,Y , while for fixed prox data, the position is indicated by zone. In order to analyse the movement together, we need to align the 2 data sets. I used tableau to create calculated field to convert X,Y to the corresponding zones:
Cz XY-to-floorZone.png

Data Visualization and Findings

Patterns of Employees by Prox Card Data

Floor-Zone Analysis

This Dashboard analyses the moving pattern of employees among different floor zones. The left graph shows number of people in each zone over times (Aggregated data from fix & Mobile Sensors). The right graph shows the position of employees at different time (mobile sensor data only). Size represent number of employees at the point, color represents morning/afternoon.
Floor-zone analysis-F1.pngFloor-zone analysis-F2.pngFloor-zone analysis-F3.png

Moving Pattern -Per Employee Analysis

This Dashboard shows the Movement across zones over each day per employee prox card. We can zoom in/out our analysis by using the Floor / Time Filter on the right.
Moving pattern employee analysis.png

Findings & Problems identified
  1. For floor 1, Most people appears at F1-Z7, F1-Z2 and F1-Z8 in the morning and F1-Z7 in the afternoon. The zones mentioned above are offices and meeting rooms.
  2. F1-Z1 and F1-Z4 generally have the same pattern: there are 3 peak period per day: around 7-8 AM, 11-2PM and 5PM. These time period can be categorized as: come to work, lunch break and leave office.
  3. For floor2, people are evenly spread among all the offices in the afternoon. In the morning, there are noticable large group of people stay at F2-Z6(Meeting & Training) room. This may indicate employees normally gather in the morning for meeting and back to their office in the afternoon.
  4. F2-Z5 and F2-Z7 generally have the same pattern: there are 2 peak period per day: around 9 AM and 2PM.
  5. For floor3, people are evenly spread among all the offices.
  6. F3-Z1, F3-Z2 and F3-Z3 generally have the same pattern: there are 2 peak period per day: around 9 AM and 2-3PM.
  7. There are 2 different types of employees by working hour: 8AM-5PM; 4PM-12AM (detailes can be found in dashboard)
  8. Problem:Some of the employees seem to change prox card frequently (e.g. G.Florez changed 5 security cards over 5 days). The lost cards may cause potential problems (e.g. P.young was tracked of using 2 cards on the same day appearing at different zones, which may be someone else using one of the card)

Notable pattern in Building data

Notable anomalies or unusual events

Observed relationships between the proximity card data and building data elements

Visualization Software

Final Outcome

Conclusion

Comment