The SpaceNet Integrated Database serves as a repository for both modeling and simulation data, and real-time logistics data. Modeling and simulation data include both inputs for the simulation and optimization model, and outputs. Real-time logistics data captures asset and inventory location, status, shipping/storage environment information, and history. The database was developed based on various use cases derived from the needs of professionals in the logistics community.
Design & Structure
The SpaceNet Integrated Database contains nearly 50 primary tables, with a "master" table describing the ten Classes of Supply used in SpaceNet. The database tables are structured according to a relational model, which allows complex queries to be constructed and executed. The database in SpaceNet 1.3 is implemented in Excel, while the database in SpaceNet 2.0 (standalone JAVA/webstart version) is implemented as a relational database in SQL. The main tables in the relational database are discussed in Appendix B of the SpaceNet 1.3 User Manual.
While a complete description of each table is too lengthy for this website, we can describe some tables and clusters of tables that play an important role in organizing the large amount of information that can be stored.
- Physical Nodes—describes the static nodes available to SpaceNet. Static nodes may be terrestrial or destination surface nodes, particular orbits, or Lagrange points.
- Astro—describes the available paths (trajectories) between the static nodes. Multiple paths may be available that allow a tradeoff of delta-V for time-of-flight.
- Scenario Inputs—captures scenarios (campaigns or just single missions), time-ordered processes, and associated elements in a way that enables reconstruction of any scenario previously saved in SpaceNet.
- Supply and Demand Inputs—captures cargo (by Class of Supply) usage rates along paths and demands at each static node over time for a given scenario.
- Scenario Outputs—captures simulated histories of elements, nodes, and cargos by Class of Supply.
- Element Type—describes the overall physical and performance properties of each generic major end-item. Physical properties include mass and dimensions. Performance properties depend on the element type. Propulsion elements, for example, are characterized by Isp, usable propellant, etc. Carriers are characterized by the mass and volume they can hold. A separate table tracks each instantiation of an element type.
- Supply Item Type—describes the overall physical, logistics, and procurement properties of each generic item type that makes up a particular Class of Supply. Physical properties include mass and volume. Logistics parameters include shelf life, shipping and storage data, hazard and disposal data. Procurement data includes price, procurement type, source, and lead-time. A separate table tracks each instantiation of a supply item type.
- Class-of-Supply-Centric Data—enables predictions of usage, consumption, or loss rates for each SpaceNet scenario. For example, MTBFs for identified ORUs/SRUs are captured in tables devoted to spares. Data in these tables are used to calculate scenario supply and demand inputs for each Class of Supply.