Professional Documents
Culture Documents
Submitted by:
Franklin Parajas
BS Criminology
March 20, 2009
Submitted to:
Dean Tacorda
Organizational architecture
The architecture of an organization provides the framework through which an
organization aims to realize its core qualities as specified in its vision statement. It
provides the
infrastructure into
which business
processes are deployed
and ensures that the
organization's core
qualities are realized
across the business
processes deployed
within the organization.
In this way
organizations aim to
consistently realize
their core qualities across the services they offer to their clients.
* Economy
An effective system is not necessarily an economical (efficient) system. For example, the
postal service may keep on schedule with mail deliveries but only by hiring a large number
of additional workers. In this case, the efficiency of the postal system would be reduced. In
another example, inventories may be controlled by using a comprehensive system of
storekeeping. However, if the cost of the storekeeping were greater than the potential
savings from this degree of control, the system would not be efficient. It is often
dysfunctional and expensive to develop much greater capacity for one segment of a system
than for some other part. Building in redundancy or providing for every contingency usually
neutralizes the operating efficiency of the system. When a system's objectives include
achieving a particular task at the lowest possible cost, there must be some degree of trade-
off between effectiveness and efficiency. When a system's objective is to perform a certain
mission regardless of cost, there can be no trade-off.
* Acceptability
Any system, no matter how well designed, will not function properly unless it is accepted by
the people who operate it. If the participants do not believe it will benefit them, are opposed
to it, are pressured into using it, or think it is not a good system, it will not work properly. If a
system is not accepted, two things can happen:(1) the system will be modified gradually by
the people who are using it, or (2) the system will be used ineffectively and ultimately fail.
Unplanned alterations in an elaborate system can nullify advantages associated with using
the system.
Differentiation and Integration
A basic consideration in the design of organizations is dividing work into reasonable tasks
(differentiation) while giving simultaneous attention to coordinating these activities and
unifying their results into a meaningful whole (integration). Two guidelines may be followed
in grouping activities:
1. Units that have similar orientations and tasks should begrouped together. (They can
reinforce each other's common concern and the arrangement will simplify the coordinating
task of a common manager).
2. Units required to integrate their activities closely should be grouped together. (The
common manager can coordinate them through the formal hierarchy).
When units neither have similar orientations nor share their activities, the task of grouping
becomes more difficult. For example, when units are similar in nature and function but are
also relatively independent, the manager must base his decision on the most appropriate
way to group activities according to his past experience.
A difficult task associated with system-subsystem determination is to establish proper
boundaries of operations. The more specific and distinct the goals of the operation, the
easier it is to set boundaries. Other factors such as the influence of the environment, the
availability of men and machines, the time schedule for design and operation, the cost of
alternative designs, and the particular biases of the designers must be considered when
establishing boundaries.