<?xml version="1.0"?>
<rss version="2.0">
<channel>
<title>Acme Forum - Forecast View - Feedback Report: Maintenance Cost versus Type - Messages</title>
<link>https://help.junoviewerweb.com/pages/topic28-feedback-report-maintenance-cost-versus-type.aspx</link>
<description>Acme Forum - Forecast View - Feedback Report: Maintenance Cost versus Type - Messages</description>
<language>en-us</language>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
<generator>Jitbit AspNetForum</generator>
<pubDate>Thu, 09 Jul 2015 15:11:52 GMT</pubDate>
<lastBuildDate>Thu, 09 Jul 2015 15:11:52 GMT</lastBuildDate>
<item>
<link>https://help.junoviewerweb.com/pages/topic28-feedback-report-maintenance-cost-versus-type.aspx</link>
<title>Message from Fritz Jooste</title>
<description><![CDATA[<span style="font-family:sans-serif">This feedback report extracts the maintenance data for the selected segment in the Forecast View, and shows a breakdown of the COST of maintenance actions versus the TYPE of maintenance action. Naturally this report can only be activated if your database holds well structured historical maintenance data. The report looks like this:</span><br/><br/><img src="https://help.junoviewerweb.com/images_help/Forecast_FB_MaintCostVType_1.PNG" border="0"><br/><br/><span style="font-family:sans-serif">The setup for this report is driven by the XML data that is stored for this report on the "tblReportSetups" table on the user database.</span><span style="font-family:sans-serif"> Except for advanced administrator users, this XML is best managed by Juno Services staff. The XML setup configuration is formatted as follows:</span><br/><br/><img src="https://help.junoviewerweb.com/images_help/Forecast_FB_MaintCostVType_2.PNG" border="0"><br/><br/><span style="font-family:sans-serif">The XML keys have the following meaning:</span><br/><br/><u>breakdownType:</u><span style="font-family:sans-serif"> Key for the breakdown type - required by the feedback report engine. Do not modify this value!</span><br/><u>yearsToGoBack:</u><span style="font-family:sans-serif">. Number of years to go back in time. Higher numbers mean a longer historical view on the data.</span><br/><u>minOverLapLengthMetre:</u><span style="font-family:sans-serif"> Minimum overlap that a maintenance action must have with the segment in order to be included in the query</span><br/><u>costGroupsToInclude</u><span style="font-family:sans-serif">: This element should contain one child element, each with name "group", for each maintenance cost group to be included in this report. To include all cost groups, leave this element without any child elements.</span><br/><br/><br/><u><span style="color:rgb(255, 0, 0)">Important Note</span>:</u> if your maintenance table does not have a "costGroup" column, then all maintenance actions will be included regardless of the cost groups specified in the setup]]></description>
<pubDate>Thu, 09 Jul 2015 15:11:52 GMT</pubDate>
</item>
</channel>
</rss>
