Requirements / Documentation for how to add Competent Authority Search

[mstanton1]

Process flows were created for Competent Authority Search. In those flows a user needed to obtain a form (same process as director search), complete and send that to BC Online administration, and then if approved the account would be granted access to the Competent Authority Search.

Can you document in more detail the work that takes place in the system so it can be reviewed by designers and we can identify any build effort. Some thoughts on questions / need for documentation are:

1. Where does a client obtain the current director search request form and what is the appropriate location for the competent authority request form?

   • Director Search is not an advertised product. Clients who learn about it will contact BC Registries (could be to our BC Registry staff, BC OnLine Help Desk, or any other help desk, or even email BCOL Admin directly) and forward the request to BCOL Admin.
   • BCOL Admin then sends the Director Search Request Form to the client.
   • If BCOL Admin will own the Competent Authority SI Request process, then they would administer the form.
   • BCOL Admin has a copy of their DS form in their processes but the actual official location of it is on the staff LAN where all forms are kept: R:\ARCS\Admin 100-499\Forms Mgmt 285\20 Forms Mgmt Active\Forms\REGISTRY Forms\20\COM forms\55COM\FORM 55 COM - Director Search Access Request.pdf o The SI form would be placed in it’s own LAN folder, which will be decided by the Digital Partnerships Team where exactly on the LAN they want to house it.

2. How does BC Online add access to director search currently (note the flow we reviewed in the system I was advised is deprecated. Rather than initiate a new account online, my understanding is that BCOL Admin raise a ticket with SBC IT Ops who triage the ticket and assign to the lab. Can you document the rules for this ticket (there are likely templates that IT Ops uses, and may be some template or process in Zenhub).

   • BCOL Admin has an email template they use to send the request to SBC IT Ops.

   • SBC IT Ops takes BCOL Admin’s email and using the info contained in that email, opens a Zenhub ticket on the Ops board. To log this ticket, they use a template as below to fill out: Add Director Search to a BCROS Account

     • [ ] Assign High Priority
     • [ ] Move to “Backlog” pipeline
     • [ ] Client’s BCROS account name and number
     • [ ] Message Teams Channel OPS Team with the title: “Director Search Access request: please look at ticket #X"
     • [ ] Dev: when ticket is ready for verification, send email to IT Ops stating ticket number and that work is completed Link to SBC issues logging process: https://docs.google.com/document/d/1kH00T0jWWC_u3P8WV3veevR1fmotULtR/edit

3. Who actions the Zenhub ticket for access to director search? We should look at who is currently trained on this process and also look into how many requests have come in for director search. This should provide insight into the volume for competent authority. Metrics can guide if we want to bypass this ticketing process and look into providing direct access for BC Online to add the product themselves.

   • The Ops Team, managed by Omid Zamani. Whoever is on ops pick it up and runs a script to add the DS to the account.
   • The Ops team and the BCOL Admin team are trained on this process.

[mstanton1]

@Apt766525 this is another ticket ready in the product backlog when you have capacity. Mags provided information that the flow we'd reviewed is no longer used, but wasn't removed from the system. I'm happy to chat this through if it's helpful:)

[Apt766525]

@mstanton1 Have updated the description with the findings.