An Introduction to NEC CCIS

Northern European Command Command and Control Information System

- a NATO AIR C2 System

Version 1.3, NEC CCIS System Support Centre, 28 April 2017
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 Foreword

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 players involved.

The document also fulfils the intent of the NOV-1 1 and NSV-1 2 documents of the NAF 3 for NEC CCIS.

General Introduction
NEC CCIS is a NATO owned Air C2 system governed through a MOU signed by SHAPE, Norway, and
NATO Airborne Early Warning & Control Force (NAEW&C F), and is funded through a cost-share
agreement between these. 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) down 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 for its logistics support tools.

Fig 1 NEC CCIS in NATINAMDS 4

1
High-Level Operational Concept Definition Subview (NOV-1)
2
System Interface Description subview (NSV-1)
3
NATO Architecture Framework v 3.1 (AC/322(SC/1-WG/1)N(2009)0005-ADD2)
4
NATO Integrated Air and Missile Defence System

page 2
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 Governance

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 NATO sites, HQs,
CRCs and air bases including NAEW&C F, Estonia, Iceland, Lithuania and Norway. During operations
and exercises, NEC CCIS can be deployed to forward operating locations using NEC CCIS deployable
kits. Interoperability with the NATO Air C2 Structure is taken care of by the NEC CCIS ICC Interface
(NISI) - operational at CAOC Uedem, CAOC Torrejon and AIRCOM Ramstein, and the NEC CCIS ACCS
interface. NAEW&C F in Geilenkirchen (DEU) 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).

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 Kolsaas, Norway. The software
support is compliant with NATO and national operational and technical requirements. Support to
local NEC CCIS System Administrators including problem solving, software installation, and support to
NATO and national units during live operations, exercises and trials are also provided by the SSC.

page 3
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 Governance

NEC CCIS hardware procurement and maintenance lies with the site/nation, however, the SSC
provides hardware recommendations on request.

Fig 3 Location NEC CCIS System Support Centre (SSC)

The SSC Commander reports directly to ACOS J3 at SHAPE. The SSC manning consists of NATO
civilians, military, and VNCs. The current Peacetime Establishment staffing requirement is 19 posts.

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&C Force and NOR). The Board has representatives from all of the NATO units and nations

page 4
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 Operational C2 Functionality

using NEC CCIS. The NEC CCIS Board, chaired by SHAPE J3 OPI, is the tasking authority for the SSC,
managed through the Programme of Work (POW) approved by the semi-annual Board meetings.

Operational C2 Functionality
NEC CCISs functionality covers critical Air C2 functions like planning, tasking, reporting, and
execution. The operational functionality in NEC CCIS continues to evolve. Currently it contains more
than 400 totes to support the total scope of NEC CCIS C2 functionality. The operational requirements
are staffed through the NEC CCIS User Group (NUG) consisting of members from all user sites.

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

When the built-in maps are used in conjunction with the input from external systems, the user can
build up a Common Operational Picture (COP). The NATO Joint Secure Tactical Chat (JChat) is also
implemented 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 MAOP tools (Air Planning)
o Air Defence tools
o Air Space Management tools
Intel Module
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 (ASAC) / Control and Reporting Centre (CRC)
Tactical Battle Management Functions(TBMF)
Emission Control (EMCON)
page 5
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 Generic Modules

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 log books

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 underlying units to fit
their need. 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 aircrafts in missions tasked to that specific
squadron. The squadron will insert additional data that will be available at all levels.

Fig 5 MAOP

page 6
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 Generic Modules

Peace-time Daily Training

If a squadron wants to conduct missions outside an ATO, they are able to insert their own missions.
These missions will automatically be replicated (via O2R) 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 sends a request for
the next day to the CAOC/NAOC (National Air Operation Centre) 5, the CAOC/NAOC can accept/reject
the request. If accepted, the data goes directly into the ATO planning tool and the planner adds
Identification Friend or Foe (IFF)(incl Mode s and 5), callsign, radio frequencies, controlling agency,
etc. This makes it possible to automatically coordinate activities at all levels, resulting in an efficient
use of airpower resources.

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 be
automatically replicated to all NEC CCIS sites and instantly available in totes at the WOC/SQOC and
the CRC, allowing them to take the mission under control and continue their task. For the logistics
totes, the aircraft will have a status of airborne and it will be locked until the aircraft has landed.
When the mission ends, the aircraft status will change and unlock the aircraft. The mission status will
at all levels automatically change to terminated when the landing time is inserted.

Fig 7 Misson Monitor

5
If the CAOC/NAOC are operating with NEC CCIS or ICC. This function will currently not work towards ACCS.

page 7
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 Generic Modules

Targeting
The targeting module can import target data from NATOs JTS 6 and from CAOC Prioritized Target List
(PTL) in ICC via NISI. The data is presented in different views (TGT 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 orders to
other positions/cells. The cells can acknowledge each event to perform the C2 within the unit.

Fig 9 Event Log

6
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 8
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 Entity Specific Modules

Messaging
NEC CCIS has an integrated military messaging system based on COTS products such as IRIS and XO-
mail. 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 site. Site backup and recovery is based on
scripts, and easily 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
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
USERS accounts
System admin and monitoring
Opus to Opus Replication (O2R) management
Geographic information system (GIS)

Entity Specific Modules

The entity specific modules cover functionality, custom made to suit the platform and types of
planning, reporting and execution that the entities are required to perform at the specific
squadron/wing ops. Typical totes cover functions like flying boards, mission and maintenance
scheduling, logistic holdings, force protection boards, intelligence and log books.

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 are also monitored by
the CAOC/NAOC and the controlling CRC. The Flying Board are also available as a web tote.

page 9
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 Entity Specific Modules

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 - like ATO txt, com Freq, callsign, mission notes etc. The planner assigns AC
and pilots to the actual mission. An AC Configuration Tote is used by the ground crew and weapon
crew to report AC status pr AC Tail number, changes to the AC configuration, used parking spot etc.
Data from the AC Configuration Tote updates the Flying Board automatically. Take-off and landing
time is 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

NATO Airborne Early Warning (NAEW)

The NAEW module is custom made to replace functionality previously provided by the
decommissioned NAEW&C F 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 are monitored and used by the
CAOCs and AIRCOM Air OPS planning and tasking.

page 10
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 Entity Specific Modules

Fig 12 AEW Missions, Flight Schedule

Fig 13 AEW Missions, Timeline

Fig 14 Message Processing

page 11
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 Entity Specific Modules

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

Fig 15 GBAD Alert Status

Fig 16 GBAD Logistics

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 LOG classes I-V. In
addition, infrastructure and manning status/planning is supported.

page 12
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 The NEC CCIS System

Fig 17 Part of Log Tool

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 (on the same server as the database backend)
The NEC CCIS client (executable 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 client installation consists of four components: The
Tote Browser (for access to text/table based data), the Geographical Information System (GIS),

page 13
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 The NEC CCIS System

currently using Teleplan MARIA 7, the Military Message Handling client (currently using Systematic
IRIS/MFS 8), and the NEC CCIS operational and technical documentation, accessible in HTML and PDF
format in a web browser (Internet Explorer).

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 18 NEC CCIS site architecture

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 9.

NEC CCIS is currently undergoing a modernization project named Magnum, where the goals are to
migrate the OPUS server from Solaris, to replace MARIA, and to adapt the Setup Analyst Tools
(Santos 10). The results will give the users a more modern user experience at a lower system
maintenance cost.

As a part of the Magnum project a web client is also being developed. Operational functionality is
being migrated from the existing NEC CCIS client into the web client, which will provide user access
to NEC CCIS from any client with a web browser connected to the NS WAN.

7
To be fully replaced by LuciadRIA in 2017/18
8
To be replaced by XOmail by end 2017/18.
9
No data is stored locally. The zero clients are unclassified as soon as power is turned off.
10
Further described in the Software Management chapter

page 14
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 The NEC CCIS System

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

Nation A
sites

CAOC A
Nation B
sites

CAOC B

Nation C
sites
CAOC C

Fig 19 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 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.

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 XO mail/X400 Link-11B

Multi-AEGIS Site Emulator (MASE) Link-1
Maritime Command and Control System (MCCIS) (OTH/Gold)
NATO SEW (Shared Early Warning)

page 15
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 The NEC CCIS System

Norwegian Advanced Surface to Air Missile System (NASAMS) II - SDXP (proprietary)

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), ASAC, statuses, and reports.

Maintaining interoperability with ACCS is an important task to the SSC, in order to ensure 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
NEC CCIS, but due to cut in functionality of ACCS, especially within the area of WOC/SQOC, NEC CCIS
will continue to be used after the fielding of ACCS. Also the increased maintenance cost of ACCS,
leading more users/nations to reconsider or delay their plans of replacing legacy systems with ACCS
at their nationally funded sites, has led to the same conclusion. The interfaces to ACCS AdatP3 and
Link-11B are under continuous development - following the evolvement of ACCS. Some development
is funded through the ACCS project and the rest is covered by SSC O&M 11 funds. Currently, NEC
CCISs AdatP3 interface to ACCS meets the CAOC Uedem Early Operational Capability (EOC)
requirements.

Security
NEC CCIS has a formal security accreditation at the NATO SECRET level in the System High mode of
operation. All NEC CCIS releases go through NATOs 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 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 development of
new functionality. The change management system allows for any software related issue to be

11
O&M; Operation and Maintenance

page 16
An Introduction to NEC CCIS
version 1.3, 28 Apr 2017 Contact Info

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.

Contact Info
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: post@ssc.nato.int

E-mail NS-WAN:
NEC CCIS SSC POST
(NECCCISSSCPOST@ais.nato.int)

History of changes

Date Version Reason for change

Content and structure updates and additions. New illustrations. Broadened scope. Changed title
28 Apr 2017 1.3
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

page 17