Example reflection- Visualization 

 Challenge 

 I work in a legal department of a research centre . Making a robust product in strict timelines in a   highly regulated field is a challenge in itself . With lot of factors affecting quality of product and so   many variables to control , scientists face many challenges in making a robust product . Intellectual   property ( IP)/patents adds further to the complexity of the product . Patents are exclusive rights   granted for new inventions . These rights are enforceable and can lead to lot of litigation cost in case   of infringement . We need to overcome patents for a successful product . 

 Working at the intersection of legal and technical involves implementing IP - compliant as well as   technically feasible strategies . My work involves explaining the legal boundaries of Intellectual   property ( IP)/patent around the product to various stakeholders and come out with IP - compliant   strategies . We face challenge in explaining scientists about scope of a patent and also in motivating   them to overcome IP as it will result in a legally fool proof product . The inability of a scientific mind   to understand legal repercussions of a strategy , often results in a tussle . We are facing issues of non- compliance of IP preferred strategy leading to increased cost in litigation . Scientist tend to outright   ridicule the IP preferred strategy at the outset . 

 Our challenge is to clearly explain the protection of IP and whitespace the scientist can work in and   finding issues that is leading to non - compliance to IP preferred strategy and reason of lack of   motivation . 

 Selection 

 We decided to use visualization tool to explain the scope of intellectual property . The product   involved a complex intellectual property / patent landscape with overlapping scope . Visualization   could help them to understand the patent and product and visualize a green space . 

 Application 

 We used a slide deck to show relevant snippets of text from the patent document on which we were   basing our ( IP ) recommendations . This allowed us to make the stakeholders understand the basis of   our recommendation and also avoided them to have their own interpretations . It was very easy to   make them understand reasons of IP recommendations . 

 We showed IP protected/ claimed space in red and help them visualize green space scientist can   work upon . 

 A simple representation of what tried to make them visualize : 

 After explaining this , we mapped their strategy with the claimed space . 

 Using description of a product and then relating it to patent we could show monetary advantages   that will result if we have an IP compliant strategy in place . It also helped them to demarcate Patent   1 and Patent 2 and think around a strategy that is suitable as whole . 

 Insight & Approach 

 With diverse team looking at the landscape we gained more than usual technical understanding of   product . It resulted in more knowledge sharing among the team . We got insights from practical   knowledge of the scientist and this helped us to find some lacuna or white - space ourselves .   Concerns of scientist were different than what we expected and we got other team to answer their   concerns . The teams were better aligned on designing strategies for the product . 

 A clear understanding triggered a very constructive discussion around various aspects of products   and to our amazement it lead to multiple ways of formulating IP preferred strategies . 

 We learned through this exercise that we need to look at the product as a whole and including other   team on the table will help us in making a better product . 

 * * * * * * * * * * * * * * * 


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: Example reflection- Visualization 

 Challenge 

 I work in a legal department of a research centre . Making a robust product in strict timelines in a   highly regulated field is a challenge in itself . With lot of factors affecting quality of product and so   many variables to control , scientists face many challenges in making a robust product . Intellectual   property ( IP)/patents adds further to the complexity of the product . Patents are exclusive rights   granted for new inventions . These rights are enforceable and can lead to lot of litigation cost in case   of infringement . We need to overcome patents for a successful product . 

 Working at the intersection of legal and technical involves implementing IP - compliant as well as   technically feasible strategies . My work involves explaining the legal boundaries of Intellectual   property ( IP)/patent around the product to various stakeholders and come out with IP - compliant   strategies . We face challenge in explaining scientists about scope of a patent and also in motivating   them to overcome IP as it will result in a legally fool proof product . The inability of a scientific mind   to understand legal repercussions of a strategy , often results in a tussle . We are facing issues of non- compliance of IP preferred strategy leading to increased cost in litigation . Scientist tend to outright   ridicule the IP preferred strategy at the outset . 

 Our challenge is to clearly explain the protection of IP and whitespace the scientist can work in and   finding issues that is leading to non - compliance to IP preferred strategy and reason of lack of   motivation . 

 Selection 

 We decided to use visualization tool to explain the scope of intellectual property . The product   involved a complex intellectual property / patent landscape with overlapping scope . Visualization   could help them to understand the patent and product and visualize a green space . 

 Application 

 We used a slide deck to show relevant snippets of text from the patent document on which we were   basing our ( IP ) recommendations . This allowed us to make the stakeholders understand the basis of   our recommendation and also avoided them to have their own interpretations . It was very easy to   make them understand reasons of IP recommendations . 

 We showed IP protected/ claimed space in red and help them visualize green space scientist can   work upon . 

 A simple representation of what tried to make them visualize : 

 After explaining this , we mapped their strategy with the claimed space . 

 Using description of a product and then relating it to patent we could show monetary advantages   that will result if we have an IP compliant strategy in place . It also helped them to demarcate Patent   1 and Patent 2 and think around a strategy that is suitable as whole . 

 Insight & Approach 

 With diverse team looking at the landscape we gained more than usual technical understanding of   product . It resulted in more knowledge sharing among the team . We got insights from practical   knowledge of the scientist and this helped us to find some lacuna or white - space ourselves .   Concerns of scientist were different than what we expected and we got other team to answer their   concerns . The teams were better aligned on designing strategies for the product . 

 A clear understanding triggered a very constructive discussion around various aspects of products   and to our amazement it lead to multiple ways of formulating IP preferred strategies . 

 We learned through this exercise that we need to look at the product as a whole and including other   team on the table will help us in making a better product . 

 * * * * * * * * * * * * * * *
### Output: 