| Introduction | Scenario1, 2, 3, 4 | Appendix A, B, C, D, E |
Scenario 1: Creating a New Project
Tasks
In this scenario, you will be creating and configuring a new automation design project.
1.) Open a new project in the prototype.
2.) Configure the following project tasks:
Task Name: Set up System View
Reference Materials: Scope of Work Document, Requirements Specification
Applications Used: System View Builder
Result: System View Created
Task Name: Submit Bid Package
Reference Materials: Scope of Work, Design Specifications, Requirements Specification, Bill of Materials
Applications Used: Bid Builder
Result: Bid Package Completed
Task Name: Modify Ladder
Reference Materials: Ladder_Start
Applications Used: RSLogix 500
Result: Updated Ladder File
3.) Create users with the following attributes:
Name: John Smith
Username: jsmith
Title: Project Manager
Email: jsmith@automationworld.com
Name: Mike Jones
Username: mjones
Title: Controls Engineer
Email: mjones@automationworld.com
Name: Cindy Clark
Username: cclark
Title: HMI Programmer
Email: cclark@automationworld.com
4.) Assign the tasks you created in Task 2 to the users you created in Task 3 as follows:
Set Up System View: John Smith
Submit Bid Package: Cindy Clark
Create HMI: Mike Jones
5.) Create milestones as follows:
Name: Phase One
Due Date: 10/01/00
Tasks: Set Up System View
Name: Phase Two
Due Date: 11/01/00
Tasks: Submit Bid Package
Name: Phase Three
Due Date: 12/01/00
Tasks: Create HMI
The project selection
screen.
The
first step of the new task wizard, where users name the new
task.
The
second step of the new task wizard, where usersThe
third step of the new task wizard, where users
specify
the task's reference materials.specify
which applications will be used in the task.
The
fourth step of the new task wizard, where users The
fifth step of the new task wizard, where users review the
specify
the result or materials produced by the task.task
they have created.
The
New User dialog, where users can configure new The
Assign Tasks dialogs, where users can
project
participantsassociate
users with tasks.
The
Create Milestone dialog, where users can define The
web view of the Project which results from New
due
dates for tasks or groups of tasks.Project
Setup.
 | Users were looking for a getting started or quick help guide. |
| "In general, Engineers don't like to have to manually enter a lot of data" |
| "Change 'users' to something like resources. We understand this term" |
| "There are many different design methodologies, this software shouldn't assume the steps in development are Preliminary Design, Final Design, Development, and Testing." |
| The project set-up is not something that many of the engineers we talked to would complete. |
| Users wanted to auto assign a job number when they started or saved a project. |
| "Configuration Management and revision control for our projects is an important requirement." |
| Users felt that specifying "applications used" in the New Task Wizard was something they wouldn't want to do. |
| Some users felt as though the project managers who were working through the wizard would lack the domain expertise to define a task effectively. |
| Participant would rather work with the tabular view after they have created the first instance using the wizard. They feel wizards typically take too long to complete & therefore would rather fill in the information within a table. |
| User wants to be able to assign multiple users to a task and multiple tasks to a user. |
| "We want to be able to assign tasks to groups- this doesn't matter unless you have a large and complex group." |
| "We should be able to drag users to tasks or tasks to users." |
| Positive feelings about the web view were directly associated with project management experience. Users with more project management responsibilities had poorer opinions of current project management tools and greater interest in the web view. |
| "Its interesting to graphically see what our thought process is." |
| "The Linear/Web Project Manager interface is very useful. Our engineers will love this." |
| "This really is neat because it shows the contingencies. I'd like to see the length of time this task would take. I'd like to see this information in both views- web & matrix." |
| One user really liked the web project model view. The items he'd identify would be: proj management, engineering, manu., programming, field service. He says, for all projects, you would utilize one or more of these items. |
| "This is my main view of the project?" |
| " I would rather see the finished diagram as a flowchart, not a web. I would include a few different layers which allow me to drill into different view if the flow." |
| "Are there different diagramming types available?" |
| "These documents do not get finished before the next docs down the line are started. This drawing communicates a linear process. It's not a linear process." |
| "Overall, the web view of the project is confusing. Not sure of a better way to present the information, but there is too much here for me to understand the relationships between tasks, milestones, etc." |
| Users wanted to be able to see: time to complete the task, who's required to complete it; notes on that individual, schedules, vacation, etc. for each resource. Also, % complete for each task; resources available for each task; revisions for each document. |
| "We want to be able to filter project information by person." |
| "We need to look at Resource Allocation and loading because we are concerned that when we assign a task to a resource and auto generate and email, that we may have a resource over-allocation situation and we'd be embarrassed by it." |
| "I assume we can put notes on users in the matrix view?" |