Page Comparison

Revalidation

• Awaiting to receive new/modified Designated body name, code and RO details from GMC on stage.

• Test new DBC by CURLing from STAGE-GREEN/BLUE

• NEW: Test new DBCs by

  • adding similar names to reference data

  • code (TCS DesignatedBodyMapper)

  • users in User Management

• The programme owner from TIS will be updated too, so needs a full sync from TIS to update ES.

Before 27th:

• Add the DBCs to TCS DesignatedBodyMapper

• Modify/Add to reference “DBC” data

• Add the new DBCs to parameter store to map to the Recommendation

• Add the new DBCs to TIS-GMC-Client service

• Add the new DBCs to tis-revalidation-connection service (probably parameter store like recommendations)

• ALSO: For Revalidation API calls to work, the admin needs to have the correct DBC assigned in usermanagement/profile service And the RO for that DBC needs to be correct (wherever that comes from).The programme owner from TIS will be updated too, so needs a full sync from TIS to update ES.in User Management).

w/c 27th:

• Modify names to reflect new organisation

  • Reference Data

  • Code (TCS DesignatedBodyMapper, …?)

“Later”:

Never?:

Legacy Revalidation

• Find the location where we need to accommodate the new DBC changes

• Can we use this as an opportunity to close down old reval? need to ask users

TIS

1. TIS-Reference: update reference.DBC , reference.LocalOffice , reference.trusttable

2. TIS-Profile: update auth.UserDesignatedBody table

3. TIS-TCS:

   1. update tcs.Programme , tcs.Post table

   2. update tcs.PersonOwner table by PersonOwnerRebuildJob in Sync service

   3. update class DesignatedBodyMapper

4. List the changes on TIS, UserManagement and Bulk upload and inform admin users.

User Management

Should be okay when db tables of reference and profile are updated.

Needs verification and investigation to see the DBCs reference elsewhere.

TSS

NDW

• Speak to the NDW Team about potential impact

  • Initial conversation with John Thompson on 17/02/23. A wider meeting with NDW Team taking place 20/02/2023.

  • Discussion on 20/02/2023 and 21/02/2023. Impact on NDW and Tableau users too great within the timescale. Agreed to attempt to delay the update to Programme.Owner and Post.Owner fields post 1st April through by only changing the DBCs in the reference table and mapping script. Also, the new Local Office names are not officially confirmed. Once the above TIS approach is confirmed will send comms to NDW and Tableau users/stakeholders.

• Coordinate with NDW of potential comms to regions and other downstream users of TIS data

ESR

Further investigation on how ESR communicate across the ?changes

Hicom Leave Manager

• Update TIS-Accent ETL to use or include the new Owner names

• Confirm with Hicom the impact on their ETL and Accent Leave Manager system changing DBCs/Owners would have and identify mitigating actions

  • 21/02/2023 email: Hicom are conducting their own impact assessment and communicate back once complete. To note, Hicom only use Programme.Owner

NDW-Tableau

• Identify scripts in the NDW which are or are a dependency for Tableau data sources which use DBC/Owner to extract relevant data

• Identify Tableau workbooks which use DBC/Owner to group, filter, etc

GMC - Educational Branch

• Met with Danial Smith, Jennifer Redman-Tootell and Andy Knapton at the GMC on 21/02/2023. No mitigation necessary for 2023 GMC NTS and no other pending impact from TIS. Agreed to share new organisation names and relating ODS codes when known.