Breakdown report

Hi PM Guru's,
Need a report that takes list of equipments / FLs as input for a maintenance plant and shows the breakdown trend for a period of say 15 years and corresponding repair cost incurred during that year.
for example : i should see for a equipment the breakdowns for period between 1995-2010 and for every year the no of breakdown's and repair cost in that year spread for entire 15 years.
Thanks

I am unclear what you require is it a report for all maintenance carried out or just for breakdowns.
Breakdown information is held on the notification where the financial information on cost of repairs and regular maintenance is on the order.
For breakdown analysis go to the PM Information system MCI7 transaction
For cost analysis go to the PM information system MCI8 transaction and search by Functional location or Equipment with month and year ranges. You have the option to switch the drill down to monthly once the report is displayed.
hope this helps
Jim

Similar Messages

  • Weekly breakdown report

    Hello every one,
    In my project my client is asking for weekly breakdown report. When i m running mci7 report that report is monthly. When i change cofiguration for Information structure as date wise. System is not calculating all the reports. Is there any other way to get the breakdown reports on weekly basis apart from PMIS.
    Regards
    Abhishek

    Hi,
    Only monthly update period is supported for this structure - see note [80311|https://service.sap.com/sap/support/notes/80311]:
    Check the Customizing settings with Transaction OMOS.
    The update period for the information structure S070 must be 'Month'.Changing the update period is not allowed.
    -Paul

  • AV Scripts, Free form docs, Breakdown reports and more...

    Hi there,
    We've posted an update to Adobe Story that includes exciting features like AV Scripts, Free form documents, and Breakdown reports among other things.
    Check out the latest release notes to know more.
    - Adobe Story team

    This is a very very nice update, especially all the breakdown reports that I was missing badly.

  • Breakdown report / Analysis - MCI7

    Hello,
    Can someone explain to me how transaction MCI7 work and how to understand the results?
    The thing is i do not get any data : in the order , besides, having "breakdown" field selected  and "malfunction start/end" filled , is there any other pre-requisites?
    Thanks,
    Pete

    Hi,
    The start up date in the equipment and fun location is the reference for all your break down analysis.
    Once you maintain this and create maintenance orders and notifications then info is passes to the respective structures.
    This all calculations are purely based on time. From the start up date system considers that the equipment has started performing considers that 24hrs ran if there is no breakdown order or notification is created against the same.
    2 maintenance orders are required if you want to see the MTTR and MTBF.
    Regards,
    N.nagaraju

  • Cost Breakdown Report for Date Range

    Hi Guys,
    i have 6 payrolls running and all of them while running for this report is working fine but for specified payroll it's not working the strange thing that it's working On TEST and not working in Production, can any one of you tell me about the prerquezt for solving or tracking this issue.
    BestRegards,

    but for specified payroll it's not working
    ==========================
    What is not working can you little specific.
    Thanks

  • Cost Breakdown Report Runs too Longs

    Hi All
    When I run Costing Reports its takes about 6-7 hours , last month the reports was working fine without any problem takes 3-5 min at most .
    I check pay_action_parameters and everything is fine , Reports Not Customized its by oracle .
    Note : i Already open SR with Oracle , but Want to see if some one have the same problem
    Hussein Sawwan : did you see this problem before !!!! Thank you All
    Br
    Osama

    Yes I did , For Hr , And For ALL
    But the Same , Actually i start thinking its bug i faced this issue on another customer site but On Gl schema with posting Reports After investigation i discover its Oracle Bug on Indexes And I applied patch for this issue now its solved .
    BR
    Osama

  • Breakdown analysis report MCI7

    Dear Experts,
    I created a break down notification for an equipment installed under a functional location and completed the notification after entering the breakdown hours with breakdown indicator checked.  Now if i run the MCI7 report with the functional location of the equipment, it does not give a break down analysis. Is it the way it usually responds or there are some additional settings we need to do?
    Please let me know
    Thanks,
    Boby

    Please ensure that the 'Startup date' field in the Equipment Master (Header tab) is filled. When there is only one Breakdown notification on a particular equipment and the 'startup date' is not filled, you will not get MCI7 report, because the first notification will be consumed as the 'startup date'. As soon as you fill this field, the MCI7 report starts, even if this only notification is created/completed before filling the field.
    Further you may go through the thread below:
    [MCI7|Re: Breakdown reports]
    Regards
    Jogeswara Rao

  • Basis in computing for breakdown duration

    Hi All,
    Good afternoon. I would just like to ask as to what is the basis in computing the breakdown duration generated upon completing a breakdown report? Is it standard that it is computed based on 24hrs a day? If it is, is there a way to change it from 24 hrs to 8 hrs per day? Hope you could help me all. Thank you.
    Thanks and regards,
    Happy

    Hello,
    The system determines the MTTR and MTBR key figures on the basis of the individual history of a technical object. The MTTR key figure represents the arithmetic average of the downtimes for the object concerned. The MTBR key figure, however, represents the times in which the reference object was fully operational.
    To generate these key figures, this system draws on all the malfunction reports with breakdowns that were created since the start-up date of the reference object. For technical objects, for which the start-up date is not specified in the master record, the system uses the end date of the first malfunction report where the breakdown indicator was set as the start date for consideration. In this case, the first malfunction report is not taken into account in further calculations.
    In addition, the system only evaluates those malfunction reports for which the start and the end of the breakdown are specified. The evaluation using the start time and the length of the breakdown is not supported.
    The system uses the amount of breakdowns reported for a technical object to first determine the effective breakdowns. In doing this, it merges two reported breakdowns that overlap in time. The reference time for assigning the MTTR and MTBR key figures to a statistics period is the start of the effective breakdown. In the case of longer breakdowns, this can make it impossible to calculate the key figures for the subsequent periods.
    MTTR = Sum of effective downtimes / Total of effective breakdowns
    MTTR = Sum of effective time between / Total of effective breakdowns
    Reagrds,
    Rakesh

  • Email analysis overview report questions

    hi,
    please see the attached file.
    this is an email analysis overview report which shows strange results...:
    1. how can the open rate be bigger than 100% ? - the eloqua report guide defines this metrics as # unique opens/# emails delivered, am i missing something here ?
    2. something is strange also with the click to open rate - the email click through link breakdown & email open overview reports are attached to the workbook also, so you can see that the total unique clicks = 152, and the total unique opens = 244, so the click to open rate should be = 152/244 = 62.2%, not 45.85%, right ?
    thanks.

    my thoughts...
    The "Email clickthrough Link Breakdown" report is only unique per link, not per person. Someone can technically uniquely click on all of the links in the email, so a user could show up as a count for all links in the email if they clicked them on that report.
    The Click to open rate as calculated in your Email Analysis Overview is based on Unique clicks per user/per email, so the most a single user can have is 1.
    When running the Email Analysis Overview Report - you can add in your unique metrics in step 5, after you select the emails to report on. make sure you add them to the right hand column.

  • MCJB report

    Dear Sap gurus ,
    Whether anybody let me know about the <b>Boulded</b> figures, Here I am not able to understand  from where 60048.10  ( time between repairs came ),MTBR (15012.03) , these huge hours came . That is why Iam sending the copy below with BOULDED
    Equipment          Description of technical object                               
       Mean Time To Repair (H)  Time Between Repairs (H)  Mean Time Between Repairs (H)
      Period Breakdowns    Downtime (H)          MTTR (H)          MTBR (H)                                                                               
    BM01ACSA09         AUTO-CONER 60 SPD-09                                          
                         5.98                 <b>60,048.10</b>                      <b>15,012.03</b>
    08.2007         3           16.00              5.33         <b>19,617.22            </b>
    10.2007         1            7.90              7.90          <b>1,196.43            </b>                                                                               
    BM01ACSA09                                                                               
    4           23.90                   
    Thank you
    GMR

    hi maheshwer
    the key figure for breakdown will be calculated as follows
    Key Figures for Breakdown Statistics
    By using the breakdown statistics you can analyze the causes of a particular breakdown more closely. The focus in this case is on the distribution of duration of the various breakdowns or repairs, and on how these were caused. The aim of these analyses is to find out the cause behind a short or long breakdown period, or the period between two consecutive breakdowns. An indicator in the first screen of the notification indicates that a malfunction report or a maintenance request contains a machine breakdown.
    Key Figures for Machine Breakdowns
    We distinguish between the following:
    Number of machine breakdowns reported
    Number of actual machine breakdowns
    The reported breakdowns are important from a business point of view, whereas the actual breakdowns are of interest from a technical viewpoint.
    There are three cases which are important for the breakdown analysis. These are represented in the following diagram, which displays two reported breakdowns in each case.
    Three Cases for Breakdown Analysis
    Key Figures for Downtime
    The key figures for downtime comprise the following figures:
    Downtime entered/Time To Repair
    Mean Time to Repair
    The average duration of a machine breakdown, MTTR (Mean Time To Repair), is calculated from the individual history of a piece of equipment. This gives the following formula:
    The key figure MTTR is calculated in hours.
    First breakdown 10 hours
    Second breakdown 05 hours
    Number of breakdowns 02
    MTTR = 10 + 5 / 2 = 7.5 hours
    To calculate the key figure Mean Time To Repair, in the breakdown analysis (information structure S070) the effective breakdowns and the number of effective breakdowns are taken into account. In all other analyses (and the underlying information structures) the noted breakdown duration and the number of noted breakdowns are taken into account.
    Key Figures for Duration Between Machine Breakdowns
    The key figures for the duration between machine breakdowns comprise the following ratios:
    Time between Repair
    Mean Time between Repair
    The average duration between two machine breakdowns, MTBR for short (Average Time between Repair), is calculated from the individual history of the equipment. This gives the following formula:
    The key figure MTBR is calculated in hours.
    The following example shows how the MTBR is calculated:
    Acquisition date of pump A 01.01.94
    First breakdown 10.01.94
    Downtime 10 hours
    Second breakdown 20.01.94
    Downtime 5 hours
    Number of breakdowns 2
    MTBR = (19 * 24 - 10) / 2 or X + Y (hr) / 2
    = (456 - 10) / 2 or (216 + 240 - 10) / 2
    = 223 hours
    Example: Average Duration Between Two Machine Breakdowns (MTBR)
    When calculating the key figure Mean Time between Repair, only the start-up date can be taken into account if the indicator Start-up was set in the master data for equipment or functional locations. If the indicator was not set then the end date of the first malfunction message will be taken into account. In this case, the first malfunction message will not be used when calculating the key figure MTBR (refer to the following illustration).
    iam not able to paste the diagram, kindly look in the link below and select the <b>information system->plant maintenance information system->how the key figures are calulated->key figure for breakdown statistics</b>
    <b>http://help.sap.com/saphelp_46c/helpdata/en/b0/df293581dc1f79e10000009b38f889/frameset.htm</b>
    check whether you have given start up date in euipment master record ,or else the breakdown calculation will be calculated from go live period
    regards
    thyagarajan

  • Question about versioning (history) in the latest release

    Hallo,
    Some questions:
    1. Will versioning ever be integrated with locked pages, locked scene, colored pages, revision marks functionality etc, so that at a particular moment you can optionally augment the current versioning with the more traditional way of production revision cycles?
    2. If above will not be the case (or is never activated): what currently happens with scene numbers & manual breakdown info that is already added, but than the scene gets deleted.  Is all this info gone (& scenes renumbered).  Can we save a version to keep this info?  Please clarify.
    3. Regarding breakdown of elements: will there be a way that we can visualize breakdown sheets on screen.  It's much easier for me to look at it that way, e.g. the Scenechronize way (I guess I'm old).
    4. Regarding breakdown and making the script 'production ready', will there be a way to combine scenes that belong together and part scenes (that are not in the same shooting location but where the writer chose to combine the action in one scene, eg like telephone conversation etc).
    I guess all my questions boil down to this: will Story also aim to offer serious production breakdown features that could be used by production managers & assistant directors to prep for physical production, or will it mainly be a collaborative writing tool (even if it does allow you to transfer text into On Location shotlists and then eventually into your clips). 
    I guess there's a conceptual difference (at least when talking about narrative film with a lot of cast, locations, props etc): do you support mainly the writing effort and than transfer into a tool like Scenechronize once production starts - or do you go further? For  (corporate) interview type shoots this matters less.
    I would be interested to hear your views on the matter.
    Regards,
    Bavo

    Yes. Versioning will be integrated with locked pages, colored pages but we are not planning to lock scenes yet. We will also show asterix against changed lines in future updates.
    You can always explicitly save a version (file->save as) to mark a checkpoint draft. You can add your own comments while saving this draft so that you can find it later.
    We'd like to support production related features because we want to leverage script metadata for all it can be leveraged for. That said, "full fledged" is a loaded term. We will take small steps and enable workflows related to production as we go along. Dynamic breakdown reports, that can be viewed and edited in Story are on our roadmap.
    --Anubhav

  • No MTTR and MTBR in Table S070 for Query

    Dear All,
    I tried to create a Query using Table S070 to modify the Breakdown report a little.But i am unable to find the MTTR and MTBR fields as below in the Query for to select in the list.So How to get those fields or Which table i have to use for to obtain those fields??
    Regards
    M.Manojkumar

    You are getting the total  TTR and TBR values from the S070 LIS. When you divide these figures by the number of breakdowns (field SMSAUS) of then the result is MTTR and MTBR
    For formulae see this picture:
    Here One failure  is one Downtime. Add all these downtimes and divided by no. of downtimes for MTTR.
    And Operating Time (between failures) is the Uptime. Add all Uptimes and divide by no. of Uptimes for MTBR.
    Jogeswara Rao K

  • How exactly does the shotlist feature work?

    I have finished my script and would now like to create a shotlist. I have noticed in the film script mode, the possibility to add a SHOT. however when I do this it wants to change the formatting of the entire script. I am not sure what is going on here. Does anyone already know how this feature works?
    Any help would be greatly appreciated.
    cheers
    Angus

    > Bavo.
    >
    > Would supporting versioning be enough to handle your production
    > workflow issue? We can implement locked pages, locked scene, colored
    > pages, etc but I'm not sure if it’s a must have considering that folks
    > are freewheeling more than in the past.
    That might be the case but there are still plenty of 'traditional' workflows,
    so if you need to conform to their way of working you'll need it.
    For me it's a mix between freewheeling (can also end in a really big mess) and
    more controlled traditional way of doing things (usually when money/time
    situation is a little easier and depending on production company).
    So maybe a feature for 2.0?
    > Thanks for sharing the shotlist information:
    No thanks.
    > I've seen the vertical lines. they make the script really hard to read
    > and I also think it is really a paper based workflow more than a
    > digital workflow. However, have you seen a lot of editors use a
    > physical script marked up this way?
    Avid has the workflow, don't know how many really use it in that integrated
    way but I do know on long form projects the editor usually asks for the
    continuity notes.
    > Wouldn't it be better if this
    > information flowed through digitally with the files captured from
    > camera, at the time of logging at the end of the day's shoot?
    Yes in an ideal situation.
    However, how does it work when a tool like On Location is not available?
    In that case I still like the lined script metaphor...
    If it's too cluttered could you not implement a feature to optionally turn
    on/off the lines once you constructed the shot list?
    I'm also referring to prep when a director does a shot list before the
    shoot (not merely the lining traditionally done by the continuity supervisor).
    I also realize that the lining method only works when your script is more
    or less finished (there we go again)... So flexibility is the key :-).
    > The BBC uses horizontal cut lines instead of the vertical lines used by
    > scripty's. They serve the same purpose and these shots (demarcated by
    > cut lines) can be exported to create a shot list and camera cards for
    > each camera person.
    Nice if it works for them. 
    I've also seen this used where the wide shots were laid out at the bottom
    and the closer shots near the top and that was supposed to correspond to
    the emotional high points in the story.  Whatever works.
    > You can try exporting the shot list from Story using the production-
    > breakdown reports menu. Let us know how it works for you.
    Will test.

  • Plant Maintenance Feature / Module

    Does Apps have any module on Plant Maintenance covering or does Apps cover Plant maintenance including:
    a. breakdown reporting with reason and categorisation into recurring & nonrecurring
    b. preventive maintenance schedule
    Please revert back ASAP.
    Thanx
    Ganesh

    Dear All,
    Can anyone share some links or materials regarding the PM module.
    I have checked the help.sap reference. but since I dont have experience & practical knowledge regarding this module I am finding a bit difficult to follow. So please advice how to start with ?
    Materials with the basics structure & Process flow in PM  Or if someone can explain the PM process flow like the PR-LIV flow in MM it will be really very helpful.
    Also if you can provide details regarding the SDN forum i.e related to PM module where I can find PM materials & threads it will be highly appreciable.
    Expecting your valuable replys.
    Regards,

  • Saving a layout for a user

    Hello;
    I want to save a particular layout with some default values. Suppose if I am running a report MCI7, I want to have an equipment number say- 1000500 as a default everytime I run the Tcode MCI7.
    I know, I can create a variant & call the variant; but I want  to get the variant automatically (after running the Tcode MCI7) without choosing the variant. This applies in some industries where only breakdown reports on only 2-3 critical equipments are required, every month.
    Points assured.
    Regards
    Hemant

    Hello Philip;
    Thanks for your valuable input, it solved my problem.
    Thanks & Regards
    Hemant

Maybe you are looking for