The user database is essentially blank when you purchase the software application. Before data can be collected in the Work Set view, you will need to enter some basic information into the database.
Specifically, you'll need to define:
Privilege Levels: (a.k.a. Access Rights) These determine what software features are available to a set of users. For example, you might define a Privilege level called Data Entry, which you can use for those Operators that will only do Data Entry. You decide which features they need to have available to them, so you could, for example, prohibit them from editing data.
Users: When you add a user, you specify an optional password (which the user can later change) and a previously-defined Privilege Level (see above).
Processes and Characteristics: You might want to re-label Processes to Parts, as we discussed in the last slide, but whatever you call them they are the top level in the data hierarchy: A Process (or Part) consists of Characteristics to be measured. Beneath each characteristic in a given Process is the data you collect.
Work Sets: As discussed, we decide how data will be collected, and create Work Sets to include whatever Characteristics (from one or more Processes) are needed to meet your data collection needs.
You'll probably find it easiest to build the database in the Explorer View.