Proceedings of the 12th European Conference on Knowledge ...

Figure 2: Explicit knowledge inside IDSC
Mohamed Farid
3.3 Observation for IDSC internal work process
IDSC internal business work schemes across its departments, as shown in figure 3 below, rely on
planned projects, ad-hoc activities or ordinary administrative business processes. Our focus in this
paper will be on both planned projects and ad-hoc activities as <strong>the</strong>y constitute <strong>the</strong> core work <strong>of</strong> IDSC.
Figure 3: IDSC internal work schemes.
The planned projects have predefined start and end dates, always managed by projects tracking
system, and go through sequential processes until <strong>the</strong>y are approved finally by a “Quality Assurance”
process, as shown in figure 3. As a real example inside IDSC, development <strong>of</strong> economic or social
study should be assigned to a primary responsible department, <strong>the</strong> responsible department start
assigning <strong>the</strong> work to an internal team, this project could require data and information to be ga<strong>the</strong>red
from internal and external sources, as later on this data should be analysed to support <strong>the</strong>
development <strong>of</strong> <strong>the</strong> concerned study. In most cases, communications with o<strong>the</strong>r departments are
established to collaborate in necessary activities related to <strong>the</strong> work in progress. After <strong>the</strong> work has
been achieved, <strong>the</strong> output study will be handled by <strong>the</strong> “Quality Assurance” department to be revised.
In most cases, <strong>the</strong> output is re-sent again to <strong>the</strong> responsible department to apply changes required
corresponding to revision comments. The process <strong>of</strong> “Quality Assurance” goes through an archiving
information system to exchange all related documents between <strong>the</strong> responsible department and
“Quality Assurance” department. Finally <strong>the</strong> output will be registered in <strong>the</strong> project tracking system.
On <strong>the</strong> o<strong>the</strong>r hand, <strong>the</strong> ad-hoc activity is carried out as a response to an external demand from a
decision maker that must be supplied in a short time, its output maybe registered or not, depending
on <strong>the</strong> situation. Not to mention, this work never goes through any collaborative environment system.
Figure 4: The internal work process <strong>of</strong> a planned project inside IDSC
1109