1 / 23

Agenda

Automated Health and Morale System (AHAMS) Charleston AFB, SC Air Mobility Command (AMC) 29-31 January 2008. Agenda. Welcome Introductions What is AHAMS? AHAMS Project Overview AHAMS Installation Schedule Charleston AFB, SC (AMC) Site Survey Questions System Requirements. Introductions.

wylie-avery
Download Presentation

Agenda

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Automated Health and Morale System (AHAMS)Charleston AFB, SCAir Mobility Command (AMC)29-31 January 2008

  2. Agenda • Welcome • Introductions • What is AHAMS? • AHAMS Project Overview • AHAMS Installation Schedule • Charleston AFB, SC (AMC) Site Survey • Questions • System Requirements

  3. Introductions • CITS PMO • Stephen Garwood – Primary & Alternate Task Monitor • Dan Sprague – Lead Engineer • AFCA • Terry Diurba - AF Telecommunications Systems Manager • Telos - Overall NetCents Program Management • Jim Morehouse – NetCents Program Manager • Andy Johnson – Deputy NetCents Program Manager

  4. Introductions • Unique Communications - Technology Provider/Subject Matter Experts/Vendor Training • Keith Arthur – Installation Engineer • EDS - Overall Project Management / Installation Team Members • Robin Mathias – AHAMS Project Manager • Paul Estrada – Installation Team Lead • Danny Guerrero – Installation Engineer • Kris Johnson – Installation Engineer • Josh Holbrook – Installation Engineer • Curtis Lewis – Installation Engineer

  5. What is AHAMS?

  6. AHAMS • Automated Health and Morale System • Automated Health, Morale & Welfare (HMW) calling services that emulates highly reliable manual attendant services, enforce Department of Defense (DoD) and Air Force policies and provide performance monitoring • System offers management controls to throttle services in times of national emergency or crisis • Provides automated control of the time of calls within a frequency (i.e. 15 minutes per week) • Phase 1 stand alone morale call authentication Morale Minder Unit (MMU) with localized support • Phase 2 transitions each MMU into an enterprise system with centralized support at the CITS helpdesk at Gunter AFB

  7. AHAMS Architecture

  8. AHAMS MMU System

  9. AHAMS MMU System

  10. AHAMS Project Overview

  11. AHAMS Installation Schedule • Charleston AFB, SC AHAMS Install • Tuesday 29 January 2008 • 0900 – 1000 AHAMS FSE In-Brief • 1000 – 1200 MMU Hardware Installation • 1200 – 1300 Lunch • 1300 – 1600 MMU Software Installation • Wednesday 30 January 2008 • 0800 – 1200 Operational Procedures • 1200 – 1300 Lunch • 1300 – 1600 Testing and Documentation • Thursday 31 January 2008 • 0800 – 1200 AHAMS Acceptance, Sign off, and Training • 1200 – 1300 Lunch • 1300 – 1500 Training • 1500 – 1600 AHAMS FSE Out-Brief

  12. Charleston AFB (AMC) Site Survey

  13. Patrick AFB (AFSPC) FSE Site Survey • Site Survey Data (Received 14 Nov 07) • Defense Data Network (DDN) Building 129 • MMU Rack Mounted • Two single phase power outlets • 12 DID / 12 DOD lines • MSgt Kenny Johnson, Designated AHAMS Support

  14. Questions

  15. Thank you for your assistance.

  16. System Requirements Review

  17. System Requirements A = Analysis, I = Inspection, D = Demonstration, T = Test, O = Observation

  18. System Requirements A = Analysis, I = Inspection, D = Demonstration, T = Test, O = Observation

  19. System Requirements A = Analysis, I = Inspection, D = Demonstration, T = Test, O = Observation

  20. System Requirements A = Analysis, I = Inspection, D = Demonstration, T = Test, O = Observation

  21. System Requirements A = Analysis, I = Inspection, D = Demonstration, T = Test, O = Observation

  22. System Requirements A = Analysis, I = Inspection, D = Demonstration, T = Test, O = Observation

  23. System Requirements A = Analysis, I = Inspection, D = Demonstration, T = Test, O = Observation

More Related