Orbital Maneuvering Vehicle (OMV) Missions Applications and Systems Requirements

The Space Congress® Proceedings 1984 (21st) New Opportunities In Space

Apr 1st, 8:00 AM

William G. Huber Manager, OMV Task Team, Marshall Space Flight Center, National Aeronautics and Space Administration

David C. Cramblit Deputy Manager, OMV Task Team, Marshall Space Flight Center, National Aeronautics and Space Administration

Follow this and additional works at: https://commons.erau.edu/space-congress-proceedings

Scholarly Commons Citation Huber, William G. and Cramblit, David C., "Orbital Maneuvering Vehicle (OMV) Missions Applications and Systems Requirements" (1984). The Space Congress® Proceedings. 6. https://commons.erau.edu/space-congress-proceedings/proceedings-1984-21st/session-7/6

This Event is brought to you for free and open access by the Conferences at Scholarly Commons. It has been accepted for inclusion in The Space Congress® Proceedings by an authorized administrator of Scholarly Commons. For more information, please contact [email protected]. ORBITAL MANEUVERING VEHICLE (OMV) MISSIONS APPLICATIONS AND SYSTEMS REQUIREMENTS

William G. Huber David C. Cramblit Manager, OMV Task Team Deputy Manager, OMV Task Team Marshall Space Flight Center Marshall Space Flight Center National Aeronautics and Space Administration National Aeronautics and Space Administration

ABSTRACT the OMV system should be operationally demon strated prior to SS Initial Operational Capa The routine delivery of large payloads to low bility (IOC). In the aggregate of its future earth orbit has become a reality with the uses, the OMV will more than offset its initial Space Transportation System (STS). However, development costs. This paper summarizes the once earth orbit has been achieved, orbit mission needs for the OMV program, and the transfer operations represent an inefficient characteristics of a typical/representative use of the Space Shuttle. The Orbital Maneu design (Figure 1) suited to meeting these needs. vering Vehicle (OMV) will add a new and needed dimension to STS capabilities. Utilized in a reusable manner, the OMV is needed to deliver QMV MISSION NEEDS AND OPPORTUNITIES and retrieve satellites to and from orbital altitudes or inclinations beyond the practical As a remotely piloted vehicle, its maneuvering limits of the Space Shuttle and to support controlled by man with hand-controllers from a basic Space Station activities. The initial ground control station, the OMV extends the OMV must also be designed to permit the addi reach of both the STS and the envelope of man's tion of future mission kits to support the involvement. It will eventually provide a wide servicing, module changeout, or refueling of range of new and unique mission capabilities as satellites in Low Earth Orbit (LEO) and Geo summarized in Figure 2. The upper portion of stationary Earth Orbit (GEO), and the retrie this figure addresses mission capabilities that val and deorbit of space debris. This paper an initial or early OMV will provide; more addresses the mission needs along with the advanced missions involving SS support and resulting performance implications, design satellite servicing will be accommodated by requirements and operational capabilities modularly augmenting the basic OMV with mission imposed on the OMV planned for use in the "kits" as needed to support these more demand late 1980's. ing classes of missions. Early OMV uses will emphasize the delivery of payloads to orbital locations beyond the effective range of the INTRODUCTION STS. With its TV cameras and a flood-light system, the OMV will be able to view the The OMV, operating as a remotely controlled delivered satellite and verify all sensors/ free-flying reusable space tug at distances appendages are deployed correctly and are func out to 1500 nautical miles away from the tioning before the OMV returns back to the Orbiter, provides a substantial augmentation Orbiter for pickup and reuse. Should the to the range of delivery, retrieval, and delivered satellite malfunction, the OMV can reboost satellite services provided by the be remotely controlled to re-rendezvous and Space Transportation System (STS). Once dock with the satellite for contingency retrie developed, the OMV will offer a wide range val and return to the Orbiter/ground for of both basic and growth capabilities which repairing. The OMV will also be used for can be adopted for use by future spacecraft planned retrievals of spacecraft after they developers with resultant cost savings to the have completed their useful mission life or for individual projects. It will also be usable periodic servicing/updates. The OMV will also as a propulsion module to augment the per provide an efficient means for reboosting large formance of planned and future high energy observatory-class payloads (which have no upper stages for delivery of payloads to propulsion of their own) back to their desired altitudes up to and beyond geosynchronous higher operational orbits after their orbits orbit (GEO). As an essential support ele have decayed. Operating with both primary and ment of the future Space Station (SS) program, vernier (RCS) thrusters, the OMV can be

7-10 utilized as a free-flying sub-satellite, trans subsequent reuse on another Shuttle flight. ferring attached science payloads or sensors to Operating out of Shuttle, in "Orbit-Stored" large separation distances from the Orbiter, mode, the OMV is left on-orbit for extended followed by later return to the Orbiter for periods of storage between missions or for the retrieval. The duration of such missions conduct of more missions until its fuel supply may vary from days to weeks to months; with is depleted. It will be retrieved by a later extended orbital operational times provided Shuttle flight for return to ground or may be by an OMV power augmentation kit. In summary, refueled and serviced out of the Orbiter to the initial OMV will be required to: extend its orbital stay time/utility. Operating in a "Space Station-Based" mode, the OMV, once - Deliver satellite payloads to orbital delivered to orbit by the Shuttle, will fly to altitudes or inclinations beyond the prac the SS and remain based there. From the SS tical limit of the existing Space Shuttle. location, the OMV will support logistics/payload exchange missions between the SS and STS, and - Retrieve satellite payloads from payload services support missions between SS orbital altitudes or inclinations beyond and associated free-flying satellites or the practical limit of the existing Space unmanned space platforms. The early OMV will Shuttle. be ground-based, but must be readily capable of evolving to the other basing modes as future - Reboost satellites to original opera missions needs and economic considerations tional orbital altitudes or higher. dictate. These basing modes will be thoroughly examined during the conduct of OMV Phase B - Accommodate mission sharing by pro definition studies in CY 1984 and 1985. viding a means to deliver multiple payloads to different orbital altitudes and inclina Figure 5 addresses the generic class of OMV tions. missions associated with support to large observatories. In this particular mission, the - Safely deorbit satellites which have OMV has acquired the target from an initial completed their useful life. 10-15 nautical mile separation distance, and then maneuvered to within a safe proximity - Be readily adaptable to the support stand-off distance using a combination of main of basic Space Station activities by trans propulsion and primary RCS thruster burns. The ferring and maneuvering of modules and OMV retractable docking probe is then actuated logistic equipment. to its extended position and terminal maneuvers performed using a secondary non-contaminating, The basic vehicle will be configured in a way cold gas RCS system. This phase of the mission that will readily permit the modular add-on is directly controlled by an OMV operator from of future mission kits or new hardware fea a ground station, utilizing sensory aids tures essential to supporting potential (radar/optical) and TV data transmitted by the future mission needs, such as: associated on-board OMV subsystems. The dock ing concept involves the use of a payload- - The servicing, module changeout, or mounted fixture and a compatible OMV docking refueling of satellites and platforms operat end effector. Several docking configurations ing in LEO, GEO, or in formation with a and mechanisms are currently being evaluated Space Station. as part of MSFC's supporting development pro gram. After rendezvous and docking with the - The retrieval deorbit of space debris large observatory at its pickup altitude which could represent an orbital hazard to (typically 250-275 nautical miles), the OMV will future space missions. return the observatory to the Orbiter (160 nautical mile altitude) for servicing. Follow In the Space Station era, as shown in Figure ing servicing of the observatory in the Shuttle 3, it is anticipated that OMV missions will cargo bay, the OMV will then re-deploy it back be conducted in two major ways: many will con to a desired operational altitude which may tinue to be "based" out of the Orbiter for range anywhere from 320-400 nautical miles. support to the SS or for spacecraft missions After the observatory is safely deployed and going to orbital locations not involved with operational, the OMV will then return to the or compatible with the SS orbit. Other OMV Orbiter. uses, dedicated to operational support of the SS, will be station-based, where the OMV is To meet projected mission needs, the OMV must serviced, maintained, and controlled from an be capable of effective operations in a number OMV support facility at the SS. The complete of operating modes, as summarized in Figure 6. range of OMV basing concepts is shown in Except for control of the terminal rendezvous Figure 4. Operating out of the Shuttle, in a and docking operations (piloted mode, ground "Ground-Based" mode, the OMV is delivered to based) the OMV will be capable of automatic orbit, performs its mission, returns to the operations under programmed control of an on same Orbiter for retrieval, and is returned board computer. It will be capable of executing to the ground for servicing, refueling, and a primary inertia! hold mode to support its

7-11 retrieval by the Shuttle/RMS. It will be cap performance gain at the higher inclinations able of detecting any onboard anomalous con (WTR) is especially noteworthy. The signific ditions and placing itself into an automatic ance of this STS augmentation is shown in hold mode (low power) until the situation can Figure 8 and graphically displayed in Figure 9. be corrected. In the event the OMV cannot be Using the Orbiter alone, it takes a dedicated retrieved on the Shuttle flight it was ini Shuttle flight (no-cost sharing possible) to tially delivered by (planned or contingency deliver a 20,000 pound payload to 350 nautical situation), the OMV will be capable of oper miles. However, using an OMV, this mission ating in a powered-down contingency hold mode can be done in a more efficient and cost effec for up to nine months for retrieval on a later tive manner for the users. In this case, the Shuttle flight. Being modular in design, the Orbiter delivers the 20,000 pound spacecraft OMV will also be scarred or readily modified and the 10,000 pound OMV to a 160 nautical mile to support extended capability mission modes, standard delivery orbit. At this lower alti such as those associated with storage at the tude, the Orbiter is also able to deliver an space station, and the control of OMV from a added 30,000 pounds of discretionary payload SS control center. Many projected extended (i.e., a Spacelab/module or other shared mission capability missions will require the OMV to payload). The cargo bay packaging arrangement provide for sustained orbital operations over for such a potential dual mission manifest is a long time. Therefore, the OMV will be shown in Figure 10. In fact, the OMV could initially designed to accommodate the future deliver the 20,000 pound spacecraft as high as add-on of a supplementary power kit and other 750 nautical miles and return back to the support equipment as required to support these Orbiter with fuel remaining. While the OMV growth mission needs. (ground-controlled) is doing the delivery mission, the Orbiter crew is free to conduct In summary, OMV mission needs and opportunities the Spacelab or support the "discretionary are encompassed by the set of generic design payload" mission. In this scenario, the reference missions (DRM's) outlined in Figure Orbiter has made full use of its maximum pay- 7. These DRM's will be used during the load delivery potential (60-65K pounds), and definition phase as a basis for configuration has accommodated two payloads. In this manner, sizing and design. It is currently planned the cost of the flight can be shared between that the initial OMV developed will meet the the two users. Clearly, the OMV offers a specific requirements identified with early powerful cost-effective means for enhancing the year mission needs (i.e., payload delivery, Orbiter's ability to manifest multiple payloads retrieval, reboost, etc.). Extended capability on a single flight. missions, although not quantifiable in terms of specific needs, will be used to insure that The low earth orbit performance corridor offered the OMV program can respond to these emerging by a typical OMV configuration is shown in future missions (satellite refueling, servic Figure 11. Orbital altitudes of 1,400 nautical ing, space debris capture, etc.). The initial miles with a 5,000 pound payload are possible. OMV will be designed in a modular way to pro Round-trip plane changes of almost 8° are also vide these services as the user needs are provided assuming a payload placement and OMV- better developed and defined. Subject to only return to the Orbiter. Added performance future design studies, it is generally (if required) is possible by the addition of a assumed that these growth capabilities will propellant tanker kit. Such kitting options be provided by augmenting the initial OMV will be investigated during the Phase B study with a series of mission kits, added on in analyses. Low earth orbit performance capabil modular fashion as required. ities for several mission profiles are shown in Figure 12. Shown parametrically are the OMV OMV PERFORMANCE CAPABILITIES AND BENEFITS capabilities to deliver, retrieve, transport payloads on a round-trip basis, and to retrieve- The STS performance capabilities at Eastern redeploy in a double mission. Typically, the Test Range (ETR) and Western Test Range round-trip performance curve indicates the (WTR) are shown in Figure 8 for the standard OMV's capability to provide contingency return injection profile and a direct injection pro of a payload that fails to operate when file. The potential for further gains by the deployed. The retrieve-redeploy curve demon addition of an in-bay Orbital Maneuvering strates the OMV capability to retrieve a space System (QMS) kit (not an approved program craft to the Orbiter or to a Space Station and element at this time) is also shown. Over then redeploy it to its operational altitude laid on these curves is the added performance after servicing. No orbital refueling of the capability offered by an OMV departing from OMV was assumed, and in all cases, the OMV the standard Orbiter delivery altitude of retains sufficient onboard fuel to return itself 160 nautical miles, delivering a payload to to the departure base at the end of the mission. a higher orbit, and returning without payload The use of an OMV propulsion module (PM) to to the Orbiter. As shown, OMV offers a sub augment the performance of high^energy upper stantial augmentation to the Orbiter 1 s stages going to geosynchronous orbit is demon "sphere of influence" relative to attainable strated in Figure 13. Applications of an OMV-PM payload delivery weights and altitudes. The with both a Centaur and a Transfer Orbit Stage

7-12 (TOS) are shown. When used with the Centaur, Contractors will be free to propose the design both the OMV and its attached spacecraft are solutions they consider most responsive to placed in geosynchronous orbit. The OMV then NASA's OMV Mission Need Statement. The top- provides maneuvering AV for spacecraft repo level design guidelines we have developed for sitioning, altitude changes, etc. Uhen used the OMV, based on studies to date, are sum with the TOS, the OMV-PM provides the apogee marized on Figure 17. These criteria will be circularization burns and plane change used to guide and direct forthcoming contractor maneuver to get the spacecraft into orbit. preliminary design efforts. The reference This leaves the remaining fuel for maneuver design which emerged from MSFC in-house studies ing capability. In both cases shown, it was to date is shown in Figures 18-21. This con assumed that major avionics functions for figuration utilizes an aluminum tubular struc the mission (guidance, navigation, power, ture that mounts directly to the Shuttle cargo control, etc.), were provided by the space bay sill and keel fittings, thereby eliminating craft and not the PM. Further interface the need for a cradle. It has been configured trade studies in this area will be conducted to minimize its length in the Shuttle cargo bay in the definition .phase. In summary, the (37"), and can be mounted in any location, OMV offers a wide range of performance thereby enhancing its manifesting potential. capabilities in support of both the STS and It will utilize a redundant onboard computer SS programs, both in LEO, and at geosynch system, inertial reference units, a global ronous locations when delivered to this positioning system (GPS) interface, and various location by a high-energy upper stage. sensors for nevigation aid (star sensor/sun sensor/horizon sensor or combinations thereof). It will communicate with the ground control BASELINE OMV DESIGN CHARACTERISTICS station through Tracking and Data Relay Satellite System (TDRSS) networks, using S-Band command- The OMV concept of today has been evolved telemetry and video links between OMV and over a number of years. It's early predeces TDRSS for low earth orbit missions. Ground sor program, Teleoperator Retrieval System networks will be utilized to support OMV (TRS), was planned to be used to reboost the missions at GEO. Skylab to a safe operational altitude, but was terminated during development in 1978 The OMV will be powered with primary batteries, because of the earlier than expected re-entry but may also require some secondary battery/ of Skylab. This vehicle, shown in Figure 14, solar array panels to meet the long-term, on- was being fabricated using a substantial orbit storage requirements. All critical amount of residual hardware from other pro avionics components are mounted in accessible grams. It contained approximately 6,000 locations to permit an on-orbit maintenance and pounds of hydrazine propellant, used a cluster repair capability. RF system elements, includ of 32 thrusters (40 pounds thrust each) for ing surface mounted omni antennas and two (2) primary propulsion, and was approximately deployable highgain antennas (Electronically 7 feet in length. It was configured to pro Steerable Spherical Array (ESSA)) are also vide an on-orbit dormant storage capability. accessible for EVA servicing. For main propul From this early design heritage and focused sion and primary RCS, both mono-propellant and mission objective, a sound data base was bi-propellant configuration options are being acquired on which to derive a more versatile, considered. The MSFC reference design uses optimized OMV concept capable of supporting 6,700 pounds of storable bi-propel1 ant (mono- a much broader range of future mission methyl hydrazine and nitrogen tetroxide) stored objectives. In the past five years, follow in four oblate spherical tanks. Propellants are ing TRS, NASA has invested $1.4M in industry pressure-fed to the thrusters at 250 psia by a Phase A studies to redefine the OMV program gaseous nitrogen pressurant stored at 4,000 psi (reference Figure 15). This, along with in 4 spherical tanks. A nominal thrust level corporate investments of $7.5M and a sub of 800 pounds was established for main propul stantial in-house design/supporting develop sion, utilizing 4 thrusters at 200 pounds thrust ment activity at MSFC .has resulted in a sound each. Other thrust levels and thruster combina data base on which to proceed to the next stage tions are also being investigated. Throttling of OMV definition (Phase B). A wide range of thrusters and gimballed thrusters may also be configuration design approaches emerged from considered further as options to the reference studies to date, some of which are shown in baseline design. Eight RCS modules are pro Figure 16. For all Phase A studies, a MSFC vided for OMV stabilization and altitude con design reference concept was developed. trol. Each module has three thrusters rated at 15 pounds thrust level each. During main pro It is this concept that will be discussed in pulsion maneuvers, a number of thrust vector more detail in this paper. It should be noted control techniques are possible; the reference here that this is a reference design, and not design utilizes main thrust modulation tech a selected configuration.The Phase B studies niques for pitch and yaw coupled with roll are intended to drive out a preferred design control from the RCS. A cold gas RCS system solution responsive to the mission and systems will also be incorporated for close-in precise performance requirements defined by NASA. OMV maneuvering around contamination sensitive

7-13 payloads. The reference design utilizes an OMV PROJECT STATUS AND PLANS extendable-retractable docking probe with an "RMS-type" end effector for docking to a pay- Definition phase studies for the OMV have been load for retrieval,, Other probe designs are approved for FY 1984; MSFC is presently evaluat all SO' being evaluated. A radar system is pro ing proposals that will lead to the selection vided to aid in target acquisition, and to of three or more Phase B study contractors for provide the OMV operator with precise range one-year contracts starting in mid-CY 1984, and range-rate data during the terminal as shown in Figure 24,. Early availability of phases of a man-in-the-loop controlled dock OMV will obviate the necessity of including ing maneuver; Two video cameras will be integral propulsion in the planning for many new provided to support rendezvous, docking, and spacecraft. Once an OMV program is approved payload viewing operations. One will be for development, mission planners and payload bore-sighted along the docking axis; another developers will rely on OMV availability for will be off-set, and will provide pan- tilt- placement, retrieval, and maneuvering services, zoom lens capabilities. Docking/flood Tights To support payload designers, and planners in will be provided to illuminate the payload their near-term assessments of program options, docking interface,,, The OMV will also have a a close working relationship will! be established standard set of aircraft-type running lights with the user community to help guide the Phase (amber-red-green) to aid the Orbiter or Space B contracted efforts. Current OMV project Station crews in visually acquiring the OMV implementation plans are based on an assumed during proximity operations, OMV retrieval, approval for development in FY 1986. This would and! berthing operations. As mentioned earlier, result in a CY 1990 launch. The OMV functional t he OHV p r o g ram w ill p r o v i d e a s p 1 in - off capabilities are also critical to the Space feature; the availability of a propulsion Station program, and should therefore be module (PM) for application to a wide variety demonstrated well in advance of initial Space of high-energy, upper-stage missions. This Station operations. At present, SS-OMV project IP'1, shown on Figure 21, will provide only the coordination meetings are conducted on a fre ill 1 n i mall v a 1 v e dl r i v e e 1 ec t r o n i c s / i n t e r fa c i n g quent basis to insure mutual awareness of inter avionics equipment necessary for control of face requirements and operational constraints the propulsion system. It is assumed that early in the definition phases of the two all o their avionics functions critical to a programs. Major milestones for coordination complete mission are provided by the space reviews between the two programs are shown in craft system utilizing the PH. A weight Figure 25. Space Station participation in the summary for the reference design OHV and OMV requirements planning, Phase B definition QHV-PH is shown on Figure 22, based on a activities, and the conduct of several interac II-" propel 1 ant load of 6,700 pounds. From a tive requirements reviews prior to completion desi gn f 1 exi bi 1 i ty stand po i n t :ll the i n i t i all of the OMV "Understanding Phase" (through PDR) ground-based OMV will be properly scarred and of development will assure that space station configured to permit ready evolution to an needs are properly reflected in the initial design extended capability OMV response to accom and development of OMV flight hardware. Develop modating growth missions. For example, it ment milestones for the flight hardware are will be scarred to permit on-orbit refueling, shown in Figure 26. The initial OMV program battery recharge, and other functions as will most likely encompass the "current program" needed to support long-duration , space-based elements outlined on Figure 27 9 which also Ollff operations. The derivation of a design portrays how the program may evolve. As seen approach i nherently fill exi bl e to evol ve now, near-term growth of an initial OMV will be "gracefully" as emerging growth mi ssions needs needed to support Space Station-based operations dictate will be a significant challenge to the and to demonstrate a capability for the remote Oil" Phase B contractor teams,, While retaining re f yell ing of spacecraft or free-flying unmanned the fill exi bi 1 i ty for growth, i t wi 11 al so be platforms. Later growth will involve spacecraft • essential to mi nimize program development servicing, more advanced manipulative devices iris Is and! costs through the use of existing for space debris capture/assembly support opera and proven hardware wherever possible. An tions, and spacecraft operations support at GEO assessment of baseline OMV subsystem require- locations. As shown on Figure 28, a supporting ments (reference Figure 23) indicates a high development program is underway at MSFC to percentage of the needed capabilities can be demonstrate the near-term capabilities needed met either by existing hardware or modifications in the rendezvous/docking area. Advanced cap thereto. No crii f i call new technol ogy needs have ability studies are underway in the remote been Identified in the OMV planning to date; how- refueling tanker area, and in the area of ewer ,, supporti nif devel opment program efforts advanced mechani sms (mani pul a/tors/automated relative to rendezvous and docking mechanisms spacecraft servicers). Support to the mech and sensors needs will be accelerated otter the anisms area is being provided by Jet Propulsion next two fears to strengthen this critical area. Laboratory (JPL) in the area of end effectors and sensors* These efforts are establishing the foundations on which future OMV advanced mission kit development efforts will be based.

7-14 Near-term MSFC efforts in the rendezvous/ docking area will continue to rely heavily on use of a target motion simulator and a six- degree-of-freedom dynamic moving base simula tor (Figure 29) to evaluate selected docking mechanisms and terminal rendezvous and contact dynamics (last four feet of closure) and to perform an engineering assessment of vehicle control dynamics. This system will be com plemented with another facility to be fully operational by mid-1984, the OMV mobility simulator described in Figures 30 and 31. This facility will be utilized to evaluate a variety of docking techniques, sensors, lighting requirements, video system require ments, and control station needs. Basic elements of the system include a six-degree- of-freedom OMV mobility unit with cold gas thrusters (variable thrust level), and a computer supported navigation/control system slaved to a remote control center via an RF communications link. The mobility unit will operate on a precision epoxy floor covering an area of 4000 ft^. These two major facili ties atJJSFC will be utilized in an integrated manner^"over the next two years to prepare a sound design requirements/design criteria data base to help guide the OMV development pro gram.

CONCLUDING REMARKS The OMV offers a wide range of new satellite services capabilities to complement the SIS program and to support a future Space Station, A sound data base exists to support an aggressive program leading to development of an operational OMV capability by early 1990.

7-16

Ll-l OMV IN THE SPACE STATION ERA

CO-ORBITING PERMANENT FACILITIES PLATFORM PLACEMENT/RETRIEVAL RETRIEVE DATA EXPERIMENT EXCHANGE REBOOST STATION • INSPECTION LOGISTICS SUPPORT AND MAINTENANC

RETRIEVE STATION-BASED OTV'S SPACE STATION

ASSY SUPPORT AND LOGISTICS

SATELLITE PLACEMENT/ RETRIEVAL /'RETRIEVABLE ^^X / SATELLITES \ SHUTTLE-BASED ( FOR V SERVICING AT SHUTTLE I \ OR STATION J

FIGURE 3 I I

7-18 STATION

BASED

SPACE

ORBIT

CONCEPTS

STORED

STAYS

FIGURE BASING

ORBIT

OMV

BASED

RETURNS

SAME

OMV ON

SHUTTLE

GROUND OMV

RENDEZVOUS

DOCK

AND

RETRIEVAL.

HANDOFF

RMS

SERVICING

f'()

AND

FIGURE

REDEPLOYMENT

WITH

OMV

t 1

RETURNS

OMV

O CN OHV OPERATIONAL HOPES

INITIAL OMV OPERATIONAL HOPES

• PROGRAMMER MOPE • PILOTEP MOPE (GROUNP BASEP)

• PRIMARY INERT IAL HOLP • AUTOMATIC (MIN. PWR.) MOPE

• CONTINGENCY ON-ORBIT HOLP MOPE (9 MONTHS MIN.)

EXTENPEP CAPABILITY MOPES (INCORPORATE OR BE SCARREP TO INCORPORATE)

• SPACE STATION MOPES

A. CONTROL VIA OMV CONTROL CENTER ON SS

B. LONG-TERM QUIESCENT STORAGE WHILE ATTACHEP TO SS

• SPACE BASEP MOPE

A. EQUIPMENT APP-ON'S TO PERMIT LONG PURATION ORBITAL MISSIONS

FIGURE 6

7-21 EXAMPLE MISSION

OMV RETURNS CN TO ORBITER r^.

c• —^^iSl^,.

FIGURE 9

LBS)

20K 20K

PAYLOAD PAYLOAD

(APPROX. (APPROX.

TYPICAL TYPICAL

OMV

SPACELAB SPACELAB

PALLET

POTENTIAL POTENTIAL

AND AND

SHARING SHARING

SPACELAB SPACELAB

FIGURE FIGURE

FLIGHT FLIGHT SPACELAB

ALTTTUDE, ALTTTUDE,

PLANE PLANE

OMV

ORBITER

ORBITER ORBITER

OMV OMV

LEO LEO

PERFORMANCE

CHANGE, CHANGE,

(TWO (TWO

OMV OMV

PERFORMANCE PERFORMANCE

(ONE (ONE

WAY; WAY;

RETURN)

WAY WAY

DEG

P/L P/L

WITH WITH

OUT; OUT;

P/L)

1400

5000 5000

7.5

360

1.4

PAYLOAD

ENVELOPE ENVELOPE

25.000 25.000

700

1.2

4.0

320

OF OF

ORBITAL ORBITAL

MANEUVERING MANEUVERING

OMV OMV

ENVELOPE

PERFORMANCE PERFORMANCE

ORBITER ORBITER

VEHICLE

ENVELOPE

CM CO OMV LEO PERFORMANCE

40 - WPROP = 6566 LB l sp = 285 SEC.

NO PLANE CHANGE

30 -

CO o

20 -

CL > O 10 -

900 1000 (N.MI.) 100 200 1000 1200 1400 1600 1800 (KM) 200 400 600 800

DELTA ALTITUDE

FIGURE 12

7-27 PERFORMANCE OF UPPER STAGE + OMV PROPULSION MODULE

GEOSYNCHRONOUS ORBIT

OMV PM WpROp = 6566 LB. OMV Ws = 2521 LB. ! SP = 285 SEC. CENTAUR

, CENTAUR G' (72K SHUTTLE) 16 CENTAUR G' (65K SHUTTLE) 14 CENTAUR G (65K SHUTTLE) _ 12 «!3 io TOS (65K SHUTTLE) 2 •• O I 6 " O

6700 LB. OMV 2- PROPELLANT LIMIT

0- 1000 2000 3000 4000 6000 7000 8000 9000 (F/S)

500 1000 1500 2000 2500 (M/S)

REMAINING A VAT GEO

FIGURE 13

7-28 ORBITAL MANEUVERING VEHICLE MSFCTELEOPERATOR

PHASE

1977

SYSTEM

RETRIEVAL

A/B STUDY A/B

MSFC

100

MAN

INHOUSE

$27.

——I—

YRS

1978

PHASE

CDR

C/D

MSFC

MARTIN

TERMINATE

MMC

PHASE

MODULAR

——I—

1979

TRS

(•GENERIC

(•COMMERCIAL

A/B

RFP

DESIGN

SUPPORTING

FIGURF

$2.5

OMVDEFIN.

PAST

—I——

1980

DEVEL.

ACTIVITIES

DEVELOPMENT

ORBITAL

MANEUVERING VEHICLE

MAN

OPTIONS

VOUGHT

YRS

—I——

OMV-IRAD

1981

STUDY

$870.

••

MARTIN

S7.5M

——h-

MSFC

1982

$300.

STUDY

STUDIES

STUDY

$193.

0BRFPV

1983

(Ltf)

II/OMV II/OMV

IN.

2^44 2^44

41 41

IASELINE

2J7f

17 17

MARK MARK

ITT. ITT.

ft,MtLKN2"4

INERT INERT

LENGTH LENGTH

• •

•PHOPMKLKNzH*

LENGTH LENGTH

WERT WERT

• •

PftOf PftOf

• •

VOU6NT VOU6NT

MARTIN MARTIN

(OPTIMIZED)

MODULE

04^MN

II/OMV II/OMV

FT.

MODS)

7 7

(LK) (LK)

1 1

MARK MARK

2JM 2JM

(SMM) (SMM)

4t"

WT. WT.

MANEUVER MANEUVER

1JU* 1JU*

LENGTH LENGTH

INERT INERT

• •

CONCEPTS

MARTIN MARTIN

MINIMUM MINIMUM

INERT INERT

PIIOP PIIOP

LENGTH LENGTH

• •

DYNAMICS DYNAMICS

OMV OMV

GEN. GEN. SPACECRAFT SPACECRAFT

FIGURE FIGURE

CONCEPT

LK.

(LK)

N2H4/MMH

IN.

PROP) PROP)

(N204AMH)

REF REF

37 37

(II (II

3,111 3,111

4.771 4.771

i.7M i.7M

COMPATIBLE)

DESIGN DESIGN

INERT INERT

LENGTH LENGTH

PROP PROP

INERT INERT

LENGTH LENGTH

MOM.Tft MOM.Tft

• •

(QMS (QMS

VOU6HT VOU6HT

MSFC MSFC

AVIONICS TMS TMS INCLUDING

SPACE)

FROM

GEO

CONSIDERATIONS

AT WITH CONTROL

PRACTICAL

EXTENDED CAPABILITY

AND

CAPABILITY

STORAGE

EXTENT

CAPABILITY

FUTURE

OPERATION

WEIGHT

REFURBISHMENT

(COMPATIBLE

FOR

AND

GUIDELINES RETRIEVAL

ORBITAL AND

STATION BASED

FIGURE,

MISSION

HARDWARE

STATION

LEO

SPACE

LIFE WITH

DESIGN AND/OR

LENGTH

INTERFACES

POTENTIAL

DURATION

ACTIVITIES

APPROACH

KEY

WITH

YEAR

GROUND

TO BE

LONG

GROWTH

ORBITER

PLACEMENT BASED

PRACTICAL

FROM

ABLE DESIGN

FOR

PROVEN/DEVELOPED

PAYLOAD

SHUTTLE CAPABLE

MINIMUM CONTROL MINIMIZE

MUST HAVE UNIQUE MISSION DESIGN USE MUST MODULAR

•

• • • • • • • • • •

•vj ro

(3)

Trunnions(4)

•/B3-OG04729A-1

KWC KWC

Fitting Fitting

(4)

Compartment Compartment

Sill Sill

Module(S)

Thrusters Thrusters

Shuttle Shuttle

Avionics Avionics

RCS RCS

Main Main

FIGURE FIGURE

Trunnion

(4) (4)

Tank Tank

Fitting Fitting

Fixture

Keel Keel

Probe

PressurantTank(4)

Batteries

Propellant Propellant

Grapple Grapple

Shuttle Shuttle

Camera

ORBITAL

RMS RMS

Docking Docking

TV TV

Antenna(2).

Radar

ESSA ESSA

CO «*4 COMMUNICATIONS

EQUIPMENT

DOCKING/DEPLOY

MECHANISM

GNC

EQUIPMENT

MSFC

REFERENCE

FIGURE

DESIGN

OMV

PRIMARY

BATTERIES

RCS

THRUSTERS

DATA

MANAGEMENT

VIDEO

EQUIPMENT

DEPLOYABLE

ANTENNA

EQUIPMENT

(LOADED)

NTO/MMH

INCHES

DESIGN DESIGN

POUNDS POUNDS

178 178

OMV

MSFC

X X

6,700 6,700

10,496 10,496 POUNDS

37 37

REFERENCE REFERENCE

PROPELLANT: PROPELLANT:

WEIGHT: WEIGHT:

DIMENSIONS: DIMENSIONS:

FIGURE FIGURE

CO CO 01 PROPULSION

FIGUP.F.

MODULE

WEIGHT: DIMENSIONS:

MASS

6700 2189LBSDRY

9089

.722

200

FRACTION:

138

IBS

LBS LBS

INCHES

NTO/MMH

LAUNCH

72 72

104

936

580

155

280

279

134

200 200

1100

6566

3596

3930 3930

10496

DESIGN

RETRIEVAL RETRIEVAL

PLACEMENT PLACEMENT

OTHER

ALL ALL

ON ON

5% 5%

AND AND

698

179

140

134

200 200

1055

9089 6566

2523 2523

2189

MODULE

PROPULSION PROPULSION

(LBS.)

SUBSYSTEMS SUBSYSTEMS

SUMMARY SUMMARY

FIGURF FIGURF

THREE THREE

WEIGHT WEIGHT

FIRST FIRST

/MMH) /MMH)

ON ON

OMV OMV

SUBSYSTEMS

15% 15%

) )

MECHANISM MECHANISM

(GN

WEIGHT WEIGHT

PROPELLANT PROPELLANT

WEIGHT

WEIGHT WEIGHT

LAUNCH LAUNCH

•CONTINGENCIES: •CONTINGENCIES:

USEABLE USEABLE

RESIDUALS RESIDUALS

BURN-OUT BURN-OUT

PRESSURANT PRESSURANT

DRY DRY

VIDEO

EPS EPS

GNC GNC

CDMS CDMS

PROPULSION PROPULSION

STRUCTURE

SUBSYSTEMS

TPS

DOCKING/DEPLOY DOCKING/DEPLOY

•CONTINGENCIES •CONTINGENCIES

CO ->J HARDWARE

THRUSTERS

PROPULSION

TRANSPONDERS/AMPLIFIER TANKS PROPELLANT

CDMS PHASED PREMODULATOR

PRESSURANT

REGULATORS

COMPUTER CAMERAS/LIGHTS

ELECTRICAL

CABLING PRIMARY

VALVE

IMAGE SENSOR

RADAR GPS SENSORS

IMU

AMD

PROCESSOR

CONTROL ELECTRONICS CONTROL

ARRAY

INTERFACE

AND BATTERIES

VIDEO

TANKS

POWER

DISTRIBUTION

ANTENNA

PROCESSOR

OMV

HARDWARE

PROVEN

FIGURE

X X

DEVELOPMENT

OR OR

MOD

X X REQ'D

X X

STATUS STATUS

NEH

X X

MX, MX,

MX MMS MILITARY PROGRAMS MILITARY MILITARY MX,

VARIOUS ERBS HERITAGE

SHUTTLE

MMS/NASA

NASA

LANDSAT &

NASA

STS STS SHUTTLE

CENTAUR

STD

PROGRAMS

MMS

STD

r^*

i i

FLT FLT

22.1984

1990

i i

FLT FLT

UNIT

1ST 1ST

UNIT

FY90

flfT—

PF01/KLAN PF01/KLAN

l l I

1989

DECEMBER DECEMBER

4 4

FY89

1988

db:

FY88

1987

FY87

)

1986

FY86

— —

VEHICLE

MAP MAP

AWAR 0C/0

1985

r r

FY85

•••

X X

•m

r— r— &...

ATP

1984

0B 0B AWARI AWARI

FIGURE FIGURE

FY84

, ,

IPI

MANEUVERING MANEUVERING

START)

1963

•••

FY83

•••

^" [_

(SLOW (SLOW

•

ORBITAL ORBITAL

1982

PHASE PHASE

••••

FY82 FY82

'^m

SYNTHESIS SYNTHESIS

(VOUGHT)

(0C/D) (0C/D)

(MMC)

A) A)

(HI)

(0 (0

(08)

DOCKING

& &

(ETR)

RET.

DEVELOPMENT

STUDY STUDY

INDICATES UNDERSTANDING UNDERSTANDING INDICATES

MILESTONES

ANALYSIS ANALYSIS

STUDY STUDY

ANALYSIS ANALYSIS

UNIT UNIT

KITS

DESIGN/REOMTS. DESIGN/REOMTS.

DEVELOPMENT DEVELOPMENT

KEY KEY

SYS. SYS.

ROBOTICS

RENDEZ. RENDEZ.

DEBRIS DEBRIS

SERVICING

SYSTEM SYSTEM

D. D.

B. B.

C. C.

A. A.

FIRST FIRST

BENEFIT BENEFIT

ALT. ALT.

SUPPORTING SUPPORTING

MISSION MISSION

SYSTEM SYSTEM

DEFINITION DEFINITION

ADV ADV

SYSTEMS SYSTEMS

• •

• • 7560-83 0BRFPV

< a. O

NASA

DEFINITION

U. CC Q.O

»- co

SEB

CONCEPT

•

CONTR.'S

MULTIPLE

O UJ

DEFIN

•

SYSTEMS

RFP

10/85V

SEB

OMV

4/86

CONTRACTS

S/v

UJ O

PRR

DEFIN.

OMV

PDR

V10/86

OC O UJ

SDR

PROGRAM

0C/D

•

FIGfFRE

OMV

MISSION

CDR

^79/87

b C/3

DEVELOPMENT

QC CL O U

_S7_

PDR

ADV.

SEB SRR

SDR

IRR

DEVELOPMENT

KIT(S)

—

— — INTERFACES

CAPABILITY

CDR

SOURCE

INTERFACE

MUTUAL

SYSTEM

CIR

DEVEL.

V1/89

EVAL.

DESIGN REQMTS.

PARTIC.

FRR

V10/89

REQMTS.

BD.;

IOC-1STFLT.

REVIEW

PLANNED

REVIEW

IOC

1983

KLAN KLAN

:Y199

FY91

22. 22.

DEC DEC

PF01/D PF01/D

JASON

1990

J J

CY CY

FY90

LAUNCH

I I

DEL

PHYSICAL

FRR FRR

[AJ

JASO

DELIV

PATHFINDER PATHFINDER

1989

QUALj

CY CY

ANALf

TESTS

" "

FY89

SYS SYS

I I

. .

CIR

PROPUL PROPUL

RADAR

A]S[O{NJD|

C/O

j j

& &

1988

TESTS TESTS

CY CY

ASSY, ASSY,

MAJMJ MAJMJ

SOFTWARE SOFTWARE

FY88

SCHEDULE

& &

J J

I I

STRUCT STRUCT

C/O

FABRI. FABRI.

PROC PROC

S S

INSTALL

TV TV

A A

CDR

1^87

j j j j

OMV OMV

FABRI FABRI

INSTALL

CY CY

INSTRUMENT INSTRUMENT

DEVELOPMENT DEVELOPMENT

FY87

FIGURE FIGURE

REVIEW REVIEW

DESIGN DESIGN

D D

& &

ASSY. ASSY.

FABRICATE. FABRICATE.

UNDERSTANDING UNDERSTANDING

FABRI. FABRI.

1986

0 0

DESIGN DESIGN

CY CY

DESIGN DESIGN

PRR PRR PDR PHASE

FY86

LL LL

ATP ATP

START)

1985

(SLOW (SLOW

INDICATES INDICATES

UNDERSTANDING UNDERSTANDING

______I______

CY CY

RFP RFP

FY85

TA)

(S/P (S/P

ASE

TESTS

DEVELOPMENT

INTEGRATION

& &

TESTS

ARTICLE ARTICLE

QUAL QUAL

TA TA

ROCUREMENTS

SYSTEM SYSTEM

SYS SYS

FLTUNITSi FLTUNITSi

STE

S/P S/P

TEST TEST

STRUCT/PROPULSION STRUCT/PROPULSION

TOOLING

DESIGN DESIGN 8962-83 PROGRAM

CURRENT

PROPULSION MODULES

DEDICATED

PROGRAM

NEAR

TERM

INCREASED

OMV

MANEUVERING

PROGRAM CAPABILITY PROGRAM

CURE

?.7

SPACE

STATION

EVOLUTION

BASED

CENTAUR

REMOTE

GEO

SERVICING/REFUELING

rA.

KITS

SUPPORT

FY88

RETRIEVAL

OPS OPS

MISSION MISSION

S/C S/C

SS SS

DEBRIS/TUMBLING DEBRIS/TUMBLING

TEST

SPACE SPACE DEFIN/DEVEL

ADV ADV

• •

OPS

MECHANISMS

SERVICING SERVICING

REMOTE REMOTE

DEV/TEST

BASED

DEMO w

STS-BASED STS-BASED

SERVICES

ORBITAL ORBITAL

GROUND GROUND

SUPPORTMG SUPPORTMG

(FY84$)

REFUELING REFUELING

TANKER

REMOTE REMOTE

• •

EVOLUTION

FIGURE FIGURE

SATELLITE SATELLITE

OPS OPS

STS

CAPABILITY CAPABILITY

REFUELED REFUELED

OF OF

1991

TANKER

ORBIT

REMOTE REMOTE

ON ON

OMV OMV

OUT OUT

TEST)

• •

SPACE-BASED SPACE-BASED

OMV

(UGHTINGJV) (UGHTINGJV)

& &

OMV

CONTROLS/DISPLAYS

CONCEPTS

REFUELING REFUELING

THE THE

DEVELOPMENTS/STUDIES DEVELOPMENTS/STUDIES

MECHANISMS MECHANISMS

(DEVEL (DEVEL

S/C S/C

REQMTS REQMTS

IN-LOOP IN-LOOP

MECHANISMS/SENSORS

OPS OPS

CAPABILITY CAPABILITY

REMOTE REMOTE

SENSOR SENSOR DOCKING DOCKING

MAN MAN

ADV ADV

REFUELING REFUELING

1990

• •

REMOTE REMOTE

RETRIEVAL

ADV ADV

& &

DEPLOYMENT DEPLOYMENT

S/C SUPPORTING SUPPORTING

MOCK-UP

OMV OMV

WITH WITH

FIGURE FIGURE

HOBILITY HOBILITY SIMULATOR

TELEOPERATOR TELEOPERATOR

.£» .£»

CJI "-H! MSEC

TELEOPERATOR/ROBOTIC DEVELOPMENT TELEOPERATOR/ROBOTIC

FACILITY