10 December 2020

Total Page:16

File Type:pdf, Size:1020Kb

10 December 2020 PERFORMANCE WORK STATEMENT FOR UNITED STATES TRANSPORTATION COMMAND (USTRANSCOM) COMMAND, CONTROL, COMMUNICATIONS & CYBER SYSTEMS DIRECTORATE (TCJ6) MANAGED INFORMATION TECHNOLOGY SERVICE (MITS) ENTERPRISE SUPPORT Managed Services 10 December 2020 1 PERFORMANCE WORK STATEMENT (PWS) 1 DESCRIPTION OF SERVICES 1.1 Background The United States Transportation Command (USTRANSCOM) located at Scott Air Force Base (AFB), IL, is one of 11 Unified Combatant Commands (UCC). USTRANSCOM provides command and control (C2) for the synchronized transportation, distribution, and sustainment of personnel and assets, making possible the projection and maintenance of national power wherever needed with speed and agility, high efficiency, and a high level of trust and accuracy. USTRANSCOM’s mission is to provide air, land, and sea transportation for the Department of Defense (DoD) and other Government and non-Government organizations during both peace and war. The Commander, USTRANSCOM, is tasked as the single manager of the Defense Transportation System (DTS) to oversee defense common-user transportation assets. The Secretary of Defense further expanded the USTRANSCOM mission by tasking USTRANSCOM to manage key components of the Joint Deployment and Distribution Enterprise (JDDE). An important functional requirement is the integration of the Transportation Component Commands (TCCs): Air Mobility Command (AMC), Surface Deployment and Distribution Command (SDDC), and Military Sealift Command (MSC). USTRANSCOM Command, Control, Communications, and Cyber (C4) Systems (C4S) Directorate (TCJ6) provides essential C4S support to the USTRANSCOM Commander, the Joint Enabling Capabilities Command (JECC) and the TCCs in performance of the command’s mission to provide global air, land, and sea transportation to meet national security objectives. The USTRANSCOM C4 environment interfaces with numerous on-site and remote commercial, DoD, service, and common-user networks (i.e., Secret Internet Protocol Router Network (SIPRNet), Non-secure Internet Protocol Router Network (NIPRNet), DoD approved cloud environments and the Scott AFB Local Area Network (LAN), Wide Area NetworkWAN), Metropolitan Area Network (MAN), or the DoD Information Networks (DoDIN)). A myriad of applications make use of the USTRANSCOM C4 infrastructure by providing access and services to the USTRANSCOM user community. USTRANSCOM operates the Common Computing Environment (CCE) surrounded by a network defense infrastructure. The USTRANSCOM CCE, supported by TCJ6 and multiple United States Air Force (USAF) organizations and SDDC, is comprised of several operating systems clients and servers both on premise and in the DoD approved cloud environments, both physical and virtual. Supported operating systems, software, applications are listed in Appendix F: Operating Systems/Software/Applications Supported and Protocols in Use are listed in Appendix G: Protocols in Use. The diversity of applications riding on the USTRANSCOM CCE (C2 systems, information management systems, mail/message systems, and security systems) increases the complexity and difficulty to integrate new system requirements. The information security infrastructure operating with the USTRANSCOM CCE is a unique integration of products demanding a high degree of technical skills and understanding. SDDC, a component of USTRANCOM provides global surface transportation to meet national security objectives in peace and war. SDDC executes its mission through three core processes: (1) surface movements, (2) personal property and passenger movement, and (3) deployability engineering. It is a joint-service major Army command and USTRANSCOM’s surface transportation component. SDDC’s mission, “To provide global surface distribution 2 management and services to meet National Security objectives in peace and war,” positions this organization as the link between DoD shippers, commercial carriers, and the warfighters offering safe, responsive, efficient distribution and deployment solutions for the military. DoD uses Information Technology (IT) for worldwide surface deployment, distribution and in-transit visibility of equipment and supplies. The SDDC Information Management Directorate’s mission is to manage the mission area support functions (communications, automation, storage area networks, audio-visual, publications, and records management disciplines). NEED TO ADD AMC LINES 1.2 1.2 Scope The scope of the contract effort is to provide a broad range of Managed Information Technology Services, MITS and C4S capabilities to support the USTRANSCOM, AMC and SDDC missions. Information Technology (IT) technical skills will be required to support the USTRANSCOM C4 environment, which interface with numerous on-site and remote commercial, DoD, service, common-user networks, and in the DoD approved cloud (i.e., Secret Internet Protocol Router Network (SIPRNet), Non-secure Internet Protocol Router Network (NIPRNet), DoD approved cloud environments and the Scott AFB Local Area Network (LAN), Wide Area Network WAN),Metropolitan Area Network (MAN), or the DoD Information Networks (DoDIN)). Additional support will be required to a myriad of applications that make use of the USTRANSCOM C4 infrastructure by providing access and services to the USTRANSCOM and SDDC user community. Additionally, the contractor shall provide a range of IT services to include cyber security, network operations and maintenance, IT planning, system integration, technical testing and evaluation, analysis and guidance, software management, systems administration, purchase of hardware and software, hardware repair and enhancements, service desk, software configuration, end user devices support/desktop services, architecture and infrastructure management, system management, audio visual and video teleconferencing, and all deliverables related to these services. The contractor shall utilize managed services best practices to perform the tasks and subtasks of this PWS to provide responsive IT service delivery. The required outcomes are delivering Managed IT services to USTRANSCOM users within agreed service levels and achieving continual service improvements to IT services. The contractor shall be responsible for coordinating, managing, assigning resources, processes, and activities with regard to the successful delivery of the entire IT service delivery process as defined in this PWS. The contactor, in concert with the Government, will establish, collect, and report metrics to evaluate and improve service delivery performance. The contractor will leverage a Managed Services framework, other Government publication (e.g. DoD Enterprise Service Management Framework (DESMF) edition II, or latest version) and IT Service Management (ITSM) to establish a business management approach and discipline to IT service delivery. Managed IT Service is a set of specialized organizational capabilities to design, implement, and manage quality services providing value to our business partners and customers. Contract shall comply with DoDI 8440.01 “DoD Information Technology (IT) Service Management (ITSM)” These capabilities take the form of functions and processes for managing services over the lifecycle, through strategy, design, transition, operations, and continual service improvement (CSI). This contract shall use Managed Services best practices to perform the following: Develop an Integrated Master Schedule incorporating all contractor tasks, projects, 3 plans, activities to show schedule, resources, and objectives Identify ITSM issues and focus on the highest priorities identified by Government Service multiple customers with varying requirements Define, measure, and report relevant metrics to help with fact-based decision-making Improve efficiency by automating standard tasks, and streamlining processes by applying lean principles to the work Unite teams and processes by understanding interdependencies and how they impact one another Influence the organizational culture to support CSI activities 1.3 1.3 Specific Tasks 1.3.1 Task 1: Contract Level and Contract Management This task consists of the functional activities relating to the administration and management of this effort. The contractor shall identify a Program Manager (PM) by name who shall provide management, direction, administration, clerical support, documentation, quality assurance, and leadership during the execution of this PWS. The contractor shall designate a principal point of contact for technical issues in addition to the PM. The contractor shall provide a centralized program management capability. The contractor shall prepare documents such as briefings, point papers, and meeting minutes related to status of the performance of this PWS. The contractor shall provide support in the specific areas outlined below in this PWS. The contractor shall provide all deliverables listed in section 1.4, to include referenced documents, contractor-developed and Government approved plans, schedules, and milestones. The contractor shall meet stated Government requirements and milestones. If contractor misses milestones, the Government must be notified in writing within 24 hours of the missed deadline. The contractor’s PM is the authorized point of contact with the Government Contracting Officer’s Representative (COR). PM responsibilities include, but are not limited to, interfacing with Government management personnel, staffing of all tasks, formulating and enforcing work standards, creating personnel and project schedules, reviewing work
Recommended publications
  • Illustrated Tutorial: Creating a Bootable USB Flash Drive for Windows XP
    Illustrated tutorial: Creating a bootable Version 1.0 February 15, 2007 USB flash drive for Windows XP By Greg Shultz The ability to boot Windows XP from a USB Flash Drive (UFD) offers endless possibilities. For example, you might make an easy-to-use troubleshooting tool for booting and analyzing seemingly dead PCs. Or you could transport your favorite applications back and forth from home to work without having to install them on both PCs. However, before you can create a bootable UFD, you must clear a few hurdles. You saw that one coming didn’t you? The first hurdle is having a PC in which the BIOS will allow you to configure the USB port to act as a bootable device. The second hurdle is having a UFD that that will work as a bootable device and that’s large enough and fast enough to boot an operating system such as Windows XP. The third hurdle is finding a way to condense and install Windows XP on a UFD. If you have a PC that was manufactured in the last several years, chances are that its BIOS will allow you to configure the USB port to act as a bootable device. If you have a good qual- ity UFD that’s at least 512 KB and that was manufactured in the last couple of years, you’ve probably cleared the second hurdle. And once you’ve cleared those first two hur- dles, the third one is a piece of cake. All you have to do is download and run some free soft- ware to create the bootable UFD.
    [Show full text]
  • System Requirements
    Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Before installing and using the software, please review the readme files, release notes, and the latest version of the applicable user documentation, which are available from the Trend Micro website at: http://docs.trendmicro.com/en-us/enterprise/officescan.aspx Trend Micro, the Trend Micro t-ball logo, and OfficeScan are trademarks or registered trademarks of Trend Micro Incorporated. All other product or company names may be trademarks or registered trademarks of their owners. Copyright © 2017 Trend Micro Incorporated. All rights reserved. Release Date: October 2017 Protected by U.S. Patent No. 5,623,600; 5,889,943; 5,951,698; 6,119,165 Table of Contents Chapter 1: OfficeScan Server Installations Fresh Installations on Windows Server 2008 R2 Platforms .............................................................................................................................................................................. 1-2 Fresh Installations on Windows Server 2012 Platforms ..................................................................................................................................................................................... 1-3 Fresh Installations on Windows Server 2016 Platforms ..................................................................................................................................................................................... 1-4 Fresh Installations
    [Show full text]
  • Migrating Active Directory to Windows Server 2012 R2
    Windows Server 2012 R2 Migrating Active Directory to Windows Server 2012 R2 Hands-on lab In this lab, you will complete a migration of a Windows Server 2008 R2 domain environment to Windows Server 2012 R2 with no downtime to clients. All roles currently held including FSMO, DHCP and DNS will be transferred to enable the Windows Server 2008 R2 domain controller to be retired. Produced by HynesITe, Inc. Version 1.0 12/15/2013 This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
    [Show full text]
  • No More Excuses: Windows 7 Makes It Easy to Manage Computer Power
    • Products that earn the ENERGY STAR® prevent greenhouse gas emissions by meeting strict energy efficiency guidelines set by the U.S. Environmental Protection Agency and the U.S. Department of Energy. www.energy star.gov NO MORE EXCUSES: WINDOWS 7 MAKES IT EASY TO MANAGE COMPUTER POWER CONSUMPTION ORGANIZATION-WIDE Here’s how you can take advantage of Windows 7’s new power management features The University of Wisconsin at Oshkosh is no stranger to the idea of sustainability. In 2003 it became the first university in the state to join the Environmental Protection Agency’s Green Power Partnership. Its green initiatives also earned the university high marks from the Sierra Club, which ranked the university nationally in its Cool Schools survey. Given this commitment to green, it’s no surprise that the university first deployed computer power management back in 2005, and that it was one of the first Energy Star power management success stories. At that time, the University’s computers ran the Windows XP and Windows 2000 operating systems, neither of which included native tools for the central administration of power management features. To implement power management settings on these machines, the University used third-party software from ENERGY STAR called EZ GPO. For detailed information and resources concerning Now that Windows 7 has CPM client management features built in, it’s much the power management of easier to administer power management. This case study will show you how the University of Wisconsin at Oshkosh took full advantage of computer power PCs running Windows XP, management features on Windows Vista and Windows 7 clients managed by please see the ENERGY STAR Windows Server 2008.
    [Show full text]
  • Chapter 15-70-411FINAL[1]
    Lesson 15: Configuring Service Authentication MOAC 70-411: Administering Windows Server 2012 Overview • Exam Objective 5.1: Configure Service Authentication • Configuring Service Authentication • Managing Service Accounts © 2013 John Wiley & Sons, Inc. 2 Configuring Service Authentication Lesson 15: Configuring Service Authentication © 2013 John Wiley & Sons, Inc. 3 Authentication • Authentication is the act of confirming the identity of a user or system and is an essential part used in authorization when the user or system tries to access a server or network resource. • Two types of authentication that Windows supports are NT LAN Manager (NTLM) and Kerberos. • Kerberos is the default authentication protocol for domain computers. • NTLM is the default authentication protocol for Windows NT, standalone computers that are not part of a domain, and situations in which you authenticate to a server using an IP address. © 2013 John Wiley & Sons, Inc. 4 Understanding NTLM Authentication • NT LAN Manager (NTLM) is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. • NTLM is an integrated single sign-on mechanism. • NTLM uses a challenge-response mechanism for authentication in which clients are able to prove their identities without sending a password to the server. © 2013 John Wiley & Sons, Inc. 5 Managing Kerberos Kerberos: • Is a computer network authentication protocol, which allows hosts to prove their identity over a non-secure network in a secure manner. • Can provide mutual authentication
    [Show full text]
  • Starburn CD/DVD/Blu-Ray/HD-DVD Toolkit: Getting Started
    StarBurn Software Technical Reference Series StarBurn CD/DVD/Blu-Ray/HD-DVD Toolkit: Getting Started April 18, 2016 StarBurn Software www.starburnsoftware.com Copyright © Rocket Division Software 2001-2016. All rights reserved. Copyright © StarBurn Software 2009-2016. All rights reserved. StarBurn CD/DVD/Blu-Ray/HD-DVD Toolkit: Getting Started Page 1 of 13 StarBurn Software Technical Reference Series INTRODUCTION .................................................................................................. 4 KEY BENEFITS ..................................................................................................... 5 KEY FEATURES .................................................................................................... 7 SUPPORTED PLATFORMS .................................................................................. 11 SYSTEM REQUIREMENTS................................................................................... 12 CONTACTS........................................................................................................ 13 StarBurn CD/DVD/Blu-Ray/HD-DVD Toolkit: Getting Started Page 2 of 13 StarBurn Software Technical Reference Series COPYRIGHT Copyright © Rocket Division Software 2001-2016. All rights reserved. Copyright © StarBurn Software 2009-2016. All rights reserved. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written
    [Show full text]
  • Exploring the Windows Server 2008 Interface
    LAB 1 EXPLORING THE WINDOWS SERVER 2008 INTERFACE This lab contains the following projects and activities: Project 1.1 Modifying Basic Server Settings Project 1.2 Configuring TCP/IP Settings Project 1.3 Configuring a Second Windows Server 2008 Computer (Optional) Project 1.4 Configuring a Windows Server 2008 Server Core Computer (Optional) Lab Review Questions Lab Challenge Verifying Active Directory SRV Records 1.1 COPYRIGHTED MATERIAL BEFORE YOU BEGIN Lab 1 assumes that setup has been completed as specified in the setup document and that your computer has connectivity to other lab computers and the Internet. To perform all projects in Lab 1, you will need: • Two (2) full installations of Windows Server 2008 • One (1) Server Core installation of Windows Server 2008 2 Microsoft Windows Server 2008 Active Directory Configuration For subsequent labs, optional projects are provided that involve a second server running the full GUI version of Windows Server 2008 to be configured as a Read- Only Domain Controller and a third server running Windows Server 2008 Server Core. You can use multiple physical computers, or you can use Microsoft Virtual PC or Virtual Server to install and run multiple servers on a single machine. This manual assumes that you are using multiple virtual machines under Microsoft Virtual PC. In the optional projects for this lab, Projects 1.3 and 1.4, you will configure the second and third servers necessary to perform the optional projects in future lessons. The instructor PC is preconfigured as a domain controller in the lucernepublishing.com domain for demonstration purposes; it is named INSTRUCTOR01.
    [Show full text]
  • Windows Server Update Services 3.0 SP2 Release Notes
    Windows Server Update Services 3.0 SP2 Release Notes These release notes describe the Windows Server Update Services 3.0 Service Pack 2 (WSUS 3.0 SP2) release. This document contains the following sections: 1. What‟s New in This Release 2. System Requirements for the WSUS 3.0 SP2 Server Installation 3. Configuration Prerequisites and Best Practice Recommendations for the WSUS Server 4. Windows Small Business Server Prerequisites 5. System Requirements for the WSUS 3.0 SP2 Remote Console Installation 6. System Requirements for Client Installation 7. Upgrade Requirements and Recommendations 8. Installing WSUS 3.0 SP2 9. Setup Command-line Parameters for Unattended WSUS 3.0 SP2 Installations 10. Known Issues What’s New In This Release Integration with Windows Server 2008 R2. Support for the BranchCache feature in Windows Server 2008 R2. Support for Windows 7 clients. Windows Update Agent (WUA) client improvements. The new WUA client offers a collection of performance enhancements, user experience improvements, plus an array of bug fixes based on customer feedback. Client scan time is faster than previous versions. Computers managed by WSUS servers can now run „scoped‟ scans against those same WSUS servers, instead of performing a full scan. This will result in order-of-magnitude faster scans for applications using Microsoft Update APIs such as Windows Defender. Windows Update Agent (WUA) user experience improvements help users better organize updates and provide greater clarity on update value and behavior. Imaged machines will be more clearly displayed in the WSUS console. For more information, see article titled A Windows 2000-based, Windows Server 2003-based, or Windows XP-based computer that was set up by using a Windows 2000, Windows Server 2003, or Windows XP image does not appear in the WSUS console.
    [Show full text]
  • In Windows Server 2008 R2 and Windows Server 2008 (The Former Containing the Later Release of Hyper-V)
    Hyper-V Microsoft Hyper-V Developer(s) Microsoft Initial release July 26, 2008 (KB950050)[1][2] R2 Service Pack 1 Stable release (KB976932)[3][4] / March 15, 2011; 15 months ago Windows 8 (both its server and client versions) (future) and Operating system Windows Server 2008 or standalone Type Virtual machine License Proprietary Hyper V Slide 1 of 21 Microsoft Hyper-V ■ Microsoft Hyper-V, ✦ codenamed Viridian ✦ and formerly known as Windows Server Virtualization, ✦ is a hypervisor-based virtualization system for x86-64 systems ■ A beta version of Hyper-V was shipped with certain x86-64 editions of Windows Server 2008, and the finalized version (automatically updated through Windows Update) was released on June 26, 2008 ■ Hyper-V has since been released in a free stand-alone version, and has been upgraded to Release 2 (R2) status Hyper V Slide 2 of 21 Versions and variants ■ Hyper-V exists in two variants: ✦ as a stand-alone product called Microsoft Hyper-V Server 2008 (Hyper-V Server 2008 R2 for the second release), ✦ and as an installable role in Windows Server 2008 R2 and Windows Server 2008 (the former containing the later release of Hyper-V). ■ The stand-alone version of Hyper-V is free, and was released on October 1, 2008. ■ It is a variant of the core installation of Windows Server 2008 that includes full Hyper-V functionality; other Windows Server 2008 roles are disabled, and there are limited Windows Services. ■ The free Hyper-V Server 2008 variant is limited to a command line interface (CLI), where configuration of the "Host" or "Parent" (Hyper-V Server 2008) OS, physical hardware and software is done using shell commands.
    [Show full text]
  • Introduction to Microsoft Core Licensing Models
    Licensing brief October 2020 Introduction to Microsoft Core licensing models This brief applies to all Microsoft Licensing programs. Contents Summary ...................................................................................................................................................................................................................... 1 Definitions ................................................................................................................................................................................................................... 2 Introduction to Per Core Licensing ................................................................................................................................................................... 4 Per Core licensing model ............................................................................................................................................................................. 5 Per Core/CAL licensing model ................................................................................................................................................................... 5 Management Servers licensing model ................................................................................................................................................... 6 SQL Server .............................................................................................................................................................................................................
    [Show full text]
  • Monitoring Windows with Powershell
    Monitoring Windows Systems with PowerShell SL1 version 8.14.0 Table of Contents Introduction 4 Monitoring Windows Devices in the ScienceLogic Platform 5 What is SNMP? 5 What is PowerShell? 5 PowerPacks 6 Configuring Windows Systems for Monitoring with SNMP 7 Configuring SNMP for Windows Server 2016 and Windows Server 2012 8 Configuring Ping Responses 8 Installing the SNMP Service 9 Configuring the SNMP Service 14 Configuring the Firewall to Allow SNMP Requests 19 Configuring Device Classes for Windows Server 2016 and Windows 10 19 Manually Align the Device Class 20 Edit the Registry Key 20 Configuring SNMP for Windows Server 2008 21 Configuring Ping Responses 21 Installing the SNMP Service 22 Configuring the SNMP Service 25 Configuring the Firewall to Allow SNMP Requests 30 Configuring Windows Servers for Monitoring with PowerShell 31 Prerequisites 32 Configuring PowerShell 32 Step 1: Configuring the User Account for the ScienceLogic Platform 33 Option 1: Creating an Active Directory Account with Administrator Access 33 Option 2: Creating a Local User Account with Administrator Access 34 Option 3: Creating a Non-Administrator User Account 34 Optional: Configuring the User Account for Remote PowerShell Access to Microsoft Exchange Server 36 Optional: Configuring the User Account for Remote PowerShell Access to Hyper-V Servers 36 Creating a User Group and Adding a User in Active Directory 36 Setting the Session Configuration Parameters and Group Permissions 37 Creating a PowerShell Credential 38 Optional: Configuring the User Account for
    [Show full text]
  • Installation and Upgrade on Windows Server 2008/2012 When the Secondary Server Is Physical Vmware Vcenter Server Heartbeat 6.6
    Installation and Upgrade on Windows Server 2008/2012 When the Secondary Server is Physical VMware vCenter Server Heartbeat 6.6 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs. EN-001234-00 Installation and Upgrade on Windows Server 2008/2012 When the Secondary Server is Physical You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: [email protected] Copyright © 2013 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc. Contents About This Book 5 1 Introduction 9 vCenter Server Heartbeat Concepts 9 vCenter Server Heartbeat Protection 11 vCenter Server Heartbeat Communications 14 vCenter Server Heartbeat Failover Processes 16 2 Implementation 21 vCenter Server Heartbeat Implementation 21 Environmental Prerequisites
    [Show full text]