1 / 12

CRaTER SOC Operations

CRaTER SOC Operations. LRO MOR Section 10. Mr. Michael Golightly CRaTER Deputy Project Scientist Boston University. CRaTER SOC Overview. Housekeeping monitors. Realtime archive. MOC R/T. TCP. SSH. Raw archive. MOC DMP. PDIST. Secure web server. SCP. Uplink archive. MOC CMD.

goro
Download Presentation

CRaTER SOC Operations

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. CRaTER SOC Operations LRO MOR Section 10 Mr. Michael Golightly CRaTER Deputy Project Scientist Boston University LRO Mission Operations Review (MOR)

  2. CRaTER SOC Overview Housekeeping monitors Realtime archive MOCR/T TCP SSH Raw archive MOCDMP PDIST Secure web server SCP Uplink archive MOCCMD Pipeline Processing SCP Archive mirror PDS PPI node SCP Pipeline archive Archive for PDS SCP firewall LRO Mission Operations Review (MOR)

  3. CRaTER Software Component Status LRO Mission Operations Review (MOR)

  4. CRaTER SOC Functions • Uplink command generation (SCP to MOC, as needed) • Continuous real-time data collection (TCP from MOC) and display • Daily receipt of recorded data (SCP from MOC) • Daily pipeline processing • Daily quick-look analysis and trending; examine data gaps for existance of anomalous data loss • Daily report to SOC lead and MOC • Daily distribution to non-secure hosts (CRaTER internal server) • Daily review of system logs for evidence of attempted instrusions • Daily/weekly data back-ups to offline storage • Weekly SOC team meetings • Weekly processing & trending report and security inspection • Monthly archive collection and rearrangement • 3-monthly archive generation and transfer to PDS • Yearly security analysis and report • Anomaly response, e.g., replication on engineering unit or flight unit #2 LRO Mission Operations Review (MOR)

  5. CRaTER SOC Organization Project Manager1(Foster) Principal Investigator(Spence) Project Scientist(Kasper) DeputyProjectScientist(Golightly) ProjectEngineer(Goeke) SOCLead2(Ford) • GSE control S/W • Engineering display • Document reviews • Code reviews • Calibration algorithms • Conversion algorithms • Science display • On-orbit commanding • Pipeline software • Document preparation • LDWG/PDS Interfaces • Archive generation • IT security andhardware maintenance 1 MIT project management ends Dec 2007 2Golightly takes over as SOC Lead Jan 2008 LRO Mission Operations Review (MOR)

  6. CRaTER SOC Staffing SOC Operations Integration/Test Science AlgorithmImprovements/Evolution S/W Development/Maintenance Science Algorithms LRO Mission Operations Review (MOR)

  7. CRaTER Key Documentation Status LRO Mission Operations Review (MOR)

  8. To backup server BU NETWORK Logger console switch CRaTER LAN (BU) Crater-A mux Recorder Printer SOC-A SOC-B Crater-B A CRaTER Team Member’s LAN RAID 15x500 GB 2x500 GB 2x500 GB UPS Printer Locked cabinet in key-coded room External networks “Secure” LAN Disk access Multiplexed consoles “Semi-open” LANs Power supply CRaTER SOC Hardware Facilities LRO Mission Operations Review (MOR)

  9. CRaTER Engineering Unit • The SOC will maintain a CRaTER engineering unit† and associated 1553 interface (S/C simulator) to assist in the diagnosis of post-delivery problems with the flight unit. • SOC staff will interact with the simulator via a UDP interface to the following set of software programs • Graphical command interface • Output capture to disk • Analog housekeeping display • User status display • Primary science stats display • Output conversion to ASCII 28VDC CRaTEREngineeringUnit Spacecraft 1553B Emulator Internet(UDP) 2 x 1553,1 Hz tick Example: send commands to the engineering unit and monitor the resulting housekeeping channels [1] Start the graphical command interface: host# CCmd & [2] Start the graphical housekeeping interface host# CHouse & † the CRaTER flight spare can also be used in place of the engineering unit, e.g., to assist in flight-unit recalibration LRO Mission Operations Review (MOR)

  10. CRaTER Software Maintenance • Operating system maintenance • SOC-A, SOC-B, Crater-A, Crater-B, and Crater-Devel • Redhat Linux—updates provided under 3-year maintenance contract with Redhat • SOC Operations Lead responsible for applying updates/patches • Pipeline code development/modifications • Through start of instrument I&T: MIT/Ford, BU/Bradford • After start of instrument I&T: BU/Bradford, BU/Wilson • Configuration Control • Code version control maintained under Subversion version control system (http://subversion.tigris.org/) • Copies of all implemented version will be maintained under version control in case it is necessary to roll-back to an earlier version • System stability/integrity carefully controlled during all upgrades • Code development/testing done outside SOC on Crater-Devel • User manuals, installation guides, code reference manuals, etc must be updated and released with new versions/changes to existing software • Changes to operating system, pipeline, or science software implemented in sequence of distinct steps • Install changes/updates on Crater-Devel--test for compatibility, stability, & functionality; • Install on the appropriate backup machine (e.g., machine-B if machine-A prime, etc)--test for compatibility, stability, & functionality; • Switch backup machine to prime, and prime to backup (e.g., machine-B → prime, machine-A → backup) • Install on remaining machine--test for compatibility, stability, & functionality. • NO FLIGHT INSTRUMENT SOFTWARE LRO Mission Operations Review (MOR)

  11. CRaTER Software Testing • The Test Plan is directly derived from the following documents: • 32–01209 CRaTER SOC Requirements Document • 32–01208 CRaTER IT Security and Contingency Plan subject to the constraints identified in the following: • 32–01210 CRaTER Data Management and Archive Plan • 32–01211 CRaTER Standard Product Software Interface Specification • 32–02080 CRaTER Science Team and the PDS PPI Node ICD • 431–ICD–000049 External Systems ICD for the LRO Ground System • The Traceability Matrix identifies 40 separate requirements: • 13 functional — the basic operations expected from the SOC • 10 design — requirements imposed by external constraints • 10 performance — ability of the s/w and human interfaces to do the job • 7 security — factors that protect the system from unintended behavior which are verified by a set of 10 tests, using various methodologies: • 5 by explicit test — did the system pass the prescribed procedural test? • 3 by demonstration — did the system produce the expected results? • 1 by analysis — are the algorithms adequate to the task? • 1 by inspection — are the planned resources available? LRO Mission Operations Review (MOR)

  12. CRaTER SOC Development Status Current Status • Hardware (5 processors, RAID storage, etc.) is being assembled • Documentation deliveries are up-to-date • Pipeline Software (Levels 0, 1, 2) is written and is under review • Standard product SIS is under review by the PDS PPI node • Engineering Unit interface is built and tested • Draft SOC test plan is out; individual test scripts are being written • Draft calibration plan has been released • SOC is fully staffed (except for students) Future Tasks • Place SOC software under configuration control • Erect network firewall around secure SOC hardware • Complete SOC testing, including SOC-MOC and SOC-PDS tests • Conduct SIS peer review by PDS PPI node LRO Mission Operations Review (MOR)

More Related