How to Architect Family of Complex Space Systems and Networks?
Upcoming SlideShare
Loading in...5
×
 

How to Architect Family of Complex Space Systems and Networks?

on

  • 878 views

Architecting Process, Frameworks and practice of Complex Space Sytems Vol 2 of Vol3

Architecting Process, Frameworks and practice of Complex Space Sytems Vol 2 of Vol3

Statistics

Views

Total Views
878
Views on SlideShare
863
Embed Views
15

Actions

Likes
0
Downloads
4
Comments
0

2 Embeds 15

http://www.linkedin.com 12
https://www.linkedin.com 3

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

How to Architect Family of Complex Space Systems and Networks? How to Architect Family of Complex Space Systems and Networks? Presentation Transcript

  • Systems Architecture Products Capturing SCaN Legacy Networks in Architecture Diagrams and Documents Constellation Orion-to-ISS Mission NASA Lunar Mission and Communication Networks SCaN Future Architecture “Architecture is a creative art, even if it is based on an existing legacy system. It is not only for engineering or construction guidance, but it also has to provide insight, intent, and vision, so that it can guide the system in moving forward through continual evolution.” Dr. Yan Zhao; CGI Federal Director for Enterprise and Solutions Architecture 1
  • Capturing SCaN Legacy Networks in Architecture Diagrams and Documents 2
  • SCaN “As Is” Architecture All-View Diagram 3
  • Deep Space Network (DSN) Operational Node Connectivity (OV-2)
  • Deep Space Network (DSN) Operational Information Exchange Matrix (OV-3) Need-line Informa-tion Information Element Producer Consumer Identifier Exchange Name Identifier Sending OpActivity Name and Receiving Op Node Name and Sending Op Node Name and Receiving Op Activity Name and Identifier Language Accuracy Identifier Identifier Identifier Scope 1 1a Customer Spacecraft Analysis of Customer Support Service DSN Operations Support Service Data Customer Mission Planning & Center Preparation (3) Requirements Operations Scheduling (2) 1 1b Planning & Conflict Customer Support Service DSN Operations Support Service Scheduling Request Resolution, DSN Mission Planning & Center Preparation (3) Resource Operations Scheduling (2) Allocation 1 1c Service Schedule Conflict resolution Customer Support Service DSN Operations Support Service Updates and realtime DSN Mission Planning & Center Preparation (3) operations Operations Scheduling (2) 2 2a Resource Specs, Customer gains DSN Operations Support Service Customer Support Service Availability & Status understanding of Center Planning & Mission Preparation (3) DSN assets and Scheduling (2) Operations services 2 2b DSN Schedules Long Range DSN Operations Support Service Customer Support Service (years), Mid Center Planning & Mission Preparation (3) Range (8-weeks) Scheduling (2) Operations and Short Range (7-day) 2 2c Accountability All customer DSN Operations Assess Quality & Customer Reports deliverables Center Performance (5) Mission including real- Operations time and post- pass deliverable
  • Near Earth Network (NEN) Systems Communications Description (SV-2)
  • Space Network (SN) Systems Functional Flow (SV-4) 7
  • Constellation Orion-to-ISS Mission 8
  • SCaN Concept of Operations CEV-ISS Missions • Prelaunch • Launch/Ascent • Low Earth Orbit (LEO) • ISS Operations • Return to Earth • Recovery 9
  • System Communications Description (SV-2) CEV-ISS Mission, Rendezvous-Docking Phase 10
  • SCaN Network Navigation Architecture CEV-ISS Mission, Rendezvous-Docking Phase 11
  • End-to-End IP Network Architecture The Constellation Project has established the initiative to extend communication infrastructures based on IP protocol from ground segment to flight/space segment to achieve interoperability among its elements. SCaN Networks can accommodate IP Service Interfaces to CxP systems. Orion MS IP service interface Applications Cx Router Applications SCaN NISN NISN Earth Data Exchange Networks Data Exchange Transport SN Transport Network IP Network IP Network IP Network IP Data Link DL DL DL DL DL DL Data Link PHY PHY PHY PHY PHY PHY PHY PHY 12
  • NASA Lunar Mission and Communication Networks 13
  • LRS ISRU Rover Power Science Station EVAs EVAs Beacons LSAM Habitat CEV LSAM EVAs LCT LRS MCC LRS NCC & LMOC Lunar Communication and Navigation Systems LGTs All-View Diagram 14
  • Lunar Communication and Navigation Systems (LCNS) Operational Node Connectivity (OV-2) Traverse Monitors, Voice CEV to/from Moon Video Coordinates MCC Data Directs & Control LSAM Land on Archive Monitoring Moon Telemetry Schedules Tracking Ephemerides Status Data Rovers Tracking Navigation Tour Beacons Manage Networks ENCC EVA Provide Provide Analysis & ephemeris services Astronauts. Status, Voice, Robot Astronaut Video, Data Support & Data Data Explore Schedules Telemetry Control Ephemerides Status Data Telemetry Habitat Provide Centralized Habitation Manage links LMOC Facilities Status Ephemerides LCNS C/N Provide Local Directives Lunar Surface Tracking Terminal Directives Status Communication Data Data Timing And LRS Access Control Telemetry Telemetry Data Science Analyze Lunar Ground ISRU Make Fuel Antenna Terminals Power LCNS Lunar Provide Relay System Power LCNS Internal Other Users LCNS Users
  • Lunar Communication and Navigation Systems (LCNS) System Communications Description (SV-2) Earth Space Lunar Surface «operations» «human» MCC «human» «system» «human» «system» 35* EVAs • SMD EVAs Vehicles 32* CEV 14 - S • pressurized EVAs • Gov Agencies • Int’l Partners «system» • open Beacon 36* • 3 or more 33* 13 4 -S 37* 1 -S 4 units 3, ,4 34* «operations» 42 «system» LMOC «system» Robots 24 - 802.1 LSAM • science , .16, Optical • construction S Surface 02.11 a, -K 2 Networks 38* 1, .16, - 15 16 25 - 8 6, 12 «operations a, S , .1 11 - Ka, S -K 7-K . 11 39 a, » 1 02 ,4 «system» S - 8 0, LCNS «system» 26 LSAM 41 Network 18 - Ka, S -S LRS 3 Ka, S 10 - K -S 4 a, S «system» 27 29* u 5 LCT 30* 9-K «system» 28* 31* LGT 1 19 «system» -S 6 «system» LRS 23 7 ISRU(s) -1 «systems» 20 2 1* 0G E Wired -S «system» Crosslink 8 «system» LGT 2 Habitat * «system» Power 22 LGT 3 Wire *802.11, .16 *802.11, .16 16
  • Moon/Earth Space Network OV-2 diagrams networked together to form a System View (SV-4) Lunar Orbit Nodal Region Lunar Surface Nodal Region Scenario: Human on EVA on Moon Conversing with Scientist at GSFC GN Ground Station Nodal Region 17
  • Crew Exploration Vehicle System to System Connections (SV-2) 18
  • Crew Exploration Vehicle Science Capture Functional Description (SV-4) DV Still Headsets Microphones Camera Camera Sensor Analog Audio Data Control MPEG JPEG VoIP Conversion Route Space Control Earth Wireless VoIP Relay on 802.15 Data (WLAN) 802.11 Routing 1G Ethernet Wall Tables Displays Ethernet Routing RF RF Transmit Science Processing Collection Requirements Data Processing Science Data Collection Science Data Transport Storage Science Sequence 19
  • SCaN Future Architecture 20
  • SCaN Integrated Communication Architecture All-View Diagram Titan Neptune Saturn Uranus Pluto Charon Jupiter SCaN  ¸ Mars Integrated  Service  Portal ISS MCC NISN Cx MCC Antenna  Array Venus SCaN µwave SCaN Optical NISN Sun Mercury 21
  • Future SCaN Network System Interfaces Diagram 22
  • Future SCaN Network Customer/Systems Operational Relationship
  • Future SCaN Network Operational Activities Flow (OV-5) 24
  • Looking Forward • System Interoperability • Cross-Organizational Interfaces and Decision Making Processes • Software Architecture and Lifecycle • Horizontal Technical Coordination and Integration • Architecture Cost-benefit Analysis • Developing NASA-Wide Architecting Process – Levels and Stages (Definition, Description and Design) • Architecture Performance and Evaluation • Integration of Architecture with Requirements and ConOps • Implementation Follow-up
  • Credits Thanks to System Concepts Integration and Planning (SCIP) Project Management for allowing this work to flourish Credit to Wes Eddy, Katy Kafantaris, Jeffrey Hayden, and Eric Knoblock for supporting this presentation package