The government, national defence, naval priorities and expeditionary requirements have not been well served by explanations for reconsideration of the approved JSS program given the economic importance and operational urgency in replacement of the old fleet supply vessels. These […]
I was the communications officer on HMCS Protecteur when she was deployed to East Timor in 1999. While we did yeoman work supporting forces ashore with fuel, stores and an […]
Having just reviewed Dr. Sloan’s book (McGill-Queen’s University Press, 2005) for Canadian Naval Review, her comments on the JSS are fresh in my mind. Sloan wrote that “rapid deployability is […]
In an industry known for its boom and bust cycles the forecast Canadian new building requirements over the next fifteen years should be signalling the start of another boom cycle […]
During the past few months there has been increasing speculation that the project to upgrade the CP-140 Aurora (the Aurora Incremental Modernization Project or AIMP) would be terminated. The decision […]
The cost factors Ken Hansen outlines demonstrate the ongoing need for sealift. Indeed, with sealift costs being between one-tenth and one-seventieth the cost of airlift, coupled with the fact that […]
Robin Allan refers to the requirement as a “Big Honking Ship”. The term is somewhat overly generous. The projected full load displacement of the JSS is about 28,000 tons, about […]
The Government is presently debating whether to buy two or three of the Joint Support Ships, and how to resolve its bidding dilemma. Both teams, led respectively by SNC-Lavalin Profac […]
This February, David Pugliese reported that a leaked copy of the Canada First Defence Strategy would retire our current AOR in 2010, two years before the JSS was delivered in […]
The report of the arrival of France’s F.N. Tonnerre in Halifax should raise some issues for Canada. Tonnerre is a four-in-one vessel – helicopter carrier, hospital ship, command ship, and […]
The Canadian navy’s sea-lift capacity has been mentioned previously in these quarters, in the context of the rumoured Conservative plan to pay-off the existing Protecteur-class replenishment ships a full two […]
The navy’s plan to replace the existing fleet on a one-for-one basis plus a couple of extra ships over the next 30 or so years is ambitious and very expensive. […]
On February 22, 2008, the Ottawa Citizen published an anonymous letter, entitled “Navy Capabilities Slide While Government Sits Idle”, attributed to a serving Canadian Naval Officer in David Pugliese’s Defence […]
For much of February 2007, a small group of academics that included serving and former naval officers engaged in an electronic debate on the future of Canada’s defence and naval […]
Cookie Consent
At Canadian Naval Review (CNR), we are committed to respecting your privacy. When visiting our website for the first time you can either “Accept all” cookies (including ‘non-essential cookies’) or “Customize” your cookie preferences, which allows you to make individual choices and get details on the cookies we use.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
