What's up with the Products?

Name	Status	Notes
IEC	Prod	Configuration files Deployed, Referential data now deployed yet. CRM admin are working on it. So, not in use yet. Business is working on Training and communications of new product. Regions have been using excel to track project engagements as the existing system has been unusable due to errors/bugs preventing closing project. Team has fixed the minimum required to get ACD online to allow users to update project status in prep for data migration. Can we provide a "train de trainer" session? Allen is on long vacation: need to contact Roslyn to plan migration dates. Roslyn is collecting Excel Spreadsheets from Regions over the next 2 weeks. If no reply their info will not be worked on. (Roslyn's words not ours). She has reviewed and mapped our Pacific so far. Migration: Open files in ACD, old system, not excel. Was busted until we fixed it recently. There would be projects that potentially we need to migrate PNR – 66 BC – 55 QC – 84 ON – 68 TOTAL: 273
OPP	Prod	Business is working on training all regions. Pacific is using app Ontario is using app Quebec is using app Atlantic is in progress, Jacob is assisting Arctic is MIA. Either understaffed or because tracking is delayed due to hunting season. Onboarding being developed by Jacob for 15-20 Program officers that require training with an intended end date of Oct 2019. Jacob is going to ask the CoP what they think about doing a retro with the regions.
Comms Internal	Prod	Pilot In production. Waiting for call letter to go out, and further feedback from users. Comms staff have reviewed. No cut-off date selected yet, however an Oct call letter is likely to be the date used. Waiting for confirmation.
Comms Anon.	Prod	Pilot In production. Waiting for call letter to go out, and further feedback from users. Comms staff have reviewed. No cut-off date selected yet, however an Oct call letter is likely to be the date used. Waiting for confirmation.
MDM	Elab.	Workshops with TDG/TSIS and MYTOA have started. Have shared the repo code for one of our products which is .NET custom, and connects to CRM (i.e. Comms Anon.) through Dynamics endpoint as working example of kind of integration work required by MYTOA. Have initial common data requirements from Ken (MYTOA) based on MYTOA stakeholder model. Strong potential of using message queues. Ken is getting licensing for a Solace instance that TC has procured. We would still develop the API for integration with Solace though.
Dynamics 365	Elab	We have the licenses from Dell to access the TC 365 online instance. Migration is proceeding and we are creating sandboxes to test the migrated solutions from GCCase, and working with the NWAR people who share the same instance.