Visualization 

 Challenge 

 I have interesting experience of visualization tool . Together with team we were working on task of   metallurgical plant energy efficiency improving . Main challenges were creating a team from different   departments ( other plants ) and focused , involved the members on solving so big task . At first the task   was really huge ; we could n’t not understand scope of the problem and structuring approach for it .   However , we had to show , that the energy was important part of future development of plant , because   management did n’t pay significant attention on it ( main focus on productivity ) – so we had to change   the management vision . 

 The visualization helped us to initiate the process and provide plant management engagement ;   determine high - level structure of solution and find interesting way for technical and organization   problems . 

 Selection & Application 

 At first , we have to determine scope of problem and main causes . It was necessary for fully   management engagement . For it our team used benchmarking results visualization . We prepared   several slides and diagrams with situation consideration . It was new view for management , because   they could n’t imagine , that the plant had so big gaps between average levels of energy consumption and   actual plant consumption . Then the team showed the energy prices dynamic on simple graphs – so we   presented our vision , however the visualization let us to shear it more efficiency . So , the management   could see only numbers , however , during the presentation they saw full picture and get main idea . The   presentation with simple graphs and diagrams helped us to initiate the project . 

 Next step was solution structure . The scope was so huge , that trying to prepare detailed plan and   schedule did n’t make a sense . In this case we decided to use fishbone diagram with main areas of   solution finding . This step let us go step by step without spending a lot of time on administration . Each   team member understood finding logic , map of solution and next big steps . We moved from hypothesis   to hypothesis . So , we covered full problem structure and find several interesting technical and   organization solution . Also , we used visual board with current status and process dynamic . It was   efficiency for engagement , motivation and team contribution filling . 

 On last stage of the project our team also used visualization tools – check list for operators ( everyone   could understand efficiency regimes and operators ’ contribution in the future results – correct actions   and behavior ) and posters , which described how the energy efficiency projects connected with   ecological . 

 Insight & Approach 

 I was leading the projects , when I started to learn the course . One moment I find interesting idea , that   result of our project could be considered like a product . Other words we helped to reduce energy   consumption and to achieve new level of efficiency – it is also product . Before start we did n’t know   what exactly would be the solution , we had to find and check different hypothesis , arranged interview   with engineers and operators for more convenient solution finding . Because alignment of employee our   results did n’t make a sense . The idea helped me to find new communication approach – it was easy to   engage people in product development ; easy to understand the results like a product – better for team 

 motivation . For same production processes very difficult to understand final point before deep analysis .   And product approach helped us went to solution without specific details , we found the details step by   step . 

 One thing is required other approach . During solution finding we focused on fixed high - level structure .   We were flexible with details and hypothesis , however was conservative with solution structure . So , our   team could find more interesting ways and ideas , if the team was more open minded . We limited our   vision , because the limitation was comfortable for process , but not efficiency for final results . Main   lesson – to arrange flexible approach for main structure and detailed hypothesis ; find correct balance   between project turbulence and team confidence . 


EMAIL: 
ID_NUM: 
NAME_STUDENT: 
PHONE_NUM: 
STREET_ADDRESS: 
URL_PERSONAL: 
USERNAME: 

### Task: You are a PII (Personal Identity Information) Detection. Given a essays written by students, you have to identify ONLY the following:
NAME_STUDENT - The full or partial name of a student that is not necessarily the author of the essay. This excludes instructors, authors, and other person names.
EMAIL - A student’s email address.
USERNAME - A student's username on any platform.
ID_NUM - A number or sequence of characters that could be used to identify a student, such as a student ID or a social security number.
PHONE_NUM - A phone number associated with a student.
URL_PERSONAL - A URL that might be used to identify a student.
STREET_ADDRESS - A full or partial street address that is associated with the student, such as their home address.
### Input: Visualization 

 Challenge 

 I have interesting experience of visualization tool . Together with team we were working on task of   metallurgical plant energy efficiency improving . Main challenges were creating a team from different   departments ( other plants ) and focused , involved the members on solving so big task . At first the task   was really huge ; we could n’t not understand scope of the problem and structuring approach for it .   However , we had to show , that the energy was important part of future development of plant , because   management did n’t pay significant attention on it ( main focus on productivity ) – so we had to change   the management vision . 

 The visualization helped us to initiate the process and provide plant management engagement ;   determine high - level structure of solution and find interesting way for technical and organization   problems . 

 Selection & Application 

 At first , we have to determine scope of problem and main causes . It was necessary for fully   management engagement . For it our team used benchmarking results visualization . We prepared   several slides and diagrams with situation consideration . It was new view for management , because   they could n’t imagine , that the plant had so big gaps between average levels of energy consumption and   actual plant consumption . Then the team showed the energy prices dynamic on simple graphs – so we   presented our vision , however the visualization let us to shear it more efficiency . So , the management   could see only numbers , however , during the presentation they saw full picture and get main idea . The   presentation with simple graphs and diagrams helped us to initiate the project . 

 Next step was solution structure . The scope was so huge , that trying to prepare detailed plan and   schedule did n’t make a sense . In this case we decided to use fishbone diagram with main areas of   solution finding . This step let us go step by step without spending a lot of time on administration . Each   team member understood finding logic , map of solution and next big steps . We moved from hypothesis   to hypothesis . So , we covered full problem structure and find several interesting technical and   organization solution . Also , we used visual board with current status and process dynamic . It was   efficiency for engagement , motivation and team contribution filling . 

 On last stage of the project our team also used visualization tools – check list for operators ( everyone   could understand efficiency regimes and operators ’ contribution in the future results – correct actions   and behavior ) and posters , which described how the energy efficiency projects connected with   ecological . 

 Insight & Approach 

 I was leading the projects , when I started to learn the course . One moment I find interesting idea , that   result of our project could be considered like a product . Other words we helped to reduce energy   consumption and to achieve new level of efficiency – it is also product . Before start we did n’t know   what exactly would be the solution , we had to find and check different hypothesis , arranged interview   with engineers and operators for more convenient solution finding . Because alignment of employee our   results did n’t make a sense . The idea helped me to find new communication approach – it was easy to   engage people in product development ; easy to understand the results like a product – better for team 

 motivation . For same production processes very difficult to understand final point before deep analysis .   And product approach helped us went to solution without specific details , we found the details step by   step . 

 One thing is required other approach . During solution finding we focused on fixed high - level structure .   We were flexible with details and hypothesis , however was conservative with solution structure . So , our   team could find more interesting ways and ideas , if the team was more open minded . We limited our   vision , because the limitation was comfortable for process , but not efficiency for final results . Main   lesson – to arrange flexible approach for main structure and detailed hypothesis ; find correct balance   between project turbulence and team confidence .
### Output: 