Your SlideShare is downloading. ×
Industry Briefing
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Industry Briefing

3,637
views

Published on

Published in: Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
3,637
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Updated
  • Transcript

    • 1. June 1-2, 2005 Headquarters Information Technology and Communications Division (HITCD) Industry Briefing National Aeronautics and Space Administration (NASA) Headquarters Washington, D.C.
    • 2. Introduction
      • OBJECTIVE: Provide potential contractors with an in-depth understanding of the NASA Headquarters (HQ) Information Technology (IT) environment
      • Industry Briefing (two days) – Presentations
        • HQ IT and Communications Division
        • Customers
      • Site Visit (one day) – Tour of facilities
    • 3.
      • The briefing will describe the HQ:
        • Organization, customer base and IT environment
        • IT architecture, services and operations
        • On-going and planned initiatives
        • Information Technology and Systems Engineering Management (ISEM) and Outsourcing Desktop Initiative for NASA (ODIN) contracts
      Briefing Contents
    • 4.
      • Each presentation topic will be followed by a question and answer period for clarification
      • Each session will be video taped
        • Copies of the video will be provided upon request
      • This briefing is posted on the Headquarters Information Technology Support Services (HITSS) web site:
      • http://www.hq.nasa.gov/isem2
      Briefing Approach
    • 5.
      • Restaurant, convenience store, and sandwich shop located at east (far) end of building on 1st floor
      • Restrooms are available just outside this auditorium on the right
      • Please observe EXIT signs in the event of an emergency
      Briefing Logistics
    • 6. Agenda – Day 1 8:30 - 8:45 Registration 8:45 - 8:50 Briefing Objective, Approach 3 - 8 and Logistics 8:50 - 9:45 General Overview 9 - 47 9:45 - 10:00 Contract Descriptions 48 - 58 10:00 - 10:55 Information Technology (IT) 59 - 87 Architecture 10:55 - 11:10 Break 11:10 - 11:45 Operations 88 - 103 11:45 - 11:55 Telecommunications 104 - 114 Architecture 11:55 - 1:00 Lunch 1:00 - 2:45 Customer Service 116 - 178 2:45 - 3:00 Break 3:00 - 3:45 Information Technology 179 - 206 Security 3:45 - 4:30 Application & Web Development 208 - 240
    • 7. Agenda – Day 2
      • 8:30 - 10:30 ISEM Task Order Details 241 - 292
      • 10:30 - 11:45 Questions
      • 11:45 - 1:00 Lunch
      • 1:00 - 4:00 Customer Presentations
      • 4:00 - 4:15 Site Visit Plan 294 - 302
      • 4:15 - 4:30 HQs Facilities 303 - 307
    • 8.
      • 8:00 - 8:30 Badging
      • 8:30 - 9:00 HQ Daily Tag-Up Meeting
      • 9:00 - 9:45 Configuration Control Board Meeting
      • 9:45 - 10:00 Break
      • 10:00 - 12:00 Tour of Facilities
      Agenda – Day 3
    • 9. General Overview Sandra Daniels-Gibson
    • 10.
      • General Description
      • HQ Organizations
      • NASA Chief Information Officer Function
      • HQ Chief Information Officer Function
      • HQ IT Environment
      • HQ IT Governance
      • IT Strategic and Tactical Planning
      • HQ IT Initiatives
      • NASA HQ IT Challenges
      • What is Required of HITSS Contractor
      General Overview Topics
    • 11.
      • HQ provides planning, advocacy, budgeting, direction, external liaison and coordination in support of NASA’s mission
      • HQ is comprised of 5 executive and staff Offices, 4 Mission Directorates and 16 Mission Support Offices
        • Mission Directorates have distinct technical and program responsibilities (e.g. Space Operations)
        • Mission Support Offices support NASA at large (e.g. Institutions and Management)
      • Total Civil Servants ~ 1785
      • Total Contractors ~ 300
      • Numerous contracts and service providers support the HQ environment
        • Utilities, facilities, security, health, IT services, Integrated Financial Management Program (IFMP), etc.
      General Description
    • 12. HQ Organization
    • 13. Office of Institutions and Management OFFICE OF THE ASSOCIATE ADMINISTRATOR FOR INSTITUTIONS AND MANAGEMENT NASA Shared Services Center Institutional Planning And Investment Office Of Infrastructure And Administration Office Of Human Capital Management Office Of Diversity And Equal Opportunity Office Of Security And Program Protection Office Of Procurement Office Of Small And Disadvantaged Business Utilization
    • 14. Office of Infrastructure and Administration Management Systems Division – John Werner Logistics Management Division – Jeffrey Parker Facilities Engineering & Real Property Division – Eugene Hubbard Environmental Management Division – James Leatherwood Aircraft Management Division – Joseph Walker EO & Diversity Management Division – Al Castillo (Act.) Information Tech. & Communications Division – Sandra Gibson HQ Facilities & Admin. Services Division- Judith Jackson (Act.) Career Management Division – Victoria Thorne Human Resources Management Division – Leah Hollander LD000 LD010 LD020 LD040 LD030 LD050 LD060 LD070 LD080 LD090 LD100 4/26/05 Office of the Assistant Administrator Assistant Administrator - Jeffrey Sutton Deputy Assistant Administrator – Olga Dominguez Deputy Assistant Administrator for HQ Operations (Vacant) Deputy Director for HQ Operations – Chris Jedrey Special Assistant – James Frelk Peer Review
    • 15. Information Technology and Communications Division DIRECTOR/HEADQUARTERS CIO -IRM Program -CIO Representatives Board -HQ IT Board of Directors -Customer Advisory Committee (CAC) Chair Sandra Daniels-Gibson Program and Administrative Support CHIEF, OPERATIONS and ENGINEERING BRANCH Lester Newell COMPUTER CENTER OPERATIONS -Servers (PC, Mac, UNIX) and Mid-Range Computers -Internet Services -Front end processors and local mainframe peripherals -Interface to NACC for Mainframe Operations DATA COMMUNICATIONS OPERATIONS -Network Operations Center -Headquarters Communications Network -Building-Wide Communication Network TELECOMMUNICATIONS OPERATIONS -Telephones, Pages, and Voice Mail -ViTS -VOTS -Satellite/Cable TV -Wide Area Network coordination -NISN coordination IT ENGINEERING SERVICES -Systems Engineering Facility -Turnkey Systems -Engineering Analyses -Agency and Special Projects -Email Postmaster PRINTING and DESIGN Graphics support Copying and GPO riders ISEM CONTRACT -Contract Administration/Task Order Mgmt. CHIEF, SECURITY and INFORMATION SYSTEMS BRANCH Roger Bullock CHIEF, CUSTOMER SERVICES BRANCH Noah Nason SOFTWARE APPLICATIONS SERVICES -Custom Software -GOTS/COTS -Data Base Administration -Internet Publishing -Headquarters Webmaster -Interface to NACC for Mainframe Applications IT PLANS and POLICY -IT Plans, Policy and Regulatory Reviews IT SECURITY -IT Security Program -IT Security Manager-Policy / Technical -Risk Assessments and Security Plans -Contingency Plan -IT Security Training CUSTOMER SERVICES -Service Managers -Desktop HW and SW Management -Accessible Technology -URC -Help Desk -Laptop and PDA Loaner Pools -Desktop Management --Training IT EQUIPMENT MANAGEMENT and MAINTENANCE -Inventory Control -Maintenance Management -Property and Life Cycle Management -Equipment Relocations ODIN Delivery Order -Contracting Officer’s Technical Representative FINANCIAL ANALYSIS -Institutional IT Budget and Funding -IRM Budget Preparation and Execution -Contract Financial Management
    • 16. NASA Chief Information Officer (CIO) Function
      • NASA CIO – Ms. Pat Dunnington
        • Provides Agency wide IT policy, direction and oversight
        • Establishes Agency IT standards and architecture
        • Responsible for Agency wide IT Initiatives
        • Serves as liaison with federal oversight agencies
        • Chairs the NASA CIO Representatives Board
    • 17. HQ Chief Information Officer (CIO) Function
      • HQ CIO – Ms. Sandra Daniels-Gibson
        • Works in close coordination with NASA and Center CIOs to assist in establishing Agency wide IT policy, standards and architecture
        • Works in close coordination with NASA and Center CIOs to assist in planning and carrying out Agency wide and Federal government IT policy and initiatives
        • Responsible for implementation of NASA CIO IT policy and standards at the HQ site
        • Establishes the HQ Enterprise Architecture in accordance with the NASA Enterprise architecture
        • Responsible for implementation of NASA CIO IT initiatives at HQ
        • Serves on the NASA CIO Representatives Board
    • 18. Profile of Current IT Environment
      • Outsourcing Desktop Initiative for NASA (ODIN)
        • Total Desktop / Laptop Computers: ~2385
          • Customer Base: ~2085
            • Includes civil servants and contractors
          • Shared use seats: ~300
            • For Systems Engineering Facility (SEF), training, conference rooms, etc.
          • Percentage distribution by operating system:
            • 78% PC
            • 21% Macintosh
            • 1% Unix
        • Supported by ODIN Central Help Desk in Madison, Alabama
    • 19. Profile of Current IT Environment
      • Information Technology Systems, Engineering and Management (ISEM) support services contract
        • Walk-In Service Center (User Resource Center)
        • Mainframe processing services provided by the NASA ADP Consolidation Center (NACC) at MSFC
        • Network Operations Center (NOC)
        • Server Operations Center (SOC)
        • Systems Engineering Facility (SEF)
        • Video Teleconferencing System (ViTS) facilities
    • 20. ISEM
      • Purpose: Provides comprehensive IT services across NASA HQ
      • Type: Cost Plus Award Fee
      • Term: June 1, 2000 – November 30, 2005 (includes one 6-month extension)
      • Contractor: Science Applications International Corporation - SAIC
      • Total FTE: ~252
      • Major Contract Elements
        • Core tasks support the operation of the overall NASA HQ. Work supports many or all Organizations
        • Optional subtasks support a specific project, program or organization
      • Contract Management
        • Contracting Officer (CO) – Mike Alexander
        • CO’s Technical Representative (COTR) – Les Newell
        • Task Managers for Core and optional subtasks
      • Contract interfaces with many other HQ services contracts
    • 21. HQ Information Technology (IT) Services Summary
      • ISEM
      • Headquarters Offices services
      • Policy and Program Review and Planning
      • Application and web site development and sustaining engineering
      • Tactical plan, special tasks and studies support
      • Acquisition support
      • Server hardware / software maintenance and management
      • Telecom budget and billing and VITS support
      • IT security services
      • System and network engineering and integration services
      • NACC and NASA HQ Computer Center (NHCC) operations support
      • Telephone (including cellular) operations and support
      • Wireless PDA support
      • ODIN
      • Desktop maintenance
      • Desktop hardware /software maintenance and management
      • Help Desk services
    • 22.
      • 1999 2005
      • Annual IT costs $29.5 M $42.0 M
      • IT Contractor support personnel ~ 296 ~ 252
      • IT support civil servants in the HQ Information 21 22 Technology and Communications Division
      • Servers ~ 87 ~150
      • Customer base ~ 1400 ~ 2085
      • Number of Offices supported 20 25
      IT Environment - Past and Present
      • 1994 –1998
      • IT Consolidation Initiative
      • Explosive growth in use of IT
      • High levels of technology infusion
      • 1999-2005
      • Extensive collaboration across NASA
      • Integrated Financial Management Program
      • E-Gov – unified Federal IT strategies
      • Web services
      • Wireless Networking
      • Increase in customer base
    • 23. 2005 State of IT Environment
      • Centralized management of IT under one organization
      • Experiencing a sharp growth in customer base and supported activities
        • Moving people to offsite locations
      • Support high-visibility teams (e.g. Recent: Columbia Accident Investigation Board (CAIB), President’s Commission on Space Exploration, Return-To-Flight)
      • New NASA Exploration goals, One NASA vision, Transformation
      • IT architecture is in transition and evolving:
        • Migrating servers to achieve load-balancing and fail-over
        • Migrating NT file storage architecture to a centralized storage
        • Migrating switches from 100MB to gigE
        • Implementing more capability into Personal Digital Assistants (PDAs)
        • Building redundancy and high availability into Network Perimeter
        • Enhancing wireless networks
        • Enhancing Information Technology Security (ITS)
        • Greater integration of email, calendars, Instant Messaging (IM), directories (HEMI)
        • Increasing integration for E-Gov and the President’s Management Agenda
      • Supported by a central help desk with onsite level-II help desk / customer service representatives
      • Close working relationships among HITCD, customers, and ISEM and ODIN contractors
    • 24. 2005 State of IT Desktop Environment
      • PC computers:
        • Standard PCs have Windows XP and Office 2003
        • Macintosh computers
          • All OS10.3.4 or greater
        • Email/calendaring environment is being upgraded. Currently using:
          • Outlook 2003 / Entourage
          • Meeting Maker 7.5 (To be retired)
        • Support for:
          • Blackberrys
          • Palms
          • Treos
          • Pocket PCs
    • 25. NASA IT INITIATIVES Office of Management and Budget (OMB) Other Federal Agencies Agency Level Committees HQ Information Technology and Communications Division Agency CIO
    • 26. Customer Interactions Customers Information Technology Point-of-Contact (IT POC) ODIN Customer Outreach Advocates (COAs) ISEM Customer Project Managers (ICPMs) HITCD Service Managers HITCD ADP/T Board of Directors Customer Advisory Committee (CAC) IT Technical Advisory Group (ITAG)
    • 27. Supporting Organizations
      • ADP/T Board of Directors
        • Provides strategic and executive guidance to the Information Technology and Communications Division, in its role of meeting the IT requirements of HQ program and staff offices
        • http://www.hq.nasa.gov/office/codec/codeci/activiti/itcomm.htm
      • Customer Advisory Committee
        • Identifies common and unique HQ IT requirements, influences solutions in support of the overall HQ mission, and provides inputs and recommendations to the Information Technology and Communications Division and the ADP/T Board of Directors
        • http://www.hq.nasa.gov/office/codec/codeci/activiti/cac.html
      • Information Technology Technical Advisory Group (ITAG)
        • Provides input from a very technical group of individuals who give a programmatic perspective on the IT capabilities needed at Headquarters to facilitate their work efforts on behalf of NASA
    • 28. IT Coordination Mechanism
    • 29. IT Coordination Mechanism
    • 30. IT Strategic and Tactical Planning
      • 5-Year Strategic Plan, dovetails with Agency Strategic Plan
        • Safety and security
        • Cost effective common infrastructure and services
        • Innovative technology and practices
        • Emerging IT areas of support
      • 2-Year Tactical Plan that establishes HQ IT goals and objectives
        • General narrative of overall direction
        • Activity descriptions
          • What / Why / Benefits / How / When / Cost
      • Basis for customer expectations
      • Approval and status worked with ADP/T Board of Directors
    • 31. Major CY04/05 Projects
    • 32. Report Card FY04 1/16/2004 1/19/2004 100% Closed Server upgrade 2003 0002555 1/16/2004 1/16/2004 100% Closed Deploy CAIB Database 2003 0002815 1/9/2004 1/9/2004 100% Closed Production Nextel 6510 BlackBerry 2003 0002796 12/22/2003 12/22/2003 100% Closed Direct Print for ISEM Staff in HQ 2003 0002765 12/22/2003 12/22/2003 100% Closed Video Broadcasting Capability in EO 2003 0002813 12/19/2003 12/19/2003 100% Closed modify email assistant 2003 0002880 12/18/2003 1/31/2004 100% Closed International Blackberry Capabiliti 2003 0002887 12/5/2003 12/5/2003 100% Closed Support CAIB 2003 0002618 12/3/2003 12/3/2003 100% Closed Upgrade ISS Scanner 2003 0002732 11/24/2003 12/3/2003 100% Closed BlackBerry Attachment Pilot 2003 0002717 11/24/2003 8/31/2004 100% Closed Calendar/Email Messaging on BlackBe 2003 0002695 11/4/2003 11/7/2003 100% Closed Bullet Proof Computer Security 2003 0002812 10/30/2003 10/13/2003 100% Closed upgrade sendmail 2003 0002467 10/29/2003 11/1/2003 100% Closed Support for Apple Power Mac G5 2003 0002791 10/24/2003 10/24/2003 100% Closed Recommend E-mail virus filter 2003 0002666 10/22/2003 10/30/2003 100% Closed Direct Printing for Windows Desktop 2003 0002691 10/21/2003 10/31/2003 100% Closed European Blackberry 2003 0002793 10/17/2003 10/17/2003 100% Closed Engineer BB6210 2003 0002803 10/16/2003 9/19/2003 100% Closed ECP: Meeting Maker Upgrade 2003 0002734 10/3/2003 10/3/2003 100% Closed Official Mac OS10 pilot 2003 0002537 10/1/2003 9/25/2003 100% Closed Bring pilot DHCP into production st 2002 0002328 Actual ECD Approved ECD % Complete Status SR Title SR#
    • 33. Report Card FY04 5/26/2004 5/28/2004 100% Closed Implement Patch Link 2003 0002888 5/25/2004 5/31/2004 100% Closed Support for Code AO G5 2003 0002811 5/21/2004 5/21/2004 100% Closed Research Shared MS Project Capabili 2004 0003051 5/14/2004 5/16/2004 100% Closed LANIER Scanner Capabilities 2004 0003044 5/14/2004 7/30/2004 100% Closed Integration of 7200 Series Blackber 2004 0003024 5/10/2004 5/14/2004 100% Closed Auto Update for Code M Majordomo Li 2004 0003043 5/7/2004 6/9/2004 100% Closed Convert current Palm to Tungsten Pa 2004 0003099 5/7/2004 5/7/2004 100% Complete Upgrade Meeting Maker 2003 0002879 4/29/2004 4/30/2004 100% Closed VPN connection to GSFC Building 25 2004 0003055 4/23/2004 2/27/2004 100% Closed Design new E-mail architecture 2002 0002195 4/15/2004 4/15/2004 100% Closed Wireless Recommendation 2004 0003000 4/15/2004 12/31/2004 100% Closed Support the Agency ePresence initia 2003 0002652 4/9/2004 4/2/2004 100% Closed ECP: Institutional MAC Refresh 2004 0002962 4/2/2004 4/2/2004 100% Closed Approval & certify Jabber IM client 2004 0002949 3/19/2004 3/23/2004 100% Closed IE as default HQ Web Browser 2003 0002726 3/15/2004 3/15/2004 100% Closed Implement netOctopus for Macs 2003 0002828 2/27/2004 2/29/2004 100% Closed ECP: PDA Future 2003 0002788 2/26/2004 2/27/2004 100% Closed Blackberry Enhancement Roadmap 2003 0002907 2/20/2004 2/20/2004 100% Closed Evaluate Phase II for New Horse 2003 0002831 1/31/2004 1/31/2004 100% Closed Upgrade FAX SR Server 2003 0002897 1/23/2004 5/30/2004 100% Closed ECP: Implement Direct Print 2004 0002955 Actual ECD Approved ECD % Complete Status SR Title SR#
    • 34. Report Card FY04 8/5/2004 8/5/2004 100% Closed Add ACE Replica w/ RADIUS to Privat 2003 0002619 8/4/2004 8/11/2004 100% Closed Implement Anti-Virus/Anti SPAM for 2004 0002973 8/2/2004 8/3/2004 100% Closed HA Solution Deployment 2004 0003227 7/30/2004 7/30/2004 100% Closed Conference room connectivity 2004 0003184 7/27/2004 8/30/2004 100% Closed Wireless Card Standard 2004 0003092 7/13/2004 5/31/2004 100% Closed Recommend web based email client 2003 0002540 7/7/2004 6/18/2004 100% Closed ECP: Storage consolidation 2004 0003020 7/7/2004 6/18/2004 100% Closed ECP: Windows NT upgrade 2004 0003018 7/1/2004 8/20/2004 100% Closed Evalaute Apache for use at HQ 2004 0003128 6/30/2004 6/30/2004 100% Closed Early MAC OS X Deployment 2004 0003102 6/18/2004 6/18/2004 100% Closed ECP: HA for Windows 2000 servers 2004 0003022 6/18/2004 6/18/2004 100% Closed ECP: HA solution for SUN servers 2004 0003021 6/18/2004 6/18/2004 100% Closed ECP: Upgrade SUN Solaris OS 2004 0003019 6/3/2004 1/30/2004 100% Closed ECP: Upgrade Eudora clients 2003 0002727 5/31/2004 5/31/2004 100% Closed Pilot PKI Support for BlackBerry 2003 0002766 5/31/2004 5/31/2004 100% Closed HQ Desktop FAX solution 2004 0002970 5/31/2004 5/31/2004 100% Closed Network Datastore 2003 0002533 5/28/2004 5/28/2004 100% Complete Implement Enterprise Refresh - Maci 2004 0002996 5/28/2004 5/31/2004 100% Closed Resolve SNA performance issues 2003 0002747 5/28/2004 5/31/2004 100% Closed emergency Prepardeness 2003 0002637 5/26/2004 6/9/2004 100% Closed Support review of CENS 2004 0003119 Actual ECD Approved ECD % Complete Status SR Title SR#
    • 35. Report Card FY04 9/13/2004 9/13/2004 100% Closed Implement USDA CENS on Windows 2004 0003141 9/13/2004 9/13/2004 100% Closed New Horse Deployment 2004 0003228 9/13/2004 9/15/2004 100% Closed Production Plan for HIRT 2004 0003225 9/9/2004 9/10/2004 100% Complete Implement Lanier Printers 2004 0003034 9/9/2004 9/10/2004 100% Closed Implement Direct Print 2004 0003054 8/31/2004 9/20/2004 100% Closed Install Mac OS X Update 10.3.4 2004 0003261 8/31/2004 8/31/2004 100% Closed MS XP and Office 2003 2004 0003009 8/30/2004 8/30/2004 100% Closed Webmail solution for Newhorse 2004 0003256 8/30/2004 9/1/2004 100% Closed Remote system security verify produ 2004 0003210 8/16/2004 8/16/2004 100% Closed Secure IP Printing 2003 0002861 8/11/2004 8/31/2004 100% Closed SMS 1.2 to netOctopus Migration 2004 0003167 8/9/2004 9/15/2004 100% Closed 7750 Blackberry 2004 0003204 8/6/2004 7/30/2004 100% Closed Provide Tungsten-E Palm Triage 1 Su 2004 0003202 Actual ECD Approved ECD % Complete Status SR Title SR#
    • 36. Report Card FY05 2/15/2005 2/15/2005 100% Closed Two Factor Authentication for Netwo 2004 0003497 2/15/2005 2/15/2005 100% Closed Automated PW Reset 2004 0003477 2/14/2005 2/14/2005 100% Closed Apple Xserve technical evaluation 2005 0003538 2/8/2005 2/8/2005 100% Closed File System Integrity Solution 2004 0003404 1/21/2005 4/22/2005 99% Suspense NASA HQ Directory Updates 2004 0003462 1/21/2005 2/8/2005 100% Closed Develop an ECP: Direct Print Web to 2004 0003491 1/14/2005 1/18/2005 100% Closed AT&T Treo/Pocket PC Pilot 2004 0003216 1/10/2005 1/10/2005 100% Closed PatchLink Server Deployment 2004 0003374 1/7/2005 1/7/2005 100% Closed Windows Server Remote Access Soluti 2004 0003437 1/3/2005 5/31/2005 100% Closed Support for IBM ThinkPad T40p 2003 0002696 12/3/2004 12/3/2004 100% Closed OS X workstation/AD interoperabilit 2004 0003330 11/30/2004 11/17/2004 100% Closed Integrate the Mac OS X Server platf 2004 0003329 11/23/2004 11/26/2004 100% Closed CMATS Pilot Server 2004 0003294 10/29/2004 10/30/2004 100% Closed Windows XP SP2 2004 0003319 10/29/2004 10/30/2004 100% Closed Evaluate server access control tool 2004 0003303 10/28/2004 10/28/2004 100% Closed Replace public search engine 2004 0003334 10/28/2004 10/28/2004 100% Closed ECP HQ VPN Service 2004 0003101 10/22/2004 10/22/2004 100% Closed Evaluate Mac-Blackberry sync softwa 2004 0003328 10/15/2004 10/15/2004 100% Closed netOctopus Mac Script Repository 2004 0003286 10/6/2004 10/6/2004 100% Closed Webalizer production system 2004 0002953 10/5/2004 10/15/2004 100% Closed Exchange Proof of Concept 2004 0003116 Actual ECD Approved ECD % Complete Status SR Title SR#
    • 37. Report Card FY05   5/31/2005 90% Sched HIRT Production Deployment 2004 0003353   5/31/2005 90% Sched HIRT Pilot Support 2004 0003352   5/30/2005 100% Sched Mac Mini Evaluation 2005 0003648   5/20/2005 75% Sched Upgrade PatchLink 2004 0003411 5/9/2005 5/9/2005 100% Sched 1800 M Street 2004 0003412   2/21/2005 0% Suspense Evaluate & Recommend an RFID soluti 2004 0003494   11/2/2004 0% Suspense Move Web tool to production 2004 0003305 5/9/2005 5/9/2005 100% Complete Upgrade Brio On-Demand Server 2005 0003602 4/6/2005 3/25/2005 100% Closed Develop ECP for the CENS JAVA versi 2005 0003620 4/6/2005 4/12/2005 100% Closed ECP: Upgrade SNA Infrastructure 2005 0003603 4/4/2005 4/4/2005 100% Closed SOC iAgenda Server 2005 0003615 4/4/2005 4/4/2005 100% Closed Facility Server Upgrade 2004 0003466 3/31/2005 3/31/2005 100% Closed Evaluate and recommend an HTTP prox 2004 0003517 3/31/2005 3/31/2005 100% Closed HQ Wireless Network 2004 0003254 3/31/2005 3/31/2005 100% Closed Upgrade PKI software, Entrust 2004 0003136 3/28/2005 3/28/2005 100% Closed Alternate access WiFi proof of conc 2004 0003492 3/24/2005 3/24/2005 100% Closed Cisco VPN Client Upgrade to Triage 2004 0003484 3/15/2005 3/16/2005 100% Complete ECP: Implement Lanier Scanning Serv 2005 0003539 3/1/2005 3/1/2005 100% Closed Move all testing systems 2003 0002580 2/28/2005 2/28/2005 100% Closed Data Backup for Desktop 2004 0003478 2/25/2005 2/25/2005 100% Closed Conduct 802.1x Pilot 2004 0003448 Actual ECD Approved ECD % Complete Status SR Title SR#
    • 38. Report Card FY05   TBD 0% Suspense Recommend & Implement Endpoint Secu 2004 0003447   TBD 5% Sched Upgrade WLSE 2005 0003712   TBD 50% Sched Create a web site for the Wireless 2005 0003647   TBD 5% Sched Configure 802.11 for Pocket PC devi 2005 0003727   TBD 5% Sched Commercial Guest Network 2005 0003729   7/29/2005 5% Sched Update SNA and FAQ links and docume 2005 0003752   7/14/2005 25% Sched Implement an NetApp Enterprise Stor 2005 0003578   6/30/2005 20% Sched Printing Solution for ASAL Labels 2005 0003730   5/31/2005 0% Suspense 802.1x Pilot 2005 0003662   5/31/2005 80% Sched Implement an Enterprise backup solu 2005 0003579   5/31/2005 80% Sched NHCC Server Upgrades 2005 0003577   5/31/2005 10% Sched Conduct Desktop Backup pilots 2005 0003674 Actual ECD Approved ECD % Complete Status SR Title SR#
    • 39. Current Agency CIO IT Initiatives
      • Wide area network replacement
      • Agency wide messaging initiative
      • InsideNASA portal (Agency intranet)
      • NASA Enterprise Architecture
      • NIST ITS compliance
      • Uniform ITS monitoring, mitigation and reporting
      • Public web “branding” and consolidation
      • Consolidated Oracle licenses
      • NASA Integrated Services Environment (NISE)
        • NASA Account Management System (NAMS)
        • Cyber Identity Management System (CIMS)
        • Badge and smart card integration (CBACS)
      • Homeland Security Presidential Directive 12
        • Identity and Account Management
    • 40. Current HQ IT Initiatives
      • Get to everything from anywhere -
        • Expanded “guest” services - Internet in conference areas, offices
        • Improved remote access to HQ resources
      • Staying current
        • Upgrade server infrastructure - Jump Start, load balanced
      • Continuing improvements to safe work environment
        • SPAM and Virus filters – different levels of filters
        • ITS monitoring and controls - Patchlink, penetration tests, and intrusion detection
    • 41. Current HQ IT Initiatives
      • Emergency Preparedness
        • Fail-over and hot sites
      • Storage and Backup Systems Upgrade
      • Customer Tools
        • Headquarters Enterprise Messaging Initiative (HEMI)
        • Wireless handheld device enhancements - attachments, office integration
        • Secure wireless - high-speed building-wide / laptop and PDA client deployments
      • “ One call does it all”
        • Eliminate need for customer to initiate follow-up actions once Help Desk has been called
      High Availability and Responsive Service are our goals
    • 42.
      • Automatic desktop backups and searchable storage
      • Desktop Video Conferencing integrated with VoIP
      • Complete building-wide roaming capability
      • “Pull” refresh in addition to “Push”
      • Expanded use of Take-Home software
        • Personal firewalls
      Future HQ IT Initiatives
    • 43. NASA HQ IT Challenges
      • Maintain customer satisfaction in the HQ corporate environment
      • Accomplish IT initiatives within budget constraints
      • Achieve success in light of the following customer environment:
        • Highly dynamic (new programs and initiatives – One NASA, CIO actions, Return-to-Flight, Moon/Mars exploration, NASA Transformation, E-Gov)
        • Heavy reliance on IT environment
        • High expectations of customer base
        • Very senior and knowledgeable staff
        • Diverse desktop hardware and software environment
      • Keep pace with demand for new IT devices and capabilities:
        • PDAs
        • Wireless
        • Group collaboration
    • 44. NASA HQ IT Challenges
      • Mitigate ever increasing IT security vulnerabilities
      • Minimize customer impact due to contract transition
      • Proactively anticipate and support HQ programmatic needs
      • Developing and maintaining simplified customer processes and procedures for IT services
      • Delivering a large volume of effective customer outreach and training within a time-constrained environment.
    • 45. What is Required of HITSS Contractor
      • Very strong customer service orientation
      • Strong technical skills
      • Ability to deliver high quality service:
        • Responsive
        • Flexible
        • On time
        • Seamless support
        • Close coordination - no surprises
    • 46. What is Required of HITSS Contractor
      • Ability to deliver in a highly dynamic environment
      • Adherence to HQ and NASA IT Policy and Procedures
      • Comprehensive compliance with all NASA security policies, Federal policies, NIST guidance and prompt mitigation of security threats
      • Forward thinking, quick learners:
        • Knowledgeable of environment
        • Evaluate and recommend technology and service improvements beneficial to HQ customer base
      • Operate safely
      • Deliver as promised
    • 47. Questions and Answers
    • 48. Contract Descriptions Les Newell
    • 49.
      • Tactical plan, special tasks and studies support
      • Acquisition and property management support
      • Application / website development and sustaining engineering
      • System and network engineering and integration services
      • Telecom budget, billing and ViTS support
      • Computer center operations support
      • Provide customer, equipment maintenance and logistics services
      • Provide IT security services
      • Provide IT services to Headquarters Offices
      HQ ISEM Services Summary
    • 50. Current ISEM Contract Scope
      • The ISEM contract is divided into two main support areas
        • “ Common Core tasks” are performed for all of the offices at NASA HQ
        • “ Optional tasks” are performed for specific offices having unique requirements
    • 51. Common ISEM Core Tasks
      • Program Management
      • Computer Center Operations
      • Communications Systems and Services
      • Software Applications Development and Maintenance
      • Customer Services
      • Information Technology Security
      • Special Tasks
    • 52. Optional ISEM Tasks
      • Optional tasks span the full spectrum of information technology expertise:
        • Web site development and maintenance
        • IFMP implementation
        • Architecture and engineering analyses for the agency CIO
        • Information technology strategic and tactical planning
        • Information technology technical support to program offices
        • Office of Inspector General Nationwide Information System
        • Corrective Action Tracking System support
        • ISO 9000 systems support
    • 53. ODIN Description
      • The ODIN contract provides the Hardware/Software installation, maintenance and technology refresh of:
        • Desktops
        • Printers
        • Facsimile
      • Customer support
      • ODIN products and services catalog
    • 54. Other HQ Non-IT Contracts
    • 55. Current Contractor Descriptions
    • 56. Current Contractor Descriptions
    • 57. Current Contractor Descriptions
    • 58. Questions and Answers
    • 59. IT Architecture Sam Ramos
    • 60. IT Architecture Topics
      • Architecture and Design Philosophy
      • Procedures, Policies, and Practices
      • Architecture Overview
      • File Service
      • Printing Environment
      • Remote Services
      • Email Service - HEMI
      • Blackberry Service
      • Web Architecture, Processes and Policies
      • Systems Engineering Facility
    • 61. Architecture and Design Philosophy
      • Staying agile to respond to new requirements
        • Largely Open Standards based
          • Reduces costs, easy to scale, simple integration, easy maintenance and multiple security options
          • Simplified design
      • Our service expectation is High Availability
        • Routers and DNS should ALWAYS be up
        • Remote access (dial-in/SSL), email, and Web services should ALWAYS be available
          • Plans underway to extend this philosophy to data and databases
    • 62. Architecture and Design Philosophy
      • Two thirds of our servers are Unix based
        • Better security, management, performance, flexibility
        • Using Sun “Jump Start” for automatic configuration
        • Migrating to standard Blades and enterprise Network Attached Storage (NAS) and Storage Area Network (SAN)
      • One third of our servers are Microsoft based
        • Migrating from Windows NT / 2000 to Server 2003
      • Desktop configurations should be as generic as possible
        • Simple configurations are easier to test, thereby facilitating faster “core” rollouts
        • Customers have local administrator privileges
    • 63. Procedures, Policies, and Practices
      • Change Control is critical
        • Configuration Control Board reviews:
          • System Requirements Review (SRR)
          • Preliminary Design Review (PDR)
          • Critical Design Review (CDR)
          • Test Readiness Review (TRR)
          • Operational Readiness Review (ORR)
        • Change packages, Version Description Documents
        • NOC manages IP address database
    • 64. Procedures, Policies, and Practices
      • No clear text reusable passwords for system administrators
        • Hardware tokens are required to administer switches and routers
          • Must log on as themselves before acquiring private access
        • Must use Secure Shell (SSH) for remote administration of Unix hosts, Switches and Routers
        • Remote admin access is NOT allowed for Microsoft-based servers
    • 65. Procedures, Policies, and Practices
      • Firewalls and Perimeter:
        • Firewall Rule Sets and Router Access Control Lists (ACLs) are structured to support required services
          • HQ Private Network permits general outbound access and denies inbound connection attempts
          • HQ Public Network permits approved services to approved host and denies all unapproved services inbound and outbound
          • HQ Perimeter Network restricts access as defined by host requirements
        • HQ Perimeter blocks insane addresses, source routing, NetBios, Internet Control Message Protocol (ICMP), inbound SSH, RFC 1918, private addresses, etc.
      • Networks are compartmentalized according to requirement and security
    • 66. Architecture Overview Office of Security and Protection (OC-3) HA Firewall Cluster
    • 67. Architecture Overview
      • Edge networks
        • Networks located outside the HQ security perimeter
        • Typically servers/devices managed and/or supported by non-HQ organizations:
          • Some visibility and coordination with HQ NOC
        • Includes
          • NASA Integrated Services Network (NISN)
          • The Office of Inspector General (OIG) network
          • Office of Security and Program Protection connection to the NASA Secure Network (NSN)
          • Guest network
    • 68. Architecture Overview
      • Public Services Network
        • Tightly controlled access to HQ services provided to the public
        • Default is “deny” for outside sources wanting to get in
        • Default is “deny” for inside services connecting out
        • Default is “deny” from Public to Private
        • All in and out ports are defined for each server
        • Secure location for services provided to NASA Centers and/or the general public
          • CCB approved and HQ monitored and maintained
    • 69. Architecture Overview
      • Perimeter networks
        • Located behind the border router and in front of the core firewalls
        • Provides support for
          • Services that require public access but do not work well behind firewalls (e.g. Real Audio servers and servers that require dynamic ranges of TCP/UDP ports)
          • Servers that are not managed by HQ personnel and are thus not trusted
          • Desktop workstations that are not managed under HQ configuration management (CM) control
          • Off-site contractor networks
        • Provides limited “first line of defense” protections
          • Blocks weakly protected services such as file sharing
          • Blocks known attacks such as “Ping of Death” and address spoofing
    • 70. Architecture Overview
      • Private Services Network
        • Services protected by core firewall
        • Default is “deny” for all outside sources wanting to get in
        • Default is “allow” for all inside sources wanting to get out
        • Provides protected services to desktop workstations and services that are not available to other Centers or the general public
    • 71. Architecture Overview
      • Network and Server Operations Center (NOC / SOC)
        • NOC manages firewalls, routers, switches and security perimeter
          • Responsible for IP management
        • SOC manages servers
          • Responsible for service performance, availability, and accounts
        • Serves as a resource for trouble-shooting and analysis
        • Sends alerts, alarms and pages when anomalies are detected
        • Uses tools for monitoring server and network operations
        • Provide visibility into each device and down to each node
        • Monitors infrastructure, nodes, servers, CPU usage, I/O utilization, broadcast traffic, switches/routers and configuration changes
    • 72. Architecture Overview
      • Paging
        • Pages from the HELP desk are human driven
          • Pages are sent for critical tickets.
        • Pages from system alerts
          • Pages are sent from HP OpenView via analog phone line.
          • Pages from service alerts are sent via Skytel
        • Web site for use by IT staff to do their own single or group snap page
    • 73. Architecture Overview
      • Network Infrastructure
        • Three communication closets on each floor with Cisco 6509/6506
          • Each Catalyst switch has two, 1 Gb, multi-mode fiber cable runs that take separate, redundant paths to alternating center closet switches and then to the Concourse and NHCC switches
            • Each center closet floor switch has two, 1 Gb, multi-mode fiber trunks. The primary is attached to the NHCC switch (root bridge) and the backup is connected to Concourse Center
            • Each wing closet (East and West) has two, 1 Gb, multi-mode fiber trunks. The primary is attached to the center closet switch for that floor. The backup is attached to the wing closet switch in the floor above and below
          • Cable is Cat 5 with 100MB Network Interface Cards (NICs) installed in all desktop computers
    • 74. Architecture Overview
      • Workstation Interface Outlet (WIO) boxes
        • WIO distribution boxes are embedded in the raised floors to provide network and phone connections to customer workstations
          • Each WIO box contains at least six outlet positions
            • 2 CatE @ 100 Mb - RJ45
            • 1 voice - RJ45, 1 modem/fax - RJ11
            • CATV- coax, 1 spare
          • Additional analog data lines are issued on an exception basis for faxing “outbound only”
          • Electric power has separate floor boxes
    • 75. Architecture Overview
    • 76. File Service Today
      • Centralized Windows 2000 and 2003-based file and print architecture:
        • Promotes easier sharing of data
      • Server architecture:
        • File Services - Hosted on 3 Dell 6350s attached to a Dell SAN
          • 1.9 TB
          • Data #4 Dell 6400 - array = 887 GB
          • Data #5 Dell 6600 - array = 1.3 TB
        • 5 Print Servers - Hosted on 2 Dell 2450s, 1 Dell 6400
          • FAX hosted on a Dell 1300
        • SMS - Dell 6300
    • 77. File Service Tomorrow
      • Microsoft 2003 server
      • Limited Active Directory
      • Flexible NAS
      • Centralized Backup
    • 78.
      • How it works:
        • Customers submit print jobs using JetDirect, IPP, or Appletalk directly to the printers
        • Printers print what they are told
        • Printers accept concurrent connections, print on first-come, first-served basis
        • Legacy print server for special case printers or printers with specific access requirements (e.g. only specific customers can print to it, job size limits)
      • Benefits:
        • No single points of failure between customers and most printers
        • Customers can access full functionality of the printers (e.g. scanners on Laniers)
        • Printing is much faster without intermediate spooling
        • Customers retain control of jobs until they are completely printed
        • Customers have direct visibility into printer state
        • Much less hardware to maintain and manage
      Current Printing Environment Print Servers Core Firewall
    • 79. Remote Services
      • Around the clock service
      • Supports personnel on travel and telecommuters
        • Peer-to-peer access to desktop systems and Point-to-Point Tunneling Protocol (PPTP) are not allowed
      • Dial-in and Kiosks (SSL) both use SecurID hardware tokens
      • Services like email and calendaring are available over the general Internet and do not require HQ addresses
      • Dial-in Service:
        • Cisco AS5300 dial-in servers
        • There are 4 T1s, each T1 supports 23 concurrent connections for a total of 92 possible connections
        • 1-800 and local numbers - pre-setup on laptops
    • 80.
      • Secure Remote Access
        • Enables Kiosk style access via SSL
        • Can support up to 100 concurrent customers
        • Accesses web applications, and SAMBA to files
        • “ Profiles” set up for customers
      Remote Services
    • 81. Email Service - HEMI
      • A tightly integrated messaging service that supports NASA HQ users with local account administration and tier 2 support, with servers and services provided by NDC@JSC and NDC@MSFC
      • Headquarters Enterprise Messaging Initiative- fully operational late June 2005
        • Phase 1 (Email) – 99% complete
          • Replace Eudora email with Outlook/Entourage
          • Enhanced Blackberry support
          • Goodlink support for TREOS and Pocket PCs
          • Enhanced Agency Wide Directory
          • Instant Messaging
          • File sharing & collaboration via SharePoint
        • Phase 2 (Calendaring)– late June 2005
          • Replace Meeting Maker calendaring with Outlook/Entourage calendaring
    • 82. Email Service - HEMI
      • An MOU between HQ, NDC@JSC and NDC@MSFC will provide Service and Performance Levels
      • ISEM provides account administration, engineering design and operations, project management, some triage 2 Help Desk
      • ISEM is working with the Agency CTO under a task order, to engineer and implement an Agency wide rollout of a common messaging platform. This will build on the HEMI foundation.
    • 83. Blackberry Service
      • Today
        • > 500 units deployed
          • 957, 6510, 6710, 6750, 6210
          • Verizon, Cingular and AT&T
          • Email and Attachments
      • Tomorrow
        • Reduce device models
        • Pursue better integrated solutions
    • 84. Web Architecture, Processes and Policies
      • Web sites and applications comply with all NASA HQ web hosting architectures, processes and policies
        • Architecture
          • SunOne Web Server, J2EE Application Server, Cold Fusion MX, Oracle 9i
          • Several browsers supported – IE 6 for PCs, Firefox 1.0, and Safari (OSX) for Macs
        • Process
          • Full life-cycle milestone review via HQ Configuration Control Board
        • Policies
          • All federal web publishing guidelines (Section 508, COPPA, etc.)
          • NASA specific publishing guidelines
            • See http://webwork.nasa.gov/policy for more details
    • 85. Systems Engineering Facility
      • The Systems Engineering Facility (SEF)
        • Self-contained facility
        • Simulates production environment for safe testing
        • Provides expertise to assist with testing efforts in the field of computing and data communications
        • Contains a wide array of computer and network technology for testing production scenarios outside the production environment
      • Includes capability to:
        • Test all production desktop computing platforms
        • Test current and planned operating system distributions
        • Test all current NASA HQ software
        • Test on the NASA HQ network, or on one or more private networks
        • Isolate network monitoring and analysis
    • 86. Systems Engineering Facility
      • The SEF contains:
        • Workstations and server-class computers
        • NASA HQ "core" desktop software configurations
        • Network-attached printers for PCs and Macs
        • Personal digital assistants
        • Cisco routers, switches, firewalls
        • Ghost Servers where ALL the Core loads are kept
    • 87. Break
    • 88. Operations Marta Goldblatt Sam Ramos
    • 89. Operations Topics
      • Operations Description
      • Server Operations Center (SOC)
      • Networks Operations Center (NOC)
      • Production Control
      • Backup Operations
      • Service Availability
      • HQ ISEM Platforms / Applications
      • NACC Applications Overview
    • 90. Operations Description
      • Operations is responsible for availability, reliability, and uninterrupted service of all hardware and software housed in the NHCC. This includes:
        • Operating systems and attendant software installation, customization, and maintenance
        • Disk and tape administration
        • Resources Management and optimization
        • Problem resolution
        • Capacity planning
        • Production control
        • Online and batch systems maintenance
        • Print job distribution
    • 91. Server Operations Center (SOC)
      • Systems Administrators of NHCC platforms perform
        • Systems monitoring
        • Systems maintenance and upgrades
        • Backup certification
        • Problem resolution
      • The SOC staff assists in the:
        • Build out and installation of new servers
        • Installation of applications software on production servers
        • Elimination of system vulnerabilities and in managing the detection of viruses via the automatic protection software, and reporting these incidents
      • The SOC is closely integrated with the HQ Local Area Network Operations Center (LANOC) and the HELP desk
    • 92. Network Operations Center (NOC)
      • The NOC manages the Headquarters Communications Network (HCN) through pro-active monitoring of HQ IT infrastructure, including:
        • Nodes
        • Servers
        • Central Processing Unit (CPU) usage
        • Input / Output (I/O) utilization
        • Broadcast traffic
        • Switches / Router Service Modules (RSMs)
        • Configuration changes
      • The NOC detects some anomalies automatically and sends alerts to the NOC staff and other involved personnel
    • 93. Production Control
      • Provides coverage for mainframe printers and related equipment
        • Set up jobs and manage output
        • Monitor and manage production schedules
        • Control and operate peripheral equipment
        • Operate high speed printers
      • Develop operational schedules
      • Coordinate customer requirements
      • Report and escalate problems to the NACC
    • 94. Backup Operations
      • Backups to tape start after 6:00 pm.
        • Daily (Incremental) kept for 2 weeks
        • Weekly (full) - kept for 6 months
        • Monthly (full) - stored off-site for one year
      • Restorations from tape as required
      • Logs are generally maintained for 30 days
      • Implementation of a Centralized Backup System is in progress
    • 95. Service Availability
      • All aspects of customer and institutional network connectivity is available 24 x 7 unless otherwise specified due to scheduled, or unforeseen outages
    • 96. NACC – HQSYSB Connection CNT-NACC Comm/CNT- HQ Network IBM 9672 HQSYSB LPAR DASD Tape silo Printers Redundant T-1 circuits IP replaced SNA TN3270 terminal connections as of Aug.2004
    • 97. NACC IBM Architecture Serving Headquarters - HQSYSB Amdahl replaced with an IBM CMOS mainframe.
    • 98. HQ NACC Configuration Overview
      • NACC LPAR = Hqsysb
      • Platform
        • IBM 9672-RB6
        • 2048 RAM/LPAR
        • OS/390 Z/OS v1.4
      • Environment
        • 2 64bit CPU’S of 10
        • 165 MIPS
      • DASD
        • 87 volumes @ 6.8gb per vol.
        • Approx: 591gb
        • Used: 115.27 GB as of May 2,2005
        • V2X disk and controller platform (fiber channel between the lpar’s)
      • Security
        • RACF 1.3b as of Jan. 2001
    • 99. HQ IBM System Configuration Overview
      • Communications / Controllers
        • CNT-NAU-AO (NHCC)
        • CNT-XAU-60 and 68 ( 68 shared ) (NACC)
        • IBM 3708 communications controller (NACC)
        • IBM 3172-3 terminal controller (NACC)
    • 100. Headquarters NHCC Configuration Overview
      • Printers
        • Xerox, DP65 NHCC
        • Stk 5280 -Prt1, Prt3 (Will be retired in July) NHCC
      • Network Connection Modes
        • TCP/IP
      • Shared Environment
        • IBM 9672-RB6
    • 101. HQ LPAR Prime Processing Averages
      • Average Time Sharing Option (TSO), interactive sessions per day: 50
      • 85% of TSO transactions are completed in < 1sec.
      • Average Prime Time Customer Information Control System (CICS) transaction count is approx: 500 daily
      • Average number of batch jobs is 500 per month
    • 102. HQ NACC Applications Overview
      • NACC LPAR Applications:
        • ASAL: Administrative Services Address Labeling
        • AWCS: Agency-Wide Coding Structure
        • CCI: Closeout Contractor Interface
        • FAAD: Federal Assistance Award Data System
        • FACT: Financial and Contractual Status (FACS), Tables Maintenance System
        • FAST: Financial Accounting System Teleprocessing
        • FPDS: Federal Data Procurement System
        • GLAS: General Ledger Accounting System
        • NPMS: NASA Procurement Management System
        • STADS: SAP Time and Labor System
        • UMIS: University Management Information System
    • 103. Questions and Answers
    • 104. Telecommunications Architecture Mike Barrett
    • 105. Telephone Service Overview
      • Telephone service at HQ is via a CENTREX system provided by Verizon through the Washington Integrated Telephone System (WITS) contract with General Services Administration (GSA)
      • There are about 2375 ISDN phones lines and 845 analog lines
      • There are also in use about 250 pagers and 400 cell phones and > 500 Blackberries
      • Voice mail service is provided by an Octel Overture 250 voice mail system, which is completely integrated via a 3A Translator with the ISDN desktop telephone service
      • An ‘800’ telephone number is used for accessing the voice mail system when customers are on travel
      • NASA provides phone service to Contractors
    • 106. New VoIP Service
      • HQ also provides telephone service from HQ to 1800 M Street via Voice over Internet Protocol (VoIP)
      • VoIP service is provided via a Cisco Unity switch and a Cisco Call Manager. There are about 180 customers on this system
      • Plans call for the VoIP system to be installed Headquarters-wide during the next several months
    • 107. Television Service Overview
      • The HQ building is wired for distribution of cable television
      • Each floor has a single CATV leg with 10 tap boxes placed along the length of the building. Each tap box has a capacity of 20 cable drops
      • Where CATV service is desired (e.g. in conference areas) a coaxial cable is run from the WIO box to the nearest available tap
      • A local Contractor (Washington Cable) provides Cable TV service via microwave
      • It is distributed to the NASA television production area
      • Local programming is mixed with the CATV service and re-broadcast throughout the HQ wiring plant
      • High Definition (HD) antenna on roof with direct cable to Space Operations Center (SOC) to provide HDTV signal to the plasma screens
    • 108. Video Teleconferencing System
      • NASA HQ has two formal video conferencing rooms and equipment supported by the NISN contract
      • Several conference rooms are capable of supporting ViTS via portable equipment
      • Several Offices have small TCP/IP based Tandberg units
        • Scheduling is customer driven though MSFC
      • MCI provides the video conferencing service
      • The Contractor provides set-up, scheduling, coordination, conference monitoring, troubleshooting, customer support, etc.
    • 109. HQ Communication Closet Description
      • The HQ building is comprised of nine floors plus a concourse (basement) level
      • Each floor, including the concourse, has three large wiring closets with separate air conditioning
      • Distribution boxes (referred to as Workstation Interface Outlet (WIO) boxes) are embedded in the floor to provide connectivity to customer workstations
      • All outlets are wired with four pair, Category 5 cable that runs from the WIO to a RJ-45 distribution panel wall mounted in the nearest wiring closet
    • 110. HQ Communication Closet Description
      • In addition to the Category 5 twisted pair cable, each floor has multi-mode fiber-optic cable run to the WIO boxes which in general, is not used
      • All communication closets have one NT1 power rack interface for the ISDN 2B1Q multipoint phone lines and telephone models
      • Each NT1 is wired to feed 110 customer workstations
    • 111. 1800 M street Communication Closet Description
      • The 1800 M Street building is comprised of one floor (6th)
      • There are two telecommunications closets a “North and South side” linked together by 100 pairs of CAT5 Copper cable and 12 strand Multimode fiber
      • These 2 telecommunications closets supply 220 terminated jack locations. Each jacked location provides 2 CAT6 terminated cables
      • Each telecommunications closet contains a Cisco 6000 series switch and Call Manager that supply network and telephone services to each jacked location
    • 112. 1800 M Street Communication Closet Description
      • The Cisco switches provide Power over Ethernet so there is no need for Power Bricks to provide power to the telephones at the customer location
      • A Cisco Unity server resides in the “South” Telecommunications closet. This server provides Voice Mail to the 1800 M Street customers
      • There is a DS3, and a Transparent LAN Service (TLS) Circuit that runs between 1800 M Street and NASA HQ at 300 E Street SW. These 2 circuits provide the bandwidth connections between both buildings. These circuits are terminated in the “South” closet at 1800 M Street
      • The TLS Circuit is the main pipe and the DS3 is for Backup should the TLS fail
    • 113. 1800 M Street Communication Closet Description
      • There are 4 PRI circuits located at 1800 M Street terminated in the “South” Closet. These are the main VERIZON circuits to the outside world. Should these circuits fail they have been programmed with Route Advance that will fail over to the NASA HQ 300 E Street location
      • The NASA HQ location has 1 Primary Rate Interface (PRI) set up to provide fail over for the 1800 M street location
    • 114. Questions and Answers
    • 115. Lunch
    • 116. Customer Service Noah Nason
    • 117. Topics
      • Customer Services Overview
      • Customer Services Functional Structure
      • End customer Support
        • Service Requests (SRs)
        • Help Desk (Tickets)
        • Desktop
      • Work Control
      • Asset and Baseline Management
      • Special and Other Services
      • Account Administration
      • Standard Meetings and Customer Outreach
      • Standard Meetings
      • Continual Improvement
      • Summary
    • 118. Customer Services Overview
      • The HQ Information Technology and Communications Division (HITCD) provides customer services to all HQ organizations and individual customers, such as:
        • Requirements analysis and acquisition support
        • Computer training and consultation services
        • Customer outreach
        • Desktop, laptop, printer, and PDA planning and deployment
        • Desktop commercial-off-the-shelf (COTS) product planning and selection
    • 119. Customer Services Overview
      • The HITCD provides customer services to all HQ organizations and individual customers, such as (cont):
        • Customer Service management
        • Work station hardware and software asset management
        • Management and tracking of all desktop services work via a work control system
        • Contract surveillance for ODIN and ISEM
        • Provides ODIN DOCOTR and ISEM Infrastructure Task Manager
        • Customer’s “Ombudsman” for problem resolution
        • Trouble ticket and SR monitoring and issue resolution
    • 120. Customer Services Functional Structure
      • Customer Outreach Advocates
      • Service Ordering Vehicles
        • Service Requests
        • HELP Desk
      • Problem Resolution/Escalation
      • Desktop Response Team
      • Consultations
      • New Customers, Moves and
      • Relocations
      • Virus Detection and Eradication
      • Asset/Baseline Management
      • Quality Assurance
      • Account Administration
      • Computer Training
      • Customer Outreach
      • Web Streaming
      • Voice Over IP
      • Wireless Networking
      • Video Teleconferencing
      End customer Support Special Services Customer Services...
    • 121. Service Delivery Process
    • 122. ISEM Customer Project Managers
      • ISEM Customer Project Managers (ICPMs) ensure customer care across all Information Technology and Communications Division IT services:
        • Serve as customer advocate and liaison
        • Serve as focal point for cross-functional support activities
        • Gather and document requirements and coordinate with IT POC and appropriate manager(s)
        • Track all procurements
        • Assist with tactical plan initiatives and deployments
        • Keep IT POC informed of HQ initiatives and schedules
        • Assist with coordination for all software deployments
    • 123. ISEM Customer Project Managers
      • ISEM Customer Project Managers also provide:
        • Ticket monitoring especially for “on hold” tickets
        • Review of negative customer survey comments with the effected customer
        • Floor walking during critical changes
        • Catalog procurement management
    • 124. Service Ordering Vehicles
      • There are two methods to request IT services at NASA HQ :
        • Service Requests - Examples include:
          • Procurements
          • New initiatives
          • Web site creation and maintenance
          • Studies and White Papers
          • Applications development
        • Help Desk Tickets - Customer calls 358-HELP to request a service or report a problem. Examples include:
          • Problem reports
          • Consultations and questions
          • Service interruption
          • Phone support
          • AV support
          • Applications trouble shooting
          • COTS installation
          • Dial-in and broadband support
    • 125. Service Requests
      • Service Requests
        • Class 1 - Processed through the CCB
          • Affects form, fit or function; procurements above IT infrastructure and product suite
        • Class 2
          • Standard service request not supported by a call-in service, e.g.: new customer requests, procurements within baseline
        • Created and tracked electronically via the IWMS
          • https://polaris.hq.nasa.gov/iwms/iwms_main.cfm
      • Service Request
      421 474 561 503 570 378 388 174 190 340 ISEM 37 77 338 265 200 I/O 1 2 16 23 14 O/I 5 7 33 25 16 ODIN 2004 2003 2002 2001 2000
    • 126. Service Request Form
    • 127. SR Examples
      • Engineering
        • Evaluation and baselining of new hardware or software at NASA HQ (such as the HP8000 printers)
      • Operations
        • Audio/Visual support for a meeting, Voice mail setup (telecom), and installing/upgrading/ removing software from servers
      • Service Management
        • Installation of a new software product across many computers
      • Software Development
        • Custom applications and NASA web sites
    • 128. Service Request Volume - Consolidated View Service Requests Dispositioned
    • 129. Service Request Closure Target: Requests Closed Within 2 Weeks of Completion Includes all ISEM Service Requests
    • 130. Customer Satisfaction Survey Service Requests Target: 98% of all Customer Survey Good or Better Responses
    • 131. HELP Desk
      • HELP Desk - 358-HELP (4357)
        • Core Hours of operation 6:00-6:00 (M-F)
        • After-hours phone support (24/7)
        • Problem resolution, escalation, dispatch
        • Process “Call-in Services”
          • Password resets
          • Software for home
      • Help desk ticket volume
        • October 04 – March 05 monthly avg. = 3817
    • 132. HELP Desk
      • HELP Desk. A centralized service ordering and a problem resolution center for all HQ personnel:
        • Functions as the major point of entry into the service request and problem report (work control) system
        • Receives requests for service via phone, fax, voice mail, e-mail, web-mail
        • Documents all requests for service in the Remedy work control system as status/update as required
        • Monitors all requests including those for non-ODIN Contractors and Government staff
      • Help Desk staff administer and monitor the automated call distribution system (ACD)
      • Maintain ~100 pager notification lists and send pager notifications
        • Priority lists, Department Specific, A/V, operations, etc.
      • Perform password/print queue resets
    • 133. Problem Resolution/Escalation
      • The HELP Desk Analyst:
        • Resolves ~50% of the service requests on the initial call
        • Documents the customer request and priority category:
          • Super Priority
          • Critical Uplift
          • Priority Service
        • Dispatches to the appropriate team/organization, as required
        • Tracks status and provides timely updates to the customer, the support team, other Contractors, and the DOCOTR
      • Dispatched team responds to request within established metrics
    • 134. Problem Resolution/Escalation
      • If the team is unable to provide corrective measures or workaround within 8 hours, the request is escalated to the DOCOTR or his designated representative
      • Cross functional teams may be established, as required, to include:
        • Service Managers, technical support staff, Desktop Response Team, Contractor contacts
      • Critical, Super Priority, and Non-Prime requests require approval before implementation. Pager notification for approvals must include:
        • Ticket Number
        • Name of Requestor
        • Telephone Number of Requestor
        • Summary of problem and why it is a work stoppage
    • 135. ODIN Desktop Response Team
      • Team dispatched via the HELP desk and performs the following services:
        • Responds to HELP desk trouble tickets within established contract metrics and escalates as appropriate
        • Provides troubleshooting and implements corrective action measures, including Returns to Service
        • Contacts customer to provide status updates
        • Provides consultation services
        • Performs virus eradication services
        • Supports IT requirements for conference room and audio visual services
        • Supports Class 1 and Class 2 Service Requests
        • Installs Triage 1, 2, and 3 HW / SW
        • Performs Move/Add/Changes (M/A/C)
    • 136. Customer Work Requests
      • Workflow Process
        • An integrated process used to record, track and maintain status on all customer work requests
        • Ensures accountability, accurate tracking and timely completion of work
          • Metrics are collected to perform trend analyses, determine customer satisfaction, and measure Contractor performance
      • Two systems:
        • ISEM Work Management System (IWMS) (Service Requests (SRs))
        • ODIN’s Remedy Action Request System (Help Desk Tickets)
    • 137. Remedy Action Tracking System
      • Supports the Service Center in the delivery and tracking of customer work requests
      • Functions include:
        • Customer interaction across multiple channels (telephone, fax, email and the web)
        • Customer interaction histories
        • Support agents to deliver personalized and efficient service
        • Work order (tickets) tracking for both ad-hoc and predefined tasks
    • 138.
      • Interacts with:
        • Headquarters ODIN New customers Request System (HONURS)
        • Provance
          • Delete Seats
          • View Seat Configurations and Inventories
      Remedy Action Tracking System
    • 139. Historical Workstation Seat Counts
    • 140.
      • Desktop software library
      • Home use software program
      • Laptop loaner pool
      • Anti-Virus
      • Server software library
      • Wireless PDA loaner pool
      • Anti-Virus
      • User Resource Center (URC)
      • Training center and computer training
      • Electronic forms
      Special and Other Services ODIN ISEM
    • 141. Logistics and Property Management
      • Maintain the NASA Equipment Management Systems (NEMS) for ISEM controlled equipment
      • Interface with GSFC Property Disposal Officer
      • Track all Headquarters Information Technology and Communications Division (HITCD) non-ODIN equipment
      • Wipe media in accordance with HQ procedures, and install baseline operating system prior to retiring the equipment
    • 142.
      • Desktop Software Library
        • Software Library Database that tracks:
          • Desktop Software license inventory
          • Desktop Software licensing agreements (single, site and volume), maintenance renewals, subscription services
          • Receiving and Inspection for desktop software
        • Central repository and storage of COTS and GOTS software media and documentation
        • “Core Load” management and maintenance
        • CD ROM duplication
        • Distribution point for “home use” software
        • Technical Reference Library and software support tools for support teams
        • Software Reuse Pool
      Asset/Baseline Management
    • 143.
      • Server Software Library
        • Primarily manages the purchase of renewals for annual maintenance and support server software
        • Software Library Database that tracks:
          • Server Software license inventory
          • Server Software licensing agreements (single, site and volume), maintenance renewals, subscription services
          • Receiving and Inspection for server software
        • CD ROM duplication
        • Managed on a Call List outside of ODIN Software
        • Technical Reference Library and software support tools for support teams
      Asset/Baseline Management
    • 144.
      • Software management
        • Automated software distribution and inventory (SMS)
          • Software installs/uninstalls
          • Hardware and software inventory collection and reporting
        • SMS Team:
          • Manage deployment schedules
          • Manage configuration of “inventory packages” and “scripts”
          • Perform follow-up activities
      Asset/Baseline Management
    • 145.
      • Software deployment - New and upgrades:
        • Evaluating, testing and scripting in the SEF by desktop engineering
        • Coordinating extended pilots
        • Training and customer information sheets including deltas from previous versions disseminated
        • Deploying packages with Patchlink and netOctopus
      Asset/Baseline Management
    • 146.
      • Baseline management:
        • DRD-ODIN-HQ-12 HW-SW Baseline Product Suite
          • ODIN maintains and updates the Hardware/Software Baseline Product Suite
          • The master document shall be updated monthly and posted to the web
        • DRD-ODIN-HQ-16 Desktop Software Release Plan
          • The ODIN contractor generates, maintains, and submits the plans and reports to track software release planning and execution.
          • Major software releases require CCB approval
          • Minor software releases require a change package
        • ISEM Does:
          • Server software
          • In depth applications testing
        • ODIN Does:
          • Desktop Software
        • Deployment is accomplished using Patchlink, SMS, and netOctopus
      Asset/Baseline Management
    • 147. Catalog Management
      • Must be available for ordering the day of contract start
      • Catalog entries shall be clearly stated in precise and understandable terms that indicate what coverage is included in catalog prices. This includes the Triage 3 disclaimer
      • HITCD will manage catalog ordering and all changes that affect pricing
    • 148.
      • Additions to Catalog – Customer Identifies Need, Contractor refines requirements and works details, COTR approves
      • Delivery Times for Purchases – Within 10 business days. Can have exceptions
      • Category 3 (Triage 3) Disclaimer – Contractor shall be responsible only for delivery and installation of the product
      Catalog Management
    • 149.
      • Hardware Items include:
        • LCD screens, Local Printers, DVD drives, USB Memory drives, etc.
      • Software Items include:
        • Microsoft Project, Adobe Suite, Dreamweaver, etc.
      Catalog Management
    • 150.
      • Software is available with the provision that “this software is required to conduct official business at home”
      • Software loan program is limited to those software applications that are properly licensed
      • Software available via:
        • Download from the software downloads web page
        • Media from the software library
      • Provide very detailed customer guides and installation instructions
      Home Use Software
    • 151.
      • Antivirus software is provided for all desktop computers and is automatically updated as it becomes available from Symantec
      • Antivirus server checks for and downloads updates. Workstations check for and download antivirus updates whenever cold booted
      • During a virus outbreak:
        • Notification of virus threats is made to the HQ customers primarily through two mechanisms:
          • Email notifications and Electronic Information Bulletins
          • Direct Dialog with HQ IT Points-of-Contact
        • Help Desk monitors actions and advises customers
        • Desktop staff are dispatched to mitigate virus infections
        • Network connections to infected computers are closed
        • Create manual scripts for virus filtering on email servers until updated antivirus signatures have been distributed to the desktop
        • Emergency antivirus updates may be pushed to the desktops when they become available
      • Impacts of recent attacks will be covered in Site Visit
      Virus Detection and Eradication
    • 152.
      • Test core load masters and install/uninstall scripts received from desktop engineering
        • Provide feedback to the technical staff re: software testing results
      • Perform desktop pushes using SMS and netOctopus. For the period from Oct 04 to Apr 05:
        • 5296 individual pushes
        • 10 push jobs
        • 1.66 push jobs/month
        • 529.6 individual pushes/job
      • Produce customer documentation and tip sheets
      • Document installation instructions and procedures for home-use software available via the software library and web download
      ODIN Engineering
    • 153.
      • User Resource Center
        • Hours of Operation 7:30-5:00 (M-F)
        • Provides a walk-in technology lab available to all employees and Contractors
        • Contains 3 PC’s, 2 Macs, 1 high speed scanning station, 1 color printer, and 1 guest network connection for laptop computers
        • Services available:
          • Consultations on hardware, software, SecurID tokens and HQ IT policies and procedures
          • Access to above core hardware and software to meet occasional requirements
          • Scanning, CD archive, file conversion and color printing services
          • Account Administration support for New Customers
        • Provides walk in support (Average 85 month)
      User Resource Center (URC)
    • 154. URC Requests by Category
      • Breakdown of URC walk-in requests by category
      October 2004 – March 2005
    • 155. Customer Satisfaction User Resource Center October 2004 – March 2005
    • 156.
      • Provides Desktop Software Training for:
        • Core Applications Software Classes including Microsoft Office Suite, Eudora, MeetingMaker, Dreamweaver, HTML, Flash, etc.
        • Training initiatives for major deployments including Information Technology Exchanges (ITE) and “Brown Bag” Sessions for Windows XP, OS X, and Outlook/Exchange (HEMI Pilot)
        • Custom Applications training including HATS, SNA, OIGATS, HONURS, etc.
        • Miscellaneous topics as PKI Entrust and HQ Infrastructure
      • Provides Deskside Training / One-on-One Training
        • The CTC delivered 287 instances of one-on-one deskside training over a 7 month period. (October 2004- April 2005)
        • These training sessions include: operating systems, desktop software, laptop usage, printing, custom applications, IT orientation, web based training, etc.
      Computer Training Center (CTC)
    • 157.
      • Facilitates Bi-Weekly IT Orientation for New HQ Employees
        • The CTC provides new incoming employees at HQ with a high level orientation to IT services provided at HQ
        • The CTC prepares materials, maintains presentation charts, coordinates rooms and logistics, provides required technology and coordinates with presenters, Human Resources (HR), and ITS
      • Coordinates and Facilitates Additional Training Initiatives at HQ
        • The CTC coordinates training room reservations, security, desktop engineering, network engineering, telecom services, A/V support, and other class requirements given by the sponsoring customer and/or Contractor representative
        • Over this period of performance, some of the training initiatives that the CTC facilitated include: IFMP, Business Warehouse, Budget Formulation, CEP and e-Payroll
      Computer Training Center (CTC)
    • 158.
      • Administers Distance Learning / e-Learning
        • Provides Web Based Training (WBT) classes to customers
        • Orients employees to use the WBT website effectively
        • Provides Demos and Technology Exhibits
      • Maintains Two Full-Time Classrooms
        • Manages the hardware, software, network connections, printer connections and general housekeeping of:
          • 3R55 - 10PCs and 2 Macs, Windows XP and OSX
          • 3R53 – 5PCs and 1 Mac, Windows XP and OSX
      Computer Training Center (CTC)
    • 159. Computer Training Center (CTC)
    • 160. Computer Training Center (CTC)
    • 161. Computer Training Center (CTC)
    • 162. Computer Training Center (CTC)
    • 163. Computer Training Center (CTC)
    • 164.
      • All Government forms required in electronic format (e-forms) and used by HQ employees are available via the HITCD web page:
        • http:// www.hq.nasa.gov/office/codec/codeci/help/forms/forms.htm
      • The ISEM Contractor:
        • Designs new forms and updates and deletes existing forms, as required
        • Maintains, manages, and provides access to ~617 e-forms
        • Provides and updates e-forms in both Informed Filler and Adobe PDF formats
        • Supports Agency access to NASA Forms (NF), Standard Forms (SF) and Optional Forms (OF) forms via the web
        • Generates Agency and HQ monthly reports of forms activity
        • Oversees the periodic update/retirement of all NASA forms
      Electronic Forms Library
    • 165. HONURS and Account Management
      • New Customers Processing
        • Space approvals
        • Initial desktop seat ordering
        • Initial account(s) creation (Form 224)
        • Initial telephone ordering
      • Move Customer Processing
        • Space approvals
      • NASA HQ Automated Systems Standard Access Request (NASA HQ Form 224) Processing
        • Standard account approvals
        • Group/Organization folder approvals
        • Web site administration approvals
        • Application access approvals
    • 166.
      • All customer accounts are managed by ISEM
      • All customer accounts are created through the Headquarters New User Request System (HONURS)
        • Web-based approval process that routes NASA HQ Form 224 (NASA Headquarters Automated Systems Standard Access Request) Requests through the appropriate approval cycle
        • For new customers who do not attend the scheduled orientation training, ODIN desktop services coordinates issuing of new customer IDs and passwords with ISEM account management
      • All customer accounts are maintained in the Headquarters Account Management System (HAMS), a database for audit purposes
        • The HAMS application has standard report templates. These templates give detail information about customers and applications
      Account Administration
    • 167.
      • The customer contacts the Help Desk for all password resets :
        • For NT/Windows Domain passwords, and passwords for HQ unique custom applications (e.g. Outlook & the ACE Database) the Help Desk:
          • Opens tickets
          • Validates customer identity by asking questions provided on NQH Form 252 Account Access Request
          • Resets passwords
        • For passwords not accessible to the Help Desk, such as non-HQ applications, (main frame applications, Employee Express, etc.)
          • Help Desk opens ticket and assigns to Logistics Support
          • Logistics Support contacts customer
          • Logistics Support validates identity of customer by asking questions provided on NHQ 252
          • Logistics Support resets passwords
      Account Administration
    • 168. Account Administration - Future
      • NASA Integrated Services Environment (NISE)
      • Agency-wide initiative
      • An Integrated Services/IT Security Environment that fulfills NASA requirements for –
        • Authoritative Source for NASA Identity Information – IDMS
        • Agency “Directory of Directories” – CIMS
        • User Account Management from request to close - NAMS
    • 169.
      • The Agency will begin to transition to NAMS in Fall 2005
      • NAMS – NASA Account Management System
        • Obtains Authoritative User Identifier Data Through CIMS
        • Establishes Secure, Consistent, Expedient, and Accurate Account Management Processes Across NASA
        • Provides Processes to Manage Accounts for Logical Users
        • Functions Fulfilled by – Sun IdM Workflow and Account Provisioning
      Account Administration - Future
    • 170.
      • The CCB, chaired by the Information Technology and Communications Division (HITCD) Systems Engineering group, provides an open forum for review of new IT requirements
      • The CCB meets each Wednesday at 9:00 am, typically lasting from 30-60 minutes, depending on agenda
      • Permanent CCB membership is comprised of:
        • NASA IT Management
        • ISEM IT Management Roles
        • Other CCB attendees may include both NASA and Contractor personnel
      Configuration Control Board (CCB)
    • 171.
      • Any HQ customer may submit a Service Request (SR) through the normal work control processes
      • New SRS are reviewed daily by the SR Review Team (SRRT) for possible CCB consideration
        • If the SRRT determines that the SR is Class 1 (proposes changes to the form, fit, or function of a production system), then the SR is routed for CCB review
        • Out of board Class 1 SR approvals can be obtained for only:
          • Emergency situations and critical tasks that cannot wait for the normal CCB approval cycle
          • Non-intrusive, standard procedures
        • Class 2 SRs do not require CCB disposition
      Configuration Control Board (CCB)
    • 172.
      • Every Class 1 SR requires a development package for CCB review
        • If the CCB grants approval to proceed, the SR schedule is baselined, and development begins
        • If the CCB disapproves the SR, the work is not done
      • When SR capability is ready for deployment, the CCB conducts an Operational Readiness Review (ORR) to ensure proper deployment
      • Detailed processes and documentation requirements are provided in the Contractor Library
      Configuration Control Board (CCB)
    • 173.
      • Daily Morning Tag-up
        • Meet at 8:30 am for 15-30 minutes, facilitated by ISEM
        • Determines the status of the HQ systems and elevate any issues
        • Screens new SRs, determine status of open actions, review calendar-driven events
      • In-depths Review:
        • Usually occurs mid-month for 1 ½ to 2 hours
        • Date / time to be mutually agreed to
        • Reviews all contract areas and associated metrics
      Standard Meetings
    • 174.
      • Monthly Budget/Expenditure Review:
        • Review the status of contract expenditures vs. plan
        • Monthly meeting, approximately 30 minutes
        • Date / time are mutually agreed to
      Standard Meetings
    • 175.
      • Focus on supplemental training methodologies to further educate the customer community on IT initiatives through:
        • ADP/T Board of Directors
        • Information Technology Technical Advisory Group (ITAG)
        • Customer Advisory Council (CAC)
        • Information Technology Exchanges
        • IT Notices
        • HQ Bulletin articles
        • Brown bag lunches
        • Town Hall meetings
      • Manage and maintain a comprehensive Information Technology and Communications Division web site that encompasses HQ IT services at: http://www.hq.nasa.gov/office/codec/codeci/
      Customer Outreach
    • 176.
      • To accomplish successful customer support for all NASA activities, NASA staff and Contractors are expected to:
        • Evaluate existing processes and modify to improve service delivery and improve customer satisfaction
        • Seek customer feedback and incorporate suggestions into processes, where appropriate
        • Manage change so that it is manageable and expected, and not chaotic and disruptive
      Continual Improvement
    • 177.
      • Timeliness
      • Accuracy
      • Thoroughness
      • Dependability
      • Attention to detail
      • Effective customer outreach
        • Keep customers informed and involved
      • An attitude / outlook that shows the customer:
        • Is always right
        • Should never have to make multiple service calls
        • Should be delighted with service results
      HQ Customer Expectations Require:
    • 178. Questions and Answers
    • 179. Information Technology Security Greg Kerr
    • 180.
      • ITS Program Evolution
      • Plan of Actions and Milestones (POA&M) Requirements
      • ITS Objectives
      • ITS Roles and Responsibilities
      • Information Sensitivity
      • HQ ITS Program Components
      TOPICS
    • 181.
      • NASA ITS Program has undergone major changes to align with recent laws, regulations, and standards
      • Federal Information Systems Management Act (FISMA) requires organizations to align with National Institute of Standards and Technology (NIST) and Federal Information Processing Standards (FIPS) requirements and publications
      • OMB and Congress may withhold IT funding for existing and new projects if ITS requirements are not being met
      ITS Program Evolution
    • 182.
      • NASA is required to report quarterly to OMB on it’s success in completing the following for each IT system:
        • Certification and Accreditation
        • Security control costs integrated into the system life cycle
        • Security controls tested and evaluated annually
        • Contingency Plan creation and annual testing
        • Mitigation of identified vulnerabilities and weaknesses
      POA&M Requirements
    • 183.
      • Ensure ITS safeguards are integrated into all activities supporting NASA’s missions and objectives
      • Ensure the ITS Program covers ALL IT resources, data, and information
      • Ensure IT resources are not exposed to undue risks
      • Ensure each NASA employee understands NASA’s information is a valuable resource which must be protected
      ITS Objectives
    • 184.
      • Agency Management – Establishes policy and provides resources commensurate with importance of ITS
      • Center Management – Create an environment that encourages and enables ITS
      • Customers – Implement ITS practices while performing daily work assignments
      • Center Support – Perform unique functions in support of ITS
      ITS Roles and Responsibilities
    • 185. NASA ITS Organization
    • 186.
      • Develop and maintain an Agency wide ITS Program compliant with Federal laws, regulations, and guidelines
      • Ensure that Federal and NASA security policies, standards, and requirements are effectively incorporated into the life cycle of the Information Resource Management Program
      • Appoint a Deputy CIO for ITS to manage and coordinate the overall direction and structure of the NASA ITS program
      NASA CIO ITS Responsibilities
    • 187.
      • Ensures ITS is appropriately integrated into all IT decisions
      • Ensures IT architectures, standards, best practices, policies, and guidance contribute to secure system operation and protection of data
      • Ensures sufficient resources are budgeted and available for ITS
      • Reports Center ITS information, metrics, and status to Agency CIO
      HQ CIO ITS Responsibilities
    • 188.
      • Responsible for day-to-day implementation of the HQ ITS program
      • Develops HQ ITS policies and guidance
      • Maintains incident response capability
      • Prepares reviews and reports on the status of the HQ ITS program
      HQ ITSM Responsibilities
    • 189.
      • The entire NASA Civil Servant and Contractor population has responsibilities that collectively provide an effective barrier against efforts to compromise systems and information
        • Managers – Assigning IT resources to employees and ensuring resources meet security requirements
        • Systems Administrators – Maintaining technical security configuration of systems
        • Customers –
          • Following security procedures
          • Reporting ITS incidents
          • Completing annual ITS Training
      Individual ITS Responsibilities
    • 190.
      • ALL NASA Information is SENSITIVE to some degree and must be protected
      • Information is categorized according to its impact on Integrity, Availability, and Confidentiality (High/Moderate/Low)
      • Different categories of information require differing protection means and controls in proportion to the risk and impact of loss/damage
      • Some information needs to be protected as mandated by law or regulation
      Information Sensitivity
    • 191.
      • Personnel screening
      • System access control
      • ITS awareness training
      • Risk management
      • Categorization of information and systems
      • Security controls
      • System certification and accreditation
      • Contingency planning, testing and execution
      • Virus detection and eradication (covered earlier)
      • Security monitoring
      • Penetration testing
      • Incident response
      • Remote access
      • Secure communications
      Key Components of HQ ITS Program Both ISEM and ODIN have varying levels of involvement in each component
    • 192.
      • Federal Employees
        • National Agency Check for public trust positions
        • Complete background investigation for National Security Clearance
        • Annual financial disclosure for designated positions
      • Contractor
        • National Agency Check for non-privileged access
        • National and Local Agency Checks and Credit Check for privileged and limited privileged access
      • Foreign Nationals
        • Cannot be granted NASA private network access
        • Must be escorted at all times in the NASA HQ building
        • Access is restricted to Mon – Fri, 7AM – 7PM
      Personnel Screening
    • 193.
      • System Access is granted only after submission and approval of Access Request Form
        • HQ Form 224 identifies the systems and access required by the customer
        • Signed by the customer and approved by the customer’s supervisor
        • Reviewed by ITS for completeness
      • Passwords are valid for 90 days and must comply with NPR 2810.1 Guidelines
      • Password resets are strictly controlled and completed by the HELP Desk only after personal information has been verified
      System Access Control
    • 194.
      • All new civil servants and contractor employees are required to receive ITS Awareness Newcomers Orientation Briefing and complete Annual ITS Training within 30 days of reporting for work
      • All Federal and Contractor personnel with access to NASA information are required to complete ITS Awareness Training annually
      • ITS Awareness Training is delivered through classroom and computer based training
      • Lead Systems Administrators are required to pass certification tests
      ITS Awareness Training
    • 195.
      • Formal NIST SP 800-30 compliant risk assessments are conducted for all systems and applications
      • Security reviews are conducted by the ITS staff as part of the SR review process
      • Agency host vulnerability scans are conducted quarterly for targeted vulnerabilities
      • Host vulnerability scans are conducted periodically at HQ for all known vulnerabilities
      • Additional ad-hoc vulnerability scans may be conducted for critical vulnerabilities
      • All IT storage media is required to be sanitized prior to disposal
      Risk Management
    • 196.
      • FIPS 199 requires managers to categorize information into the appropriate information type to arrive at the recommended impact level for Integrity, Availability and Confidentiality
      • NIST Special Pub (SP) 800-60 defines the information categories and recommends the impact levels for each
      • The identified impact level (High, Moderate, Low) will be used to determine the security requirements and solutions for the system
      • Systems will often have multiple information categories. The security requirements for the most stringent category must be followed unless the system design can permit enforcement of multiple requirements
      Categorization Of Information and Systems
    • 197.
      • The security categorization of information will dictate the NIST SP 800-53 security controls used and the minimum required security settings for a system
      • Security controls are divided into the following categories
        • Management Controls that address the system security management aspects and management of risk
        • Operational Controls that address the security mechanisms implemented and executed by people
        • Technical Controls that address the security mechanisms contained in and executed by the system
      • FISMA requires annual testing and evaluation of the security controls to ensure they continue to be effective
      Security Controls
    • 198.
      • C&A is a formal process designed to make certain that there are adequate security measures in place to protect information residing on NASA IT Systems
      • C&A is applicable to all NASA IT Systems
      • Federal Regulations require C&A to be performed every 3 years or upon a major change affecting the security of a system
      • All systems are reviewed annually to ensure ITS Plans are current and security controls are functioning as expected
      Certification and Accreditation (C&A)
    • 199.
      • NASA HQ has a Contingency Plan that outlines steps to be taken to continue and restore IT operations in the event of a disaster
      • Contingency Plan provides for orderly execution of emergency response, interim operations, and recovery actions
      • Contingency Plan is tested and updated annually
      • Participation is required by the Government and by the ODIN and ISEM Contractors
      Contingency Planning
    • 200.
      • Real-time Monitoring with automated rule sets is used to effectively manage network traffic and ensure security of systems
      • Monitoring is conducted through the use of NISN monitors and analyzes border traffic 24/7
      • Internal monitoring data is collected 24/7 and analyzed by the contractor during normal working hours
      • During incidents and periods of heightened security, contractor staff provides additional analysis and investigation of logs
      Security Monitoring
    • 201.
      • A penetration test is executed in an effort to gain unauthorized or unintended access to network and system resources and information
      • Penetration testing is conducted annually on the internal HQ network systems to determine how well security measures and controls work
      • Third party penetration testing is conducted periodically to validate internal testing effectiveness
      Penetration Testing
    • 202.
      • The contractor and NISN monitor systems and networks for intrusion attempts, unauthorized access, system compromises, and denial of service attacks
      • Customers are trained and encouraged to report all anomalies and unexpected behavior to the Help Desk
      • Customers should forward abusive, threatening, or offensive material to abuse@hq.nasa.gov
      • The contractor, NISN and the Help Desk monitor will conduct preliminary assessments and notify the HQ Computer Emergency Response Team (CERT)
      • HQ CERT will notify NASA Incident Response Center (NASIRC), conduct an investigation and involve the Office of Inspector General (OIG) and Counterintelligence as required by law
      Incident Response
    • 203.
      • Remote Access to the private network is allowed via the Internet and institutional dial-in service
        • Requires prior approval from management and ITS
        • RSA SecurID token is issued for 2 factor user authentication
      • Analog line dial-in is prohibited for networked personal computers
      • Analog line dial-out permitted on an exception basis
        • Documented specific requirement
        • Under strict control
      Remote Access
    • 204.
      • Entrust (PKI) or Pretty Good Privacy (PGP) encryption is required for e-mail transmission of sensitive information
      • Secure Shell (SSH) use is required for remote administration
      • Secure Socket Layer (SSL) encryption is utilized for client communications with non-Public web applications
      • Remote access sessions via the Internet are SSL encrypted
      Secure Communications
    • 205.
      • Expect the NASA HQ ITS staff to independently audit and monitor the entire IT environment on a scheduled and unscheduled basis
      • Expect to be aggressively audited by the OIG
      • Contractor participation is required for all inspections
      • Expect strong external oversight by Congress and the Executive Branch
      Conclusion
    • 206. Questions and Answers
    • 207. Break
    • 208. Applications & Web Development Roger Bullock
    • 209.
      • Applications Development Objectives
      • Custom Application Functional Groupings
      • Application Life Cycle Methodology
      • Application Environments
      • Application Documentation
      • Application Examples
      • Web Development
      • Application Reviews / Reports / Metrics
      • Web Services
      Applications & Web Overview
    • 210.
      • Maintain and support legacy applications
        • Web-based
        • Client-server
        • Mainframe
      • Develop and support New Applications
        • Web-based (standard architecture to the extent practical)
        • Client-server (where absolutely required)
        • Mainframe (only in exceptional situations)
      • Ensure integrity, security and durability of applications functionality
      • Ensure accuracy, timeliness, and security of applications and meta-data
      Applications Development Objectives
    • 211.
      • 138 active applications
        • Majority in sustaining engineering phase
        • Trend towards web-based applications
        • Majority are business applications
        • Scope:
          • Agency-wide
          • Headquarters-wide
          • HQ organizational unit
          • Single customer
      NASA Headquarters Custom Applications
    • 212.
      • Finance, accounting and budget (18)
      • Payroll and personnel (11)
      • Property and procurement (13)
      • General and administrative (96)
      Custom Application Functional Groupings
    • 213. Application Groupings by Architecture 11 2 9 Mainframe 138 47 91 TOTAL 49 9 40 Client/Server 78 36 42 Web App TOTAL 10.x CORE
    • 214.
      • Software used by Headquarters to formulate and execute budgets and operating plans, and perform accounting for Headquarters and the Agency
      • The NASA Integrated Financial Management Program System (IFMP), developed under the auspices of the Chief Financial Officer, continues its implementation to improve the financial, accounting and budget process
      Finance, Accounting and Budget
    • 215. Payroll And Personnel
      • Payroll and Personnel applications include a variety of software that supports HQ and the Agency human resource activities
    • 216. Property And Procurement
      • Property and Procurement applications track NASA Headquarters assets and facilitate the procurement and procurement analysis processes
    • 217. General And Administrative
      • General and Administrative systems provide support for a number of business activities and general office administration
    • 218.
      • Project Initiation
      • Define Requirements (SRR)
      • Design / Prototype (PDR and CDR)
      • Build
      • Test (TRR)
      • Certify
      • Baseline
      • Deploy (ORR)
      • Maintain
      Application Life Cycle Methodology
    • 219. Application Environments Technical Environment
    • 220.
      • Five application categories, “A” through “E”, determine the documentation requirement. Categories are based on:
        • Estimated size of the activity measured in projected personnel assigned and time frame of the development period
        • Number of customers who will actively use the completed system
        • Criticality of the software
        • Complexity of the hardware and software environment
        • Span of operations that considers activities ranging from Agency-wide, HQs-wide, and large-scale systems to small systems developed for a specific organization or individual
      Application Documentation
    • 221.
      • Representative application documentation includes:
        • Project plan
        • Requirements Specifications
        • Design Specification
        • Test Plan and Procedures
        • User and Operations Guide
        • Training Plan and Procedures
        • System Implementation Plan
        • Version Description Document
      Application Documentation
    • 222.
      • Provides detailed information on the active supported applications including websites
      • Provides the following information:
        • Application name and version number
        • Customer organization and organization title
        • POCs: NASA requestor and NASA Contractor analyst
        • Purpose of the application
        • Production hardware and software requirements
        • Languages
      Catalog of Supported Applications
    • 223.
      • Current baselined products for all custom applications developed under the ISEM and predecessor contracts
      • All baselined custom software applications and documentation are stored on the ISEM Contractor’s CM system
      • Archive of closed/cancelled Service Requests generated under the ISEM and predecessor contracts
      • Archives of the ISEM In-depth reviews
      Configuration Management (CM) Library
    • 224.
      • Financial Accounting System, Teleprocessing (FAST): provides on-line update and retrieval of NASA accounting documents
      • Federal Assistance Award Data System (FAAD): tracks NASA grants and cooperative agreements
      Mainframe Applications - Examples
    • 225.
      • Video File Database System (VFDS): contains a description and location of the Office of Public Affairs’ video files
      • Litigation Tracking System (LTS): this is an Agency-wide system used to track and report the status of litigation for the Office of the General Counsel
      • HQ Document Management System (HQDMS): provides HQ organizations with the capability to store archive official documents and provides a COTS client for search capabilities
      Client/Server Applications - Examples
    • 226. Web Applications - Examples
      • Headquarters Action Tracking System (HATS): A tracking system used to manage HQ action items and correspondence. An action is the record of a task to be completed that follows a basic life cycle through as many as six states; open, concurred, submitted, signed, overdue, and closed
      • HQ New User Request System (HONURS): Automates the seat ordering process for new HQ users and the HQ user relocation process
      • Headquarters e-Directory (HQeD): Provides a searchable HQ phonebook for all HQ users
    • 227. HQ Web Applications Standard Architecture Agency-wide Custom Application Internet
    • 228.
      • Develop and maintain internet and intranet based web pages and applications
        • Agency
        • Headquarters
        • Organization/Program/Project specific
      • Develop and maintain processes and tools for customer updating of web pages
      • Evaluate and implement conformance with Agency outsourcing efforts for web hosting
      Web Development Objectives
    • 229.
      • Java/J2EE
      • Cold Fusion MX
      • MS SQL Server
      • Verity Information Server
      • Oracle
      • Macromedia Products
      • XML/XSLT/XHTML
      • Vignette Content Management System
      • iPlanet Web server
      • Apache/Tomcat
      Web Development Tech Environment
    • 230.
      • Static Web Content
      • Agency currently transitioning to fully outsourced web hosting for public web content and Agency intranet content (“portals”)
        • Customers and contract support use a content management system for migrated portal content
        • Non-migrated, locally hosted content is updated via Samba shares and FTP access to internal “mirrored” web server
      Web Development
    • 231.
      • Dynamic Web Content
      • Dynamic content systems follow standard SDLC
        • Technologies used are determined by the project requirements within the baseline architecture (Oracle, Cold Fusion MX, Apache/Tomcat)
        • Full configuration management process engaged and formal milestone review is required
        • Extensive cross-browser testing required and enforced
      Web Development
    • 232.
      • Legacy applications moving to web implementations
      • Transitioning to Web Services Architecture (Apache/Tomcat)
      • Increased use of XML/XHTML for data interchange and display
      • Static content migrating to the Agency portal infrastructure
      • Adoption of formal usability testing methodology
      Web Development Directions
    • 233.
      • Reviews:
        • Weekly Application Managers Meeting
        • Biweekly Applications Review
        • Monthly In-depth Review
      • Reports:
        • Applications Weekly Status Report
        • Applications Monthly Review
      Application Reviews And Reports
    • 234.
      • Milestone Metrics:
        • Completed Service Request Trends
      • Trend Analysis:
        • Release Trend by Software Category
      • Quality
        • Post-TRR / Post-ORR P1 / P2 PRs
      Application Metrics
    • 235. Completed Service Request Trends
    • 236. Post-TRR / Post-ORR P1 / P2 PRs
    • 237. Web Services – Projects
      • Example Projects
        • Recent work includes 25 web sites that were created or existing sites that were redesigned for Headquarters customers
        • 8 Usability studies were performed by the ISEM Certified Usability Analyst on web sites and web applications for Headquarters and Agency programs
        • 11 multimedia projects within the last 12 months included digitizing video for use on the web and in presentations, creation of CD’s to supplement information on web sites, development of DVD’s for use as outreach materials
        • “ As Only NASA Can!” DVD won a 1st Place 2003 Telly Award
    • 238. Web Services - Streaming
      • Headquarters Hosted Streaming Media
      • Headquarters supplies one of three NTV feeds to the Agency portal. However, the portal is not the only customer of streaming media at Headquarters.
        • At peak, approximately 8,000 concurrent streams were sent out for President Bush’s speech
        • Approximately 11,000 streams supported for Opportunity landing
        • Approximately 10,000 streams supported on March 2nd for Science Update (Strong evidence of water on Mars)
        • Approximately 1,000 streams supported for March 24th Science Update (Opportunity Hits the Beach)
        • Between 150 to 500 users daily view NASA TV streams on the portal
    • 239. Event Support Overview
      • Multimedia Design and IT Support
        • Provide high end event support to include the design, development and creation of DVD/CD presentations and onsite support for ten Codes at NASA Headquarters
        • Highlights
        • Provided close out support to the Columbia Accident Investigation Board Final Report DVD creation and distribution
        • Provided on-site network, network services and desktop support for the President's Commission on Implementation of United States Space Exploration Policy
        • Supported more than 50 high visibility events for a variety of NASA Headquarters activities within the last 6 months
    • 240. Questions and Answers
    • 241.
      • 8:30 - 10:30 ISEM Task Order Details 241 - 292
      • 10:30 - 11:45 Questions
      • 11:45 - 1:00 Lunch
      • 1:00 - 4:00 Customer Presentations
      • 4:00 - 4:15 Site Visit Plan 294 - 302
      • 4:15 - 4:30 HQs Facilities 307 - 307
      Agenda – Day 2
    • 242. ISEM Task Order Details
    • 243.
      • CO Mike Alexander GSFC 301-286-6718
      • COTR Les Newell HQ 202-358-4601
      • Alt. COTR Roger Bullock HQ 202-358-1332
      HQ ISEM Contacts
    • 244. ISEM Services Summary 6:00 – 6:00 Help Desk Hours External / internal threats requiring an integrated solution Yes Incident Response Yes ViTS Yes Pagers Billing Support, Operations and Maintenance Telephones / Cell Phones Operations/ Maintenance Systems Engineering Facility (SEF) Consulting, Operations and Maintenance HQ Communications Network (HCN) Yes Acquisitions Emerging IT Technologies, policies, standards, CIO registry Yes Special Assessments Yes Special Tasks 138/52 Application / Website Support NACC at MSFC Yes Mainframe Partition Support 150 (approximately) Servers Operated and Maintained Yes Tactical / Strategic Plan Support Daily – tag-up and SR Screening Weekly – CCB Monthly – In-depth and 533 Review Yes Regular Meeting Attendance Remarks ISEM
    • 245.
      • Work Hours
        • Help Desk (Level II) 6:00 am – 6:00 pm
        • URC 7:30 am – 5:00 pm
        • Incident Response 7 x 24 coverage
        • Network Operations 7 x 24 coverage
        • NHCC Operations 6:00 am – 6:00 pm, then backups and production
        • NHCC Availability 7 x 24 coverage
      • HQS Facility Space that are available to the ISEM Contractor
        • 5500 square feet of furnished space on the Concourse
        • Computers provided for on-site ISEM personnel, training, URC, SEF, NOC, etc.
      Special Interest Items
    • 246.
      • Contract Transition
        • Scheduled to occur between 11/1/05 and 11/30/05
        • NASA to issue a firm fixed price task order for these services
          • Job shadowing
          • Develop insight into 10.0 and 10.x HQ tasks and complete negotiations
          • Finalize space utilization
          • Finalize hardware/software/furniture (GFE) utilization
      Special Interest Items
    • 247.
      • 1.0 Management and Administration
      • 2.0 Information Technology Resources and Management Support
      • 3.0 Applications Development and Sustaining Engineering
      • 4.0 System Engineering, Integration and Telecommunications Services
      • 5.0 NASA Headquarters Computer Center (NHCC) Support
      • 6.0 Customer Services
      • 7.0 Information Technology Security (ITS)
      • 8.0 Transition Planning
      • 9.0 Not Used
      • 10.0 Special Requirements for Headquarters’ Offices
      ISEM WBS Structure
    • 248.
      • Electronic Data and Document Interchange capability at contract start
      • IT Management Plan
      • Small Business (SB) / Small Disadvantaged Business (SDB) / Women Owned Business (WOB) management oversight
      • Resource Management Reports (533)
      • Configuration Management Plan
      • SR and QA Plan (Safety Plan due at contract start)
      • Tactical plan
      WBS 1.0 - Management and Administration
    • 249.
      • IT policy, procedures and standards technical support
        • Federal, Agency, programmatic, CIO, and HQS
        • Assessing, recommending changes and applying
      • Special task support
      • Operational, tactical and strategic plan technical support
      • IT assessments, studies and recommendations
      • Note: Support for this WBS provided by expertise across the contract
      WBS 2.0 – IT Resources and Management Support
    • 250.
      • Software/website development and sustaining
      • Data base management
      • Custom software customer training
      • Life cycle process reviews
      • Software documentation
      • Status reviews
      • Tactical and strategic plan support
      WBS 3.0 – Applications Development and Engineering
    • 251.
      • System engineering support
      • HQS Security Perimeter operations
      • Operation of the NOC, SEF and ViTS
      • HCN advisory and consulting support
      • Internet engineering support
      • Telecommunications budget and billing support
      • Pager acquisition, issuance and record keeping support
      • Tactical and strategic plan support
      WBS 4.0 –Engineering, Integration and Telecom
    • 252.
      • Computer operations, maintenance, administration
      • Production job operations
      • Disaster recovery planning
      • Software maintenance
      • Capacity planning and performance monitoring
      • Safety and security administration
      WBS 5.0 - NASA HQ Computer Center (NHCC)
    • 253.
      • Customer support
        • http://www.hq.nasa.gov/office/codec/codeci/
        • Note: Not all sub-folders are available outside the NASA.Gov domain.
      • Help desk (level II) for custom applications / web services
      • Service request process system
      • Work management tracking system
      • User resource center operations
      • Customer education
      • Audio/visual presentation support
      • Hardware maintenance
      • Equipment moves, relocations and excess
      • Property management and logistics
      WBS 6.0 - Customer Services
    • 254.
      • Develop ITS procedures and standards
      • Conduct periodic audits
      • Support ITS working group
      • Develop and conduct ITS training
      • Support incident response and reporting
      • Perform system and network monitoring
      • Support HQ penetration testing
      • Provide software applications systems security plan support
      • Develop infrastructure Protection Plan
      • Comply with NASA HQ Network Security Policy and NASA Policy Guideline (NPG) 2810
      WBS 7.0 – IT Security (ITS)
    • 255.
      • Purpose is to become able to:
        • Assume responsibilities of the incumbent contractor with no degradation of service, and
        • Complete negotiations for performing WBS 10.0 tasks.
      • A transition plan shall be submitted with the proposal, and requires Government approval prior to proceeding. The plan must:
        • Address interfaces with affected parties
        • Review work being performed by the incumbent contractor
        • Gain knowledge of the WBS 10.0 special tasks, establish liaison with customers and complete negotiations.
        • Develop a space utilization plan and ensure staff are in place by contract start
        • Develop a software development environment plan to ensure software efforts continue flawlessly
        • Finalize HW/SW/Furniture (GFE) utilization
        • Provide briefing to COTR that confirms readiness to assume the task
      WBS 8.0 – Transition Plan
    • 256.
      • Not used.
      WBS 9.0
    • 257. Questions and Answers
    • 258.
      • Support provided across several functional areas for Headquarters’ Offices
        • Applications development support
        • Web site development
        • Project management support
        • Strategic and tactical plans support
        • Customer training of COTS products above and beyond ODIN
        • Internet technology research
        • Information technology security
        • Engineering support
        • Public education / outreach
      WBS 10.0 – Special Requirements for HQ Offices
    • 259. WBS 10.0 – Special Requirements for HQ Offices
      • 30 tasks currently exist supporting 15 HQS Offices that will transition to HITSS
        • Transition shall be seamless to the customer
        • Ongoing support shall continue at contract start
        • Transition Plan shall address this transition
        • Most will be renewed at the start of a new fiscal year
        • New tasks will be generated during the fiscal year
        • 3 “representative” tasks will be defined in the TO RFP and addressed in offered proposals
    • 260. 10.X Special Task Summary ODC Value Task Value Customer Type of Support $52,343 $211,786 HQ Facilities Application Support $163,684 $652,415 Science MD Technical Support $179,609 $585,069 Public Affairs Internet Support $87,512 $443,803 Science MD Project Mgt Support $297,213 $681,859 Science MD Engineering Support $120,113 $796,708 Aeronautics Research MD Application Support $88,622 $596,138 Office of CIO Application Support $48,556 $571,161 Space Operations MD Application Support $36,733 $206,170 Space Operations MD Infrastructure Support $157,477 $1,141,297 Space Operations MD Application Support $2,369 $443,796 NASA Mgt Office Technical Support $4,588 $70,243 Safety & Mission Assurance Application Support $412,824 $1,669,611 Exploration Systems MD Technical Support $84,202 $2,111,565 Science MD Technical Support $579,104 $597,104 HITCD Technical Support
    • 261. 10.X Special Task Summary ODC Value Task Value Customer Type of Support $25,469 $165,158 Office of CIO Technical Support $40,358 $469,310 IFM Program Office Financial Mgt Support $12,148 $251,899 Mgt Systems Division Application Support $60,851 $303,448 NASA TV Webcast/Media Support $35,447 $295,176 HQ Facilities CAD System Support $13,913 $120,178 Logistics Division Application Support $325,882 $731,297 Office of CIO Technology Support $159,639 $225,656 Exploration Systems MD SEB/RFP Support $60,678 $682,996 Exploration Systems MD Technical Support $97,040 $481,286 Aerospace technology Technical Support $123,934 $1,265,067 Office of CFO Application Support $10,056 $88,701 IFM Program Office Technical Support $67,347 $2,158,511 HQ Administrative Mgt Project Mgt Support $24,596 $262,539 Education Customer Training $414,717 $159,362 Inspector General Engineering Support
    • 262.
      • Functional Area: Technical support
      • Customer: Information Technology and Communications Division
      • Description: The contractor shall:
        • Provide hardware and software to provide failover services within the HQ IT infrastructure
        • Design, develop and implement a remote email failover services to a secondary geographical location
      • OY-04 Funding Total: $579,104
      • OY-04 ODC Total: $579,104
      Technical Support (WBS 10.07)
    • 263.
      • Functional Area: Technical support
      • Customer: Science Missions Directorate (SMD)
      • Description: The contractor shall:
        • Evaluate emerging technologies to enhance SMD business systems and processes
        • Develop, maintain, and document the SMD IT architecture
        • Exploit the latest Internet products and services for SMD
        • Provide Web related services
        • Provide review and consultation on IT security policies, procedures, and architecture standards
        • Provide analysis, development, sustaining engineering, and maintenance for SMD Web sites
        • Support the Management of a SMD advanced technology test environment
      • OY-04 Funding Total: $2,111,565
      • OY-04 ODC Total: $84,202
      Technical Support (WBS 10.08)
    • 264. Technical Services (WBS 10.11)
      • Functional Area: Technical support
      • Customer : Exploration Systems Mission Directorate (ESMD)
      • Description: The contractor shall:
        • Evaluate emerging technologies for enhancements to ESMD business applications
        • Develop, maintain and document the ESMD IT architecture
        • Provide technical support to ESMD web sites
        • Procure and install hardware components for the ICE development environment
        • Fully support the ESMD integrated collaborative environment (ICE)
          • Assist in the application of ICE project development life cycle
          • Design a specification and deploy a turnkey integrated audio and video conference and collaborative tools solution
        • Recommend, procure and configure mobile devices such as Blackberry, Palm and other PDAs
      • OY-04 Funding Total: $1,669,611
      • OY-04 ODC Total: $412,824
    • 265.
      • Functional Area: Applications development
      • Customer: NASA HQ Office of Safety and Mission Assurance
      • Description: The contractor shall provide IT-related support and maintenance to existing applications and websites. This includes:
        • Provide a variety of systems analysis support functions
        • Provide applications support and development
        • Provide Engineering/Consulting services
        • Provide ADP/T customer training on unique organizational applications
        • Comprehensive microcomputer or mainframe-based applications networked across one or more NASA Headquarters organizations for applications:
          • Contact List and Special Interest Computing System (CLASICS)
          • Incident Report Information System (IRIS)
          • Office of Safety and Mission Assurance Travel Manager System (QTMS)
      • OY-04 Funding Total: $70,243
      • OY-04 ODC Total: $4,588
      Application Support (WBS 10.12)
    • 266. Technical Support (10.14)
      • Functional Area: Technical services
      • Customer: NASA Management Office (NMO)
      • Description: The contractor shall provide network and systems support, systems engineering, programming support, application development support, electronic messaging / information support, data integrity, virus protection, IT system security, systems design and training. The contractor shall:
        • Provide support for the NASA prime contract system application (NPCS)
        • Provide database administration for NASA prime contract system application (version 2.6 Foxpro)
        • Support interfaces with Jet Propulsion Laboratory’s New Business System (NBS)
        • Support the Integrated Financial Management Program (IFMP) systems
        • Support the Internet presence with information architecture, system / site integration, graphic design and all user support
        • Provide network design and system network support
        • Support computer security
        • Provide technology infusion such as web based applications
        • Support data conversion, validation, interchange and integration between legacy and future applications
      • OY-04 Funding Total: $443,795
      • OY-04 ODC Total: $2,369
    • 267.
      • Functional Area: Provide IT planning and analysis, applications development and IT research and special studies
      • Customer: Office of Space Flight (OSF)
      • Description: The contractor shall:
        • Evaluate office automation systems and Internet based websites and applications unique to OSF
        • Support in areas such as IT Strategic Plan, OSF IT Master Schedules, IT cost insight, IT emerging technology and currency issues
        • Provide operations, maintenance, planning, development and training for all unique applications/databases currently existing or under development
        • Recommend commercial-off-the-shelf software packages and/or automated systems
        • Recommend front-end customer interfaces
        • Maintain customer-developed applications
      • OY-04 Funding Total: $1,141,297
      • OY-04 ODC Total: $157,477
      Application Support (WBS 10.15)
    • 268.
      • Functional Area: IT Infrastructure support
      • Customer: Office of Space Flight (OSF) and the Emergency Operations Center (EOC)
      • Description: The contractor shall:
        • Provide daily on-site and/or on-call support for activities of the OSF Action Center and EOC and related commissions and boards
        • Demonstrate, configure and operate new and emerging hardware in use by the OSF Action Center and EOC
        • Develop as required Internet sites, applications, and multimedia products and event support
        • Support commercial-off-the-shelf software packages and/or automated systems;
        • Provide end-to-end support for the integration of the CAIB Database standalone system until no longer required
      • OY-04 Funding Total: $206,170
      • OY-04 ODC Total: $36,733
      Infrastructure Support (WBS 10.18)
    • 269.
      • Functional Area: Applications development
      • Customer: Office of Space Flight
      • Description: The contractor shall:
        • Perform software requirements analysis, security, development, training, documentation, administration and maintenance to the NMIS
        • Support code re-factoring for NMIS in a rapid application development environment
        • Define, collect and analyze key performance indicators (KPIs) for the Space Flight Enterprise Centers
        • Develop, maintain and document the NMIS web page
      • OY-04 Funding Total: $753,161
      • OY-04 ODC Total: $48,556
      Application Support (WBS 10.19)
    • 270.
      • Functional Area: Applications development
      • Customer: Office of the Chief Information Officer
      • Description: The contractor shall:
        • Provide support in advancing the use of the eXtensible Markup Language (XML) within NASA
        • Provide technical advice and assistance, studies, data gathering, XML registry submission assistance, web site development, account administration, market and product research, business case development support, product evaluations, development and training on the use of XML and XML tools, and logistical support for meetings and working groups
      • OY-04 Funding Total: $596,138
      • OY-04 ODC Total: $88,622
      Application Support (WBS 10.22)
    • 271.
      • Functional Area: Applications development
      • Customer : Office of Aeronautics (OA)
      • Description: The contractor shall:
        • Evaluate emerging technologies and make enhancement recommendations to AO Resources management business applications
        • Develop and exploit the latest web and information technologies (also provide hardware and software to support activities)
        • Develop, maintain, and document OA Resources Management Division IT architecture as it relates to Agency architecture
        • Support commercial-off-the-shelf and customer-developed applications.
        • Provide development, maintenance and operational support to following applications:
          • Resource Authority System (ARS), Budget System (BUDS)
          • Executive Level Reporting (ELR), Guideline Change System (GLCS)
          • Interactive Data Extract Analysis System, On-Line Access System (On-line)
          • Phasing Plan System (PPS), Resource Management and Reporting System
      • OY-04 Funding Total: $796,708
      • OY-04 ODC Total: $120,113
      Application Support (WBS 10.30)
    • 272.
      • Functional Area: Engineering support
      • Customer : Science Mission Directorate (SMD)
      • Description: The contractor shall support IT Operations, provide technology infusion support, and provide general IT planning with emphasis on:
        • Local Area Network/NASA Science Internet Bandwidth Assessment (ISEM)
        • Hardware, software, and maintenance upgrades to ensure interoperability of distributed client-server workstations (ODIN)
        • Graphical display processing requirements, evaluation, and purchasing recommendations for COTS (ISEM)
        • Perform day-to-day workstation operations and maintenance and install new or upgraded software (ODIN)
        • Plan and perform routine data back-ups for all workstations (ODIN)
        • Ensure compliance with all HQ UNIX security procedures and recommendations (ODIN)
        • Support the organization’s UNIX operating system and COTS packages computer training needs (ISEM)
      • OY-04 Funding Total: $681,859
      • OY-04 ODC Total: $297,213
      Advanced Technology Test Bed (WBS 10.34)
    • 273.
      • Functional Area: Project management support
      • Customer: Science Mission Directorate (SMD)
      • Description: The two key IRM planning elements are:
        • An Enterprise-level IRM Strategic Plan; and,
        • Input to a Headquarters SMD 5-year ADP plan.
      • OY-04 Funding Total: $443,803
      • OY-04 ODC Total: $87,512
      IRM Strategic Plan Support (WBS 10.41)
    • 274.
      • Functional Area: Provide ADP/T support services
      • Customer: Office of Public Affairs
      • Description: The contractor shall:
        • Provide technical support to the NASA Public Portal
        • Provide multimedia design, digitization and technical support for the NASA TV and portal teams
        • Recommend upgrades to critical portal software
        • Provide quality assurance of content entered into the portal Content Management System (DAM)
        • Develop custom applications
        • Maintain and make more efficient the following Web pages:
          • NASA main web site
          • NASA news activity main web site
          • NASA-wide search engine
      • OY-04 Funding Total: $585,069
      • OY-04 ODC Total: $179,609
      Internet Support (WBS 10.46)
    • 275.
      • Functional Area : Technical support
      • Customer : Office of Space Science (OSS)
      • Description: The contractor shall:
        • Provide technical and analytical support for the OSS CIO and staff
        • Evaluate emerging technologies to recommend enhancements to the OSS applications
        • Provide system administration for multiple UNIX and Windows 2003 systems
        • Provide Demonstrations and training on new technology
        • Evaluate and develop new systems based on state of the art and leading edge technologies, custom development, and commercial-off-the-shelf (COTS) products
      • OY-04 Funding Total: $652,415
      • OY-04 ODC Total: $163,684
      Technical Support (WBS 10.47)
    • 276.
      • Functional Area: Applications development support
      • Customer: HQ Facilities
      • Description: The contractor shall:
        • Maintain and upgrade, as needed, both the development and computing environment to operate the Division’s applications
        • Develop, maintain, and support the Division’s databases
        • Develop and conduct ADP/T customer training on Division’s applications
        • Currently maintained applications:
          • Facility Utilization System (FUS)
          • Major Facilities Inventory (MFI)
          • (RPI)
        • Update and maintain accurate Configuration Management (CM) materials
      • OY-04 Funding Total: $211,786
      • OY-04 ODC Total: $52,343
      Application Support (WBS 10.48)
    • 277. Engineering Support (10.50)
      • Functional Area: Engineering support
      • Customer: Office of Inspector General (OIG)
      • Description: The contractor shall:
        • Provide OIG with a customized action tracking system based on the Headquarters Action Tracking System (HATS)
      • OY-04 Funding Total: $159,362
      • OY-04 ODC Total: $14,717
    • 278.
      • Functional Area: Customer training of COTS products
      • Customer: Education Office
      • Description: T he contractor shall:
        • Develop and conduct an IT customer training program for all NASA HQ civil servant customers of all ISEM/ODIN systems, equipment, software, and services
        • Provide training for COTS and custom software
        • Provide for custom courseware, as required and include, but shall not be limited to baseline products and key tactical plan software deployments.
      • OY-04 Funding Total: $262,539
      • OY-04 ODC Total: $24,596
      Customer Training (WBS 10.52)
    • 279.
      • Functional Area: IFMS project management support
      • Customer : HQ Administrative Management and Business
      • Description: The contractor shall support the development, maintenance, and enhancement of the following electronic tools:
        • Decision support tools, specifically data warehouses to support the analysis of financial data used by the HQ financial community in conducting business operations
        • The Budget Execution Support System (BESS) to support the HQ Chief Financial Officer budget execution responsibilities
        • The Web Based Time and Attendance Distribution System (WebTADS)
        • The ePayroll System
        • The IFM Core Financial Application, the IFM Travel Manager Application, the IFM Budget Formulation Application, the WebTADS Application, and any other IFMP application at HQ.
        • The IFM/SAP Business Warehouse (BW) for both Core Financial and Budget Formulation
        • HQ and Agency level legacy applications
        • Maintain the Office of the Chief Financial Officer main web site
      • OY-04 Funding Total: $2,158,511
      • OY-04 ODC Total: $67,347
      Project Management Support (WBS 10.53)
    • 280. Technical Support (10.54)
      • Functional Area: Technical support
      • Customer: IFM Program Office (IFMPO)
      • Description: The contractor shall provide technical support that includes:
        • The design, development, delivery, maintenance and support of a new public-facing program web site
        • The design, development, delivery, maintenance and support of an IFM web content maintenance tool
        • General media services, communications and outreach, and web support
      • OY-04 Funding Total: $88,701
      • OY-04 ODC Total: $10,056
    • 281.
      • Functional Area: Applications development
      • Customer : HQ Office of the Chief Financial Officer
      • Description: The contractor shall:
        • Maintain and support the central resources control system (CRCS)
        • Provide for technical support for the BRIC application
        • Support deployment of COTS, “short term” and “long term”, Account Relationship Tracking System (ARTS)
        • Support the NASA Audit Tracking System (NATS)
        • Develop and submit a plan to migrate financial mainframe legacy data to the HQ CFO computing environment
        • Design, develop, test, provide training, implement, maintain, and support the Mandatory Controls Tool
        • Develop, operate, and support the CFO web site (portal)
        • Provide SAP consulting support services
      • OY-04 Funding Total: $1,265,067
      • OY-04 ODC Total: $123,934
      Application Support (WBS 10.57)
    • 282.
      • Functional Area: Evaluate, demonstrate, develop, deploy and maintain information technology, multimedia, electronic commerce and business process solutions
      • Customer: Aerospace Technology Enterprise (OAT)
      • Description: The contractor shall:
        • Evaluate emerging technologies to recommend enhancements to business applications
        • Develop, maintain and document OAT IT architecture as it relates to Agency IT architecture and any locations hosting OAT servers/applications
        • Develop and exploit latest web and information services and products for OAT (includes the acquiring of hardware and software)
        • Devise and implement Enterprise information architecture
      • Currently maintained web sites are:
        • NASA Office of Aerospace Technology main web site
        • NASA Office of Commercial Technology main web site
      • OY-04 Funding Total: $481,286
      • OY-04 ODC Total: $97,040
      Technical Support (WBS 10.61)
    • 283.
      • Functional Area: Technical support
      • Customer: Exploration Systems Mission Directorate
      • Description: The contractor shall:
        • Support the investigation and deployment of state-of-the-art and leading edge technologies within the Directorate’s Internet by providing custom and COTS solutions
        • Provide quantitative and qualitative studies which help the Directorate make strategic IT decisions
        • Develop, implement, and maintain state-of-the-art tools to improve work flow efficiency, provide cost savings, and meet specific Directorate requirements
        • Shall develop and deploy office automation tools for the Directorates business processes
      • OY-04 Funding Total: $682,996
      • OY-04 ODC Total: $60,678
      Technical Support (WBS 10.62)
    • 284. SEB / RFP Support (10.65)
      • Functional Area: Provide support and services
      • Customer: Exploration Systems Mission Directorate (ESMD)
      • Description: The contractor shall provide support and services for 125 NASA ESMD customers working to support the Explorations Systems RFP and SEB. Support Includes:
        • Installation of cable plant to two SEB rooms
        • Configure LAN of an internal workgroup for each of the SEB rooms
        • Provide telephone sets for each SEB room
        • Provide security mitigation, FAX, print, projector and shredders
        • Provide hardware and software to support SEB participants
      • OY-04 Funding Total: $225,656
      • OY-04 ODC Total: $159,639
    • 285.
      • Functional Area: Investigate new technology and provide recommendations for new technology infusion
      • Customer: NASA Office of the Chief Information Officer (CIO)
      • Description: The contractor shall:
        • Provide technical input to the formulation and adoption of an Agency wide Enterprise Architecture effort
        • Provide technical input and management support to the formulation and adoption of the Agency wide NASA integrated Services Environment (NISE) effort
        • Formulate NIST compliant master security planning documents and standards
      • OY-04 Funding Total: $731,297
      • OY-04 ODC Total: $325,882
      Technology Support (WBS 10.69)
    • 286. Application Development (10.82)
      • Functional Area: Application development
      • Customer: NASA Headquarters Logistics Management Division
      • Description: The contractor shall provide the following services:
        • Web based application development
        • ADP/T training
        • Sustaining engineering
        • Multimedia
        • Configuration management
        • Section 508 requirements
        • Security – NASA NPR – 2810 requirements
      • OY-04 Funding Total: $120,178
      • OY-04 ODC Total: $13,913
    • 287. CAD System Development and Operation (10.87)
      • Functional Area: Development and Operation of a CAD System
      • Customer: HQ Facilities Management
      • Description: The contractor shall:
        • Operate and maintain a Computer Aided Design / Computer Aided Facility Management (CAD / CAFM) system
        • Provide hardware and software engineering to continue development of the Facilities Help Desk System (FHDS)
      • OY-04 Funding Total: $295,176
      • OY-04 ODC Total: $35,447
    • 288. Webcast and Streaming Media Support (10.89)
      • Functional Area: Webcast and Streaming Media Support
      • Customer : NASA TV
      • Description: The contractor shall:
        • Digitize existing analog or digital material for web download for webcast
        • Work with NASA TV to enable webcasting and archiving any material shown on NASA TV
        • Develop a plan for simultaneous webcast from NASA Headquarters
        • Support additional webcast requirements such as CD ROM or website development
        • Support a total of 18 NASA events
        • Provide the means to host web conference events
        • Provide high-end IT event support for on and offsite functions in support of the Office of the Administrator
        • Examine existing web casting web capability at other NASA facilities and provide a recommendation that will enable the NASA webcast infrastructure to be used by all centers
        • Support both uni-cast and multi-cast routing
      • OY-04 Funding Total: $303,448
      • OY-04 ODC Total: $60,851
    • 289. Applications Support (10.94)
      • Functional Area: Applications support
      • Customer: NASA Headquarters Management Systems Division
      • Description: The contractor shall maintain and upgrade the CATS II application for the following modules:
        • Office of Inspector General (OIG)
        • General Accounting Office (GAO)
        • Columbia Accident Investigation Board (CAIB)
        • Management Control (MC)
        • Quality Management System (QMS)
        • Defense Contractor Audit Agency (DCAA)
        • Information Technology Security (ITS)
        • President of the United States Vision (POTUS)
        • Management Action Resource System (MARS)
        • Aerospace and Safety Advisory Panel (ASAP)
      • OY-04 Funding Total: $251,899
      • OY-04 ODC Total: $12,148
    • 290. Integrated Financial Management Support (10.96)
      • Functional Area: Integrated Financial Management Support
      • Customer: Agency’s Integrated Financial Management Program (IFMP)
      • Description: The contractor shall provide services and support to the following IFMP applications:
        • Enterprise upgrade to the SAP Core Financial System
        • The Budget Formulation System at Headquarters
        • E-Payroll System
        • FPDS-NG System
      • The contractor shall provide project management, project planning, data cleanup, data conversion, legacy system interfaces, technical architectural support, logistics support and software installation services
      • OY-04 Funding Total: $469,310
      • OY-04 ODC Total: $40,358
    • 291. Technical Support (10.98)
      • Functional Area: Technical support
      • Customer: NASA Office of the Chief Information Officer (OCIO)
      • Description: The contractor shall provide assistance on all Federal Section 508 compliance. This includes:
        • Reviewing and providing comments on draft Section 508 technical documentation
        • Maintaining the Agency level Section 508 web site
        • Surveying electronic and information technology products that conform with the Section 508 requirements
        • Providing a testing capability (hardware, software and Section 508 personnel) to determine compliance of specific Electronic and Information Technology (E&IT) with Section 508 requirements
        • Conduction studies of specific topic areas related to the interpretation and implementation of Section 508
      • OY-04 Funding Total: $165,158
      • OY-04 ODC Total: $25,469
    • 292. Questions and Answers
    • 293. Site Visit Plan Ray Johnston
    • 294.
      • Objective
      • Contractor Badging Procedure
      • Site Visit Rules
      • Site Visit Information
      • Exit session
      Topics
    • 295. Objective
      • The Site Visit provides the opportunity for potential Headquarters Information Technology and Support Services (HITSS) bidders to visit NASA HQ and observe the current ISEM processes
    • 296. Contractor Badging Procedure
      • To obtain a badge each Site Visit attendee must:
        • Be a US citizen
        • Show a picture ID
        • Fill out and sign the security form
      • A temporary badge will be provided at the NASA HQ West lobby security station
      • The temporary badge must be visible and worn above the waist at all times
    • 297. Contractor Badging Procedure
      • The first entry into the NASA HQ building and the last exit out must be at the west lobby security station
      • If a badged attendee exits past the east or west lobby security station the badge must be surrendered
        • An attendee who has exited NASA HQ and wishes to re-enter and use the same badge must:
          • Provide a picture ID and
          • Know the number of the previous badge
        • Otherwise, the badging process must be repeated
      • At the end of the Site Visit each attendee must exit through the NASA HQ West lobby security station and turn in the temporary badge
    • 298. Site Visit Rules
      • Each potential bidder was allowed to submit one Site Visit attendee name
        • 37 attendee names were submitted
        • Substitution may occur up until the start of the tour
      • Attendees are always escorted by HITCD personnel
      • Please, do not touch any equipment
      • All questions must be submitted in writing
        • Do not ask questions to anyone
        • All relevant submitted questions will be posted and appropriately responded to
    • 299. Site Visit Information
      • Attendees must be signed in and badged at the NASA HQ West lobby security station not later than 8:15am on Friday, June 3, 2005.
        • HITCD personnel will escort the attendees to MIC-6A
      • Prior to the start of the Site Visit, the attendees will be allowed to observe the:
        • Daily tag-up from 8:30 – 9:00
        • Weekly CCB from 9:00 – 9:45
      • Upon CCB conclusion a Site Visit kickoff will occur, followed by the start of the Site Visit tour
        • The kickoff will supply all pertinent detailed Site Visit information
    • 300. Site Visit Information
      • Attendees have be divided into four groups of 9-10 personnel and escorted through HQ areas where ISEM equipment is operated, services are provided, and on-site personnel are stationed.
      • Site Visit Tour guides are:
        • Elaine Bowman
        • Ray Johnston
        • Greg Kerr
        • Brenda Williams
      • Each tour group will see the same areas of interest
        • Groups and attendees are shown on the following page
    • 301. Exit Session
      • At the end of the Site Visit the tour groups will return to MIC-6A for a Site Visit exit session
        • final instructions / questions / issues
      • Upon conclusion of the Site Visit exit session the attendees are escorted to the west lobby security station to turn-in their badge and exit the building
    • 302. Questions
    • 303.
      • Thank You For Attending
    • 304. Acronyms
    • 305. Acronyms
      • ACD Automated Call Distribution
      • ADP/T Automated Data Processing / Telecommunication
      • BDC Backup Domain Controller
      • CAC Customer Advisory Council
      • CATV Cable Television
      • CAIB Columbia Accident Investigation Board
      • CBACS Common Badging and Access Control System
      • CCB Configuration Control Board
      • CDR Critical Design Review
      • CIMS Cyber Identity Management System
      • CIO Chief Information Officer
      • COA Customer Outreach Advocates
      • COOP Continuity Of Operations Plan
      • COTR Contracting Officer Technical Representative
      • COTS Commercial Off-the-Shelf
      • CSCC Catalog of Services and Commercial Components
      • CTC Computer Training Center
      • DBMS Database Management System
      • DHCP Dynamic Host Configuration Protocol
    • 306. Acronyms
      • DNS Domain Name Server
      • DO Delivery Order
      • DOCO Delivery Order Contracting Officer
      • DOCOTR Delivery Order COTR
      • DOSP Delivery Order Selection Process
      • DS3 Digital Signal Level 3
      • ENAC Entrance National Agency Check
      • FTP File Transfer Protocol
      • FY Fiscal Year
      • GOTS Government Off-the-shelf Software
      • GSA General Services Administration
      • GSFC Goddard Space Flight Center
      • HCN HQ Communications Network
      • HISP HQ Information Security Perimeter
      • HQ (NASA) HQ
      • H/W Hardware
      • ICMP Internet Control Message Protocol
      • IETF Internet Engineering Task Force
      • IFMS Integrated Financial Management System
    • 307. Acronyms
      • IMAP Internet Message Access Protocol
      • ISDN Integrated Services Digital Network
      • ISEM IT Systems, Engineering and Management
      • ISO International Standards Organization, Greek for &quot;equal“
      • ITAG Information Technology Technical Advisory Group
      • IWMS ISEM Work Management System
      • HONURS HQ New User Request System
      • HITSS Headquarters Information Technology Support Services
      • HAMS Headquarters Account Management System
      • IT Information Technology
      • ITS Information Technology Security
      • ITSM IT Security Manager
      • JPL Jet Propulsion Laboratory
      • LAN Local Area Network
      • LANOC LAN Operation Center
      • LOE Level Of Effort
      • MAC Macintosh
      • M/A/C Move/Add/Change
      • MAN Metropolitan Area Network
    • 308. Acronyms
      • MIC Management Information Center
      • MSFC Marshall Space Flight Center
      • NACC NASA Administration Computing Center
      • NAMS NASA Account Management System
      • NAS Network Attached Storage
      • NHCC NASA HQ Computer Center
      • NISE NASA Integrated Services Environment
      • NISN NASA Integrated Services Network
      • NOC Network Operations Center
      • NPR NASA Policy Requirement
      • NSN NASA Secure Network
      • NTE Not to exceed
      • ODIN Outsourcing Desktop Initiative (for NASA)
      • OIG Office of the Inspector General
      • ORR Operational Readiness Review
      • OS Operating System
      • PC Personal Computer
      • PDA Personal Digital Assistant
      • PDC Primary Domain Controller
    • 309.
      • PDR Preliminary Design Review
      • PGP Pretty Good Privacy
      • PKI Public Key Infrastructure
      • POC Point of Contact
      • POP Post Office Protocol
      • PPTP Point to Point Tunneling Protocol
      • PRC Program Review Center (9H40)
      • PRI Primary Rate Interface
      • PSCN Program Support Communication Network
      • RTS Return to Service
      • SAIC Science Application International Corporation
      • SCIF Sensitive Compartmented Information Facility
      • SEF Systems Engineering Facility
      • SMBS Seat Management Business System
      • SMS Systems Management Server
      • SMTP Simple Mail Transport Protocol
      • SNMP Simple Network Management Protocol
      • SOC Space Operations Center
      • SRRT Service Request Review Team
      Acronyms
    • 310.
      • SSH Secure Shell
      • SSL Secure Socket Layer
      • S/W Software
      • TLS Transparent LAN Service
      • VLAN Virtual LAN
      • WANOC Wide Area Network Operation Center
      • WIO Workstation Interface Outlets
      • WITS Washington Integrated Telephone System
      • WOC Washington Office Center (SAIC Office Space)
      • WWW World Wide Web
      Acronyms