Year in Review

2021

YearInReviewSummary.docx

Support Resources

  • concern when Harry and Catherine are no longer on project
  • would benefit from centralized team or person for support
  • dedicated Divisional staff were not budgeted for nor obtained
  • would benefit from a centralized Knowledge Base
  • 1 Division is unhappy with the support and responsiveness level and communication manner of Cameron at ReSolved; would like to investigate other individuals in ReSolved or other companies that could be available

Staffing Resources

  • under-estimated the amount of work and time needed for TGRIP
  • under-estimated number of staff required for sustainment
  • 1 Division plans to develop and train AROs to (1) become SMEs for customer service needs and (2) write requirements and workflows
  • 2 Divisions have AROs as first line of contact for external users
  • concern of trained and knowledgeable staff leaving Division and creating a gap
  • lack of a Business Analyst to review and convey business needs
  • IT Support
    • no IT support assigned: PF&R, SSHA/HS, SDFA
    • over-taxed IT support: EDC
    • SNP has 2 IT resources at 20% time

Grant Streams and Builds/Flexibility of System

  • concern of future builds being required and not having resources to complete in-house
  • not confident about in-house testing completed to sign off on builds
    • knowledge of required testing needs and practices felt to be lacking
  • 3 Divisions would like the builds to always be relevant and changeable for needs that are not anticipated and in response to emerging community needs
  • too much customization for individual programs in system making them difficult to repurpose
  • difficulty when time cycles are not standard
  • flexibility for work that is needed due to emergencies or time-sensitive needs
  • integration with SAP/S4 is desired
  • concern that regression testing will always be needed to ensure unexpected changes do not occur to existing programs

Training

  • including tooltips in the system for users that direct on actions needed to complete work
  • would prefer individual topics trained in smaller modules
  • non-technical training language for those expected to make sustainment changes
  • include a guided path of tutorials e.g., beginner, intermediary, expert, etc.
  • repository of information and training manuals should exist

Sustainment and Maintenance

  • under-estimated level of time commitment needed for sustainment
  • unclear of what is covered in the agreement with SmartSimple
  • unclear of the boundaries of work for Re-solved VS SmartSimple
  • worry that other Divisions making changes will negatively impact builds of their Division unintentionally

Cost

  • smaller Divisions have smaller funds available for additional items (e.g., new builds)
  • would like to know yearly fees at the onset (licensing and signatures costs are based on usage and not estimates)
  • amendments and changes being out of scope and requiring additional payments

External Users

  • some had a steep learning curve
  • some grassroots organizations do not have the staffing or technical knowledge capacity to complete all steps required
  • would like an internal storage area for Org docs without an associated application

Archiving Data

  • would like capability to close or archive applications and funding opportunities and freeze changes