27.06.2013 Views

Information and Knowledge Management using ArcGIS ModelBuilder

Information and Knowledge Management using ArcGIS ModelBuilder

Information and Knowledge Management using ArcGIS ModelBuilder

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

Walter Castelnovo<br />

the potential risks that SCIA could entail. By <strong>using</strong> st<strong>and</strong>ard tools for risks analysis <strong>and</strong> evaluation (for<br />

instance those described in (IMA 2007), through this step each partner is thus able to associate to the<br />

SCIA under processing a level of risk, with respect to the matters on which he has competence.<br />

Besides evaluating the potential risks involved, during this phase each partner can also plan the<br />

execution of their control activities on that SCIA. The timing of these activities depends both on the<br />

level of risk detected <strong>and</strong> on the other activities in which that agency is possibly already occupied.<br />

The team review allows the partners to jointly evaluate the SCIA on the basis of the potential risks<br />

each one of them identified individually, thus arriving at a shared risk evaluation. Such an evaluation<br />

forms the basis for determining the more adequate risk treatment strategy to assume among<br />

accepting, rejecting or h<strong>and</strong>ling the risks.<br />

Figure 2: Integration of TRM within the SUAP’s workflow<br />

In the case we are considering, accepting the risk means that the team evaluation is such that the<br />

level of risk of the SCIA is not ranked high; thus, also considering the other constraints that could<br />

possibly limit the partners’ activities, there is no particular problem in delaying, <strong>and</strong> even possibly<br />

avoiding, the ex-post controls. Rejecting the risk amounts to recognizing that the SCIA does not<br />

involve any particular risk <strong>and</strong> could thus be treated in terms of a silent-assent procedure. Finally,<br />

h<strong>and</strong>ling the risk means adopting mitigation plans with the aim of reducing the risks involved in the<br />

SCIA by implementing appropriate risk mitigation actions. Such actions will amount to the competent<br />

authorities planning <strong>and</strong> performing all the required ex-post controls with a timing that will allow the<br />

processing of the SCIA to be completed within the terms provided by law (60 days).<br />

Once defined <strong>and</strong> agreed on by all the participants to the team review, each partner has to implement<br />

its own risk h<strong>and</strong>ling actions, according to the timing defined by the team review. As observed above,<br />

the execution of the risk h<strong>and</strong>ling options can introduce secondary risks that need to be managed.<br />

These risks can be determined by the occurrence of unforeseen situations that could affect the<br />

partners’ capacity to execute the risk h<strong>and</strong>ling actions within the terms agreed on. Such risks should<br />

be promptly identified <strong>and</strong> treated since a delay in one partner’s activity could affect the final result of<br />

the processing of a SCIA. Moreover, because of the potential consequences they could have on the<br />

other partners’ activities, the emergence of these risks should be promptly communicated to the<br />

partners, in order to let them assume all the measures apt to cope with the new situation.<br />

In the TRM model this can be done by a repeated execution of the team review process. However,<br />

due to the strict temporal constraints the processing of a SCIA must satisfy, in the situation we are<br />

considering the team review process cannot be implemented simply as a periodic meeting among the<br />

partners, as it is considered in (Higuera et al. 1994). Since in this case the reiteration cycles of both<br />

the team review process <strong>and</strong> the continuous processes must be much shorter than those described in<br />

the original model, all these processes should rather be implemented as continuous communication<br />

processes through which people belonging to the same organization, as well as people from different<br />

organizations, interact continuously on a daily basis.<br />

95

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

Saved successfully!

Ooh no, something went wrong!