|
NETMATION
BUSINESS
CONSULTING
SOFTWARE
HELP
|
Technical Architecture
Introduction
A technical architecture defines the "technologies" that are
required to support an organization's automation environment. The
goal of a technical architecture is to identify and define those
technologies that are critical to the implementation and use of a
new applications environment. The level of definition is, by
design, at a high level. If the definition of technologies and
configurations was too detailed and specific, the architecture
would be too restrictive to allow growth and would rapidly fall
out-of-date in relation to advances in technology. The level of
detail presented should be taken as a guideline for implementing
any of the technologies or procedures defined in an architecture.
Goals of a technical architecture are:
The primary goal of the technical architecture study is to provide
an architecture (or environment) within which your company will
have the capability of accessing data to meet your needs in an
easy manner. The "look and feel" provided by the technology
defined will be very similar throughout organizations if not
exactly the same.
The technical architecture plan contains technical and procedural
recommendations which will facilitate the
group/project/office/interoffice connectivity to support shared
information, input/output devices and message services. The
recommendations address computers, networks, programming software
and data base software. Also included are the technical and
management guidelines which are required to control such an
environment.
An essential element for designing and implementing an integrated
environment is the need to develop an efficient hardware and
communication system for processing and supporting integrated
applications. An integrated technical architecture strategy has
been developed to link the applications and data bases.
The major elements of the strategy include:
Integrated Technical Architecture
A complex integrated technical architecture requires a highly
trained staff to manage resources and provide services. This
staff must perform specialized functions: managing daily
operations, controlling the systems development environment,
maintaining software to operate the environment, and planning for
future requirements. Above all else, the technical environment
must be continually monitored to ensure it meets all business and
engineering requirements.
Ensuring that hardware, systems software, communication networks,
program development standards, and data base resources for
business operations are in place and available.
An effective technical architecture depends on a businesses
ability to deliver sufficient resources to the systems users. The
implementation of the proposed architecture will otherwise fail.
Providing appropriate types of service delivery and maintaining
appropriate performance measurement standards.
The Technical Architecture incorporates specific services to
support the system users. These services range from defining
relational data base management systems to installing a backbone
communications network. Providing these services represents a
major cost; however, the return is an effective mechanism for
supporting integrated applications and integrated project
requirements.
Standardization of a basic technical architecture provides
strategic and economic benefits. However, because systems
integration requires access to more of the hardware, software, and
information resources, it exposes the organization to greater risk
by allowing access to sensitive data. Although unauthorized
access of information is a risk in any systems environment, the
risk is even greater in a decentralized environment because of the
increased access to systems and the complexity of controlling
information.
The integrated systems environment is characterized by a
disciplined approach where the correct information is readily
available to quickly and efficiently do the job right the first
time. This allows the designers and technicians to fully explore
previous operating experience, customer requirements, and total
cost implications of alternatives. To achieve this environment,
the design function must be carefully evaluated and the identified
requirements implemented in an integrated systems environment.
By enhancing and developing new applications and creating data
bases which contain the shared design data, the cycle time
(calendar days) required for the design process can be
substantially reduced. The systems need to continually move
towards the vision that anyone can access any required information
(with proper security and management controls). This can
represent a significant change from the current situation and must
occur over a period of time. It is important to first standardize
the hardware and software platforms, then design the shared data
bases. Once this is accomplished, the applications can be designed
and developed.
Historically, automation has focused on isolated "islands of
automation" due to the paper-based method of information exchange.
The systems recommended in this report will move to an online
information exchange among the design groups. As this evolves,
further opportunities will occur by linking the data bases with
new expert systems. Parametric design systems (where the design
rules are captured and the drawing, bill of material and process
plans are output) must also be evaluated. These systems have the
potential to make conventional software applications, where a
"rule based" repetitive design is required, obsolete. Their
implications must be evaluated before a final commitment is made
to conventional software applications.
It is necessary to implement a mechanism to control all
information created in the design process. This controlling
mechanism will serve as the configuration management function for
all design data residing at multiple project locations. The
document control project as defined in "Project Planning and
Control" will be critical to control the engineering design work
which is regarded as released and also to give other groups the
capability to access the most recent work related to any analysis
or design results. Security will be the key to ensuring that only
authorized groups can update the design data. Thus, all of the
projects outlined here will need to address the configuration
management issues in order to achieve the key benefits.
Application Planning/Administration.
Select a systems development methodology which will fit into the
organization's culture and provide the necessary structure for
designing and implementing all the required systems in the future.
Designate responsibilities for the technical architecture
development projects.
Technical Infrastructure.
Service Delivery.
Define and establish a corporate-wide data administration
function. This function administers the components of the logical
and physical data base design and ensures corporate-wide data
integration.
Initiate a service management process. The new architecture must
provide specific services to support all users.
Formalize the process of capacity planning and performance
management. This process measures the performance and resource
consumption of systems.
Implement a support organization for the resolution of problems.
The purpose of problem management is to maintain and protect the
integrity of the computing environment.
Security and Administration.
![]()
|