<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>200605 May/June 2006 Archives - Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</title>
	<atom:link href="https://insidegnss.com/category/issue-sorting/200605-may-june-2006/feed/" rel="self" type="application/rss+xml" />
	<link>https://insidegnss.com/category/issue-sorting/200605-may-june-2006/</link>
	<description>Global Navigation Satellite Systems Engineering, Policy, and Design</description>
	<lastBuildDate>Wed, 20 Jun 2018 00:28:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://insidegnss.com/wp-content/uploads/2017/12/site-icon.png</url>
	<title>200605 May/June 2006 Archives - Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</title>
	<link>https://insidegnss.com/category/issue-sorting/200605-may-june-2006/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>GPS III, Block IIF Programs Hit New Delays</title>
		<link>https://insidegnss.com/gps-iii-block-iif-programs-hit-new-delays/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Mon, 01 May 2006 07:06:23 +0000</pubDate>
				<category><![CDATA[200605 May/June 2006]]></category>
		<category><![CDATA[Aerospace and Defense]]></category>
		<category><![CDATA[Block IIF]]></category>
		<category><![CDATA[GPS]]></category>
		<category><![CDATA[L5]]></category>
		<category><![CDATA[military]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[satellites/space segment]]></category>
		<category><![CDATA[system infrastructure/technology]]></category>
		<guid isPermaLink="false">http://insidegnss.com/news/gps-iii-block-iif-programs-hit-new-delays/</guid>

					<description><![CDATA[<p>The GPS program appears to be struggling on several fronts recently. GPS III, the next-generation modernization project for the space and ground segments,...</p>
<p>The post <a href="https://insidegnss.com/gps-iii-block-iif-programs-hit-new-delays/">GPS III, Block IIF Programs Hit New Delays</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>The GPS program appears to be struggling on several fronts recently. </p>
<p>GPS III, the next-generation modernization project for the space and ground segments, is facing renewed uncertainty and possible schedule delays. At the same time, anticipated first launch of the follow-on block of satellites (Block IIF) with the new civil L5 signal has been postponed. </p>
<p><span id="more-23667"></span><br />
The GPS program appears to be struggling on several fronts recently. </p>
<p>GPS III, the next-generation modernization project for the space and ground segments, is facing renewed uncertainty and possible schedule delays. At the same time, anticipated first launch of the follow-on block of satellites (Block IIF) with the new civil L5 signal has been postponed. <br />
<!--break--><br />
The Air Force Acquisition Strategy Panel (ASP) will conduct a crucial meeting on June 7 to determine the new road map for GPS III. The Acquisition Strategy Panel is a panel of senior level acquisition personnel from offices of the Secretary of the Air Force for Acquisition (SAF/AQ), Air Force Materiel Command, and the user community, including Space &amp; Missile Center (SMC) representation, that provides advice to program managers on their acquisition strategies. </p>
<p>Representatives of the NAVSTAR GPS Joint Program office, which is part of the SMC at Los Angeles AFB, told Inside GNSS that &quot;pending results [from the ASP meeting] and approval of the acquisition strategy, a contract could be awarded as early as Dec 06/Jan 07.&quot; However, the JPO added, &quot;the ASP may decide to have the program continue with payload risk reduction and system definition efforts.&quot; </p>
<p>This final observation reflects Air Force interest in keeping the GPS III satellites light and simple enough to keep costs down and possibly permit them to be launched two at a time, further reducing program costs. That was also the recommendation of a Defense Science Board Task Force on GPS report released earlier this year. </p>
<p>Should the ASP elect to recommend contract award, the RFP release would normally occur about five to six weeks after the panel&#8217;s decision, according to an SMC spokesperson. Contract award is then normally projected at seven months after the ASP decision. </p>
<p>If the contract is delayed for a substantial period of time, however, it will put pressure on the two competing GPS III consortia, led the Boeing Company and Lockheed Martin, to keep their engineering teams intact during the interim. </p>
<p>Meanwhile, the Air Force has increased its calculations for mean mission duration (or MMD, or projected lifespan) of the replenishment block satellites, including the modernized version with the new civil L2C and military M-code (Block IIR and IIR-M). </p>
<p>A longer MMD allows the Air Force to slow the rate at which it replaces satellites. For instance, the first Block IIR-M launch was in September 2005 and the next is not scheduled until next September. </p>
<p><strong>Block IIF Difficulties.</strong> These developments are taking place at the same time that the U.S. Air Force is considering a plan to &quot;truncate&quot; the Block IIF buy at 12 satellites and introduce a phased GPS III technology development and acquisition plan. </p>
<p>That alternative calls for a GPS III contract in which the first set satellites would provide IIF-level capabilities that could be upgraded in later GPS III acquisition stages. It may also reflect unhappiness at what Air Force officials recently characterized as the &quot;technical difficulties&quot; encountered by IIF contractor Boeing that reportedly led to the launch delay from May 2007 to March 2008. </p>
<p>The continuing uncertainty in the GPS III program has not, however, dissuaded Lockheed Martin and EADS Astrium from announcing a teaming agreement to ensure interoperability of GPS III and the European GNSS, Galileo. </p>
<p>According to the agreement, the companies will perform systems engineering and technical assistance tasks for each other in the areas of interoperability, integrity and optimization of joint constellation performance. Additionally, the companies will offer reciprocal bids on operational hardware and software within the policy and export constraints of both programs. </p>
<p>A decision to award a single contract for modernized user equipment (MUE), the military handheld unit that will be able to process the M-code as well as legacy GPS signals, has also been delayed from its long-anticipated late-April decision deadline. </p>
<p>Failure to commit funds allocated for MUE by the end of March apparently led to the money being reprogrammed. However, according to Air Force and industry sources, the JPO is now looking at awarding three interim development contracts valued at about $7 million each in place of a single &quot;down-select&quot; award of about $11 million. </p>
<p>L3/Interstate Electronics, Rockwell Collins, and Raytheon are the three leading contenders for the contract and have been working under initial MUE contracts issued several years ago.</p>
<p><em>Copyright 2006 Gibbons Media and Research LLC</em></p>
<p>The post <a href="https://insidegnss.com/gps-iii-block-iif-programs-hit-new-delays/">GPS III, Block IIF Programs Hit New Delays</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Civil L1 Signals: Galileo ICD, GPS L1C, New MBOC</title>
		<link>https://insidegnss.com/civil-l1-signals-galileo-icd-gps-l1c-new-mboc/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Mon, 01 May 2006 07:04:07 +0000</pubDate>
				<category><![CDATA[200605 May/June 2006]]></category>
		<category><![CDATA[Aerospace and Defense]]></category>
		<category><![CDATA[civil]]></category>
		<category><![CDATA[commercial]]></category>
		<category><![CDATA[Galileo]]></category>
		<category><![CDATA[GPS]]></category>
		<category><![CDATA[signal]]></category>
		<category><![CDATA[system interoperability]]></category>
		<guid isPermaLink="false">http://insidegnss.com/news/civil-l1-signals-galileo-icd-gps-l1c-new-mboc/</guid>

					<description><![CDATA[<p>Within weeks of a bilateral working group’s recommendation for a common civil GNSS signal design, the European Galileo and U.S. GPS programs have...</p>
<p>The post <a href="https://insidegnss.com/civil-l1-signals-galileo-icd-gps-l1c-new-mboc/">Civil L1 Signals: Galileo ICD, GPS L1C, New MBOC</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Within weeks of a bilateral working group’s recommendation for a common civil GNSS signal design, the European Galileo and U.S. GPS programs have filed draft interface specifications (IS) or interface control documents (ICDs) for the new signals planned for the L1 frequency (around 1575 MHZ). </p>
<p><span id="more-23666"></span><br />
Within weeks of a bilateral working group’s recommendation for a common civil GNSS signal design, the European Galileo and U.S. GPS programs have filed draft interface specifications (IS) or interface control documents (ICDs) for the new signals planned for the L1 frequency (around 1575 MHZ). <br />
<!--break--><br />
The common design recommended by a technical working group set up under the 2004 US/EU agreement on GPS and Galileo is a multiplexed binary offset carrier (MBOC) signal, which is discussed in detail in the “Working Papers” column that begin on page 57 in this issue of Inside GNSS. </p>
<p>The working group recommendation and a joint statement, signed by the heads of the EU and U.S. delegations, can be found on the NAVSTAR GPS Joint Program Office (JPO) website as well as the <a href="http://www.galileoju.com/page3.cfm" target="_blank">Galileo Joint Undertaking (GJU) website</a>.<br />
 <br />
On April 19 2006, they issued a draft IS-GPS-800 for the so-called L1C signal proposed as part of the GPS III program still under development. The document marks the culmination of a yearslong civil/military effort. </p>
<p>The L1C signal will use a BOC modulation and consists of two main components: a pilot signal without any data message, which is spread by a ranging code, and a carrier that is spread by a ranging code and modulated by a data message. </p>
<p><strong>Galileo ICD Released.</strong> The long-awaited Galileo signal in space (SIS) ICD was posted May 23 on the <a href="http://www.galileoju.com/page2.cfm" target="_blank">Galileo Joint Undertaking (GJU) website</a>. The ICD covers the Galileo signals and services that will be transmitted at E1, E5, and E6 frequencies. In particular, it contains the spreading codes and navigation message format for the signals, which have not previously been publicly available and are needed by GNSS receiver designers and manufacturers in order to build Galileo-capable receivers. </p>
<p>Under the 2004 agreement, a BOC (1,1) modulation (denoting a subcarrier frequency and spreading code chipping rates both at 1.023 MHz) represents the baseline design for a common signal. However, the MBOC would interweave (or multiplex) BOC (6,1) and BOC (1,1) modulations, which would provide superior performance, according to its advocates, particularly in dealing with multipath (reflected signals) and code tracking in noisy RF conditions. </p>
<p><strong>MBOC Doubters.</strong> Despite the enthusiastic unanimous endorsement of the MBOC design by technical experts on the US/EU working group, others are not so sure — suggesting that MBOC will benefit applications requiring high- precision GNSS equipment to the disadvantage of consumers using low-cost GNSS receivers. </p>
<p>Receiver manufacturers of mass-market receivers use a narrower portion of the spread spectrum signal to reduce the costs of the equipment. They argue that, even though an MBOC signal could be received and processed on a BOC (1,1) receiver, the multiplexed signal will deliver between 0.5 and 1 decibel lower effective received power as well as lower effective signal bandwidth. </p>
<p>That arguably could raise difficulties for manufacturers and users who hope to employ high-sensitivity, but low-cost receivers, indoors or in other challenging environments. Qualcomm is among the skeptics of the multiplexed L1 design. The European Space Agency also reportedly would prefer to remain with the original BOC (1,1) design. </p>
<p>EU and U.S. officials are currently assessing the “relevant programmatic aspects of implementing the joint-optimization” as MBOC or BOC (1,1).</p>
<p><em>Copyright 2006 Gibbons Media and Research LLC</em></p>
<p>The post <a href="https://insidegnss.com/civil-l1-signals-galileo-icd-gps-l1c-new-mboc/">Civil L1 Signals: Galileo ICD, GPS L1C, New MBOC</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
