IceCube Kilometer Scale Netrino Observatory Work...

IceCube Kilometer Scale NetrinoObservatory

Work Breakdown Structure

Friday, April 22, 2005 of 44

IceCube WBS Dictionary 1.1 Project Support

1.1 Project Support L3 Lead:

Provide oversight and direction in managing and facilitating the IceCube Project. Act as focal point for ensuring continued support for customer related issues and decisionprocesses. Provide ongoing support for daily operations and review processes toensure accuracy of reporting data while providing leadership in developing tools,preparing for purchases and manufacturing equipment required for IceCubecompletion.

1.1.1 Management L3 Lead: Bob Paulos (Acting)

Coordinate and facilitate activities related to project involving report preparation,subaward management, financial reporting, and customer related issues. Provideoversight of management related activities and act as liaison for managing cost andschedule issues.

1.1.1.1 Project Director/Project Manager L3 Lead: Bob Paulos (Acting)

Direct and manage all resources and activities necessary to deliver a kilometer-scaleNuetrino Observatory to the National Science Foundation (NSF) that is on-time, withinbudget, and meets all performance goals.

1.1.1.2 Financial L3 Lead: Bob Paulos (Acting)

Communicate and coordinate with collaborating institutions and accounting offices forgathering financial data related to IceCube. Maintain a Project Management ControlSystem (PMCS) for processing financial and schedule data into managementinformation and reports (including earned value reports). Disseminate recurring andon-demand management information to managers throughout the colloboration.Support proposal preparation and financial reporting to higher management authorities.

1.1.1.3 Subawards L3 Lead: Bob Paulos (Acting)

Support preparation, award, and management of all subawards and non-USmemorandums of agreement. Prepare documentation and requirements for subaward participation and reporting to IceCube. Act as liaison for reporting and other relatedissues and communicate with all levels of management. Conduct periodic site visits toensure performance and delivery of products within reasonable and acceptabletimeliness.

1.1.1.4 Reviews L3 Lead: Bob Paulos (Acting)

Includes the costs of planning, coordination and infrastructure support for projectreviews and internal collaboration meetings. It also includes anticipated costs forselect collaboration members to attend specific project reviews and internalcollaboration meetings that are not supported within their own budgets.



1.1.1.5 Reliability & Quality Assurance L3 Lead: Bob Paulos (Acting)

Provide expertise in all areas related to Quality Assurance, Reliability and Safety.Prepare plans outlining requirements and operation parameters to ensure environs arewithin acceptable standards. Coordinate and conduct periodic reviews and reportfindings recommending best course of action to resolve issues. Maintain opencommunication with all levels of management.

1.1.1.6 Plans and Controls L3 Lead: Bob Paulos (Acting)

Develop plans and generate reports to satisfy project management and customerrequirements. Conduct detail planning for both cost and schedule representing scopein sufficient detail to manage delivery of key components. Maintain data to supportbaseline and funding profiles for reporting purposes. Gather information fromappropriate sources to consolidate and prepare periodical reports for managers at alllevels of the IceCube project. Provide expertise and guidance for assessing andreporting earned value and for conducting schedule progress updates.

1.1.1.7 Participant Support L3 Lead: Bob Paulos (Acting)

Obtain support from outside experts to assess project status, managementprocesses, and scientific/technical approach; and to recommend and help prioritizenecessary actions. (Not subject to overhead or indirect costs).

1.1.2 Systems Engineering L3 Lead: Randall Iliff

System Engineering includes all engineering above the subsystem/black box level. Itincludes the understanding of scientific, logistical, environmental, contractual, reliability,quality, and safety requirements and forming them into top level system requirementsand design, subsystem requirements, and interface definitions. It includes systemoptimization and trade studies as well as risk mitigation.

1.1.2.1 System Engineering Management L3 Lead: Randall Iliff

Activity associated with the planning and conduct of the overall system engineeringeffort for the IceCube project, exclusive of EHWD related tasking.

1.1.2.1.1 System Engineering Management Plan L3 Lead: Randall IliffUpdate

The System Engineering Management Plan forms the basis for all SE activity on theproject, and requires periodic review and appropriate changes in order to remaineffective.

1.1.2.1.2 PDR/CR Review Activities L3 Lead: Randall Iliff

Preliminary and Critical Design Reviews will be conducted for each Configuration Itemidentified on the project. Duration and formality of the each review will be proportional to the CI content complexity and project risk exposure, and will vary significantly from CI to CI.



1.1.2.1.3 Meetings and Coordination L3 Lead: Randall Iliff

Periodic coordination is essential to establish and maintain an effective SE program.This task covers internal UW-Madison coordination, Technical Board meetings,Collaboration Board Meetings, NSF Project Review support, and periodic SE specificsite visits as required.

1.1.2.2 Software Coordination L3 Lead: Randall Iliff

Activity associated with the planning and conduct of the overall software coordinationeffort for the IceCube project, exclusive of EHWD related tasking.

1.1.2.2.1 Software Development Plan Update L3 Lead: Randall Iliff

The Software Development Plan forms the basis for all software activity on theproject, and requires periodic review and appropriate changes in order to remaineffective.

1.1.2.2.2 PDR/CDR Review Activities L3 Lead: Randall Iliff

Preliminary and Critical Design Reviews will be conducted for each SoftwareConfiguration Item identified on the project. Duration and formality of the each review will be proportional to the CI content complexity and project risk exposure, and willvary significantly from CI to CI.

1.1.2.2.3 Meetings and Coordination L3 Lead: Randall Iliff

Periodic coordination is essential to establish and maintain an effective softwaredevelopment program. This task covers internal UW-Madison coordination, TechnicalBoard meetings, Collaboration Board Meetings, NSF Project Review support, andperiodic SE specific site visits as required.

1.1.2.2.4 DAQ Development and Coordination L3 Lead: Randall Iliff

Level of effort coordination support for DAQ related development activity.

1.1.2.2.5 Data System Development Coordination L3 Lead: Randall Iliff

Level of effort coordination support for Data System related development activity.

1.1.2.2.6 Science Operations Coordination L3 Lead: Randall Iliff

Level of effort coordination support for Science Operations related developmentactivity.

1.1.2.2.7 Software Integration L3 Lead: Randall Iliff

Level of effort support for planning and coordination of the Software Integrationactivity across IceCube.

1.1.2.3 Interface Control L3 Lead: Randall Iliff

Identification of key system level interfaces, review and approval of interfacedocumentation and products.



1.1.2.3.1 System Level Documentation L3 Lead: Randall Iliff

Finalize / update and maintain system level interface definitions and ICD status.

1.1.2.3.2 ICD Coordination, Review and Approval L3 Lead: Randall Iliff

Ongoing review and coordination of project ICD traffic.

1.1.2.4 Requirements & Specifications L3 Lead: Randall Iliff

Effort associated with the establishment and update of system level EngineeringRequirements, including production and maintenance of the system level EngineeringRequirements Document (ERD) as well as coordination support for lower level ERDproducts.

1.1.2.4.1 SERD Updates L3 Lead: Randall Iliff

The SERD forms the basis for all subordinate requirements traceability on the project,and requires periodic review and appropriate changes in order to remain effective.

1.1.2.4.2 Requirements/Specifications Coordination, L3 Lead: Randall Iliff Review and Approval

Ongoing review and coordination of project Requirements and Specifications.

1.1.2.4.3 Requirements Authoring Support L3 Lead: Randall Iliff

Provides limited assistance and "ghost-writing" for requirements generated at lowerlevels.

1.1.2.5 System Integration & Test L3 Lead: Randall Iliff

Effort associated with the establishment, management, and conduct of integrationtests on the IceCube project.

1.1.2.5.1 Test Management L3 Lead: Randall Iliff

Responsible for test planning, coordination, review of procedures and test conduct inconjunction with Quality and the Systems Engineering Manager.

1.1.2.5.2 Test Planning L3 Lead: Randall Iliff

High level support for verification and integration testing effort.

1.1.2.5.3 Review of Test Procedures L3 Lead: Randall Iliff

Review of test procedures for consistency with requirements, suitability of methodsand definition of testing activities.

1.1.2.5.4 Test Participation L3 Lead: Randall Iliff

Limited support for observation / coordination of key test activities.



1.1.2.5.5 System Modeling and Simulation L3 Lead: Randall Iliff

Provides for establishment of Monte Carlo simulation modeling tool set associated with verification of system timing, error budget, reliability, and other aspects, which mustbe confirmed by analysis prior to system deployment. (This is not a duplication of thesensor simulation effort.)

1.1.2.6 Risk Assessment & Mitigation L3 Lead: Randall Iliff

Effort associated with the identification and control of project risk.

1.1.2.6.1 Assessment L3 Lead: Randall Iliff

Analysis activities performed to identify and characterize risk.

1.1.2.6.2 Mitigation Planning and Tracking L3 Lead: Randall Iliff

Response to identified risks, including determination of risk mitigation methods andassociated tracking through closure.

1.1.2.7 Engineering Support L3 Lead: Randall Iliff

General engineering support on an as-needed basis across all project elements.

1.1.2.7.1 Electrical L3 Lead: Randall Iliff

Level of effort electrical engineering support to other WBS 1.1.2 tasks.

1.1.2.7.2 Mechanical L3 Lead: Randall Iliff

Level of effort mechanical engineering support to other WBS 1.1.2 tasks.

1.1.2.7.3 Software L3 Lead: Randall Iliff

Level of effort software engineering support to other WBS 1.1.2 tasks.


IceCube WBS Dictionary 1.2 Implementation

1.2 Implementation L3 Lead:

Implementation is responsible for providing the logistical, drilling, and installation ofinstruments needed to construct a detector consisting of 80 elements buried up to 2.5 kilometers deep in the ice at the South Pole.

1.2.1 Logistics L3 Lead: Terry Hannaford

Level of Effort Activities (no WBS breakdown below Level 3): Provide logistical support to all areas involved in the movement of personnel and equipment to and from thejob site. Prepare documentation and associated plans to reduce risk and minimizedelays in shipping while ensuring all governing documents and international rules arefully evaluated and implemented. Prepare drilling, deployment and commissioningteams for field seasons. Maintain lists of deployment personnel to facilitate andenhance use of billeting for maximum support of site operations. Organize and trackcargo shipments to and from the site maintaining methods of shipment and arrivaldates at points of entry to facilitate and provide expedient delivery to site foroperational support. Assure laboratory and communications requirements are met atthe site. Work closely with NSF and RPS in defining space, power, and communications requirements for all IceCube facilities at the South Pole. Evaluate the needs foradditional contractor supplied science technicians a well as suggest electronics and test equipment to be used in a general laboratory setting.

1.2.2 Drilling L3 Lead: Mark Mulligan

This element includes all activities related to drilling - specification, design, fabrication,construction, test, and operation - and all of its associated subsystems (controlsystem, hose/plumbing, heating, and tower operations). It includes both at theUniversity of Wisconsin and at South Pole. Major Deliverables: 1. (2) Drill Heads 2.(2) Tail Loggers 3. System Spares 4. System at South Pole: Drill Supply Hose Reeland Tower-01 5. Control system software updates.

1.2.2.1 Drilling Management L3 Lead: Mark Mulligan

This element includes the annual oversight, planning, and reporting for the EnhancedHot Water Drill; the system level design decision-making; the development andmaintenance of system level planning, operational, and testing documents; and thecompliance with all applicable safety requirements. Deliverables: 1. Quarterly Reports 2. Detailed Seasonal Plan

1.2.2.2 Enhanced Hot Water Drill Development L3 Lead: Mark Mulligan

These level five elements are not active after the deliverables are made for PY01.

1.2.2.2.7 Integration & Testing L3 Lead: Mark Mulligan

This elements includes the PY03 costs to complete the integration, verification, andtesting fo the EWHD system.



1.2.2.3 Drill Control System Maintenance L3 Lead: Mark Mulligan

This element includes all activities related to maintenance of the drilling control system, both software and hardware. This includes the control algorithms, system operations,operating system maintenance, computer hardware,RS-485 network, Ethernetnetwork, E-stop network, system sensors (temperature, pressure, flow, andenvironmental), and the drill control center. During PY02, activities will focus oncontinued software and algorithm development, developing a system simulator, andcontinued environmental testing. Deliverables: 1. System simulator 2. Controlsystem software updates 3. Environmental Testing Report

1.2.2.3.1 Software L3 Lead: Mark Mulligan

The Software element includes the effort to develop and maintain the control systemalgorithms, the system operations and manuals, and the operating system software. A few drill algorithms will be developed in PY02 and maintenance and adjusting of thealgorithms will occur throughout the entire drilling period. An operations manual will bedeveloped based on the control software. During PY02, further development will bemade to complete the entire control system software. Completing and maintaining itwill occur of the entire drilling period.

1.2.2.3.2 Hardware L3 Lead: Mark Mulligan

The Hardware element includes all efforts to maintain the system computers, the RS-485 network, the Ethernet network, the e-stop network, the system I/O, and the DrillControl Center (DCC) Mobile Drilling Structure (MDS). Maintenance will include a review and evaluation of the system performance following each season, developing andimplementing changes to the system, and the purchase of spare components for thesystem computers, network panels (e-stop and RS-485), sensors, actuators and DCC equipment.

1.2.2.4 Electrical Power Distribution Maintenance L3 Lead: Mark Mulligan

This element includes all activities related to maintenance of the electrical powerdistribution in the system. This includes the generators, motors, drives, electrical feeder cable, panels, uninterruptible power supplies, and general electrical equipment (wiring,electric heaters, lights, and transformers). During PY02, activities will focus onsupporting RPSC and the generator vendor during the fabrication and testing of thesecond and third generators. This includes installing a third switch gear in the powerdistribution unit. Additional work will focus on the selection and procurement of spares.

1.2.2.4.1 Generator L3 Lead: Mark Mulligan

The generator element includes the testing and checkout support of units two andthree. It also includes all maintenance of the system or support of RPSC maintenanceof the system between field seasons.



1.2.2.4.2 Motors L3 Lead: Mark Mulligan

The motor element includes all efforts to maintain the system motors. This includesthe motors on all pumps, hose reels, cable reels, cable winches, and hoists. It includeswork to maintain motors between field seasons and the purchase and testing of sparemotors.

1.2.2.4.3 Drives L3 Lead: Mark Mulligan

The drives element includes all efforts to maintain the system drives. This includes themotor drives on all pumps, hose reels, cable reels, cable winches, and hoists. Itincludes work to maintain drives between field seasons, reprogramming, and thepurchase and testing of spare motor drives.

1.2.2.4.4 Feeder Cable L3 Lead: Mark Mulligan

The feeder cable element includes all efforts to maintain the system feeder cable andconnectors (on both the cable and the Mobile Drilling Structures (MDS)). This includesall power delivery cables to and between the MDSs, hose reels, cable reels, cablewinches, generators, and the power distribution module. It includes work to maintainthe feeder cable and connectors between seasons and the purchase and testing ofspare and replacement feeder cables and connectors.

1.2.2.4.5 Panels L3 Lead: Mark Mulligan

The panel element includes all efforts to maintain the system single and three phasepower panels. This includes all single and three phase panels in the Mobile DrillingStructures. It includes work to maintain the panels between seasons and the purchaseand testing of spare and replacement panel components.

1.2.2.4.6 Uninterruptible Power Supplies L3 Lead: Mark Mulligan

The Uninterruptible Power Supply (UPS) element includes all efforts to maintain thesystem UPSs. This includes the UPSs in the Drill Control Center and Tower OperationsStructure 1 and 2. It includes work to maintain UPSs between field seasons and thepurchase and testing of spare UPSs.

1.2.2.4.7 General Equipment L3 Lead: Mark Mulligan

The general equipment element includes all efforts to maintain general equipment inthe system. This includes the wiring, back-up electric heaters, lights, and transformers. It includes work to maintain the equipment and the purchase and testing of spare orreplacement equipment.

1.2.2.5 Hose/Plumbing System Maintenance L3 Lead: Mark Mulligan

This element includes all maintenance of the system plumbing for both water and fuel.This includes the High Pressure Pumps, Rodriguez Well System, Seasonal EquipmentWorkshop, and Water Tank MDS; the Drill Supply Hose Reel, the fuel tower anddistribution, the return water system and the system hoses. During PY02, activities will focus on the selection and procurement of system spares. It may also include theselection of additional equipment, components , or tools for the Seasonal EquipmentWorkshop Deliverables: 1. Hose / plumbing system spares.



1.2.2.5.1 High Pressure Pump House L3 Lead: Mark Mulligan

The High Pressure Pump (HPP) House element includes all efforts to maintain the HPP.This includes the maintenance of the pumps, belts, pulleys, plumbing fittings, furnace,ductwork, ventilation system, building structure and all other hardware excludinghardware defined in elements 1.2.2.3 and 1.2.2.4 that may be physically located in the HPP. It includes work to maintain the equipment and the purchase and testing ofspare or replacement equipment.

1.2.2.5.2 Rodriguez Well System L3 Lead: Mark Mulligan

The Rodriguez Well System (RWS) element includes all efforts to maintain the RWS.This includes the maintenance of the small heaters, pumps internal to the RWS, theRodriguez Well Reel, the Rodriguez Well pump, plumbing fittings, furnace, ductwork,ventilation system, building structure and all other hardware excluding hardwaredefined in elements 1.2.2.3 and 1.2.2.4 that may be physically located in the RWS. Itincludes work to maintain the equipment and the purchase and testing of spare orreplacement equipment.

1.2.2.5.3 Seasonal Equipment Workshop L3 Lead: Mark Mulligan

The Seasonal Equipment Workshop (SEW) element includes all efforts to maintain theSEW. This includes the maintenance all hardware housed or stored in the SEW excepthardware defined in elements 1.2.2.3 and 1.2.2.4 that may be physically located in the SEW. It includes work to maintain the equipment and the purchase and testing ofspare or replacement equipment.

1.2.2.5.4 Water Tanks L3 Lead: Mark Mulligan

The Water Tanks (WT1 & WT2) element includes all efforts to maintain WT1 and WT2.This includes the maintenance of the charge pumps, transfer pumps, cover plates,plumbing components, railings, hoists, stairs, liner, and building structure It excludeshardware defined in elements 1.2.2.3 and 1.2.2.4 that may be physically located in the WT1 and WT2. It includes work to maintain the equipment and the purchase andtesting of spare or replacement equipment.

1.2.2.5.5 Drill Supply Hose Reel L3 Lead: Mark Mulligan

The Drill Supply Hose Reel (DSHR) element includes all efforts to maintain the DSHR.This includes the maintenance of the reel, level wind, enclosure, and plumbingcomponents mounted to the structure. It excludes hardware defined in elements1.2.2.3 and 1.2.2.4 that may be physically located on the DSHR. It includes work tomaintain the equipment and the purchase and testing of spare or replacementequipment.

1.2.2.5.6 Return Water System L3 Lead: Mark Mulligan

The return water system element includes the maintenance of the return water hosereel, the return water pump, and the return water pump cable reel. It excludeshardware defined in elements 1.2.2.3 and 1.2.2.4 that may be physically located onthis equipment. It includes work to maintain the equipment and the purchase andtesting of spare or replacement equipment.



1.2.2.5.7 Hoses L3 Lead: Mark Mulligan

The hoses elements includes all efforts to maintain system hoses. This includes the drill supply hose, the Rodriguez Well hose, hoses internal to the Mobile Drilling Structures(MDSs), hoses between MDSs, hose crimping equipment, and hose couplings. Itincludes work to maintain the equipment and the purchase and testing of spare orreplacement equipment.

1.2.2.5.8 Fuel Distribution System L3 Lead: Mark Mulligan

The fuel distribution element includes all efforts to maintain system fuel delivery. Thisincludes the fuel tower, fuel pumps, plumbing components, and fuel hoses. It includeswork to maintain the equipment and the purchase and testing of spare or replacement equipment.

1.2.2.6 Heating System Maintenance L3 Lead: Mark Mulligan

This element includes all maintenance of the heating system beyond the needs of theRodriguez Well. This includes the Pre-Heater System and Main Heating Plant MDS andall of the associated hardware inside them.

1.2.2.6.1 Main Heating Plants L3 Lead: Mark Mulligan

The Main Heating Plants (MHP) element includes all efforts to maintain the MHPs. Thisincludes the large heaters, furnace, ductwork, plumbing fittings, ventilation system,building structure and all other hardware excluding hardware defined in elements1.2.2.3 and 1.2.2.4 that may be physically located in the MHPs. It includes work tomaintain the equipment and the purchase and testing of spare or replacementequipment.

1.2.2.6.2 PreHeat System L3 Lead: Mark Mulligan

The PreHeat System (PHS) element includes all efforts to maintain the PHS. Thisincludes the large heaters, small heaters, furnace, ductwork, plumbing fittings,ventilation system, building structure and all other hardware excluding hardwaredefined in elements 1.2.2.3 and 1.2.2.4 that may be physically located in the MHPs. Itincludes work to maintain the equipment and the purchase and testing of spare orreplacement equipment.

1.2.2.7 Tower Operations Site Maintenance L3 Lead: Mark Mulligan

This element includes all maintenance of the system hardware that moves from holeto hole. Activities will focus on fabrication and test of (2) drill heads; the specification,design, fabrication, and test of (2) drill head tail loggers; and the selection &procurement of tower operations spares. Deliverables: 1. (2) Drill Heads 2. (2) TailLoggers 3. Tower Operations spares

1.2.2.7.1 Tower Operations Structure 1 L3 Lead: Mark Mulligan

The Tower Operations Structure (TOS1) element includes all efforts to maintain TOS1.This includes the firn drill, furnace, ductwork, ventilation system, building structure andall other hardware excluding hardware defined in elements 1.2.2.3 and 1.2.2.4 thatmay be physically located in TOS1. It includes work to maintain the equipment and thepurchase and testing of spare or replacement equipment.



1.2.2.7.2 Tower Operations Structure 1 Tower L3 Lead: Mark Mulligan

The Tower Operations Structure 1 (TOS1) Tower element includes all efforts tomaintain the tower. This includes the tower structure, lower level enclosure, hosecrescent, cable crescent, sheaves and tower hoist. It includes work to maintain theequipment and the purchase and testing of spare or replacement equipment.

1.2.2.7.3 Drill Head System L3 Lead: Mark Mulligan

The drill head system element includes efforts to maintain the drill head, support cable,support cable reel, and the drill head slip assembly. It includes work to maintain theequipment and the purchase and testing of spare or replacement equipment.

1.2.2.7.4 Auto Banding System L3 Lead: Mark Mulligan

The auto banding system element includes effort to maintain the autobander. Thisincludes the maintenance of the hardware between seasons, modifying the systemsoftware, and the purchase and testing of spare or replacement equipment.

1.2.2.7.5 Deployment Winch L3 Lead: Mark Mulligan

The deployment winch element includes efforts to maintain the deployment winchbetween field seasons and the purchase and testing of spare or replacementequipment. It excludes hardware defined in elements 1.2.2.3 and 1.2.2.4 that may bephysically located on the deployment winch.

1.2.2.7.6 IceTop Water Supply L3 Lead: Mark Mulligan

The IceTop Water Supply elements includes efforts to plan, implement, and modify thesystem for supply water for the IceTop water tanks. It includes the purchase of anyequipment specific to this effort, the maintenance of the equipment, and equipmentspares.

1.2.2.8 Field Seasons L3 Lead: Mark Mulligan

This elements is for all activities at the South Pole. It is confined to the travel and laborof individuals going to the South Pole and the cost of the process to medically clearthem. It should also include time to prepare a post-season report after returning toCONUS. PY03 season activities include assembling the Drill Supply Hose Reel,assembling tower-01, spooling hose on to the Drill Supply Hose Reel, placing MDS onto sleds, and examining the status of all equipment arriving at the South Pole.Deliverables: 1. Assembled Drill Supply Hose Reel 2. Assembled Tower-01 3. Spooledhose on the Drill Supply Hose Reel 4. MDS at South Pole on sleds 5. FY04 SeasonalReport



1.2.3 Deployment L3 Lead: Bob Morse

Installation consists of placing 2.5 km long strings of detectors into holes drilled in theice. Each string will be approximately 2.5 kilometers in length with 60 optical modulesattached, one module every 17 meters. The installation teams will be responsible forattaching the detector modules to the cables, lowering the array into a water filledhole, collecting data and ensuring that the modules are operational. The array will then be connected to computers for data collection and made available to the collaboration for analysis.

1.2.3.1 Deployment Management L3 Lead: Bob Morse

This element includes the annual oversight, planning and reporting for the OpticalStrings Deployment Program, which includes the system level design decision-making,the development and maintenance of the system level planning, operational, and thecompliance with all applicable safety requirements. Deliverables: 1. Quarterly Reports, 2. Detailed FY-05 3. Out-year Seasonal Plans.

1.2.3.2 System Design L3 Lead: Bob Morse

This element includes all activities related to deployment-specification, design,fabrication, construction, test, and operation, and all the associated subsystems(control systems, cable-reels, tower operations, monitoring of OMs). It includes bothat the University of Wisconsin and at South Pole (in cooperation with RPSC) majordeliverables such as: cable-reels, system spares, control and monitoring systemshardware, electronics, and software.

1.2.3.3 Field Season Operations L3 Lead: Bob Morse

For the FY-05 season activities include cable spooling from the Tulsa PO-20 payoutdevices, use of the drilling towers for deployment activities, installing the electronicsneeded to actively readout the Paro and Keller Devices as they are being deployeddown the holes. The installation of the IceTop tanks, the trenching of cable routes, and the laying in of signal and power cables.

1.2.4 Project/Technical Management L3 Lead: Bob Morse

This element includes all the labor and travel for the technical oversight andmanagement of Implementation. It includes a travel budget to support strategy andplanning meetings within the collaboration and with RPSC & and the NSF.


IceCube WBS Dictionary 1.3 Instrumentation

1.3 Instrumentation L3 Lead:

Instrumentation is responsible for designing and assembling the detector and it's major components, In-Ice Devices, IceTop, Data Acquisition Hardware, and Data AcquisitionSoftware. This includes in the Level 3 category In-Ice Devices the construction ormore than 5000 Optical sensors (Digital Optical Modules, short DOMs) and cablessystems to form 80 strings. The optical sensors are built and tested to verify that theperformance meets the requirements of the instrument. The surface detectorcomponent IceTop requires the production of 160 tanks of 2 m diameter and specificengineering required ti integrate this detector component into the combined IceCubedetector system. The data acquisition for all optical sensors both on the strings and in the tanks includes hardware and software to operate the optical sensors and readoutthe data. The data acquisition includes software on the optical sensor as well as in anarray of about 100 computers loaded with specialized hardware to communicate withthe DOMs, readout all data, form a trigger and build events. The instrumentationsystem delivers calibrated events for further processing in the Level 2 area 1.4 datasystems.Instrumentation does not include the shipping and installation of the strings in the ice,task performed by the L2 area Logistics

1.3.1 In-Ice Devices L3 Lead: Kael Hanson

In-ice Devices includes the design, purchase, assembly, and test of all components and systems for the optical modules, cables, and the IceTop array.

1.3.1.1 Optical Modules L3 Lead: Kael Hanson

These elements include the design, fabrication and test of the optical modulecomponents.

1.3.1.1.1 Optical Module Layout & Design L3 Lead: Kael Hanson

The labor required to layout the overall technical design of the optical module includingthe structural design of the Å-metal shield and the possible design of the wavelengthshifter.

1.3.1.1.2 Flasher Board Design & Production L3 Lead: Kael Hanson

The labor, materials and capital equipment purchases required to design, fabricate, and quality test the flasher board for all optical modules.

1.3.1.1.3 PMT Baseboard Design & Production L3 Lead: Kael Hanson

The labor, materials and capital equipment purchases required to design, fabricate, and quality test the photo-multiplier tube base board for all optical modules.

1.3.1.1.4 Photo-Multiplier Tube L3 Lead: Kael Hanson

The labor and capital equipment purchases required to spec, order, and quality checkupon receipt the photo-multiplier tubes.

1.3.1.1.5 Pressure Vessel L3 Lead: Kael Hanson

The labor and capital equipment purchases required to spec, order, and quality checkupon receipt the pressure vessels.



1.3.1.1.6 Delay Board L3 Lead: Kael Hanson

The labor and capital equipment purchases required to spec, order, and quality checkupon receipt the Delay Boards.

1.3.1.1.7 Connector L3 Lead: Kael Hanson

The labor and capital equipment purchases required to spec, order, and quality checkupon receipt the optical module connectors.

1.3.1.1.8 Magnetic Shield L3 Lead: Kael Hanson

The labor and capital equipment purchases required to spec, order, and quality checkupon receipt the Å-metal magnetic shields.

1.3.1.1.9 Mechanical Harness L3 Lead: Kael Hanson

The labor required to spec, order, and quality check upon receipt the mechanicalharness for the optical modules.

1.3.1.1.10 Optical Module Production L3 Lead: Kael Hanson

The labor, materials and capital equipment to fabricate and assembly the opticalmodules at the three production facilities (University of Wisconsin, DESY, and theUniversity of Stockholm). In addition, this element includes the purchase of shippingcontainers and the expense of shipping the optical modules to Port Hueneme.

1.3.1.1.11 Quality Assurance, Calibration & Testing L3 Lead: Kael Hanson

The labor, material, and capital equipment required to calibrate and test all opticalmodules following production. Calibration and testing will occur at each productionfacility (University of Wisconsin, DESY, and University of Stockholm).

1.3.1.2 Cables L3 Lead: Kael Hanson

These elements include the design, specification, purchase, and quality testing of thecables and harnesses required to deploy the optical modules and the cable to connectthe optical module string to the counting house.

1.3.1.2.1 Main Cables L3 Lead: Kael Hanson

The labor and capital equipment required to design, spec, order and quality check upon receipt the deployment main cables and main cable breakouts. In addition, theelement includes the purchase and testing of cable from various vendors prior to finalvendor selection and the expense of shipping the cable hardware to Port Hueneme.

1.3.1.2.2 String Hardware L3 Lead: Kael Hanson

The labor, material, and capital equipment required to design, spec, order and qualitycheck upon receipt the octopus wire harness, deployment chains, cable weights, cablestops, and miscellaneous cable hardware. In addition, this element includes theexpense of shipping the string hardware to Port Hueneme.



1.3.1.2.3 Special Devices L3 Lead: Kael Hanson

The labor and material required to spec, order and quality check upon receipt thetemperature sensors, pressure sensors, light sources, and miscellaneous materials and supplies. In addition, this element includes the expense of shipping the string hardware to Port Hueneme.

1.3.1.2.4 Quality Assurance L3 Lead: Kael Hanson

The labor and materials required to test and checkout the cable assemblies prior toshipment to Port Hueneme.

1.3.1.3 In-Ice Management L3 Lead: Kael Hanson

Manage the design, production, testing, and shipping of In-Ice Devices.

1.3.2 IceTop L3 Lead: Tom Gaisser

IceTop is the surface component of IceCube. By detecting cosmic-ray showers incoincidence with the deep detector it provides certain unique calibration and vetofunctions for neutrino astronomy in addition to permitting IceCube to function as athree-dimensional air shower array for study of cosmic-ray astrophysics up to EeVenergies.

1.3.2.1 Tanks L3 Lead: Tom Gaisser

Design and build tanks; design and test deployment and freezing procedures toprovide working ice-Cherenkov detectors for the surface array component of IceCube. Exclusion: Provision of water to fill the tanks is excluded because it will be an integralpart of deployment (see 1.2.3.3.4 under 1.2.3.3 Field Season Operations). There isalso a need for coordination with drilling (1.2.2) in connection with water supply. Tankdeployment is under 1.2.

1.3.2.2 Cables L3 Lead: Tom Gaisser

Specification of cabling to power and monitor freezing, testing and operation of tanks.Exclusion: Cabling for tank DOMs should be included in the main surface cables(1.3.1.2). Conductors suitable for monitoring the tanks and for providing powerduring deployment will be provided under 1.3.1.2. Connections from the DOMs to the surface cables must be provided, as well as cables connecting the DOMs to eachother, also under 1.3.1.2.

1.3.2.3 Optical Modules L3 Lead: Tom Gaisser

Develop final acceptance test and verification procedures for IceTop DOMs. Designand produce fixtures for mounting DOMs in tanks. Construction of DOMs is excludedbecause the DOMs for IceTop will be part of DOM production runs (1.3.1.1). Design ofmodifications that may be needed for IceTop will be carried out in collaboration with1.3.3 and 1.3.4 as part of IceTop specific engineering (1.3.2.4).



1.3.2.4 IceTop Specific Engineering L3 Lead: Tom Gaisser

Design, Maintenance, calibration and operation of the surface component of IceCubeto the extent that these require special procedures. IceTop is an integral componentof the IceCube detector. To a large extent, both its hardware and softwarecomponents are similar, if not identical, to those of the deep detector. This elementincludes integration of air shower detector calibration, DAQ, trigger, reconstruction and simulation into the corresponding IceCube processes.

1.3.2.4.1 Engineering Resources L3 Lead: Tom Gaisser

Develop engineering resources necessary for the design, _construction, calibration,commissioning and verification, of IceTop components. This includes an IceTopinstrumentation and development facility and a tank test station on campus at theUniversity of Delaware, a tank test station at UW River Falls, mobile test tanks and atank test station at the South Pole Air Shower Experiment (SPASE).

1.3.2.4.2 IceTop Detector Simulations L3 Lead: Tom Gaisser

Develop simulations needed for IceTop design, calibration, commissioning andverification. Develop air shower simulations of common interest for IceTop and forsimulation of backgrounds in the deep detector (in coordination with WBS 1.4.3). Forexample, simulations of tank response and of the surface array trigger are in this WBSelement, while simulations for generating backgrounds in the deep detector are under1.4.3.1.

1.3.2.4.3 Data Acquisition L3 Lead: Tom Gaisser

Design, specify and produce IceTop-specific DAQ firmware and software components,including triggering and feature extraction algorithms in the onboard FPGA. Specifyrequirements for IceTop mainboards, including any variations from mainboards to beused in ice. Specify requirements for including surface data in IceCube data handlingand filtering procedures. Coordinate with related activities in WBS elements 1.3.3,1.3.4 and 1.4.

1.3.2.5 Integration of SPASE L3 Lead: Tom Gaisser

Maintenance and operation of the existing SPASE air shower detector to the extent itremains useful as a calibration device for IceCube.

1.3.2.6 IceTop Management L3 Lead: Tom Gaisser

Local project monitoring and reporting to project office.

1.3.3 Data Acquisition Hardware L3 Lead: Dave Nygren

Data Acquisition (DAQ) Hardware development and production. Primary deliverablesinclude DOM Main Boards (DOMMB) and DOM Hub including DOR and DSB cards

1.3.3.1 Design L3 Lead: Dave Nygren

DAQ Hardware Design including Firmware but not Software.



1.3.3.1.1 System Architecture L3 Lead: Dave Nygren

Evaluation of technical benefits, risks, and tradeoffs of reasonable alternative systemarchitectures based on analog/digital & electrical/optical communication paths; analysis of performance degradation, failure and SPF modes, stability, calibration, networkbehavior, and interfaces; analysis of mutual impact of hardware and software design.Documentation of technical path and justifications. Design review process.

1.3.3.1.2 System Design L3 Lead: Dave Nygren

Detailed design at block level, timing, data flows, simulations; interfaces frozen andwell documented; hardware architecture integrated into block level design.

1.3.3.1.3 Reliability and Q/A Design L3 Lead: Dave Nygren

Development of Q/A plan and management Production engineering for enhancedreliability of hardware to be deployed in-ice

1.3.3.1.4 Main PCB Design L3 Lead: Dave Nygren

Design of DOMMB pcb including parts selection for reliability and firmware.

1.3.3.1.5 DOM Hub Design L3 Lead: Dave Nygren

Design of DOM HUB including DOR pcb card including parts selection for reliability andfirmware

1.3.3.1.6 Power & Slow Controls Design L3 Lead: Dave Nygren

Interface to experiment control; Firmware for fault detection, alarm processing;protection and shutdown, message handling, power conditioning and control.

1.3.3.1.7 Calibration and Monitoring Design L3 Lead: Dave Nygren

Calibration firmware integrated into the design to permit on-demand,foreground/background operation of calibration of both dynamic and staticcalibrations, without impact on normal data acquisition for dynamic variables such astiming stability.

1.3.3.1.8 Post-Deployment Commissioning Design L3 Lead: Dave Nygren

Design for commissioning after string deployment. Commissioning of electronic chainwill commence immediately, and require little or no operator intervention on-site; allfeatures and functions can be remotely tested and exercised. System must be able to function during drilling.

1.3.3.2 Prototype Development and System Test L3 Lead: Dave Nygren

Prototype Hardware design, fabrication and evaluation.

1.3.3.2.1 Design L3 Lead: Dave Nygren

Design of prototype DOM Main Board and DOR (hub) pcbs for evaluation anddevelopment. Conceptual framework for test, organization of site and logisticalsupport for test; definition of scope and goals for test. Design review process.



1.3.3.2.2 Fabrication L3 Lead: Dave Nygren

Fabrication of prototype boards, cables, etc, and construction of test bed facility.Purchases, QA, etc

1.3.3.2.3 Test & Evaluation L3 Lead: Dave Nygren

Execution of test plan, evaluation of results; modifications as indicated, with repeattesting as needed. Documentation of results. Design review process.

1.3.3.3 Hardware Production L3 Lead: Dave Nygren

Production of Hardware for deployment and for support

1.3.3.3.1 Purchasing & Warehousing L3 Lead: Dave Nygren

With approval for production, purchase of parts, components, and safe storage.

1.3.3.3.2 Main PCB Production L3 Lead: Dave Nygren

With approval for production, fabrication of DAQ hardware: Multiyear delivery of DOMMB

1.3.3.3.3 DOM Hub Production L3 Lead: Dave Nygren

With approval for production, fabrication of DAQ hardware: Multiyear delivery of DOMHUB hardware including DOR cards, DSB Card and PCI chassis.

1.3.3.3.4 Crates, Racks, & Power Supplies L3 Lead: Dave Nygren

All electrical, mechanical, cooling, hardware and interconnects needed to supportoperation of DAQ system.

1.3.3.3.5 String Processor Hardware L3 Lead: Dave Nygren

All computer hardware related to the string processors, including CPUs, disks,switches, racks and cables.

1.3.3.3.6 Event Builder/Global Trigger Hardware L3 Lead: Dave Nygren

All computer hardware related to the event builder and global trigger, including CPUs,disks, switches, racks and cables.

1.3.3.4 Testing and Shipping L3 Lead: Dave Nygren

Final q/a testing of DOM hardware prior to shipment for integration. Final q/a testingof other DAQ hardware prior to shipment for deployment. Shipping of hardware forintegration and deployment.

1.3.3.5 Commissioning/Onsite Installation L3 Lead: Dave Nygren

Setup of racks, crates, and DAQ subsystems and demonstrate plug & play capabilityafter transport to site. Support kits of portable test equipment.

1.3.3.6 DAQ Hardware Management L3 Lead: Dave Nygren

Management of DAQ Hardware development, fabrication and Q/A .



1.3.4 DAQ Software L3 Lead: Chuck McParland

Data Acquisition (DAQ) Software design, integration and production. Primarydeliverables include production testing system for DOM Main Boards (STF TestSystem), final production testing system for integrated optical modules (TestDAQ),and DAQ software system for data acquisition operations at the South Pole (initial, first year system and subsequent upgrades).

1.3.4.1 System Architecture L3 Lead: Chuck McParland

Conceptual design of IceCube DAQ software system covering all aspects of dataacquisition and handling starting with DOM Main Board software and terminating in thebuilding of events. Deliverables include: Set of documents that contain overalldescription, decomposition view and dependencies for each major DAQ softwarecomponent. Exclusions: Task: These documents, as of the end of this task, will not contain detailed implementation descriptions. Reason: Implementation details foreach DAQ software component will be added as part of the tasks associated withdelivering phased DAQ software releases.

1.3.4.1.1 IceCube DAQ System Requirements L3 Lead: Chuck McParland

Develop requirements for IceCube DAQ system architecture.

1.3.4.1.2 DAQ System Components Descriptions L3 Lead: Chuck McParland

Prepare initial descriptions of DAQ system software components and their interactionsand dependencies.

1.3.4.1.3 Update DAQ System Component L3 Lead: Chuck McParlandDescriptions

Update DAQ component descriptions and documentation for first DAQ deploymentsystem.

1.3.4.1.4 Finalize DAQ Component Descriptions L3 Lead: Chuck McParland

Update DAQ component descriptions and documents for final DAQ system.

1.3.4.2 Production Test Software Framework L3 Lead: Chuck McParland

This task covers the design, implementation and documentation of a software testingenvironment used for acceptance testing of electronics hardware manufactured foruse in conjunction with the IceCube DAQ system. In addition to development of theoverall

1.3.4.2.1 Test Framework L3 Lead: Chuck McParland

Design and implementation of test framework

1.3.4.2.2 Individual DOM Main Board tests L3 Lead: Chuck McParland

Specification and implementation of individual DOM Main Board tests



1.3.4.2.3 Test Framework User Interface L3 Lead: Chuck McParland

Design and implementation of test session user interface

1.3.4.2.4 Instrumentation Database L3 Lead: Chuck McParland

Instrumentation database interface design and implementation.

1.3.4.2.5 Component Integration L3 Lead: Chuck McParland

Component integration and testing of test environment.

1.3.4.3 DAQ System Monitoring and Control L3 Lead: Chuck McParland

This task includes definition of DAQ system operations and procedures as seen fromthe perspective of IceCube detector operations at the South Pole. It also includessoftware programs and mechanisms that allow both user-based (e.g. GUI) andprogrammatic

1.3.4.3.1 DAQ Control System Requirements. L3 Lead: Chuck McParland

Develop requirements for IceCube DAQ control software.

1.3.4.3.2 DAQ Control System L3 Lead: Chuck McParland

Design and document IceCube DAQ control system.

1.3.4.3.3 Test DAQ Control System L3 Lead: Chuck McParland

Develop and release limited DAQ control software for Test DAQ

1.3.4.3.4 Initial DAQ Control System L3 Lead: Chuck McParland

Develop and release limited DAQ control software for first deployment system.

1.3.4.3.5 Finalize DAQ Control System L3 Lead: Chuck McParland

Develop and release final DAQ control software.

1.3.4.3.6 DAQ Control System Integration and Test L3 Lead: Chuck McParland

Integrate and test final release of DAQ control software with experiment controlsupervisory program

1.3.4.3.7 DAQ Monitoring Requirements L3 Lead: Chuck McParland

Develop requirements for IceCube DAQ monitoring software.

1.3.4.3.8 DAQ Monitoring System L3 Lead: Chuck McParland

Design and document IceCube DAQ monitoring system.

1.3.4.3.9 Initial DAQ Monitoring System L3 Lead: Chuck McParland

Develop and release limited DAQ monitoring software for first deployment system.



1.3.4.3.10 Finalize DAQ Monitoring Software L3 Lead: Chuck McParland

Develop and release final DAQ monitoring software.

1.3.4.4 DAQ Test and Integration Test-bed L3 Lead: Chuck McParland

DAQ software system development will be phased over at least three major releaseconfigurations. Each of these releases must be tested and validated, to the extentpossible, prior to installation at the South Pole. While the integration activities invol

1.3.4.4.1 Network Infrastructure L3 Lead: Chuck McParland

Specify required processors and network infrastructure.

1.3.4.4.2 System Purchase L3 Lead: Chuck McParland

Delivery and installation of processors and networking equipment

1.3.4.4.3 System Installation L3 Lead: Chuck McParland

Specify and install Linux OS software environment compatible with that proposed forSouth Pole installation.

1.3.4.5 First Production (Test DAQ) Test System L3 Lead: Chuck McParland

We will need to thoroughly test prototype and first production DOMs beforecommitting to their full-scale production. Although initial single DOM testing will beaccomplished using tools produced under WBS 1.3.4.2, their design cannot be released for ful

1.3.4.5.1 Test DAQ System Requirements L3 Lead: Chuck McParland

Develop requirements for Test DAQ system.

1.3.4.5.2 Initial DOM MB Software L3 Lead: Chuck McParland

Develop and release initial version of DOM MB data taking software

1.3.4.5.3 Initial DOM Hub Software L3 Lead: Chuck McParland

Develop and release initial version of DOM Hub software.

1.3.4.5.4 Data Collector Software L3 Lead: Chuck McParland

Develop and release TestDAQ data collector software.

1.3.4.5.5 Data Visualization Software L3 Lead: Chuck McParland

Develop and release TestDAQ data visualization software.

1.3.4.5.6 IceTop Integration L3 Lead: Chuck McParland

Integration of IceTop DOMs and data structures into all TestDAQ software levels.



1.3.4.5.7 TestDAQ Integration Tests L3 Lead: Chuck McParland

Integrate and test all TestDAQ software components.

1.3.4.5.8 Preliminary DAQ Software Distribution L3 Lead: Chuck McParlandSystem

Develop preliminary system for distributing DAQ software to multiple sites.

1.3.4.6 First Deployment DAQ System L3 Lead: Chuck McParland

The first IceCube deployment will consist of a small number of strings. While we willneed to operate these strings to acquire engineering test data, we will also want tobegin using them to acquire physics data from what constitutes a small portion of th

1.3.4.6.1 First Deployment DAQ System L3 Lead: Chuck McParlandRequirements

Develop operational requirements for first deployment DAQ system.

1.3.4.6.2 DOM MB Software L3 Lead: Chuck McParland

Maintenance releases of DOM MB data taking software for both In-Ice and IceTopDOMs.

1.3.4.6.3 DOM Hub Software L3 Lead: Chuck McParland

Fully functional release initial version of DOM Hub software.

1.3.4.6.4 String Processor Software L3 Lead: Chuck McParland

Develop and release DAQ string processor software

1.3.4.6.5 Trigger Processor Software L3 Lead: Chuck McParland

Develop and release initial DAQ trigger processor software for In-Ice, IceTop and global trigger DAQ software components.

1.3.4.6.6 Event Builder Software L3 Lead: Chuck McParland

Develop and release initial DAQ event builder software.

1.3.4.6.7 Integration Tests L3 Lead: Chuck McParland

Integrate and test all DAQ first deployment software components.

1.3.4.6.8 Release of First Deployment DAQ Software L3 Lead: Chuck McParland

Release first deployment version of DAQ software deployment system.



1.3.4.7 Fully Deployed Detector DAQ System L3 Lead: Chuck McParland

At this point we will have a fully deployed IceCube detector with a full population ofboth In-Ice and Ice Top elements. All DAQ software components will be at their finaldesign release. Deliverables include: -Maintenance releases of DOM Main Boardsoftware for both In-Ice and Ice Top. -Final release of DOM Hub software. -Finalrelease of string processor software component. -Final release of trigger softwarecomponents including fully integrated In-Ice and Ice Top triggers. Also includes support for external triggers and coordination with Amanda DAQ data stream. -Final release of event builder software component.

1.3.4.7.1 Final Deployment DAQ System L3 Lead: Chuck McParland

Develop operational requirements for final deployment DAQ system.

1.3.4.7.2 DOM MB Software L3 Lead: Chuck McParland

Maintenance releases of DOM MB data taking software for both In-Ice and IceTopDOMs.

1.3.4.7.3 DOM Hub Software L3 Lead: Chuck McParland

Develop and release final version of DOM Hub software.

1.3.4.7.4 String Processor Software L3 Lead: Chuck McParland

Develop and release final version of DAQ string processor software

1.3.4.7.5 Trigger Processor Software L3 Lead: Chuck McParland

Develop and release final DAQ trigger processor software for In-Ice, IceTop and globaltrigger DAQ software components.

1.3.4.7.6 Event Builder Software L3 Lead: Chuck McParland

Develop Final Event Builder Software

1.3.4.7.7 Integration Tests L3 Lead: Chuck McParland

Develop Final Component Software

1.3.4.7.8 Release Final Deployment DAQ System L3 Lead: Chuck McParland

Release final version of DAQ software deployment system.

1.3.4.8 Software System Engineering Tasks L3 Lead: Chuck McParland

Successful accomplishment of tasks contained within the 1.3.4 WBS will requireadditional system level software engineering activities. They are collected here. Sincedeployment of the IceCube DAQ system will take place in well defined phases and since,

1.3.4.8.1 DAQ System Deployment Requirements L3 Lead: Chuck McParland

Develop requirements for DAQ system deployment covering initial DAQ deployment tofinal installed system.



1.3.4.8.2 DAQ System Deployment Plan L3 Lead: Chuck McParland

Write and distribute DAQ System Deployment Plan

1.3.4.8.3 DAQ String Integration Requirements L3 Lead: Chuck McParland

Develop preliminary DAQ requirements for string testing and integration after SouthPole deployment.

1.3.4.8.4 DAQ String Integration Plan Development L3 Lead: Chuck McParland

Write and distribute preliminary DAQ String Integration Plan.

1.3.4.8.5 DAQ String Integration Plan Review L3 Lead: Chuck McParland

Review string integration requirements and revise DAQ String Integration Plan forsubsequent South Pole deployments.

1.3.4.9 DAQ Software Management L3 Lead: Chuck McParland

Manage efforts at institutions contributing to DAQ software development. CoordinateDAQ software development schedule with IceCube project office. Coordinate DAQsoftware development plans with members of IceCube collaboration.

1.3.5 Project/Technical Management L3 Lead: Albrecht Karle

Management of Instrumentation development, production, testing, shipping, anddeployment.


IceCube WBS Dictionary 1.4 Data Systems

1.4 Data Systems L3 Lead:

Data Systems responsibilities consist of defining and incrementally developing andimplementing subsystems required to filter data, trigger and reconstruct neutrinoevents at the South Pole, locally archive raw and filtered data, and accomplish thesatellite transfer of filtered data from the South Pole to the Northern Hemisphere.Related tasks include the development and/or adaptation of simulation software tosupport detector commissioning and verification, the development of test software tosupport instrumentation development activities, and the development andimplementation of incremental data system functional and performance enhancements phased to meet the data quantity demands and operational requirements of theemerging full scale IceCube Neutrino Observatory.

1.4.1 Data Handling L3 Lead: Darryn Schneider

Data Handling comprises all equipment, software, and personnel necessary to movedata to and from the Processing and Filter function [WBS 1.4.2], archive the data,manage the Data Warehouse, and serve the data to the scientific users. Data Handlingwill also include transferring the data from the South Pole to the Northern hemisphere.Simulation data will also be stored and served.

1.4.1.1 South Pole Systems & Operation L3 Lead: Darryn Schneider

South Pole computer and networking hardware design, installation, and maintenance.Operation in normal running configuration of the computer systems, and software that comprise the surface systems of the IceCube detector at the South Pole.

1.4.1.1.1 South Pole Systems Hardware L3 Lead: Darryn Schneider

Design and implement South Pole hardware systems. Provide system managementincluding Operating System installation, and maintenance, and IceCube softwareinstallation management. Maintain standard operating procedures for the South Pole.

1.4.1.1.2 South Pole Test System L3 Lead: Darryn Schneider

Development work will be performed on a test system as similar as possible to theSouth Pole system. The test system will be located in the northern hemisphere, andclose to the DOM testing facility. After changes to a software or hardware are shownto be operationally ready on the test system, directions for installation by theoperators will be given - integration and verification testing.

1.4.1.1.3 South Pole Winter-Over Operation L3 Lead: Darryn Schneider

Operate South Pole hardware in standard operating modes. Includes training SouthPole operators and guidance during the austral winter months.

1.4.1.2 Data Transfer L3 Lead: Darryn Schneider

The production of 2 archives of data at the South Pole, one of all the data produced by the DAQ, and on-line filtering systems, the other of data required for operations, andof high scientific value. After archiving the former data is conditioned, and transferredfor high volume satellite transfer. These systems communicated to, and are invokedby experiment control. Design and implement network and security systems.



1.4.1.2.1 South Pole Data Movement and Archive L3 Lead: Darryn Schneider

Programs to control data movement from the output of the data filter to the interfaceof the satellite transfer system, and for making magnetic tape media archives of all the data.

1.4.1.2.2 South Pole Networking and IT Security L3 Lead: Darryn Schneider

Define IceCube data transfer, networking, and communications requirements to andfrom the South Pole. Ensure operational functionality of store/forward, TCP/IPnetworking, and voice communications systems. Implement private networks forSouth Pole technical computing. Maintain and monitor the security of IceCube SouthPole systems and networks.

1.4.1.3 Data Warehouse L3 Lead: Darryn Schneider

The definitive repository of IceCube data, including data acquired at the South Pole,and data produced during the simulation of the IceCube detector. Including the longterm storage, the data is documented, cataloged, and made easily available to theIceCube collaboration.

1.4.1.3.1 Data Administration and Documentation L3 Lead: Darryn Schneider

Provide tools for documenting data in the form of metadata, and associated metadata search and editing tools. Maintain the metadata standard used by IceCube. Maintainand implement data policy including access policy as specified by IceCube Collaboration Board.

1.4.1.3.2 Data Storage L3 Lead: Darryn Schneider

Provide an online storage facility for experimental and simulation data. Maintain anarchive of online data, and means of recovering archives, including the South Pole data archives.

1.4.1.3.3 Data Distribution L3 Lead: Darryn Schneider

Provide means of accessing data for both people (web interface), and for CPUresources. Programs for input of data from simulations and South Pole satellitetransfers into the data storage system.

1.4.1.4 Northern Hemisphere Resources L3 Lead: Darryn Schneider

For further analysis of data collected by the IceCube detector, and for the productionof simulation data, a core computing system will be maintained. To facilitate the useby the collaboration, and to maximize utilization, large computing resources will becoordinated, and connected through distributed computing techniques.

1.4.1.4.1 Computing Services L3 Lead: Darryn Schneider

Implement a computing environment available to all members of the IceCubecollaboration to enable IceCube detector simulation and data analysis. This will includeservices such as user account administration, issue resolution, and core infrastructure.



1.4.1.4.2 Central CPU Resource L3 Lead: Darryn Schneider

Maintain a CPU resource for analysis of experimental data, and for the production ofassociated simulation data.

1.4.1.4.3 Distributed CPU Resources L3 Lead: Darryn Schneider

Coordinate the connection of significant CPU resources in IceCube collaborationmember institutes into a distributed computing environment. Ensure access to CPUresources, such as national computing centers, needed to meet IceCube long termsimulation requirements. Implement distributed computing techniques for connectingIceCube and third party CPU resources and associated data distribution techniquesinterfaced to the IceCube data warehouse.

1.4.1.5 Data Handling Management L3 Lead: Darryn Schneider

Management of Data Handling subsystem.

1.4.2 Data Filtering and Software L3 Lead: Erik Blaufuss

Data Filtering and Software comprises all of the control software necessary to receivedata from the DAQ Event Builder, reconstruct the events, and test the reconstructeddata against filter criteria. The appended reconstruction and filter information will bepassed to a monitoring function.

1.4.2.1 South Pole Online Processing Software L3 Lead: Erik Blaufuss

South Pole online processing software receives data from the DAQ Event Builderwhence events are reconstructed and filtered on a scalable CPU farm. The results ofthe reconstruction are made available to monitoring and analysis software.

1.4.2.2 Production Processing Software L3 Lead: Erik Blaufuss

Production Processing Software comprises the control software for retrieving datafrom the Northern hemisphere data warehouse, reconstructing and filtering the events, and writing the events to output streams. The output streams are passed back to the data warehouse.

1.4.2.3 Database Design and Implementation L3 Lead: Erik Blaufuss

Database design and implementation provides databases and database tools for non-waveform data such as reconstruction constants and calibration constants.

1.4.2.4 Visualization Tools L3 Lead: Erik Blaufuss

Visualization tools will provide software for displaying events in three dimensions withtime-encoding. This function will also provide standard packages for plotting,histogramming, and fitting of data.



1.4.2.5 Software Management L3 Lead: Erik Blaufuss

Manage and coordinate all activities for Data Filtering and Software. Provide directionand oversight to ensure all requirements are met and conduct periodic reviews toensure all requirements and deliveries are proceeding as scheduled. Maintaincommunication with all levels of management preparing documentation as necessaryto accurately reflect performance.

1.4.3 Simulation L3 Lead: Klas Hultqvist

The principal function of Simulation is to prepare synthetic data corresponding tovarious physics processes relevant to IceCube to be used for software development,parametric studies, and understanding the detector response by comparison ofsimulated with real data.

1.4.3.1 Event Generation L3 Lead: Klas Hultqvist

Event generation models physical processes such as cosmic ray-induced air showersor neutrino interactions. It should include models for all processes of interest toIceCube, even including exotic objects such as monopoles or WIMPs. The output ofthe event generators include the species, energy, and directions of particles, whichcould be detected by the IceCube observatory, including Ice Top.

1.4.3.2 Lepton Propagation L3 Lead: Klas Hultqvist

The leptons are generated in the medium (ice) by the generators either as secondaries to neutrinos or directly as primary particles. From the generator they are given acertain position, direction, energy and time. The propagator takes these particles andpropagates them through the medium (ice and/or rock) taking into account energyloss processes. Together with the lepton, these energy losses are inputs for thedetector response simulation.

1.4.3.3 Photon Field and Detector Simulation L3 Lead: Klas Hultqvist

The Photon field simulation takes photons emitted by a source with a specific spectraland angular distribution and propagates them through the medium (ice). Thepropagation simulates the wavelength-dependent optical properties of the medium,including both scattering and absorption. The OM simulation interfaces to the photonfield simulation. In a first step photoelectron arrival times are generated. The secondstep simulates the electrical and electronical behavior of the OM. The triggersimulation takes information sent by several OMs or some intermediate processor and decides if an event is relevant or not. Given a trigger decision, relevant informationfrom the whole detector is collected by the event builder and stored in an eventformat for later processing.

1.4.3.4 Simulation Production L3 Lead: Klas Hultqvist

Simulation Production comprises the computing, storage, and operational resourcesrequired to produce large sets of synthetic data for use in reconstruction softwaredevelopment and detector performance studies.



1.4.3.5 Special Simulations L3 Lead: Klas Hultqvist

Special simulations comprise special studies in addition to the mainstream simulationchain in order to address specific, focused issues such as particular energy lossmechanisms or engineering tradeoff decisions. These special studies make use of tools such as GEANT, which are not part of the standard IceCube simulation.

1.4.3.6 Documentation L3 Lead: Klas Hultqvist

Documentation will include a Users Guide, or practical description of how to use thecode. In addition, Documentation will also provide the technical description of the codenecessary for maintenance. Formal releases and version controls will be included.

1.4.3.7 Simulations Management L3 Lead: Klas Hultqvist

Manage and coordinate all activities for Simulations. Provide direction and oversight toensure all requirements are met and conduct periodic reviews to ensure allrequirements and deliveries are proceeding as scheduled. Maintain communicationwith all levels of management preparing documentation as necessary to accuratelyreflect performance.

1.4.4 Project/Technical Management L3 Lead: Greg Sullivan

Manage and coordinate all activities for Data Systems. Provide direction and oversightto ensure all requirements are met and conduct periodic reviews to ensure allrequirements and deliveries are proceeding as scheduled. Maintain communicationwith all levels of management preparing documentation as necessary to accuratelyreflect performance.

1.4.5 Experiment Control L3 Lead: Simon Patton

Provide a infrastructure for all parts of the IceCube system at the South Pole that willallow the efficient deployment and use of the IceCube Neutrino Observatory.

1.4.5.1 Experimental Control Logging L3 Lead: Simon Patton

Provide a common logging system that will be used by all parts of the system toreport exceptions from software and hardware subsystems components. The loggingsystem will include Java and C++ interfaces and implementations of these interfacesto be used by the component developers of the IceCube software. It will also providecentralized software that will manage, archive and display the contents of the loggingsystem.

1.4.5.2 Experimental Control Monitoring L3 Lead: Simon Patton

Provide a common monitoring system that will be used by all parts of the system atthe South Pole so that the health of the system can be evaluated at any point in time.Included in the monitoring system will be Java and C++ interface classes andimplementations to be used by the component developers for providing input into thecommon monitoring system. It will also provide centralized software that willmanage, archive and display the contents of the monitoring system.



1.4.5.3 System Control L3 Lead: Simon Patton

Provide a control infrastructure for all parts of the IceCube system at the South Polethat will allow the efficient deployment and use of the IceCube Neutrino Observatory.The control infrastructure includes: 1) a common architecture that all componentsshall need to implement in order to provide both deployment and execution control;2) a single point of control that will give the Experiment Controller access to allcomponents running at the south pole; and 3) integration with the logging andmonitoring systems to provide system status information to the Experiment Controller.


IceCube WBS Dictionary 1.5 Detector

1.5 Detector Commissioning and Verification L3 Lead:

Manage and coordinate the commissioning of the IceCube detector and oversee theprocess by which data from the detector is verified as valid and consistent with aproperly functioning detector. Design, implement and test online filter algorithms.Design and coordinate use of monitoring system. Devise and run calibration tests toverify key detector functionalities. Integrate the AMANDA detector into the IceCubehardware and software environments.

1.5.1 Detector Verification & Physics L3 Lead: Gary HillBenchmarks

Manage and execute the plan to verify the correct operation of the detector. Definethe physics benchmarks which will be used to verify that the IceCube detectorfunctions at a level where the data is sufficient for subsequent physics analysis. Verifythe data against these benchmarks and plan for subsequent physics analysis of thesedata. Commission new strings into the detector.

1.5.1.1 Planning Documentation L3 Lead: Gary Hill

Produce documentation of the plan for the commissioning and verification (dataanalysis) of the IceCube detector. The role of analysis coordinator as distinct from theL3 lead will be defined, as will the method of selection of the Analysis coordinator.

1.5.1.2 Benchmarking and Data Verification L3 Lead: Gary Hill

Define the physics benchmarks which will be used to verify that the IceCube detectorfunctions at a level where the data is sufficient for subsequent physics analysis. Verifythe data against these benchmarks and plan for subsequent physics analysis of thesedata.

1.5.1.2.1 Analysis Coordinator L3 Lead: Gary Hill

Lead collaboration efforts to define the benchmarks against which the correctoperation of the IceCube detector will subsequently be verified and lead the effort toplan for later analysis of data. Organize collaborators into working groups and ensurecommunication within and between these groups to efficiently accomplish theseobjectives.

1.5.1.2.2 Working Groups L3 Lead: Gary Hill

Individual working groups consist of collaborators with similar physics interests. Theywork together to define benchmarks in their particular area of expertise against whichthe correct operation of the detector is checked. Each working group will verify thedata and plan for the later analysis of data in their particular area of interest.

1.5.1.2.2.1 Atmospheric Muons Working Group L3 Lead: Gary Hill

Working group consisting of collaborators working together to verify data and plan forlater analysis of data gathered for Atmospheric Muons and their IceTop coincidences.



1.5.1.2.2.2 Atmospheric Neutrinos Working Group L3 Lead: Gary Hill

Working group consisting of collaborators working together to verify data and plan forlater analysis of data gathered for Atmospheric Neutrinos, WIMPs and NeutrinoOscillations.

1.5.1.2.2.3 Ultrahigh Energy Muons Working Group L3 Lead: Gary Hill

Working group consisting of collaborators working together to verify data and plan forlater analysis of data gathered for Ultrahigh Energy Neutrinos from diffuse sources,point sources, and GRBs.

1.5.1.2.2.4 Ultrahigh Energy Isolated Cascades L3 Lead: Gary HillWorking Group

Working group consisting of collaborators working together to verify data and plan forlater analysis of data gathered for Ultrahigh Energy Isolated Cascades from containedand non-contained diffuse sources and Ultrahigh Energy Tau Neutrinos.

1.5.1.2.2.5 Supernova Working Group L3 Lead: Gary Hill

Working group consisting of collaborators working together to verify data and plan forlater analysis of data gathered for Supernova and Seasonal Variations with Down-going Muons.

1.5.1.2.2.6 Cosmic Ray Working Group L3 Lead: Gary Hill

Working group consisting of collaborators working together to verify data and plan forlater analysis of data gathered from IceTop data, and In-Ice/IceTop coincident data, to further understanding of high energy cosmic-ray-induced showers, including but notlimited to the cosmic ray spectrum and composition, horizontal air showers, non-nuclear cosmic rays, and the extension of hadronic interaction parameters to highenergies.

1.5.1.3 Detector Commissioning L3 Lead: Gary Hill

Create a plan to integrate deployed strings into the existing array and bring thesestrings to full operational status.

1.5.1.3.1 Planning Documentation L3 Lead: Gary Hill

Write plan for commissioning deployed strings.

1.5.1.3.2 Commissioning Coordination L3 Lead: Gary Hill

Coordinate collaboration efforts to commission deployed strings.

1.5.1.5 Verification and Physics Benchmarks L3 Lead: Gary HillManagement

Manage the effort of verification and physics benchmarking.



1.5.2 Reconstruction L3 Lead: Stefan Schlenstedt

The task is to reconstruct and select desired physics events, in particular high-energyneutrinos and events from below and close to the horizon. This process will enhancethe signal and allow suppression of the background of high rate, low energy muonevents.

1.5.2.1 Planning Documents for Reconstruction L3 Lead: Stefan Schlenstedt

Write the requirements and interface documents and develop test plans for on- andoffline reconstruction.

1.5.2.2 Online Reconstruction L3 Lead: Stefan Schlenstedt

Develop robust and fast algorithms to reconstruct events on the South Pole.

1.5.2.2.1 Feature Extraction L3 Lead: Stefan Schlenstedt

Write an algorithm that extracts hits from the electronic and simulated signals.

1.5.2.2.2 Event, OM, Hit-Selection L3 Lead: Stefan Schlenstedt

Develop/ adopt a selection method for events, DOMs and hits.

1.5.2.2.3 LineFit for Muon track reconstruction L3 Lead: Stefan Schlenstedt

Design, implement and test the LineFit algorithm to reconstruct a muon track.

1.5.2.2.4 DirectWalk for Muon track reconstruction L3 Lead: Stefan Schlenstedt

Design, implement and test the DirectWalk algorithm to reconstruct a muon track

1.5.2.2.5 JAMS for Muon track reconstruction L3 Lead: Stefan Schlenstedt

Design, implement and test the JAMS algorithm to reconstruct a muon track.

1.5.2.2.6 DipoleFit for Muon track reconstruction L3 Lead: Stefan Schlenstedt

Design, implement and test the DipoleFit algorithm to reconstruct a muon track.

1.5.2.2.7 Studies for and development of new L3 Lead: Stefan Schlenstedtalgorithms for Muon track reconstruction

Design, implement and test new algorithms to reconstruct a muon track.

1.5.2.2.8 CFirst for Cascade Reconstruction L3 Lead: Stefan Schlenstedt

Design, implement and test the CFirst algorithm to reconstruct a cascade.

1.5.2.2.9 Studies for and development of new L3 Lead: Stefan Schlenstedtalgorithms for Cascade Reconstruction

Design, implement and test new algorithms to reconstruct cascades.

1.5.2.2.10 Tensor-of-Inertia for Event classification L3 Lead: Stefan Schlenstedt

Design, implement and test the Tensor-of-Inertia algorithm to classify events.



1.5.2.2.11 Reconstruction using IceTop L3 Lead: Stefan Schlenstedt

Design, implement and test algorithms to measure air showers, also usable forcalibration and veto for IceCube.

1.5.2.2.12 Pattern recognition L3 Lead: Stefan Schlenstedt

Design, implement and test algorithms to find signatures of overlays of a backgroundmuon with any physics event (muon, cascade, tau etc) and to identify muon bundles.

1.5.2.2.13 Studies for and development of L3 Lead: Stefan Schlenstedtreconstruction algorithms of tau-neutrinos

Design, implement and test algorithms to find "double bang" or "lollipop" hit patternsproduced by a tau neutrino interaction.

1.5.2.2.14 Studies for and development of L3 Lead: Stefan Schlenstedtreconstruction algorithms for Low EnergyEvents (e.g. from WIMPs)

Design, implement and test algorithms to find low energy muons (i.e. short tracks)and cascades.

1.5.2.2.15 Studies for and development of L3 Lead: Stefan Schlenstedtreconstruction algorithms for Events withUltra High Energy

Design, implement and test algorithms to search for Ultra High Energy Neutrinos be itfrom muons or cascades.

1.5.2.2.16 Provide Reconstruction Information for L3 Lead: Stefan SchlenstedtFiltering

Condense reconstruction information for filter purposes in the PnF system.

1.5.2.2.17 Quality assurance L3 Lead: Stefan Schlenstedt

Organize code reviews and tests to track software interferences.

1.5.2.2.18 System Integration Tests L3 Lead: Stefan Schlenstedt

Organize a test-bed to run different modules at the same time for code stability andproperties.

1.5.2.4 Offline Reconstruction L3 Lead: Stefan Schlenstedt

Develop sophisticated algorithms to reconstruct events off the South Pole.

1.5.2.4.1 A simple Muon Track Likelihood L3 Lead: Stefan SchlenstedtReconstruction

Design, implement and test a LLH algorithm to reconstruct muon tracks.

1.5.2.4.2 A generic reconstruction framework L3 Lead: Stefan Schlenstedt

Design, implement and test a LLH framework connecting the photon ProbabilityDensity Functions and different fit methods .



1.5.2.4.3 Muon reconstruction algorithms in the L3 Lead: Stefan Schlenstedtframework

Incorporate fit algorithm to reconstruct a muon track into the framework.

1.5.2.4.4 Cascade reconstruction algorithms in the L3 Lead: Stefan Schlenstedtframework

Incorporate fit algorithm to reconstruct a cascade into the framework.

1.5.2.4.5 Studies for and development of new L3 Lead: Stefan Schlenstedtalgorithms for Muon track reconstruction

Design, implement and test new algorithms to reconstruct a muon track.

1.5.2.4.6 Studies for and development of new L3 Lead: Stefan Schlenstedtalgorithms for Cascade Reconstruction

Design, implement and test new algorithms to reconstruct cascades.

1.5.2.4.7 Reconstruction using IceTop L3 Lead: Stefan Schlenstedt

Design, implement and test algorithms to measure air showers, also usable forcalibration and veto for IceCube.

1.5.2.4.8 Improvements of the photon Probability L3 Lead: Stefan SchlenstedtDensity Functions

Work on improved photon PDFs incorporating the knowledge of ice properties andDOM behavior.

1.5.2.4.9 Interfaces to the photon Probability L3 Lead: Stefan SchlenstedtDensity Functions

Design, implement and test the interfaces of photon PDF to the generic reconstructionframework.

1.5.2.4.10 Pattern recognition L3 Lead: Stefan Schlenstedt

Design, implement and test algorithms to find signatures of overlays of a backgroundmuon with any physics event (muon, cascade, tau etc) and to identify muon bundles.

1.5.2.4.11 Studies for and development of L3 Lead: Stefan Schlenstedtreconstruction algorithms of tau-neutrinos

Design, implement and test algorithms to find "double bang" or "lollipop" hit patternsproduced by a tau neutrino interaction.

1.5.2.4.12 Studies for and development of L3 Lead: Stefan Schlenstedtreconstruction algorithms for Low EnergyEvents (e.g. from WIMPs)

Design, implement and test algorithms to find low energy muons (i.e. short tracks)and cascades.



1.5.2.4.13 Studies for and development of L3 Lead: Stefan Schlenstedtreconstruction algorithms for Events withUltra High Energy

Design, implement and test algorithms to search for Ultra High Energy Neutrinos be itfrom muons or cascades.

1.5.2.4.14 Quality assurance L3 Lead: Stefan Schlenstedt

Organize code reviews and tests to track software interferences.

1.5.2.4.15 System Integration Tests L3 Lead: Stefan Schlenstedt

Organize a test-bed to run different modules at the same time for code stability andproperties.

1.5.2.6 Reconstruction Management L3 Lead: Stefan Schlenstedt

Manage and coordinate reconstruction activities in WBS element 1.5.2.

1.5.3 Detector Characterization L3 Lead: Kurt Woschnagg

This category includes the monitoring of the detector and all calibration activities during and after deployment.

1.5.3.1 Detector Monitoring L3 Lead: Kurt Woschnagg

This element describes the tasks needed to monitor the detector performance and the data quality, both for the In-Ice detector and for the IceTop surface array.

1.5.3.1.1 Monitoring of In-Ice Array L3 Lead: Kurt Woschnagg

Produce documentation describing the system for detector-wide monitoring of the In-Ice detector, including a plan for system design, implementation, testing and operation. Design and implement algorithms to derive quantities to monitor, determine whichparameters are most important to monitor, and coordinate the effort to determinewhich action to take when parameters go out of acceptable range(s). Coordinatedevelopment and implementation of In-Ice monitoring system. Define databaseinterface and contents, and define interface and procedures for communications withExperiment Control. Oversee development of a user interface and coordinate shiftsduring monitoring operations.

1.5.3.1.2 Monitoring of IceTop Array L3 Lead: Kurt Woschnagg

Produce documentation that describes the system for monitoring of the IceTopsurface array, including a plan for system design, implementation, testing andoperation. Design and implement algorithms to derive quantities to monitor,determine which parameters are most important to monitor, and coordinate the effort to determine which action to take when parameters go out of acceptable range(s).Coordinate development and implementation of IceTop monitoring system. Definedatabase interface and contents, and define interface and procedures forcommunications with Experiment Control. Oversee development of a user interfaceand coordinate shifts during monitoring operations.



1.5.3.2 Calibrations (During and After Deployment) L3 Lead: Kurt Woschnagg

This element contains all tasks needed for detector calibration during and after stringdeployment and tank installation. These tasks divide into low-level calibrations of therecorded raw data, and high-level calibrations performed on reconstructed physicalquantities.

1.5.3.2.1 Planning Documentation for Calibration L3 Lead: Kurt Woschnagg

Produce a calibration plan document that describes the calibration tasks to beperformed during and after string deployment and tank installation and includes a high-level description of requirements and functionality of dedicated calibration hardware.

1.5.3.2.2 Charge Calibration L3 Lead: Kurt Woschnagg

Develop, implement and (when possible) automate procedures to calibrate and/orverify the PMT gain in situ in order to translate the charge extracted from the capturedwaveforms to number of photoelectrons. Develop interface to monitoring system anddatabase containing charge calibration constants measured pre-deployment, such assingle photoelectron peaks, linearity of PMT response and PMT saturation behavior.

1.5.3.2.3 Verification of Timing Calibration L3 Lead: Kurt Woschnagg

Develop, implement and (when possible) automate procedures to verify RAPcal timecalibration and to determine overall time resolution for individual DOMs, using datafrom in-situ light sources and from down-going muons.

1.5.3.2.4 Geometry Calibration L3 Lead: Kurt Woschnagg

Develop, implement, and (when possible) automate procedures to determine theabsolute position of every DOM in the ice, and every IceTop DOM and tank on thesurface, with an accuracy comparable to that resulting from the timing resolution.Refine, test and apply three complementary position calibration procedures developedin AMANDA: 1) using non-optical data recorded during deployment for a fast, first-stage absolute calibration; 2) using optical inter-string data from the flasher boardsfor a high-accuracy relative geometry; and 3) using calibrated data from down-goingmuons to survey the array.

1.5.3.2.5 Directionality Calibration L3 Lead: Kurt Woschnagg

Develop, implement, test and execute procedures to calibrate directional accuracy andresolution in the reconstruction of muon tracks, using data from events thatsimultaneously trigger IceTop and the in-ice array (coincidence data).

1.5.3.2.6 Energy and Vertex Resolution L3 Lead: Kurt Woschnagg

Develop, implement, test and execute procedures to calibrate the reconstructedenergy and vertex position of cascades, using data from one or more of the following: in-situ light sources such as calibrated laser modules (standard candles) and flashers,bremsstrahlung events created by down-going muons, and atmospheric electronneutrinos.



1.5.3.2.7 Ice Properties L3 Lead: Kurt Woschnagg

Develop, implement, test and (when possible) automate procedures to augment ourknowledge of ice properties (as mapped with AMANDA) to cover the full geometry and wavelength range relevant for analyzing IceCube data. Determine possible horizontalvariations in the dust layers that dominate optical properties below 1500 m, using data from dust loggers and flashers. Measure the extent to which the optical properties ofthe refrozen column of ice around the in-ice DOMs (the hole ice) affects their angularefficiency.

1.5.3.2.8 Interface to Calibration Database L3 Lead: Kurt Woschnagg

Define interface to calibration database, and what calibration data (constants) toinclude in database and with what periodicity. Define what pre-, during-, and post-deployment calibration data needs to be available in database to enable furthercalibrations.

1.5.3.3 Detector Characterization Management L3 Lead: Kurt Woschnagg

Manage detector characterization activities, coordinate calibration and monitoringtasks defined in 1.5.3.

1.5.4 AMANDA/IceCube Integration L3 Lead: Tyce DeYoung

Amanda/IceCube integration includes the upgrade of AMANDA software as a test bedfor IceCube analysis tools, the later integration of AMANDA software into the IceCubetoolset, the coordination of corresponding software developments, the preparation ofa common triggering scheme, the upgrade of the Amanda computing systems at Pole, the operation, evaluation and development of trigger schemes for the AMANDAchannels with TWR readout, and preparation of the integration of the supernova trigger system in IceCube.

1.5.4.1 Planning and Management L3 Lead: Tyce DeYoung

Produce documentation describing: a) the plan for integrating the logistics of the AMANDA and IceCube detectors b) the plan for integrating the triggers, software packages, and hardware aspects of the AMANDA and IceCube detectors c) the plan for integrating operational and maintenance aspects of the AMANDA and IceCube detectorsManage the AMANDA/IceCube integration effort.

1.5.4.2 [Obsolete] Integration of L3 Lead: Tyce DeYoungAMANDA/IceCube Software (moved to1.4 and 1.5.4.13)

This WBS element was canceled in Jan.2005. It has been moved to WBS section 1.4. The maintenance of the existing Amanda offline software will be covered by WBS item 1.5.4.13.



1.5.4.2.1 [Obsolete] Filter/Reconstruction Code L3 Lead: Tyce DeYoungIntegration

[INACTIVE] A prototype software package within the IceTray framework is planned tobe released end 2004. For the immediate Amanda purposes, the analysis packageSIEGMUND is presently replaced by SIEGLINDE. This package is considerably faster,easier to handle and has more flexibility than SIEGMUND. A compact version ofSIEGLINDE has been installed at the South Pole for 2004 on-line filtering. Part of theSIEGLINDE modules will likely be integrated into IceCube reconstruction software(using IceTray as framework)

1.5.4.2.2 [Obsolete] Simulation Code Integration L3 Lead: Tyce DeYoung

[INACTIVE] IceCube simulation will make use of existing modules used in Amanda(CORSIKA, MMC, É) In 2004, the IceTray framework will be functional, which willinclude the IceCube detector simulation package. This new, flexible framework will becapable to simulate IceCube as well as Amanda. For first IceCube simulations, theAmanda Monte-Carlo mass production tree based on AMASIM is used.

1.5.4.3 [Obsolete] AMANDA Software L3 Lead: Tyce DeYoungCoordination (Replanned in 1.5.4.13)

Item canceled in Jan.2005.This item has been included in WBS item 1.5.4.13.

1.5.4.4 [Obsolete] Muon DAQ Maintenance L3 Lead: Tyce DeYoung(Replanned in 1.5.4.5, 1.5.4.10, 1.5.4.11)

Item canceled in Jan. 2005.The maintenance of the muon DAQ is included in 1.5.4.5. These efforts will go inparallel to upgrades towards IceCube integration, like synchronization and commontriggering. The latter items are now addressed in new WBS items 1.5.4.10 and1.5.4.11.

1.5.4.5 AMANDA Computing System L3 Lead: Tyce DeYoung

This task includes upgrading of the Amanda computing system, networking hardwareand networking systems, including DAQ systems. After archiving, the data areconditioned and moved to systems for satellite transfer. In the northern hemisphereAmanda data will be integrated into the data warehouse covered in WBS section 1.4.

1.5.4.5.1 AMANDA Data Movement and Archiving at L3 Lead: Tyce DeYoung South Pole

Oversee the management of AMANDA data at Pole. Ensure compatibility with IceCube data handling.

1.5.4.5.2 AMANDA DAQ Hardware L3 Lead: Tyce DeYoung

Make modifications to AMANDA DAQ hardware as needed to ensure compatibility withIceCube systems.



1.5.4.5.3 Offline Analysis Hardware L3 Lead: Tyce DeYoung

Update AMANDA offline analysis computers to ensure continued compatibility withIceCube systems and software.

1.5.4.5.4 Operating System and Security L3 Lead: Tyce DeYoung

Upgrade AMANDA computing operating systems and security to ensure compatibilitywith IceCube systems.

1.5.4.5.5 Data Movement to Satellite System L3 Lead: Tyce DeYoung

Oversee the movement of AMANDA data to the satellite system. Ensure compatibilitywith IceCube data handling.

1.5.4.6 [Obsolete] String 18 as Test Bed for L3 Lead: Tyce DeYoungIceCube (ends on 31-Mar-05)

With the appearance of the first realistic IceCube strings in January 2005 and afterhaving realized that string 18 reveals limitations which are overcome for IceCube, theactions on 1.5.4.6 will be terminated by documentation to be written in March 2005.

1.5.4.7 Transient Waveform Recording (TWR) L3 Lead: Tyce DeYoung

The TWR system enhances the dynamic range of Amanda and is also a condition forsuccessful building of a common trigger and merging Amanda and IceCubeinformation. The latter goals are addressed in 1.5.4.10 and 1.5.4.11. Based on realdata, methods for t0 cross calibration to the standard muon DAQ are established andphysics tools for waveform utilization developed. The system is upgraded towardshigher data rates, e.g. by installing feature extraction at low levels close to the ADCs.In preparation of a common global trigger based on IceCube and Amanda data, asoftware trigger of Amanda alone will be installed and tested.

1.5.4.8 Supernova L3 Lead: Tyce DeYoung

The Amanda Supernova system will be run in the SNEWS alert mode. With thestandard muon DAQ likely going to be replaced by the “only TWR” system, a modifiedtrigger has to be programmed and implemented. It will be investigated whether 2independent Supernova trigger systems will be run – one with the Amanda strings, theother with IceCube strings, the one confirming the other – or whether a commontrigger will be formed.

1.5.4.9 [Obsolete] AMANDA/IceCube Integration L3 Lead: Tyce DeYoungManagement (moved to 1.5.4.1)

[INACTIVE] Item canceled in 2004.This item has been moved to 1.5.4.1

1.5.4.10 Time synchronization Amanda-IceCube L3 Lead: Tyce DeYoung

Synchronization of Amanda and IceTop to an accuracy of 15 nsec or better ismandatory for reconstruction of merged events. A plan for synchronization will beworked out in spring 2005, tested at the Northern hemisphere in Summer and installed at the South Pole in the season 2005/06.This item has been moved to 1.5.4.1



1.5.4.11 Coincident triggering L3 Lead: Tyce DeYoung

On top of separate Amanda-only and IceCube-only events, events will be triggeredwhich are below the trigger threshold of the IceCube strings and the Amanda stringsalone. Such a trigger will enhance the effective area and lower the energy threshold ofboth subarrays. For later stages of IceCube, the detection of very low energy eventsin the Amanda strings using IceCube strings as veto can profit from a common trigger. Requirements for a common trigger have to be defined in spring 2005, and thesoftware developed until summer 2005. After a test at the Northern hemisphere inlate summer 2005, in the season 2005/06 the coincident trigger will be implementedat the South Pole. This season allow for a first in-situ test. Further improvements areexpected for the year 2006. In 2007, an improved coincident trigger should yield thefull benefit for IC-32/Amanda.

1.5.4.12 Event building and reconstruction L3 Lead: Tyce DeYoung

Amanda events (or sub-events) will be built in the Amanda-DAQ. Building of globalevents in the IceCube event builder is not preferred due to the necessary interferencewith IceCube data exchange cycles. Instead, the merging of Amanda and IceCubeevents (sub-events) will be performed in the P&F cluster, with a subsequentreconstruction. The reconstruction software belongs to WBS item 1.5.2.This item has been moved to 1.5.4.1

1.5.4.13 Amanda offline software L3 Lead: Tyce DeYoung

Amanda software will be frozen from mid 2005 on. In parallel to getting the IceCubesoftware working, some upgrades of the Amanda software in early 2005 will be usefulin the sense of test beds for the IceCube software within a proven framework. Thisincludes the implementation of photonics into Amasim and the correspondingcomparisons to PTD based simulations and the implementation of TWR informationinto Sieglinde and the development and use of corresponding algorithms. Fromsummer 2005 on, new Amanda analyses should use IceCube software. Analysesusing, in addition to Amanda, information from early IceCube strings should be basedon IceCube software alone.

1.5.5 Project/Technical Management L3 Lead: Doug Cowen

Management of the Detector Verification and Commissioning effort.


IceCube WBS Dictionary 1.6 Raytheon Polar

1.6 Raytheon Polar Services Company L3 Lead:

As the National Science Foundation support contractor, RPSC is responsible forproviding the necessary support labor, materials, engineering, transportation of freightand personnel to McMurdo and South Pole stations, and to demobilize and retrogradeexisting facilities and the drill camp upon project completion.

1.6.1 IceCube Indirects L3 Lead: Eivind Jensen

Level of Effort Activities: Denver Headquarters labor and materials required for projectoversight and management, which includes planning, estimating, documenting,scheduling and cost and control. Indirect labor and fringe costs for RPSC support atSouth Pole and McMurdo. Transportation cost of IceCube cargo to South Pole,including personnel deployment costs, and the additional fuel consumed by eachIceCube participant while on the ice. Indirect equipment support such as logisticsequipment required for handling increased cargo load in system due to IceCube. Theon-ice downtime spent by RPSC employees in training, safety meetings, anddeployment to and from South Pole.

1.6.1.1 Deployment Labor & Downtime L3 Lead: Eivind Jensen

This account represents the percentage of downtime that will be filled by IceCubeemployees. Downtime refers to time on the ice that will be spent in training, all-handsmeetings, safety meetings, and deployment to and from the ice.

1.6.1.2 Division Management/DHQ L3 Lead: Eivind Jensen

Covers the labor and materials required to perform project planning, estimating,scheduling, and cost control for RPSC off-ice support of IceCube. This includes allrequirements for Quarterly Reviews and operations in both Port Hueneme andChristchurch.

1.6.1.3 On-Ice Project Support - Labor L3 Lead: Eivind Jensen

Covers the labor and fringe costs for RPSC support of IceCube at South Pole and atMcMurdo. This is all the indirect labor that is required for the IceCube Project, butdoes not include direct work done on specific components of the Project.

1.6.1.4 On-Ice Project Support - ODC L3 Lead: Eivind Jensen

Covers the indirect costs due to support of IceCube such as additional fuel and foodconsumed by each IceCube participant while on the ice. The quantities are determined according to the South Pole Station Modernization (SPSM) Project model.

1.6.1.5 Equipment Support L3 Lead: Eivind Jensen

Covers the equipment for indirect support of IceCube, including, but not limited to,additional logistics equipment to handle the increased cargo load in the system due toIceCube.


IceCube WBS Dictionary 1.6 Raytheon Polar

1.6.2 IceCube Infrastructure L3 Lead: Eivind Jensen

Direct costs (material, labor and material transportation) associated with theconstruction and logistics of individual buildings, major systems, and new equipment.These categories are: Counting House, Power Plant, Major Equipment, fuel for drilling,fuel for LC-130 transport of IceCube cargo, Construction, and Operations &Maintenance.

1.6.2.1 Counting House L3 Lead: Eivind Jensen

Covers labor and materials required to design the conversion of the South PoleElevated Dormitory into the IceCube Counting House, to procure the necessaryconstruction materials, and to transport these materials, and to carry out theconstruction.

1.6.2.2 Power Plant L3 Lead: Eivind Jensen

Covers the labor and materials required to complete the procurement of the IceCubePower Plant. The final plant will consist of three Caterpillar 225-kW engine/generatorsets, each including a heat recovery system, housed in its own 20-ft Milvan, plus onepower distribution module containing the necessary switchgear and parallelingequipment to operate the plant.

1.6.2.3 Major Equipment L3 Lead: Eivind Jensen

Covers labor and materials required to design, procure and deploy major supportequipment for the IceCube Project, for example, one cable trenching and placementmachine.

1.6.2.4 Drilling Fuel L3 Lead: Eivind Jensen

Covers the material cost of the fuel necessary to produce the IceCube detector holesusing hot-water drilling technology.

1.6.2.5 Aircraft Fuel L3 Lead: Eivind Jensen

Covers the material cost of the fuel consumed by the LC-130 aircraft that areengaged in transporting the IceCube cargo to South Pole.

1.6.2.6 Construction L3 Lead: Eivind Jensen

Covers the labor and materials required for on-site construction support of theIceCube project. This includes, but is not limited to, assembly to the IceCube HoseReel, assembly of the drill tower structures, spooling approximately 10,000-ft ofhose onto the completed hose reel, attached Mobile Drill structures to their respectivesleds, and supporting the installation of IceTop tanks.

1.6.2.7 O&M L3 Lead: Eivind Jensen

Covers the labor and materials for O&M support of IceCube building and facilities.


IceCube Kilometer Scale Netrino Observatory Work...

Documents

Transcript of IceCube Kilometer Scale Netrino Observatory Work...