ds3910003600.pdf

DS-391-000-36 Verify that this is the latest revision.

1 of 13 Check for change orders or requests

DESIGN STANDARD Doc. No.

DS-391-000-36 R0

LUSI SUB-SYSTEM

(All)

MECHANICAL DESIGN

STANDARDS SUPPLEMENT

Prepared by: Donald Arnett

LUSI System Design Supervisor Signature Date

Reviewed by: Kurt Vaillaincourt

CAD Support Engineer Signature Date

Approved by: Rick Tankersley

Mech. Design Dept. Head Signature Date

Approved by: Nadine Kurita

LUSI Chief Engineer Signature Date

Approved by: Jerry Hastings

LUSI Project Director Signature Date

Revision Date Description of Changes Approved

R0 17 Dec 07 Initial release

Table of Contents

1. Introduction

2. Applicable Documents

2.1. MD Design Standards

2.2. MD PDM Support Documents

2.3. Non-MD Documents

3. Mechanical Design File Management

3.1. CAD Files and Project Documentation

3.2. Configuration Control and ECOs

4. LUSI Documentation Structure

4.1. Top Level LUSI Documents

4.1.1. Main Beamline and Experimental Hall Facilities

4.1.2. Experiment Hutches

4.2. Experiments and Components

4.3. General Purpose Drawings

4.4. Installation Drawings

5. Modeling Conventions

5.1. Coordinate Systems and Beamline Orientations

5.2. UHV Flanges

5.3. Flexible Couplings for Vacuum Chambers

5.4. Vendor Items and Hardware

5.5. Unique vs. Common Components

5.6. SE Model File Requirements

6. Drafting Conventions

6.1. File Names and Drawing Numbers

6.2. Drawing Titles and Approvals

6.3. Drawing Content and Arrangement

6.4. Material Callouts

6.5. Parts Lists/Material Lists

6.6. Notes

6.7. Dimensioning and Tolerancing

6.8. Drawings Submitted for Check

6.9. Miscellaneous

DS-391-000-36 Mechanical Design Standards Supplement

1. Introduction

This document provides for the LUSI engineering and design staff the requirements and standards that are to be used when generating CAD models and detail drawings for the LUSI project experiments and components. This Standard is to be used in conjunction with the SLAC Mechanical Design Standards documents that are accessible through the MD website. This document supplements those standards by providing additional requirements that are particular to the needs of the LUSI project.

2. Applicable Documents

2.1. MD Design Standards

http://mdweb.slac.stanford.edu/Resources.MD%20Standards.php (requires login)

• gy DS-016-110-14 Design Tree File Management Methodolo

• DS-016-110-01 General Drafting Instructions

• DS-016-110-04 General Drafting Instructions-Mechanical Design

• umbering System DS-016-310-01 Engineering Document N

• DS-016-110-13 Abbreviation Standards

2.2. MD PDM Support Documents

http //m dsup/Support%20Documents/Forms/AllItems.aspxs: dpdm.slac.stanford.edu/sites/design/mca ure.pdf

Check, Approve, Release Form Help.pdf

• Revision Request Form Proced

• f MDPDM User Procedures.pd

• MDPDM Requirements.pdf

2.3. Non-MD Documents

• ASME Y14.5 Dimensioning and Tolerancing

• LCLS-TN-03-8 LCLS Undulator Coordinate System

3. Mechanical Design File Management

3.1. CAD Files and Project Documentation

The MD Design Standards address everything from CAD file creation and management to drawing preparation and release of both drawings and files. Those Standards are to be used by all LUSI design staff wherever applicable. While “in work”, all SolidEdge™ (SE) documents shall be maintained in the Insight PDM system, under the hierarchy provided at:

https://mdpdm.slac.stanford.edu/sites/design/pre/LUSIDocLib

All other design related, non-releasable files shall be stored in the V:\LUSI\LUSI Design Tree &

Support Docs hierarchy. It is here that the design staff will store and archive all of their support documents such as ANSYS files, BOMs, manufacturing documents, MSOffice documents, image files, PDFs, and downloaded/received files such as .stp, .dxf, .dwg, etc. The V:\ drive hierarchy is also to be http://mdweb.slac.stanford.edu/Resources.MD%20Standards.php https://mdpdm.slac.stanford.edu/sites/design/mcadsup/Support%20Documents/Forms/AllItems.aspx used as a guide for naming and storing of SE files in the PDM. The folders there are a parallel structure to the one in the PDM. The folder names include the number series that are to be used for the document numbers that the folders contain. See figure below.

Insight PDM

V Drive

Figure 1. LUSI File Structure Examples (subject to change)

3.2. Configuration Control and ECOs

LUSI design configuration control consists of maintaining SE files in the MD PDM and images of released drawings in the MD Document Control SODA database. All models and drawing packages shall be released when complete using the “MD Check Approve Release” process. Refer to the MD PDM support documents “Check, Approve, Release Form Help.pdf.” for instructions on how to accomplish these tasks. See also section 6.8 below for submitting drawings. When changes are necessary, an appropriate ECO must be prepared and approved, after which the documents can be revised if required and released. Refer to the document “Revision Request Form Procedure.pdf.” All models must be maintained at the same revision level as the drawing to which they report.

4. LUSI Documentation Structure This section describes how to build the document types shown below. Refer to the V:\LUSI\LUSI

Design Tree & Support Docs hierarchy for where the various documents are stored and how they are numbered.

4.1. Top Level LUSI Documents

The physical arrangement of the actual LUSI project is as follows:

The LCLS beam from the undulators enters the FEE building at the end of LCLS. In the FEE, the incoming beam is split off into the beams that will enter the LUSI areas, which consist of the Near Experimental Hall (NEH), followed by the X-Ray Transport Tunnel (XTT), and finally the Far Experimental Hall (FEH). The NEH and FEH each contain three “hutches”, which are large rooms that house the experiments and are connected by common beamlines and the XTT. The effort is to document each of these rooms in detail and be able to bring them together at the hall level which then reports to the main LUSI top level document. A “GP” (see below) schematic drawing will serve as the main, top level document for describing the LUSI project and its main sub systems.

4.1.1. Main Beamline and Experimental Hall Facilities

The primary documents for constructing the NEH and FEH shall be two GP drawings that collect the

“hutch” assembly files. Each of these assembly files shall be prepared with a “main beamline” file (mr39175000.par, Master Beam) attached to it and a hall “building” file attached to it (from DGN/INTEGR/CONVFAC). These two files are connected via coordinate systems to the “LUSI 0,0,0” origin, which is defined to coincide with the LCLS “HOMS M2” mirror. See figure below. (Note: the location of the mirror with respect to the LCLS coordinate system may change, but the mirror will remain the LUSI origin.) Together, the two files serve to anchor the hutches to the facility they are installed in.

This guarantees that the position of the beamline components will always be correct even if one or the other is updated.

Figure 2. LUSI Coordinate System

The geometry shown in Fig. 2 is in reference to the LCLS coordinate system Sta. 100 origin, as described in Tech Note:

http://www-ssrl.slac.stanford.edu/lcls/technotes/lcls-tn-03-8.pdf

The Master Beam file contains a variety of coordinate systems which serve to locate the buildings, hutch beam lines, and the main LUSI experiments within the hutches.

The XTT drawing will be a GP that shows the main assemblies that are installed into the tunnel.

4.1.2. Experiment Hutches

The main hutch assembly drawings shall be GP drawings that contain all of the various experiment devices and the integration components that connect them to the facilities world. The first parts placed in these assembly files are the Master Beam and building files (as above). A “local” hutch beamline file is then attached to the Master Beam via a mated coordinate system from each file. To this local beamline file, coordinate systems are added which serve to locate device centers and populate the hutch. These coordinate systems shall be placed in the file by the MD 3D Layout tool in SE, using a controlled MSExcel file. This file is to be kept “In Work” by the experiment designers. The hutch components can then be viewed or documented with the buildings turned on or off as desired.

4.2. Experiments and Components

Experiments are broken down into major sub-systems for manageability, and together with all of the various types of other devices serve as “components” that can be put wherever desired and, if necessary, duplicated in other locations. These components must reside in the DGN/ folder in the hierarchy. The top level drawing for any stand-alone component that can be placed onto a beamline or otherwise located http://www-ssrl.slac.stanford.edu/lcls/technotes/lcls-tn-03-8.pdf into a hutch as a main component shall be an AD drawing, and a “DeviceCenter” coordinate system is inserted into the model. See 5.1 below.

4.3. General Purpose Drawings

A GP drawing is used as follows:

• To call out installation drawings to help guide people to the correct documentation. For example, the GP drawings for the NEH and the FEH would indicate what drawings to refer to, in order to drill down to the lower level drawings.

• GP drawings are also used for critical and non-critical instrumentation documentation. Non-critical instrumentation is defined as any instrumentation that is not used for PPS, MPS or machine operations. For example, thermocouples that help diagnose a component failure are non-critical instrumentation, but thermocouples that are used to shut off the beam for machine protection would be critical instrumentation.

4.4. Installation Drawings

IDs serve to bring together various components from the DGN/ folder and show how they are installed into the hutches. The ID drawings shall show the following when applicable:

• Interface connections and hardware and any support stand(s)’ hole patterns.

• Floor drilling instructions and the hardware required to attach the stand to the floor.

• Floor anchor setting and grouting callouts.

• Adjacent components that are being connected to or are close enough physically shall be shown in phantom.

• Location, positioning and alignment information.

5. Modeling Conventions To insure uniformity and efficiency in SE the following conventions shall be used.

5.1. Coordinate Systems and Beamline Orientations

SE coordinate systems shall be used as device centers in component level assembly model files and must be placed on the native file reference planes whenever possible. The orientation of the model about these axes shall be set as shown in Figure 3. Always use the “match coordinate system” command in SE to place component level devices onto the beamlines in the hutches. Selecting a standard SE isometric view rotation will yield a view where the upbeam end of the device is in the upper left corner of the view and the downbeam end of the device is in the bottom right corner of the view. Any data that comes from the physicists to do beamline analysis (such as a ray trace) must be corrected for the axis discrepancy in the data before it is placed in SE. More information on creating device centers is available at:

https://mdpdm.slac.stanford.edu/sites/design/mcadsup/Support%20Documents/Solid%20Edge/Device

%20Center%20Coordinate%20Systems%20.pdf https://mdpdm.slac.stanford.edu/sites/design/mcadsup/Support%20Documents/Solid%20Edge/Device%20Center%20Coordinate%20Systems%20.pdf https://mdpdm.slac.stanford.edu/sites/design/mcadsup/Support%20Documents/Solid%20Edge/Device%20Center%20Coordinate%20Systems%20.pdf

Figure 3.

5.2. UHV Flanges

A variety of different vacuum flanges will be used in the LUSI beamlines, in addition to the typical stainless steel knife edge conflat type, with the OFE copper metal gasket and 12-point silver plated bolt set. In most cases, the upbeam flange of a beam line vacuum chamber should be non-rotatable, and the downbeam flange rotatable. For a visual cue when looking at models make sure the rotatable flanges are green and the non-rotatables are red. Flange pairs shown on drawings shall be labeled with a text callout “R” and “NR” placed adjacent to the flanges, as appropriate. All standard CF flanges and flange hardware must be placed in models from the following location:

https://mdpdm.slac.stanford.edu/sites/design/rel/ComPartDocLib/Flange Common thru bolt flange hardware does not need to be included in assembly models or shown in drawing views. These fasteners must be called out in the parts list, along with the metal gasket that forms a sealed flange pair. The “REF__ xxFlgGskt__common.par” part files in the PDM hardware directories have “compressed” (deformed) gasket models in them and a callout that appears in the parts list on the drawing. Insert the appropriate part into the assembly at the flange joint with an “insert” command. The deformed gasket appears correctly in section views without the lines on top of each other. The “REF__ xxFlgGsktwBolts__common.par” parts include the bolt set callout. Any other flange hardware that is used shall be shown, and the “REF__ xxFlgGskt__common.par” part file shall be used so that a parts list item is generated. When the typical thru bolts are not shown, the drawing shall contain a note that states “THRU BOLTS (12 PT, Ag PLT) AND NUTS NOT SHOWN” or “THRU BOLTS (HEX HEAD, Ag PLT) AND NUTS NOT SHOWN”, depending on which one is used. Typically, flanges 10” and smaller use 12 point bolts, and flanges larger than 10” use hex head bolts.

5.3. Flexible Couplings for Vacuum Chambers

Commonly known as “bellows”, these are usually vacuum components that may be used in more than one location. If a special design is needed, it is to be created and stored in the “DGN/VAC/FlxCouplng” directory. Use “off-the-shelf” convolution modules and endplates from vendors wherever possible.

Models of bellows units are to be kept simple and shall have features that represent convolutions, are https://mdpdm.slac.stanford.edu/sites/design/rel/ComPartDocLib/Flange adjustable in length, and appear reasonably correct in section views. Make an “adjustable part” in SE, and have the length limits set in a variable table. This variable is then set at the next assembly. Straight ID/OD protrusions are not allowed, and the endplates/eyelets/fittings must represent and carry features of the actual item.

SLAC does not weld bellows convolution segments together or to endplates (eyelets). Because of this, welded bellows assemblies and endplates sometimes need to be custom made by a vendor. In this case an “SC” drawing is created showing the envelope sizes and tolerances and a SLAC “PS” specification is cited that applies to the manufacture, performance, and quality control of the item being purchased.

5.4. Vendor Items and Hardware

Models of vendor items shall be stored and retrieved from:

https://mdpdm.slac.stanford.edu/sites/design/rel/VenDocLib Unless otherwise specified, all multi-part vendor items shall be modeled as one part. Possible exceptions would be articulated or sliding parts, in which case the item shall be modeled as simply as possible with the moving element controlled by limits in a variable table and a dimension that is set at the next assembly (adjustable part/adjustable assembly).

If you are modeling a vendor part that is not already in the database then the part must be stored in the “LIBrary” directory for subsequent promotion into the database. Refer to the MD PDM support document “MDPDM Procedures.pdf” for instructions on this workflow. Make sure that proper file naming conventions are followed and keep the filename as short as possible.

Models of hardware items shall be stored and retrieved from the fastener databases in the PDM located at:

https://mdpdm.slac.stanford.edu/sites/design/rel/VenDocLib and https://mdpdm.slac.stanford.edu/sites/design/rel/ComPartDocLib/Fstnr If a new hardware item is to be created, it must be placed in the “LIBrary” directory for subsequent promotion as described above. All multi-part hardware items shall be modeled as one part whenever possible.

Unless otherwise specified, all hardware required to build a component level assembly (except for flange bolt sets as described in 5.2 above) is to be shown in its entirety on the AD and is called out in the parts list.

Consumables (lubricants, epoxies, braze alloys, etc) that are used in assembly are not shown in parts lists; they should appear in drawing notes.

5.5. Unique vs. Common Components

Most unique parts and assemblies are stored in the appropriate device component directory in DGN, and carry part numbers assigned to those directories.

Common parts and assemblies are stored in the “Mech”, “Vac”, or “Integr” directories and carry the part numbers assigned to those directories. The DC will arrange exceptions as required.

5.6. SE Model File Requirements

The design staff is expected to be familiar with the “minimum SE file requirements” found in the MD website document http://mdweb.slac.stanford.edu/stds/01611014R1.pdf. Efficient design practices reduce model complexity and allow others to edit files easier. Use the following guidelines when constructing model files:

• Try to model in as few steps as possible.

• Extrude primary protrusions symmetrically about their reference plane.

https://mdpdm.slac.stanford.edu/sites/design/rel/VenDocLib https://mdpdm.slac.stanford.edu/sites/design/rel/VenDocLib https://mdpdm.slac.stanford.edu/sites/design/rel/ComPartDocLib/Fstnr http://mdweb.slac.stanford.edu/stds/01611014R1.pdf

• In profiles, use geometric constraints in lieu of dimensional constraints wherever possible.

• Use feature based modeling commands such as mirror, hole, round, fillet and lip in lieu of profile based commands such as protrusion or cutout when adding features to a part.

• Use the folder “DGN/AssyLib” for storing groups of fasteners that will be placed into assemblies that don’t contain patterns. Refer to SE Help for how to use the “Create Systems Library” command, and remember to occasionally delete the files you place in the “AssyLib” folder.

• Avoid overly complex profiles.

• Avoid the use of “.pwd” file type in SE (weldment).

• Avoid creating welds as an assembly feature.

• Avoid making copies of files to “temp” directories, and not cleaning them out when done.

• Avoid leaving un-releasable files in PDM directories.

6. Drafting Conventions The following conventions and guidelines shall be used when preparing drawings. Attention to these details will insure that a drawing or drawing package is ready for check. Checkers will be looking for these things.

6.1. File Names and Drawing Numbers

Design staff shall refer to the V:\ drive hierarchy for guidance in selecting and recording numbers for their file names and drawings. The Excel files provided there are used to record drawing number usage by project type. Consult with the DC for all issues related to the hierarchy and numbering.

6.2. Drawing Titles and Approvals

Design staff shall use the drawing number Excel files mentioned above to record the information for filling out the drawing titles. Generally, the first line is the LUSI system, the second line is the device or component name (usually the folder name), and the third line is the detail name. See Section 6.9 for a list of the main LUSI systems. Use the part naming standard found at:

http://mdweb.slac.stanford.edu/stds/01611004R3.pdf Consult with the DC/checker for questions about what to put in the drawing titles. Avoid duplication of terms in the title block. Avoid the use of fabrication terms like “MACHINING” or “WELDMENT” in the names of parts or assemblies.

The approvals block for LUSI drawings will generally consist of the project/system manager, the DC and/or checker, and the chief engineer. Additional names may be required in special cases. All drawings must have the date of release next to the drafter’s name in the “xxMON(th)year” format. Example:

08APR2008.

6.3. Drawing Content and Arrangement

Proper arrangement and content is important to the communication function that technical drawings provide:

• Views must be positioned on the sheet in correct orthographic positions where possible.

• Sections must be positioned directly behind the cut plane where possible.

• Use single-view section for cylindrical parts if possible.

• Section arrows and annotations are not required if there is only one section view on a drawing and it is cut on a centerline.

http://mdweb.slac.stanford.edu/stds/01611004R3.pdf

• Avoid breaking out a detail of a section view. Scale up the section view.

• Out-of-default-scale views and view rotations must be noted.

• Use the minimum number of views and the smallest sheet size to show the item being represented, but do not crowd views, dimensions, or notes. If necessary use a larger sheet.

• Place isometric views on a drawing only for visual aid when the item is complicated, or when an exploded assembly is required.

• Hidden lines in normal views are turned off by default when placing drawing views. When necessary for clarity turn on hidden lines. Examples would be for threaded or counterbored holes, or wherever the depth or orientation of a hidden feature is unclear and extra views would need to be created.

• Hidden lines are never shown in section views, except on threaded holes.

• Centerlines must be shown on all appropriate major features.

• All parts and assemblies must have the physical properties current and all PFs, SAs, and ADs must show the weight stamp located at:

https://mdpdm.slac.stanford.edu/sites/design/mcadsup/Symbol%20Library/Forms/AllItems.aspx

• Part mark identification must be provided for on all parts unless otherwise specified. Place a note on the drawing that states to apply the part number to the part; use tag and bag as an alternate method. Assemblies that will be made in any quantity other than (1) shall contain a serial number in the part marking. See section 6.6 below for more on drawing notes.

6.4. Material Callouts

Use the native material callouts from the SE Material Table whenever possible when starting a part.

Refer to the “Notes.xls” file at V:\LUSI\...\Dgn for standardized callouts for various other materials.

UHV parts require a certified material note: “1. MATERIAL:….” callout on the drawing.

6.5. Parts Lists/Material Lists

All parts lists are populated automatically by Property Manager. When creating SE models of parts and assemblies, MD guidelines for filling out properties must be adhered to. For vendor parts, the “Document No.” property box in Property Manager must contain the vendor name and part number and “OR EQ”, and the “PartDsg” property box must contain the description. For reference, the format for part descriptions is generally the noun and adjectives first, then the size, then the material.

When a part is a “make from”, list the part that is being modified in the material designation and place a “MAKE FROM” callout with a leader next to it on the drawing.

6.6. Notes

The MD utility “MD NoteBuilder” shall be used when creating drawing notes. This utility places notes as a “callout” and can be edited. If necessary, the utility database can be edited to add notes that do not appear. Inform the DC if any additional notes are required in the database.

UHV part and assembly drawings must have all of the appropriate UHV notes appear on the face of the drawing. A “LUSI UHV PART” stamp available at:

https://mdpdm.slac.stanford.edu/sites/design/mcadsup/Symbol%20Library is pasted onto the face of the drawing and the appropriate notes are placed from MD NoteBuilder in this order:

1. material (if a PF-) (certs required)

2. machining (grinding and sulphur based coolants prohibited, (if a PF-) or welding (if an SA-)

3. protect knife edge (if applicable) https://mdpdm.slac.stanford.edu/sites/design/mcadsup/Symbol%20Library/Forms/AllItems.aspx https://mdpdm.slac.stanford.edu/sites/design/mcadsup/Symbol%20Library

4. cleaning (PF-)

5. leak checking (SA-)

6. part marking

7. handling/packaging

Assemblies that are brazed shall have the braze alloy called out in the braze note. Consideration as to correct braze alloys is especially important in cases where multiple braze steps are involved.

6.7. Dimensioning and Tolerancing

• Do not crowd dimensions (dims) too close to the object lines of the part.

• On multi-view drawings, place as many dims that define and locate a particular feature or group of features on the one view where the feature(s) appear in profile.

• If a detail is pulled to show a feature, place as many dims as possible on that view, for that feature.

• Use Geometric Dimensioning and Tolerancing (GD&T) wherever applicable. Apply it correctly by choosing datum features and control tools wisely. Refer to ASME Y14.5 for rules on applying GD&T, and if required, seek assistance before starting drawings.

• When choosing control tools for GD&T, concentricity and symmetry are to be avoided.

• Unilateral (+.000/-.005, for example) and unequal bilateral dimensions and tolerance zones are discouraged. Construct models and apply dimensions to the mean of the tolerance. An exception would be when a dimension has to match a standard drill size for a hole, and the hole can be no smaller, as in the cap screw chart shown below.

• Standard block tolerances for machined and sheet metal parts shall be: .xx = .02, and .xxx = .005. Use 63 for surface finish and .5 for degrees.

6.8. Drawings Submitted for Check

Prior to submittal for check, the drafter should thoroughly review his/her drawings for errors and omissions. When ready for check, a set of drawings shall be prepared and marked “CHECK PRINT”.

This set of drawings shall be reviewed by the cognizant engineer, initialed, and forwarded to the design group checker, along with the “Check Approve Release” form. Any applicable layouts, dimension and tolerance calculations, catalog references, reference prints, and other pertinent data shall be provided to the checker together with the check prints.

6.9. Miscellaneous

• Use the chart below for designing and sizing typical counterbored holes for socket head cap screws. These sizes are based on tools that are available in SE specifically for cap screw applications (all dimensions in inches). Access is through the pull-down menu that appears in the “hole” command when modeling. Use the 3-place “smart-dimension” command when dimensioning the thru holes and apply the tolerances shown. Use the automatic size and depth tools to dimension the counterbores as 3-place dimensions (plus or minus .005 default). Refer to the fixed fastener position tolerance column for placing a GD&T position feature control frame for that hole size at MMC. For floating fasteners, double the values shown in the “fixed” column.

CAP SCREW HOLE AND C'BORE CHART

SCREW

SIZE DIA

CLEAR

HOLE

DIA

CLEAR

HOLE

TOL

HEAD

DIA

C'BORE

DIA

C'BORE

TOL

C'BORE

DEPTH

DEPTH

TOL

POS'N

TOL

FIXED

#0 .060 .073 .086 .133 .075 .005

#2 .086 .106

+.006 -.002 .140 .176 .101 .009

#4 .112 .136 .183 .219 .127 .011

#6 .138 .170 .226 .266 .153 .015

#8 .164 .194

+.010 -.002

.270 .312 .179 .014

#10 .190 .219 .312 .344 .205 .013

1/4 .250 .281 .375 .406 .265 .014

5/16 .312 .344 .467 .500 .327 .015

3/8 .375 .406 .562 .594 .390 .014

7/16 .438 .469

+.015 -.002

.656 .688 .453 .014

1/2 .500 .531 .750 .781 .515 .014

5/8 .625 .688 .938 1.000 .640 .030

3/4 .750 .812

+.030 -.002

1.125 1.188

±.005

.765

±.005

.030

• Main LUSI Systems for line 1 of drawing title blocks:

LUSI SYSTEMS LUSI AMO

LUSI NEAR EXP HALL LUSI XPP

LUSI FAR EXP HALL LUSI XCS

LUSI XRAY TUNNEL LUSI CXI

LUSI HUTCH 1 LUSI XRAY OPTICS

LUSI HUTCH 2 AMO LUSI DIAGNOSTICS

LUSI HUTCH 3 XPP LUSI MECHANICAL

LUSI HUTCH 4 XCS LUSI VACUUM

LUSI HUTCH 5 CXI LUSI CONTROLS

LUSI HUTCH 6