| Introduction | Scenario1, 2, 3, 4 | Appendix A, B, C, D, E |
This section is comprised of interactions with the library manager paper prototype. It is arranged into two subsections: paper prototype artifacts, and user feedback.
Participants were introduced to the library manager as they performed various tasks in the paper
prototype, and given as little assistance as possible when interacting with it.
The Library Manager shows
The
Library Manager showing a
a list of tasks available tolist
of project documents for
the user.reuse.
The Library Manager shows a
list of lines for reuse, with their
associated devices and device
assemblies.
 | "I want the ability to store data in a common location" |
| "I think it's very important to have a centralized place for information" |
| One user immediately recognized the Library Manager, and saw the value-add. "I would want to pull templates of key elements (tasks, budgets, PM engineering, program and field service information)." |
| Many participants experienced at least 50% reuse. |
| "I want the ability to upload a template first, before I do anything else. I want to auto-populate with project template specifications. I want to pull in templates from a similar project for reuse here so that I can customize them for the EVEREST." |
| "Show me a list of users and sort them by roles. I don't want to have to go through a step-by-step wizard configuration." |
| "I do a lot of reuse. This would be helpful, because we reuse about 90% of what we do." |
| "Batching Process in 90 % re-use, Pelding is 99 % re-use. Receiving only 50% re-usable because everyone routes the raw materials differently." |
| "We have a lot of standard code. We tie the I/O to the registry in which it's used. We tie the inputs to trigger the bits." |
| "We should be able to pull in existing NT users, or add new ones." |
| "I would like a way to attach comments about each device describing what worked and what did not." |
| "I should be able to sort by implementation method (IEC 518), quality assurance projects, Functional specification, SW specification, test spec., ECAD, E drawings, Panel builds, PLC coding, HMI coding, module test, system test, factory acceptance test." |