Project How Tos

Disclaimer: This is RS view - none of this is binding!

CDD - Drawings Quality Cycle

All drawings for LIU-Ions must go through the Quality Control 1 and 2, and then an approval process.

The approval process is launched by the the activity leader for the project requesting the change. For example RS will launch the approval process for any LIU requested designs.

C1 is performed by the design office (check of drawing information).

C2 is (for equipment) performed by the engineer. For a section assembly, it is done by RS (only as a prelude to launching an approval).

To make C2:

  • The right to make C2 is given depending on the drawing code. RS has the right for PS_L for the LEIR lines (at least).
  • Go to EDMS, and log in, then to CDD home page ( , select Quality Control
  • Enter the drawing number to be controlled (using a wildcard will return several drawings, they can be individually controlled) - it can take a minute to seach.
  • On the next page, right click on the drawing number and open in a new tab, from there open the drawing to check it, if it is a second round after rejection, also open the previous version to check comments were taken into account).
  • Once you have controlled it, click "Execute Control 2/Set to release" - this can take 1 minute.
  • A page is returned saying control 2 was done.
  • Repeat for several drawings.

To make Start an Approval Process:

  • The right to make C2 is given depending on the drawing code. RS has the right for PS_L for the LEIR lines (at least).
  • Go to EDMS, and log in, then to CDD home page (
  • First decide who should approve: Under Manage Group click manage group.
  • Click the "LEIR Drawing Approval List" and modify as necessary.
  • Go back to the Approval Process Page (you may have to go back to the CDD home page to find it again).
  • Select Approval Process.
  • Under Start Approval Process, Click drawing or folder (if one exists).
  • Find the LEIR Drawing Approval List (of members).
  • Enter the name of the drawing or folder.
  • Enter a comment (e.g. for a section assembly, note what has been changed).


Designing a Work Unit

A workunit is followed up by 1 person, who should be well aware of the technical, schedule and budget requirements of the associated deliverables.

The workunit must be designed to allow both budget evaluation and work progress assessment!

Take an item (a device) and break down its cost and schedule, typically into specification, design, production, installation, commissioning.

Does the cost of each part have a non-linear profile. E.g. production might incur a lot of costs at the end, if that is true, split further.

Weight each deliverable to its budget (in CHF, or kCHF).

Budget for any device must include

  • All design costs. Don't forget vacuum insertions, and the assembly drawings for sectors.
  • Integration costs (merging designs, preliminary layouts etc).
  • Cabling, racks, electrical power distribution. Now there can be decabling costs (can double the cost of cabling).
  • Supports
  • alignment targets, their metrology, and some cost for survey team.
  • Vacuum insertion (unless agreed with vacuum otherwise) including its design.
  • Vacuum pumping (unless agreed with vacuum otherwise).
  • Manpower for FSU etc, clearly mark.
  • Manpower for students fellows (clearly marked, this might be moved to a central budget in the next phase).
  • Transport and handing (hardware, tooling and maybe actual transport if there is a lot to do).


Report once a month on a workunit, an email is sent.

The workunit deliverable progress with budget should reflect the advancement in paying the budget towards a full 100% cost. For example, if 50% of the (present estimate) of the final cost is paid, 50% should be reported. If this really cost 60% of the original budget, this will turn up as a

If you want to report work progress on actual equipment,

-- RichardScrivens - 2018-01-08

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2018-12-11 - RichardScrivens
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    IONSUpgrade All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback