So I am super stuck with this question and don't even know where to start from. This is the info I have:
Start to Finish Number of People per Day roundtrip
Seattle to Bainbridge 5,847 passengers 14.4 miles
Seattle to Tacoma, WA 3,243 passengers 40.2 miles
Bainbridge to Tacoma, WA 746 passengers 42 miles
This whole system costs 20 million. I need to develop different prices for the roundtrip tickets in a way that will be fair and understaandable to everyone. If the costs go from 20- 22 million, the system should be felxible to adjust for that too. The hint is to use equation "y=mx+b". This is the only information that I am given. Can anyone please help me where to even start? My idea was that we should charge Tacoma,WA passengers the most money cause it's less people and longest miles, second we should charge Seatle-Tacoma,WA passengers and finally the least amount should be charged to Seattle-Bainbridge passengers because it's the least miles and most passengers. Can you guys help me formulate this in an excel and how to get a head start with this one. |
I would really aprreciate the help,
Thanks,
Nika
Consider charging all passengers a specific amount per mile. The more you charge per mile, the more revenue you will generate on a daily basis.
At a minimum, the mileage rate should be set to generate enough money to cover the daily operating costs and create a maintenance reserve.
If you increase the mileage rate beyond this, you will also generate a cash stream that you can use to retire 20 million investment. The greater the rate the quicker the payback!
Related
I hope everyone's healthy and happy and enjoying the sun. (if in the Southern Hemisphere)
Would somebody mind having a quick check over so the below to know if I'm applying the correct methodology for required application
The Question;
I've decried to put all our garden sprinkler settings into excel to help calculate usage, costs while trying to optimise watering settings.
The general formula I am using is; (I've included a image for an example)
Cost=(R/1000)*L
L=(Flow*T)*Nodes
T=Min*D
D=ROUNDDOWN((End-Start+1)/Interval,0)
Where;
R = Cost Per 1KL
L = Total Litres Used
T = Total Run Time Cost per
1 Kilolitres= 2.99
Flow = 1.6 (Flow Rate Per/Min of 1x 90° Sprinkler Head)
Nodes = Amount of Sprinkler Heads
Min = Watering Run Time in Minutes
Start = Watering Start Date
End = Watering End Date
Interval = Watering Interval Day
Thats the method of calculating the costs. I'd love to hear anyone's thoughts and please do let me know if I've missed anything.
Any feedback would be greatly appreciated and many thanks in advance. :)
P.S; if anyone knows how to calculate the usage and costs for running drip line irrigation, I'd love to hear it. :) (The Drip line is about 153 meters in length with hole spacing every 300mm apart. It's 2.2 l/hr Flow. I haven't been able to think of how to calculate this)
For costing example; (sorry for the image, I didn't know if I could upload a sheet)
OP
https://www.mrexcel.com/board/threads/equation-formula-review-proof-for-garden-watering.1193183/
Microsoft secure score API provides score for Office 365 configurations. It provides list of best practices to secure O365 account. If we fix the mentioned issue and when we retrieve the secure score results again, we are getting same old result. As per Microsoft documentation, secure score should be updated daily but it is not happening. Any idea about its refresh frequency?
https://learn.microsoft.com/en-us/graph/api/resources/securescores
The official document explains it like this:
The score is calculated once per day (around 1:00 AM PST). If you
make a change to a measured action, the score will automatically
update the next day. It takes up to 48 hours for a change to be
reflected in your score.
According to the documentation, the score should be calculated once a day, starting at about 1:00 AM Pacific time, but it will take several hours to run. There are also instances where the job fails and we need to restart it so this might be why you don't see it updated at the exact same time every day.
Moreover, it may take up to 48 hours to refresh, so I suggest you wait until 48 hours to see if it refreshes.
The graph shows cpu's max > 96%, but cpu's avg < 10%
How can this be the case? (I mean, shouldn't cpu's avg > 40, or at least >30?)
Not really, I estimated some of the values from the Graph, and put them in a spreadsheet and calculated a 5 Min Average, as well as calculated the Max CPU and the Average of the 5 Min Average. Below is what it looks like. When you are doing an Average over a time, it smooths out all the peaks and lows.
Max 5 Min Avg
85
40
20
5
25 35
40 26
5 19
10 17
99 35.8
Max Average
99 26.56
If it is continually at high CPU, then your overall average will start growing.
However that average does look rather low on your graph, but you aren't showing the Min CPU either, so it may be short burst where it is high, but more often low CPU usage, you should graph that as well.
Are you trying to configure alerts or scaling? Then you should be looking at the average over a small period e.g. 5 minutes, and if that exceeds a threshold (usually 75-80%) then you send the alert and or scale out.
I asked Microsoft Azure support about this. The answer I received was not great and essentially amounts to "Yes, it does that." They suggested only using the average statistic since (as we've noticed) "max" doesn't work. This is due to the way data gets aggregated internally. The Microsoft Product engineering team has a request (ID: 9900425) in their large list to get this fixed, so it may happen someday.
I did not find any documentation on how that aggregation works, nor would Microsoft provide any.
Existing somewhat useful docs:
Data sources: https://learn.microsoft.com/en-us/azure/azure-monitor/agents/data-sources#azure-resources
Metrics and data collection: https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/data-platform-metrics#data-collection
I am testing anomaly detector on metrics of count of specific event per hour for last 90 days. For some reason I always get spikes (isPositive) only, but never drops, while I'm mostly interested to detect drops.
Data has weekly seasonality (expected drops on weekends) and definitely has abnormal drops mid week unusual for this day of week.
I also tried to play with specific hours to take them to extremely low for this time and week day. I tried different values for sensitivity (between 90 and 20).
On the positive side I get too many spikes, which create a lot of noise, while low sensitivity value didn't help to get rid of them.
Below is a link to request JSON.
Request JSON
You can try to set the maxRatio to 0.01, it should be what you expect.
Currently the sensitivity control is not good enough for low value. But we will rollout a new version in next week to improve it.
And you can also leverage https://aka.ms/addemo, and use a CSV to have more test.
I would like to use stripe to bill per GB of data used in an application. Here is an example of an invoice:
Usage: 2.38GB
Rate: $0.20/GB
Total: $0.46
However, it seems like Stripe only allows integer quantity, so how would the above be done? If I were to bill per MB, then I'd have the following:
Usage: 2380MB
Rate: $0.0002
Total: $0.46
However, the lowest rate that I could add (at least from what it looked like in the dashboard) was $0.01.
So, what would be the best way to accomplish the above (other than round to the nearest GB -- which looks a bit fishy to an end user, imho).
Stripe cannot support charging less than the minimum unit for a currency (because you can't charge a customer less than that, for example if they only used 1 unit).
You could set your "Unit" to be the smallest amount of data that would total to one cent, so that you are rounding to the smallest amount possible. In this case, $0.20/GB = $0.0002/MB = $0.01/50MB, 1 cent per 50 MB. You would have to account for this when reporting usage to the API, by keeping track of their usage yourself and updating the API using action= set rather than increment[0].
While this is what you'd have to do behind the scenes, there's no reason you have to expose that to the user. You could still list your rate in units of MB, with a note saying that totals will be rounded to the nearest 50MB.
[0] https://stripe.com/docs/api/usage_records/create#usage_record_create-action