23.01.2014 Views

READIT-2007 - Indira Gandhi Centre for Atomic Research

READIT-2007 - Indira Gandhi Centre for Atomic Research

READIT-2007 - Indira Gandhi Centre for Atomic Research

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The infrastructure based approach integrates all OM in to a single system and hence<br />

provides higher benefits, since it is spread across the entire organization rather than a few<br />

process. The process based approach is more suitable <strong>for</strong> small organizations with well<br />

defined OM goals. The infrastructure approach is preferred <strong>for</strong> large organizations, where the<br />

OM needs are not known, but the organization knows that OM is necessary.<br />

Studies of different OM implementations (Ackerman, 1994) reveals that, the success<br />

rate of process based OM is high compared to infrastructure based organization wide OM.<br />

Hence, it is suggested that even in infrastructure based organization wide OM, it is preferable<br />

to break OM into manageable pieces, that correspond to specific process, task, project or<br />

department and integration of these smaller pieces to <strong>for</strong>m the overall OM. This hybrid<br />

approach of having an overall plan of infrastructure based OM, identifying the components as<br />

process based OM and finally integrating to <strong>for</strong>m the complete organization wide OM has the<br />

dual benefits of infrastructure based approach and process based approach.<br />

Design of OMS<br />

The basic components of OMS are capturing, storing, searching, retrieving, using and<br />

assessing OM. The issues affecting the design of OMS are perspective of OM from different<br />

organizational groups, in<strong>for</strong>mation overload, quality control and security of OM, capturing<br />

mechanism , storing, retrieval, usage and integration of memory components. OM<br />

repositories need to be designed to accommodate different types of data like meta data,<br />

structured data, semi structured data and unstructured data. Organization and representation<br />

of memory and the user interfaces are the keys to success of OMS. Effective memory maps<br />

need to be designed based on the user requirements. Capture of certain memory can be done<br />

automatically from transaction processing system. However it is also required to capture<br />

manually by designated personnel. Thecontent in OM ages with time and need to be purged<br />

when it is no longer required. Methods <strong>for</strong> identifying and purging outdated memory, like<br />

validity period and automatic/ administrator controlled purging after the validity period etc.<br />

need to be evolved. Design of OMS should also consider the technology infrastructure like<br />

network, servers, storage, back up devices etc. A typical OMS applicable <strong>for</strong> a large <strong>Research</strong><br />

and Development Organization is depicted in figure 2.<br />

Projects HR Finance<br />

Procurement & Materials<br />

Management<br />

Scientific Data<br />

Warehouse<br />

Quality Control & Security<br />

Mapping<br />

Digital Library<br />

Per<strong>for</strong>mance<br />

Department<br />

Department Department n<br />

Purging<br />

Users &<br />

Figure-2 Organizational Memory System<br />

196

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!