Learning Launch .     Challenge   We had a series of special sessions dedicated to design thinking in our organization . It was   decided to find out several perspective directions for innovations . During these sessions , we   split into groups to come up with ideas to implement . Then , we were presenting ideas for   colleagues and they had to choose some of them . One of the approved ideas was changing the   current fleet management system .   Problem description :   Our organization , ​IQBusiness , has offices all over the world . Each country has its own fleet   management system . In our country , we have a country office and three project offices with   cars assigned to each office . The current system does n't allow us to book cars from different   offices . So , sometimes one office does n't have free cars , while another office has several cars . It   has been decided to implement a system with a joint pool of cars to improve this situation ; so ,   when there is no car in your office , you can rent a car from another office . A team consisting of   members from various departments including me was formed to follow up .     Selection and Application   We went through several stages of the process and came up with the three ideas : buying new   software from corporate vendors , re - design our current fleet management system , and try a   fleet management system used in another country by our colleagues . We stopped our choice   on a fleet management system used in another country because a ) it had already decided the   same problems we have ; b ) we had many similarities like the sizes of the offices , region ; and c )   it was free .   We had agreed with colleagues to explore it before accepting it as a solution . So , as described   in the Learning Launch Tool video on Week 4 , the process of a learning launch was started .    We started with the country office and two project offices . We have planned to run three   months ' test and prearranged several learning sessions for our users . During this pilot , our team   collected feedbacks from users , drivers , and administrative staff .     Insight and Approach   The results were very surprising . They were far away from our expectations . We were assuming   that the solution working for the organization with almost the same structure and goals should   work ideally for us . However , the feedbacks were extremely negative . Users complained a lot   about the user interface . Our drivers were very upset that the program has only one language ,   English , while they speak only Russian . Also , the administrative staff was partially satisfied   because they were not happy with how the system manages leaves for drivers .   I believe that there were several causes of this failure , however , the main thing is confirmation   bias in my opinion . We were concentrated on our goal to solve the task we had , and we   " forgot " about the actual users . When we tested the solution by ourselves , we were very   satisfied with a new program : It allowed us to reserve cars from different projects . However , an 

 actual test clearly showed us that the users were very far away from the problem we solved ,   and they did not accept our solution in exchange for their comfort .   Alongside with the solving the above - mentioned problem , our team wanted to introduce a   solution with better user experience , “ better than the current alternative ” . After testing a new   system and getting such results , we decided to postpone the implementation of this solution   and first work on the elimination of the issues we were told by our users . And , of course , we   will make another round of experiment before implementing the solution . Hopefully , this time   we will be more successful .   This example clearly showed us the benefit of design thinking . We had a small experiment   before introducing a big change in the work of the organization and find out a lot of drawbacks   we did not see . So , we have saved resources and we believe that our next solution after these   tweaks will be much better suited for our customers . 


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: Learning Launch .     Challenge   We had a series of special sessions dedicated to design thinking in our organization . It was   decided to find out several perspective directions for innovations . During these sessions , we   split into groups to come up with ideas to implement . Then , we were presenting ideas for   colleagues and they had to choose some of them . One of the approved ideas was changing the   current fleet management system .   Problem description :   Our organization , ​IQBusiness , has offices all over the world . Each country has its own fleet   management system . In our country , we have a country office and three project offices with   cars assigned to each office . The current system does n't allow us to book cars from different   offices . So , sometimes one office does n't have free cars , while another office has several cars . It   has been decided to implement a system with a joint pool of cars to improve this situation ; so ,   when there is no car in your office , you can rent a car from another office . A team consisting of   members from various departments including me was formed to follow up .     Selection and Application   We went through several stages of the process and came up with the three ideas : buying new   software from corporate vendors , re - design our current fleet management system , and try a   fleet management system used in another country by our colleagues . We stopped our choice   on a fleet management system used in another country because a ) it had already decided the   same problems we have ; b ) we had many similarities like the sizes of the offices , region ; and c )   it was free .   We had agreed with colleagues to explore it before accepting it as a solution . So , as described   in the Learning Launch Tool video on Week 4 , the process of a learning launch was started .    We started with the country office and two project offices . We have planned to run three   months ' test and prearranged several learning sessions for our users . During this pilot , our team   collected feedbacks from users , drivers , and administrative staff .     Insight and Approach   The results were very surprising . They were far away from our expectations . We were assuming   that the solution working for the organization with almost the same structure and goals should   work ideally for us . However , the feedbacks were extremely negative . Users complained a lot   about the user interface . Our drivers were very upset that the program has only one language ,   English , while they speak only Russian . Also , the administrative staff was partially satisfied   because they were not happy with how the system manages leaves for drivers .   I believe that there were several causes of this failure , however , the main thing is confirmation   bias in my opinion . We were concentrated on our goal to solve the task we had , and we   " forgot " about the actual users . When we tested the solution by ourselves , we were very   satisfied with a new program : It allowed us to reserve cars from different projects . However , an 

 actual test clearly showed us that the users were very far away from the problem we solved ,   and they did not accept our solution in exchange for their comfort .   Alongside with the solving the above - mentioned problem , our team wanted to introduce a   solution with better user experience , “ better than the current alternative ” . After testing a new   system and getting such results , we decided to postpone the implementation of this solution   and first work on the elimination of the issues we were told by our users . And , of course , we   will make another round of experiment before implementing the solution . Hopefully , this time   we will be more successful .   This example clearly showed us the benefit of design thinking . We had a small experiment   before introducing a big change in the work of the organization and find out a lot of drawbacks   we did not see . So , we have saved resources and we believe that our next solution after these   tweaks will be much better suited for our customers .
### Output: 