These changes have been merged into foundation-2016. Marking as fixed.

commit da1ea5dee2be518f29d610a4fc692a4e49ff3dc8

We'll try and code-review these changes and then integrate them into 16.

Problem 4) Unresolved outages aren't accounted because ifregainedservice is null and isn't considered by the OVERLAPS function.

Solution) In query "outage_scope", instead of using the ifregainedservice, we always use a non null value: ifregainedservice is there's a value, report's "end_time" if ifregainedservice is null.

Instead of

Should be

Problem 3a) if an outage is still active and the "lost" timestamp is older than the start_date of the report, the report will account the outage's time since it's beginning instead of the beginning of the report.
Problem 3b) if an outage is resolved and the "regained" timestamp is newer then the end_date of the report, the report will account the outage's time until it was resolved, instead of the ending of the report.

Solution 3a)
Instead of using the field iflostservice in query "outages_scope", the GREATEST function should be used, in order to return the greatest of start_time,iflostservice.

Solution 3b)
Instead of using the field ifregainedservice in query "outages_scope", the LEAST function should be used, in order to return the least of end_time,ifregainedservice.
NOTE: end_time is a new internal parameter, used to specify the end_time of the report

Instead of

Should be

Problem 2) Outage percentage is calculated using the average of outage's time, when should be used the total time of the outage.

Solution)
Instead of:

This should be: