Salesforce Announcement Templates

Communication Type (Email, Confluence, System Notification)

Message

Send by

Communication Type (Email, Confluence, System Notification)

Message

Send by

Outage for Deployment

Please be advised that EWMS Maximo system is undergoing a release this weekend for Transportation Services. During this time the system will NOT be available for all users. Kindly request all to sign off from your EWMS Maximo application at end of business/ by 4:30 P.M tomorrow [DATE].

 

System Unavailable: [TIME] [INSERT DATE] to [TIME] [DATE].

Action Required: Please Sign Out from EWMS Maximo application by [TIME] & [DATE].

Release Coordinator from EWMS@toronto.ca account

Communication- Release Tasks & Responsibilities- CM000XXXXX - EWMS Maximo

Kindly be advised that the change ticket CM000XXXXX is ready for rollout [TIME] [INSERT DATE] to [TIME] [DATE]. Following are the tasks and respective team members executing the change. All of the members will be contacted through their provided number IF & WHEN there’s a need. I will be available to address any issues @437-339-3045 during the release.

 Please use this email chain ONLY to update all of their roles & responsibilities of their respective tasks/issues during the release period. There’s WEBEX SPACE for all enquires/discussions and all relevant participants have been added.

WEBEX SPACES: Tech Only-CM000XXXXX-EWMS Maximo

                            Validation & Business LEADS ONLY- EWMS Maximo

ROLES & RESPOSIBILITY

 

VALIDATION

A Webex meeting has been scheduled for [TIME] [INSERT DATE] and the required participants are invited. Below validation will take place simultaneously. EMA participants may leave as their steps are completed.

BACKOUT (IF NEEDED)

SIGN-OFF

The below members have been informed about their availability between [TIME] [INSERT DATE] for “Go/No- sign-off from the recommendation by the validation team. A webspace has been created for all happenings for validation and decisions. An email sign off is a must & on unavailability they will be contacted on the provided contact information.

 

Thanks Much,

EWMS Support

Release Coordinator from EWMS@toronto.ca account

Release Status Update with recommendation

Release Status: All TS EWMS Maximo related deployment is completed. Validations has been completed.

 Summarizing the validation outcomes from leads.

Thanks

EWMS Support

 

Post Go Live- Stabilization Daily Touch Points

Please be advice that as part of EWMS Maximo Team’s Client onboarding process- The sustainment team will be focusing on Transportation Maximo users for a 2-week stabilization period followed by the Go-Live date of [TIME] [INSERT DATE] .

 Who:

  • Core EWMS sustainment team

  • Client Division Maximo admins

 What Happens:

  • Discuss about any criticality faced post Go-Live.

  • Address all concerns through HPSM service requests.

  

Thanks & Warm regards,

Preethi.

Release Coordinator from EWMS@toronto.ca account

Welcome Onboard - Transportation Services EWMS Maximo Users

EWMS Maximo Users,

The EWMS Maximo sustainment team is very excited to share that the Transportation Services release to production has been deployed successfully & we welcome our most valuable users. We are here to provide the best of support for all.

Purpose

To elaborate on

  • How the EWMS Maximo users will be supported

  • Different ways to reach the EWMS Maximo support team

 

When

The Transportation Services clients GO-LIVE with EWMS Maximo starting  30th October, 2022.

Production EWMS Maximo Link: https://insideto-ewms.toronto.ca/maximo

Who

Below is the list of your divisional level technical support for point of contact

How

The EWMS (Maximo) Product TechWeb page contains information related to the EWMS Maximo application, FAQs, Admins etc.

EWMS Maximo: TECHweb (toronto.ca)

 There are various ways to submit a EWMS Maximo service requests

  • Send in your request directly to your divisional EWMS Maximo admins via email. After reviewing your request, the EWMS Maximo admins submits HPSM service request on your behalf.

OR

HP Service Manager (toronto.ca)

Any other Non-Service requests EWMS information that’s not available on TechWeb / through Divisional Admin’s (Note: No Service request ONLY Information) please email as below.

  • For all Non-Service requests and/or Maximo application knowledge questions, email EWMS@toronto.ca

TS EWMS Admins can

To understand the roles of the Division Admins' and how they can further assist you, please visit Roles - EWMS Maximo: TECHweb (toronto.ca) for more information.

Points to remember

  • The Maximo login is same as your City’s Login.

  • There is no password reset for Maximo as the application uses City’s Username and password.

  • The listed items can be resolved by your divisional EWMS Admins.

In a nutshell

 

Warm Regards,

EWMS MAXIMO- Support.

Release Coordinator from EWMS@toronto.ca account

EWMS Maximo Sustainment-[MONTH] Sprint Planning

Good Morning All,

Pre-Booking For [DATE].

Purpose: This meeting is for the EWMS Maximo Sustainment team November Sprint planning. In this space we will discuss to prioritize the list of items that has been reported as part of service requests, enhancements and other business requirements.

 Agenda:

  • Meeting is scheduled for 2 hours- The business can drop off once the plan has been solidified.

  • The Core team will use the rest of the time to discuss.

  • [SCRUM MASTER] to give a 5-min walkthrough of the sprint process to the business audience- Joining as NEW.

  • Step by step of request walkthrough to comment and prioritize and choose November tasks for delivery.

  • Acceptance and sign-off

  • Floor open to core team for discussion.

 

Pre-Requisite for the EWMS CORE TEAM:

  • The roadmap Epics / User stories to be picked up from the workplan on the basis of priority ([PRODUCT OWNER).

  • All of the items (epics & User stories) ready for planning session in Jira ([SCRUM MASTER]).

  • All of the team please make sure your if any tasks to be filled into Jira prior to this planning.

 Kindly reach out to me if any assistance is required.

 Warm Regards & Thank You,

[SCRUM MASTER].

Release Coordinator from [SCRUM MASTER] account

EWMS Maximo Sustainment-[MONTH] Sprint Review & completion

Good morning,

This meeting time to review our Stories for completion towards “DOD” Definition of Done. Once it has been accepted by Product Owner/s, Application Manager and Business Leads the story and relevant epic can be moved completed/done in Jira.

 [MONTH] Sprint Board: Sprint Planning 2022 - Agile Board - Jira (atlassian.net)

 

Timeline:

  • Solid waste related tasks be discussed - this should help us cover all SWMS tasks in 30 mins).

  • Transportation related tasks be discussed - this should help us cover all TS tasks in 30 mins).

  • Followed by EWMS enhancements

  • Finally project related tasks and other.

What happens:

  1. We will iterate one story or task at a time.

  2. Followed by which the story or task owner (Scrum Team) may walk through how the story is achieved to be completed.

  3. The business will vote on acceptance.

  4. Items incomplete will go back into the Project backlog and relevantly brought into sprint backlog as per the project need.

 EWMS CORE TEAM

  • Please be ready to present your story or task as a 3mins walkthrough if applicable.

  • Please update as much of information into all of your owned tasks. And update the status.

 

Thanks,

[SCRUM MASTER].

Release Coordinator from [SCRUM MASTER] account

EWMS Maximo Sustainment-[MONTH] Daily Scrum Meeting

Good morning All,

As discussed during our Sprint session, kindly this will be the Scrum meeting.

  • Please connect on time. This is STRICTYLY 20 minutes meeting. It’s a round table pattern.

  • 3 topics to cover: What has been completed yesterday, what to planned for today, Impediments.

  • We will use SPRINT BOARD on JIRA, so we could comment on tasks and APPLAUD for completions!!!!

 And if anyone needs a training walkthrough of the scrum process, happy to assist. Kindly reach out to me.

 Warm Regards,

[SCRUM MASTER].

Release Coordinator from [SCRUM MASTER] account