WHIR | BLOGS | WEB HOST NEWS | FIND WEB HOSTS | RESELLER HOSTING | MAGAZINE | WHIR TV | NEWSLETTER | rss feeds
web hosting news - daily web host interviews, insight Jobs | Events | Sitemap | Search 
Error Occurred While Processing Request


WEB HOSTING NEWS | BLOGS | INTERVIEWS | EUROPE | EVENTS | WEB HOSTING JOBS

<< DemoWolf Partners with BobCares     SharkSpace Announces Green Tactics >>


Coast Guard to Operate Data Center

May 1, 2008 -- (WEB HOST INDUSTRY REVIEW) -- The United States Coast Guard has signed an agreement with the International Maritime Organization to open a new international data exchange center to track the positions at sea of about 3,000 ships per day, according to a final rule published in the Federal Register.

   
Level 1 PCI DSS Certified Service Provider! DataPipe delivers the best network & support; top tier data centers; New York metro, Silicon Valley, London, Hong Kong, Shanghai. DataPipe - Personal Touch, Global Reach.

The data center, which goes into operation on January 1, 2009, will be run by the Coast Guard for the Long-Range Identification and Tracking system until December 31, 2010. It has not yet been decided as to what will happen to the data center after that date.

The service's identification and tracking applies to ships on international voyages that come within 1,000 nautical miles of US region, which includes passenger ships holding 12 or more people. The Coast Guard says the rule applies to roughly 3,000 vessels a day, in which most of these ships are not US-owned.

The Coast Guard says it anticipates investing about $1 million a year to pay for the ship owners' costs of instantly transmitting the vessels' global positioning data by satellite to the facility, based on each ship transmitting four times a day.

The International Maritime Organization's Maritime Safety Committee will meet on May 7 to consider a proposal to decrease the required number of transmissions to two per day.

"Reducing required transmissions to two per day would reduce the communications cost of transmissions from ship-to-data-center by half," says the Federal Register notice. "The Coast Guard believes this proposal deserves serious consideration as a cost saving vehicle that has little, if any, adverse impact on the maritime domain awareness benefits to be derived from LRIT."

The facility's need for identification and tracking systems, and geospatial positioning systems, including radios, networks, software and storage systems, will open some key contract opportunities to the private sector.

Print this Page       Email this Page        Add to: | del.icio.us | digg


COMMENTS

Be the first one to comment on this article. Click the link below to post your comment.

[POST COMMENT]



The Planet Launches Virtual Racks

Mosso Launches CloudFS Storage

Layered Tech Ready for Integration

Online Services Okay with Partners

Indian Host NetMagic Going Global

Judge Withdraws Wikileaks Ruling

Microsoft Launch a Big Production

More feature interviews and reports
 

Error Occurred While Processing Request

An error occured while Parsing an XML document.

An invalid XML character (Unicode: 0x13) was found in the element content of the document.
 
The error occurred in D:\home\thewhir\html01\templates\art_whnews_Close.cfm: line 72
70 : 	<cfscript>
71 : 	XMLwang = trim(cfhttp.filecontent);
72 : 	XMLwang = XMLParse(XMLwang);
73 : 	</cfscript> 
74 : 

Please try the following:

Browser   CCBot/1.0 (+http://www.commoncrawl.org/bot.html)
Remote Address   38.103.63.17
Referrer  
Date/Time   12-May-08 05:24 AM
Stack Trace
at cfart_whnews_Close2ecfm1364004782.runPage(D:\home\thewhir\html01\templates\art_whnews_Close.cfm:72) at cf050108_Coast_Guard_to_Operate_Data_Center2ecfm975340292.runPage(D:\home\thewhir\html01\marketwatch\050108_Coast_Guard_to_Operate_Data_Center.cfm:1)

coldfusion.xml.XmlProcessException: An error occured while Parsing an XML document.
	at coldfusion.xml.XmlProcessor.parse(XmlProcessor.java:154)
	at coldfusion.runtime.CFPage.XmlParse(CFPage.java:182)
	at cfart_whnews_Close2ecfm1364004782.runPage(D:\home\thewhir\html01\templates\art_whnews_Close.cfm:72)
	at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:152)
	at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:343)
	at coldfusion.runtime.CfJspPage._emptyTag(CfJspPage.java:1908)
	at cf050108_Coast_Guard_to_Operate_Data_Center2ecfm975340292.runPage(D:\home\thewhir\html01\marketwatch\050108_Coast_Guard_to_Operate_Data_Center.cfm:1)
	at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:152)
	at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:343)
	at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65)
	at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:210)
	at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:51)
	at coldfusion.filter.PathFilter.invoke(PathFilter.java:86)
	at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:50)
	at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)
	at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)
	at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
	at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
	at coldfusion.CfmServlet.service(CfmServlet.java:105)
	at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:78)
	at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91)
	at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
	at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:257)
	at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:527)
	at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:204)
	at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:349)
	at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:457)
	at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:295)
	at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)