Prototype ReportVersion 3.1

Prototype Report

LADOT Scanning

Team 08

Name / Primary Role / Secondary Role
Anirudh Govil / Project Manager / Life Cycle Planner
Jeffrey Colvin / Prototyper / Systems and Software Architect
Aditya Kumar / Feasibility Analyst / Project Manager
Nisheeth Joshi / Systems and Software Architect / Life Cycle Planner
Niraj Brahmkhatri / Operational Concept Engineer / Requirements Engineer
Corey Painter / IIV&V / Shaper

Version History

Date / Author / Version / Changes made / Rationale
10/05/11 / JC / 1.0 / ●Original template / ●Initial draft for use with ICM EPG Template version 2.1
10/07/11 / JC / 1.1 / ●Updated Team Roles / ●Team roles in v1.0 were incorrect
10/14/11 / JC / 2.0 / ●Updated diagrams and descriptions
●Changed formatting / ●Project specifications had changed since v1.1
●Response to feedback on v1.1 by TA’s (such as Navigation Flow being incorrect)
●New format is easier to follow
10/16/11 / JC / 2.1 / ●Added additional prototype photos
●Updated team roles / ●Additional diagrams for further clarification
●Team roles were further updated on the team website
10/23/11 / JC / 3.0 / ●Updated diagrams to have no conditional components
●Broke down sections into our deliverables compared to future plans / ●Changes from the ARB session and project rescoping
11/21/11 / JC / 3.1 / ●Updated diagrams and models with up-to-date information / ●Prototype has changed slightly with requirements

Table of Contents

Prototype Report

Version History

Table of Contents

Table of Tables

Table of Figures

1 - Introduction

1.0 - Purpose of the prototype report

1.1 - Status of the prototype

2 - Navigation Flow

2.1 - Truck Navigation Flow

2.2 – Future Consideration

2.2.1 – Computer Navigation Flow Chart

3 – Prototype

3.1 – Login Screen

3.2 – Call Log Popup

3.3 – Job Perform Screen

3.4 – Log Issue Report

3.4 – Future Consideration

3.4.1 – Task Allocator Screen

3.4.2 – Report Windows

Table of Tables

Table of Figures

Figure 1 - Truck Navigation Flow Chart______

Figure 2 – Computer User Navigation Flow Chart______

Figure 3 - Login Screen______

Figure 4 - Call Log Screen______

Figure 5 - Job Perform Screen______

Figure 6 - Log Issue Popup______

Figure 7 - Task Allocator Screen______

PRO_TRR_F11a_T08_V3.1.docVersion Date: 11/21/11

1

Prototype ReportVersion 3.1

1 - Introduction

1.0 - Purpose of the prototype report

The purpose of the prototype report is to outline the current system prototype and its changes from previous revisions as well as show how the prototype will meet project requirements.

1.1 - Status of the prototype

This version of the prototype report has updated navigation flow and screenshots from the actual prototype instead of mock-up pages.

2 - Navigation Flow

2.1 - Truck Navigation Flow

Figure 1 - Truck Navigation Flow Chart

The Truck Navigation Flow Chart (Figure 1), shows the navigation flow of the system in place on the LADOT field worker trucks. The truck’s software will only be able to be accessed by a Field Worker. Once logged in, a field worker can log that they have received a call from any screen and can log-out from any screen. Once a job has been selected, you can perform the job, which allows you to log issues. Once a job is finished, the user is returned to the selection screen.

2.2 – Future Consideration

2.2.1 – Computer Navigation Flow Chart

Figure 2 – Computer User Navigation Flow Chart

The Computer User Navigation Flow Chart (Figure 2) , show the navigation flow for user’s on the computer. There are 3 types of users who can use the computer system: Field Employees, Department Supervisors and Task Allocators. Each user will be able to log in but are then directed to different pages.

2.2.1.1 – Field Employees

The the field employee, once logged on to the system, will be able to view their own maintanence reports and edit them if they require.

2.2.1.2 – Department Supervisors

Department supervisors will be directed to a search screen. On the search screen, they will be able to perform 2 different searches: by location and by employee. The search by employee will only be visible if the Department Supervisor is given the permission to view that employee’s reports. Both search result screens will show a table sorted chronologically (most recent completed first), with columns sortable by: time assigned, time started, time completed, job type and work order number. The Employee search will also have a sortable column by location and the Location search will have a sortable column by employee name.

2.2.1.3 – Task Allocators

Task allocators will be brought to a screen that shows them a map of the trucks currently active as well as the current jobs that need assigning. Additionally to the map, there will be 2 lists, one for trucks and one for jobs. When the task allocator selects either a truck or a job, they will be able to assign a task. When selecting a truck to assign a task to, the task allocator will be prompted to select at least one task to assign to the truck. When selecting a task, the task allocator will be prompted to select only one truck to assign the task to. The Task Selection screen will show either a map and list of trucks or tasks, depending on what the assignment is for. The map will show the location of the truck or the task being assigned, and the list will be sorted by distance.

3 – Prototype

3.1 – Login Screen

Figure 3 - Login Screen

Figure 3, Login Screen, denotes a simple log-in screen for the truck software. The page simply requires entering a user name and password.

3.2 – Call Log Popup

Figure 4 - Call Log Screen

Throughout the program, field worker’s may log their calls at the “Log Job Call” popup window. Figure 4 shows the Log Job Call popup on top of the perform job screen. The Log Job Call popup allows workers to log all pertinent information in regards to receiving a call about a specific job. When finished, pressing the “Log Call” button will log the call and return the field worker to their current screen.

3.3 – Job Perform Screen

Figure 5 - Job Perform Screen

When actually doing a job, the field worker will be presented with the Job Perform Screen. Upon arriving, the user will push the “Log Arrival” button, which will time-stamp on the screen their arrival time. A similar action will be done upon completion and departure.

The right side of the screen is designated to various problems that could have arisen while performing the job. This list will propigate with IssueChains created via the Log Issue Report button.

When the “Log Departure” button has been pressed, the job will be closed, and the next job will be selected or the user will be prompted to log more calls.

3.4 – Log Issue Report

Figure 6 - Log Issue Popup

The log issue popup allows the user to log issues related to the job. The page first contains only 1 combobox, with each selection generating the next list section. When completed, pressing “Log Issue” will log the current issue chain to the job.

3.4 – Future Consideration

3.4.1 – Task Allocator Screen

Figure 7 - Task Allocator Screen

The Task Allocator Screen is broken down into 3 main components: the map, the trucks list and the tasks list. Certain actions do not change the physical screen page, but instead just change the layout of the current page (with the screen shot being of the basic default page).

When the task allocator selects a truck from either the truck list or the map, the truck list is hidden, the trucks on the map are all hidden (except for the truck being given an assignment). The task list is updated to also have the distance from the current location in a column. The task allocator can than either select multiple tasks from the map or the task list and click an “assign” button (not shown for clarity of base screen) to assign the tasks.

Similar functionality exists for the tasks except hiding the tasks items and showing the trucks from the above example.

3.4.2 – Report Windows

As there are multiple report windows, none have been drawn. Each of the report windows (the user maintanence screen, the manager location screen and the manager employee screen) contains a simple sortable table with appropriate headers.

PRO_TRR_F11a_T08_V3.1.docVersion Date: 11/21/11

1