madeline close systems engineer manager gemini observatory … · 2015-09-23 · •...

Madeline Close Systems Engineer Manager Gemini Observatory March 17, 2015

Topics I.  A Brief History of Gemini and Systems Engineering II.  Systems Engineering in Gemini Development III.  Systems Engineering in Gemini Opera>ons IV.  Conclusions

2

Objec>ves: To describe how systems engineering is integrated into Gemini Observatory’s development and opera>ons. To broaden cross-‐organiza>onal knowledge of systems engineering and its benefits.

Systems Engineering at Gemini ObservatoryMadeline Close, March 17th 2015

A short introduc>on before we start •  Former “rocket scien>st” with ten years

experience in the aerospace and defense industries.

•  First experience in systems engineering as a System Opera>ons engineer at Boeing Satellite Opera>ons and Ground Systems.

•  Boeing project manager and systems engineer for DTCS Phase 2, a satellite-‐based communica>ons system.

•  Chief engineer and project manager for U.S. defense agency R&D programs as a Booz Allen government contractor.

•  Systems Engineer Manager for Gemini Observatory since March 2014.

•  Cer>fied Systems Engineering Professional (INCOSE CSEP).

•  Cer>fied Project Manager (PMI PMP).

3Systems Engineering at Gemini ObservatoryMadeline Close, March 17th 2015

Systems Engineering Group (SEG)

4

•  Five team members (2.5% of observatory staff) –  Three systems engineers including manager –  Two support associates –  Cross-‐site support at both Gemini North and

Gemini South •  Focused support to maximize impact:

–  Complex interdisciplinary projects –  Configura>on management –  20% of >me reserved for smaller ini>a>ves

•  Three other observatory engineers provide systems engineering (SE) support for other specific projects.

•  Vision is to mature and stabilize systems engineering at the observatory for the benefit of all.

A Brief History of Gemini and Systems Engineering


?Now Hiring

for a Systems Engineer!

http://www.gemini.edu/jobs

I. A Brief History of Gemini and Systems Engineering

5Systems Engineering at Gemini ObservatoryMadeline Close, February 18th 2015

A Brief History of Gemini

6

•  Two 8-‐m Cassegrain telescopes located in Chile and Hawaii, providing full-‐sky coverage.

•  Interna>onal partnership consists of U.S., Canada, Brazil, Argen>na, Chile, Australia* and South Korea**.

•  Staffed by ~190 personnel, including five in the SEG. •  Annual opera>ng budget ~$30M •  Annual development budget ~$4M

*Becomes limited partner in 2016 **Limited partner 2015-‐2016


Counterclockwise from top left: inside the dome, Gemini South, Mauna Kea, Gemini North (source: Gemini website)


A Brief History of Systems Engineering

7

•  Concepts behind systems engineering were created at Bell Telephone Laboratories during the early 1900’s.

•  Adopted by DoD during WWII. –  Air Force created the RAND Corpora>on and

coined the term “systems analysis.” –  Used for missile and missile defense system

designs –  NASA Apollo program employed “systems

management”

•  First formal teaching was at MIT in 1950 è Now widely taught and prac>ced!

–  In Government: NASA, DoD, etc. –  In private industry: aerospace, automo>ve,

informa>on technology, medical, etc.


Growing membership in the International Council on Systems Engineering (INCOSE)

(source of text and graphic: INCOSE website)


Systems Engineering + Gemini

8

Our group is often asked, What is Systems Engineering?

One answer is:Traditional engineering disciplines at observatories include mechanical, electrical, optical and software. None of these addresses all of the facets of complex systems such as large telescopes, astronomical instruments, laser guide star systems or the observatory as a whole.

Systems Engineering is the engineering discipline focused on complex interdisciplinary systems and the necessary activities, processes and tools to successfully achieve and maintain these systems.


Major phases of the system lifecycle. (source: Gemini Systems Engineering Department)


Systems Engineering + Gemini (con>nued)

9

Our group is often asked, Why Systems Engineering?

Systems Engineering’s activities, processes and tools help us to:•  Deliver instruments that are optimized to meet stakeholders’ needs through

user needs analysis, requirements definition, design trades and validation. •  Deliver instruments that perform as expected through system requirements

derivation, budget allocation, interface analysis and verification.•  Improve operational efficiency by delivering new processes and tools that

meet stakeholders’ needs and reduce overhead.•  Maintain efficient operations by monitoring and analyzing performance

metrics, approaching fault investigations from a holistic perspective, and by planning for end-of-life.

•  Maintain integrity of documented configurations through formal change request processes.



•  Complex inter-‐disciplinary projects in the Observatory Project Porlolio –  At least half of all Development projects:

•  New instrument conceptual design: Gemini Instrument Feasibility Study (GIFS) •  New instrument development: Gemini High Resolu>on Op>cal SpecTrograph (GHOST) •  New instrument transi>on to Opera>ons: Gemini Planet Imager (GPI) •  System upgrade: Natural Guide Star (NGS2) •  System upgrade: Laser Guide Star Facility (LGSF)

Current Projects Supported by the SEG

10

Systems Engineering and Instrument Development at Gemini

Gemini Observatory Project Portfolio (source: Gemini Observatory)


•  Complex inter-‐disciplinary projects in the Observatory Project Porlolio –  At least a quarter of all Opera>ons and Transi>on projects

•  Full remote opera>ons capability: Base Facility Opera>ons (BFO) •  Improvements to opera>ons: Gemini Mul>-‐conjugate Adap>ve Op>cs System (GeMS) •  Replacement of opera>ons tool: Project Insight/Plan for the Week (PI/PFW)

Current Projects Supported by the SEG (con>nued)

11



Gemini Observatory Project Portfolio (source: Gemini Observatory)

•  Smaller ini>a>ves –  Document Management Tool (DMT) improvements

•  Improve naviga>on by modifying and flapening hierarchy and improving home page. •  Improve searching by expanding use of meta data and formal naming for change

controlled documents.

–  Document management policy –  (Upcoming) Web content management policy –  (Upcoming) Engineering opera>ons fault and performance metrics –  Requirements management tool –  (Upcoming) Integrated SE-‐PM framework (systems engineering & project management)

•  Alignment of SE ac>vi>es and deliverables with Prince2 PM stages. •  Templates for common SE and PM documents. •  Gemini Systems Engineering Management Plan (SEMP) •  Gemini Project Management Plan (PMP)

Current Projects Supported by the SEG (con>nued)

12



II. Systems Engineering in Gemini Development

Gemini’s Instrument Development Lifecycle •  Instrument development lifecycle based on the classical Vee model (also known as

modified Waterfall model). –  Sequen>al workflow at the top level

•  Stages modified to reflect Gemini procurement model –  Added Proposal stages –  Grouped technical processes for requirements and design to reflect itera>ve approach –  Defined several stages of integra>on and verifica>on

14


Development lifecycle used for GHOST. Lifecycle will differ in Proposal Phase for Gen4#3. (source: Gemini Development Division)


Classic Vee model. (source: Clarus Concept of Operations,

Federal Highway Administration)

Proposal Phase Systems Engineering The role of the Gemini Systems Engineer is to: •  Establish and maintain repository for internal files, notes, etc. •  Define science requirements in collabora>on with scien>sts. •  Iden>fy observatory documents required to respond to proposal.

–  Gemini interface control documents (ICDs) –  Gemini system level requirements and constraints

•  Develop Statement of Work (SOW) in collabora>on with PM and contracts officer, focusing on technical ac>vi>es and deliverables.

•  Develop selec>on criteria in collabora>on with PM and contracts officer, focusing on technical management and performance.

•  Develop web content in collabora>on with PM. •  Answer technical ques>ons from proposers. •  Assess proposals against selec>on criteria. •  Maintain confiden>ality

15



GIFS and Gen4#3 Proposals •  Gemini Instrument Feasibility Study (GIFS) and Genera>on 4, Instrument #3

(Gen4#3) implement changes to Gemini’s procurement model: –  Open call for proposals, including en>re interna>onal community, not just Gemini partners. –  Proposal stage 1 (GIFS) is for feasibility study to garner community input for Gen4#3.

•  GIFS is a set of instrumenta>on design studies that are community-‐created and science-‐driven, guided by principles from the Gemini Science and Technology Advisory Commipee (STAC).

•  At comple>on of GIFS, Gemini together with the STAC and wider community will decide on the top-‐level science and instrument requirements for Gen4#3.

16



STAC guiding principles for GIFS and Gemini reference documents (sources: http://www.gemini.edu/sciops/future-instrumentation/gifs-gemini-instrument-feasibility-studies and http://www.gemini.edu/sciops/instruments/specifications)

Design Phase Systems Engineering

The role of the Gemini Systems Engineer is to: •  Establish external-‐facing repository for project documents,

accessible by en>re project team. •  Define file formats and numbering scheme. •  Refine system requirements in collabora>on with project

team. Monitor requirements management. •  Par>cipate in system modeling ac>vi>es including system

architectures, interfaces and budgets. •  Par>cipate in design trade studies. •  Monitor and assess risk mi>ga>on ac>vi>es. •  Review deliverables and enforce change control process. •  Develop integra>on, test and commissioning plans.

17

In a competitive environment, the role of the observatory systems engineer is constrained to ensure fairness, and is focused on answering questions and assessing results.Once final down select is made, the role becomes collaborative. This increased involvement with the project team was re-introduced by Gemini for Generation 4 instruments based on lessons learned. The extent of collaboration will depend on the systems engineering expertise in the project team. More on this in a minute…



Case Study: GHOST Preliminary Design

18



•  Gemini High Resolu>on Op>cal SpecTrograph (GHOST) completed the preliminary design stage in December 2014. –  Fiber fed, bench-‐mounted spectrograph –  The most significant design trade concerned

the spectrograph loca>on. The best loca>on for stability required the longest fiber and thus highest throughput losses.

(Clockwise from top) GHOST system models for component location, throughput performance, software architecture and instrument behavior. (sources: Australian Astronomical Observatory (AAO); National Research Council Canada (NRC); AAO; AAO all via the GHOSD-06 Preliminary Design Document)

GHOST PD Architecture and Interfaces

19



(Clockwise from top) GHOST system architecture and interfaces, product breakdown structure and requirements flow down, N-squared interface diagram. (sources: Australian Astronomical Observatory (AAO) via the GHOSD-06 Preliminary Design Document; Gemini Systems Engineering Department; same)

Build Phase Systems Engineering The role of the Gemini Systems Engineer is to: •  Assess spares management plan. •  Monitor metrology and component quality

assurance. •  Conduct site visits to manufacturers and project

team members. •  Ini>ate knowledge transfer to Gemini team. •  Monitor propaga>on of real data into system

models and impacts. •  Monitor requirements verifica>on. •  Monitor integra>on and tes>ng. •  Document processes and procedures (alignment,

calibra>on, etc). •  Review deliverables and enforce change control

process.

20



Test Phase Systems Engineering The role of the Gemini Systems Engineer is to: •  Monitor simulated end-‐to-‐end tes>ng (sta>c,

dynamic, environmental). •  Coordinate shipping and delivery to Gemini. •  Coordinate day>me tes>ng and logis>cs for

commissioning. •  Inventory supplementary tools and equipment. •  Monitor requirements verifica>on. •  Facilitate knowledge transfer to Gemini team. •  Review deliverables and enforce change control

process. •  Prepare for transi>on to opera>ons.

–  Coordinate with Science Ops on transi>on criteria –  Establish opera>ons repository –  File delivered documents, drawings and ICDs in

appropriate repository collec>ons

21



Case Study: GPI Transi>on to Opera>ons •  Gemini Planet Imager (GPI) completed commissioning runs

in Sept 2014 and was offered for science in Nov 2014. –  Success story as the one Genera>on 3 instrument to be delivered.

–  Outstanding ac>ons include disposi>on of waived requirements and priori>za>on of post-‐transi>on ac>ons.

22


Vendor lab

acceptance

Site/telescope

acceptance

Sky technical

commissioning

Sky science

commissioning

System

Verifications

(end-to-end exercise)

Science

Operations

Instrument Procurement Cycle

(lab to science)

Led

by

vendor

Led by PM

(+ vendor)

Led

by

PS &

SciOps

Led

by

SciOps

On-site

delivery

RTE RTO

RTU

RTE: Release To Engineering

RTO: Release To Operations

RTU: Release to Users

RTD: Release to Development

PM: Project Manager (Gemini)

PS: Project Scientist (Gemini)

Vendor

documentation

delivered

Prioritize

modes of Ops

RTD

Normal staff

Led by Dev

Instr. upgrade

shutdown

Extra staff

Reject or

other modes

of Ops changes: yes

changes: no

Regular

call

reject or

accept

DEV OPS

SV call

GPI commissioning stage breakdown (source: Gemini Systems Engineering Department)


GPI criteria for transition to operations (source: Gemini operations division)

III. Systems Engineering in Gemini Opera>ons

Systems Engineering in Opera>ons

24

Systems Engineering in Opera<ons at Gemini

•  Recall that Systems Engineering is the engineering discipline focused on complex systems and the necessary ac>vi>es, processes and tools to achieve and maintain these systems successfully.

•  Systems Engineering is important throughout the lifecycle of a system. –  Improve process efficiencies –  Monitor performance metrics and trends –  Analyze and priori>ze issues and faults –  Manage configura>on and enforce change control process –  Manage technical risks including spares and obsolescence



25


•  The “long tail” of opera>ons refers to the idea that systems may spend much longer in opera>ons versus development.

•  Total opera>ons costs may dwarf total development costs.

•  Applying systems engineering to opera>ons can lead to higher efficiencies. $184 $30 $4

$-‐ $50 $100 $150 $200

Initial Development

Cost

Annual Operating

Budget

Annual Development

Budget

Cost

in $M

$0

$100

$200

$300

$400

$500

1995 2000 2005 2010 2015

Cost

in $M

Year

Cumulative Development Cost Cumulative Operating Cost

Gemini Observatory Development and Operations Costs and Budgets (source: Gemini Development Division; some numbers approximate)



26


•  Improve process efficiencies. –  Look for opportuni>es to

reduce overhead, reduce manual labor, streamline tasks, consolidate informa>on.

–  The tool should fit the process, not the other way around.

•  Manage technical risks including spares and obsolescence

–  Transi>oning to Maintscape for inventory management.

The following slides describe the ideal roles of systems engineering in Operations. Engineering operations currently holds some of these roles. Educating the staff on systems engineering, including individuals in these roles, is one way the SEG is striving to integrate systems engineering into daily observatory operations despite the small size of the group itself.

Primary mirror coating – a major endeavor that occurs every few years! (source: Gemini website)

Project Insight page – a planning tool forced into change and task management. (source: https://project.gemini.edu:2010/)



27


•  Monitor performance metrics and trends:

–  Gemini Engineering Archive (GEA) displays real-‐>me and historic metrics

•  Analyze and priori>ze issues and faults:

–  Reported and assigned via Remedy trouble >cket tool.

–  Monitored in monthly site-‐specific fault reviews.

Remedy page (source: https://remedy.gemini.edu)

GEA page (source: http://geanorth.hi.gemini.edu)


Upcoming ini>a>ve: Re-‐integra>ng metrics from four different sources to provide one site for monitoring.


28


•  Manage configura>on and enforce change control process:

–  Changes formally requested via sosware tool. Current tool and process under review.

–  Change controlled documents managed in Docushare repository. Policy just revised for first >me in fiseen years.

–  Web-‐based content should follow the same guidelines as documents for change control and configura>on management.

Change control process for general document. (source: Gemini Document Management Policy)

Change Request page (source: https://project.gemini.edu:2010/)


Case Study: BFO •  Base Facility Opera>ons (BFO) will enable remote nightme opera>on from

the base facility. Comple>on at Gemini North is expected by early 2016. –  Major change in paradigm, and required a rethinking of many processes and

studies on how to provide func>ons remotely (such as audio and visual clues). –  Impacts nearly every stakeholder group at the observatory, which drove the need

for strong communica>ons supported by formal processes and including Trello (ac>on items and mee>ng minutes) and Jira (change requests, issue reports).

29


Example BFO use case and activity sequence.

(source: BFO Concept of Operations)


Example BFO Trello board including status of action items and recent meeting minutes.

(source: BFO Trello site)

IV. Conclusions

Value in Systems Engineering & Value in Systems Engineers

Over the next few years, the SEG will help Gemini: 1.  Deliver a full suite of 4th Genera>on instrumenta>on. 2.  Achieve and maintain Base Facility [remote] Opera>ons. 3.  Develop and deploy new processes and tools for change management, planning,

task management, and resource management. 4.  Improve opera>ons performance monitoring and issue resolu>on.

To do this, the SEG will need to apply: •  Best prac>ces learned in formal training, educa>on and cer>fica>on. •  Ap>tude for understanding the breadth of a system and the concepts,

interac>ons and processes that will enable the system to perform. •  Holis>c knowledge of Gemini systems and capabili>es. •  Experience in applying and tailoring systems engineering to specific projects.

31



Contact me at: [email protected] Check out my upcoming blog: https://systems2stars.wordpress.com Gemini public website: http://www.gemini.edu Gemini future instrumentation: http://www.gemini.edu/sciops/future-instrumentation

madeline close systems engineer manager gemini observatory … · 2015-09-23 · •...

Documents