Synopsis: D-Request for Information for Rapid Delivery of Military Capabilities via Space; Notice Type: Sources Sought., 6594-6596 [E9-2716]
Download as PDF
<![CDATA[
6594
Federal Register / Vol. 74, No. 26 / Tuesday, February 10, 2009 / Notices
550 C Street W, Randolph Air Force
Base, TX 78150–4709; Chief of Air Force
Reserve, Headquarters United States Air
Force, Washington, DC 20330–1000;
The Director, Air National Guard,
Washington, DC 20310–2500; National
Military Personnel Records Center,
(NPRC/NRPMF), 9700 Page Boulevard,
St. Louis, MO 63132–5100, or directly to
agency officials at the respective system
location. Official mailing addresses are
published as an appendix to the Air
Force’s compilation of record systems
notices.
Written request should contain full
name, Social Security Number (SSN)
and complete mailing address with
notarized signature as below.
An unsworn declaration under
penalty of perjury in accordance with
section 1746 of 28 U.S.C. (Reference (n))
or notarized signatures are acceptable as
a means of proving the identity of the
individual.
If an unsworn declaration is executed
within the United States, its territories,
possessions, or commonwealths, it shall
read ‘‘I declare (or certify, verify, or
state) under penalty of perjury that the
foregoing is true and correct. Executed
on (date). (Signature).’’
If an unsworn declaration is executed
outside the United States, it shall read
‘‘I declare (or certify, verify, or state)
under penalty of perjury under the laws
of the United States of America that the
foregoing is true and correct. Executed
on (date). (Signature).’’
erowe on PROD1PC63 with NOTICES
RECORD ACCESS PROCEDURES:
Individuals seeking to access records
about themselves contained in this
system should address written inquiries
to Deputy Chief of Staff/Personnel,
Headquarters United States Air Force,
(USAF/A1), 1040 Air Force Pentagon,
Washington, DC 20330–1040;
Headquarters Air Force Personnel
Center, (HQ AFPC/DPSID), 550 C Street
W, Randolph Air Force Base, TX 78150–
4709; Chief of Air Force Reserve,
Headquarters United States Air Force,
Washington, DC 20330–1000; The
Director, Air National Guard,
Washington, DC 20310–2500; National
Military Personnel Records Center,
(NPRC/NRPMF), 9700 Page Boulevard,
St. Louis, MO 63132–2001, or directly to
agency officials at the respective system
location. Official mailing addresses are
published as an appendix to the Air
Force’s compilation of record systems
notices.
Written request should contain full
name, Social Security Number (SSN)
and complete mailing address with
notarized signature as below.
An unsworn declaration under
penalty of perjury in accordance with
VerDate Nov<24>2008
14:17 Feb 09, 2009
Jkt 217001
section 1746 of 28 U.S.C. (Reference (n))
or notarized signatures are acceptable as
a means of proving the identity of the
individual.
If an unsworn declaration is executed
within the United States, its territories,
possessions, or commonwealths, it shall
read ‘‘I declare (or certify, verify, or
state) under penalty of perjury that the
foregoing is true and correct. Executed
on (date). (Signature).’’
If an unsworn declaration is executed
outside the United States, it shall read
‘‘I declare (or certify, verify, or state)
under penalty of perjury under the laws
of the United States of America that the
foregoing is true and correct. Executed
on (date). (Signature).’’
CONTESTING RECORD PROCEDURES:
The Air Force rules for accessing
records and for contesting contents and
appealing initial agency determinations
are published in Air Force Instruction
33–332, Privacy Act Program, 32 CFR
part 806b; or may be obtained from the
system manager.
RECORD SOURCE CATEGORIES:
Performance evaluations that are
maintained on Air Force Active Duty,
Reserve, and Air National Guard
personnel in the grades of airman basic
E–1 through general O–10.
EXEMPTIONS CLAIMED FOR THE SYSTEM:
Brigadier General Selectee
Effectiveness Reports and Colonel and
Lieutenant Colonel Promotion
recommendations with close out dates
on or before January 31, 1991, may be
exempt under the provisions of 5 U.S.C.
552a(k)(7) from subsections of 5 U.S.C.
552a(c)(3); (d); (e)(4)(H); and (f), as
applicable, but only to the extent that
disclosure would reveal the identity of
a confidential source. For additional
information contact the system manager.
An exemption rule has been
promulgated in accordance with the
requirements of 5 U.S.C. 553(b)(1), (2),
and (3), (c) and (e) and published in the
32 CFR part 806b.
[FR Doc. E9–2782 Filed 2–9–09; 8:45 am]
BILLING CODE 5001–06–P
DEPARTMENT OF DEFENSE
Department of the Air Force
[Solicitation Number: TBD, Classification
Code: TBD, NAICS Code: TBD]
Synopsis: D—Request for Information
for Rapid Delivery of Military
Capabilities via Space; Notice Type:
Sources Sought.
Closing Date: March 15, 2009.
PO 00000
Frm 00026
Fmt 4703
Sfmt 4703
SUMMARY: The purpose for this Request
For Information (RFI) is to identify (1)
near-term industry solutions that could
provide the Department of Defense
(DoD) the capability to rapidly deliver
military capabilities via space, and (2)
long-term advanced space transport
concepts that could evolve from nearterm capabilities. Interested sources
should provide a white paper describing
current space transport technologies and
capabilities, and commercial visions for
future capabilities that are projected to
evolve from those current space
transport technologies. The vision in the
white paper should be tailored towards
the interests of the U.S. Government
that are outlined in the questions listed
below.
In order to clarify the DoD’s need in
this area and to develop a technology
assessment for these capabilities, the
National Security Space Office (NSSO)
and Headquarters, Air Force Security
Forces Center (HQ AFSFC) are cohosting a Technology Forum for the
Rapid Delivery of Military Capabilities
via Space on 24–26 Feb 2009 at
Lackland Air Force Base, San Antonio,
TX. This Technology Forum is open to
all industry, U.S. Government, and
military interested in assisting in the
development of a technology assessment
for this capability. This RFI is being
released prior to the Technology Forum
in order to help generate thought for
discussion at the event. Responses are
due 15 Mar 09, after the Technology
Forum, so the combination of this
solicitation and the events at the
Technology Forum will help to refine
responses.
The concept of Rapid Delivery of
Military Capabilities via Space was
based initially on the Marine Corps’
Small Unit Space Transport and
Insertion (SUSTAIN) concept which
would provide the Joint Force
Commander (JFC) the capacity to
rapidly transport operationally relevant
capabilities to any point on the globe,
effectively instantaneously. The
SUSTAIN capability spans the full
spectrum of conflict, from strategic
Special Forces employment to a full
range of specialized manned and
unmanned warfighting payloads. The
formal need for a SUSTAIN capability is
documented in the Marine Corps
SUSTAIN Universal Need Statement
dated 22 July 2002, and the USSOCOM
Space Enabling Concept dated 25 March
2004.
RFI Requirements
The first section of this RFI seeks to
identify information on existing
commercial systems or low risk systems
in development that could potentially
E:\FR\FM\10FEN1.SGM
10FEN1
erowe on PROD1PC63 with NOTICES
Federal Register / Vol. 74, No. 26 / Tuesday, February 10, 2009 / Notices
apply to a DoD capability to rapidly
transport militarily relevant capabilities
through sub-orbital space to a remote
location on short notice. This nearerterm capability could serve as the first
phase of a spiral developmental effort.
The following specific definitions are
applicable to this first section of the RFI:
• The ‘‘transport altitude regime’’ is
defined by upper and lower sub-orbital
space boundaries, namely between an
altitude above 50 nautical miles and an
altitude below that which requires prior
USSTRATCOM coordination.
• ‘‘Rapidly’’ is defined as two hours
or less of flight time, preceded by a
launch preparation period, with the
combined total of flight time and
preparation time not to exceed four
hours.
• ‘‘Militarily relevant payloads’’ are
defined as an Unmanned Aerial System
(UAS) or an Unmanned Ground Vehicle
(UGV), either alternative having a mass
of 200 kilograms or less, a transport
volume of 2 cubic meters or less, and
either system must be fully operational
upon delivery.
• The ‘‘target destination’’ is defined
as any point within 5,000 Nautical miles
of the launch site, including options to
launch a UAS directly into target
airspace at high altitude or land a UGV
on the ground at a prepared or
unprepared site.
• The delivery vehicle, whether a
single stage vehicle or the upper stage
of a multi-stage vehicle, must be
recoverable and reusable.
With respect to the specific
definitions above that are related to
nearer-term technologies and
capabilities, this RFI seeks answers to
the following specific questions:
a. What plans would improve suborbital and/or orbital space transport
capabilities in these areas: (1) Spacebased capabilities; (2) Terrestrial
capabilities; (3) Enabling capabilities;
(4) Non-material aspects including
policies, procedures, and operations
concepts?
b. What technologies are needed to
achieve, maintain, or improve suborbital and/or orbital space transport
capabilities? What is the practical limit
of these technologies?
c. What technologies are considered
high payoff for future sub-orbital and/or
orbital space transport capabilities,
including those without current funding
support or U.S. Government
sponsorship?
d. To what extent should autonomy or
automation be implemented in ground
and sub-orbital and/or orbital space
systems to support space as a transport
medium?
VerDate Nov<24>2008
14:17 Feb 09, 2009
Jkt 217001
e. What sub-orbital and/or orbital
capabilities should the U.S. Government
provide? Which commercial capabilities
do you believe could enhance U.S.
Government-provided sub-orbital and/
or orbital space transport capabilities?
f. In order to achieve needed suborbital and/or orbital space
transportation capabilities through the
2025 time frame, what international
cooperation will be required?
g. What interrelationship is planned
or desired with the U.S. Government
through the 2025 time frame from a suborbital and/or orbital space transport
perspective? What Position, Navigation,
Timing (PNT) capabilities are expected
from the U.S. Government?
h. What interest is there in providing
selected sub-orbital and/or orbital space
transport capabilities?
i. What interest is there in providing
a full range of sub-orbital and/or orbital
space transport services to the U.S.
Government?
j. What analytical tools or simulations
are recommend for assessing the
performance, cost, and utility associated
with sub-orbital and/or orbital space
transport capabilities?
k. How do purchasers of sub-orbital
and/or orbital space transport end-user
equipment make their needs known to
the provider?
l. In general, what are the most
important attributes of sub-orbital and/
or orbital space transport services (or
combinations of services) for a
consumer?
This second section of the RFI seeks
to identify industry concepts that could
lead to a future DoD capacity to rapidly
transport a full spectrum of militarily
relevant capabilities through sub-orbital
and/or orbital space to any point
globally on short notice. Such concepts
could constitute advanced phases of the
spiral developmental effort described
above. Accordingly, information is
solicited on the following advanced
capabilities, capabilities that are
formulated as questions for RFI
responses:
a. Can capabilities be scaled up for the
purpose of delivering unmanned
payloads of up to 30,000 pounds
suborbitally to any point on the globe,
including the poles? If so, describe a
notional spiral evolution to the future
capability?
b. Can capabilities be scaled up for
the purpose of delivering militarily
relevant payloads to low earth orbit? If
so, describe a notional spiral evolution
to the future capability?
c. Can capabilities be integrated with
Government Furnished Equipment
(GFE) launch vehicles such as the Atlas,
Delta, and future families of launch
PO 00000
Frm 00027
Fmt 4703
Sfmt 4703
6595
vehicles? If so, describe a notional spiral
evolution to the future capability?
d. Can individual vehicle capabilities
be man-rated to enable the insertion of
a squad-sized, combat-equipped team
into any global contingency? If so,
describe a notional spiral evolution to
the future capability?
e. Can capabilities evolve to a family
of assault support vehicles capable of
launch on demand and refuelingassisted transport and insertion of
systems and forces? If so, describe a
notional spiral evolution to the future
capability?
f. Can capabilities be scaled up to
permit the insertion of unmanned
capabilities or manned teams that is still
capable of self-extraction without
refueling? If so, describe a notional
spiral evolution to the future capability?
g. Can capabilities allow for a low
earth orbit (LEO) loiter-like capability?
h. Can capabilities be increased into
an on-orbit support infrastructure for
space-based support, allowing for the
timed injection of into any contingency
from orbit? If so, describe a notional
spiral evolution to the future capability?
i. Can capabilities allow for an entire
mission cycle from launch, through
transit, insertion, terrestrial or space
execution, extraction, and finally egress
to any global point of origin, without the
need for refueling?
RFI Purpose and Limitations
The U.S. Government is aware of and
understands the tactical, operational,
and strategic opportunities that space
can provide the DoD from the
perspective of speed of delivery and
global reach. The Government’s
intention is to better understand the
current, state-of-the-art capabilities and
future technological projections to
determine a technological assessment.
Industry feedback is vitally important
and the Government will be receptive to
any and all ideas received from
industry. This RFI is an expression of
the Government’s interest only and does
not obligate the Government to pay for
the requested information nor respond
to any submissions. Responses to this
notice are not offers and cannot be
accepted by the Government to form a
binding contract. Proprietary
information is not being solicited;
however, if it is submitted, it should be
properly marked.
Please limit formal white paper
submission to no more than ten (10)
pages, not including the cover letter or
any attachments. In addition, it may
include up to five attachments that
consist of briefing slides, suggested
contract language, current plans, or
standard operating procedures.
E:\FR\FM\10FEN1.SGM
10FEN1
6596
Federal Register / Vol. 74, No. 26 / Tuesday, February 10, 2009 / Notices
Electronic submissions are strongly
encouraged. All items must be
compatible with Microsoft Office or
Adobe PDF format and free of all
computer viruses.
Technical questions and industry
responses shall be submitted via email
to: LtCol Paul Damphousse,
paul.damphousse@osd.mil.
Responses must be received no later
than 2 p.m. Eastern Standard Time, on
March 15, 2009.
All material submitted in response to
this RFI must be unclassified and, if
proprietary, marked appropriately.
Point of Contact: LtCol Paul
Damphousse,
paul.damphousse@osd.mil, or (571)
432–1411.
This Is a Request for Information (RFI)
Only
This RFI is issued as Market Research,
solely for information and planning
purposes. It shall not be considered as
an Invitation for Bid (IFB), Request for
Quotation (RFQ), Request for Proposal
(RFP), or as an obligation on the part of
the Government to acquire any products
or services. Any response to this
synopsis will be treated as information
only. No entitlement to payment of
direct or indirect costs or charges by the
Government will arise as a result of
contractor submission of responses to
this synopsis or the Government for use
of such information. The information
provided may be used by the National
Security Space Office in developing a
strategy and in a Statement of Work/
Statement of Objectives and
Performance specifications for any
future study. Not responding to this RFI
does not preclude participation in any
future RFP, if issued. If a solicitation is
issued, it will be synopsized on the
Federal Business Opportunities
(FedBizOpps) Web site. It is the
responsibility of any potential offeror to
monitor this site for additional
information pertaining to this
requirement.
Bao-Anh Trinh,
Air Force Federal Register Liaison Officer.
[FR Doc. E9–2716 Filed 2–9–09; 8:45 am]
ACTION: Notice To Alter a System of
Records.
SUMMARY: The Department of the Army
is proposing to alter a system of records
in its existing inventory of records
systems subject to the Privacy Act of
1974, (5 U.S.C. 552a), as amended.
DATES: The proposed action will be
effective on March 12, 2009 unless
comments are received that would
result in a contrary determination.
ADDRESSES: Department of the Army,
Privacy Office, U.S. Army Records
Management and Declassification
Agency, 7701 Telegraph Road, Casey
Building, Suite 144, Alexandria, VA
22325–3905.
FOR FURTHER INFORMATION CONTACT: Mr.
Robert Dickerson, (703) 428–6513.
SUPPLEMENTARY INFORMATION: The
Department of the Army systems of
records notices subject to the Privacy
Act of 1974, (5 U.S.C. 552a), as
amended, have been published in the
Federal Register and are available from
the address above.
The proposed system report, as
required by 5 U.S.C. 552a(r) of the
Privacy Act of 1974, as amended, was
submitted on January 30, 2009, to the
House Committee on Oversight and
Government Reform, the Senate
Committee on Homeland Security and
Governmental Affairs, and the Office of
Management and Budget (OMB)
pursuant to paragraph 4c of Appendix I
to OMB Circular No. A–130, ‘Federal
Agency Responsibilities for Maintaining
Records About Individuals,’ dated
February 8, 1996 (February 20, 1996, 61
FR 6427).
Dated: February 4, 2009.
Morgan E. Frazier,
Alternate OSD Federal Register Liaison
Officer, Department of Defense.
A0381–20b DAMI
SYSTEM NAME:
Counterintelligence/Information
Operations/Security Files (December 14,
2001, 66 FR 64811).
CHANGES:
*
BILLING CODE 5001–05–P
*
*
*
*
SYSTEM NAME:
Department of the Army
Delete entry and replace with
‘‘Foreign Intelligence/
Counterintelligence/Information
Operations/Security Files.’’
[Docket ID USA–2009–0001]
CATEGORIES OF INDIVIDUALS COVERED BY THE
SYSTEM:
erowe on PROD1PC63 with NOTICES
DEPARTMENT OF DEFENSE
Privacy Act of 1974; System of
Records
AGENCY:
Department of the Army, DoD.
VerDate Nov<24>2008
14:17 Feb 09, 2009
Jkt 217001
Delete entry and replace with
‘‘Military personnel of the U.S. Army,
including active duty, National Guard,
reservists and retirees; civilian
PO 00000
Frm 00028
Fmt 4703
Sfmt 4703
employees of the Department of the
Army (DA), including contract,
temporary, part-time, and advisory,
citizen and alien employees located
both in the U.S. and in overseas areas;
individuals identified in foreign
intelligence or counterintelligence
reports and supportive material,
including individuals involved in
matters of foreign intelligence interest;
industrial or contractor personnel
working in private industry which have
contracts involving classified
Department of Defense (DoD)
information; aliens granted limited
access authorization to U.S. Defense
information; alien personnel
investigated for visa purposes; certain
non-DoD affiliated persons whose
activities involve them with the DoD,
namely, activities involving requests for
admission to DoD facilities or requests
for certain information regarding DoD
personnel, activities, or facilities;
persons formerly affiliated with the
DoD; persons who applied for or are/
were being considered for employment
with or access to DoD such as applicants
for military service, pre inductees and
prospective contractors; individuals
residing on, having authorized official
access to, or conducting or operating
any business or other function at any
DoD installation and facility; and U.S.
Army Intelligence sources; and U.S.
persons who have been declared
missing, prisoners of war (POW),
civilian persons who are being detained
or held hostage or personnel recovered
from hostile control; persons of interest
encountered as part of military
operations; individuals to include those
brought to the attention of DoD by
federal, state, local, tribal, foreign, or
international organizations/agencies
about whom there is a reasonable basis
to believe that they are engaged in, or
plan to engage in, activities such as (1)
sabotage, (2) possible compromise of
classified defense information by
unauthorized disclosure or by
espionage, treason or spying; (3)
terrorism; (4) narcotics trafficking; (5)
activities that are a direct threat to
national or international security, or the
conduct of military operations, (6)
subversion of loyalty, discipline or
morale of DoD military or civilian
personnel by actively encouraging
violation of lawful orders and
regulations or disruption of military
activities, and (7) activities that are a
direct threat to DoD personnel, facilities
and material or classified Defense
contractor facilities or those individuals
suspected or involved in criminal and
intelligence activities directed against or
involving DoD Information Systems.’’
E:\FR\FM\10FEN1.SGM
10FEN1
]]>Agencies
[Federal Register Volume 74, Number 26 (Tuesday, February 10, 2009)]
[Notices]
[Pages 6594-6596]
From the Federal Register Online via the Government Printing Office [www.gpo.gov]
[FR Doc No: E9-2716]
-----------------------------------------------------------------------
DEPARTMENT OF DEFENSE
Department of the Air Force
[Solicitation Number: TBD, Classification Code: TBD, NAICS Code: TBD]
Synopsis: D--Request for Information for Rapid Delivery of
Military Capabilities via Space; Notice Type: Sources Sought.
Closing Date: March 15, 2009.
SUMMARY: The purpose for this Request For Information (RFI) is to
identify (1) near-term industry solutions that could provide the
Department of Defense (DoD) the capability to rapidly deliver military
capabilities via space, and (2) long-term advanced space transport
concepts that could evolve from near-term capabilities. Interested
sources should provide a white paper describing current space transport
technologies and capabilities, and commercial visions for future
capabilities that are projected to evolve from those current space
transport technologies. The vision in the white paper should be
tailored towards the interests of the U.S. Government that are outlined
in the questions listed below.
In order to clarify the DoD's need in this area and to develop a
technology assessment for these capabilities, the National Security
Space Office (NSSO) and Headquarters, Air Force Security Forces Center
(HQ AFSFC) are co-hosting a Technology Forum for the Rapid Delivery of
Military Capabilities via Space on 24-26 Feb 2009 at Lackland Air Force
Base, San Antonio, TX. This Technology Forum is open to all industry,
U.S. Government, and military interested in assisting in the
development of a technology assessment for this capability. This RFI is
being released prior to the Technology Forum in order to help generate
thought for discussion at the event. Responses are due 15 Mar 09, after
the Technology Forum, so the combination of this solicitation and the
events at the Technology Forum will help to refine responses.
The concept of Rapid Delivery of Military Capabilities via Space
was based initially on the Marine Corps' Small Unit Space Transport and
Insertion (SUSTAIN) concept which would provide the Joint Force
Commander (JFC) the capacity to rapidly transport operationally
relevant capabilities to any point on the globe, effectively
instantaneously. The SUSTAIN capability spans the full spectrum of
conflict, from strategic Special Forces employment to a full range of
specialized manned and unmanned warfighting payloads. The formal need
for a SUSTAIN capability is documented in the Marine Corps SUSTAIN
Universal Need Statement dated 22 July 2002, and the USSOCOM Space
Enabling Concept dated 25 March 2004.
RFI Requirements
The first section of this RFI seeks to identify information on
existing commercial systems or low risk systems in development that
could potentially
[[Page 6595]]
apply to a DoD capability to rapidly transport militarily relevant
capabilities through sub-orbital space to a remote location on short
notice. This nearer-term capability could serve as the first phase of a
spiral developmental effort. The following specific definitions are
applicable to this first section of the RFI:
The ``transport altitude regime'' is defined by upper and
lower sub-orbital space boundaries, namely between an altitude above 50
nautical miles and an altitude below that which requires prior
USSTRATCOM coordination.
``Rapidly'' is defined as two hours or less of flight
time, preceded by a launch preparation period, with the combined total
of flight time and preparation time not to exceed four hours.
``Militarily relevant payloads'' are defined as an
Unmanned Aerial System (UAS) or an Unmanned Ground Vehicle (UGV),
either alternative having a mass of 200 kilograms or less, a transport
volume of 2 cubic meters or less, and either system must be fully
operational upon delivery.
The ``target destination'' is defined as any point within
5,000 Nautical miles of the launch site, including options to launch a
UAS directly into target airspace at high altitude or land a UGV on the
ground at a prepared or unprepared site.
The delivery vehicle, whether a single stage vehicle or
the upper stage of a multi-stage vehicle, must be recoverable and
reusable.
With respect to the specific definitions above that are related to
nearer-term technologies and capabilities, this RFI seeks answers to
the following specific questions:
a. What plans would improve sub-orbital and/or orbital space
transport capabilities in these areas: (1) Space-based capabilities;
(2) Terrestrial capabilities; (3) Enabling capabilities; (4) Non-
material aspects including policies, procedures, and operations
concepts?
b. What technologies are needed to achieve, maintain, or improve
sub-orbital and/or orbital space transport capabilities? What is the
practical limit of these technologies?
c. What technologies are considered high payoff for future sub-
orbital and/or orbital space transport capabilities, including those
without current funding support or U.S. Government sponsorship?
d. To what extent should autonomy or automation be implemented in
ground and sub-orbital and/or orbital space systems to support space as
a transport medium?
e. What sub-orbital and/or orbital capabilities should the U.S.
Government provide? Which commercial capabilities do you believe could
enhance U.S. Government-provided sub-orbital and/or orbital space
transport capabilities?
f. In order to achieve needed sub-orbital and/or orbital space
transportation capabilities through the 2025 time frame, what
international cooperation will be required?
g. What interrelationship is planned or desired with the U.S.
Government through the 2025 time frame from a sub-orbital and/or
orbital space transport perspective? What Position, Navigation, Timing
(PNT) capabilities are expected from the U.S. Government?
h. What interest is there in providing selected sub-orbital and/or
orbital space transport capabilities?
i. What interest is there in providing a full range of sub-orbital
and/or orbital space transport services to the U.S. Government?
j. What analytical tools or simulations are recommend for assessing
the performance, cost, and utility associated with sub-orbital and/or
orbital space transport capabilities?
k. How do purchasers of sub-orbital and/or orbital space transport
end-user equipment make their needs known to the provider?
l. In general, what are the most important attributes of sub-
orbital and/or orbital space transport services (or combinations of
services) for a consumer?
This second section of the RFI seeks to identify industry concepts
that could lead to a future DoD capacity to rapidly transport a full
spectrum of militarily relevant capabilities through sub-orbital and/or
orbital space to any point globally on short notice. Such concepts
could constitute advanced phases of the spiral developmental effort
described above. Accordingly, information is solicited on the following
advanced capabilities, capabilities that are formulated as questions
for RFI responses:
a. Can capabilities be scaled up for the purpose of delivering
unmanned payloads of up to 30,000 pounds suborbitally to any point on
the globe, including the poles? If so, describe a notional spiral
evolution to the future capability?
b. Can capabilities be scaled up for the purpose of delivering
militarily relevant payloads to low earth orbit? If so, describe a
notional spiral evolution to the future capability?
c. Can capabilities be integrated with Government Furnished
Equipment (GFE) launch vehicles such as the Atlas, Delta, and future
families of launch vehicles? If so, describe a notional spiral
evolution to the future capability?
d. Can individual vehicle capabilities be man-rated to enable the
insertion of a squad-sized, combat-equipped team into any global
contingency? If so, describe a notional spiral evolution to the future
capability?
e. Can capabilities evolve to a family of assault support vehicles
capable of launch on demand and refueling-assisted transport and
insertion of systems and forces? If so, describe a notional spiral
evolution to the future capability?
f. Can capabilities be scaled up to permit the insertion of
unmanned capabilities or manned teams that is still capable of self-
extraction without refueling? If so, describe a notional spiral
evolution to the future capability?
g. Can capabilities allow for a low earth orbit (LEO) loiter-like
capability?
h. Can capabilities be increased into an on-orbit support
infrastructure for space-based support, allowing for the timed
injection of into any contingency from orbit? If so, describe a
notional spiral evolution to the future capability?
i. Can capabilities allow for an entire mission cycle from launch,
through transit, insertion, terrestrial or space execution, extraction,
and finally egress to any global point of origin, without the need for
refueling?
RFI Purpose and Limitations
The U.S. Government is aware of and understands the tactical,
operational, and strategic opportunities that space can provide the DoD
from the perspective of speed of delivery and global reach. The
Government's intention is to better understand the current, state-of-
the-art capabilities and future technological projections to determine
a technological assessment. Industry feedback is vitally important and
the Government will be receptive to any and all ideas received from
industry. This RFI is an expression of the Government's interest only
and does not obligate the Government to pay for the requested
information nor respond to any submissions. Responses to this notice
are not offers and cannot be accepted by the Government to form a
binding contract. Proprietary information is not being solicited;
however, if it is submitted, it should be properly marked.
Please limit formal white paper submission to no more than ten (10)
pages, not including the cover letter or any attachments. In addition,
it may include up to five attachments that consist of briefing slides,
suggested contract language, current plans, or standard operating
procedures.
[[Page 6596]]
Electronic submissions are strongly encouraged. All items must be
compatible with Microsoft Office or Adobe PDF format and free of all
computer viruses.
Technical questions and industry responses shall be submitted via
email to: LtCol Paul Damphousse, paul.damphousse@osd.mil.
Responses must be received no later than 2 p.m. Eastern Standard
Time, on March 15, 2009.
All material submitted in response to this RFI must be unclassified
and, if proprietary, marked appropriately.
Point of Contact: LtCol Paul Damphousse, paul.damphousse@osd.mil,
or (571) 432-1411.
This Is a Request for Information (RFI) Only
This RFI is issued as Market Research, solely for information and
planning purposes. It shall not be considered as an Invitation for Bid
(IFB), Request for Quotation (RFQ), Request for Proposal (RFP), or as
an obligation on the part of the Government to acquire any products or
services. Any response to this synopsis will be treated as information
only. No entitlement to payment of direct or indirect costs or charges
by the Government will arise as a result of contractor submission of
responses to this synopsis or the Government for use of such
information. The information provided may be used by the National
Security Space Office in developing a strategy and in a Statement of
Work/Statement of Objectives and Performance specifications for any
future study. Not responding to this RFI does not preclude
participation in any future RFP, if issued. If a solicitation is
issued, it will be synopsized on the Federal Business Opportunities
(FedBizOpps) Web site. It is the responsibility of any potential
offeror to monitor this site for additional information pertaining to
this requirement.
Bao-Anh Trinh,
Air Force Federal Register Liaison Officer.
[FR Doc. E9-2716 Filed 2-9-09; 8:45 am]
BILLING CODE 5001-05-P
