<?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>200709 September/October 2007 Archives - Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</title>
	<atom:link href="https://insidegnss.com/category/issue-sorting/200709-september-october-2007/feed/" rel="self" type="application/rss+xml" />
	<link>https://insidegnss.com/category/issue-sorting/200709-september-october-2007/</link>
	<description>Global Navigation Satellite Systems Engineering, Policy, and Design</description>
	<lastBuildDate>Mon, 20 Aug 2018 02:34:55 +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>200709 September/October 2007 Archives - Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</title>
	<link>https://insidegnss.com/category/issue-sorting/200709-september-october-2007/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>USAF evolves GPS architecture with $800 million upgrade to ground control segment</title>
		<link>https://insidegnss.com/usaf-evolves-gps-architecture-with-800-million-upgrade-to-ground-control-segment/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Sat, 15 Sep 2007 00:18:18 +0000</pubDate>
				<category><![CDATA[200709 September/October 2007]]></category>
		<category><![CDATA[Aerospace and Defense]]></category>
		<category><![CDATA[GPS]]></category>
		<category><![CDATA[infrastructure]]></category>
		<category><![CDATA[military]]></category>
		<category><![CDATA[satellites/space segment]]></category>
		<category><![CDATA[signal]]></category>
		<category><![CDATA[system infrastructure/technology]]></category>
		<guid isPermaLink="false">http://insidegnss.com/news/usaf-evolves-gps-architecture-with-800-million-upgrade-to-ground-control-segment/</guid>

					<description><![CDATA[<p>On September 14, Air Force crews at Schriever AFB, Colorado, completed the initial phase of an $800 million upgrade to the GPS operational...</p>
<p>The post <a href="https://insidegnss.com/usaf-evolves-gps-architecture-with-800-million-upgrade-to-ground-control-segment/">USAF evolves GPS architecture with $800 million upgrade to ground control segment</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>
On September 14, Air Force crews at Schriever AFB, Colorado, completed the initial phase of an $800 million upgrade to the GPS operational control segment.
</p>
<p>
Operators in the 2nd Space Operations Squadron (2SOPS) of the USAF 50th Space Wing migrated control of the GPS satellite constellation and ground monitoring facilities from a 1970s-era mainframe computer to a distributed IT infrastructure with advanced automated features. The 50th Space Wing, through the 2nd SOPS, performs the satellite command and control mission for the Global Positioning System.
</p>
<p><span id="more-23683"></span></p>
<p>
On September 14, Air Force crews at Schriever AFB, Colorado, completed the initial phase of an $800 million upgrade to the GPS operational control segment.
</p>
<p>
Operators in the 2nd Space Operations Squadron (2SOPS) of the USAF 50th Space Wing migrated control of the GPS satellite constellation and ground monitoring facilities from a 1970s-era mainframe computer to a distributed IT infrastructure with advanced automated features. The 50th Space Wing, through the 2nd SOPS, performs the satellite command and control mission for the Global Positioning System.
</p>
<p>
The upgrade, called the Architecture Evolution Plan (AEP), will add new digital communications and a new message format for telemetry, tracking, and control (TT&amp;C) —uploading information and operational commands to the GPS satellites. A new capability to command satellites through Air Force Satellite Control Network (AFSCN), will increase the number of available antennas for contacting satellites.
</p>
<p>
The Air Force team, along with contractors from Boeing, Lockheed Martin, and The Aerospace Corporation, have been preparing for the transition to the new control segment since March 2006.
</p>
<p>
“This is like changing the engine on a car while it is traveling 50 miles an hour down the road,” says Lt. Gen. Michael Hamel, commander of the Space and Missile Systems Center at Los Angeles AFB, California, where the GPS Wing is located.
</p>
<p>
The upgrade also involved installing and activating the alternate Master Control Station at Vandenberg AFB, California, and upgrading the current GPS ground antennas.
</p>
<p>
The addition of eight National Geospatial-Intelligence Agency facilities to the six GPS-dedicated monitoring stations around the globe will reportedly provide triple-redundancy tracking of satellites — that is, every satellite will be visible to at least three ground stations 99 percent of the time to quickly identify signal anomalies or outages.
</p>
<p>
<strong>Groundwork for the Future </strong><br />
AEP will lay the foundation for future improvements to the Operational Control Segment (OCS) to support new capabilities, such as those that will become available with the GPS Block IIF satellites. A further AEP upgrade next summer will enable support the new Master Control Station at Schriever to operate the IIFs, the first launch of which has been delayed until late in 2008.
</p>
<p>
On August 27, under GPS Wing review, the first GPS Block IIF satellite successfully passed its Initial Integrated System Test (IIST) at the Boeing Spacecraft Development Center in El Segundo, California. Completion of the IIST signifies the spacecraft is ready to enter acoustic, separation, and thermal vacuum testing.
</p>
<p>
A next-generation GPS control segment (OCX) is scheduled to be in place in the 2011–12 time frame to support the GPS III generation of satellites scheduled to launch beginning in 2013. Three industry teams led by Lockheed Martin, Raytheon, and Boeing are competing for the OCX contract, which is expected to be announced soon. A request for proposals to build the GPS IIIA satellites was issued earlier this year, with a decision now not expected before early 2008.
</p>
<p>
<strong>Hope for Invisible Transition</strong><br />
Rehearsed several times several times in advance, the Air Force used a phased approach with satellites transitioning to the new OCS one at a time.
</p>
<p>
The new AEP message structure has been analyzed down to the bit, according to Air Force officials, and is functionally equivalent to the legacy message. It incorporates a new Kalman filter that will enable the system controllers to monitor and control more satellites and signals, including uploading navigation messages more frequently. The legacy TT&amp;C architecture can only support about 31 satellites but will be able to handle up to 60 after OCX is complete in 2013, according to Col. David Madden, commander of the GPS Wing.
</p>
<p>
According to the Air Force, in the event of an unforeseen anomaly during transition, the process is fully reversible at any time.
</p>
<p>
The transition to AEP was originally scheduled to occur more than five years ago. But the task turned out to be more complicated than expected. The AEP makes use of a unique complex software system that is a wholesale replacement for the old one. Moreover, additional requirements were added and others changed over the course of development as the system and software matured, according to statements from the GPS Wing.
</p>
<p>
<strong>Help for civilian GPS users </strong><br />
Air Force officials expected that the transition would be transparent to GPS users. However, should problems appear that might be connected with AEP, civil users may contact the U.S. Coast Guard Navigation Center, telephone 703-313-5900, website &lt;<a href="http://www.navcen.uscg.gov/" target="_blank">http://www.navcen.uscg.gov/</a>&gt;.
</p>
<p>
<strong>Help for military GPS users</strong><br />
Military users should contact the GPS Operations Center, telephone DSN 560-2541 OR commercial 719-567-2451, website &lt;<a href="http://gps.afspc.af.mil/GPSOC/" target="_blank">http://gps.afspc.af.mil/GPSOC/</a>&gt;.</p>
<p>The post <a href="https://insidegnss.com/usaf-evolves-gps-architecture-with-800-million-upgrade-to-ground-control-segment/">USAF evolves GPS architecture with $800 million upgrade to ground control segment</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>ICG  sets up new Providers Forum to pursue compatibility among  GNSS systems, augmentation systems</title>
		<link>https://insidegnss.com/icg-sets-up-new-providers-forum-to-pursue-compatibility-among-gnss-systems-augmentation-systems/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Wed, 12 Sep 2007 22:39:00 +0000</pubDate>
				<category><![CDATA[200709 September/October 2007]]></category>
		<category><![CDATA[International Committe on GNSS]]></category>
		<category><![CDATA[Office of Space and Advanced Technology]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[State Department Ken Hodgkins]]></category>
		<category><![CDATA[system interoperability]]></category>
		<guid isPermaLink="false">http://insidegnss.com/news/icg-sets-up-new-providers-forum-to-pursue-compatibility-among-gnss-systems-augmentation-systems/</guid>

					<description><![CDATA[<p>Operators of the world’s four GNSS systems and regional augmentation systems have laid the foundation for a multilateral environment in which to discuss...</p>
<p>The post <a href="https://insidegnss.com/icg-sets-up-new-providers-forum-to-pursue-compatibility-among-gnss-systems-augmentation-systems/">ICG  sets up new Providers Forum to pursue compatibility among  GNSS systems, augmentation systems</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[<div class='special_post_image'><img decoding="async" class='specialimageclass img-thumbnail' src="https://insidegnss.com/wp-content/uploads/2018/01/icg-members-nov2006a.jpg" ><span class='specialcaption'></span></div>
<p>
Operators of the world’s four GNSS systems and regional augmentation systems have laid the foundation for a multilateral environment in which to discuss issues of compatibility and interoperability.</p>
<p><span id="more-23684"></span></p>
<p>
Operators of the world’s four GNSS systems and regional augmentation systems have laid the foundation for a multilateral environment in which to discuss issues of compatibility and interoperability.</p>
<p>Meeting September 4 in Bangalore, India, in advance of a session of the International Committee on GNSS (ICG), six nations established a Providers Forum that will operate in parallel with the United Nations–backed group. Ken Hodgkins, deputy director of the State Department’s Office of Space &amp; Advanced Technology, characterized the ICG gathering as “a huge success.”</p>
<p>“The PF [Providers Forum] was particularly notable in that we reached a common understanding on the general concept of compatibility and interoperability in a multilateral setting,” Hodgkins told Inside GNSS.</p>
<p>Initial members of the forum and their current and future systems include: China, Compass/Beidou Navigation Satellite System (CNSS); the European Union, Galileo and the European Geostationary Navigation Overlay Service (EGNOS); India, the GPS Aided Geo Augmented Navigation (GAGAN) system and Indian Regional Navigation Satellite System (IRNSS); Japan, the Quasi-Zenith Satellite System (QZSS) and the MTSAT Satellite-based Augmentation System (MSAS); Russian Federation, GLONASS and Wide-area SDCM (System of Differential Corrections and Monitoring); United States, GPS and the Wide Area Augmentation System (WAAS).
</p>
<p>
As noted in a report from the session, “The forum is not a policy-making body, but provides a means to promote discussion among system providers on key technical issues and operational concepts.” Nonetheless, it represents a comprehensive membership and focus on GNSS affairs that has not previously existed.
</p>
<p>
<strong>Baseline Principles</strong><br />
In the course of their discussions, the Providers Forum participants agreed on the following points:
</p>
<p>
• Transparency in the provision of open services is desirable, and requires the open publication and dissemination of signal and system characteristics, in due time, to allow manufacturers to design and develop GNSS receivers on a non-discriminatory basis.<br />
• Discussions should emphasize cooperation regarding GNSS infrastructure (space and ground control/monitoring segments).<br />
• System providers should strive to monitor the performance of their open signals and provide timely updates to users regarding critical performance characteristics such as timing accuracy, positioning accuracy and service availability.<br />
• The protection of RNSS [radionavigation satellite service] spectrum is vital to GNSS service provision. Therefore, adequate spectrum protection through domestic and international regulation should be pursued.<br />
• Physical separation of operational satellite constellations and end-of-life disposal orbits should also be examined.
</p>
<p>
<strong>Compatible, Interoperable</strong><br />
On the key issues of GNSS system compatibility and interoperability, the forum established the following definitions and principles:
</p>
<p>
Compatibility refers to the ability of space-based positioning, navigation, and timing services to be used separately or together without interfering with each individual service or signal.
</p>
<p>
• Radiofrequency compatibility should involve thorough consideration of detailed technical factors, including effects on receiver noise floor and cross-correlation between interfering and desired signals.
</p>
<p>
• Compatibility should also involve spectral separation between each system’s authorized service signals and other systems’ signals.<br />
• Any additional solutions to improve compatibility are encouraged
</p>
<p>
Interoperability refers to the ability of open global and regional satellite navigation and timing services to be used together to provide better capabilities at the user level than would be achieved by relying solely on one service or signal.<br />
• Ideal interoperability allows navigation with signals from at least four different systems with no additional receiver cost or complexity.<br />
• Common center frequencies are essential to interoperability, and commonality of other signal characteristics is desirable.<br />
• Geodetic reference frames and system time standards should also be considered.
</p>
<p>
The Indian Space Research Organization hosted the full ICG meeting September 4-7 and cochaired the Providers Forum with the United States.
</p>
<p>
Forum participants agreed to meet again, no later than the next meeting of the ICG, in Pasadena, California, Dec 8-12, 2008. They may also meet on the margins of the next session of the Scientific &amp; Technical Subcommittee of the United Nations Committee on the Peaceful Uses of Outer Space in February 2008.
</p>
<p>
The UN Office for Outer Space Affairs, as the Secretariat for the ICG, will continue to act as the focal point for Providers Forum meeting preparations. The chair of the Providers Forum will rotate among the members each year.</p>
<p>The post <a href="https://insidegnss.com/icg-sets-up-new-providers-forum-to-pursue-compatibility-among-gnss-systems-augmentation-systems/">ICG  sets up new Providers Forum to pursue compatibility among  GNSS systems, augmentation systems</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>It’s MBOC for common Galileo-GPS civil signal</title>
		<link>https://insidegnss.com/its-mboc-for-common-galileo-gps-civil-signal/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Sun, 09 Sep 2007 23:28:50 +0000</pubDate>
				<category><![CDATA[200709 September/October 2007]]></category>
		<category><![CDATA[Aerospace and Defense]]></category>
		<category><![CDATA[Galileo]]></category>
		<category><![CDATA[GIOVE-B]]></category>
		<category><![CDATA[GPS]]></category>
		<category><![CDATA[Matthias Ruete]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[Reno Harnish]]></category>
		<category><![CDATA[satellites/space segment]]></category>
		<category><![CDATA[signal]]></category>
		<category><![CDATA[system infrastructure/technology]]></category>
		<category><![CDATA[system interoperability]]></category>
		<guid isPermaLink="false">http://insidegnss.com/news/its-mboc-for-common-galileo-gps-civil-signal/</guid>

					<description><![CDATA[<p>The United States and the European Union (EU) have agreed to use the multiplexed binary offset carrier (MBOC) for a common GPS-Galileo signal...</p>
<p>The post <a href="https://insidegnss.com/its-mboc-for-common-galileo-gps-civil-signal/">It’s MBOC for common Galileo-GPS civil signal</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 United States and the European Union (EU) have agreed to use the multiplexed binary offset carrier (MBOC) for a common GPS-Galileo signal for civilian use. In the future, this will enable combined GNSS receivers to track the GPS and Galileo signals with higher accuracy, even in challenging environments that include multipath, noise, and interference.
</p>
<p>
These signals will be implemented on the Galileo Open Service and the GPS IIIA new L1 civil signal known as L1C.
</p>
<p><span id="more-23682"></span></p>
<p>
The United States and the European Union (EU) have agreed to use the multiplexed binary offset carrier (MBOC) for a common GPS-Galileo signal for civilian use. In the future, this will enable combined GNSS receivers to track the GPS and Galileo signals with higher accuracy, even in challenging environments that include multipath, noise, and interference.
</p>
<p>
These signals will be implemented on the Galileo Open Service and the GPS IIIA new L1 civil signal known as L1C.
</p>
<p>
MBOC will appear first on the Galileo L1F signal transmitted by Galileo In-Orbit Validation Element (GIOVE) spacecraft, the first of which — GIOVE-A — has been in orbit since its December 27, 2005, launch. A GPS IIIA launch is not currently expected before 2013. The larger GIOVE-B satellite, which more closely matches the fully operational Galileo spacecraft design, is scheduled for launch in the final days of this year.
</p>
<p>
On September 3 the spacecraft — built by a production team led by prime contractor Thales Alenia Space and including Telespazio, EADS Astrium, and ESA — began its journey from the Thales Alenia plant in Rome to the ESA-ESTEC facility in Noordwijk, The Netherlands.
</p>
<p>
GIOVE-B has successfully passed all preliminary tests, including the thermal-vacuum test that duplicates the satellite’s in-orbit environment, and will undergo further tests in The Netherlands before being sent to the Baikonur cosmodrome to start launch preparations.
</p>
<p>
<strong>Building on 2004 Pact</strong><br />
Building on the historic cooperative agreement on GPS and Galileo signed between the two parties in June 2004, a joint working group overcame technical challenges to design interoperable optimized civil signals that will also protect common security interests. Incorporating MBOC into both GPS and Galileo is expected to enhance commercial opportunities for the development of new GNSS products and services.
</p>
<p>
Matthias Ruete, director general of the European Commission’s energy and transport agency responsible for Galileo, said the announcement “underscores Europe’s commitment to interoperability between Galileo and GPS and to managing the Galileo program in an innovative partnership with the United States. The international GNSS community, including the U.S., will have full and transparent access to information on how to access Galileo and GPS services.”
</p>
<p>
U.S. State Department Principal Deputy Assistant Secretary Reno Harnish said, “The U.S.-EU collaboration that produced this innovation and led to its joint adoption reflects the strong working relationships that we have developed on GPS and Galileo. This technical milestone represents the next step in our ongoing commitment to open standards and market-driven innovation that will benefit all users world wide.”
</p>
<p>
The cooperative agreement reflects a marked turnaround in U.S. attitudes toward Galileo. In the early years of the George W. Bush administration, numerous attempts were made to forestall implementation of what was then seen as a rival to GPS.
</p>
<p>
<strong>Related article</strong>:
</p>
<p>
Inside GNSS Sept-Oct 2007, page 43: &quot;The MBOC Modulation,&quot; by members of the Galileo Signal Task Force</p>
<p>The post <a href="https://insidegnss.com/its-mboc-for-common-galileo-gps-civil-signal/">It’s MBOC for common Galileo-GPS civil signal</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>Proton launch failure raises questions about timeline for completing GLONASS constellation</title>
		<link>https://insidegnss.com/proton-launch-failure-raises-questions-about-timeline-for-completing-glonass-constellation/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Sun, 09 Sep 2007 22:46:43 +0000</pubDate>
				<category><![CDATA[200709 September/October 2007]]></category>
		<category><![CDATA[Earth Parameters 1990]]></category>
		<category><![CDATA[GLONASS]]></category>
		<category><![CDATA[GLONASS designer Yuri Urlichich]]></category>
		<category><![CDATA[GLONASS-M]]></category>
		<category><![CDATA[International Terrestrial Reference Frame]]></category>
		<category><![CDATA[Proton-M]]></category>
		<category><![CDATA[satellites/space segment]]></category>
		<category><![CDATA[system infrastructure/technology]]></category>
		<guid isPermaLink="false">http://insidegnss.com/news/proton-launch-failure-raises-questions-about-timeline-for-completing-glonass-constellation/</guid>

					<description><![CDATA[<p>The September 6 crash of a Russian Proton-M rocket carrying a Japanese telecommunications satellite (JCSAT 11) has injected an element of uncertainty into...</p>
<p>The post <a href="https://insidegnss.com/proton-launch-failure-raises-questions-about-timeline-for-completing-glonass-constellation/">Proton launch failure raises questions about timeline for completing GLONASS constellation</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 September 6 crash of a Russian Proton-M rocket carrying a Japanese telecommunications satellite (JCSAT 11) has injected an element of uncertainty into plans for completing the GLONASS constellation.
</p>
<p>
Russia’s Baikonur cosmodrome automatically suspended all Proton rocket flights, pending an investigation, after the failure of the rocket, which crashed in the steppes of Kazakhstan just over two minutes after lift-off. Russia rents the space facility from Kazakhstan, a former republic in the USSR.
</p>
<p><span id="more-23681"></span></p>
<p>
The September 6 crash of a Russian Proton-M rocket carrying a Japanese telecommunications satellite (JCSAT 11) has injected an element of uncertainty into plans for completing the GLONASS constellation.
</p>
<p>
Russia’s Baikonur cosmodrome automatically suspended all Proton rocket flights, pending an investigation, after the failure of the rocket, which crashed in the steppes of Kazakhstan just over two minutes after lift-off. Russia rents the space facility from Kazakhstan, a former republic in the USSR.
</p>
<p>
Just two weeks earlier, the Russian Federal Space Agency (Roskosmos) had announced that the next triple GLONASS satellite launches would occur on October 25 and December 25, 2007. The Proton-M, the latest in a line of successful heavy Russian rockets, is used for the GLONASS-M launches. Europe&#8217;s Galileo program will use the Russian Soyuz launcher for its early missions, which also take flight from the Baikonur site.
</p>
<p>
Interfax news agency quoted officials at the Russian space technology manufacturer Khrunichev as saying that the failed launch may delay “commercial launches of foreign satellites” planned in November and December. Satellite operator SES Global, for instance, announced that the company will delay two planned satellite launches — SIRIUS 4 in October and AMERICOM 14 in December — pending the results of the official inquiry into the Proton launch failure.
</p>
<p>
The crash and the harsh Kazakh governmental criticism that ensued may also reinforce Russia’s plans to move GLONASS satellites onto a new rocket, the Soyuz-2, and launch these from the Plesetsk space facility in Russia instead of the Baikonur space center.
</p>
<p>
In comments at a press conference in April, Lt. General Alexander Kvasnikov, deputy commander of the Russian Space Forces, said, “We are planning to gradually transfer all launches of GLONASS satellites from Baikonur to the Plesetsk space center to ensure Russia’s independence in launching its own spacecraft.”
</p>
<p>
<strong>A Temporary Setback</strong><br />
The events in Kazakhstan may prove a momentary distraction from a GLONASS program that has been gathering momentum since the Russian government’s August 2001 decision to rebuild and modernize its GNSS system.
</p>
<p>
The GLONASS constellation currently has 12 operational satellites (four temporarily switched off as of September 8) and an additional modernized spacecraft (GLONASS-M) denoted as being in the “commissioning phase.” The latter satellite is one of three launched last December 25 that the Russian Space Forces have had trouble bringing on line.
</p>
<p>
Successful launches of the six additional GLONASS-M satellites would bring the constellation to initial operational capability (IOC) of 18 orbiting spacecraft and meet a program goal set in 2005. The current schedule calls for a fully operational capability (FOC) by the end of 2009.
</p>
<p>
Earlier this year, a decree by President Vladimir Putin ensured continuation of the GLONASS program through 2020. A proposed requirements update for the next 15 years was expected to be submitted in September, as well as a signal modernization plan and future GLONASS mission definition through 2040.
</p>
<p>
On August 31, the Roskosmos Information Analytical Center of Positioning, Navigation, and Time (IAC PNT) announced that an improved version of the national geocentric coordinate system “Earth Parameters 1990” (PZ-90.02) would be applied to the GLONASS system beginning September 20 in accordance with a Russian Federation governmental degree issued in June this year.
</p>
<p>
“On switching to the International Terrestrial Reference Frame ITRF2000, PZ-90.02 transformation parameters will contain only origin shift [from ITRF2000] along X, Y, Z by -36 cm, +8 cm, +18 cm respectively,” according to the IAC, adding that update sheets to the GLONASS Interface Control Document (version 5.0) would be published by September 10.
</p>
<p>
The GLONASS geodetic reference system will be “permanently improved in the direction of ITRF,” according to Russian officials, with the goal of coming within a few centimeters of the ITRF. This coordination of reference frames is expected to help reduce the inter-system errors in receivers using satellite signals from multiple GNSS systems.
</p>
<p>
Last April, the IAC PNT, which had been designated in 2006 as the GLONASS Information Center for the civil community, became an independent center within Roskosmos’s Central Research Institute for Machine Building (TsNIIMASH). Its role is to provide scientific and intellectual support for Roscosmos in PNT strategy development with respect to GLONASS.
</p>
<p>
Meanwhile, earlier this year Yuri Urlichich, director general of the Russian Institute of Space Device Engineering, was named chief designer for GLONASS.
</p>
<p>
<strong>Resources:</strong><br />
Roscosmos<br />
www.roscosmos.ru/index.asp?Lang=ENG<br />
GLONASS Information Analytical Center http://www.glonass-ianc.rsa.ru/pls/htmldb/f?p=202:1:17421293520707003964::NO</p>
<p>The post <a href="https://insidegnss.com/proton-launch-failure-raises-questions-about-timeline-for-completing-glonass-constellation/">Proton launch failure raises questions about timeline for completing GLONASS constellation</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>
