An IT Architecture for Emory University
Adopted by CIRT
Directory Service Domain Architecture
February 20, 2002
ITA Version 2.4.6
© 2000 Emory University
Page 12-30
29. Manage the Emory-wide Directory in a unified way.
Status: Adopted
Emorys IT departments and unit leaders should have a common vision and
understanding of what it means to have an Emory-wide directory, and there should
be a process to implement and enforce that vision across Emory. This is needed
even when IT responsibility is decentralized.
Justification
§
A common vision and understanding simplifies governance. It makes it easier to make
decisions for the good of the whole organization, especially when such decisions are
not optimal for a particular unit.
§
The customer base is the entire Emory community. A unified approach, as opposed to
just a centralized approach, helps to accommodate the diversity of perspectives
present in a diverse organization. Broad representation enables decisions to take into
account the full context and implications of the decisions.
§
An Emory-wide view helps to identify situations where an Emory-wide directory could
potentially add value. Examples include situations where process and data sharing
occur across Emory.
§
A unified approach also facilitates a systemic, consistent, Emory-wide view of the data
in the directory and of the meaning of those data items.
Implications
1.
A unified approach will require an organizational structure that enables cooperative
decision-making and cooperative enforcement.
2.
Organizationally, unification will have to represent the perspectives and needs of many
constituencies informally or formally, including Emory-wide, unit, and central IT.
3.
A governing body that is inclusive and representative of all the components of Emory
will be needed.
4.
There will need to be a process and organizational structures to establish policies,
priorities, principles, product standards, and configurations, and to manage the
directory organization and its contents, including approving changes.