Laserfiche WebLink
<br />-. '0 ." r- ~\ :"\ r~ <br />~ U oJ G J <br />The Integral Project <br /> <br />, <br /> <br />It is important that the DSS have the capability of accessing and/or utilizing the results from <br />these utility-specific models. To preserve the generic nature of the DSS, however, such <br />models will not be directly integrated (or embedded) into the DSS, but will be considered as <br />'off-line' or 'non-resident' models. Appropriate connections, referred to as Data <br />Management Interfaces (DMIs), will be developed to enable sharing of input and output data <br />between these non-resident models and the DSS. DMIs will also be developed to allow for <br />data exchange with the large, historical data files that are often associated with these <br />complex, off-line models. Exchange of data between the non-resident models and the DSS <br />will allow for the use of the DSS visualization and analysis tools. In this manner, the results <br />of the non-resident models can be incorporated into the scheduling and planning process. A <br />more detailed discussion of non-resident models is presented in Section 4. <br /> <br />Analysis Tools <br /> <br />An important feature of the DSS is the provision of a common set of tools to analyze the <br />results from resident and non-resident models, as well as real-time status information. These <br />tools must be capable of: summarizing model results, evaluating system behavior with <br />respect to performance criteria, tracking model performance, portraying multi-objective <br />tradeoffs, and providing general statistical analysis, along with graphics and reporting <br />utilities. The requirements for the analysis tools are discussed in more detail in Section 5. <br /> <br />Example Applications and The Problem Centered Design Approach <br /> <br />The design of the DSS is based upon a problem centered design (PCD) methodology. PCD <br />uses an incremental design approach, providing iterative interaction between the system <br />designers and the DSS user. The interaction between these two parties is formalized through <br />the development of specific, representative problems for which the user wants decision <br />making support. A number of scenarios are developed whereby the designer lays out the <br />sequence of actions, utilities, models, and data that must be used to solve the specified <br />problems. These scenarios are iteratively reviewed and redesigned by the system designers <br />and users until both parties feel confident that the intended problem solving support has been <br />adequately portrayed. During the design process, the DSS functionality is generalized from <br />the specific problems so that the resulting decision support system will be useful in solving a <br />broad range of similar problems or logical extensions of the original problems presented <br />(Behrens and Ostrowski, 1992). <br /> <br />For the TV A System, six example problems were formulated that would address the major <br />applications intended for the DSS. These problems, which are summarized in Table I, fall <br />into three major categories: <br /> <br />· Scheduling and Forecasting, <br />· Operational Planning, and <br />· Policy Planning. <br /> <br />2-6 <br />