AS DESCRIBED IN THE RESEARCH TRAINING PLAN (RTP) THE FIRST STEP WAS TO ESTABLISH A HISTORICAL DATABASE FROM WHICH MISSION PARAMETERS AND SIMULATION FILES CAN BE EXTRACTED AND ANALYZED. THE DATABASE MANAGEMENT SYSTEM SELECTED WAS AN OBJECT-RELATIONAL DATABASE MANAGEMENT SYSTEM (ORDMS). SUCH DATABASE PROVIDES A BRIDGE BETWEEN RELATIONAL AND OBJECT-ORIENTED PARADIGMS. THE STANDARD SELECTED FOR MANAGING INFORMATION IN THE DATABASE IS THE STRUCTURED QUERY LANGUAGE (SQL) AND IS IMPLEMENTED THROUGH THE POSTGRESQL SOFTWARE. THE RESULTING DATABASE WAS BUILT IN PYTHON USING THE SQLALCHEMY TOOLKIT AND SERVED AS AN INTERFACE BETWEEN THE DATABASE AND POSTGRESQL. ONE OF THE FIRST STEPS FOR IMPLEMENTING THE DATABASE MODEL WAS TO DEFINE THE OBJECTS (TABLES) AND THE RELATIONSHIPS BETWEEN THEM IN THE DATABASE. IDEALLY WE WANT OBJECTS IN THE DATABASE TO CONTAIN DESCRIPTIONS OF EACH MISSION AND ACCESS DATA OF INTEREST DURING DIFFERENT EVENTS IN THE EDL SEQUENCE. ORIGINALLY THE DATABASE WAS DIVIDED BY THREE SEGMENTS: ENTRY DESCENT AND LANDING. HOWEVER THIS MODEL WAS DISCARDED GIVEN THAT STAGES SUCH AS PARACHUTE DESCENT AND POWERED DESCENT ARE NOT NECESSARILY EXCLUSIVE TO THE DESCENT CLASS FOR EXAMPLE. WITH THIS A NEW LAYOUT SCHEMA (FIGURE 1) WAS CREATED WHICH DIVIDES THE MISSION INTO ENTRY PARACHUTE DESCENT POWERED DESCENT AND TOUCHDOWN. THIS REMOVES ANY CONSTRAINTS ON PARAMETERS THAT MAKE THEM EXCLUSIVE TO A GIVEN SEGMENT.