CHEFS Objectives & Key Results

Objectives and Key Results

Business Case Commitments

1. Enhance the security measures of CHEFS by ensuring confidentiality, integrity and availability of sensitive government and personal data

2. Improve system scalability and performance by allowing CHEFS to handle an increased user size and workload while maintaining desired levels of performance

3. Reduce effort and cost of updating the CHEFS product to align any changes made to the BC Gov Brand

4. Facilitate a sustainable expansion of the service by decreasing user requests for help from support channels and project team by offering users resources (self-service documentation, chat interface)

5. Improve user login experience and identifiable information collection by providing single sign on integration 

6. Increase the consistency of the users' experiences and the trust they have in the product when submitting information to government

Digital Plan Alignment

The quarterly objectives are aligned with the 4 missions set out in the 2023 Digital Plan. Each mission contained calls to action in the areas of connected services, digital trust, reliable and sustainable technology, and a digitally equipped BC Public Service.

Common Components Roadmap

Capabilities available today

• Email Notifications (external service - CHES)

  • Submitters can forward themselves a link to their submission

  • Submitters are notified if their submission is changed to the status “Completed”

  • Form Owners can be notified at a specified email address

  • Emails are sent to a person that is assigned a permission on a form

  • Emails are sent to a person that is assigned a permission on a draft submission

  • Emails can be sent to notify a submission reviewer that an exported list of submissions is ready for download.

• Document Generation (external service - CDOGS)

  • Downloading a pdf of a submission

  • Exporting a list of submissions (JSON or CSV)

  • Printing to a template

• Submitting form attachments and uploading reusable print templates (external service - OCIO Object Storage)

• Form Design and Form Submission (CHEFS)

  • Showing a list of data in a drop down on a form from a secure external API

  • Autocomplete address field using the BC Geocoder

  • Autocomplete legal BC business organization name field from OrgBook

  • file attachment form component

• Tech Docs (documentation source published through developer.gov.bc.ca)

• Administrative functions for the CHEFS service

  • a list of users

  • a list of forms

  • Basic usage metrics displaying counts of users by identity provider, counts of forms, and counts of submissions

  • Function to reinstate ownership of a form if abandoned or orphaned

  • Function to restore deleted forms

Capabilities available as a pilot

• Integrating system messages between CHEFS and Line-Of-Business applications (Event Stream):

  • Example Use Case:

    • Health staff use the Service to add info about new primary care facilities in real-time so that this data can be made available immediately in a form's drop down field.

    • Submitters don't have to wait to see those updates.

•  

Capabilities working towards a proof of concept

• Management of User Roles on Forms (Team Manager)

  • Example Use Case:

    Long Term and Primary Care programs have #'s of forms managed by their team.

    (Roles include: Designers, Reviewers, and Approvers)

    • Current State: If a team member changes, the permissions for each form must be updated individually

    • Outcome: All forms managed by a single group can be updated with one update

• Identifying the forms a program depends on for service delivery (Multitenancy)

  • Example Use Case:

    Health team has a group of forms related to the Primary Care program

    • Current State: Each form is separately integrated with their LOB system. A list of forms used to deliver the primary care program is not readily available.

    • Outcome: Business Owners will know what forms support their primary care program. This allows for simpler integration and supports the program's total cost of ownership calculations.

•  

Capabilities being discovered

• Using AI tools to help people design forms

  • Example Use Case:

    CHEFS users ask "How do I design a progress bar?"

    • Current State: The CHEFS Team helps each customer to find and use the documentation.

    • Outcome: Create an AI Tool which can easily explain how to build forms with CHEFS.

•  

Problems being explored

• Connecting services into automated processes (Workflow)

  • Example Use Case:

    ECON uses a group of CHEFS forms for their grant program.

    • Current State: Linking forms into a single process currently requires that each business area make their a custom app.

    • Outcome: A common workflow component exists that can connect multiple forms into a connected service.

•  

Existing capabilities being refined

• Map component for form design

• Form authentication options (BC Services Card and Person Credential)

• Form settings to support feature flagging

• Form submission data management database infrastructure upgrade

• DevOps process refinements for support of user acceptance testing

• Form design usability enhancements

• Increasing the topics covered in Techdocs

• Expanding automated testing coverage and increasing our code maintainability scores

•