Page 74 -

A Company and its Data 35

negative effect. In that case, MDM must replace PLM, as
long as it is able to integrate the subsystems of R&D and
that the workgroup functions, i.e. its workflow data
approval, are adapted.

1.5.4. Lightweight Directory Access Protocol (LDAP)

Among the most common data repositories, the one that is
concerned with the description of an organization is very
important. It holds the description of the geographical,
organizational structures as well as the people involved. It
can also contain other descriptions linked to a number of a
company’s assets.

Under the effects of functional and technical silos, IT
looks to rationalize the “directory” aspect of organization
description. This deals, in particular, with the unification of
user identifier and password management used to authorize
access. An LDAP IT standard is adapted to this type of
repository. In this way, most software packages, operating
systems and desktop solutions are compatible with this
standard, which allows directory access to be rationalized.

Over time, this directory has taken a wider turn,
integrating partner descriptions, other information about
contact details (email, telephone, etc.) and also
administrative assets (conference room, projector, etc.) in
order to supply resource reservation tools. Going from a
functional use, the limitations of LDAP becomes obvious.
These limitations are linked to the absence of business
governance functions. Only IT experts can manage LDAP
data, especially as they become more and more complex.

The associations between business objects, for instance,
between the description of a manager and their
administrative assets (offices, projectors, computers, books,
etc.) are difficult to handle adequately. In the end, facing the