This document provides specifications for a Matrix page that provides a high-level overview of vehicle data and performance across different sources and stages of a workflow system. The page includes a vehicle source drilldown displaying summaries for each source, and a stage summary view showing metrics for all sources by stage. It defines the required components, screenshots of the design, and additional details for implementation.

1. Matrix Page Specification Template
MIMS Matrix
Matrix Page God View Specification
Overview
This page is primarily dedicated to Mota operations. It is the launch pad for
investigations into the performance of MIMS, and a bird’s eye view into the world of our
Vehicle Sources.
This page must satisfy the following goals:
· Drill down to secondary levels – the Vehicle Source by Fleet page
· Provide access to unique (one off) VINs
· Show up-to-the-minute results of every vehicle according to Vehicle Source ID,
which includes summaries.
· Allow users to upload a new fleet
Screenshot
Date Last Modified: 9/7/2014 1 of 16

2. Matrix Page Specification Template
MIMS Matrix
Page Components
Global Components
Here is a highlighted screenshot of the required global components:
Global elements consist of two primary components: a header component and a footer
component.
Here are the required component definitions for the page:
Component Name Type Definition
Page Title Label Simple string that says “REAL PAGE NAME
HERE”
Mota Exchange
Logo
Image Contains the graphic in Appendix A: Graphics:
Mota Exchange Logo
Global Navigation
Horizontal Rule
Image Contains the graphic in Appendix A: Graphics:
Mota Exchange Logo
Upload Fleet Link Link Link to page to upload vehicles.
Copy: “upload a new fleet”
URI: “unknown”. Need john/greg to specify.
TITLE: “upload a new fleet”
New window? No
Name of new window: N/A
Search for a VIN Label Simple string that says “search for a VIN:”
Search for a VIN TextBox TextBox for VIN
Validate? Yes
Validation type: VIN
Search for a VIN
Button
Button Button to search for a VIN.
Copy: “find VIN”
Functionality: Redirects to XXXX page.
John/Greg: where does this redirect to?
Welcome Message Label Simple string that says “Welcome
<FIRSTNAME> <LASTNAME>.” Here is an
example: “Welcome Jason Stagliano.”
Today’s Date Label Simple string that says “<MONTH NAME>
Date Last Modified: 9/7/2014 2 of 16

3. Matrix Page Specification Template
MIMS Matrix
<DAY OF MONTH>, <YEAR>”. Here is an
example: “January 21, 2007”
Here are the required component definitions for the footer page:
Component Name Type Definition
Copyright Label Link to page to upload vehicles.
Copy: “upload a new fleet”
URI: “unknown”. Need john/greg to specify.
TITLE: “upload a new fleet”
New window? No
Name of new window: N/A
Page Components
Here is the hierarchy of the Page Components on this page:
· VehicleSource By Fleet Drilldown
· Stage Summary God View
Here is a picture of the page components:
Date Last Modified: 9/7/2014 3 of 16

4. Matrix Page Specification Template
MIMS Matrix
VehicleSource By Fleet Drilldown
The primary purpose is to catch a glimpse of how each Vehicle Source ID is
progressing through the workflow system. Various high-level points of interest are
highlighted underneath respective vehicle sources. This module is placed on the left
side of the screen and is the primary index for navigating out of this page. Navigation is
by VehicleSource (repeated vertically).
Here is a picture of the VehicleSource By Fleet Drilldown:
Here are the required component definitions for this page:
Component Name Type Definition
VehicleSource
Repeating Vertical
Summary
List
A container for all the VehicleSources in the
mota exchange. Each container maintains a
summary of the activity for a specific
VehicleSource.
VehicleSourceName Link Link to VehicleSource By Fleet Page.
Copy: VehicleSource name
URI: “unknown”. Need john/greg to specify.
TITLE: VehicleSource name
New window? No
Date Last Modified: 9/7/2014 4 of 16

5. Matrix Page Specification Template
MIMS Matrix
Name of new window: N/A
Last Fleet Upload
Date
Label Complex string that says “last fleet upload date:
mm/dd/yy”
Total Live Vehicles Label Simple string that says “total live vehicles: “
Total Live Vehicles
Count
Link Link to Sales Dashboard. ISSUE: this is not in
any spec that John/Greg have seen.
Copy: Total Live Vehicles Count number
URI: “unknown”. Need john/greg to specify.
TITLE: Total Live Vehicles Count number
New window? No
Name of new window: N/A
Errors to Resolve Link Link to Vehicle Errors By Vehicle Source
Page. ISSUE: this is not in any spec that
John/Greg have seen.
Copy: “errors to resolve: <ERRORS TO
RESOLVE COUNT>”
URI: “unknown”. Need john/greg to specify.
TITLE: “errors to resolve: <ERRORS TO
RESOLVE COUNT>”
New window? No
Name of new window: N/A
Stage Summary God View
This is the content area that actually provides users with an up-to-the-minute snapshot
of all activity from every source in the MIMS system. It’s consolidated by stage level,
and further indexed along three lines: total number of VINs present in that stage,
amount processed without error, and those with errors.
It is on the right side of the screen, and is the primary index for summarizing all
VehicleSources by workflow stage.
Here is a picture of the Stage Summary God View:
Date Last Modified: 9/7/2014 5 of 16

6. Matrix Page Specification Template
MIMS Matrix
Based on the above picture, here are the required component definitions for this page:
Component Name Type Definition
Stage Column
Column Header Displays stage name.
Header
Sortable? No
Supported sort types: N/A
Default sort type: N/A
VehicleSource
Status Row
Column Row By stage, displays status of VehicleSource’s
vehicles in that stage. Contains Total VINS
Count, VINs Processed Count and Errors
Count. Each row correlates to a
VehicleSourceName listed in the
VehicleSource By Fleet Drilldown.
Total VINs Count Label Complex string that says “total VINS: <TOTAL
VINS COUNT>”
Issue: these are not linked. Is that cool? Design
says it is
VINs Processed
Count
Label Complex string that says “VINs processed:
<VINS PROCESSED COUNT>”
Date Last Modified: 9/7/2014 6 of 16

7. Matrix Page Specification Template
MIMS Matrix
Errors Count Label Complex string that says “errors: <ERRORS
COUNT>”
Issue: can this be hotlinked to the Vehicle
Errors By Vehicle Source Page. (described
above)
Additional Requirements
Mota has plans for 5 stages in our business process. Currently, only 3 stages are
implemented. Initial implantation should hide the incomplete 4th and 5th stages. When
those are completed, they should “automatically” show up in this god view.
Issues
Issues
1. The most efficient use of this page (in terms of solving errors) on any given fleet, per
stage, is some sort of aggregate ‘error view’ page, whereby errors – regardless of
workflow step – are displayed on one screen for users to edit. MIMS does not currently
support this requirement, but should allow for this functionality in future iterations.
Future Features
Future Features
1. Notice the second column from the left on the mock-up. This area is designed to
provide users with an iconic system of alerts and notifications (system and user
generated notifications). While no specification exists now, plan for this type of
expansion in the future.
2. On the table is where this page sits in the overall IA flow. Current assumptions: this is
the first page any Mota operations officer will view, which means this is the page that
pops up after login.
Appendices
Appendix A: Graphics
Here are the needed graphics:
Component Name Required information
Mota Exchange
Logo
Path: pathtographicfile.png
Dimensions: 120x80
ALT text: “mota exchange”
Date Last Modified: 9/7/2014 7 of 16

8. Matrix Page Specification Template
MIMS Matrix
New window? No
Name of new window: N/A
Matrix Page Fleet View (Stage 1) Specification
Overview
The Fleet View page is the next ‘step’ in the design flow. Users have the opportunity to
see MIMS step performance on a fleet-by-fleet basis. Steps are separated by stage,
and are presented horizontally.
This page must satisfy the following goals:
· Display all fleets
· Provide access to unique (one off) VINs
· Allow users to upload a new fleet
· Show up-to-the-minute results of every vehicle according to sales group name
· Expand and hide fleet-specific data
Screenshot
Date Last Modified: 9/7/2014 8 of 16

9. Matrix Page Specification Template
MIMS Matrix
Page Components
Global Components
Here is a highlighted screenshot of the required global components:
Global elements consist of two primary components: a header component and a footer
component.
Here are the required component definitions for the page:
Component Name Type Definition
Page Title Label Simple string that says “REAL PAGE NAME
HERE”
Mota Exchange
Logo
Image Contains the graphic in Appendix A: Graphics:
Mota Exchange Logo
Global Navigation
Horizontal Rule
Image Contains the graphic in Appendix A: Graphics:
Mota Exchange Logo
Navigation Prompt Label Simple string that says: “switch to:”
Vehicle Source ID
List
Drop Down Menu Drop down menu that displays all Vehicle
source IDs
Switch Vehicle
Source ID Button
Button Button to switch Vehicle Source ID.
Validate? Yes
Validation Type: Vehicle Source ID
Search for a VIN Label Simple string that says “search for a VIN:”
Search for a VIN TextBox TextBox for VIN
Validate? Yes
Validation type: VIN
Search for a VIN
Button
Button Button to search for a VIN.
Copy: “find VIN”
Functionality: Redirects to XXXX page.
John/Greg: where does this redirect to?
Welcome Message Label Simple string that says “Welcome
<FIRSTNAME> <LASTNAME>.” Here is an
example: “Welcome Jason Stagliano.”
Upload Fleet Link Link Link to page to upload vehicles.
Copy: “upload a new fleet”
Date Last Modified: 9/7/2014 9 of 16

10. Matrix Page Specification Template
MIMS Matrix
URI: “unknown”. Need john/greg to specify.
TITLE: “upload a new fleet”
New window? No
Name of new window: N/A
Today’s Date Label Simple string that says “<MONTH NAME>
<DAY OF MONTH>, <YEAR>”. Here is an
example: “January 21, 2007”
Here are the required component definitions for the footer page:
Component Name Type Definition
Copyright Label Link to page to upload vehicles.
Copy: “upload a new fleet”
URI: “unknown”. Need john/greg to specify.
TITLE: “upload a new fleet”
New window? No
Name of new window: N/A
Date Last Modified: 9/7/2014 10 of 16

11. Matrix Page Specification Template
MIMS Matrix
Page Components
Here is the hierarchy of the Page Components on this page:
· Vehicle Fleet by Source ID drilldown
· Baseline Fleet data
· Step Summary, separated by Stage
· Stage separator
Here is a picture of the page components:
Vehicle Fleet By Source Drilldown
Users should be able to view all fleet activity one Source ID at a time. Presented is a
step-by-step summary of all activity within any given stage. Next to each fleet is an
expand/collapse button that displays some baseline information pertinent to that fleet.
This module is placed on the left side of the screen; it will describe fleet performance,
and give Mota operations a detailed view of all fleet activity in MIMS.
Here is a picture of the VehicleSource By Fleet Drilldown:
Date Last Modified: 9/7/2014 11 of 16

12. Matrix Page Specification Template
MIMS Matrix
Here are the required component definitions for this page:
Component Name Type Definition
Vehicle Fleet
Repeating Vertical
Summary
List
A container for all the Vehicle Fleets in the
mota exchange system. Each container
maintains a summary of the activity for a
specific fleet according to Vehicle Source.
Vehicle Source
Name
Label Simple string that says “<VEHICLE SOURCE
ID>”
Fleet name Label Link to Stage Summary Page in MIMS.
Copy: <Fleet name>
URI: “unknown”. Need john/greg to specify.
TITLE: Fleet name
New window? Yes
For now, the system will list all fleets available,
with the most current sales group on the top.
Future iterations can hide ‘old’ fleets. However,
further user experience research should to be
done to justify the parameters.
Date Last Modified: 9/7/2014 12 of 16

13. Matrix Page Specification Template
MIMS Matrix
Expand/Collapse
Function
Button Button to hide and/or expose additional fleet
information.
Uploaded Vehicles Label Complex string that says “uploaded: <DATE
UPLOADED>”
Total VIN Count Label Complex string that says, “total VINs: <TOTAL
VINS UPLOADED>
Error Count Label Complex string that says “errors: <TOTAL
STAGE ERRORS>”
Stage Summary Fleet View
This is the content area that provides users with an up-to-the-minute snapshot of all
activity from every fleet according to Vehicle Source in MIMS system. It’s displayed
according to steps level, and separated by stage. It scrolls horizontally through the
stages. Please note that the fleet content bucket does not scroll. This is to provide users
with the maximum amount of context when viewing the steps.
It is on the right side of the screen, and is the primary index for summarizing all
VehicleSources by workflow stage.
Here is a picture of the Step Summary for Stage One:
Date Last Modified: 9/7/2014 13 of 16

14. Matrix Page Specification Template
MIMS Matrix
Here is a picture of the Step Summary for Stage Two:
Based on the above pictures, here are the required component definitions for this page:
Component Name Type Definition
Step Column HeaderColumn Header Displays step name.
Columns (in order): [Stage 1] validate data,
validate pricing, assign sales groups, contact
info, validate sales group (SG), approve SG –
EP, approve SG – Mota… [Stage 2] validate
VHR, validate inspection results, sort photos,
verify trim, edit options, content check, QA
approval.
Sortable? No
Supported sort types: N/A
Default sort type: N/A
VehicleSource
Status Row
Column Row By fleet, displays status of VehicleSource’s
vehicles in that step.
Preliminary requirements: Contains Total VINS
Count, VINs Processed Count and Errors
Count. Each row correlates to a Fleet listed in
the VehicleSource By Vehicle Source ID
Drilldown.
Date Last Modified: 9/7/2014 14 of 16

15. Matrix Page Specification Template
MIMS Matrix
End Stage Notifier Image Contains image: “EndStageOne.gif” and
“EndStageTwo.gif”. See Appendix B for details.
Total VINs Count Label Complex string that says “total VINS: <TOTAL
VINS COUNT>”
Issue: these are not linked. Is that cool? Design
says it is
VINs Processed
Count
Label Complex string that says “VINs processed:
<VINS PROCESSED COUNT>”
Errors Count Label Complex string that says “errors: <ERRORS
COUNT>”
Issue: can this be hotlinked to the Vehicle
Errors By Vehicle Source Page. (described
above)
Additional Requirements
Mota has plans for 5 stages in our business process. Currently, only 3 stages are
implemented. Initial implantation should hide the incomplete 4th and 5th stages. When
those are completed, they should “automatically” show up in this god view.
Issues
Issues
1. It is still unclear as to how we will display vehicles.
a. How do we account for vehicle attrition?
b. What about vehicles with multiple statuses per step?
2. There is no method to track total errors and then link to them on one page.
Future Features
Future Features
1. A robust error notifications system with complementing web architecture to:
a. Solve specific problems/tasks
b. Move back and forth between pages after resolving issues.
2. UI solution to handle, track, group, and sort FSBO vehicles.
Appendices
Date Last Modified: 9/7/2014 15 of 16

16. Matrix Page Specification Template
MIMS Matrix
Appendix A: Graphics
Here are the needed graphics:
Component Name Required information
End Stage
Notification
Path: pathtographicfile.png
Dimensions: 40x680
ALT text: “end stage one”
New window? No
Name of new window: N/A
End Stage
Notification
Path: pathtographicfile.png
Dimensions: 40x680
ALT text: “end stage two”
New window? No
Name of new window: N/A
Date Last Modified: 9/7/2014 16 of 16