Alan T' Waite

1
Environmental, Safety, and Occupational Health
Management Information System (ESOH-MIS)
Alan T. Waite HQ USAF/ILEVQ 20 Nov 03
2
Overview

• Summary
• What are We Doing?
• Why are we Doing IT?
• Who is doing IT?
• When are We Doing IT?
• How do We Define Requirements?
• Issues?
• Conclusions

3
Summary

• Environment, Safety, and Occupational Health
  Management Information System (EESOH-MIS)
• Integrated
• Corporate
• Phased development/deployment of 16 environmental
  applications
• Phase 1 deployment begins in Jan 04
• Hazardous materials application
• Phase 2 development begins in FY04
• Pest management application

4
Summary

• Air Force Global Combat Support System -
  Information Framework (AF GCSS-IF) is the hosting
  agency
• Centrally hosted within AF GCSS-IF framework on
  DISA servers
• No downloaded components security issue
• Certificate of Networthiness (CON) and
  Certificates to Operate (CTOs) are not required
• Accessed through the Air Force Portal
• All test and implementation personnel must obtain
  their own password for https//my.af.mil
• Microsoft Internet Explorer (IE) 6.0 Browser

5
What are We Doing?

• EESOH-MIS
• Focused on improving and standardizing business
  practices
• Integrated, multimedia system vs. multiple
  stovepipe systems
• Internal and external Air Force Interfaces
• Is NOT an incremental adaptation and interfacing
  of existing legacy systems
• Strategic goals
• Integrated solution
• Adaptable
• Standardized
• Shared information

6
What are We Doing?
Architecture
7
Why are We Doing IT?

• Global Combat Support System - Air Force(AF
  GCSS-AF)
• Clinger-Cohen Act of 1996 (40 USC 1425)
• Web-based systems
• Commanders' NOTAM 00-5, 11 Sep 00, One Air Force,
  One Network
• JCS Capstone Requirements Document, 5 Jun 00

8
Why are We Doing IT?

• Command, Control, Communications, Computers and
  Intelligence Support Plan (C4ISP)
• Certificate of Networthiness (CON)
• Certificates to Operate (CTOs)
• Air Force Portal

9
Why are We Doing IT?

• Global Combat Support System - Air Force
• A strong and robust ACS is key to the success of
  the EAF concept and supports the Air Force core
  competency of Rapid Global Mobility.
• Global Combat Support System - Air Force
  (GCSS-AF) is a key enabler of ACS and provides a
  framework for integrating our critical combat
  support information systems and processes
  across functional areas. It will provide
• the warfighter and supporting elements
• with timely, accurate, and trusted ACS
• information to execute the full
• spectrum of
  military operations.

10
Why are We Doing IT?

• Clinger-Cohen Act
• Ensure the interoperability of IT and national
  security systems throughout DoD
• Provide for the elimination of duplicate IT and
  national security systems within and between the
  military departments and Defense Agencies
• Ensure that IT and national security systems
  standards that will apply throughout the DoD are
  prescribed

11
Why are We Doing IT?

• Web-based System
• Commanders' NOTAM 00-5, One Air Force, One
  Network, 11 Sep 00
• providing every airman access to rich training
  resources, simple and intuitive self-service
  web-based tools, and the ability to communicate
  reliably, securely, globally all the time.
• JCS Capstone Requirements Document, 5 Jun 00
• The goal of GCSS is to operate in a web-based
  environment with shared data whereby corporate
  information is readily available to authorized
  users regardless of where the needed data is
  located.

12
Why are We Doing IT?

• C4ISP - Certifications
• Mandated by DOD regulation 5000.2-R
• Necessary requirements to ensure systems will be
  fully supportable once handed over to the
  operating community
• Looks at system-to-system interoperability,
  intelligence support, Joint Technical
  Architecture Air Force compliance, security and
  networthiness
• Certificate of Networthiness
• Describes the relative risks associated with
  fielding a networked system or application
• Certificates to Operate (CTOs)
• Single authorization to proceed with installation
  of the application on base networks - MAJCOM
  specific

13
Why are We Doing IT?

• Air Force Portal
• What is it?
• A gateway or major starting web site
• A web-based front-end to corporate information no
  matter where it resides
• Benefits
• Common interface and access point
• Provide targeted content to specific users
• Access to structured and unstructured data
• Why do we need it?
• Operational need
• Functional Users access to the information
  required to accomplish their mission
• Decision makers need the information now!
• Provides a catalyst for eliminating duplicate
  systems
• When will we have it?
• CSAF/SECAF 3 Jan 01 memo
• move all unclassified applications to the
  Air Force portal by 1 Jul 01
• How will we access it?

14
Who is Doing IT?
System Integration
15
Who is Doing IT?

• ACES Automation Steering Group (ASG)
• AF/ILE-2 Chairs with MAJCOM representation
• Provides strategic direction
• ACES Configuration Control Board (CCB)
• AFCESA/CEO chairs with MAJCOM representation
• Technical arm of the ASG
• Provides configuration management of Civil
  Engineering standard systems
• ACES Environmental Integrated Process Team (IPT)
• AFMC/CEVO Chairs with MAJCOM representation
• Functional working group representing the Civil
  Engineering community
• Defines system requirements

16
Who is Doing IT?

• Base, MAJCOM, and AF/ILEV representatives formed
  groups to models the business process of every
  environmental program
• Everything evolves around the business process
• The act of doing something with something
• Define boundaries (starting and ending points)
• Describe where to collect data

17
Who is Doing IT?
Management Organization
18
When are We Doing IT?
Development/Deployment
19
When are We Doing IT?
Schedule
20
How Do We Define Requirements?
21
How Do We Define Requirements?
System/Software Process Flow
SRR/SDR
Requirements Definition
Project Startup
Design and Development (Build)
System Acceptance
Project Startup
System Requirements Analysis
System Design
Software Requirements Analysis
Software Design
CSCI/HWCI Integ Test
CSCI Quality Test
Unit Integrate Test
SW Implement Unit Test
System Qualification Test
IEM Standard Process Flow
Customer

• System Req. Review
• SW Specification
• Review

• System Req.
• Contract

• SW Design Review

• Test Readiness
• Review

• System Acceptance

• Approved SW Req.
• Approved Sys. Design

• Agreement to Proceed

• Accepted Test Plans,
• Procedures

System Engineering

• System Req. Analysis
• Allocation (1.2.1)
• System Design (1.2.2)

• System Engineering
• Mgmt. Plans (1.1)

• Eng. Dev.
• Plans (1.2)

• SW Req. Analysis Allocation (1.2.1)

SW Eng. Development

• Implement (1.2.3)

• Unit/Component
• Test (1.2.4)

• Integrate SW Components 1.2.5)

• Qualify Software (1.2.6)

• SW Design (1.2.2)

• Maintain Dev.
• Files (1.1.17)

• Maintain Dev.
• Files (1.1.17)

• Maintain Dev.
• Files (1.1.17)

System Integration Test

• Acceptance Test
• Plan (1.2.8)

• Develop Acceptance
• Procedures (1.2.8)

• Integrate
• System
• (1.2.5)

• Acceptance
• Test (1.2.8)

Baseline Management

• Product
• Baseline
• System
• PCA/FCA

• SW Design Baseline (1.1.7)

• SW
• PCA/FCA

• Software Baseline

Project/Engineering Management (1.1) Risk
Management (1.1.13) Mgmt. And Technical Reviews
(1.1.10, 1.1.11) Subcontract Management (1.1.18)
Requirements Management (1.1.12) Configuration
and Data Mgmt. (1.1.14) Quality Assurance
(1.1.15) S/SEPG (1.1.1) Training (1.1.19)
22
How Do We Define Requirements?

• Process Flow
• Suppliers-Input-Process-Output-Customers (SIPOC)

Controls (PPE, Engineering)
CUSTOMERS
SUPPLIERS
Process/Activity
Outputs (Pest management)
Inputs (Materials)
Mechanism (People/Equipment)
23
How Do We Define Requirements?

• Pest Management Process Flow

24
How Do We Define Requirements?

• IPMIS functionality
• Contract tracking
• Pest Management Plan Tracking
• Inventory Management
• Etc.
• Military-unique pest control situations
• Vegetation control on missile silos
• Communications sites
• Ranges

25
How Do We Define Requirements?

• EESOH-MIS Capabilities
• Shop Management
• Planning
• Recording
• Reporting
• Barcode/Labeling
• Handheld Devices
• GeoBase
• Building and building layouts available so
  controllers could document exact treated area

26
(No Transcript)
27
(No Transcript)
28
(No Transcript)
29
(No Transcript)
30
(No Transcript)
31
(No Transcript)
32
(No Transcript)
33
Issue?

• Business Modernization Management Program (BMMP)
• This program is chartered to
• Transform and modernize business processes across
  DoD
• Standardize and integrate processes enabled by
  technology and systems
• Capitalize on DoD strengths and infuse leading
  practices into DoD operations

34
Issue?
The Vision The Department of Defense will be
managed in an efficient, business-like manner in
which accurate, reliable, and timely financial
information, affirmed by clean audit opinions, is
available on a routine basis to support informed
decision-making at all levels throughout the
department. Secretary of Defense Donald
Rumsfeld
DoD Domain Areas
Logistics
Acquisition/Procurement
Installations and Environment
Human Resource Management
Finance,Accounting Operations Financial
Management
Strategic Planning Budgeting
Technical Infrastructure

• Fewer spent on business processes and systems
  more available for the war fighting mission
• Men and women in uniform have what they need when
  they need it
• Congress is told, with confidence, where are
  being spent in DoD

35
Issue?

• Business Modernization Management Program (BMMP)
• Development of an enterprise architecture - A
  list of business, technical and systems
  requirements
• End-to-end business scenarios - Functional
  business process validation
• A transition plan - Lays out the key high level
  tasks which must be accomplished to implement the
  architecture
• Activities, business rules and requirements in
  the architecture have been grouped by business
  area, or domain
• Domain leaders will lead the transformation

36
Issue?

• Transition Plan toTo-Be Environment

37
Conclusions

• Integrated, corporate, Management Information
  System
• AF GCSS IF as the hosting agency
• All test and implementation personnel must obtain
  their own password for https//my.af.mil
• Phased development/deployment of 18 applications
• Phase 1 will be completed by May 04
• Phase 2 begin in FY04
• Pest Management application in early stages
  Requirements identification
• Get Involved
• Think outside the box
• Process centric from materials centric

38
Questions and comments
Alan T. Waite HQ USAF/ILEVQ [phone],
DSN 327-0192 Fax [phone], DSN
664-1812 email alan.waite_at_pentagon.af.mil
39

• Material Centric
• 1 Shop 1 NSN 1Process 1 Authorization
• Complete AF Form 3952
• ID Shop - Corrosion Control Shop
• ID Material
• Define task - remove corrosion from aluminum
  alloy
• T.O. 1-1-691 para E14.2
• Engineering controls - none
• PPE
• Waste streams - industrial waste treatment plant
• ESOH Review and Approval

40

• Material Centric
• 1 Shop 1 Process 1 (or More) NSNs 1
  Authorization
• Complete AF Form 3952
• Id Shop - Corrosion Control Shop
• Define task - remove corrosion from aluminum
  alloy
• Id Material(s)
• T.O. 1-1-691 para E14.2
• Engineering controls - none
• PPE
• Waste streams - industrial waste treatment plant
• ESOH Review and Approval