1 / 17

“ELR 101”

“ELR 101”. What is an ELR ? . Engineering Liaison Request – a documented request to the engineering organization for an answer to an issue/problem encountered on the factory floor where the design could be a contributing factor.

nicola
Download Presentation

“ELR 101”

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. “ELR 101”

  2. What is an ELR ? • Engineering Liaison Request – a documented request to the engineering organization for an answer to an issue/problem encountered on the factory floor where the design could be a contributing factor. • An answered ELR has NO AUTHORITY to alter the existing released design definition, but it is a documented request for “help needed” to the Engineering team to investigate for possible solutions. • Controlling 787 Process is BPI-5350 (BPI-566 for legacy programs)

  3. When Initiating an ELR what should I do? • Review ELR 101 understanding when it appropriate to write an ELR and when a different request path should be taken. • Find an LE in the control station where the issue exists and coordinate prior to writing an ELR. Anyone in the LE Organization will point you in the right direction. Note: add LE name to the ELR form as indicated on slide 10 (Information needed from the requestor) • Use this Power Point Template and attach it to the ELR Form. Note: this is the presentation used by the ACAT team, any information you can provide in this presentation template will help (especially pictures) • Complete form and send all supporting documentation to the ELR group mailbox GRP 787 SC ELR. Note: save the ELR number for tracking purposes later.

  4. When to use an ELR • To correct minor errors in drafting or design as long as the incorporation point is not mandatory but at manufacturing discretion. Note: no planning action will be required. • Non-production-impact issues that do not affect type design and do not justify the cost of an engineering revision. • Allow for revision to the export control sensitivity value of PDD. • Provide clarification regarding engineering type design intent.

  5. When to use an ELR • To address incorrectly nulled part effectivities. • To address incorrectly orphaned instances of parts and assemblies. • To re-establish required connectivity to broken installation requirements model (IRM) linkages. • To prevent occurrence of any product non-conformance caused by an engineering design component within the build plan.

  6. When not to use an ELR • When issues are encountered on line units that are not yet in the factory (Initiate Problem Reports BPI-5416 or contact Prime DE and ME though GAD listing) • When issues encountered do not constrain the ability to complete jobs. Resolution may be via a PR and processed per BPI-5416 (e.g. fay seal surface was extracted improperly, surface of sealant is off the surface of the part). • Flow time will not support production schedule -If formal release per this process does not support short term critical units, use the emergent quick change (EQC) process in accordance with BPI-4849(authorized under BPI-5716). This process shall not be used to re-authorize an existing change. • IRMs beginning with the number "9"are for Test Installations only (flight test, static, fatigue, etc unique requirements). Please contact Test Engineering to address your concerns with the IRM. 

  7. When not to use an ELR • An open nonconformance record (NCR) exists, or should exist, on the same PDD. • When a known active, open, or both, engineering-charged NCR and related corrective action record (CAR) exists on the same PDD, continue processing those records in accordance with BPI-5515. If a nonconforming condition already exists on the product and work cannot be continued nor be held pending a design correction, initiate the nonconformance process in accordance with BPI-4843. • Note: When a nonconformance condition due to deficiency in design is anticipated, but an NCR does not yet exist, the nonconformance process is not appropriate. Instead, use this liaison change process, using BPI-5716to select the correct change authority. Use the concurrent change process in accordance with BPI-5214(as appropriate), to prevent the nonconformance condition.

  8. Information needed from the requestor What is being held up? Why should we make the change? Pin Number from GAD Investigator will complete Originator As it appears in outlook Instance Name Line Number where Problem was found LE that you coordinated with prior to writing the ELR Affected PDD # ME Lead Status of Planning V5 or other source PDM, Mapper If this form is not filled out completely your request will be returned. Detailed instructions for filling out form is within the form on sheets 3 and 4. Also note you can attach supporting information excel, PowerPoint etc by selecting the paperclip in the top right corner of the form. Describe the Problem and proposed solution if known Note: when the originator c/w someone that they put that person's name, phone number on the ELR (this will help speed up our investigation) ACAT will respond back with Dispo and Record all change below this line Note: May need to use sht 2 May add attachments to form

  9. Process Flow Map

  10. Priority 1

  11. Priority 2

  12. Priority 3

  13. Flow through LE

  14. References Helpful Links: • Blank ELR form http://forms.web.boeing.com/detail.cfm?fnum=D141013500 • View TELLS status http://liaison.ca.boeing.com/TELLS/tellssearch.asp • BPI http://policyplus.boeing.com/DownLoad.aspx?filename=bpi-5350.pdf • ELR Stored on Server \\nw\787Lib\SPLR-BSCDE-WKG\ELR's View TELLS status

  15. References Helpful Links: • LDAR information share and Factory Hot list location and process in work (future state controlled by ME) • BSC SharePoint for Engineering https://vtr2c.web.boeing.com/sites/BOEINGSCDE/default.aspx Contacts: Katherine Laufenberg (Manager) Matthew S Coleman Steven M Graham

  16. When to LDAR an ELR • When LCPT has requested they would like to work the request • When LCPT already has a change in-work that will satisfy the request • When the request requires a business case. • When the change/issue is so convoluted, that Liaison can not determine the Design Intent. • When the change involves more than one Partner and requires a CN

  17. When to LDAR an ELR • When the change is too large. This would have to be determined by the Lead. An example would be an ELR written on say 1 IRM, but after investigation, it was determined that the issue was much greater and affected multiple Reworks and involved cutting back multiple Instances and creating multiple Removals and so on. This may be considered a reason for LDARing. It would be a case by case decision. Another reason is a situation where the Partner did not follow the process and released IRMs that were not per the design intent. (ie...created an And On IRM to do Rework).

More Related