Challenge Summary
Welcome to "GUARD - ZIAP Instant Alert Platform Design Concepts Challenge". In this challenge, we need your help to create the look and feel of our new application called ZIAP. ZIAP is an application aims to contribute towards better and faster customer services by enhancing communication flow between our company representation and Broker or/and Customer.
Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!
3) PolicyRenewalPackage Inspection Screen
4) Who was in charge of fulfilling each stepPolicyRenewalPackage Lifecycle Screens
2) Dashboard Screen
- As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt.
- Make sure all pages have correct flow. Use the proper file numbers, (1, 2, 3, etc.)
1) Login Screen
2) Dashboard Screen
3) PolicyRenewalPackage Inspection Screen
4) Who was in charge of fulfilling each stepPolicyRenewalPackage Lifecycle Screens
5) Notifications Screen
- As part of your Final submission, you must replace your checkpoint submission with the final submission into MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt.
- Make sure all pages have correct flow. Use the proper file numbers, (1, 2, 3, etc.)
Background Overview
Our International Programs offer a tailor made, international insurance solutions to large multinationals across the globe through an international network. It has a local and global presence and strives to deliver customer oriented, compliant programs ensuring along the way high level service and quality. The issuance of programs and related communication towards the vast network can add additional complexity, delays and decreased quality of service due to variety of tools and processes applied.
The process gets delayed starting from information gathering stage due to inefficient email communication and absence of technical solution in place.
Our ZIAP application comes to be a solution and aims to contribute towards better and faster customer services by enhancing communication flow between our company and Broker or/and Customer.
Through instant notifications, standardized information templates and link of other Broker or/and Customer tools, ZIAP ensures faster and more accurate data collections and a great enhancement on communication between teams.
Overall, the ZIAP process split into 4 activity:
1. Data Gathering
2. Data Validation
3. Data Processing
4. Issuance
5. Premium Payment
For this challenge, we only need to cover the first activity "Data Gathering" to make sure an initial minimum product value can be met.
Challenge Goals
Create a simple, modern and efficient UI/UX for an Insurance data gathering solution that able to help enhancing communication flow between different parties and able to ease the items status visualization
ZIAP Application Capability
- Ability to see the PRP renewal status (time frame before it has to be renewed/workflow triggered).
- Ability to visualize status of PolicyRenewalPackages (PRP) within the flow (steps), and status on who is owner of the action.
- Ability to visualize the details of the PRP (policy holder, Broker, expiration date, next action owner etc)
- Ability to send notifications to different actors (brokers, company representative, others) depending on the status of the PRP.
- Ability to modify status of the PRP, so it can move through the steps of the flow
- Ability to introduce new data in order to provide required details for the item.
- Ability to generate pending points/actions list (per user)
- Ability to chat between users.
User Flow
- Our company representative will need to fill up all required data, which is then sent to Broker.
- During this step, minimum data validation is performed, mostly to ensure all renewal mandatory items are present.
- Our company representative responsible for the policy will guide, help and perform such data validations.
- Information gathering to be done in several steps by various parties providing data, validating it in between the steps and sending notifications to assigned parties once action required or the step is complete.
- Here is the data gathering process done:
-- Current IPZ policy system feed the PolicyRenewalPackages at least 71 days before renewal
-- ZIAP Notifies our company representative 70 Days before renewal
-- our company representative validates PolicyRenewalPackage and adds additional data to it if needed
-- ZIAP Notifies Broker 60 Days before renewal
-- Broker reviews PolicyRenewalPackage, sends data to our company representative, sets PRP as ready (for our company representative Data Review)
-- ZIAP Notifies our company representative that PolicyRenewalPackage is Ready for Data Review
-- Our company representative Reviews PolicyRenewalPackage
-- If all data sent by the Broker is correct he can accept it, and the package will be processed
-- If data is wrong or missing, our company representative add comments to the PolicyRenewalPackage and sends it back to Broker:
-- Broker receives Notification from ZIAP
-- Flow reiterates from step 5
Design Compatibility
- Responsive website (can work on desktops & mobile devices)
- Easy to understand flow from page to page
- Intuitive for the user; should never be left asking "what do I do next?"
- Simple, clean, modern.
- Easy viewing for pages that may be over overcrowded with information (eg. when hovering over an item will enlarge for easy viewing or similar)
Design Usability
- Simple; not too many steps involved in any part
- Easy; to understand the navigation from section to section
- Fast; and efficient experience
Branding Guidelines
- Ask in Forum for Access to Branding Guidelines
- Modern Crisp look and feel adhering to our standards.
- Follow our Branding Guidelines Document for design style, font, and colors.
- Designs should reuse our SDK components as much as possible (in cases you need a component is not in the list you can use a one designed by you)
Challenge Forum
If you have any doubts or questions regarding challenge requirements, please ask in our challenge forum:
https://apps.topcoder.com/forums/?module=ThreadList&forumID=622406���
Screen Requirements
For this challenge, we are looking for the below pages to be designed/considered in your concepts. The screen functionality details listed below are suggested functionality for consideration. Do not allow the suggestions below to impact the creativity of design. If there is a better way to accomplish the same goal, then feel free to take creative liberties.
1) Login Screen
- As a User I want to log into the system so that I can interact with it
- Ordinary login form (username, password, forgot password, register)
- Provide error scenario for wrong credential
- Acceptance Criteria: Ability to access the system and visualize data according to my role and rights.
2) Dashboard Screen
- As a User I want to visualize all the ongoing PolicyRenewalPackages so I can take action on them, according to their status
- Acceptance Criteria:
-- Ability to view all PolicyRenewalPackages which I should have access to, based on my roles and rights (Our Company Representative, Broker, Specialist, System Admin)
-- Display minimum information (think of it as a list/table with selectable rows, where each row is an "PolicyRenewalPackage"): type of policy, Policy Number and Status
-- Display time elapsed on the current step (e.g. time to respond by our company representative, Broker).
3) PolicyRenewalPackage Inspection Screen
- As a User I want to be able to select a PolicyRenewalPackage and view its data, and history (if any) so I can take actions and accelerate its resolution.
- Acceptance Criteria:
-- Type of Policy (Master, Local or Freedom of Services (FoS))
-- Policy Number
-- Product Type (D&O Commercial, D&O FI, D&O Side A, Crime Commercial, Crime FI, BBB, AIMI, PTL, EPL, PI A&E, PI Tech, PI Misc, PI FI, PI Lawyers, BPL)
-- Our Company Producing office details: Our company Entity Name, Our company representative Contact Name, Underwriting Specialist Contact Name, Producing Country
-- Customer details: Entity Name, Address, Phone, email. Country
-- PolicyRenewalPackage status within the flow: Every step that has occurred within this PolicyRenewalPackage since it was created: Time elapsed in each step
4) Who was in charge of fulfilling each stepPolicyRenewalPackage Lifecycle Screens
4.1) Start PolicyRenewalPackage Lifecycle Screen
- as company representative, I want to be able to select a PolicyRenewalPackage, and set it to be started. I also want to be able to add a new free text note that will be attached to the PRP and visible by all parties.
- Acceptance Criteria:
-- A note to the PRP can be added with defined requirement for an assigned party
-- A field to define a due date to complete the action
-- When inspecting an PolicyRenewalPackage there is the possibility to "start" its flow
-- After starting the flow the assigned Broker receives a notification
-- Field to attach a document/multiple documents in various formats
4.2) Submit Data
- As a Broker I want to be able to select one of my pending PolicyRenewalPackages and upload the documents/data that is required and set it as fulfilled so it can be sent back to the company representative to validate
- Acceptance Criteria:
-- The PolicyRenewalPackage inspection screen is displayed
-- The Input requirement section is displayed and list the documents/data that I need to submit to the company representative
4.3) Validate PolicyRenewalPackage
- As an company representative I want to be able to review PolicyRenewalPackages sent/fulfilled from the broker, so I can assess the information sent and confirm that the PolicyRenewalPackage is ready to be sent to the next step ("Processing") or not
- Acceptance Criteria:
-- If an PolicyRenewalPackage is rejected there should be the possibility to add a note specifying the reason of rejection
-- The PolicyRenewalPackage should be marked as processed if all data is correct.
-- The PolicyRenewalPackage should be assignable to the Broker (if any of the data received is wrong or missing)
4.4) Resubmit PolicyRenewalPackage
- As a Broker I want to be able to reprocess Incorrect/Incomplete PolicyRenewalPackage, so I can correct it and send it back to the company representative
- Acceptance Criteria:
-- I have the possibility to open my PolicyRenewalPackages that are incorrect/incomplete
-- I see a list of all the notes on the pending/incorrect items on the PolicyRenewalPackage
-- I can set the PolicyRenewalPackage done/fulfilled and this should assign it back to the company representative
-- I can add a note to the PRP with comments
5) Notifications Screen
- A notification is received which can be selected and the system displays the corresponding actionCommunication
- The system should provide easy channels so that users can communicate (for ex, user chat, chat bot, however, these chat features is out of scope)
- The system should be able to notify one/several users when one of following takes place:
5.1) A PolicyRenewalPackage to be initiated
- As a company representative, I want to receive notifications when a PRP to be initiated, 70 days before expiration of the policy.
5.2) A PolicyRenewalPackage needs further actions:
- As a Broker user I want to receive notifications when PolicyRenewalPackages need further actions so I have an easy way to follow the lifecycle of the PolicyRenewalPackage
- Acceptance Criteria:
-- A notification when action is pending/ a new PRP assigned for Broker completion
-- A notification is received when the PRP change its status is "rejected" (validation has been performed, but the package cannot be processed due to missing/incorrect data)
-- A notification is received when PRP change its status to "complete"
5.3) A PolicyRenewalPackage has been idle for too long
- As a company representative I want to receive notifications when a PolicyRenewalPackage has been stuck for longer than defined in the created action ("due date").
Important:
- Keep things consistent. This means all graphic styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance
Marvel Prototype
- We need you to upload your screens to Marvel App.
- Please send your marvel app request to fajar.mln@gmail.com (Challenge Copilot)
- You MUST include your Marvel app URL (in your marvel app prototype, click on share and then copy the link & share it with your notes/comment this link while you upload).
Documentation (Ask in Forum)
- Flow Document
- Branding Guidelines Document
Target Devices
- This application will be created as responsive web app
- For this challenge, you only need to focus on Desktop device
- 1366px width with height adjusting accordingly
Target Audience
- Internal Employee
- Broker
Judging Criteria
Your submission will be judged on the following criteria:
- Overall idea and execution of concepts
- How well does your design align with the objectives of the challenge
- Execution and thoughtfulness put into the solving the problem
- Overall design and user experience
- Cleanliness of screen design and user flow
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
- Submit JPG/PNG image files based on Challenge submission requirements stated above
- MarvelApp link for review and to provide feedback
Source Files
All source files of all graphics created in either Adobe Photoshop/Illustrator/Sketch and saved as editable layer
Final Fixes
As part of the final fixes phase, you may be asked to modify your graphics (sizes or colors) or modify overall colors.
Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!
Round 1
Submit your initial design for a Checkpoint Feedback3) PolicyRenewalPackage Inspection Screen
4) Who was in charge of fulfilling each stepPolicyRenewalPackage Lifecycle Screens
2) Dashboard Screen
- As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt.
- Make sure all pages have correct flow. Use the proper file numbers, (1, 2, 3, etc.)
Round 2
Submit your Final Design plus Checkpoint Updates1) Login Screen
2) Dashboard Screen
3) PolicyRenewalPackage Inspection Screen
4) Who was in charge of fulfilling each stepPolicyRenewalPackage Lifecycle Screens
5) Notifications Screen
- As part of your Final submission, you must replace your checkpoint submission with the final submission into MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt.
- Make sure all pages have correct flow. Use the proper file numbers, (1, 2, 3, etc.)
Background Overview
Our International Programs offer a tailor made, international insurance solutions to large multinationals across the globe through an international network. It has a local and global presence and strives to deliver customer oriented, compliant programs ensuring along the way high level service and quality. The issuance of programs and related communication towards the vast network can add additional complexity, delays and decreased quality of service due to variety of tools and processes applied.
The process gets delayed starting from information gathering stage due to inefficient email communication and absence of technical solution in place.
Our ZIAP application comes to be a solution and aims to contribute towards better and faster customer services by enhancing communication flow between our company and Broker or/and Customer.
Through instant notifications, standardized information templates and link of other Broker or/and Customer tools, ZIAP ensures faster and more accurate data collections and a great enhancement on communication between teams.
Overall, the ZIAP process split into 4 activity:
1. Data Gathering
2. Data Validation
3. Data Processing
4. Issuance
5. Premium Payment
For this challenge, we only need to cover the first activity "Data Gathering" to make sure an initial minimum product value can be met.
Challenge Goals
Create a simple, modern and efficient UI/UX for an Insurance data gathering solution that able to help enhancing communication flow between different parties and able to ease the items status visualization
ZIAP Application Capability
- Ability to see the PRP renewal status (time frame before it has to be renewed/workflow triggered).
- Ability to visualize status of PolicyRenewalPackages (PRP) within the flow (steps), and status on who is owner of the action.
- Ability to visualize the details of the PRP (policy holder, Broker, expiration date, next action owner etc)
- Ability to send notifications to different actors (brokers, company representative, others) depending on the status of the PRP.
- Ability to modify status of the PRP, so it can move through the steps of the flow
- Ability to introduce new data in order to provide required details for the item.
- Ability to generate pending points/actions list (per user)
- Ability to chat between users.
User Flow
- Our company representative will need to fill up all required data, which is then sent to Broker.
- During this step, minimum data validation is performed, mostly to ensure all renewal mandatory items are present.
- Our company representative responsible for the policy will guide, help and perform such data validations.
- Information gathering to be done in several steps by various parties providing data, validating it in between the steps and sending notifications to assigned parties once action required or the step is complete.
- Here is the data gathering process done:
-- Current IPZ policy system feed the PolicyRenewalPackages at least 71 days before renewal
-- ZIAP Notifies our company representative 70 Days before renewal
-- our company representative validates PolicyRenewalPackage and adds additional data to it if needed
-- ZIAP Notifies Broker 60 Days before renewal
-- Broker reviews PolicyRenewalPackage, sends data to our company representative, sets PRP as ready (for our company representative Data Review)
-- ZIAP Notifies our company representative that PolicyRenewalPackage is Ready for Data Review
-- Our company representative Reviews PolicyRenewalPackage
-- If all data sent by the Broker is correct he can accept it, and the package will be processed
-- If data is wrong or missing, our company representative add comments to the PolicyRenewalPackage and sends it back to Broker:
-- Broker receives Notification from ZIAP
-- Flow reiterates from step 5
Design Compatibility
- Responsive website (can work on desktops & mobile devices)
- Easy to understand flow from page to page
- Intuitive for the user; should never be left asking "what do I do next?"
- Simple, clean, modern.
- Easy viewing for pages that may be over overcrowded with information (eg. when hovering over an item will enlarge for easy viewing or similar)
Design Usability
- Simple; not too many steps involved in any part
- Easy; to understand the navigation from section to section
- Fast; and efficient experience
Branding Guidelines
- Ask in Forum for Access to Branding Guidelines
- Modern Crisp look and feel adhering to our standards.
- Follow our Branding Guidelines Document for design style, font, and colors.
- Designs should reuse our SDK components as much as possible (in cases you need a component is not in the list you can use a one designed by you)
Challenge Forum
If you have any doubts or questions regarding challenge requirements, please ask in our challenge forum:
https://apps.topcoder.com/forums/?module=ThreadList&forumID=622406���
Screen Requirements
For this challenge, we are looking for the below pages to be designed/considered in your concepts. The screen functionality details listed below are suggested functionality for consideration. Do not allow the suggestions below to impact the creativity of design. If there is a better way to accomplish the same goal, then feel free to take creative liberties.
1) Login Screen
- As a User I want to log into the system so that I can interact with it
- Ordinary login form (username, password, forgot password, register)
- Provide error scenario for wrong credential
- Acceptance Criteria: Ability to access the system and visualize data according to my role and rights.
2) Dashboard Screen
- As a User I want to visualize all the ongoing PolicyRenewalPackages so I can take action on them, according to their status
- Acceptance Criteria:
-- Ability to view all PolicyRenewalPackages which I should have access to, based on my roles and rights (Our Company Representative, Broker, Specialist, System Admin)
-- Display minimum information (think of it as a list/table with selectable rows, where each row is an "PolicyRenewalPackage"): type of policy, Policy Number and Status
-- Display time elapsed on the current step (e.g. time to respond by our company representative, Broker).
3) PolicyRenewalPackage Inspection Screen
- As a User I want to be able to select a PolicyRenewalPackage and view its data, and history (if any) so I can take actions and accelerate its resolution.
- Acceptance Criteria:
-- Type of Policy (Master, Local or Freedom of Services (FoS))
-- Policy Number
-- Product Type (D&O Commercial, D&O FI, D&O Side A, Crime Commercial, Crime FI, BBB, AIMI, PTL, EPL, PI A&E, PI Tech, PI Misc, PI FI, PI Lawyers, BPL)
-- Our Company Producing office details: Our company Entity Name, Our company representative Contact Name, Underwriting Specialist Contact Name, Producing Country
-- Customer details: Entity Name, Address, Phone, email. Country
-- PolicyRenewalPackage status within the flow: Every step that has occurred within this PolicyRenewalPackage since it was created: Time elapsed in each step
4) Who was in charge of fulfilling each stepPolicyRenewalPackage Lifecycle Screens
4.1) Start PolicyRenewalPackage Lifecycle Screen
- as company representative, I want to be able to select a PolicyRenewalPackage, and set it to be started. I also want to be able to add a new free text note that will be attached to the PRP and visible by all parties.
- Acceptance Criteria:
-- A note to the PRP can be added with defined requirement for an assigned party
-- A field to define a due date to complete the action
-- When inspecting an PolicyRenewalPackage there is the possibility to "start" its flow
-- After starting the flow the assigned Broker receives a notification
-- Field to attach a document/multiple documents in various formats
4.2) Submit Data
- As a Broker I want to be able to select one of my pending PolicyRenewalPackages and upload the documents/data that is required and set it as fulfilled so it can be sent back to the company representative to validate
- Acceptance Criteria:
-- The PolicyRenewalPackage inspection screen is displayed
-- The Input requirement section is displayed and list the documents/data that I need to submit to the company representative
4.3) Validate PolicyRenewalPackage
- As an company representative I want to be able to review PolicyRenewalPackages sent/fulfilled from the broker, so I can assess the information sent and confirm that the PolicyRenewalPackage is ready to be sent to the next step ("Processing") or not
- Acceptance Criteria:
-- If an PolicyRenewalPackage is rejected there should be the possibility to add a note specifying the reason of rejection
-- The PolicyRenewalPackage should be marked as processed if all data is correct.
-- The PolicyRenewalPackage should be assignable to the Broker (if any of the data received is wrong or missing)
4.4) Resubmit PolicyRenewalPackage
- As a Broker I want to be able to reprocess Incorrect/Incomplete PolicyRenewalPackage, so I can correct it and send it back to the company representative
- Acceptance Criteria:
-- I have the possibility to open my PolicyRenewalPackages that are incorrect/incomplete
-- I see a list of all the notes on the pending/incorrect items on the PolicyRenewalPackage
-- I can set the PolicyRenewalPackage done/fulfilled and this should assign it back to the company representative
-- I can add a note to the PRP with comments
5) Notifications Screen
- A notification is received which can be selected and the system displays the corresponding actionCommunication
- The system should provide easy channels so that users can communicate (for ex, user chat, chat bot, however, these chat features is out of scope)
- The system should be able to notify one/several users when one of following takes place:
5.1) A PolicyRenewalPackage to be initiated
- As a company representative, I want to receive notifications when a PRP to be initiated, 70 days before expiration of the policy.
5.2) A PolicyRenewalPackage needs further actions:
- As a Broker user I want to receive notifications when PolicyRenewalPackages need further actions so I have an easy way to follow the lifecycle of the PolicyRenewalPackage
- Acceptance Criteria:
-- A notification when action is pending/ a new PRP assigned for Broker completion
-- A notification is received when the PRP change its status is "rejected" (validation has been performed, but the package cannot be processed due to missing/incorrect data)
-- A notification is received when PRP change its status to "complete"
5.3) A PolicyRenewalPackage has been idle for too long
- As a company representative I want to receive notifications when a PolicyRenewalPackage has been stuck for longer than defined in the created action ("due date").
Important:
- Keep things consistent. This means all graphic styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance
Marvel Prototype
- We need you to upload your screens to Marvel App.
- Please send your marvel app request to fajar.mln@gmail.com (Challenge Copilot)
- You MUST include your Marvel app URL (in your marvel app prototype, click on share and then copy the link & share it with your notes/comment this link while you upload).
Documentation (Ask in Forum)
- Flow Document
- Branding Guidelines Document
Target Devices
- This application will be created as responsive web app
- For this challenge, you only need to focus on Desktop device
- 1366px width with height adjusting accordingly
Target Audience
- Internal Employee
- Broker
Judging Criteria
Your submission will be judged on the following criteria:
- Overall idea and execution of concepts
- How well does your design align with the objectives of the challenge
- Execution and thoughtfulness put into the solving the problem
- Overall design and user experience
- Cleanliness of screen design and user flow
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
- Submit JPG/PNG image files based on Challenge submission requirements stated above
- MarvelApp link for review and to provide feedback
Source Files
All source files of all graphics created in either Adobe Photoshop/Illustrator/Sketch and saved as editable layer
Final Fixes
As part of the final fixes phase, you may be asked to modify your graphics (sizes or colors) or modify overall colors.
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.