An Introduction to NEC CCIS - NATO

NATO UNCLA SSI F IED

NATO UNCLA SSI F IED

An Introduction to NEC CCIS Northern European Command – Command and Control Information System

- a NATO AIR C2 System Version 1.6, NEC CCIS System Support Centre, 03 September 2021

An Introduction to NEC CCIS version 1.6, 03 Sep 2021

N A T O U N C L A S S I F I E D

page 2

Foreword This document, formerly known as “NEC CCIS in a NutShell”, provides a general introduction to NEC CCIS, including governance, operational functionality, system architecture, geographical distribution, and involved stakeholders.

General Introduction NEC CCIS is a NATO owned Air C2 system used by both nations and NATO HQs and units. It is governed through a Memorandum of Understanding (MOU) currently signed by SHAPE, Norway, NATO Airborne Early Warning & Control Force (NAEW&C F) and NATO Alliance Ground Surveillance (NAGSF) and is funded through a cost-share agreement between these parties. NEC CCIS provides a wide spectrum of Air Command and Control (Air C2) operational functionality used for planning, tasking, execution and reporting of air operations. From the Combined Air Operations Centre (CAOC) or national equivalent, Control and Reporting Centres (CRCs) to the Wing Operation Centre (WOC), Squadron Operation Centre (SQOC) and Surface Based Air Defence (SBAD) level, NEC CCIS is recognised for its comprehensive operational functionality and also comprises of logistics support and other specialized tools.

Fig 1 NEC CCIS in NATINAMDS1

NEC CCIS has served NATO and NEC CCIS member nations for almost three decades by adapting to constantly shifting operational needs. It supports air operations at more than 30 sites, HQs, CRCs and air bases including NAEW&CF Geilenkirchen (DEU), NAGSF Sigonella (ITA), Estonia, Iceland, Lithuania and Norway. During operations and exercises, NEC CCIS can be deployed to forward operating locations using NEC CCIS deployable kits, supporting for instance forward presence and

1 NATO Integrated Air and Missile Defence System



page 3

Quick Reaction Alert (QRA) missions. Interoperability with the NATO Air C2 Structure is taken care of by the NEC CCIS – ICC Interface (NISI) and the NEC CCIS – ACCS interface. NAEW&CF in Geilenkirchen uses NEC CCIS to provide message handling, scheduling, mission planning and current ops functionality to the E-3A Component and the E-3D in Waddington (GBR). NAGSF uses NEC CCIS to cover much the same operational needs as NAEW&CF.

Fig 2 NEC CCIS Footprint

Governance

NEC CCIS System Support Centre System software maintenance, software development and system administration support are provided by the NEC CCIS System Support Centre (SSC) located at Kolsås, Norway. The software support is compliant with NATO and national operational and technical requirements. The SSC is also providing support to NATO and national units during live operations, exercises and trials, including problem-solving and support to local NEC CCIS System Administrators and operators.

NEC CCIS hardware procurement and maintenance is the responsibility of the respective site/nation, however, the SSC provides hardware recommendations on request.



page 4

Fig 3 Location NEC CCIS System Support Centre (SSC)

The SSC Commander reports to Assistant Chief of Staff Strategic Development of Forces at Supreme Headquarters Allied Powers Europe (SHAPE) in Mons, Belgium. The current SSC Peacetime Establishment (PE) manning consists of 19 NATO civilian and military staff, plus a few Nationally Assigned Posts (NAP).

Fig 4 Organisation Chart

The NEC CCIS Board The SSC is governed by the NEC CCIS Board with the MOU signatories as voting members (SHAPE, NAEW&CF, NAGSF, and NOR). The Board has representatives from all NATO units and nations using NEC CCIS. The NEC CCIS Board, chaired by SHAPE , is the tasking authority for the SSC, managed through the Programme of Work (POW) approved by the semi-annual Board meetings.



page 5

Operational C2 Functionality

NEC CCIS’s functionality covers critical non-real time Air C2 functions such as planning, tasking, reporting, and execution. The operational functionality in NEC CCIS continues to evolve. Currently, it contains more than 400 totes2 to support the total scope of NEC CCIS C2 functionality. The operational requirements are staffed through the NEC CCIS User Group (NUG) consisting of both operational and technical members from all user sites.

NEC CCIS supports both live operations and synthetic exercises – simultaneously – and the system is currently configured to support up to 100 simultaneous operations. NEC CCIS is interoperable with NATO simulation tools like Integrated Training Capability (ITC) over NISI to ICC, Joint Theater Level Simulation (JTLS) and Integrated Simulation Package (ISP).

When the built-in maps are used in conjunction with the input from external systems, the user can build a Common Operational Picture (COP). The NATO Joint Secure Tactical Chat (JChat) can also run on the NEC CCIS platform and provides an Extensible Messaging and Presence Protocol (XMPP)-based chat system.

The NEC CCIS C2 functionality includes:

Planning, Tasking and Reporting • (C)AOC Module

o Master Air Operations Plan (MAOP) type tools supporting the production or handling of Air Tasking Orders (ATO)

o Air Defence planning tools o Air Space Management planning tools supporting the production or handling of

Airspace Control Orders (ACO) • Entity Specific Modules (Planning & Reporting, Logistics, Logbooks, Force Protection, Intel,

Electronic Warfare) o AEW Module (Mission & Air Crew Planning) o Current Ops Module (WOC) o Fighter Squadron Module (SQOC) o Helicopter Module (SQOC) o Multi engine Module (SQOC) o CRC Module o SBAD Module

• Targeting (JTS and PTL for NEC CCIS)

Execution of Air Operations • Mission Monitor • Flight Plan • Air Surveillance and Control System (ASACS) / Control and Reporting Centre (CRC) • Tactical Battle Management Functions (TBMF)

2 Tote – Text or Tabular Entry, much like an electronic information board or a web page



page 6

• Emission Control (EMCON) • NATO Crises and Response System (NCRS) • Air Raid Warning (ARW) • Rules of Engagement (ROE) • Chemical, Biological, Radiological and Nuclear (CBRN) • ALERT management • Shared Early Warning distribution and display (SEW) • Force Protection • Intelligence • Tactical Data Link (TDL) – Link-1/L-11/L-16 • Land (Own Forces and TIC reports) • Maritime (Recognised Maritime Picture (RMP) from MCCIS, NAVC2) • Logistics • Electronic logbooks including management of events and info flow

Generic Modules

Mission Planning The ATO is always available for all users at all levels during creation. When an ATO is released, all missions, with data, will automatically be published to the different views for subordinate units to fit their needs. For a WOC, the missions will be displayed in the Mission Monitor. For a squadron, the ATO will be broken down to the level of individual aircraft in missions tasked to that specific squadron. The squadron will insert additional data that will be available at all levels.

Fig 5 MAOP



page 7

Peace-time Daily Training If a squadron needs to conduct missions outside an ATO, they can insert their own missions. These missions will automatically be shared (via database replication) and displayed at higher echelon, in the same way as standard ATO missions. Operators can insert requests for training activities along with requests for airspace and control unit for their training missions. The squadron can send a request for the next day to the CAOC/, the CAOC/NAOC can accept/reject the request. If accepted, the data goes directly into the ATO planning tool and the planner can add Identification Friend or Foe (IFF) codes (incl Mode S and 5), callsign, radio frequencies, controlling agency, etc. This makes it possible to coordinate activities at all levels, resulting in an efficient use of airpower resources, and promotes situational awareness.

Fig 6 Sqn ATO MSN Request

Mission Monitor When a mission is executed, the WOC or the SQOC enters the take-off time. This take-off time will automatically be replicated to all NEC CCIS sites and instantly available in totes at the WOC/SQOC and the CRC, enabling them to control the mission. For the logistics totes, the aircraft will have a status of “airborne” and is locked until the aircraft has landed. When the mission ends, the aircraft status will change and unlock the aircraft. The mission status will automatically change to “terminated” at all levels when the landing time is inserted.

Fig 7 Misson Monitor



page 8

Targeting The targeting module can import target data from NATO’s JTS3 and the CAOC Prioritized Target List (PTL) in ICC via NISI. The data is presented in different views (target data/details) and are editable by the user. Target data for different campaigns or exercises are stored in a structured form.

Fig 8 Weaponeering and Bomb Creator

Event Log (Logbook) Several Event Logs are available in the system and can be used at all levels. With this functionality, every position/cell at a NEC CCIS site can record events, and at the same time give info or action orders to other positions/cells. The cells can acknowledge each event, performing the C2 within the unit.

Fig 9 Event Log

3 Joint Targeting System (JTS) is NATO's designated targeting tool for developing target folders, managing target lists, and maintaining a legal record of target development and target operations. It is a joint tool with mapping and web-service capabilities.



page 9

Messaging NEC CCIS can be integrated with Military Message Handling Systems (MMHS) such as Thales XOmail. NEC CCIS can also support messaging via the Simplified Mail Transfer Protocol (SMTP), which allows for integration with Microsoft Exchange and Outlook. NEC CCIS is a member of the Bi-SC Active Directory Forest and all NEC CCIS users have proper NATO e-mail addresses to be used on the NATO Secret WAN.

NEC CCIS Database Maintenance Data handling is mainly done through the NEC CCIS Tote system. Extensive data packages will normally be inserted as part of upgrades to the system. If classification settings or other issues make this difficult, database packages can remotely be imported from the SSC or be sent to the system administrator as easy-to-use scripts for local import at the site. Site backup and recovery is based on scripts and can easily be done by the system administrators. Due to the NEC CCIS replication mechanism, a site can even import an external backup from another site if necessary. This will allow a failed local database to become operational and in-sync with the rest of the NEC CCIS community.

NEC CCIS Database Maintenance covers:

• Data Maintenance • NEC CCIS static data • User accounts • System admin and monitoring • Opus to Opus Replication (O2R) management • Geographic information system (GIS)

Further details are provided under the section “The NEC CCIS System”.

Entity Specific Modules The entity-specific modules cover functionality custom made to suit the platform and types of planning, reporting and execution that are required to perform tasks at the specific WOC/SQOC level entities. Typical totes cover functions like flying boards, mission and maintenance scheduling, logistic holdings, force protection boards, intelligence and logbooks.

Fighter Squadron Flying Board To support the planning and tasking cycle at the Squadron level, a Flying Board has been developed. The Flying Board contains all the necessary information following a Fighter Aircraft (AC) from workshop, line, armament, step-desk, airborne and landing. The Flying Board is also monitored by the CAOC/NAOC and the controlling CRC. The Flying Board is already available as a web tote using a web client browser.



page 10

Fig 10 Fighter Sqn Flying Board

The Flying Board is used at the SQOC for detailed planning of all flying activities. Data is automatically updated from the ATO - including ATO txt, com Freq, callsign, mission notes etc. The planner assigns aircraft (a/c) and pilots to the actual mission. An AC Configuration Tote is used by the ground crew and weapon crew to report a/c status pr tail number, changes to the a/c configuration, parking spot etc. Data from the AC Configuration Tote updates the Flying Board automatically. Take-off and landing times are either transferred to the Flying Board from Mission Monitor based on WOC input - or entered directly into the Flying Board by the SQOC. Airbase and runway status, and local weather info will also be displayed in the Flying Board.

Fig 11 Flying Board - Timeline



page 11

NATO Airborne Early Warning (NAEW) The NAEW module is custom made to replace functionality previously provided by the decommissioned NAEW&CF Mission Support System (MSS). The NAEW module contains functionality to support NAEW&C message handling, NAEW&C scheduling, NAEW&C mission planning and NAEW&C current ops (WOC/SQOC). The NAEW totes can be used by the CAOCs and AIRCOM for Air Ops monitoring, planning and tasking.

Fig 12 AEW Missions, Flight Schedule

Fig 13 AEW Missions, Timeline



page 12

Fig 14 Message Processing

SBAD The SBAD module has extensive functionality fulfilling very specific requirements to support mobility for SBAD units and C2 coordination with higher echelons. (…)

Fig 15 GBAD Alert Status



page 13

Fig 16 GBAD Logistics



page 14

Logistics Tool With the logistics tool provided in NEC CCIS, a unit can record the status of its equipment (eg. Air Frames) and also generate reports to be sent to higher units based on the logistics classes I-V. In addition, infrastructure and manning status/planning is supported.

Fig 17 Part of Log Tool



page 15

Integrated Scheduling Tool The integrated scheduling support in NEC CCIS consists of a selection of totes which add crew management to the air mission scheduling process. The regular short term and long term air task planning process can then be integrated with personnel management, for example, to assign aircrews to the missions. To effectively support this, the integrated scheduling feature also includes support for personnel status i.e. training management, air currency logging/monitoring and absence management (leave, sickness, deployments). The inclusion of support for personnel functions allows for creating a user-centric dashboard where aircrew can monitor future tasks and plans.

Fig 18 Squadron calendar



page 16

Fig 19 Squadron consolidated schedule

Fig 20 Personal dashboard



page 17

The NEC CCIS System

System Architecture The NEC CCIS software suite implements a standard three-tier architecture:

• The database backend (Oracle RDBMS on a Solaris server). • The NEC CCIS application server (running on the same server as the database backend). • The NEC CCIS client (a desktop application installed on the users’ Windows PCs, or a web

client running in a standard web-browser).

Seen from an operational user point of view, the desktop client installation consists of four components: The Tote Browser (for access to text/table-based data), the Geographical Information System (GIS), currently using Teleplan MARIA, the Military Message Handling client (either XOmail Client or Outlook), and the NEC CCIS operational and technical documentation, accessible in HTML and PDF format in a web browser (Internet Explorer).

The NEC CCIS functionality is also to some extent already available in a web browser, which allows for access to the NEC CCIS totes and GIS without having a local installation other than the standard web browser. The web GIS is based on the Luciad RIA software package.

The transition from using a desktop application to using web browser is ongoing, both methods (desktop and web) are currently supported.

A traditional NEC CCIS site consists of a NEC CCIS Solaris server (for the application server and the database backend), the users’ Windows workstations, and the Windows servers required to implement the site as a first-class citizen of the NATO Active Directory (AD) implementation (NS WAN). Most NEC CCIS sites on NS WAN are contained in the necccis.ais.nato.int domain.

Fig 21 NEC CCIS site architecture



page 18

A NEC CCIS site can be implemented on a fully virtualised infrastructure, with traditional server virtualisation (all Windows server and the NEC CCIS Solaris servers on x86), and also desktop virtualisation for the Windows workstations; all running on top of a few physical servers at each site. The virtual desktops are displayed to the operational users through zero clients, providing a high performance, low maintenance solution with clear security benefits, as no data is stored locally, the zero clients are unclassified as soon as power is turned off.

Data Replication Each operational site has a database storing all operational data. Databases are kept synchronised across the geographically dispersed sites through sophisticated data replication mechanisms (O2R). This ensures that information inserted at one site will automatically be available at all other NEC CCIS sites as defined.

Fig 22 NEC CCIS database replication

NEC CCIS also supports Live Updates which will automatically update the operator screens when data changes in the database. New or modified data will be highlighted in the tote. Through the data replication and Live Update mechanisms, the amalgamation between NEC CCIS sites creates one tightly integrated system. The system allows the operator to view data as text (totes), as military messages, or as graphical objects on a map (graphic displays) and information can be updated or altered directly on the totes or graphic displays.

In case of a lack of connectivity between sites, a site can operate autonomously. Then, once connectivity is re-established, the operational data will be automatically synchronised with the other NEC CCIS sites. The same principle applies to the client application running on a site: If the connection to the local server is lost, the operator can continue his work in offline mode and synchronise any changes with the server once the connectivity has been re-established. This makes NEC CCIS a robust and resilient system well suited for use in a military operational environment.

Nation Bsites

CAOC C

CAOC A

CAOC B

Nation Asites

Nation Csites



page 19

Interoperability Interoperability is a critical capability to enable modern Air Power. Therefore, the SSC uses a lot of resources on system interfaces. Currently, NEC CCIS has external interfaces towards:

• Air Command and Control System (ACCS) – AdatP-3 – XOmail/X400 – Link-11B • Multi-AEGIS Site Emulator (MASE) – Link-1 • Maritime Command and Control System (MCCIS) (OTH/Gold) • NATO SEW (Shared Early Warning) • Flight plans - AIMS (ADEXP subset) • National meteorological services (METEO) • Joint Mission Planning System (JMPS) for F-16/F-35 - USMTF • Joint Theatre Level Simulation (JTLS) • NIRIS RAP (Link-16, link-11, Joint-Range Extension (JRE)) • Military Message Handling System (MMHS) • NATO-wide Integrated Command and Control Software for Air Operations (ICC) – NISI (NEC

CCIS - ICC System Interface) NISI is a database-to-database interface maintained by SSC for exchanging operational data in predefined functional areas between NEC CCIS and ICC. NISI provides seamless and automatic data transfer between the two systems. The functional areas covered include, but are not limited to Friendly Order Of Battle, Airspace Control Order (ACO), Air Tasking Order (ATO), ASACS functions, statuses, and reports.

Maintaining interoperability with ACCS is an important task to the SSC, ensuring a seamless AirC2 structure within the NATO Command Structure and NATO nations, also known as NATO Integrated Air and Missile Defence System (NATINAMDS). Originally, ACCS was supposed to replace other C2 systems including NEC CCIS, but due to reductions in functionality of ACCS, especially within the area of WOC/SQOC, NEC CCIS will continue to be used after the fielding of ACCS. The interfaces to ACCS – AdatP3 and Link-11B – are under continuous development, following the evolvement of ACCS.

Security NEC CCIS has a formal security accreditation at the NATO SECRET level in the System High mode of operation, and is subject to a full re-accreditation every 3 years. Currently, two of the four annual NEC CCIS releases are submitted for NATO’s Approved Fielded Products List (AFPL) testing regime. To ensure NEC CCIS remains in compliance with the most current NATO and National security requirements, the NEC CCIS system security is controlled by a dedicated NEC CCIS Security Accreditation Board (NAB) with voting members from all NATO and national security accreditation authorities having one or more NEC CCIS sites within their area of responsibility (AOR).

Software Management Currently, the SSC has a quarterly release cycle for the NEC CCIS C2 software – a release rate that makes NEC CCIS very adaptable to changing operational requirements.

The SSC incorporates agile/scrum principles for its software development and takes advantage of the in-house developed high-level Santos toolkit, to maintain and develop metadata in an Integrated System Dictionary (ISD). These tools and the ISD allow for quick changes, as well as the development



page 20

of new functionality. The change management system allows for any software related issue to be reported by any user in the NEC CCIS community through the NEC CCIS web portal on NS WAN. All issues are evaluated frequently, and the software problems and minor software changes are implemented, tested, and released without any unnecessary delay. The typical lead time for a software fix is 3-5 months from the moment a problem is identified until it is corrected in the software and released to the users. Critical fixes can be implemented in the ISD and distributed to sites within hours.

Support The SSC provides back-end software support to users and site system administrators during installation, upgrades, exercises, operations, and daily business. The SSC also provides hardware support to sites as needed, especially covering the set-up and use of the virtualisation environment (VMWare) used by many sites. Close cooperation with users and administrators means that the support organisation is ready and able to assist when called upon.

How to acquire NEC CCIS? Who can use NEC CCIS? NEC CCIS is property of NATO, thus making it NATO off-the-shelf (NOTS) software available to all NATO units and NATO member nations.

How to request access to the NEC CCIS software? For NATO units, an official request needs to be submitted to SHAPE. For Nations interested in using NEC CCIS, send an official request to the NEC CCIS Board Chairman ([email protected]).

Who can request support from NEC CCIS SSC? Existing members of the NEC CCIS MOU who are contributing to the NEC CCIS O&M budget, and entities covered by SHAPE are eligible to receive support from the NEC CCIS SSC.

How to become a member of the NEC CCIS MOU? Your NATO unit/nation must submit a written request to the NEC CCIS Board chairman ([email protected]). That request would then be presented to the Board for approval of membership. If approved, an MOU negotiation process, to agree terms and SSC O&M budget cost share, will be performed.

mailto:[email protected]




page 21

Contact Info – NEC CCIS SSC Surface Mail: NEC CCIS SSC

P.O. Box 25 N-1333 Kolsaas Norway

Phone: (Civ) +47 6786 5500 (NCN) 920 47 0515 5500

Fax: +47 6786 5501

E-mail unclassified: [email protected]

E-mail NS-WAN: NEC CCIS SSC POST ([email protected])

List of acronyms • AC: Aircraft • ACCS: Air Command and Control System • ACO: Airspace Coordination Order • AD: Active Directory • ADEXP: ATS Data Exchange Presentation • AEW: Airborne Early Warning • AFPL: Approved Fielded Product List • AIMS: Aircraft Information Management System • AIRCOM: Air Command • AOC: Air Operations Centre • AOR: Area of Responsibility • ARW: Air Raid Warning • ASACS: Air Surveilland and Control System • ATO: Air Tasking Order • ATS: Air Traffic Services • CAOC: Combined Air Operation Centre • CBRN: Chemical, Biological, Radiological, Nuclear • COP: Common Operational Picture • COTS: Commercial on the Shelf • CRC: Control and Reporting Centre • DEU: Germany • EMCON: Emission Control • EOC: Early Operational Capability • GBAD: Ground Based Air Defence • GBR: Great Britain





page 22

• GIS: Graphical Information System • HQ: Headquarters • HTML: Hypertext Markup Language • ICC: Integrated Command and Control • IFF: Identification Friend or Foe • ISD: Integrated System Dictionary • ISP: Integrated Simulation Package • IST: Integrated Scheduling Tool • ITC: Integrated Training Capability • JMPS: Joint Mission Planning System • JRE: Joint-Range Extension • JTLS: Joint Theater-Level Simulation • JTS: Joint Targeting System • MAOP: Master Air Operations Plan • MASE: Multi-site AEGIS Site Emulator • MCCIS: Maritime Command and Control Information System • METEO: Meteorological Office • MMHS: Military Message Handling System • MOA: Memorandum of Agrement • MOU: Memorandum of Understanding • MSN: Mission • MSS: Mission Support System • NAB: NEC CCIS Accreditation Board • NAEW&CF: NATO Airborne Early Warning & Control Force • NAF: NATO Architecture Framework • NAGSF: NATO Alliance Ground Surveillance Force • NAOC: National Air Operations Center • NATINAMDS: NATO Integrated Air and Missile Defence System • NATO: North Atlantic Treaty Organization • NCN: NATO Core Network • NCRS: NATO Crisis Response System • NCS: NATO Command Structure • NEC CCIS: Northern European Command – Command and Control Information System. • NIRIS: Networked Interoperable Real-time Information Services • NISI: NEC CCIS ICC System Interface • NOR: Norway • NOTS: NATO Off The Shelf • NS: NATO Secret • NUG: NEC CCIS User Group • O&M: Operations and Maintenance • OS: Operating System • OTH: Over the Horizon



page 23

• PC: Personal Computer • PDF: Portable Document Format • POW: Programme of Work • PTL: Prioritized Target List • RAP: Recognized Air Picture • RDBMS: Relational Datbase Managemt System • RIA: Rich Internet Application • RMP: Recognized Maritime Picture • ROE: Rules of Engagement • SBAD: Surface Based Air Defence • SC: Strategic Command • SEW: Shared Early Warning • SHAPE: Supreme Headquarters Allied Powers Europe • SMTP: Simplified Mail Transfer Protocol • SQOC: Squadron Operations Centre • SSC: System Support Centre • TBMF: Tactical Battle Management Functions • TDL: Tactical Data Links • TIC: Troops in contact • USMTF: United States Message Text Format • WAN: Wide Area Network • WOC: Wing Operations Centre • XMPP: Extensible Messaging and Presence Protocol

Record of changes

Date Version Reason for change 03 Sep 2021 1.6 General review. Lots of changes and updates. 31 Jan 2019 1.5 Updated to include NAGSF in the intro chapter. Org chart Fig. 4 updated to reflect NCS Adaptation. 10 Oct 2018 1.4 Added info on how to acquire NEC CCIS at end of document. 07 Mar 2018 1.3b Updated front page (new logo)

28 Apr 2017 1.3 Content and structure updates and additions. New illustrations. Broadened scope. Changed title from “NEC CCIS in a NutShell”

07 May 2015 1.2 Content and structure updates 08 Apr 2015 1.1 Re-structured, reviewed and de-classified / released to the public domain. 30 Mar 2015 1.0 Initial version

Documents

An Introduction to NEC CCIS - NATO