It is necessary to recognize that much of the information gathered before and during the conceptual design phase was largely based on experience. This may be appropriate during a conceptual design process. As the design matures, additional regulatory requirements that impact ANS with the often conflicting user requirements must be coordinated to make this a user-friendly facility. Critical information must be collected, validated, and integrated for the designer. This same information can be reorganized to glean additional information from a different perspective. With the complex management structure, subcontracting arrangement, and potential geographical dispersion of the ANS design team, the current MORRZ tool must be expanded to allow ANS to manage the explosion of information that will result with the start of detailed design.

The original MORRZ tool was developed as a flat-file data base, required labor intensive data input, and was designed to operate on a stand-alone personal computer. MORRZ is currently being upgraded to take advantage of a server-based computer network that will ultimately link essentially the entire ANS design team, including personnel at remote locations. Data input and retrieval capability will be greatly expanded. Rather than incorporate all the information into one data base, MORRZ is being redesigned as a relational data base that will access existing information from other sources if the information is in the correct format.

MORRZ will continue to provide the architect/engineer and the user with the necessary user-friendly computer interface that can be tailored to either a design discipline system or a functional area. The actual MORRZ model--a collection of data tables in a relational data base--ensures that all information exists in a common location what it can be readily accessed, though it may be displayed in many different forms. Such a method could ease the burden of data input and would also ensure information was current.

Some of these design tools guide the designer through a logic process as well as extracting data for incorporation in the model. Some examples include the interface assessment check list (Fig 8), project schedule, cost estimate, equipment lists, work breakdown structure (WBS), and procurement information. New development will incorporate radiation zone definition, maintenance resource utilization, definition of common model structure for future integration of unknown requirements, and expanded data input capabilities.

Because of the ANS schedule and the constantly evolving project needs, development of MORRZ will extend ova many years. A MORRZ committee to oversee requirements definition and development of the model has been identified and will function throughout the life of ANS.

Many of the data collected during the design phases predicts anticipated daily activities within the facility. That data will be useful to the operator in planning routine activities and the consumption of resources for maintenance and operation and control. Computer interfaces specifically tailored to those tasks will connect him/her to a central server and be a common link to other planners.

Fig. 8. A display of ICL graphical user interface and MORRZ diagram.

In summary, the ANS team feels that the MORRZ application is useful for controlled planning and design for any complex facility. It allows the designer to collect vast amount of information, examine specific processes over time, and has a GUI (graphical user interface) tailored to the different users. Besides providing a repository of information in a very flexible format it also allows as the designer to predict impacts of design decisions before they are incorporated The ANS design, which incorporates many smart features, is a testimony to the usefulness of MORRZ

Where to?

[ Return to Index | or | ANS Home Page | or | Hanna Shapira's Home Page ]

Revised by hbs 3/21/95