Download No-Cost Raptor Software Section 1- RAPTOR software is a modeling software program for: (tells you how many failures to expect), (tells you how much uptime to expect), and (tells you about maintenance down time and times between maintenance demands) A RAM model tells you numbers for how your system operates: 1. Yes, I know you’re an expert about things such as pumps, compressors, furnaces, heat exchangers, and vessels!

Jan 23, 2018 - FREE 30 Day Trial Please complete the. Reliability Software. Powerful simulation tools for the engineer. Root Cause Analysis. Jun 4, 2013 - Chapter 2 A Basic Reliability Block Diagram. Phased Elements in the Simulation View. This workbook concentrates on the use of the Raptor software. Using these databases to find similar equipment to their application. Subsystems: engine, electronics, fuel, cooling, transfer-drive, brakes,.

You’ve also got information about their ages to failure and times for repairs. You can also organize the data into a statistical format for use in a RAM model to forecast how well things will perform in the future. It’s important to make your data speak for future events in building a model for new process and equipment.

We need the facts. Other web pages at tell you how to reduce these facts into the few details you need for the RAM model. Yes, I know you have great engineers who fit the system together with expertise about how the blocks are conveniently arranged for a production process. These same “fathers” or “mothers” of the process often will look you in the eye and deny the deteriorating effects of time and loads that cause entropy changes resulting in failures of “their systems—think of their children”. Our provincial outlook makes it difficult to admit the facts about how the creations we conceived will fail. All systems fail—the key is when, where, and how often.

All systems require maintenance. We can’t repeal the natural laws of entropy changes. This means we must account for the failures and the effects of the failures as the model reflects real-life conditions. Yes, I know you have experts in the process and how the system should perform on a steady-state basis. Unfortunately we design processes and equipment for steady-state conditions.

However, we operate the systems in a dynamic mode. What we design and how we operate them often incurs problems which we need to predict. Systems deteriorate and systems fail so use the facts from your records to gain details for your models. What you rarely know, on a factual basis, is how the installed system will really function for number of failures, availability, and maintenance demands. The bottom line of these numbers must be reflected into time and money. Monte Carlo RAM models allow you to compute the cost of unreliability () for a business perspective.

They are helpful in searching for cost effective alternatives for life cycle cost considerations. Few engineers can support the ideas in items 1-4 with engineering calculations. They often resort to opinions--not facts. For business results we need calculated facts before we build so we can convert the facts into $ statements. We must make business decisions from the technical details.

We need more operating facts summarized into numbers and less opinions devoid of numbers! We need operational details before we commit to bricks and mortar in a plant site. We need the facts to match the economics for the plant or process. We need these calculated facts from the model on one side of one sheet of paper. We need a practical representation of our operating plans into a computer simulation model so we can watch it run under simulated conditions.

RAPTOR helps work out the details using a Monte Carlo model (allows randomness in how the equipment operates before it fails and it also allows randomness in how long it takes to repair equipment) so we can visualize what’s happening to our overall system and components in the system. Data for RAPTOR models should come from your own maintenance data systems. Are available to represent life/death of equipment.

Other data sources are available in the on this website with data sources marked by a dagger symbol, †. RAPTOR is useful for engineers for converting technical details into money for life cycle cost considerations. It does not require statisticians to build the model or run the model. It lets you perform “What If?” exercises to arrive at the best tradeoffs for the system.

Best of all, the system produces numbers by simulation using your facts—not opinions. You can learn what is going wrong and where you can find some advantageous over your competitor by building the plant and operating it as a computer model before you install the equipment. Rearrangement of plants and processes by cutting torch is an expensive process compared to building a simple RAM model. Remember the techie details are not the primary important issue in most models— the money is what’s important; and time/money is what the business must consider—of course we use the technical details to get to the money! You can download some technical papers (as PDF files) showing RAPTOR models and life cycle costs from this site—just follow the hyperlinks below. Three papers listed below show how RAPTOR has been used for making decisions using the factual details from the field of and to arrive at the lowest long term cost of ownership (this is concept important to the stockholders view and requires that engineers must think like MBA’s as they act like engineers ): 1. Other are available for download as PDF files or you can go to the short list at the bottom of the.