# Presentation: 693309

##  US Air Force/Open Applications Group Activities

**Ms Sandra Swearingen**
**HQ AFCA/ITCM, 618-229-6830**
**February 2003**
** **** **

## Overview

**Air Force Open Applications Group, Inc (OAGI) representation**
**Global Combat Support System – Air Force (GCSS-AF) implementation**
**Enterprise Information Management (EIM) applications**
**Integration using Web Services**

## AF OAGI Representation

**AFCA/ITCM - Air Force representative to the Open Applications Group**
**Lockheed Martin Systems Integration (LMSI) – GCSS-AF System Integrator**

## GCSS-AF

**Global Combat Support System - Air Force **
**Secure, accurate, timely, ubiquitous combat support information to the operator**
**Combat Support enterprise divided into 22 functional pillars**
**Supply, Transportation, Personnel, Communications, Maintenance, Acquisition, etc.**

## GCSS-AF Architecture

**Application**
**Framework**

**Cross-business Interoperability**

**Middleware**

**OS, DBMS, Platforms,**
**Networks**

**Information Services**

**Security, Directory Serv., **
**Distribution Concurrency, **
**Events, Persistency ...**

*Reference Architecture*

***GCSS-AF Architecture***

## GCSS-AF

**GCSS-AF approach to interfaces**
- Open Applications Group Inc. Specification (OAGIS) based – Business Object Document (BODs)
- Align functional pillars with industry
- Develop verticals for AF processes
**New supply chain interfaces**
***Item Management Cataloging (7 BODs)***
***Audit Trail (5 BODs)***
** ****EIM Integration **

## Knowledge Reservoir

- Functional Interoperability

**Goal:  Integrated suite of products that empowers users to electronically create, coordinate, collaborate, and obtain approval of any official action in a seamless intuitive environment**** **

**Notes:**
- State:  We want to establish a knowledge reservoir and establish Functional Interoperability between the suite of EIM applications 

## Seamless functional exchange of information
Capitalize on GCSS-AF architecture
Open Applications Group Inc. (OAGI) XML-based Business Object Documents for data exchange
AFCA AF technical representative to OAGI 
Use standard data exchange
eXtensible Markup Language (XML)
Web services

**Capitalize on GCSS-AF architecture**
**Open Applications Group Inc. (OAGI) XML-based Business Object Documents for data exchange**
**AFCA AF technical representative to OAGI **
**Use standard data exchange**
**eXtensible Markup Language (XML)**
**Web services**

***EIM Integration***

**Notes:**
- We want to implement Enterprise Information Management within the context of the GCSS-Air Force Integration Framework 

    -- We want to capitalize on the GCSS-Air Force architecture, using the Open Applications Group XML Business Object Documents

    -- We want to use XML to facilitate standard data exchange between the EIM applications
        --- We are planning to use XML to exchange data between ESTARS and ECATS  

## Web Services

**Web Services standardizes**
**Shape of the plugs**
**Shape of the outlet**
**Technology neutral**
**Web Services needs electrical current (Business Language) to travel over the wire**
**OAGIS is a the Business Language (electrical current)**

***Web Services***

**Notes:**
Web Services is a way to send one XML BOD messagegrams wrapped in SOAP envelopes from one AIS to another. You’ll notice that the socket has a place for Security while the plug does not. This is a reminder that we must properly secure the Enterprise Transaction Layer from the very beginning and not try to bolt security on later.

## Take Aways

**Create an “Interoperable Business Environment”**** **
**Total business approach to Automated Information System (AIS) development **
**Seamless exchange of AIS functional information**
**Ability to replace AIS functionality transparently**
**Not “locked” to proprietary solutions--keeps “vendors” honest and competitive**
**Corporately adopt GCSS OAGIS/XML for “functional” info exchange/AIS development**
**Use GCSS-AF IF with Web Services enhancement**

**Notes:**
At the end of the day, the most important strategic accomplishment of the EIM project will be the modular backbone that allow the first two or three applications to exchange data. This will allow us to focus future enterprise improvement efforts on at the data element layer instead of buying whole new applications.

## Air Force fully supports implementation of XML technology
Represented Defense Information Systems Agency in W3C XML Query working group
XML standards included in DoD and Air Force Technical architectures
Active in OAGI and incorporating OAGI specifications into AF operational systems 
Closely following Navy and Federal CIO Council XML Working Group XML initiatives 

**Represented Defense Information Systems Agency in W3C XML Query working group**
**XML standards included in DoD and Air Force Technical architectures**
**Active in OAGI and incorporating OAGI specifications into AF operational systems **
**Closely following Navy and Federal CIO Council XML Working Group XML initiatives **

***Summary***

## Air Force Communications Agency

***I n t e g r i t y  -  S e r v i c e  -  E x c e l l e n c e***