NASA Office of Logic Design

NASA Office of Logic Design

A scientific study of the problems of digital engineering for space flight systems,
with a view to their practical solution.

2005 MAPLD International Conference

Staff Comments and Lessons Learned and Ideas for 2006

Facilities and Production

  1. Need to make room reservations a bit more formal between NASA, Infonetics, and RRB/ITC. (rk)

  2. Rockets

    1. Lunch in rocket garden was great, let's do it more (Wes)

    2. Need to coordinate equipment for rocket assembly just a bit more.  ;-) (rk)

  3. Reagan Building

    1. Vacuum and clean exhibit area each night

    2. Broken glass left on stage from previous event

    3. Reserved parking spots - GREAT (rk)

    4. Key for Meridian A - GREAT (rk)

    5. Bottled water, cold, by the chairman's table.  Speakers are getting dry mouth.

    6. Coffee

      1. Actually got compliments on the coffee

      2. More coffee in strategic locations

      3. Session G - have coffee, tea, and soft drinks available right there. (rk)

      4. Also several comment on coffee out there during the poster session. (we were supposed to have a break in the Amphitheater pre-function area for exactly this purpose, I didn't attend that, was in Session G).

  4. Infonetics

    1. Update invited registration form for media -- have to comply with policies.

    2. Door prizes -- only put names in bowl of people who signed up for dinner (assuming we do dinner again).

    3. put one line, 5 small text boxes, for registering people to write their paper numbers in. then we can sort and match must faster, better, and cheaper.

  5. Social Stuff

    1. Thursday night cocktail party in the Air and Space Museum and dinner speaker in the IMAX theater. (rk)

    2. Wednesday night "get together" social in the rocket garden.  Lots of finger foods, bar, light the place up with nice lighting.

    3. Designated Apollo table -- perhaps with a nice Saturn V model on it.

Sessions, Presentations, and Interesting Ideas for Program

  1. Device Qualification.  I'll try to figure out how to do that debate of customers vs. suppliers. Another debate that we were asked to do is what is needed to qualify new technology? Not only suppliers vs. customers but Customer A vs. Customer B, perhaps both of whom are in the same organization!

  2. New session on non-volatile memory?

  3. Reliability

  4. Design verification

  5. High performance reconfigurable computers
  6. Experiences with reconfigurable computing programming tools
  7. Standards issues, portability issues and tool issues (e.g., OpenFPGA approaches) related to FPGA boards and reconfigurable computing systems


  1. Spacewire 101 (Rakow)

  2. Radiation and Programmable Logic Devices  (Swift)

  3. Systems Safety and Embedded Computing Systems (Nancy)

  4. Verification Tutorial "Bruce Wiley" <> ???

  5. Real-Time Software and Operating Systems for Hardware Engineers

  6. Technical Data Analysis and Presentation (Tufte) carolyn williams, 203-250-7007,, minimum of 200 people @ $175/head.

Birds of a Feather

  1. Need to split BOF sessions to get more interaction between sessions. (Wes)

  2. Refine Session-W to include more case studies, some from outside the mil-aero community.  (Wes)

  3. Get Nancy to get aircraft and nuclear safety people for Session W verification? (rk)

  4. Session R - Reviewing aerospace designs.


  1. Have extra backdrops for lost or missing exhibits

  2. Have a backdrop for "outreach station"

  3. Publicize outreach effort

  4. Inputs from other centers for outreach

  5. Organize and publicize book signings.

Not sure where to put it - general

  1. Need panel discussion of Mission Systems Engineers from multiple centers about what PLD technologies they would accept for a variety of applications.  (Wes)  Perhaps part two of Session J? (rk)

  2. Need timers for speakers on Panels and BOF's.  Kitchen timers will work (rk).

  3. Facilities for book signings both at RRB/ITC and Air and Space Museum.


  1. All updates through

  2. Publish presentations earlier.

  3. Better, less ambiguous guidelines on file naming.

  4. Do not send .zip files

  5. .ppt strongly preferred

Panel: "Why Is Learning Lessons From Mishaps So Hard?" A Discussion of The Lessons Learned and Relearned with Recommendations for Breaking the Repetitive Cycle

Home - NASA Office of Logic Design
Last Revised: February 03, 2010
Digital Engineering Institute
Web Grunt: Richard Katz