Reliability Failure Analysis Request Form The FAR (Failure Analysis Request) is designed to verify a product problem and determine corrective action through the evaluation of a small quantity. The process begins with the customer contacting the Area Sales Office or the Customer Return Services (CRS) group at (321)724-7400 or [email protected]. The customer will be requested to fill out the FAR form completely in order for the factory to understand the problem experienced by the customer and aide the analysts in their efforts to determine the root cause of the failure and corrective action. The CRS group will then assign a tracking number and give instructions as to where to ship the parts along with the completed FAR form. Failure Analysis Request (FAR) FAR#:

FAR Requestor Customer Distributor Intersil Sales or Sales Representative Customer Name: Distributor Name: will be the main contact person for the FAR. Requestor Name: Contact Name: Contact Name: (First & Last Name) (First & Last Name) (First & Last Name) Street Address: Street Address: Street Address: City: City: City: State: State: State: Country: Country: Country: Postal (Zip): Postal (Zip): Postal (Zip): Phone# Phone#: Phone#: Email: Email: Email:

Customer Type: 1=Standard 2=TS16949 (Signed Automotive TS16949 Agreement Only). Customer Location: Division if multiple locations are located in the same city, else city name. Customer Project Name & Project name assigned by customer and Application Type Application: (Example: L33 / Laptop Computer) End Customer Name: End user/Customer name Region: 1=China 4=Korea 7=Taiwan 2=Europe 5=North America 3=Japan 6=SE Asia Intersil Part Number: Full Part number as on Sales Order Customer Reference#: SCAR#, Reference#, Etc. Field Apps Engineer (FAE) FAE Email address email: Type of Issue: 1=Administrative (wrong parts, wrong qty, labels, packing, shipping damage, etc.). Supply photos & details on separate attachment. 2=Electrical (Parametric or functional failure) 3=Visual/Mechanical (Bent leads, solderability, chipouts, visual defects, etc). Supply photos & details on separate attachment. Issue Detected at: 1=Incoming ICT (Unit level test at contractor/customer location) 2=Board (Fails on a board at contractor or customer location) 3=System (Fails in system beyond the board at contractor or customer location. Also, used for 0KM automotive failure.) 4=Field Failure (End user in field or application actual use) Approximate Hours of 1=0 hrs (failed during power up) Operations Before Failure: 2= >0 to 48 hours (worked initially then failed). * 3= >48 hours (latent issue)* *(Actual time can be placed in Problem Description Section) Test Temperature in Celsius : 25C is room temp. otherwise specify temperature Lot Quantity: Estimation of Lot, Batch, Project, etc. rates at the time the unit was identified. Used to estimate failure rates of the issue reported. Quantity Tested: Used to estimate failure rates Quantity Failed: Used to estimate failure rates Quantity Returned for Qty should be <10 Analysis: Trace Code: Trace Code branded on the units for lot traceability

FAR Form Rev 7 Device/System History: 1=Production Ramp-up 2=Production normally running without incident 3=Production running/chronic issues. 4=Experiment/Stress testing 5=Product/Application Changed 6=New Development Application

RMA Pending: (Yes or No) & Y/N: Qty: Lot size on hold that could require a RMA. Quantity Problem Description-Detailed description of the failure to include pins, voltages, measurements obtained versus expected: Is this a known or repeat Issue Determines if this is an issue previously seen or identified on a (Yes/No) previous analysis for this customer. Failures Verified (Yes/No) Identifies if failures were returned with or without verification to isolate the failure. ABA Performed (yes or No) ABA verification consists of removing a suspect device from the failing product and placing it on a known good product, along with placing a known good device on the failing product. If not performed on all units, then highlight in Verification Procedure. Describe Failure Verification Procedures Used:

Schematics, test conditions, Details of the customer application and test conditions are needed waveforms, measurements to evaluate beyond ATE production test. Customer to provide as etc. attached (Yes or No) much details as possible (i.e. schematics, test conditions, waveforms, measurements, photos, etc.) to aid in the evaluation.

Special Requirements for HS Video (TWxxxx) products: Please describe the failure feature in detail and list all processing that occurred prior to the failure. Attach any pictures or videos to show the symptom if possible (Use additional sheets as needed): Setup Conditions: (Circle or check all that apply) Register values: Default Yes___ No___ If No; please provide customer's register setting as separate file. Input source: Composite___ S-Video___ Component___ Digital RGB___ Digital YUV___ Describe test pattern: Title PIP OSD Scene Other: Describe ______Video Format: NTSC___ PAL___ SECAM___ Analog RGB Resolution ______Sync Type: DSS___ ACS___ DCS___ Digital RGB Resolution ______Format: 601___ 656___ 16 bit___ 18 bit___ 24bit___ Other ______Please check all multiple inputs and provide detailed timing if the input signal is non-standard format Output panel resolution ______Panel type: TTL___ LVDS___ TCONLESS___ Ambient operation temp: Room____ Temp (specify) ______What is supply voltage if not nominal supply voltages per data sheet? ______Application is a: Car Navigation System___ Backup display___ AV / DVR / Monitor___ Other ______Additional information:

FAR Form Rev 7