1 / 12

FSW Organization Chart

FSW Organization Chart. Mission Project Office FSW Management E. Andrews. Project Manager (IPM) L. Klaisner. I&T Manager E. Bloom. Electronics & FSW Manager G. Haller. On-line, Test-Scripts R. Claus, S. Tuvi. FSW Management Support T. Schalk. FSW Lead J. J. Russell.

desmond-clear
Télécharger la présentation

FSW Organization Chart

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. FSW Organization Chart Mission Project OfficeFSW Management E. Andrews Project Manager(IPM)L. Klaisner I&T Manager E. Bloom Electronics & FSW ManagerG. Haller On-line, Test-Scripts R. Claus, S. Tuvi FSW Management Support T. Schalk FSW LeadJ. J. Russell FSW Independent Test-Team Lead M. Huffer Thermal ControlM. Monirzad AlgorithmsJ. J. Russell Tools K. Lo Configuration ManagerA. P. Waite S/C Interface D. Wood Test ExecutiveS. Maldonado Test TeamRama, Shanu (tbd) (tbd) LAT ConfigurationJ. Swain SoftwareArchitecturesA. P. Waite CalibrationJ. Swain Driver DevelopmentC. Brune Front End SimulatorsO. Saxton Cmd & TelemDatabaseB. Davis Boot/RAD750ProcessorR. Caperoon C&DHA.P. Waite DocumentationR. Morin

  2. Software planning (TS me) • Current activity (working on a roadmap) • Reviewing processes, issues, status • Evaluating re-baseline schedule (work in progress) • Establish metrics • Insertion of Demos and mini demos as milestones • monthly activity • Understand FS & mini tower status wrt FSW usage • Add people

  3. Software planning (TS me) • Major drivers • EM2 (may) • Build Integrates with Multiple Towers • ISIS (may) • Em2 base + more formal docs; testing; support • Start of FU hardware integration (I&T) july • FU • Dec 2004 –FU acceptance Testing • Feb 2005 – FU delivered to I&T for Instrument System Testing • Establish a CCB for FSW to control potential feature creep • (FSW Peer Review (2?)) • Navigate the extensive documentation and identify holes • QLR response

  4. QLR response / “plan” • Requirements • Completeness… control… traceability… tests • Mike DeKlotz CCB in place well before ISIS • Schedule • Reflect real work load (eg hardware testing) • Reflect real priorities for FU elements • Margins ? • With integrated milestones / demos • Expect updates to PMCS during Jan • Metrics • Useful to project –and- team • Resource usage • Testing (support & planning) • CCB and Reviews (including Jan EM2 peer review) • staffing

  5. Organization Status • Manpower issues • M. Monirzad ? • Test script writers • ISIS owner ? (remember this is more formal) • New people have a schedule impact both ways • Technical status • primary and secondary boot code • (pulled next page from QLR) • Code management tools (CMT CMX CVS) upgrades • Housekeeping design progress • Cmd and event server developments • LCB driver testing • Web access to existing docs

  6. Accomplished since CDR (5) • Primary boot of RAD750 (from “internal” RAD750 SUROM) • Integrated polled 1553 driver • Secondary boot of RAD750 (from “external” SIB EEPROM) • SIB EEPROM formatted, file system laid out • Performed successful communication test with the Spacecraft Instrument Interface Simulator (SIIS) provided by Spectrum Astro • Other tasks such as VxWorks upgrade, etc.

  7. Command & Telemetry Database • Three Pieces • Utility to capture & edit the information (python) • The information itself (xml files) • Software to respond to telecommand / generate telemetry (data stmts) • Utility • Prototyped a version allowing entry into a ‘neutral’ database • Will export in a variety of formats • ITOS • Autogen FSW code tables • Autogen documentation (web and full doc) • Test output in ITOS format sent to NRL to try on the SIIS • Information • Two extensives documents defining Telecommands/Telemetry for • File System / Memory Dumps / Task Status / Memory Usage • Critical Housekeeping information • Software • Critical Housekeeping gathering/reporting in design phase • To Do • Move utility from prototype to production quality code • Implement critical housekeeping code

  8. Near term activities (jan) • testing of EM1 Build • TRK/CAL/DAQ configuration • Event Filtering • Demonstration of flight crate boot • Demonstrate software control of GASU • Configuration • Control and readout • Table driven cmd server prototype • EM2 event server prototype • Housekeeping design & toy version of code

  9. Additional Tasks in next 3 Months • Design Internal LAT Software Communication Protocols • Communication task-to-task and CPU-to-CPU • Framework (mode control) • What commands can be sent in various modes • EM1 packages have been tested, but no formalized reports • EM1 packages were extensively tested before delivery to I&T • Detailed Unit testing of EM2 packages (uses EM1 packages) • Design Software watchdog • Support test-bed effort with software

  10. More short term tasks • Incorporate GASU/PDU/EPU code to complete software for test-bed • SIB thermal control/main power switch driver (minor, just register writes) • Service level software for EBM/AEM to be tested with hardware • Service level software for inter-task communication • Finish/test health/housekeeping code • Applications level software scheduled for EM2/FU • Testing

  11. PMCS next 2 months…

  12. PMCS next 2 months…

More Related