= (product) UI Review - 02.21.2001 =

To protect the rights of my clients, all names and proprietary information has been omitted.

Attendees

(names omitted)

 

Agenda

 

1. Outline general information about the product.

2. Review survey results to identify key features & functionality.

3. Review past UI Review recommendations.

3. Look at the current iteration.

 

Points of Discussion 

Overview of the product

(product) is the heart of a Change Management Solution that consists of four basic elements

*    Revision Control

*    Change Documentation and Audit Trail

*    Backup & Recovery

*    Audit Logging and Reporting

Features

*    Maintenance Organization, Information, and Monitoring Center…

*    Central Maintenance Information Center
    -Information access, Information viewing

*    License Management and File Check-out
    -Check out licenses and project files based on rights and availability
    -Automatic detailed configuration change audits

*    Revision Control
    -Enforced revision rules and procedures

*    User Access and Profiles
    -Secure, managed access to maintenance functions

*    Event Repository
    -Single point to track plant maintenance activity

 

Survey Results

All of the functionality identified in the survey conducted at Automation Fair 2000 is included in the current version.  Therefore, there is no need to justify priorities.  However, we can do another rev of this survey for future customer interviews.

 

Past UI Improvement Recommendations

We reviewed items covered by this illustration of recommendations

 

Next Steps

 

*    UE team needs to provide

*    product icon

*    splash 

*    login

*    login confirmation

 

*    Share the (product) Change mgmt. PowerPoint presentation – Laura & UE

 

 

UI Improvements

*    Standardize and distinguish background color of content vs. headings

*    Change scroll bar in the event logger to scroll just the events, do not scroll the event headings

*    Use more redundancy to identify the difference between information, error, etc.  Since the operator needs to gather this info quickly, use standardized symbols behind the written identifier.

*    Allow users to customize their view of the information

*    change around columns

*    change around windows

*    close columns & windows that they don't want to view