This data base is essential for all concept development work.Key transportation attributes were derived based on data provided in each of the market areas. Theoretically, the goal is to provide a system which meets all of the attributes for all of the market areas. In practice this is often difficult because the users' needs may vary significantly.
After reviewing the initial list of attributes it became evident that there was a core set of attributes which were common to many, or in some cases all, of the market areas. Some of the more common attributes are shown in Figure A.1-1 below.
| Category | Attribute |
| Dependability | High Probability of Launching on Schedule |
| Schedule | Minimum Advanced Booking Time |
| Reliability | equal to or greater than Current System |
| Cost | Minimum Cost Per Launch |
| Operations | Standardized and Simplified Payload Interfaces |
| Capabilities | Support Multiple Payload Classes Provide Delivery to Multiple Destinations Provide On-Orbit Rendezvous and Docking Capabilities Provide Delivery and Return Capabilities |
| Availability | High Probability System Will Be in An Operational Rather Than a Standdown State |
| Responsiveness | Minimum Response Time for Launching On Need |
The booking time requirement varied by market area and the values ranged from 1 month to 18 months. The potential range of values are plotted as shown in Figure A.1-2 below. For each booking time value, we determine what percentage of the markets can be captured and what percentage of the revenue these markets represent. The percentage of revenue captured is based on the flight costs ($/lb).
This figure shows that a system with a 6 month window captures 77% of the market areas and 90% of the potential revenue at both $1000/lb and $400/lb. The $400/lb system is very sensitive to booking times greater than 6 months. It is evident that a majority of the flights in the key market areas cannot tolerate longer booking times. Thus, 6 months appears to be a reasonable value for the initial system requirement.
Segment | 3.1 Communications |
Market Area | 3.1.3 Fixed Satellite Services |
| Attributes | |
| Dependability | High probability of launching on schedule |
| Responsiveness | Minimal response time for launching on need (Note: Need to determine if launch on need is necessary) |
| Availability | High probability that the system will be in an operational rather than a standdown state |
| Schedule | Minimize advanced booking time Maximize launch window size |
| Reliability | Higher than current systems (US and foreign) |
| Cost | Minimum cost per launch |
| Capabilities | Multiple orbital delivery locations Adaptable to market needs, with a clear growth path GEO medium-large satellites |
| Operations | Provide standardized user interfaces User friendly launch site operations Rapid payload changeout capability |
GEO. The system shall have the capability of delivering a single payload weighing between 3,000 and 7,000 lbs into a GEO orbit(s) of TBD at inclination(s) of TBD.
System Requirements
Dependability. The system shall have a 90% (TBR) probability of conducting launches within 10 days of their scheduled dates. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies.
Launch on Need. The system shall not require more than 30 days between notification and launch for launch on need missions. (Note: Need to determine if LON applies to this market area.)
Availability. The system must maintain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather than standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Mission Scheduling. Payloads can be scheduled for flight with 18 months notice.
Launch Window. The system shall maximize the payload launch windows. (TBD matrix will show inclination, destination (GEO), and window size)
Reliability. The system must deploy payloads to their intended mission orbits with a total success probability of at least 0.98. This includes reliability of the launch vehicle and the upper stage ( if used).
System Growth. The system shall emphasize modularity to accommodate adaptability and growth to meet changing market needs.
Vehicle Requirements
Payload Volume. The system must accommodate payloads comparable to current volumes up to 2x current volumes (Note: Need to translate current volumes into length and diameter dimensions)
Payload Interface. The system shall provide TBD standardized payload interfaces with which the payloads must conform.
Operations Requirements
Launch Rate. The sytem must support an annual launch rate between 20 and 31 . (Note: This is extracted from December 93 Results. Assumes number of satellites equals the number of launches for the period 2005 to 2010. This needs to be verified.)
Payload Changeout Capability. To enhance system flexibility, the system must allow payload changeout (of the same payload) up to five days prior to launch and payload changeout (to a different payload) up to 30 days prior to launch. Payload replacement shall be completed within 5 days. Following the payload replacement, the launch system shall be at the same number of days before launch as when the payload change notification was received.
Payload Integration. Payload integration must be greatly simplified in comparison to current operations. This refers to the difficulty of the operations, standardization of integration procedures, the time required to perform the operation, and the number of personnel required.
Payload Access. The system will provide hands on access to their payload before the shroud is installed and limited access through a TBD stand fairing access in the launch vehicle integration facility, and no access after leaving the launch vehicle integration facility. There will be a maximum of two days (TBR) between the last payload access in the launch vehicle integration facility and launch.
Segment | 3.1 Communications |
Market Area | 3.1.4 Broadcast Satellite Service |
| Attributes | |
| Dependability | High probability of launching on schedule |
| Responsiveness | Minimal response time for launching on need (Note: Need to determine if launch on need is necessary) |
| Availability | High probability that the system will be in an operational rather than a standdown state |
| Schedule | Minimize advanced booking time Maximize launch window size |
| Reliability | Higher than current systems (US and foreign) |
| Cost | Minimum cost per launch |
| Capabilities | Multiple orbital delivery locations Adaptable to market needs, with a clear growth path GEO medium-large satellites |
| Operations | Provide standardized user interfaces User friendly launch site operations Rapid payload changeout capability |
GEO. The system shall have the capability of delivering a single payload weighing between 3,000 and 7,000 lbs into a GEO orbit(s) of TBD at inclination(s) of TBD.
System Requirements
Dependability. The system shall have a 90% (TBR) probability of conducting launches within 10 days of their scheduled dates. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies.
Launch on Need. The system shall not require more than 30 days between notification and launch for launch on need missions.
Availability. The system must maintain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather than standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Mission Scheduling. Payloads can be scheduled for flight with 18 months notice.
Launch Window. The system shall maximize the payload launch windows. (TBD matrix will show inclination, destination (GEO), and window size)
Reliability. The system must deploy payloads to their intended mission orbits with a total success probability of at least 0.98. This includes reliability of the launch vehicle and the upper stage ( if used).
System Growth. The system shall emphasize modularity to accommodate adaptability and growth to meet changing market needs.
Vehicle Requirements
Payload Volume. The system must accommodate payloads comparable to current volumes up to 2x current volumes (Note: Need to translate current volumes into length and diameter dimensions)
Payload Interface. The system shall provide TBD standardized payload interfaces with which the payloads must conform.
Operations Requirements
Launch Rate. A nominal launch rate of at least 2-3 (TBR) missions per year is required to satisfy the direct broadcast missions.
Payload Changeout Capability. To enhance system flexibility, the system must allow payload changeout (of the same payload) up to five days prior to launch and payload changeout (to a different payload) up to 30 days prior to launch. Payload replacement shall be completed within 5 days. Following the payload replacement, the launch system shall be at the same number of days before launch as when the payload change notification was received.
Payload Integration. Payload integration must be greatly simplified in comparison to current operations. This refers to the difficulty of the operations, standardization of integration procedures, the time required to perform the operation, and the number of personnel required.
Payload Access. The system will provide hands on access to their payload before the shroud is installed and limited access through a TBD stand fairing access in the launch vehicle integration facility, and no access after leaving the launch vehicle integration facility. There will be a maximum of two days (TBR) between the last payload access in the launch vehicle integration facility and launch.
Segment | 3.1 Communications |
Market Area | 3.1.5 Mobile Satellite Service |
| Attributes | |
| Dependability | High probability of launching on schedule |
| Responsiveness | Minimal response time for launching on need (Note: Need to determine if launch on need is necessary) |
| Availability | High probability that the system will be in an operational rather than a standdown state |
| Schedule | Minimize advanced booking time Maximize launch window size |
| Reliability | Higher than current systems (US and foreign) |
| Cost | Minimum cost per launch |
| Capabilities | Adaptable to market needs, with a clear growth path System can accommodate multiple payloads per launch Multiple orbital delivery locations |
| Operations | Provide standardized user interfaces User friendly launch site operations Rapid payload changeout capability |
LEO. The system shall deliver between 16,500 lbs and 150,000 lbs per year to LEO orbits of < 1,000 nmi with inclinations from 55 degrees to 98.6 degrees.
Co-manifested Payloads. The system must be capable of delivering multiple (TBR) satellites per launch. Each satellite may weigh up to 3,000 lbs.
System Requirements
Dependability. The system shall have a 90% (TBR) probability of conducting launches within 10 days of their scheduled dates. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies.
Launch on Need. The system shall not require more than 30 days between notification and launch for launch on need missions.
Availability. The system must maintain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather than standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Mission Scheduling. Payloads can be scheduled for flight with as little as 18 months lead time.
Launch Window. The system shall maximize the payload launch windows. (TBD matrix will show inclination, destination, and window size)
Reliability. The system must deploy payloads to their intended mission orbits with a total success probability of at least 0.98. The includes reliability of the launch vehicle and the upper stage ( if used).
System Growth. The system shall emphasize modularity to accommodate adaptability and growth to meet changing market needs.
Vehicle Requirements
Payload Interface. The system shall provide TBD standardized payload interfaces with which the payloads must conform.
Payload Volume. The system must accommodate payloads up to TBD feet in diameter and length up to TBD feet.
Operations Requirements
Launch Rate. A nominal launch rate of TBD missions per year is required to satisfy the mobile communication missions.
Payload Changeout Capability. To enhance system flexibility, the system must allow payload changeout (of the same payload) up to five days prior to launch and payload changeout (to a different payload) up to 30 days prior to launch. Payload replacement shall be completed within 5 days. Following the payload replacement, the launch system shall be at the same number of days before launch as when the payload change notification was received.
Payload Integration. Payload integration must be greatly simplified in comparison to current operations. This refers to the difficulty of the operations, standardization of integration procedures, the time required to perform the operation, and the number of personnel required.
Payload Access. The system will provide hands on access to their payload before the shroud is installed and limited access through a TBD stand fairing access in the launch vehicle integration facility, and no access after leaving the launch vehicle integration facility. There will be a maximum of two days (TBR) between the last payload access in the launch vehicle integration facility and launch.
Segment | 3.1 Communications |
Market Area | 3.1.6 Positioning Satellite Services |
| Attributes | |
| Dependability | High probability of launching on schedule |
| Responsiveness | Minimal response time for launching on need (Note: Need to determine if launch on need is necessary) |
| Availability | High probability that the system will be in an operational rather than a standdown state |
| Schedule | Minimize advanced booking time Maximize launch window size |
| Reliability | Higher than current systems (US and foreign) |
| Cost | Minimum cost per launch |
| Capabilities | Adaptable to market needs, with a clear growth path LEO and MEO small-medium satellites Multiple orbital delivery locations |
| Operations | Provide standardized user interfaces User friendly launch site operations Rapid payload changeout capability |
LEO and MEO. The system shall have the capability of placing payloads weight between current GPS mass and 2x current GPS mass into a TBD orbit at an inclination of TBD. (Note: The GPS system mass needs to be quantified)
System Requirements
Dependability. The system shall have a 90% probability of launching within one month of the scheduled date. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies. (Note: the one month value does not appear to reflect the urgency of launching on schedule which was reflected in early data. Need to verify that this is sufficient to meet needs, including need of replacing failed on orbit assets.)
Launch on Need. The system shall not require more than 30 days between notification and launch for launch on need missions.
Availability. The system must maintain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather than standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Mission Scheduling. Payloads can be scheduled for flight with as little as 3 months lead time.
Launch Window. The system shall maximize the payload launch windows. (TBD matrix will show inclination, destination , and window size)
Reliability. The system must deploy payloads to their intended mission orbits with a total success probability of at least 0.98. This includes reliability of the launch vehicle and the upper stage ( if used).
System Growth. The system shall emphasize modularity to accommodate adaptability and growth to meet changing market needs.
Vehicle Requirements
Payload Volume. The vehicle must accommodate payloads up to TBD feet in diameter and length up to TBD feet.
Payload Interface. The system shall provide TBD standardized payload interfaces with which the payloads must conform.
Operations Requirements
Launch Rate. A nominal launch rate of TBD missions per year is required to satisfy the survey and locate missions. This rate includes 2-5 annual missions for the GPS market.
Payload Changeout Capability. To enhance system flexibility, the system must allow payload changeout (of the same payload) up to five days prior to launch and payload changeout (to a different payload) up to 30 days prior to launch. Payload replacement shall be completed within 5 days. Following the payload replacement, the launch system shall be at the same number of days before launch as when the payload change notification was received.
Payload Integration. Payload integration must be greatly simplified in comparison to current operations. This refers to the difficulty of the operations, standardization of integration procedures, the time required to perform the operation, and the number of personnel required.
Segment | 3.2 Space Manufacturing |
Market Area | 3.2.2 Space Manufacturing |
| Attributes | |
| Dependability | High probability of launching on schedule |
| Responsiveness | Minimal response time for launching on need (Note: Need to determine if launch on need is necessary) |
| Availability | High probability that the system will be in an operational rather than a standdown state |
| Schedule | Minimize advanced booking time |
| Reliability | Comparable to or better than current systems |
| Cost | Minimum cost per launch |
| Capabilities | Provide launch, orbital servicing and recovery capabilities |
| Operations | Provide airline type operations Provide launch facilities and recovery site facilities Provide rapid turnaround technologies and processing facilities |
Destination Orbit. The launch system shall deliver a maximum of 4500 lbs to a TBD sun synchronous polar orbit at 98 degrees.
Rendezvous and Docking. The system shall be capable of performing on orbit rendezvous and docking operations.
Return Capability. The recovery module and 3000 lbs of product. shall be returned to earth.
System Requirements
Dependability. The system shall have a 90% (TBR) probability of conducting launches within 1 day of the scheduled dates. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies.
Availability. The system must maintain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather than standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Mission Scheduling. Payloads can be scheduled for flight with 4 months notice.
Launch Window. The system shall maximize the payload launch windows. (TBD matrix will show inclination, destination, and window size)
Reliability. The system must deploy payloads to their intended mission orbits with a total success probability of at least 0.98. This includes reliability of the launch vehicle and the upper stage ( if used).
System Growth. The system shall emphasize modularity to accommodate adaptability and growth to meet changing market needs.
Vehicle Requirements
Payload Volume. The system must accommodate payloads up to 75 ft3.
Payload Interface. The system shall provide TBD standardized payload interfaces with which the payloads must conform.
Delivery Accuracy. The system shall provide TBD delivery accuracy.
Electrical Power. The system will provide a TBD orbital asset which maximizes the electrical power available for microgravity processing. Electrical power needs are estimated at 20 kW.
Orbiting Service Module. The system will provide an orbiting service module equipped with autonomous microgravity processing capabilities. These capabilities will be used to support the manufacture of electronic, photonic and detector materials, ultra-high vacuum processing, biological and organic materials processing and the support of research subunits for microgravity activities. The capabilities will include monitor and control facilities for each processing activity.
The service module will be design for 5 year on orbit operations and shall be configured with standard guidance, navigation and control functions, automated rendezvous and docking functions, command and communication functions, environmental control capability, high on-board continuous power system, an autonomous product module exchange facility for on-load/off-load of product material subunits.
Recovery Module. The system shall provide a recovery module which provides controlled on orbit maneuvering and autonomous rendezvous and dock capabilities with the service module.The recovery module shall be designed for reentry and recovery operations.
Operations Requirements
Launch Rate. The sytem must support at least one launch every 30 days.
Payload Integration. Payload integration must be greatly simplified in comparison to current operations. This refers to the difficulty of the operations, standardization of integration procedures, the time required to perform the operation, and the number of personnel required. The system shall integrate between 20-30 subunits of individual product/containment modules for each launch. The system shall integrate pre-certified payloads. The payloads will conform to predetermined commercial Federal space regulations and shall not require individual government controlled safety reviews.
Payload Access. The payloads require late access of 12 hour for selected subunits.
Payload Unique Environment. The TBD Payload unique requirements will be addressed by use of an adapter system or self-contained servicing support sytem.
Routine Space Access. The system shall provide routine access to space, similar to flight travel opportunities offered by the commercial airline industries.
Automated Operations. The system shall emphasize automated payload launch processing, on orbit processing and processed sample return. Use of man in the system must be eliminated or minimized. Provide regular routine flights dedicated to material process
Space Operations. The system shall provide a minimum of 30 days and a maximum of 90 days in the orbital microgravity environment.
Recovery Facilities. The system shall provide, maintain, and operate the recovery site facilities. The system shall provide post flight delivery of processed samples or products to a recovery facility.
Refurbishment Operations. The recovery modules shall be refurbished on a routine basis.
Segment | 3.3 Remote Sensing |
Market Area | 3.3.2 Remote Sensing |
| Attributes | |
| Dependability | TBD |
| Responsiveness | Provide launch on need capability to replace failed satellite |
| Availability | High probability that the system will be in an operational rather than a standdown state |
| Schedule | Minimize advanced booking time |
| Reliability | Higher than current systems (US and foreign) |
| Cost | Minimum cost per launch |
| Capabilities | Launch commercial satellites, U.S. govt. satellites, and international satellites Accurate placement in polar orbits. High precision trajectories with final trim capabilities Provide fail safe modes |
| Operations | Provide standardized user interfaces Provide integration and test facilities to satellite operators Provide technical support to satellite operators Provide streamline regulations, procedures, paperwork, and requirements for payloads |
| Mass (kg) | Orbit | Primary User(s) |
| 200 - 500 | Low Earth Polar Orbit | Commercial, US Govt |
| 900 - 1,400 | Low Earth Polar Orbit | Comm, US Govt, Intl |
| 1,500 - 2,200 | Low Earth Polar Orbit | US Govt, Intl |
| 2,400 - 2,800 | Low Earth Polar Orbit | US Govt, Intl |
| 5,000 - 6,000 | Low Earth Orbit | US Govt |
| 700 - 2,400 | Geostationary | US, Intl |
System Requirements
Dependability. The system shall have a 90% (TBR) probability of conducting launches within a month of their scheduled dates. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies. (Note: There is a concern that one month is not consistent with the urgency of launch on schedule expressed in the report. Need to clarify that this is sufficient or reduce to an acceptable level.)
Launch On Need. The system must be capable of launching a replacement satellite within 15 days of a failed satellite.
Availability. The system must maintain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather than standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Scheduling. New payloads can be scheduled for flight with 3-6 months lead time. (Note: 3-6 months is referred to in the final report and 12 months is documented in the requirements matrix put together in December 93 at Langley.)
Reliability. The system must provide an ascent reliability, or probability of success, of .99 System Growth. The system shall emphasize modularity to accommodate adaptability and growth to meet changing market needs.
Vehicle Requirements
Payload Interface. The system shall provide TBD standardized payload interfaces with which the payloads must conform. The separation interface between the vehicle and the payload will use marmon clamps.
Payload Volume. The first generation of commercial space sensors require payload volumes of 3-6 m3. The system must accommodate payloads which range from current (TBD) up to 2x current. (Note: We need to be more specific and indicate lengths and diameters. It is also unclear if this is meant to include commercial, Govt, and Intl. payloads or if this pertains to some specified subset of users.)
Fail Safe Design. Design shall provide for a fail safe mode which allows the vehicle to sustain a failure and successfully complete its mission.
Delivery Accuracy. The system shall provide TBD accuracy for placement of satellites in polar orbits
Launch Environment. The maximum vehicle acceleration shall not exced 8Gs.
Operations Requirements
Launch Rate. The system launch rate must be adequate to deploy TBD % of the remote sensing satellites. Annual projections from 2000 to 2010 are shown in the table below.
| Deployment Year | |||
| 00 | 05 | 10 | |
| Total | 10 | 12 | 18 |
| Commercial | 3 | 4 | 6 |
| Govt/Intl. | 7 | 8 | 12 |
User Support. The system must provide technical support and make integration and test facilities available to the user.
Payload Integration. Payload integration must be greatly simplified in comparison to current operations. This refers to the difficulty of the operations, standardization of integration procedures, the time required to perform the operation, and the number of personnel required.
Payload Access. The system will provide hands on access to their payload before the shroud is installed and limited access through a TBD stand fairing access in the launch vehicle integration facility, and no access after leaving the launch vehicle integration facility. There will be a maximum of two days (TBR) between the last payload access in the launch vehicle integration facility and launch.
Segment | 3.4 Government Missions |
Market Area | 3.4.2 Government Missions |
| Attributes | |
| Dependability | High probability of launching on schedule |
| Responsiveness | Minimum response time for launching on need |
| Availability | High probability that the system will be in an operational rather than a standdown state |
| Schedule | Minimize advanced booking time |
| Reliability | High reliability |
| Cost | Minimum cost per launch Minimum payload integration cost to facilitate changeovers from other systems |
| Capabilities | Provide transportation for civil and DoD missions Accommodate more than one payload per launch (Note: Need to verify this. It was not mentioned in final report inputs) |
| Operations | Provide standardized user interfaces |
Mission classes. The system shall deliver payloads in the following mission classes: 1) 8,000-10,000 lbs to GTO and up to 12,500 lbs to GSO, 2) 18,000-20,000 and up to 40,000 lbs to LEO due East, 3)14,000-16,000 lbs and up to 32,000 lbs to polar orbits. (Note: Need to clarify wording and intent of (2) and (3). This wording was extracted from the final report inputs).
System Requirements
Dependability. The system shall have a 90% (TBR) probability of conducting launches within 10 days of their scheduled dates. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies. (Note: 10 days is based on recent ALS efforts, but requirements matrix of December 1993 from Langley meetings uses a month. Need to clarify numerical value).
Launch on Need. The system shall not require more than 30-45 (TBR) days between notification and launch for launch on need missions.
Availability. The system must maintain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather than standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Mission Scheduling. Payloads can be scheduled for flight with as little as 18 months lead time.
Launch Window. The system shall maximize the payload launch windows. (TBD matrix will show inclination, destination, and window size).
Reliability. The system must deploy payloads to their intended mission orbits with a total success probability of at least 0.98. The includes reliability of the launch vehicle and the upper stage ( if used).
System Growth. The system shall emphasize modularity to accommodate adaptability and growth to meet changing market needs.
Vehicle Requirements
Payload Interface. The system shall provide TBD standardized payload interfaces with which the payloads must conform.
Payload Volume. The system must accommodate payloads up to TBD feet in diameter and length up to TBD feet.
Operations Requirements
Launch Rate. A nominal launch rate of 8 missions per year from the East coast and 4 mission per year from the West coast is required to satisfy the government missions.
Payload Changeout Capability. To enhance system flexibility, the system must allow payload changeout (of the same payload) up to five days prior to launch and payload changeout (to a different payload) up to 30 days prior to launch. Payload replacement shall be completed within 5 days. Following the payload replacement, the launch system shall be at the same number of days before launch as when the payload change notification was received.
Payload Integration.Payload integration must be greatly simplified in comparison to current operations. This refers to the difficulty of the operations, standardization of integration procedures, the time required to perform the operation, and the number of personnel required.
Payload Access. The system will provide hands on access to their payload before the shroud is installed and limited access through a TBD stand fairing access in the launch vehicle integration facility, and no access after leaving the launch vehicle integration facility. There will be a maximum of TBD days between the last payload access in the launch vehicle integration facility and launch.
Segment | 3.4 Government Missions |
Market Area | 3.4.4 Increased Space Station Missions |
| Attributes | |
| Dependability | High probability of launching on schedule |
| Responsiveness | Minimum response time for launching on need |
| Availability | |
| Schedule | Minimize advanced booking time to provide rapid access to space |
| Reliability | Higher than current STS system |
| Cost | Minimum cost per launch |
| Capabilities | Deliver payloads to Space Station Return payloads from Space Station to earth Frequent resupply capability Provide civilian access to space |
| Operations | Provide streamlined regulations, procedures, paperwork, and requirement for payloads Improved ground processing for quick refurbishment and turn-around Late access to payloads prior to launch and early access to payloads returning to earth |
Rendezvous and Docking. The system shall accomplish rendezvous and cargo delivery to Space Station.
Return Capability. The system shall be designed to return experiments to earth. The launch system will meet TBD vibration, temperature, cleanliness, and data requirements.
Manned Capability. The system shall provide for delivery of people to station and return of people to earth.
System Requirements
Dependability. The system shall have a 90% (TBR) probability of conducting launches within one month of the scheduled dates. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies.
Launch on Need. The system shall not require more than 30 (TBR) days between notification and launch for launch on need missions.
Availability. The system must maintain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather than standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Mission Scheduling. Payloads can be scheduled for flight with 18 months notice.
Launch Window. The system shall maximize the payload launch windows. (TBD matrix will show inclination, destination, and window size).
Reliability. The system shall have a higher reliability (relative to STS) for delivery and return of persons and high value payloads.
System Growth. The system shall emphasize modularity to accommodate adaptability and growth to meet changing market needs.
Vehicle Requirements
Payload Volume. The system must accommodate payloads up to TBD ft3.
Payload Interface. The system shall provide TBD standardized payload interfaces with which the payloads must conform.
Operations Requirements
Launch Rate. The sytem must support 7-12 annual launchs.
Payload Integration. Payload integration must be greatly simplified in comparison to current STS operations. This refers to the difficulty of the operations, standardization of integration procedures, the time required to perform the operation, and the number of personnel required.
Payload Access. The system shall provide for late access, less than 72 hours (TBR), to payloads prior to launch and for early access, less than 72 hours (TBR), to payloads upon return to earth.
Payload Unique Environment. The system or a system provided adapter kit must provide sufficient power (TBD) and thermal capabilities (TBD) to meet the payload demands
Ground Processing. The system shall provide improved (relative to STS) ground processing for quicker refurbishment andturn around.
Segment | 3.4 Government Missions |
Market Area | 3.4.6 Human Planetary Exploration |
| Attributes | |
| Dependability | High probability of launching on schedule |
| Responsiveness | Provide launch on need capabilities to support contingency operations |
| Availability | High probability that the system will be in an operational state rather than a standdown state |
| Schedule | Minimize advanced booking time Maximize launch windows |
| Reliability | Significantly higher than current systems (to support human rating) |
| Cost | Minimum cost per launch |
| Capabilities | Adaptable, with clear growth path which takes advantage of previous efforts in other markets Deliver crew and cargo to lunar and Mars surfaces Return crew and cargo to earth Support extended surface stay Provide launch and return capability any day during lunar cycle (Note: Need an attribute for launch and return capabilities for Mars) Delivery to multiple landing sites |
| Operations | Provide standardized user interfaces Minimize operational impact to users Support rapid cargo changeout capabilities |
| Human Rating | Provide capability for crew ingress, egress, and escape as necessary to support human payload launches |
Mars System Capability. The system shall be designed to deliver a crew of TBD and TBD tons of cargo or TBD tons of cargo alone to the surface of Mars.
Surface Stay Time. The system shall be designed for a TBD-day lunar surface stay and a TBD-day Mars surface stay.
Cargo Return Capability. The system shall be designed to return TBD kg from the lunar surface and TBD kg from Mars.
Manned Flights. Support manned missions by the year TBD.
Rendezvous and Docking. The system shall be capable of performing on orbit rendezvous and docking operations.
System Requirements
Dependability. The system shall have a 90% (TBR) probability of conducting launches within 1 day of their scheduled dates. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies.
Availability. The system must sustain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather than standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Launch Window. The system shall maximize the payload launch windows. TBD minutes for lunar missions and TBD minutes for Mars missions.
Mission Scheduling. Payloads can be scheduled for flight with as little as 18 months lead time.
Reliability. TBD
Commonality. System shall emphasize commonality with hardware, software, and operations which have been previously developed to fulfill other market areas and segments.
Vehicle Requirements
Payload Interface. The system shall provide TBD standardized payload interfaces with which the payloads must conform.
Payload Volume. The system must accommodate payloads up to 30 feet in diameter and length up to 100 feet.
Operations Requirements
Launch Rate. Minimum nominal launch rate shall be 4 (TBR) per year with growth to accommodate TBD flight per year by TBD. (Note recent STV efforts used 4 with growth, but the requirements matrix uses a low of 1-2 and a high of 4. This needs to be resolved.)
Facilities. The operations and processing facilities shall be designed in parallel with the vehicle system to achieve more efficient, reliable operations involving fewer people and shorter launch schedules.
Cargo Changeout Capability. To enhance system flexibility, the system must allow cargo changeout (of the same payload) up to five days prior to launch and cargo changeout (to different cargo) up to 30 days prior to launch. Cargo replacement shall be completed within 5 days. Following the replacement, the launch system shall be at the same number of days before launch as when the cargo change notification was received.
Payload Integration. Payload integration must be greatly simplified in comparison to current operations. This refers to the difficulty of the operations, standardization of integration procedures, the time required to perform the operation, and the number of personnel required.
Payload Access. The system will provide hands on access to their payload before the shroud is installed and limited access through a TBD stand fairing access in the launch vehicle integration facility, and no access after leaving the launch vehicle integration facility. There will be a maximum of two days (TBR) between the last payload access in the launch vehicle integration facility and launch.
Nuclear System Handling. The system should be capable of processing TBD nuclear systems.
Segment | 3.4 Government Missions |
Market Area | 3.4.9 Space Science Outwards |
| Attributes | |
| Dependability | High probability of launching on schedule |
| Schedule | Minimize advanced booking time to provide rapid access to space Maximize launch windows |
| Availability | High probability that the system will be in an operational rather than a standdown state |
| Reliability | Comparable to current systems |
| Cost | Minimum cost per launch Minimize payload integration cost to support reduction of payload/instrumentation development cost |
| Capabilities | Support multiple payload classes Deliver and return payloads (Note: Early white papers mention return payloads, but requirements matrix of December 93 from Langley meeting does not. This needs to be clarified) Delivery to multiple destinations Accommodate more than 1 payload per launch |
| Operations | Provide standardized user interfaces Support high annual launch rate for small missions Support moderate annual launch rate for medium missions Support low annual launch rate for large missions Provide launch site services and facilities for parallel independent payload integration Provide streamlined regulations, procedures, paperwork, and requirement for payloads |
Delivery Locations. The system shall deliver science payloads to near earth orbit, heliocentric orbit, and interplanetary destinations (excluding manned missions).(Note: this wording is consistent with the payload masses referenced in the early white paper. Need to decide if requirements matrix or white paper should be used as source material)
Multiple Payloads. The system shall have the capability of delivering more than 1 payload per launch.
System Requirements
Dependability. The system shall have a 90% (TBR) probability of conducting Ragship class launches within the hour, Discovery class launches within a day and Explorer class launches within 10 days of their scheduled dates. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies.
Availability. The system must sustain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather than standdown state. Standdown time is associated with pose-failure shutdowns, scheduled and unscheduled maintenance.
Mission Scheduling. Ragship class payloads can be scheduled for flight with 24 months notice. Discovery class payloads can be schedules for flight with 18 months notice, and Explorer class payload can be scheduled with 6 months notice.
Launch Window. The system shall maximize the payload launch windows. (TBD matrix will show inclination, destination, and window size)
Reliability. The system must deploy payloads to their intended mission orbits with a total success probability of at least 0.95.
Vehicle Requirements
Payload Interface. The system shall provide TBD standardized payload interfaces with which the payloads must conform.
Payload Volume. The system must accommodate: Ragship payloads of up to TBD feet in diameter and length up to TBD feet; Discovery payloads which have dimensions compatible with Delta and Atlas systems; and Explorer payloads which have dimensions compatible with Pegasus. (Note: We need to quantify the dimensions instead of referencing other systems)
Operations Requirements
Launch Rate. The system shall provide up to 25 launches per year for payloads ranging from 500 lb into 100 nm to 250 lbs into 600 nm. The system shall provide up to 3 launches per year for Delta class payloads. The system shall provide at least one launch of a Titan IV/Centaur class mission every 2 years. (Note: These may need to be worded such that they are compatible with the terminology of Ragship, Discovery, and Explorer .)
User Support. The system must provide integration and test facilities available to the user.
Payload Integration. Payload integration must be greatly simplified in comparison to current operations. This refers to the difficulty of the operations, standardization of integration procedures, the time required to perform the operation, and the number of personnel required.
Payload Access. The system will provide hands on access to their payload before the shroud is installed and limited access through a TBD stand fairing access in the launch vehicle integration facility, and no access after leaving the launch vehicle integration facility. There will be a maximum of two days (TBR) between the last payload access in the launch vehicle integration facility and launch.
Payload Unique Environment. Payload unique requirements should be addressed by use of an adapter system or self-contained servicing support.
Segment | 3.5 Transportation |
Market Area | 3.5.3 Fast Package Delivery |
| Attributes | |
| Dependability | Assured on time delivery |
| Responsiveness | Improved point-to-point delivery times Provide launch on need capability |
| Availability | High probability that the system will be in an operational rather than a standdown state |
| Schedule | Daily flights |
| Reliability | Comparable to aircraft |
| Cost | Comparable to existing services |
| Capability | Delivery to multiple world wide destinations Accommodate multiple payloads per launch Provide large annual delivery capability (tons/year) Provide special handling provisions to user (i.e. perishable items) Adaptable to market needs, with a clear growth path Robust, weather resistant system |
| Operations | Provide rapid vehicle turnaround Minimum integration operations Provide high level of confidence that package will not be lost or damaged Compatible with existing package delivery infrastructure |
Delivery Locations. The system shall provide delivery of packages to multiple (TBD) world wide destinations.
Manned Flights. The system shall have the capability to accommodate man by year TBD.
System Requirements
On Time Delivery. The system shall have a .99 probability of delivery by the specified hour and .99999 probability of correct day delivery. (Note: The wording of this requirement is equivalent to Federal Express, but the requirements matrix of December 1993 suggests plus/minus 2 hours with no particular probability stated. This needs to be resolved)
Noise Limitation. The system shall meet TBD noise limitations.
Air Traffic Compatibility. The system shall be compatible with existing air traffic
System Capability. The system shall be compatible with the existing package delivery infrastructure (in particular the distribution system)
Payload Compatibility. The standard payload containers shall be airline compatible.
Schedule. Packages can be scheduled for flight with as little as 24 hour notice.
Vehicle Requirements
Vehicle Range. The longest range of interest is 10,000 nmi. (TBR).
Payload Interface. The system shall provide a TBD standardized interface for the standard containers.
Payload Module Volume. The system will accommodate TBD containers. Dimensions of the individual containers will not exceed TBD.
Operations Requirements
Flight Rate. The system shall be able to operate two flights daily.
Payload Integration. Payload integration must be greatly simplified in comparison to current operations. This refers to the difficulty of the operations, standardization of integration procedures, the time required to perform the operation, and the number of personnel required.
Takeoff/Landing Operations. The vehicle will takeoff and land from the same location. This location shall be easily accessible by air and road transport, and will preferably be in close proximity to major commerce centers.
Market Area | 3.5 Transportation |
Segment | 3.5.5 Hazardous Waste Disposal |
| Attributes | |
| Schedule | Maximize launch window size? |
| Reliability | Higher than current systems (US and foreign) |
| Cost | Minimum cost per launch |
| Safety | Ensure safety of personnel and public |
| Operations | Provide standardized user interfaces Ensure safe ground handling operations |
System Requirements
Dependability. The system shall have a 90% (TBR)probability of launching within one month of the scheduled date. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies.
Availability. The system must maintain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather than standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Reliability. The system must deploy payloads to their intended mission orbits with a total success probability of at least 0.98. This includes reliability of the launch vehicle and the upper stage ( if used).
Mission Scheduling. Payloads can be scheduled for flight with 12 months notice.
Vehicle Requirements
Launch Abort. The system must provide for an intact abort.
Payload Interface. The system shall provide a TBD standardized interface for the TBD canisters.
Payload Module Volume. The system will accommodate TBD canisters. Dimensions of the individual containers will not exceed TBD.
Operations Requirements
Launch Rate. The system must be capable of launching every 9 days.
Ground Processing. Ground operations must provide safe handling of nuclear waste payloads (potentially thermal).
Payload Access. The system will provide hands on access to their payload before the shroud is installed and limited access through a TBD stand fairing access in the launch vehicle integration facility, and no access after leaving the launch vehicle integration facility. There will be a maximum of two days (TBR) between the last payload access in the launch vehicle integration facility and launch.
Segment | 3.6 Entertainment |
Market Area | 3.6.3 Orbiting Movie Studio |
| Attributes | |
| Dependability | High probability of launching on schedule |
| Responsiveness | Minimal response time for launching on need |
| Availability | High probability that the system is in an operational rather than a standdown state |
| Schedule | Minimize advanced booking time Maximize launch windows |
| Reliability | Significantly higher than existing systems |
| Cost | Minimum cost per launch |
| Capabilities | Deliver and return payloads Provide delivery to and docking with orbital facility Provide civilian access to space |
| Safety | Provide system safety comparable to commercial ground transportation |
| Operations | Provide standardized user interfaces Provide a system which can be booked and boarded as if it were a bus, train, or commercial aircraft Provide streamlined regulations, procedures, paperwork, and requirement for payloads |
Rendezvous and Docking. The system shall be capable of performing on orbit rendezvous and docking operations.
System Requirements
Dependability. The system shall have a 90% (TBR) probability of conducting launches within 1 day of their scheduled dates. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies.
Launch on Need. The system shall not require more than TBD days between notification and launch for launch on need missions.
Availability. The system must sustain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather that standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Mission Scheduling.Customers shall be able to reserve transportation services with as little as 3 months lead time.
Launch Window. The system shall maximize the payload launch windows.
Reliability. The system must deploy payloads to their intended mission orbits with a total success probability of at least 0.98.
System Safety. System safety must be comparable to commercial air transportation.
Passenger Transportation Services. After the orbiting movie studio is operational, the system will function as a passenger transporter, moving groups of 12-20 people with personal effects and camera equipment to and from the facility. The system must be designed to transport civilians with minimal or no training required.
System Cost. To capture this market, the system cost must be $400/lb or less.
Vehicle Requirements
System Design. The system must provide a docking module and a logistics module.
Payload Interface. The system shall provide a TBD standardized interface for the TBD modular cargo containers.
Payload Volume. TBD
Operations Requirements
Launch Rate. The system shall provide regular flights on a weekly basis.
Payload/User Interface. The system shall provide airline like cargo and passenger handling. Space qualification requirements for payloads must be simplified (TBD).
On-orbit Facility Operations. The system must support the transfer of passengers and hardware to the orbital facility.
Segment | 3.6 Entertainment |
Market Area | 3.6.4 Space Athletic Events |
| Attributes | |
| Dependability | High probability of launching on schedule |
| Availability | High probability that the system will be in an operational, rather than a standdown state |
| Schedule | Minimize advanced booking time Maximize launch windows |
| Reliability | Significantly higher than existing systems |
| Cost | Minimum cost per launch |
| Capabilities | Deliver and return payloads Delivery to orbital facility Provide civilian access to space Provide on orbit rendezvous and docking capabilities |
| Safety | Provide system safety comparable to commercial ground transportation |
| Operations | Provide system which can be booked and boarded as if it were a bus, train, or commercial aircraft Provide streamlined regulations, procedures, paperwork, and requirement for payloads |
Rendezvous and Dock. The system must be capable of performing on orbit rendezvous and docking operations.
System Requirements
Dependability. The system shall have a 90% (TBR) probability of conducting launches within 1 day of their scheduled dates. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies.
Availability. The system must sustain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather that standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Mission Scheduling Customers shall be able to reserve transportation services 6 months in advance.
Launch Window. The system shall maximize the payload launch windows.
Reliability. The system must deploy payloads to their intended mission orbits with a total success probability of at least 0.98.
System Safety. System safety must be comparable to commercial ground transportation.
Passenger Transportation Services. The system must be designed to transport civilians with minimal or no training required.
System Cost. The system must provide a reduced transportation cost relative to current system costs. Cost should be reduced to at least $500/lb and preferably to $100/lb or less.
Vehicle Requirements
System Design. The system must provide a docking module and a logistics module.?
Payload Interface. The system shall provide a TBD standardized interface for the TBD modular cargo containers.
Payload Volume. TBD
Crew and Cargo Accommodations. The vehicle shall be designed for 12 persons, estimated at 250 lb each, 4000 lb of props, 1000 lbs of production equipment and 8,400 lbs of additional personal allowance (100 lb per day per person).
Operations Requirements
Launch Rate. The system shall provide regular monthly, or preferably weekly flights.
Payload/User Interface. The system shall provide airline like cargo and passenger handling. Space qualification requirements for payloads must be simplified (TBD).
Segment | 3.6 Entertainment |
Market Area | 3.6.5 Artificial Space |
| Attributes | |
| Dependability | |
| Availability | |
| Schedule | |
| Reliability | |
| Cost | |
| Capabilities | |
| Operations | |
| Requirements | |
Segment | 3.6 Entertainment |
Market Area | 3.6.6 Space Theme Park |
| Attributes | |
| Dependability | High probability of launching on schedule |
| Availability | High probability that the system will be in an operational, rather than a standdown state |
| Schedule | Minimize advanced booking time Maximize launch windows |
| Reliability | Significantly higher than existing systems |
| Cost | Minimum cost per launch |
| Capabilities | Deliver and return payloads Delivery to Space Theme Park in LEO Accommodate multiple payloads per launch Provide civilian access to space |
| Safety | Provide system safety comparable to commercial ground transportation |
| Operations | Provide standardized user interfaces Provide a system which can be booked and boarded as if it were a bus, train, or commercial aircraft Provide streamlined regulations, procedures, paperwork, and requirement for payloads |
System Requirements
Dependability. The system shall have a 90% (TBR) probability of conducting launches within 1 day of their scheduled dates. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies.
Availability. The system must sustain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather that standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Mission Scheduling. Customers shall be able to reserve transportation services 6 months in advance.
Launch Window. The system shall maximize the payload launch windows.
Reliability. The system must deploy payloads to their intended mission orbits with a total success probability of at least 0.98.
System Safety. System safety must be comparable to commercial transportation.
System Cost. To capture this market, the system cost must be $100/lb or less.
Vehicle Requirements
Payload/User Interfaces. The system will provide standardized payload interfaces for the satellite systems.
Operations Requirements
Launch Rate. Initially, the system must support 9 payloads per year. (less than 1000 lb each to support ground based segment) The number of payloads is expected to grow to 60-90 annually as transportation costs are reduced. The peak demand will be around 135/year at $100/lb. Initially the system must support 52 flights/year. As demand increases, the system may require daily flights and multiple vehicles. (Note: Need to verify that this is for passenger service and then clarify wording) The system shall provide airline like passenger handling to support the space based segment.
Segment | 3.7 New Missions |
Market Area | 3.7.7 Space Business Park |
| Attributes | |
| Dependability | |
| Availability | |
| Schedule | |
| Reliability | |
| Cost | |
| Capabilities | |
| Operations | |
| Requirements | |
Segment | 3.8 Space Utilities |
Market Area | 3.8.2 SpacePower Utilities |
| Attributes | |
| Dependability | High probability of launching on schedule |
| Reponsiveness | Minimal response time for launching on need |
| Availability | High probability that the system will be in an operational, rather than a standdown state |
| Schedule | Minimize advanced booking time to provide rapid access to space |
| Reliability | Higher than current systems |
| Cost | Minimum cost per launch Minimize payload integration cost |
| Capabilities | Deliver large payloads to highly inclined, elliptical orbits |
| Operations | Provide standardized user interfaces Provide streamlined regulations, procedures, paperwork, and requirement for payloads |
Manned Flights. The system shall provide transportation for assembly crews by year TBD.
Rendezvous and Docking. The system shall provide rendezvbous adn docking capabilities to support user on orbit assembly and servicing.
System Requirements
Dependability. The system shall have a 90% (TBR) probability of conducting launches within a week scheduled dates. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies.
Availability. The system must maintain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather than standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Launch on Need. The system shall not require more than TBD days between notification and launch to support unscheduled maintenance activities.
Mission Scheduling. Payloads can be scheduled for flight with as little as 6 months lead time.
Launch Window. The system shall maximize the payload launch windows.
Reliability. The system must deploy payloads to their intended mission orbits with a total success probability of at least 0.98. This includes reliability of the launch vehicle and the upper stage ( if used).
System Growth. The system shall emphasize modularity to accommodate adaptability and growth to meet changing market needs.
Vehicle Requirements
Payload Volume. System will accommodate payloads up to 15 feet in diameter and length up to 40 feet.
Payload Interface. The system shall provide TBD standardized payload interfaces with which the payloads must conform.
Orbital Transfer System. The system shall provide an orbital transfer system.
Operations Requirements
Launch Rate. The system shall provide the capability of launching every several days (Note: 1 - 2 times per week. Verbal per telecon with Dana. Need to select preferred wording)
Payload Integration. Payload integration must be greatly simplified in comparison to current operations. This refers to the difficulty of the operations, standardization of integration procedures, the time required to perform the operation, and the number of personnel required.
Nuclear System Handling. The system should be capable of processing TBD nuclear systems.
Segment | 3.10 Advertising |
Market Area | 3.10.5 Space Burial |
| Attributes | |
| Dependability | High probability of launching on schedule |
| Availability | High probability that the system will be in an operational, rather than a standdown state |
| Schedule | Ensure launch within a year of customer request for services |
| Reliability | Higher than existing systems |
| Cost | Minimum cost per launch |
| Capabilities | Provide capabilities to comanifest space burial module with other payloads |
| Operations | Provide standardized user interfaces Provide for receipt, recremation, and storing of ashes until launch |
System Requirements
Dependability. The system shall have a 90% (TBR) probability of conducting launches within 1 month of their scheduled dates. This includes external factors such as weather and internal factors such as production, assembly, and payload integration anomalies.
Availability. The system must sustain a system availability of at least 0.90, measured over the system life cycle. Availability is the fraction of time that a system is in an operational, rather that standdown state. Standdown time is associated with post-failure shutdowns, scheduled and unscheduled maintenance.
Mission Scheduling. The system should be designed such that remains are launched within 1 (TBR) year of a request.
Reliability. The system must deploy payloads to their intended mission orbits with a total success probability of at least 0.98.
Vehicle Requirements
Operations Requirements
Launch Rate. The system must provide an average of 1.3 launches per year from 2000 though 2030.
Facility. The system shall provide a facility for receiving cremains, processing (recremating), storing, and integrating them into the capsule for launch.
  |
Back to top |  |