Updating the Company Profile

Once there, you will find the Company Profile ready for your updates. 

Company Name

The Company Name will appear in a variety of locations, but most prominently you can find it in the upper right corner of each user's screen below their name.

Default Timezone

The timezone setting is used for all time-based configurations in Aimably.

We recommend selecting the local timezone of your corporate headquarters, or where the majority of the Aimably team is located. This timezone dictates the selected time for all regular notification emails and the default schedule appearance of any Work Schedules configured in Aimably Reduce. Keep in mind that any schedule can be customized to a local timezone as well.

Daily Alert Time

The Daily Alert and Daily Report emails are sent at the time specified here, in accordance with the Default Timezone setting.

Some notifications provided by Aimably Warn are dependent on AWS cost data retrieved from the previous day. As a result, it is important to select a time of day to receive these alerts when your team is most likely to be able to take action. Please note that AWS begins to aggregate its usage data around 1 am UTC, which means that teams should avoid selecting a local alert time that is before 1 am UTC.

Example: If you are located in New York City, 6 am local time is 1 am UTC. Therefore, a 5 am alert configuration would not be advised and a 9 am alert time would increase the likelihood of total data available from AWS.

Daily Report Time

Each day, Aimably Warn is configured to send a summary email detailing the costs of the previous day. This setting determines when these emails should be delivered to the team. The same caveats to AWS data aggregation apply to this email as well: AWS begins to aggregate its usage data around 1 am UTC, which means that teams should avoid selecting a local alert time that is before 1 am UTC.

It is important to select a daily cost email delivery time that will ensure you the most complete and recent data available. We recommend the following steps to determine your appropriate notification time:

 Convert 1 am UTC to your local time zone (e.g. 5 pm PST, 8 pm EST)

Add at least two hours to protect yourself from variations due to daylight savings and give the AWS billing logic enough time to aggregate your total usage

If the selected time is outside of your working hours, review your corporate behavior and determine whether it's more appropriate to delay delivery until the next working hour or if immediacy is preferred

For assistance in making this decision, the following table demonstrates which data would be reported depending on general timeframes in the North American workday.