MICE AFC Work Group meeting February 13, 2004 Introducing the Coat Hanger technique --- the Global reference system Wing Lau.

Slides:



Advertisements
Similar presentations
Softricity LLC Advance slides with arrow keys. Without PDMLynx Informal processes based upon excel, access, paper files No consistency across organization.
Advertisements

MICE RF Cavities and RFCC Module Update Derun Li Lawrence Berkeley National Laboratory MICE RF Workshop Daresbury Laboratory, UK April 17, 2012 April 17,
SOFTWARE TESTING. INTRODUCTION  Software Testing is the process of executing a program or system with the intent of finding errors.  It involves any.
Method to fix wall tiles. Preparation All wall tiles to be immersed in water for 3-4 hours for better results. Some gap in between the rows to allow the.
MICE Collaboration meeting at RAL 26 th Oct ~ 29 th Oct, 2004 Wrap up on Radiation Shielding Module Design Stephanie Yang 26 th October, 2004.
© 2012 Autodesk Structural Workflows for Autodesk ® Plant Design Suite Projects Abraham Koenig Technical Specialists Manager AEC/ENI Central Europe Alexandre.
Chapter 10—Creating Presentations
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
HERMES tracking for OLYMPUS. Part #1. Detector survey. A.Kiselev OLYMPUS Collaboration Meeting DESY, Hamburg,
A simple clamping device for the Solid absorber Wing Lau, Oxford.
AFC engineering group meeting on the 26 th of Jan 2004 MICE Absorber Focus Coil work schedule for the next 6 months By Wing Lau, Oxford.
Agreement on scope of supply and extent of interface among different suppliers of the AFC module This talk covers the scope of supply on the Absorber Focus.
1 Sources:  SusanTurner - Napier University  C. Robson, Real World Research, Blackwell, 1993  Steve Collesano: Director, Corporate Research and Development.
MICE RF and Coupling Coil Module Integration Issues Steve Virostek Lawrence Berkeley National Laboratory MICE Collaboration Meeting October 27, 2004.
MICE Collaboration meeting at CERN March 28 – April 1, 2004 MICE Cooling Channel --- AFC Module work group report Wing Lau – Oxford.
MICE Engineering Integration Update August 13, 2003 Edgar L. Black IIT.
CMPUT 301: Lecture 25 Graphic Design Lecturer: Martin Jagersand Department of Computing Science University of Alberta Notes based on previous courses by.
MICE Collaboration meeting at Berkeley 9 – 12 February 2005 Cooling Channel layout Presented by Stephanie Yang & Wing Lau.
Background to the current problem 1. As a result of the high stresses in the bobbin due to the magnet load, the bobbin end plate needs to be increased.
MICE Collaboration Meeting March 29 - April 1, CERN MICE Integration Edgar Black/IIT March Room.
Status of 201 MHz Prototype and RFCC Module Derun Li, S. Virostek, M. Zisman Center for Beam Physics Lawrence Berkeley National Laboratory In collaboration.
MICE Collaboration Meeting March 29 - April 1, CERN MICE alignment, tolerances and supports Tuesday March 30 Room Edgar Black/IIT March17-
bobbin Thermal radiation shield Magnet cryostat Large End Flange The leading dimensions.
Integration March 18, 2004 Latest MICE integrated lattice layout Edgar L.Black IIT.
MICE Collaboration meeting at CERN March 28 – April 1, 2004 MICE Cooling Channel --- AFC Module progress update Wing Lau – Oxford.
MICE Collaboration Meeting Harbin, China 13 – 17 January 2009 Integration Issues By Wing Lau, Oxford University.
FNAL-SCRF 会議報告 1. Cryomodule, Plug-compatible Interface ( 大 内) 2. High Pressure Code, 5K Shield (Tom Peterson)
Integrate your people maximize your knowledge Tel SalesBase Customer.
RF Cavity / Coupling Coil Module
Activity 1 - WBs 5 mins Go online and spend a moment trying to find out the difference between: HIGH LEVEL programming languages and LOW LEVEL programming.
MICE VIDEO Conference 17 th December 2003 Report on AFCSWG Safety Review -- Future Plan By Wing Lau -- Oxford.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
DAY 14: ACCESS CHAPTER 1 Tazin Afrin October 03,
Engineering Matrix Megatec 2011.
In the next step you will enter some data records into the table. This can be done easily using the ‘Data Browser’. The data browser can be accessed via.
1 Computer Systems & Architecture Lesson Building Systems from Off-the-Shelf Components.
CLIC Permanent Magnet Quadrupole update 1 st December 2010 Mechanical Engineering status N. Collomb1.
Hall 180 Cryogenic test facility: Project management: Project Change Request, EVM and Interface Sheet L. Serio.
Presented by: Ashgan Fararooy Referenced Papers and Related Work on:
Sequence Diagrams And Collaboration Diagrams HungNM.
Basic Concepts of Component- Based Software Development (CBSD) Model-Based Programming and Verification.
© 2012 Autodesk Autodesk Structural Curriculum 2013 Unit 5: Advanced Structural Analysis & Coordination Advanced Structural Analysis & Coordination.
MICE – MUON Interface meeting at Mission Inn, Riverside, California January , 2004 MICE Cooling Channel Integration Issues Wing Lau – Oxford & Steve.
1Page # Machine Assembly WBS 700 By: James H. Chrzanowski January 24, 2001.
MICE RF Cavities and RFCC Module Update Allan DeMello and Derun Li Lawrence Berkeley National Laboratory MICE CM32 at RAL, UK February 9, 2012 February.
Design Concept Display. Emphasis The dictionary contains emphasis in the form of bolded words. The words in bold are given importance to differentiate.
SOFTWARE TESTING. Introduction Software Testing is the process of executing a program or system with the intent of finding errors. It involves any activity.
This tutorial will talk you through a very basic workbench queueing simulation. The queueing system modelled is of customers entering an infinite capacity.
Object Oriented Programming Criteria: P2 Date: 07/10/15 Name: Thomas Jazwinski.
A guided tour of Ensembl This quick tour will give you an outline view of what Ensembl is all about. You will learn: –Why we need Ensembl –What is in the.
NEDM Collaboration Meeting 5/2008 Preliminary Engineering Report nEDM Central Detector John C. Ramsey Los Alamos National Laboratory.
BCM 210-L1 IMPACTS OF MATERIALS AND METHODS. DEFINE THE FOLLOWING MATERIALS METHODS ASSEMBLIES.
WBS ? Proposed by IPRP … –Preparation for a review –MICE Costs & Time Scales need to be more accurate & Justified –Technical Leaders arranged by technology.
1 of 175 Focus 3D X 130 and X 330 Laser Scanners SCENE 5.3 September 2014.
Module 7 Unit 22 – Welding Prints. Learning Objectives Identify a welding symbol. List the elements of a welding symbol. Explain the meaning of a welding.
TEAM FOUNDATION VERSION CONTROL AN OVERVIEW AND WALKTHROUGH By: Michael Mallar.
SPHENIX MECHANICAL D. Lynch September 11, AGENDA Global Design Concept – Updated Global Assembly Concept – Updated Inner HCal Installation concept.
OsC mtg 15/10/2014 MICE Step IV Alan Grant. Content Step IV – Construction Status – Finances – Schedule – Risks – Summary 2.
VERY PRELIMINARY SURVEY OF MAGNET AXES OF USS – FC – DSS 26 March 2015 V. Blackmore & J. Cobb Everything that follows must be regarded as very preliminary.
3M Partners and Suppliers Click to edit Master title style USER GUIDE Supplier eInvoicing USER GUIDE The 3M beX environment: Day-to-day use.
Introducing the MiTek 20/20 MiTek 20/20 Roof Engineering Program.
SOFTWARE TESTING LECTURE 9. OBSERVATIONS ABOUT TESTING “ Testing is the process of executing a program with the intention of finding errors. ” – Myers.
Network planning models These project scheduling techniques model the project's activities and their relationships as a network. In the network, time flows.
RFCC Engineering Status and Plans Allan DeMello Lawrence Berkeley National Laboratory MAP Winter Meeting March 6, 2012 March 6, 2012.
Software Testing.
FIRST VIDEO CONFERENCE JANUARY 7, 2004 Edgar L. Black IIT
Eleanor Roosevelt High School
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
Door and Window Schedules
PSS0 Configuration Management,
Presentation transcript:

MICE AFC Work Group meeting February 13, 2004 Introducing the Coat Hanger technique --- the Global reference system Wing Lau

Distinguishing between a stand-alone item and an interfacing item through drawing convention Stand alone items are those within the scope and responsibility of the same supplier and as such it does not interface with any other equipment suppliers. As an example, the Magnet Coil is a stand alone item as its design bears no impact on either the Window or the Absorber supplier. Where items made by one supplier and joined to those made by another supplier, they are known as interfacing items. As an example, the flange in the Large End Plate (marked in Pink) is an interface item as it interfaces with the Warm Vessel supplier. In the drawing on the left, there are three different suppliers, each is marked with a different colour code. The parts that interface with other parts of different suppliers are marked in pink. Drawings on the Pink parts have a joined ownership of all the interfacing suppliers. In the MICE project, the pink parts will have a different drawing convention than the rest. Any changes made on these drawings will be notified to all the related interface suppliers for comments and consent.

The Coat Hanger technique An equipment which has multiple suppliers would comprise stand alone parts and interface parts as explained previously. The design and supply of the stand alone parts are the sole responsibility of the individual suppliers, but the design and arrangement on the interface parts have the joint ownership of all those who have an interest in that interface. The WBS project engineer is responsible for specifying the interface dimensions and space envelop. As long as the stand alone equipments are within the given space envelop, the suppliers are free to make changes to them. No approval is needed for making these changes. But any alteration to the interface parts must have the approval of the project engineer. This must be communicated via the interface drawings. Even then, it is still not possible to catch all the changes made to the interface drawings because of the nature and the size of the project. A better system which could automatically trigger a warning to the project engineer of changes made is therefore needed. The Coat Hanger technique is designed to offer this facility and is a good way to ensure interface compatibility

The Coat Hanger technique (continue) The conventional way of assembling the different parts together is by attaching the adjoining parts to a common interface boundary. Where there are multiple interfaces, or where one part joins onto another part and another part and so forth, it would be difficult to define the order of interface. It would also accumulate errors as parts are assembles related to each other only locally and not globally. This makes the checking of interface compatibility extremely difficult. As an example, the tiling of a wall……….

The Coat Hanger technique (continue) These are the supplied tiles This tile is slightly oversized, but not noticeable without a dimensional check This is what the drawing says how the wall should be tiled Sequence of tiling is as shown: Black arrows first, followed by red arrows

The Coat Hanger technique (continue)

Mismatch / foul went undetected until the job is nearly finished

The Coat Hanger technique (continue) The conventional way of assembling the different parts together is by attaching the adjoining parts to a common interface boundary. Where there are multiple interfaces, or where one part joins onto another part and another part and so forth, it would be difficult to define the order of interface. It would also accumulate errors as parts are assembles related to each other only locally and not globally. This makes the checking of interface compatibility extremely difficult. The way to overcome this is to avoid having to assemble parts onto each other. In this new concept, every parts will have a reference centre which coincides with one of the globally registered centres designed to position the magnet modules relatively to the beam line and then to the experimental hall. This reference centre acts like a coat hanger

The Coat Hanger technique (continue) Global reference centre

The Coat Hanger technique (continue) Global reference centre Reference centre for the individual tile

The Coat Hanger technique (continue) Global reference centre

The Coat Hanger technique (continue) Global reference centre Reference centre for the individual tile

The Coat Hanger technique (continue) Global reference centre Reference centre for the individual tile

The Coat Hanger technique (continue) Global reference centre

The Coat Hanger technique (continue) Global reference centre

The Coat Hanger technique (continue) Global reference centre Overlap / mismatch identified

The Coat Hanger technique (continue) Global reference centre

The Coat Hanger technique (continue) The conventional way of assembling the different parts together is by attaching the adjoining parts to a common interface boundary. Where there are multiple interfaces, or where one part joins onto another part and another part and so forth, it would be difficult to define the order of interface. It would also accumulate errors as parts are assembles related to each other only locally and not globally. This makes the checking of interface compatibility extremely difficult. The way to overcome this is to avoid having to assemble parts onto each other. In this new concept, every parts will have a reference centre which coincides with one of the globally registered centres designed to position the magnet modules relatively to the beam line and then to the experimental hall. This reference centre acts like a coat hanger The referencing system works like a global navigation system. Through the reference centres, we can refer the position of each parts to a global coordinate. By hanging the various parts to a globally registered centre, it will automatically assemble the parts to a pre-defined position. Any interface incompatibility will be easily detected as each equipment / parts will have its unique place in the global coordinate system. No two parts should have the same coordinates. We will insist on this centre being retained on all the stand alone and interface drawings.

This is how it works on MICE: There are different levels of reference centre, designated to have a similar “level” allocation as the WB packages. The level 1 reference centre is the centre of the experimental hall; The level 2 reference centres are those along the beam line centre for the positioning of each of the modules; The level 3 reference centres are the centres of the individual modules As an example:- The Focus Coil module will have a level 3 reference centre. All the parts associated with the windows and the absorber will be referenced to this level 3 reference centre. The Focus Coil modules, the Coupling Coil, the detector modules and any equipment that are aligned to the beam centre line will be referenced to the level 2 reference centre. The beam line centres will be referenced to the level 1 reference centre etc.

These parts will have level 3 reference centre attached The level 3 reference centre on the FC module

All the AFC parts will then be hung to the level 3 reference centre at the Focus Coil

The hanging of the AFC and Coupling modules

Level 2 reference centres Level 3 reference centres

Interface compatibility check at a glance

The Coat Hanger technique is an effective tool in keeping interface control simple and fool proof. A software is being developed to allow mismatches and fouls to be check automatically. I suggest we ask the package suppliers to apply the global reference centre to each and every drawing that they produce. I will discuss with the Integration managers on the coordinates of the relevant reference centres applicable to all the parts within the AFC module. It is hope that this can be applied to other modules across the MICE project. Observations: