25D - AGMT - PD SOFTWARE SYSTEM - Laserfiche WebLink

Home Browse Search

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