1 / 7

Executive Perspectives on CBS: NASA’s EOSDIS Core System

Executive Perspectives on CBS: NASA’s EOSDIS Core System. Mike Moore, ESDIS Project NASA Goddard Space Flight Center mike.moore@gsfc.nasa.gov 301-614-5123. System Background. EOSDIS Core System will manage unprecedented science data volumes (~ 9 PB) from 20 instruments on 9 spacecraft

jorn
Download Presentation

Executive Perspectives on CBS: NASA’s EOSDIS Core System

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. Executive Perspectives on CBS:NASA’s EOSDIS Core System Mike Moore, ESDIS Project NASA Goddard Space Flight Center mike.moore@gsfc.nasa.gov 301-614-5123

  2. System Background • EOSDIS Core System will manage unprecedented science data volumes (~ 9 PB) from 20 instruments on 9 spacecraft • System deployed at four geographically distributed, independent Data Centers • Large system (1.1M SLOC) with heavy dependence on COTS (~ 50 products integrated in system) • Initial development period was 60 months • System has been operational for 22 months

  3. Key COTS Issues • Familiar, accepted acquisition and lifecycle models do not accommodate CBS • No basis for estimating CBS lifecycle schedules and costs, especially long-term maintenance • Stakeholder understanding of COTS is based on limited COTS usage • COTS expertise can increase attrition rates • Developers like to build things • COTS upgrades cause continual system change • Hard to coordinate COTS and system upgrades

  4. Unsuccessful COTS Strategies • Mandating maximum use of COTS • Waterfall model for COTS-intensive systems, especially when pushing COTS performance envelopes • Bringing in the experts; they have agendas too • Over reliance on open systems standards to address COTS compatibility issues • Maintaining COTS source code • Adhering to high-end COTS solutions when simpler solutions will work

  5. Successful COTS Strategies • Use a more adaptive lifecycle model • Sponsor competing COTS vendors for mission critical areas • Use COTS wrappers to avoid lock-in • Require vendors execute customer-defined benchmarks as part of bid • Prototype use of new or competing products • Assess COTS replacements throughout lifecycle • Maintain active management relationships with vendors

  6. Center-wide Strategies • Site licenses for key infrastructure COTS • Sponsorship of niche products • Commercialization of NASA products • Tool workshops to enhance profitability of niche markets • Standardized interfaces for niche products to allow plug-and-play across vendors • Exploring Product Line development to promote longer-term markets • Exploring independent COTS certification

  7. Workshop Goals • Understand the available CBS experience base • Examine system acquisition and lifecycle models to realize potential CBS, Open Source and component reuse benefits • Discuss possible benefits of cross-agency COTS and component knowledge bases

More Related