| 6.1. |
Requirements
for multi-person, multi-discipline, multi-organization and
multi-location team collaboration: |
| |
6.1.1. |
Multiple
people should be able to work on the same model with the software
assisting in conflict resolution |
| |
6.1.2. |
The
team must be able to partition the model, then merge the sub-models |
| |
|
6.1.2.1. |
By
discipline |
| |
|
6.1.2.2. |
By
three-dimensional coordinate region |
| |
6.1.3. |
These
collaboration techniques must operate across the Web |
|
|
| 6.2. |
Requirements
for model management and control: |
| |
6.2.1. |
Ability
to lock in design intent |
| |
6.2.2. |
Ability
to enter non-plotted annotation to document reasons for decisions
or changes |
| |
6.2.3. |
Ability
to prevent changes by unauthorized users identified by: |
| |
|
6.2.3.1. |
Organization |
| |
|
6.2.3.2. |
Discipline |
| |
|
6.2.3.3. |
Project
responsibility |
| |
6.2.4. |
Automated
change notification: |
| |
|
6.2.4.1. |
Graphically
highlight changes |
| |
|
6.2.4.2. |
Maintain
audit trail of when and by whom the changes were made |
|
|
| 6.3. |
Requirement
to maintain multiple, parallel, fully intelligent schemes: |
| |
6.3.1. |
To
archive progress checkpoints |
| |
6.3.2. |
To
study multiple alternatives |
|
|
| 6.4. |
Requirements
for interoperability: |
| |
6.4.1. |
Ability
to integrate models from multiple systems and sources to analyze
interfaces and interferences |
| |
6.4.2. |
Ability
to pull details and intelligent product templates from vendor
Web sites |
