Portal features

Annotations:

• Interaction with external systems 1. Blackjack does periodic calls to MLog for all contracts that are imported but not completely registered and activated.  2. Blackkjack receives accident data from MZone and return customer data, vehicle data, and insurance data to MZone 3. Blackjack creates user in MZone.
• Main Blackjack resources is:  1. Policies which contains information about insured person, insured vehicle, and installed unit 2. Accidents

1. Login Page
   1. Login with invalid user
      1. Error message
   2. Login with valid user
      1. Insurance company employee (Insurer or IE)
         1. Policies (Upload Results) istead of grid will be summar
         2. Accidents
         3. Users Detailed Edit
         4. Views
            1. Insurance
               1. Overview device
               2. ECall? Not included for HDI
               3. Reporting
         5. Insurance and Assistance administartion
            1. Enter and edit insurance master data
            2. Enter and edit the assigned assistance company(s) master data
            3. Insurance configurations

               Annotations:

               • o Escalations additionally per mail o Claim creation via mail or GDV or other  not necessary in first step o Several mail addresses for claim creation, escalation, process problems, etc. o SLA  see section 5 o Response times Assistance  not necessary in first step o Response times insured person  not necessary in first step
            4. Assistance configurations

               Annotations:

               •    o  Interfaces o  Contact details, way of contact o  Escalation possibilities o  Save user for status change   
      2. Administrator (PA) - Syways
         1. Admin Homepage
            1. Upload Policies

               Annotations:

               • Upload file format validation: 1. Uploaded file format is correct 2. Field data in uploaded file is correct e.g. is field which expected to be a number is actually a number etc. 3. If uploaded file wants to update allready existing policy, check if some immutable policy properties is going to be changed, if yes verification failed 4. If action is "N" - "new   contract" but such contract allready exists verification fails
            2. Policies (Upload Results) ??? istead of grid will be summary
            3. Logged Content
            4. Accidents
            5. Users Detailed Edit
            6. User Management
            7. Editing configurations
            8. User administration ??? maybe the same as User Management
            9. Reporting
            10. Support and FAQ
      3. Insured person (IP)
         1. First drive invitation page
         2. First drive complete page
         3. History
         4. Accidents
         5. User Detailed Edit
         6. View
            1. User profile

               Annotations:

               •   - user can edit profile according to the field definition (see excel) - Possibility to administrate several vehicles (family fleet) à not for HDI - Possibility  to administrate drivers including main users (even though for HDI we only need 2 drivers, up to 5 should be foreseen in the database)  
            2. Installation help

               Annotations:

               • specific info about device and vehicle model saved and there is  link to this info. The same info which was send during registration
            3. ECalls
            4. Theft? Not necessary for HDI
         7. Non-Standard functions
            1. Score
            2. Feedback
            3. Ranking
            4. logbook pdf
            5. trip type (B/P)

               Annotations:

               • this info will be included in logbook downloaded pdf and in MZone
2. Registration

   Annotations:

   • Everyone with registration link
3. Change Password

   Annotations:

   • Any authenticated person
4. Contact Form

   Annotations:

   • Access: Unauthorized user, IP Contact form available from start page for unauthorized users and insured persons. Insured persons have  fields First Name, Last Name, Mail address prefilled and not editable. Form sends an email to configured address containing form data. Categories: * Support * Suggestions  * Feedback  * Other
5. Background processes
   1. Escalation process for registration

      Annotations:

      • necessary if registration is not done in a certain time frame.   1.       Send configured count of emails after configured periods to a configured portal management email address and if possible, to customer email address, if sent device is not registered. 2.       Send configured count of emails after configured periods to a configured portal management email address and customer email address if registered device is not activated. 3.       Send configured count of emails after configured periods to a configured portal management email address and if possible, to customer email address, if activated device is not registered. 4.       Sending of  Activation completed message (mail or sms) to customer and configured insurance company email.  
6. FAQs