h=10 nowrap> « back to results for ""
Below is a cache of http://www.omg.org/docs/c4i/05-11-01.pdf. It's a snapshot of the page taken as our search engine crawled the Web.
The web site itself may have changed. You can check the current page or check for previous versions at the Internet Archive. Yahoo! is not affiliated with the authors of this page or responsible for its content.
Alert Management Service for CMS Systems

Page 1 of 32
11/14/2005
APPROVED FOR PUBLIC RELEASE: USN STATEMENT A, DATED Nov 14, 2005




Alert Management Service for CMS Systems

Proposal prepared by
Raytheon Integrated Defense Systems
in response to OMG RFP c4i/2004-11-13



14 November 2005

OMG document number c4i/2005-11-01

Raytheon Integrated Defense Systems
8680 Balboa Ave.
San Diego, Calif.


Telephone: 858 522 2042
Facsimile: 858 522 4322



Page 2 of 32
11/14/2005
APPROVED FOR PUBLIC RELEASE: USN STATEMENT A, DATED Nov 14, 2005
This page is intentionally Blank
ALAMS RFP Submission
Raytheon Integrated Defense Systems

Page 4 of 32
11/14/2005
APPROVED FOR PUBLIC RELEASE: USN STATEMENT A, DATED Nov 14, 2005
Table of Contents


Alert Management Service for CMS Systems .......................................................................................1
1 ALMAS DESIGN............................................................................................................................6
1.1 Alert-Management-Service-for-CMS-Systems/' >Scope........................................................................................................................................6
1.1.1 Identification.......................................................................................................................6
1.1.2 Copyright Statement............................................................................................................6
1.1.3 Proof of Concept ................................................................................................................6
1.1.4 Point of Contact..................................................................................................................6
1.1.5 Document Overview ...........................................................................................................6
1.2 Introduction to ALMAS.............................................................................................................7
1.2.2 Terminology & Design Concepts.........................................................................................7
1.2.3 Scope of Proposal ..............................................................................................................8
1.2.4 General Design methodology...............................................................................................9
1.3 ALMAS Components..............................................................................................................10
1.3.1 Alerts Definition Schema ...................................................................................................10
1.3.2 API ..................................................................................................................................12
1.3.3 Alerts Configuration File....................................................................................................14
1.3.4 Requirement Compliance Matrix........................................................................................14
2 Specification for ALMAS................................................................................................................15
2.1 ALMAS Context Representation..............................................................................................15
2.2 ALMAS Platform independent model.......................................................................................15
2.3 ALMAS sequence diagrams.....................................................................................................17
2.3.1 Console Mode Control Changes ...........................................................................................18
2.3.2 Application Operator Alert................................................................................................19
2.3.3 Application Delete Operator Alert.....................................................................................20
2.3.4 Console Generate Alert List ..............................................................................................21
2.3.5 Console Generate Highest Alert.........................................................................................23
2.4 ALMAS API...........................................................................................................................24
2.4.1 Alert Queue Manager IDL ...............................................................................................24
2.4.2 Client Alert Queue IDL....................................................................................................27
3 CHANGES TO EXISTING OMG SPECIFICATIONS ................................................................32


Table of Figures

Figure 1 Alert Queue.........................................................................................................................15
Figure 2 -- Alert Queue Manager.......................................................................................................16
Figure 3 -- Alert Database Description...............................................................................................17
Figure 4 Console Mode Control Affects on Alert Registration.............................................................18
Figure 5 Appliction Operator Alert Sequence Diagram........................................................................19
Figure 6 Application Delete Operator Alert........................................................................................20 ALAMS RFP Submission
Raytheon Integrated Defense Systems

Page 5 of 32
11/14/2005
APPROVED FOR PUBLIC RELEASE: USN STATEMENT A, DATED Nov 14, 2005
Figure 7 Console Generate Alert List..................................................................................................22
Figure 8 Console Generate Highest Alert............................................................................................23 ALAMS RFP Submission
Raytheon Integrated Defense Systems

Page 6 of 32
11/14/2005
APPROVED FOR PUBLIC RELEASE: USN STATEMENT A, DATED Nov 14, 2005

1 ALMAS DESIGN

1.1 Scope
1.1.1 Identification

This document is the Raytheon Integrated Defense Systems (IDS) proposal for the standard Alert
Management System (ALMAS).

1.1.2 Copyright Statement

Raytheon IDS: (i) grants to the Object Management Group, Inc. (OMG) a nonexclusive, royalty-free, paid
up, worldwide license to copy and distribute this document and to modify this document and distribute
copies of the modified version, and (ii) grants to each member of the OMG a nonexclusive, royalty-free,
paid up, worldwide license to make up to fifty (50) copies of this document for internal review purposes
only and not for distribution, and (iii) has agreed that no person shall be deemed to have infringed the
copyright in the included material of any such copyright holder by reason of having used any OMG
specification that may be based hereon or having conformed any computer software to such specification.
1.1.3 Proof of Concept

This proposal is based directly upon the implementation of the Alert Management component found within
the Ship Self Defense System Mk2 (SSDS MK2) Combat Management System product. The alerts and
associated client modules have successfully undergone customer Formal Acceptance Testing for multiple
platforms.
1.1.4 Point of Contact

Point Of Contact:
Ronald W. Townsen
Raytheon Integrated Defense Systems
8680 Balboa St
San Diego, Ca. 92123
Email: rwtownsen@raytheon.com

1.1.5 Document Overview
ALAMS RFP Submission
Raytheon Integrated Defense Systems

Page 7 of 32
11/14/2005
APPROVED FOR PUBLIC RELEASE: USN STATEMENT A, DATED Nov 14, 2005
This document is organized as follows:
??
Section 1.2 introduces ALMAS.
??
Sections 1.3 describe non-normatively the proposed structure and relevant design.
??
Section 2 provides a normative proposed specification for ALMAS.
??
Section 3 provides a normative breakdown of required changes to existing OMG specifications.


1.2 Introduction to ALMAS


1.2.1 Problem statement


The vast domain of C4I systems all share a common need to report significant events to interested parties,
be that interested party a system operator, or an affected software component. The concept of alert
management is implemented in a wide variety of systems. Furthermore such components tend to be
developed alongside and integrated with the system for which they are intended, leading to unnecessary