TALOS MR TEM platform Lessons in diversity management and cost

Transcription

1 TALOS MR TEM platform Lessons in diversity management and cost Jamie Mc Cormack TALOS Technical Lead (System Architect) CT R&D Systems Group April 19, 2016

2 Agenda TEM Basics TALOS requirements architecture and design strategy a flexible platform rather than a fixed product How this was realized (focus, agility, cost effectivity, re-use, leverage) Conclusions 2

3 Introduction to mid-range TEM Key figures electron source condenser lens system specimen objective lens projector lens system fluorescent screen & cameras Vacuum 3 Vacuum: < 10-6 Pa HT: 200 kv ± 160mV (0.8 ppm) Drift < 5 Å/min (3.8M years/km) Noise (Acoustic) Vibrations / Pressure Stray fields (EMI) Temperature OL: 11 A ± 20 ma (2 ppm pk-pk) Magn: > 1 Mx See a tennis ball on the moon Detection Imaging (TEM) Scanned imaging (STEM) X-ray (EDX) Energy loss (EELS) Info limit 1.2 Å (0.12nm) Atomic resolution

4 TALOS the requirements End of 2011 R&D was commissioned to develop a new mid-range TEM, with the following high-level requirements: Sustainability: remove obsolescence issues & comply with RoHS Profitability: gross margins (GM) to FEI s standards Credibility: Fit for the future A workhorse to get repetitive work done reliably and quickly operable by a broader group of people. In short need to move from an instrument to a tool Time to market: The need for speed launch in 1.5 years (M&M2013), shipments in 2 years (2014Q1) Platform: Derived tools are placed on roadmap up front Arctica for Cryo-TEM, Lab6 systems for screening, Problem Statement: Create a new platform, with an initial offering within 2 years, followed by regular derivatives/updates 4

5 TALOS Architecture & Design Strategy Basic waterfall model would not work for this time-frame instead Faster TTM, lower NRE and better COGS via Focused & Phased activities Integrated V-model and Agile approach Basic platform design secured via v-model Dynamic feature and bundle development via agile Early testing and prototyping Re-use Example: Existing SW framework Leveraging Multi-platform components: Example: Vacuum driver Off-the-shelf components: Example: On-system display Strategic supplier involvement 5

6 Focused & Phased activities 1 Simplify the commercial offer Simplified System trees & logistics Allows streamlined factory build-up Allows faster release testing Reduces diversity even with NSR s lower TTM & lower COGS & faster Cycletime Feature bundles for faster TTM Basic carrier & feature set in 1 st release within 2 years Following feature sets in 6 month slots Deliberate product phasing (e.g. Cryo-TEM in B2b) Fitted to environmental rhythms (marketing events, SW heartbeat, budget, etc.) 6

7 Focused & Phased activities 2 V-model combined with agile Bundles are each a V (PMP project management process) SyRD, FRD, CRD s, CDD, STD s etc. are created and executed Items in the bundle (feature) list have a maintained priority SyRD is synchronized at each initiation gate Feature set is then frozen for that bundle Within bundles agile is used for feature development Bundle feature list is backlog for SW and used even in mechanical design 3 week sprints for SW Lean platform development Bundle content can change during bundle definition 7 When agreed with stakeholders items moved from bundle Bundle roadmap with backlog bundle for logging platform scope Features that drop out are put on backlog for future bundles Priority of features used to plan the execution in the bundle Agile system development

8 Leveraging Multi-platform components Apply components from higher volume lines for COGS Approach worked for infrastructure items but not all Example: Vacuum Driver Module project driven by SDB (high volume application) BB Architecture = 2 for SDB and 1 for TALOS = COGS / scalability Forward compatibility to new 120kV system Common form factor, aligned feature set (FW, FW IF + comm s) 8

9 Leveraging Off-the-shelf components Off the shelf solutions for specific features Approach worked for infrastructure items Example: On-System Display Standard industrial quality part Business case showed and is showing better value than developing and maintaining FEI specific module Seems counterintuitive due to total volume vs specific volume Standard form factor and standard stable interfaces Mech, Elec (12V + Cat5) and SW (web app + Ethernet) Easy migration to future Adapter in mechanical design System operates independently of OSD presence Workflows documented and maintained with application scientists Web application communicates with the system PC via Ethernet» all intelligence (workflow translation) in Microscope PC Direct OSD supply to factory and field with plug n play Supports graceful degradation

10 Leveraging Strategic supplier involvement Early supplier involvement for specific custom designs coupled to production enabled ambitious time schedule (via virtual R&D) works well when supported by internal experts NTS : Frames & Hoist, Enclosure Neways: PCBs: Vacuum control, communication, power distribution, Prodrive : Optics Electronics In: power, cooling, communication (Ethernet) Out: highly stable currents (11 A, < 2 ppm pk-pk) van Berlo: Industrial Design Sioux : On System Display Software 10

11 Forward / Backward compatibility 1 reuse: SW stack new: EE & ME reuse: all except Integrate: autoloader module New: Covers, OSD workflow Improved IDU Talos Arctica Tecnai Talos F200 reuse: all except New: Sub-frame, Covers, accelerator module, HT tank One SW stack Talos Lab6 11

12 Forward / Backward compatibility 2 V-model sets the framework (architecture) Ensures system design is future prepared and forward compatible maximise re-use and avoid diversity Applied for defining the Platform and its scope In order to minimize changes (in future bundles) In Talos most changes are cosmetic (e.g. cover) with reuse of key elements (e.g. column, optics electronics) Dominates in early bundles Agile Ensures fast and flexible development of features Applied for feature and accessory integration (within bundles) Allows for more flexible feature release within a bundle Dominates in later bundles 12

13 Agile System development fast prototyping Not just Agile in software: Testing major use cases on mock-ups and proto-types Used Proof of Concept optics electronics for Alpha tool Testing by user representatives and service/manufacturing All of this early in Design Phase 13

14 Conclusions Talos is a flexible platform rather than a fixed product Addresses the stakeholder requirements in allowed timeframe First product realisation in 2 years Still expanding with new products and features The V-model and agile approach are combined V-model ensures platform approach and avoids diversity Agile ensures flexible timeboxing of features with good stakeholder alignment Leverage of multiplatform components for better GM and lower NRE Works well for infrastructural functions (e.g. vacuum, HT) Leverage of off-the-shelf components for better GM and lower NRE Works well for platform/product specific items (e.g. Talos OSD) 14

15 Thank You