catch ~Next ~Previous ~Home!
See also Patrol and Business software!
Zeta series Military Helicopter FC4M Software:
[001]~ Mission
[002]~ Theater
[003]~ Network
[004]~ Manned vehicles
[005]~ Hatching
[006]~ Target
[007]~ Navigation
[008]~ Schedule
[009]~ Dropping sensors
[010]~ FC Helicopter Sensoring
[011]~ Freedom Base FB
[012]~ Freedom Sensors FS
[013]~ Sensored data
[014]~ Commands
[015]~ Resources
[016]~ Messages
[017]~ Logic
[018]~ Operating system
[019]~ Forces
[020]~ Environment
[021]~ Context
[022]~ M+
[023]~ Simulation Software
[024]~ High Level Architecture (HLA)
[025]~ Joint Tactical Radio System
[026]~ SCA /Software Defined Radios(SDR)
[027]~ SCA / Waveforms
[028]~ Software Communications Architecture (SCA)
[029]~ Ontology
[030]~ Java Platform
[031]~ Common Operating System
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[001]~ Military Helicopter FC Software: Mission
Base class:
~ military unmanned air vehicle's mission
Sub classes:
~ military unmanned rotary wing air vehicle's mission
FC Helicopter class:
~ FC_Helicopter_Mission_Manager
~ methods: start, survey, sensor, drop sensors, collect sensor data, report, communicate, rest, stop
~ tailored: rapid deployment to remote nuclear power station and unmanned operating there
Description:
~ manages FC helicopter's flying near nuclear power station
~ handles mission goals, orders, reports, messages
catch: ~[content] ~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[002]~ Military Helicopter FC Software: Theater
Base class:
~ military standard theater
Sub classes:
~ military unmanned rotary wing air vehicle's theater
FC Helicopter class:
~ FC_Helicopter_Theater_Manager
~ methods: give map, show target, give obstacles, show forces...
~ tailored: tailored to FC helicopter, navy,air force, army, surveillance of nuclear power station
Description:
~ handles location information
~ checks maps around nuclear power station, wheather in that area, obstacles, FB bases to be dropped there
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[003]~ Military Helicopter FC Software: Network
Base class:
~ military standard network
Sub classes:
~ military unmanned rotary wing air vehicle's network
FC Helicopter class:
~ FC_Helicopter_Network_Manager
~ methods: make connection, give status, show resources...
~ tailored: wireless FS sensor networks, network between FB base,FC helicopter, MILITARY NET
Description:
~ takes care of all networking operations during mission
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[004]~ Military Helicopter FC Software: Manned vehicles
Base class:
~ military manned air vehicle
Sub classes:
~ military rotary wing air vehicle
FC Helicopter class:
~ FC_Helicopter_Manned_Vehicle_Manager
~ methods: download software, download mission instructions, tell about dropping, confirm hatching...
~ tailored: fighter deploying FC helicopter to target area such as oil field due to fire, for example
Description:
~ manages communication, messages, refuelling, collaboration with FB base
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[005]~ Military Helicopter FC Software: Hatching
Base class:
~ n/a - to be developed
Sub classes:
~ n/a- to be developed
FC Helicopter class:
~ FC_Helicopter_Hatching_Manager
~ tailored: FC helicopter is capable to hatch in the air after being dropped by a fighter
~ methods: release, confirm...
Description:
~ manages all phases of hatching,
~ communicates with a fighter dropping FC helicopter
~ reports to a nearest FB base, if there is one in area
~ starts mission
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[006]~ Military Helicopter FC Software: Target
Base class:
~ military unmanned air vehicle's target
Sub classes:
~ target for military unmanned rotary wing air vehicle's
FC Helicopter class:
~ FC_Helicopter_Target_Manager
~ tailored: target might be a nuclear power station
~ methods: show location, give resources around, tell dimensions...
Description:
~ manages targets by taking care of having the latest information
~ finds out target location and architecture in FC helicopter
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[007]~ Military Helicopter FC Software: Navigation
Base class:
~ military unmanned air vehicle's navigation
Sub classes:
~ military unmanned rotary wing air vehicle's navigation
FC Helicopter class:
~ FC_Helicopter_Navigation_Manager
~ tailored: FC helicopter registers where it drops FS sensors and uses them also to navigate
~ methods: show sensors along route, give location information...
Description:
~ manages routes by knowing route nodes, landscape, obstacles, length, sensors dropped
~ avoids collisions, registers remarkable points,
~ handles digital map, receives instructions for navigation from FB base
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[008]~ Military Helicopter FC Software: Schedule
Base class:
~ military unmanned air vehicle's schedule for a mission
Sub classes:
~ military unmanned air vehicle's schedule for a mission
FC Helicopter class:
~ FC_Helicopter_Schedule_Manager
~ tailored: unmanned & autonomous FC helicopter operating in a remote theater
~ methods: download, give, update, upload ...
Description:
~ schedules sensor dropping, collection of sensor data, flying, sheltering, refuelling
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[009]~ Military Helicopter FC Software: Dropping sensors
Base class:
~ military dropping sensors from fixed wing UAV
Sub classes:
~ military dropping sensors from rotary wing UAV
FC Helicopter class:
~ FC_Helicopter_Dropping_Manager
~ tailored: FC helicopter registers FS sensor location and reports it to FB base
~ methods: start, drop, register, stop, pause, schedule ...
Description:
~ handles dropping of sensors to required positions,
~ dropping new sensors to target area, if necessary
~ dropping sensors around FB base
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[010]~ Military Helicopter FC Software: FC Helicopter Sensoring
Base class:
~ military unmanned air vehicle's sensoring
Sub classes:
~ military unmanned rotary wing air vehicle's sensoring
FC Helicopter class:
~ FC_Helicopter_Sensoring_Manager
~ tailored: FC helicopter has it's own sensors
~ methods: start, stop ...
Description:
~ manages FC helicopter's sensoring tasks and sensor database
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[011]~ Military Helicopter FC Software: Freedom base FB
Base class:
~ military standard base
Sub classes:
~ military unmanned base
FC Helicopter class:
~ FC_Helicopter_FB_Manager
~ tailored: FC helicopter knows only the FB bases it is allowed to know in target area
~ methods: order more fuel, refuel, receive sensored data, download software & instructions...
Description:
~ manages collaboration with FB base
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[012]~ Military Helicopter FC Software: Freedom Sensors FS
Base class:
~ military standard sensor
Sub classes:
~ wireless military sensor
FC Helicopter class:
~ FC_Helicopter_FS_Manager
~ tailored: security i.e. only FC helicopter which has dropped FS sensor is typically allowed to communicate with it
~ methods: give sensor data, receive software and instructions, stop, erase yorself...
Description:
~ manages sensors FC helicopter drops by establishing communication with them,
~ by uploading sensor data and downloading software updates and instructions to sensors
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[013]~ Military Helicopter FC Software: Sensored data
Base class:
~ military standard sensor data
Sub classes:
~ wireless sensor data from smart sensors
FC Helicopter class:
~ FC_Helicopter_Sensor_Data__Manager
~ tailored: sensor data FC helicopter collects from FS sensors and from it's own sensors
~ methods: save, download...
Description:
~ handles sensored data by tagging it and by making it ready for downloading to FB base
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[014]~ Military Helicopter FC Software: Commands
Base class:
~ military unmanned air vehicle's commands
Sub classes:
~ military unmanned rotary wing air vehicle's commands
FC Helicopter class:
~ FC_Helicopter_Command_Manager
~ tailored: commands from FB base and from MILITARY NET to FC helicopter
~ methods: receive, perform...
Description:
~ manages command queues, command handling, priorities
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[015]~ Military Helicopter FC Software: Resources
Base class:
~ military unmanned air vehicle's resources
Sub classes:
~ military unmanned rotary wing air vehicle's resources
FC Helicopter class:
~ FS_Helicopter_Resource_Manager
~ tailored: FC helicopter's own resources, FB base, FS sensors, resources in theater, MILITARY NET
~ methods: give fuel amount for mission, to return to FB base...
Description:
~ manages resources minimizing resource, such as fuel usage
~ maximizing sensor usage by optimizing sensor locations
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[016]~ Military Helicopter FC Software: Messages
Base class:
~ military unmanned air vehicle's messages
Sub classes:
~ military unmanned rotary wing air vehicle's messages
FC Helicopter class:
~ FC_Helicopter_Message_Manager
~ tailored: messages between FC helicopter and FB base, FS sensors and MILITARY NET
~ methods: receive, send, store, queue...
Description:
~ manages messages, receiving, sending, storing, handling, queueing
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[017]~ Military Helicopter FC Software: Logic
Base class:
~ military unmanned air vehicle's logic
Sub classes:
~ military unmanned rotary wing air vehicle's logic
FC Helicopter class:
~ FC_Helicopter_Logic_Manager
~ tailored: fuzzy logic is being used for missions
~ methods: n/a
Description:
~ uses fuzzy logics
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[018]~ Military Helicopter FC Software: Operating system
Base class:
~ Common Operating System (COS)
Sub classes:
~ Embedded COS
FC Helicopter class:
~ FC_Helicopter_OS
~ tailored: UAV, FC helicopter requirements
~ methods: operating system methods
Description:
~ embedded OS handles FC helicopter application software, hardware and communication
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[019]~ Military Helicopter FC Software: Forces
Base class:
~ forces with military unmanned air vehicle
Sub classes:
~ forces with military unmanned rotary wing air vehicle
FC Helicopter class:
~ FC_Helicopter_Forces_Manager
~ tailored: special operation forces, commandors, marines...
~ methods: get, update, communicate...
Description:
~ manages information about forces in theater, it may send help
~ message to FB base, which may alarm a person connected to FB base with FD1/FD2 device
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[020]~ Military Helicopter FC Software: Environment
Base class:
~ military unmanned air vehicle's environment
Sub classes:
~ military unmanned rotary wing air vehicle's environment
FC Helicopter class:
~ FC_Helicopter_Environment_Manager
~ tailored: surveillance, reconnaissance, nuclear power station, Iraq, Persian Gulf area ...
~ methods:
Description: give wheather, tell obstacles...
~ manages environment data about that specific area taking into account
~ desert heat, storms, day times, landscapes, obstacles
catch: ~[content] ~[previous]~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[021]~ Military Helicopter FC Software: Context
Base class:
~ military standard context with unmanned air vehicles
Sub classes:
~ military standard context with unmanned rotary wing air vehicles
FC Helicopter class:
~ FC_Helicopter_Context_Manager
~ tailored: Persian Gulf area, Iraq, Iran, Saudi Arabia, UAE, Yemen, Bahrain, Kuwait, Persian Gulf, Iran
~ methods: give, update, get, upload ...
Description:
~ manages context by taking into account specific features
~ of oil industry, oil pipelines, oil refineries specially in Persian Gulf area
catch: ~[content] ~[previous]~[next]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[022] FC4M Software ~ Military Helicopter: ~ M+
M+ explored:
~ any of allies fighter may drop FC helicopter
~ pod such as Lockheed Martin Sniper XR targeting pod is one alternative to drop FC helicopter
~ helmet-mounted cueing system (HMCS) may give information where to drop FC helicopter
~ FC could be part of Joint Direct Attack Munition (JDAM)
~ Data collected,which FC collects from sensors and sensors by itself, and which FC downloads to FB, could be uploaded to fighters by FB base
~ Link 16 protocol could be used between FB base and fighters
Links & info:
~ F-16 software adds new missile capabilities
~ US Air Force (USAF) F-16 Fighting Falcons are being given a capability to deliver
~ the Lockheed Martin AGM-158 Joint Air-to-Surface Standoff Missile (JASSM)
~ as a result of receiving the M3+ standard of software.
~ F-16s operating in Belgium, Denmark, the Netherlands, Norway and Portugal are receiving the M3 standard,
~ which allows them to deliver the Joint Direct Attack Munition (JDAM).
~ The M3+ software also allows US F-16s to use the helmet-mounted cueing system (HMCS),
~ the Lockheed Martin Sniper XR targeting pod and the Link 16 datalink.
catch: ~[content] ~[previous] ~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[023] FC4M Software ~ Military Helicopter: ~ Simulation Software
Simulation Software
~ Simulation software is being used for FC and also to FB
~ FB base can simulate FC route and activities after downloading new instructions from command and control center
Links:
~ The Defense Modeling and Simulation Office (DMSO) is the catalyst organization for Department of Defense (DoD)
~ modeling and simulation (M&S)
catch: ~[content] ~[previous] ~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[024] FC4M Software ~ Military Helicopter: ~ High Level Architecture (HLA)
High Level Architecture (HLA)
~ HAL could be used both to FC and FB
Links & Info:
~ The High Level Architecture (HLA) is a general purpose architecture for simulation reuse and interoperability
~ to support reuse and interoperability across the large numbers of different types of simulations developed and maintained by the DoD.
~ the standard technical architecture for all DoD simulations on September 10, 1996.
~ The HLA was approved as an open standard through the Institute of Electrical and Electronic Engineers (IEEE) - IEEE Standard 1516 - in September 2000
~ Joint Battlespace /Joint Virtual Battlespace!
catch: ~[content] ~[previous] ~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[025] FC4M Software ~ Military Helicopter: ~ Joint Tactical Radio System
Joint Tactical Radio System
~ JTA could be used
Links:
~ The functionality and expandability of the Joint Tactical Radio System is built upon the Software Communications Architecture (SCA)
~ The SCA is an open architecture framework that tells designers how elements of hardware and software are to operate in harmony within the JTRS
~ Standard framework both fo sw and hw
catch: ~[content] ~[previous] ~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[026] FC4M Software ~ Military helicopter: SCA /Software Defined Radios(SDR)
SCA /Software Defined Radios(SDR)
~ SCA and SDR are being used
~ FB base do many software tasks for FC helicopter
Background:
~ shift from hardware-intensive radios to flexible, multiband, multimode software radios,
~ in which functionality is provided through software rather than hardware
Definition:
~ A Joint Tactical Radio (JTR) set consists of waveform applications,
~ the radio hardware, and associated operating environment, which conform to the Software Communications Architecture (SCA).
~ The JTR set hardware, with the associated SCA operating environment, includes:
~ Radio Frequency (RF) hardware components
~ Receiver
~ Amplifier
~ Modem
~ Antenna
~ Information Security (INFOSEC) devices
~ Hardware-specific interfaces
~ Operating System (real-time, POSIX compliant)
~ CORBA Common Object Request Broker
~ Core Framework software
~ Associated adapters/drivers used to interface between the software and hardware
~ Software including waveform applications, crypto algorithms, protocols, formats, and routers
catch: ~[content] ~[previous] ~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[027] FC4M Software ~ Military Helicopter: ~ SCA / Waveforms
SCA / Waveforms
~ SCA waveforms are being used
Definition:
~ Interoperability within JTRS will be supported through the use of software-based waveforms.
~ The waveform software developed for JTRS includes not only the actual radio frequency (RF) signal in space,
~ but the entire set of radio functions that occur from the user input to the RF output and vice versa.
~ For example, in the transmitting JTRS, the waveform software will control the receipt of the data
~ (either analog or digital) from the input device and manage the encoding.
~ The encoded data is passed to the encryption engine.
~ The resultant encoded/encrypted data stream is modulated into an intermediate frequency (IF) signal.
~ Finally, the IF signal is converted into a RF signal and transmitted to the antenna.
~ These same functions will be reversed in the receiving JTRS with the ultimate output of the data to the user.
~ JTRS waveforms will be "portable" between hardware platforms
catch: ~[content] ~[previous] ~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[028] FC4M Software ~ Military Helicopter: ~ Software Communications Architecture (SCA)
Software Communications Architecture (SCA)
~ SCA is being explored
Overview:
~ The functionality and expandability of the Joint Tactical Radio System
~ is built upon the Software Communications Architecture (SCA).
~ The SCA is an open architecture framework that tells designers
~ how elements of hardware and software are to operate in harmony within the JTRS.
~ It governs the structure and operation of the JTRS, enabling programmable radios to
~ load waveforms,
~ run applications, and
~ be networked into an integrated system.
~ Design engineers use the SCA definition document just as an architect
~ or planner uses a local building code to design and build homes.
~ Through adherence to standards detailed in the SCA definition document,
~ both hardware and software designers know what equipment and programs to design.
~ The SCA does not tell designers how to design their equipment and programs.
~ Thus, JTRS compliant radios and networked systems, when designed in compliance with the SCA,
~ will meet JTRS standards for interoperability,
~ just as properly designed plumbing or electrical systems meet local codes for construction and safety.
~ The software application waveforms, including
~ the Wideband Networking Waveform (WNW),
~ network services, and
~ the programmable radio set (i.e., the traditional radio box) form the JTR set.
~ The JTR sets, when networked with other JTR sets, becomes the JTRS.
Standardization
~ The Software Communications Architecture (SCA) defines standard interfaces
~ that allow waveform applications to run on multiple hardware sets.
~ The SCA defines a Core Framework (providing a standard operating environment) that must be implemented on every JTR set.
~ Interoperability among radio sets is enhanced because the same waveform software can be easily ported to all JTR sets.
~ Standardization is the key and two activities are on-going to assure
~ that the SCA is widely accepted as the programmable radio system definition standard.
~ First, the JPO has been working closely with the Software Defined Radio Forum (SDRF)
~ to involve their expertise in the development of the SCA.
~ The SDRF is not a standards body itself;
~ however, the group adopted the SCA as a body of work mature enough to move out to a formal standards body,
~ in this case the Object Management Group (OMG). This occurred FY2000 when the SCA was at v1.0.
~ Since then the SDRF and the OMG have developed a formal liaison relationship to help further the standardization of the SCA.
~ The OMG, a non-for-profit consortium that produces and maintains computer industry specifications
~ for interoperable enterprise applications,
~ has established a Domain Special Interest Group for software radios (SWRADIO DSIG).
~ This group, with JPO sponsorship, is working toward building an international commercial standard based on the SCA.
~ Actions within the OMG SWRADIO DSIG will evolve the SCA through multi-source inputs, including those from governments,
~ the SDRF and the private sector. Once an international standard is defined and adopted,
~ then future programmable radio development (including JTRS within the DoD and US Government)
~ would align with this standard as it evolves.
~ The Configuration Management process within the JTRS JPO
~ will review the standards and decide how to incorporate them into the SCA.
~ As a result, future software radios should be interoperable
~ in much the same way that the international phone system has been constructed
~ into an integrated multi-national managed but one global system.
Future work will include:
~ Developing common radio systems applications other than waveform
~ Building a broader library of Application Program Interfaces (APIs)
~ Developing future releases of the SCA that emphasize backward compatibility
~ Implementation of security features that are acceptable across a broad range of multi-national users.
~ Individual nations, such as France and Sweden have adopted or are considering adopting forms of the SCA
~ The United States and others are also working within NATO to have the SCA adopted.
~ Work will continue within the OMG to standardize relevant areas of the SCA
~ as a formal international standard to assure that development within separate nations, and possibly NATO,
~ are aligned and coordinated under a single worldwide standard.
catch: ~[content] ~[previous] ~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[029] FC4M Software ~ Military Helicopter: ~ Ontology
Ontology
~ Ontology is being explored
Links & comments:
~ Daml.org (DARPA)
~ DAML+OIL
~ Rosetta
~ It is easier to convert coordinates to different units
~ Messages between FC and FB base: detach point,landing point...
~ CONTENT points: detach point, landing zone...ALTERNATIVE detach at sea...
~ FB may ask FC to find out locations of SAM missiles
~ DAML.ORG
~ OIL~ Europe
~ OIl Inference Layer
~ Ontologies provide a shared and common understanding of a domain
~ that can be communicated between people and across application systems
~ They will help FC and FB to communicate with each others and FB to communicate with command and control center
~ Location ontology
~ Medical Ontology
~ Hospital Ontology
~ UK rescue operation
~ KAoS agent
~ Semantic Web Services
~ DAML Rules
~ Helicopter ontology!
~ Helicopter
~ CYC
~ opencyc.org
~ US Navy operation
Summary:
~ FC4M,FS4M and FB4M devices could be modelled based on ontology!
~ This would allow to use standard terminology and coding and symbols
~ Messages to and from UAV helicopter have already been modelled!
~ Modelling of special messages:
~ between fighter and FC helicopter
~ between FB base and FC helicopter
~ between FB helicopter and FS sensors
catch: ~[content] ~[previous] ~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[030] FC4M Software ~ Military Helicopter: ~ Java Platform
Java Platform
~ in certain cases java might be a software platform to use
Waves:
~ the Headquarters Operations and Sustainment Systems Group of the Dept. of the Air Force
~ is the first Dept. of Defense organization to completely implement a Java Center of Excellence (JCOE) program.
~ The U.S. Air Force worked with Sun for over a year to develop and codify an iterative application development methodology
~ and architecture plan that can be used to streamline future development efforts.
~ Java Center of Excellence provides a centralized structure that institutionalizes technology, knowledge and skills transfer
~ throughout the organization, increasing our agility while facilitating product and service delivery via the Web
~ Recognizing the interoperability and modular construction enabled by the Java platform
catch: ~[content] ~[previous] ~[next]!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[031] FC4M Software ~ Military Helicopter: ~ Common Operating System
Common Operating System
~ being explored; COS is the new operating system designed for J-UCAS and for networked battle space
Links& News:
~ Green Hills Software Inc
~ WindRiver
catch: ~[content] ~[previous]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Small & Smart Inc reserves rights to change this specification
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~