Table of Contents for Appendix A

Appendix A System Attributes & Requirements
A.1 Introduction
Figure A.1-1. Common CSTS Attributes
Figure A.1-2. CSTS Reqmts. Sensitivity Analysis
A.2 Commercial Space Trans. Study Overview
A.3 Launch System Requirements

Commercial Space Transportation Study


Appendix A
System Attributes & Requirements Overview

A.1 Introduction

Early identification and definition of system attributes and requirements is essential to ensuring the transportation system meets the users' needs. This appendix contains the preliminary data base of these attributes and requirements which were identified during the market evaluation and analysis activities.

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.


CategoryAttribute
DependabilityHigh Probability of Launching on Schedule
ScheduleMinimum Advanced Booking Time
Reliability equal to or greater than Current System
CostMinimum Cost Per Launch
OperationsStandardized and Simplified Payload Interfaces
CapabilitiesSupport Multiple Payload Classes
Provide Delivery to Multiple Destinations
Provide On-Orbit Rendezvous and Docking Capabilities
Provide Delivery and Return Capabilities
AvailabilityHigh Probability System Will Be in An Operational Rather Than a Standdown State
ResponsivenessMinimum Response Time for Launching On Need

Figure A.1-1. Common CSTS Attributes

Ultimately the database information will be used to establish the system level requirements. We have developed an analysis process to evaluate differences in the quantified attributes and requirements. Our process allows us to make informed decisions when selecting the appropriate system level requirements. A preliminary example of the process is illustrated below using the booking time requirement.

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.



Figure A.1-2. CSTS Requirements Sensitivity Analysis

Basically, a preliminary attributes and requirement database has been established and will be utilized as a Point-of-Departure reference for further market, business, and technical evaluation activities. The database can be updated as revisions and modifications in the market evaluation become available. Commercial Space Transportation Study

A.2 Commercial Space Transportation Study Overview

Segment

3.1 Communications

Market Area

3.1.3 Fixed Satellite Services

Attributes
DependabilityHigh probability of launching on schedule
ResponsivenessMinimal response time for launching on need (Note: Need to determine if launch on need is necessary)
AvailabilityHigh probability that the system will be in an operational rather than a standdown state
ScheduleMinimize advanced booking time
Maximize launch window size
ReliabilityHigher than current systems (US and foreign)
CostMinimum cost per launch
CapabilitiesMultiple orbital delivery locations
Adaptable to market needs, with a clear growth path
GEO medium-large satellites
OperationsProvide standardized user interfaces
User friendly launch site operations
Rapid payload changeout capability

Mission Requirements

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
DependabilityHigh probability of launching on schedule
ResponsivenessMinimal response time for launching on need (Note: Need to determine if launch on need is necessary)
AvailabilityHigh probability that the system will be in an operational rather than a standdown state
ScheduleMinimize advanced booking time
Maximize launch window size
ReliabilityHigher than current systems (US and foreign)
CostMinimum cost per launch
CapabilitiesMultiple orbital delivery locations
Adaptable to market needs, with a clear growth path
GEO medium-large satellites
OperationsProvide standardized user interfaces
User friendly launch site operations
Rapid payload changeout capability

Mission Requirements

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
DependabilityHigh probability of launching on schedule
ResponsivenessMinimal response time for launching on need (Note: Need to determine if launch on need is necessary)
AvailabilityHigh probability that the system will be in an operational rather than a standdown state
ScheduleMinimize advanced booking time
Maximize launch window size
ReliabilityHigher than current systems (US and foreign)
CostMinimum cost per launch
CapabilitiesAdaptable to market needs, with a clear growth path
System can accommodate multiple payloads per launch
Multiple orbital delivery locations
OperationsProvide standardized user interfaces
User friendly launch site operations
Rapid payload changeout capability

Mission Requirements

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
DependabilityHigh probability of launching on schedule
ResponsivenessMinimal response time for launching on need (Note: Need to determine if launch on need is necessary)
AvailabilityHigh probability that the system will be in an operational rather than a standdown state
ScheduleMinimize advanced booking time
Maximize launch window size
ReliabilityHigher than current systems (US and foreign)
CostMinimum cost per launch
CapabilitiesAdaptable to market needs, with a clear growth path
LEO and MEO small-medium satellites
Multiple orbital delivery locations
OperationsProvide standardized user interfaces
User friendly launch site operations
Rapid payload changeout capability

Mission Requirements

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
DependabilityHigh probability of launching on schedule
ResponsivenessMinimal response time for launching on need (Note: Need to determine if launch on need is necessary)
AvailabilityHigh probability that the system will be in an operational rather than a standdown state
ScheduleMinimize advanced booking time
ReliabilityComparable to or better than current systems
CostMinimum cost per launch
CapabilitiesProvide launch, orbital servicing and recovery capabilities
OperationsProvide airline type operations
Provide launch facilities and recovery site facilities
Provide rapid turnaround technologies and processing facilities

Mission Requirements

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
DependabilityTBD
ResponsivenessProvide launch on need capability to replace failed satellite
AvailabilityHigh probability that the system will be in an operational rather than a standdown state
ScheduleMinimize advanced booking time
ReliabilityHigher than current systems (US and foreign)
CostMinimum cost per launch
CapabilitiesLaunch 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
OperationsProvide 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

Mission Requirements

LEO and GEO. The system shall have rated lift capabilities to accommodate the six major classes of remote sensing payloads as outlined in the table below:

Mass (kg)OrbitPrimary User(s)
200 - 500Low Earth Polar OrbitCommercial, US Govt
900 - 1,400Low Earth Polar OrbitComm, US Govt, Intl
1,500 - 2,200Low Earth Polar OrbitUS Govt, Intl
2,400 - 2,800Low Earth Polar OrbitUS Govt, Intl
5,000 - 6,000Low Earth OrbitUS Govt
700 - 2,400GeostationaryUS, 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
000510
Total101218
Commercial346
Govt/Intl.7812

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
DependabilityHigh probability of launching on schedule
ResponsivenessMinimum response time for launching on need
AvailabilityHigh probability that the system will be in an operational rather than a standdown state
ScheduleMinimize advanced booking time
ReliabilityHigh reliability
CostMinimum cost per launch
Minimum payload integration cost to facilitate changeovers from other systems
CapabilitiesProvide 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)
OperationsProvide standardized user interfaces

Mission Requirements

The system shall deliver an average of 176,000 lbs/year to both low and high inclinations spanning from LEO at 90 nmi to GSO at 19,930n nmi from the year 2000 to 2020.

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
DependabilityHigh probability of launching on schedule
ResponsivenessMinimum response time for launching on need
Availability
ScheduleMinimize advanced booking time to provide rapid access to space
ReliabilityHigher than current STS system
CostMinimum cost per launch
CapabilitiesDeliver payloads to Space Station
Return payloads from Space Station to earth
Frequent resupply capability
Provide civilian access to space
OperationsProvide 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

Mission Requirements

LEO. The system shall have the capability of delivering payloads weighing up to 25,000 lbs into a LEO orbit of 220 nmi x 220 nmi at an inclination 51.6 to 176;

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
DependabilityHigh probability of launching on schedule
ResponsivenessProvide launch on need capabilities to support contingency operations
AvailabilityHigh probability that the system will be in an operational state rather than a standdown state
ScheduleMinimize advanced booking time
Maximize launch windows
ReliabilitySignificantly higher than current systems (to support human rating)
CostMinimum cost per launch
CapabilitiesAdaptable, 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
OperationsProvide standardized user interfaces
Minimize operational impact to users
Support rapid cargo changeout capabilities
Human RatingProvide capability for crew ingress, egress, and escape as necessary to support human payload launches

Mission Requirements

Lunar System Capability. The system shall be designed to deliver a crew of 4 and 5 tons of cargo or 33t of cargo alone to the lunar surface.

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
DependabilityHigh probability of launching on schedule
ScheduleMinimize advanced booking time to provide rapid access to space
Maximize launch windows
AvailabilityHigh probability that the system will be in an operational rather than a standdown state
ReliabilityComparable to current systems
CostMinimum cost per launch
Minimize payload integration cost to support reduction of payload/instrumentation development cost
CapabilitiesSupport 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
OperationsProvide 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

Mission Requirements

Payload Classes. The system shall have the capability of supporting multiple payload classes. The Ragship class includes payloads up to TBD lbs to TBD LEO, GEO, and escape orbits. The Discovery class includes payloads up to TBD lbs to TBD LEO, GEO, and escape orbits. The Explorer class includes payloads up to 1,000 lbs to TBD LEO and near earth orbits. TBD or The system must accommodate multiple payload sizes including 500 lbs into 100 nm, 250 lbs into 600 nm, Delta class payloads, Titan IV class payloads, and Titan IV/Centaur class payloads. (Note: The wording of this requirement comes from an early white paper, need to clarify which is preferred)

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
DependabilityAssured on time delivery
ResponsivenessImproved point-to-point delivery times
Provide launch on need capability
AvailabilityHigh probability that the system will be in an operational rather than a standdown state
ScheduleDaily flights
ReliabilityComparable to aircraft
CostComparable to existing services
CapabilityDelivery 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
OperationsProvide 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

Mission Requirements

Payload Capability. The sytem must be capable of delivering 3000lb. It is estimated that the system will deliver between 30 and 500 tons per year. (Note: The second part of this statement came from early presentation material. Need to confirm the quantity)

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
ScheduleMaximize launch window size?
ReliabilityHigher than current systems (US and foreign)
CostMinimum cost per launch
SafetyEnsure safety of personnel and public
OperationsProvide standardized user interfaces
Ensure safe ground handling operations

Mission Requirements

Lunar Delivery. The system shall have the capability of placing 8 tons of payload, consisting of nuclear waste and canisters, onto the lunar surface.

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
DependabilityHigh probability of launching on schedule
ResponsivenessMinimal response time for launching on need
AvailabilityHigh probability that the system is in an operational rather than a standdown state
ScheduleMinimize advanced booking time
Maximize launch windows
ReliabilitySignificantly higher than existing systems
CostMinimum cost per launch
CapabilitiesDeliver and return payloads
Provide delivery to and docking with orbital facility
Provide civilian access to space
SafetyProvide system safety comparable to commercial ground transportation
OperationsProvide 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

Mission Requirements

System Capability. The system shall deliver cargo and passengers to a LEO business park. The annual estimated mass of 650 klbs is based on launching 12,500 lbs on a weekly basis. The system shall be capable of delivering the orbiting facility, with an initial launch mass of 80,000 lb to a TBD LEO orbit . The facility is to be operational by 2005-2006. (Note: Need to verify dates, they do not show up in the final report) To capture the near term (TBD) opportunities, the system must provide a mechanism for 50lb , camera size, payloads to piggyback on its primary satellite missions which are scheduled to be returned to earth. (Note: This requirement does not show up in the final report. Need to verify if it is still applicable.)

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
DependabilityHigh probability of launching on schedule
AvailabilityHigh probability that the system will be in an operational, rather than a standdown state
ScheduleMinimize advanced booking time
Maximize launch windows
ReliabilitySignificantly higher than existing systems
CostMinimum cost per launch
CapabilitiesDeliver and return payloads
Delivery to orbital facility
Provide civilian access to space
Provide on orbit rendezvous and docking capabilities
SafetyProvide system safety comparable to commercial ground transportation
OperationsProvide 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

Mission Requirements

System Capability. The system shall deliver cargo and passengers, approximately 20 klbs, to a LEO business park. The system shall be capable of delivering the orbiting facility, approximately the size of an external tank, to a TBD LEO orbit. The facility is to be operational by 2005-2006. At low transportation costs (less than $100/lb), the system must accommodate 426-853 klbs/year. For costs of $500/lb, the system must accommodate 16.4-65.6 klbs/year.

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
DependabilityHigh probability of launching on schedule
AvailabilityHigh probability that the system will be in an operational, rather than a standdown state
ScheduleMinimize advanced booking time
Maximize launch windows
ReliabilitySignificantly higher than existing systems
CostMinimum cost per launch
CapabilitiesDeliver and return payloads
Delivery to Space Theme Park in LEO
Accommodate multiple payloads per launch
Provide civilian access to space
SafetyProvide system safety comparable to commercial ground transportation
OperationsProvide 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

Mission Requirements

System Capability. The system shall deliver cargo and passengers to a LEO business park. To support early ground based segment, the system must provide delivery of multiple small satellite payloads (less than 1000 lb each) annually to various LEO orbits, including polar orbits. The system must provide transportation of the initial TBD facility. Once the Space Theme Park is operational, the system will function as a commuter service. Vehicle passenger capacity requirements will grow from 15-25 passengers initially to 75+ passengers later on (TBD). At current transportation costs ($5,000/lb), the system must deliver 6-42 klbs/year. At a reduced cost of $500/lb, the system must support 362-826 klbs/year and at a cost of $100/lb the system must accommodate 703-7209 klbs/year.

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
DependabilityHigh probability of launching on schedule
ReponsivenessMinimal response time for launching on need
AvailabilityHigh probability that the system will be in an operational, rather than a standdown state
ScheduleMinimize advanced booking time to provide rapid access to space
ReliabilityHigher than current systems
CostMinimum cost per launch
Minimize payload integration cost
CapabilitiesDeliver large payloads to highly inclined, elliptical orbits
OperationsProvide standardized user interfaces
Provide streamlined regulations, procedures, paperwork, and requirement for payloads

Mission Requirements

Molynia. The system shall have the capability of placing payloads weighing 25-50 MT into a TBD Molynia orbit at an inclination of 63 by 176; or higher. (Note: 25 MT into Molynia at 63 by 176; From Requirements matrix. Final report uses 55,000-100,000lbs into elliptical, highly inclined greater than or equal to 63 by 176. Need to verify that wording is acceptable.)

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
DependabilityHigh probability of launching on schedule
AvailabilityHigh probability that the system will be in an operational, rather than a standdown state
ScheduleEnsure launch within a year of customer request for services
ReliabilityHigher than existing systems
CostMinimum cost per launch
CapabilitiesProvide capabilities to comanifest space burial module with other payloads
OperationsProvide standardized user interfaces
Provide for receipt, recremation, and storing of ashes until launch

Mission Requirements

LEO. The system shall deliver a TBD lb capsule to a TBD LEO orbit.

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.


A.3 Launch System Requirements

  1. Launch system should be capable of meeting scheduled take-off time with approximately 95% schedule confidence.

  2. System should significantly lower cost as compared to existing system based on life cycle costs.

  3. 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.

  4. System must allow payload substitution (within a given payload class and mission ) prior to launch. Following payload replacement, the system shall be at the same number of calendar days before launch as when the payload change notification was received.

  5. There will be no routine payload access after leaving the payload encapsulation facility..

  6. The system will minimize the time between payload encapsulation and launch to reduce payload support requirements including batteries.

  7. System will use integrate-transfer-launch operations philosophy (to reduce cost improve reliability).

  8. Accomplish rendezvous and cargo delivery to xxx.

  9. System will accommodate payloads up to x feet in diameter and length up to x ft.

  10. Provide hands on access to the payload in the PEF before the shroud is installed, or through access ports after the shroud is installed.

  11. Provide transportation of encapsulated payload or encapsulated payload/upper stage to VIF or VAB where is will be mated with the vehicle.

  12. Provided limited payload access through standard fairing access panel, for final payload flight preparation in the VIF/VAB.

  13. Provide no payload access after the vehicle leaves the VIF/VAB.

  14. There will be a maximum of xxx clock hours between the last payload access in the VIF/VAB and launch.

  15. Provide capability for fail-safe abort prior to launch commit, including safe liquid engine shutdown from a full thrust condition.

  16. Provide an operations and facilities concept wherein launch vehicles are both integrated and mated with their payload in off-line facilities, and then transported to the launch pad for fueling, final checkout and launch. In an ITL concept, minimum time is spent on the launch pad, thus requiring only a simple clean pad and enabling attainment of lower costs, improved schedule dependability , and higher launch rate capabilities.

  17. System will define and develop standard payload interfaces with which payloads must conform. As a goal, payload-unique requirements should be addressed by use of adapter system and self-contained servicing support.

  18. The system shall have the capability of placing payloads weighing between TBD and TBD lbs into a LEO orbit of 100 x 100 nmi at an inclination of xx.x by176.

  19. The system shall be capable of delivering a single payload to xxx.

  20. The system will have rated lift capabilities of at least x lbs to x x x nmi, yy.y by176; orbit.

  21. The system must maneuver cargo to effect orbit circularization, transfers, and/or phasing.

Back to top