1 / 26

Deployment, logistics and systems engineering

Deployment, logistics and systems engineering. PILOT Design Study. Main functions of conceptual design study for PILOT for feasibility, costing and risk assessment purposes.

justus
Download Presentation

Deployment, logistics and systems engineering

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Deployment, logistics and systems engineering

  2. PILOT Design Study • Main functions of conceptual design study for PILOT for feasibility, costing and risk assessment purposes. • In order to properly capture the full lifetime facility cost, it is necessary to investigate and plan the operations of the complete facility as well as the telescope itself. • Systems engineering approach

  3. Systems Engineering Systems engineering is an interdisciplinary approach and means to enable the realization of successful systems … [an] integrated, ‘holistic’ view of the complete system, intended to ensure that the delivered system meets requirements. INCOSE (International Council on Systems Engineering)

  4. Systems Engineering • Integrated, multidisciplinary, ‘holistic’ view of complete system, intended to ensure that the delivered system meets requirements • Not just nice words to keep in mind while doing ‘old style’ engineering – now a formalised methodology • ISO/IEC 15288, Second edition, 2008 • Systems and software engineering – System life cycle processes • INCOSE Systems Engineering Handbook, Version 3.1, August 2007

  5. Systems Engineering • Formal documentation structure • Full system design – system boundary definition • Interface management (external) • Requirements management (identification, validation, verification) • All requirements to be traceable • Documentation structure grows to map susbsystem design • Interface management (internal) • Document control (numbering, version control)

  6. Subsystem FPRD Subsystem FPRD Subsystem FPRD Subsystem FPRD PILOT Documentation Structure Science Case Document Environmental Conditions Document Science Case Document Customer Requirements Science Requirements Document Functional & Performance Requirements Document Delivery Plan Document Operations Concept Document System Specification Document Design Study Report

  7. Subsystem FPRD Subsystem FPRD Subsystem FPRD Subsystem FPRD PILOT Documentation Structure Science Case Document Environmental Conditions Document Science Case Document Customer Requirements Science Requirements Document Functional & Performance Requirements Document Delivery Plan Document Operations Concept Document System Specification Document Requirements traceability Design Study Report

  8. What is PILOT?

  9. PILOT SYSTEM What is PILOT? • Systems engineering methodology requires clear definition of system boundaries Astronomical science light Physical Docks and shipping AAD (Hobart) staging facilities Dome C atmosphere Optical Physical Overland Antarctic transport system Physical Physical Dome C surface Physical Physical Observer Antarctic air transport Config tools Physical Raw dataReduced data Archive/VO Physical Commissioning crew Control I/FData transport Satellite communications infrastructure Physical Physical Concordia lifting/handling equipment Physical Physical Organisational Organisational Consumables supply Organisational Concordia-based support scientist Instrument designers/builders Antarctic legislation Concordia Station

  10. PILOT facility functional roles

  11. PILOT facility functional roles

  12. PILOT facility subsystem breakdown • Facility extends well beyond components at telescope site • Must consider all aspects of running any observatory • observing support, maintenance, data archive and distribution, TAC, upgrade cycle • Extended logistics chain • Unusual access/upgrade cycle

  13. Unusual elements of PILOT system design for Dome C • Site characteristics and facilities • Physical access • Communications • Observing model • Organisational model • Commissioning/decommissioning

  14. Dome C 75.6ºS 123.2ºE, 3250m elevation

  15. Dome C

  16. Concordia Station • Significant infrastructure and logistics support • ‘a dozen’ wintering staff • can accommodate up to 80 in summer • PILOT proposed to be 500 – 1000m from station • Cold: long periods <-60ºC, reaching -80ºC • Supersaturation: frosting a problem • Remote: limited physical access, limited communications • Deep ice (>3000m)

  17. Site access • Physical access via traverse (tractors pulling sleds) or air • Traverse can carry hundreds of tonnes, taking 10 to 14 days • Air transport fast but limited in capacity • IPEV have established traverse support to Concordia, with three traverses annually carrying ~450T (PILOT to augment for construction) • Short access season ~10 weeks, November to February • Access season applies to commissioning crews, too

  18. Power supply • PILOT Antarctic components expected to consume ~20kW annual mean load • Sited close enough to Concordia to integrate power supplies (reliability, economies of scale) • Concordia diesel generators have sufficient peak load capacity but limited by diesel • PILOT requirements would require additional 60,000 litres of diesel annually • Carry additional fuel with increased traverse capacity

  19. Alternative power options • Diesel has high cost due to transport • Solar panels: reduce station fuel burn in summer to provide PILOT reserve • Wind turbines: Year-round power supplement • Payback period < 4 years • Progressive or mixed implementation options • Environmental credentials

  20. Communications • No overland communications link • All data via satellite or physical carriage of media • Two main satellite options: • Iridium (2400 bps @ $1/min) • Geostationary, 128kbps (limited coverage due to low elevation angles from 75ºS) • Iridium broadband option planned rollout later 2008 • Will not be possible to transmit all PILOT raw data • Close remote control of telescope impractical

  21. Queue-based robotic observing • PILOT’s strengths in large surveys (wide field good seeing) • Surveys well-suited to queue-based observing • Limited winter access even for PILOT operator at Concordia • Limited access and communications also suggest queue-based observing • Robotic operation proposed • Intelligent queue scheduler local to the telescope, responsive to variations in observing conditions

  22. Queue-based robotic observing • Observation scripts transmitted via satellite • Wintertime instrument exchanges limited to those that can be simply automated (e.g. switching tertiary mirror to select Nasmyth port) • Limited data reduction done in data pipeline for QA • Observation reports and quality monitoring data transmitted back via satellite • Full data archive physically carried out by air annually

  23. Commissioning

  24. Decommissioning • Part of systems engineering approach • Legislated Antarctic responsibilities • Nominal 10-year lifetime • Dismantling and carriage out of structures similar to carriage in for commissioning • No particular site restoration difficulties (deep ice) • Possible handover to future facilities (interferometer? submillimetre?)

More Related