14.03.2014 Views

Quality and Reliability Methods - SAS

Quality and Reliability Methods - SAS

Quality and Reliability Methods - SAS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

264 Recurrence Analysis Chapter 15<br />

Examples<br />

Cost is a column that must contain one of the following values:<br />

• a 1, indicating that an event has occurred (a unit failed or was repaired, replaced, or adjusted). When<br />

indicators (1s) are specified, the MCF is the mean cumulative count of events per unit as a function of<br />

age.<br />

• a cost for the event (the cost of the repair, replacement, or adjustment). When costs are specified, the<br />

MCF is a mean cumulative cost per unit as a function of age.<br />

• a zero, indicating that the unit went out-of-service, or is no longer being studied. All units (each System<br />

ID) must have one row with a zero for this column, with the Y, Age, Event Timestamp column<br />

containing the final observed age. If each unit does not have exactly one last observed age in the table<br />

(where the Cost column cell is zero), then an error message appears.<br />

Note: Cost indicators for Recurrence Analysis are the reverse of censor indicators seen in Life<br />

Distribution or Survival Analysis. For the cost variable, the value of 1 indicates an event, such as repair; the<br />

value of 0 indicates that the unit is no longer in service. For the censor variable, the value of 1 indicates<br />

censored values, <strong>and</strong> the value of 0 indicates the event or failure of the unit (non-censored value).<br />

Grouping produces separate MCF estimates for the different groups that are identified by this column.<br />

Cause specifies multiple failure modes.<br />

Timestamp at Start specifies the column with the origin timestamp. If you have starting times as event<br />

records, select the First Event is Start Timestamp option instead. JMP calculates age by subtracting the<br />

values in this column.<br />

Timestamp at End specifies the column with the end-of-service timestamp. If end times are given for all<br />

units, specify that column here. If end times are not given for all units, specify the Default End Timestamp<br />

option instead. But if you have a record in which Cost is equal to zero, JMP uses that record as the end<br />

timestamp <strong>and</strong> you do not need to specify this role.<br />

Age Scaling specifies the time units for modeling. For example, if your timestamps are coded in seconds,<br />

you can change them to hours.<br />

Examples<br />

Valve Seat Repairs Example<br />

A typical unit might be a system, such as a component of an engine or appliance. For example, consider the<br />

sample data table Engine Valve Seat.jmp, which records valve seat replacements in locomotive engines. See<br />

Meeker <strong>and</strong> Escobar (1998, p. 395) <strong>and</strong> Nelson (2003). A partial listing of this data is shown in Figure 15.2.<br />

The EngineID column identifies a specific locomotive unit. Age is time in days from beginning of service to<br />

replacement of the engine valve seat. Note that an engine can have multiple rows with its age at each<br />

replacement <strong>and</strong> its cost, corresponding to multiple repairs. Here, Cost=0 indicates the last observed age of<br />

a locomotive.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!