9LV

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

9LV is a Naval Combat Management System (CMS) from the Swedish company Saab. The 9LV was established when Philips Teleindustri AB (1975 renamed Philips Elektronikindustrier AB), a subsidiary of Philips of the Netherlands, was selected as the supplier of the torpedo and dual purpose gun fire control system including a radar fire control director for the Royal Swedish Navy Norrköpings-class torpedo boats.[1]

Prior to the Norrköpings-class, Philips provided torpedo fire control to Spica class and Plejad class torpedo boats, as well as to Sjöormen class and Draken-class submarines, and also anti-submarine fire control for the Halland-class destroyers and Visby-class frigate. However, not until the air defence fire control and radar fire control director was introduced, the name 9LV was established; LV is the Swedish abbreviation for "luftvärn", i.e. air defence.[citation needed]

9LV is currently used on several classes of naval combatants, including the Australian Anzac-class frigates, the Swedish Visby-class corvettes, the Canadian Halifax-class frigates[2] and the Australian Canberra-class landing helicopter dock ships.

Name etymology

The heritage of the name 9LV can be traced back to the late 1960s and Philips Teleindustri (Järfälla, SE). Philips gave the number nine to the product from Sweden.[citation needed]

LV is the Swedish abbreviation for Ground Based Air Defence (GBAD), in Swedish "Luftvärn".[citation needed]

Often, a specific ship class 9LV configuration is identified by a three digit number, consisting of one complexity digit and a two digit serial or country code. The first digit is defined by the following table.[citation needed]

System numbers
1 Small system, optronic (EOS) "100" director
2 Small system, radar (Ceros) "200" director
3 Significant system, optronic and radar (100 + 200 = 300) directors
4 Major system (actually "2+2" i.e. double Ceros)(Göteborg, ANZAC, Visby, Naresuan)

Naval Combat Management introduction

A Naval Combat Management System (CMS) is the computer system that connects a naval ship's sensors, weapons, data links, support measures and other equipment to the officers and staff performing the tasks in combat through the cycle of the OODA loop. Typical functions include sensor control, sensor data fusion, threat evaluation, weapons assignment, weapons control etc.[citation needed]

9LV Mk1 (1968–1977)

To meet the requirements of the Royal Swedish Navy replacement of Signaal's M22 system on the Spica class, the 9LV200 system was developed in 1968 by Philips Swedish subsidiary ("Philips Elektronikindustrier AB", PEAB). The contract was awarded PEAB 1969.[3] Also in the late 1960s, the contract for radar and optical fire control systems for the Royal Swedish Navy "Norrköping" class torpedo boats was awarded PEAB.[citation needed]

The solution included was based on analogue computers with a newly developed hydraulically controlled director platform and a frequency agile Ku-band fire control radar, Ceros. The solution also included an X-band track-while-scan target acquisition radar. In the Royal Swedish Navy, the system was denoted "ARTE 722".[4]

Mk1 included a fixed program digital computer [3]

9LV Mk2 (1977–1983)

The patrol boat Jägaren ("The hunter") was built as a test vessel with the Norwegian gun boats "Storm" and "Snögg" as references. Later Bergens Mekaniske Verksteder built another 16 patrol boats based on "Jägaren". The patrol boats were equipped with 9LV Mk2 (Arte 726).[5] The system was called 9LV Mk2 during the period Arte726 A-D.[6]

9LV Mk2.5 (1983–1987)

The 9LV Mk2.5 introduced a new high level language (RTL/2) and also upgrades to the hardware architecture with new processors and busses. The Swedish Navy Arte726E is an example of 9LV Mk2.5.

9LV Mk3 (1987–2005)

Based on the experiences from 9LV MK2.5, a major redesign of 9LV was performed for 9LV Mk3, starting around 1985. It featured a module based architecture called Base System 2000 (Bassystem 2000), as an addition of the commercial OS/9 RTOS. The new programming language Ada was introduced in cooperation with the company Rational.[7] After the acquisition of the Ericsson "H Division" developing a competing Combat Management System (Maril systems) January 1, 1990, several key architectural features were transferred into 9LV Mk3.

Features of 9LV Mk3 included a fully distributed system, based on Ethernet LAN, with small, location independent, applications implemented in Ada. It also featured a "system family" concept, with all ship classes based on a common code base (reference book on reuse) and multi-function consoles, allowing any operator to perform any task from any position.

9LV Mk3E (1998–2008)

Aiming to benefit from the fast development of commercially available hardware, the software base of MK3 was transferred to Intel based processors on cPCI, running MS Windows NT instead of the real-time OS/9 used in MK3.[citation needed]

9LV Mk4 (2008–)

In order to facilitate integration and partnerships, the MK4 was developed towards the Naval Open Architecture. MK4 employs DDS to create modularity and introduces the Java programming language for certain applications. The first deployment of the 9LV MK4 was the Halifax-class frigate where Saab acted as a sub-supplier to Lockheed-Martin Canada.[citation needed].

One important milestone for 9LV Mk4 was the firing on 30 August 2015 of the ESSM missile [8] from HTMS Naresuan during Exercise CARAT 2015, less than three years after the signing of the contract for the missile.[9]

Awards and recognition

<templatestyles src="Template:Blockquote/styles.css" />

Saab wins Project of the Year Award in Australia, 2012: Saab, along with BAE Systems and CEA Technologies, has won the Major Company/DMO Project Team of the Year for the Anti-Ship Missile Defence project which implemented the most advanced model of the Saab 9LV combat management system.

[10]

Company heritage of 9LV development

The history of C2S, the creator of 9LV

  • 1938: Standard Radiofabrik is established
  • 1956: SRT (Standard Radio & Telefon AB) is founded
  • 1964: SRT builds a factory in Veddesta, Järfälla outside Stockholm
  • 1968: Philips Teleindustrier is established; opening ceremony with the Swedish King
  • 1971: Stansaab is created out of the computer part of SRT, (owners are the state, Saab and ITT)
  • 1973: ITT leaves their ownership of Stansaab
  • 1975: Stansaab get a big order regarding AOC in Moskva
  • 1976: Philips Elektronikindustrier (merger with Philips Teleindustrier)
  • 1978: Datasaab created from merger of Stansaab & Datasaab
  • 1981: Ericsson buys Datasaab and keeps Alfaskop while SRA procures radar systems, later to be Ericsson Radio Systems
  • 1982: Ericsson Information Systems (EIS) established
  • 1982: SRA Communications AB is established
  • 1983: Marconi leaves ownership of SRA to Ericsson Radio Systems
  • 1988: Command & control and radar technology becomes Ericsson Radar Electronics (ERE)
  • 1990: Bofors Electronics (BEAB) acquires Philips, Ericssons (ERE) military production
  • 1991: BEAB joins Nobeltech
  • 1993: Nobeltech changes name to Celsiustech
  • 2000: Saab buys Celsiustech; new names are SaabTech Systems and SaabTech Electronics
  • 2003: SaabTech created from Saab Avionics & SaabTech Systems
  • 2005: Saab Systems created
  • 2009: Saab Security and defence solutions

Command and control history within Saab 1966 a work group started (name SESAM) to work on the next generation combat management system. This led to the first drafts on what was later to become NIBS (Näckens InformationsBehandlingsSystem). The group came up with an entirely digital combined combat and fire control solution with two operator positions able to evaluate at least 10 targets. The three operator consoles where of Stansaab type. The order was later given to Stansaab; the software was delivered by Teleplan.

  • 1988: SESUB (Strids- & Eldledning SUBmarin); contract awarded to Datasaab (modern NIBS)
  • 1996: SESUB 940 entire solution awarded to CelsiusTech

References

  1. Lua error in package.lua at line 80: module 'strict' not found..
  2. Lua error in package.lua at line 80: module 'strict' not found..
  3. 3.0 3.1 Friedman 1997, p. 292.
  4. Lua error in package.lua at line 80: module 'strict' not found..
  5. Lua error in package.lua at line 80: module 'strict' not found..
  6. HMS Mode (P154).
  7. Friedman 1997, p. 346.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found..

Bibliography

  • Lua error in package.lua at line 80: module 'strict' not found..
  • Lua error in package.lua at line 80: module 'strict' not found.