The technical interfaces between th

The technical interfaces between the system(s) to be
procured in this project, the existing systems, and the
systems procured in other parallel projects are well
defined, not too complex, and not too heterogeneous.
The supplier’s responsibility is clear, and it is clear
who is responsible for parts that are not included in the
supplier’s responsibility.
Responsibilities of strategic ITnS management.
Obviously, this success criteria cannot be achieved by a
single IT project, nor is it llkely to come into existence
without planning. Consequently, the utility will
become responsible for the architectural design of the
EIS, and it should be a long term goal for the utility’s
SISP to manage the EIS architecture so that the
technical interfaces that must be dealt with by the
individual projects are well defined, structured, and
reasonably homogenous. SISP should also provide
adequate models of existing systems, and planned
future systems, to the IT projects. Today, such models
are often reproduced by every new program or project.
Furthermore, the models are today often informal boxand-line
diagrams lacking several qualities needed to
support the SISP (1 1). From a SISP point of view, the
EIS Architecture should includes a number of blackbox
components, since the suppliers should be kept
responsible for their internal architectural design (8).