Laserfiche WebLink
Cit Corn Services <br />Fit /Gap and Contract Support <br />identified during the evaluation and selection process (independent of the Business Case <br />findings). <br />1 -4: Prepare Comparative Analysis (12 hours) <br />Identify RIMS modules that may need to be developed by SAPD IT personnel (i.e., Personnel <br />Management, Background and Training, Select CAD Features, etc.), and consolidate all Phase 1 <br />findings in a Comparative Analysis, <br />Cit Corn would triage all identified gaps, and develop closure recommendations for each. <br />Specifically, Cit Corn would: <br />• Triage all gaps in a Comparative Analysis to prioritize those which may impact the <br />implementation time, cost, quality, or scope. <br />• Prioritize all gaps identified in the SAPD Business Case. <br />• Review each priority gap with Boris (and anyone else associated with reviewing the gaps). <br />• Review each priority gap with TriTech to identify how their solution could fully, or <br />partially, close each one. <br />Review the potential gap closure approach with the SAPD personnel impacted by <br />the gap closure. The employees would be asked to develop a recommended <br />closure for each gap (Close with technology, close with business process change, <br />close with a combination of both; or, accept the gapl). Where applicable, Cit Corn <br />will elicit the following: <br />I. I-low will SAPD's policies and procedures be impacted by the <br />recommended closure? <br />L Cit Corn could draft recommended Policy and Procedure language <br />associated with any gap closure, in concert with the standard <br />Lexipol format and content. <br />ii. Which specific individuals are accountable for closing each gap (including <br />technology closures)? <br />' Gaps are typically "closed" In one of the following four approaches: l) Close the Gap with Technology: This option <br />identifies the specific technology modifications, or enhancements, that are necessary to affect change. Beyond <br />literal software applications, this category often includes a training component (when product functionality is <br />resident In the current applications, but is unknown to the end user) as well as an application workaround (using <br />alternative product features to close a gap); 2) Close the Gap with Business Change: This option modifies the existing <br />business practices to conform to the design, and workflow, of the technology; 3) Close the Gap with a Combination, <br />or; 4) Accept the Gap: This least -used option is applied when closure is deemed by the organization to be impractical <br />or untenable. <br />lei <br />