Attachment 12 TACLAN SOW Final.pdf

Section C – Statement of Work

USSOCOM C4I Production-Tactical Local Area Network (TACLAN)

10 February 2011

1.0 Introduction

2.0 Background and Historical Summary

3.0 Summary of Effort

3.1 TACLAN Initial Production Suites (IPS)

3.2 TACLAN Production/Lifecycle Support……………………………………………………….. 7

3.3 Equipment Lifecycle Support……………………………………………..……………………..8

3.4 System/Equipment Information Listing…………………………………………………………8

4.0 Applicable Conditions

4.1 Locations for Work Performance

4.2 Contractor Security…………………………………………………………………………….9

4.3 Security Management Support

4.4 Compliance with DoD / USSOCOM IT Standards

4.5 IT Service Management

4.6 IT Operations Management

4.7 Contractor Travel

5.0 ITMO

6.0 Contractor Responsibility

6.1 Facilities Location

6.2 Contractor Support

7.0 TACLAN Systems

7.1 TACLAN Systems Engineering and Design

7.1.1 Post Award Conference/ System Requirements Review (SRR)

7.1.2 Preliminary Build Review (PBR)

7.1.3 Critical Build Review (CBR)

7.2 Engineering and Integration

7.3 Software Validation

8.0 Contractor Integrated Logistics and Technical Susta inment Support

8.1 Integrated Logistics Support (ILS) Plan

8.2 Logistics Support

8.3 Failure and Maintenance Status Reporting ……………………………………………… 15

8.4 Provisioning and Spares

8.5 Technical Manuals

9.0 TACLAN Program Management

9.1 Monthly Funds Status Report……………………………………………………………… 16

9.2 Integrated Product Teams (IPT)

9.3 Conferences, Reviews, and Audits

9.4 In-Progress Review (IPR)

9.5 Program Management Reviews (PMR)

9.6 Safety Assessment Report (SAR)

10.0 TACLAN Management Support

10.1 Planning and Analysis

10.2 Project Management

10.3 Requirements Definition

10.4 TACLAN Design Specification

10.5 Initial Equipment Installation Planning, Scheduling, and Coordination

10.6 Asset Tracking and Management

10.7 TACLAN Software License Management

10.8 Configuration Management

10.9 Change Management

10.10 Implementation and Migration Management

10.11 Release Management

10.12 Validation, Integration, and Testing

10.12.1 Coordinate Maintenance of Test Environment Reflective of TACLAN

10.12.2 TACLAN Testing Requirements

10.12.2.1 TACLAN Test Plans……………………………………………………………………...23

10.12.2.2 Production Qualification Testing (PQT)…………………………………………….…. 23

10.12.2.3 Baseline Acceptance Testing (BAT)……………………………………………….….. 23

10.12.2.4 Test Reports………………………………………………………………………….….. 23

10.13 Service Delivery Document Management

10.14 TACLAN New Equipment Training (NET)

10.15 Contractor Continual Service Improvement Management

10.16 Independent Performance Assurance and Benchmarking…………………………….. 25

11.0 Contractor Information Assurance Coordination

11.1 TACLAN General Information Assurance

11.2 TACLAN Intrusion Detection Services

11.3 TACLAN Security Compliance and Management Services

11.4 TACLAN Information Security Management Services

11.5 TACLAN Physical Security Management Services

12.0 TACLAN Operation Management Support

12.1 TACLAN On-Site Technical Support

12.1.1 Incident Support

12.1.2 Problem Support…………………………………………………………………………..29

12.1.3 Request for Changes

13.0 System Engineering/Studies

14.0 Software Baseline Management

15.0 TACLAN Sustainment Training

16.0 TACLAN Transition-Out Services (End-of-Contract)

Appendix A

1.0 Introduction

Tactical Local Area Network (TACLAN) is a modular, scalable family of computer network equipment and workstations, providing the tactical equivalent of United States Special Operations Command (USSOCOM) Command, Control, Communications, Computers and Intelligence Automated System (C4IAS) and Special Operations Command Research, Analysis and Threat Evaluation System (SOCRATES) networks. TACLAN extends Command, Control, Communications, Computers, and Intelligence (C4I) capabilities and the Special Operations Forces (SOF) Information Environment (SIE) to tactical SOF locations to accomplish the timely exchange of information between deployed and garrison SOF headquarters, and main operating locations, while facilitating liaison and coordination with regional combat commands, Services, Department of Defense (DOD) and national agencies concerning SOF operational support.

TACLAN shall scale to accommodate network resizing to meet mission requirements. The TACLAN program’s primary operational mission is to provide the tactical user with flexible interfaces to communications, databases, and mission applications that will collectively extend the equivalent fixed base garrison C4I Surveillance and Reconnaissance (C4ISR) architecture.

The TACLAN Family of Systems (FoS) currently includes: TACLAN Suite (Full and C2), Mission Planning Kit (MPK), Field Computing Device (FCD), Coalition Local Area Network (C-LAN), Radio Over Internet Protocol (RoIP) Kit, and Full Motion Video (FMV) Video Distribution Hub – Lite (VDH-Lite),hereafter referred to as the TACLAN FoS.

Numerous joint, service, and SOF deployed automation programs/efforts operate on the TACLAN FoS to gain connectivity to SIE networks and associated SIE services. The TACLAN program merges numerous deployed SOF automation efforts into a consolidated infrastructure program consisting of hardware and SOF validated software applications that comply with DoD and USSOCOM policies and directives.

All TACLAN program efforts shall be coordinated with the USSOCOM IT Management Office (ITMO), a J6 division responsible for providing oversight and management of the performance of the SOF Information Technology Enterprise Contracts (SITEC) using the Information Technology (IT) Infrastructure Library (ITIL) framework. Please see Appendix A for complete information on the ITMO.

2.0 Background and Historical Summary

USSOCOM is comprised of: a headquarters at MacDill Air Force Base (AFB), FL; one sub-unified command—the Joint Special Operations Command (JSOC)—at Fort Bragg, NC; and four Component Commands: the United States Army Special Operations Command (USASOC) at Fort Bragg, NC; the Naval Special Warfare Command (NAVSPECWARCOM) at Coronado, CA; the Air Force Special Operations Command (AFSOC) at Hurlburt Field, FL; and the Marine Corps Forces Special Operations Command (MARSOC) at Camp Lejeune, NC. In addition, each of the seven Combatant Commanders has an attached Theater Special Operations Command (TSOC) that provides theater-related special operations strategy and planning efforts.

The SIE is USSOCOM’s worldwide IT infrastructure. The SIE encompasses all SOF IT assets throughout the Command within the Continental United States (CONUS) and Outside the Continental United States (OCONUS), down to the deployed sensor and shooter. The SIE houses USSOCOM’s TACLAN resources and related enterprise services, as well as SOF’s global terrestrial and satellite connectivity. The current SIE vision and concept of operations has been documented by USSOCOM Communications Systems Directorate (J6)/Chief Information Officer (CIO) and is considered an underpinning set of IT capabilities required for the SOF community.

The TACLAN concept originated in May 1998 and the TACLAN Operational Requirement Document (ORD) was approved in June 2001. The TACLAN FoS consists primarily of Commercial Off-the-Shelf (COTS) and/or Government Off-the-Shelf (GOTS) equipment and software applications that are compliant with industry and DOD standards. TACLAN implements an open systems computing architecture in order to minimize interoperability issues.

TACLAN interconnects all deployed SOF elements from the smallest team to a Joint Special Operations Task Force (JSOTF) headquarters with one seamless network to share information and facilitate responsive knowledge based decisions. It supports connectivity to interconnect liaison elements and tactical teams to the main network, including the fielding of FCDs for tactical teams. Figure 1 depicts the notional high level TACLAN functional segments/components shown connected to the Special Operations Forces Tactical Assured Connectivity System (SOFTACS) transport media.

Figure 1- TACLAN Functional Components

Multiple enhancements have been approved since TACLAN’s inception that enables net-centric warfare, interconnecting deployed SOF elements through USSOCOM’s mobile IT infrastructure and applications. These elements can include soldiers and teams or JSOTFs and can also comprise the tactical equivalent of a garrison network (NIPRNet, SIPRNet and JWICS).

Unless otherwise specifically identified, throughout the remainder of this document, all references to USSOCOM, USSOCOM enterprise, and enterprise-wide shall be considered to be all inclusive of all IT infrastructure hardware, software, and networks, and applications utilized within USSOCOM, USASOC, NAVSPECWARCOM, AFSOC, MARSOC, JSOC, and TSOCs, as well as all related sites and facilities. In addition, all references to the TACLAN shall be considered to be all inclusive of all infrastructure hardware, software and networks, and applications utilized within the TACLAN environment.

3.0 Summary of Effort

The Contractor shall provide TACLAN Systems Production, Logistics, and Sustainment Support Services in accordance with the requirements specified in this Statement of Work (SOW). The Contractor shall manage, support, service, and maintain all hardware, and personnel associated with the TACLAN FoS. The Contractor shall acquire all components necessary to fabricate/produce the TACLAN FoS, integrate software baseline updates, integrate hardware and software components, support baseline acceptance testing (BAT), accreditation testing (in collaboration with the Enterprise SOF Integration Facility (SIF), and HQ USSOCOM J6), conduct training, and field the TACLAN components.

3.1 TACLAN Initial Production Suites (IPS)

The Contractor shall provide TACLAN full suites in accordance with SOW and attachments.

The Contractor shall establish/start-up a facility, develop New Equipment Training (NET) training materials, update attachments 1-6 as required, provide BAT support to the Government, support meetings/design reviews, develop the Provisioning and Spares List (PSL), and migrate current TACLAN software baseline as necessary.

The Contractor shall provide one year of lifecycle support as described in section 3.2 for all IPS.

After one year the systems shall be supported under legacy equipment (reference section 3.3)

The Contractor shall include all start-up costs associated with satisfying the requirements in this SOW in its entirety. The IPS delivery order shall include procurement, integration, fabrication, test, configuration management (CM), Information Assurance (IA), security and communication security (COMSEC) management, conduct NET, unique identifier (UID), shipping, fielding, sparing, depot maintenance/repair (excluding non-warranty repairs), integrated logistics support (ILS), ITMO and SITEC Associate Contractor Agreements (ACAs) and Operating Level Agreements (OLAs) to support trouble ticket and change request resolution, and all other tasks for complete lifecycle and customer support. Contractor shall prepare all Certification & Accreditation (C&A) documentation required by USSOCOM in order to receive an authority to operate (ATO).

3.2 TACLAN Production/Lifecycle Support

The Contractor shall provide TACLAN FoS equipment in accordance with the SOW and attachments. The TACLAN Production and Lifecycle Support shall include, for hardware;

engineering, design, procurement, integration, fabrication, test, Program Management and IPT support (including travel, reference section 9.2), CM, IA, security and COMSEC management, component obsolescence and end of life management, NET, UID, shipping, fielding, sparing, depot maintenance/repair (excluding non-warranty repairs), ILS, COTS IT-industry trend analysis/forecast, ITMO and SITEC ACAs and OLAs in support of trouble ticket and change request resolution, and all other tasks for complete lifecycle and customer support. The Contractor shall provide one year of lifecycle support for all TACLAN FoS (excluding laptops and FCDs). After one year, the system shall be supported under legacy equipment (reference section 3.3)

The TACLAN Contractor shall provide USSOCOM with technology insertion/refresh assessments and recommendations for TACLAN FoS, [CDRL A0001]. Assessments and recommendations shall include, but not limited to:

a. Increase system modularity, flexibility and scalability.

b. Improve transportability by reducing the equipment footprint and decreasing set-up time.

c. Improve supportability.

d. Improve performance.

e. Improve training.

f. Improve design stability.

g. Improve security.

h. Increase flexibility and speed of component replacement.

i. Lower total ownership cost.

3.3 Equipment Lifecycle Support

For Legacy TACLAN Suites and segments, including those fielded prior to contract award, and associated software baselines, the Contractor shall provide all labor, material, and travel to support ongoing hardware/equipment replenishment as fielded hardware/equipment requires replacement or reaches end of life; reporting and management; follow-on/sustainment training;

shipping; non-warranty repair; spares; depot repair/ILS; ITMO and ACA/OLA support, and the SOW. This support includes equipment ordering and purchase, receipt from the manufacturer, and shipping to the requesting unit. The Contractor shall also provide for associated engineering, acquisition, information assurance, configuration and asset management, training, and related services as needed. Current legacy TACLAN suite hardware is located at Attachment 11 and shall be updated throughout the contract performance period by the contractor. Any repair action determined to require 65% or more of that item’s replacement cost shall be considered beyond economical repair and shall result in replacement of the affected part or replaceable unit.

3.4 System/Equipment Information Listing

The Contractor shall update Attachment 11, List of Legacy TACLAN Suites, throughout the contract performance period. As the Contractor fields new production systems/equipment, this information will be added to the System/Equipment Information Listing. The listing shall include, but not be limited to, System/Equipment nomenclature, Serial Number, Date Initially Fielded, Projected/Actual Capital Equipment Replacement (CERP) date as applicable, fielding location, gaining unit, Training Dates (NET/Sustainment), and any other pertinent information (CDRL A0002).

4.0 Applicable Conditions

The conditions that affect the TACLAN acquisition are described below.

4.1 Locations for Work Performance

Unless approved in advance by the Government, all production, warehousing and support shall be at the TACLAN Contractor’s facilities. The Government will make available the SIF, to assist in BAT and system integration testing, live Secure Internet Protocol Router Network (SIPRNet) and Joint Worldwide Intelligence Communication System (JWICS) connectivity testing, and systems engineering demonstrations as required. Initial and final integration testing will occur at the Contractor facility as network connectivity permits.

4.2 Contractor Security

Security will be in accordance with the contract DD254. Many Contractor personnel supporting this contract shall require a Top Secret (TS)/Secure Compartmentalized Information (SCI) clearance. The Contractor shall have access to the Non-Secure Internet Protocol Router Network (NIPRNet), SIPRNet, JWICS computer systems at Government facilities; and SIPRNet access at Contractor facilities. NIPRNet access from Contractor facilities, if required, shall be subject to approval by USSOCOM.

4.3 Security Management Support

The Contractor shall provide security management support. Typical security management support efforts include, but are not limited to, performing classified document control functions, classified materials inventories, COMSEC account management, program access requests, preparing and monitoring personnel training, indoctrination and debriefing agreements, and maintaining and using security-related databases.

4.4 Compliance with DOD / USSOCOM IT Standards

The Contractor shall perform all service delivery responsibilities in compliance with all DOD and USSOCOM IT standards, direction, and guidance, as well as other applicable service delivery documents.

4.5 IT Service Management

The Contractor shall utilize the hardware and software provided by USSOCOM in carrying out IT Service Management services for TACLAN. The Contractor shall use the SIE Standard Trouble Ticket and IT Service Management system which resides on the USSOCOM LAN. The Contractor is responsible for obtaining SIPRNET access for connectivity to the USSOCOM LAN.

Until SIPRNET is available at the Contractor’s facility, the Government will provide the contractor access to the Command LAN at USSOCOM HQ. The contractor also may arrange, via OLAs,to use remote telephone and unclassified email access via the SITEC Service Desk to provide the connectivity, dispatch, and updates to the ITSM tickets for incidents, problems, changes, and other ITSM related tickets. If OLAs are not established, contractor will be responsible for updating ITSM tickets at government facility where access can be obtained.

4.6 IT Operations Management

Due to security requirements, the Contractor shall use USSOCOM's suite of service operations management and information assurance management equipment and software tools for performing all day-to-day interactions and interfaces with the SIE. The Contractor shall not install and/or utilize any software or hardware within the SIE that is not authorized for use by

USSOCOM.

4.7 Contractor Travel

The contractor staff may be required to travel to Continental United Stated States (CONUS) and Outside Continental United States (OCONUS) locations, including war zones. For any travel accomplished on behalf of the Government, the Contractor shall provide a trip report within ten

(10) business days of return (CDRL 0003).

The Contractor shall use the Synchronized Predeployment and Operational Tracker (SPOT) web-based system, at http://www.dod.mil/bta/products/spot.html, to enter and maintain the data as per DFARS 252.225-7040.

5.0 ITMO

Other SITEC IT Service Area providers (e.g., (Enterprise Network, Applications, Specialty Service Providers, etc.) may require Contractor consultation and support as assigned and approved by the TACLAN PM.

The Government may award additional contracts for any of the enterprise-wide services in support of the USSOCOM SIE. In that event, the Contractor shall cooperate with the selected service providers. Additional contracts may include the following services:

� SIE asset inventory audits � USSOCOM customer community communications, marketing, and outreach services � Independent verification and validation (IV&V) and quality assurance activities � Additional ITMO management or project support as required

6.0 Contractor Responsibility

The Contractor shall provide planning, acquisition, engineering, production, sustainment, logistics, training, and IA services during the full lifecycle for the TACLAN FoS in conjunction with other SITEC contractors/vendors. The Contractor shall establish and/or maintain a security-compliant facility for the execution of responsibilities under this contract. The Contractor shall facilitate USSOCOM’s ongoing ability to effectively and efficiently optimize delivery, performance and maintenance of the entire TACLAN FoS.

Unless otherwise stated within this SOW, all tasks, activities, responsibilities, and obligations specified as a Contractor service requirement only applies to operations and management of the hardware software, and services identified within this SOW as belonging to the TACLAN Service Area and related environment interconnectivity. In no case will the Contractor be responsible for managing or performing work, defining or implementing processes, or for providing any resources or recommendations pertaining to any other IT Service Area other than TACLAN Services.

In the remainder of this SOW, all of the relevant IT Service Management activities shall be based upon the Information Technology Infrastructure Library Version 3 (ITIL v3) guidelines.

USSOCOM considers these processes and functions to be essential services for the effective delivery of IT services and equipment across the command. These functions are applicable to each SITEC IT Service Area, including those that support TACLAN, and must be uniformly implemented, applied, maintained, and managed enterprise-wide across all USSOCOM geographies / sites to ensure that all of USSOCOM’s SIE information technology environments are supported within common and consistent IT lifecycle service and process frameworks (e.g., ITIL; Capability Maturity Model Integration (CMMI).

6.1 Facilities Location

The Contractor shall be within a 25 mile drive of MacDill AFB, FL in order to facilitate frequent interaction with USSOCOM stakeholders. Manufacturing may take place outside the local area.

6.2 Contractor Support

The Contractor shall perform all delivery, integration, and testing activities in close coordination and cooperation with the TACLAN PM, the ITMO, and the other SITEC IT Service Area providers to ensure security and operational integrity of all TACLAN hardware and software components as detailed in this SOW.

The TACLAN Contractor’s team shall include key senior representatives responsible for performance of the Contractor tasks and activities as specified in this SOW. The Contractor shall:

• Produce and support TACLAN FoS IAW paragraph 3 above

• Manage TACLAN product delivery in accordance with the respective TACLAN performance metrics, including Service Level Agreements (SLAs), Associate Contractor Agreements (ACAs), and Operating Level Agreements (OLAs)

• Design and develop TACLAN delivery processes in collaboration with the TACLAN PM and ITMO

• Perform lifecycle TACLAN Production Management activities in accordance with USSOCOM’s enterprise-wide policies and procedures using USSOCOM’s designated change management tools and enterprise processes

• Perform integration and testing activities in close coordination and cooperation with the TACLAN PM, the ITMO, and other SITEC IT Service Area providers to ensure security and operational integrity of all hardware and software components within the TACLAN

• Provide Level 3 technical support and operations management coordination with the other SITEC IT Service Area providers.

7.0 TACLAN Systems

7.1 TACLAN Systems Engineering and Design

The Contractor shall design the TACLAN FoS to satisfy evolving user requirements. The Contractor shall develop and institute a Systems Engineering Plan detailing the Contractor’s process for system engineering (CDRL A0004).

7.1.1 Post Award Conference/ System Requirements Re view

(SRR)

The Contractor shall conduct a Post Award Conference (PAC) and Systems Requirements Review (SRR) at the Contractor's facility no later than (NLT) 15 days after contract award. The purpose of this conference is to ensure a common understanding between the Government and the Contractor of the overall contract requirements for TACLAN and incorporate feedback and comments as part of their planning efforts. The Contractor shall develop and brief the Government on the TACLAN Program Management Plan (PMP) (reference section 9), which shall include schedule, integration, accreditation, and test activities (CDRL A0017). The Contractor shall prepare agendas, briefings and minutes for the reviews In Accordance With

(IAW) CDRL A0005.

7.1.2 Preliminary Build Review (PBR)

The Contractor shall conduct a PBR no later than 60 days after contract award. After that time, PBRs shall occur as required for each new TACLAN baseline release. At the initial PBR for the IPS, the Contractor shall formalize the hardware/software design in its proposal. Informal Build Reviews may be held at times agreed to by the Government and the Contractor. The Contractor shall prepare agendas, briefings (to include design documentation) and minutes for the reviews IAW [CDRL A0005].

7.1.3 Critical Build Review (CBR)

The Contractor shall finalize the production design at CBR within 30 days after the PBR. At the CBR, the Contractor shall formally report the results of tests and address recommended hardware/software design changes, including trade-off impacts, approved by the Government at PBR. Government approval of the hardware/software design is required before the Contractor is authorized to proceed with IPS hardware fabrication/integration and software integration/accreditation. The Contractor shall incorporate all hardware/software design changes approved by the Government during the CBR. The Contractor shall prepare agendas, briefings (to include design documentation) and minutes for the reviews IAW [CDRL A0005].

If, after Critical Build Review (CBR), the Contractor needs to change or modify the TACLAN design, they shall prepare and submit engineering change proposals (ECP) [CDRL A0006] for technologies and/or potential design changes to the Government for approval. As an addendum to ECPs, the Contractor shall provide implementation plans for migration, training and operations, and maintenance requirements, as required.

7.2 Engineering and Integration

The Contractor shall integrate Government approved COTS/GOTS software/hardware into a stable and accredited TACLAN baseline. Software integration shall be limited to the design of menu systems and “scripts” written to integrate and manage the installation of the various COTS and GOTS applications into the TACLAN FoS via a universal serial bus (USB) hard drive.

The Contractor shall provide a complete system administration guide (SAG), installation manual, operation and maintenance (O&M) manual, version description document (VDD), software requirements specification (SRS), software product specification (SPS) and documentation for the software/hardware baseline. The Contractor shall be responsible for the preparation of all required IA, DIACAP, and CM documentation required by USSOCOM CIO to receive an ATO on the SIE. The Contractor shall support the following levels of change to the TACLAN baseline:

• Major software Releases and hardware upgrades or replacements, normally containing large areas of new functionality. A major upgrade or Release usually supersedes all preceding minor upgrades, Releases and emergency fixes.

• Minor software Releases and hardware upgrades, normally containing small enhancements and fixes, some of which may have already been issued as emergency fixes. A minor upgrade or Release usually supersedes all preceding emergency fixes.

• Emergency software and hardware fixes, normally containing the corrections to a small number of known problems.

The Contractor shall utilize a software development lifecycle (SDLC) process that is compliant with Software Engineering Institute Capability Maturity Model Institute (SEI-CMMI) Level-3, or an industry-recognized equivalent. The Contractor shall maintain these processes throughout the life of the contract.

7.3 Software Validation

The Contractor shall validate documents and programming materials compliance and accuracy with the Software Requirements Specification (SRS) [CDRL A0007]. This specification shall address requirements for both legacy and production systems. The Contractor shall provide a draft TACLAN SRS within 30 days after the Preliminary Build Review (PBR).

The Contractor shall index and cross reference the applications and structure of the integration effort, and describe the scripts developed and employed in a Software Product Specification (SPS) [CDRL A0008]. The Contractor shall prepare and provide the draft TACLAN SPS within 60 days of approval of the SRS.

The Contractor shall provide a Version Description Document (VDD) [CDRL A0009] that defines the software release and the hardware baseline being supported.

Following the completion of baseline acceptance testing (BAT), user evaluation, and accreditation, and upon official release, the Contractor shall deliver a master copy of the latest software baseline to the TACLAN PM on USB hard drive [CDRL A0010]. The Contractor shall ensure copies of the baseline are provided to all currently fielded TACLAN components on USB hard Drive [CDRL A0010].

8.0 Contractor Integrated Logistics and Technical S ustainment

Support

The Contractor shall provide full life-cycle support for the TACLAN FoS IAW with section 3.

The Contractor shall provide logistics support and, as required, warehousing for TACLAN systems and components until shipped to a Government-designated location (e.g., SOFSA).

The Contractor shall provide logistics support for repair of warranty and non-warranty items.

The Contractor shall provide depot-level repair of failed components. The Contractor shall provide necessary materiel to the user organization and provide the logistics for materiel repair.

The Contractor shall ship replacement parts to the user’s unit and verify failures of parts returned by the user.

8.1 Integrated Logistics Support Plan (ILSP)

The Contractor shall plan for a two level maintenance concept (Organizational & Depot). The Contractor shall provide an ILSP [CDRL A0011] to the Government for review and approval.

The TACLAN logistics support concept shall be based upon a modular system design that provides for field replacement of electronic equipment items and software baseline upgrades.

Upon removal, failed items shall be returned to the Contractor. The Contractor ILSP shall address all issues associated with, but not limited to, sparing, provisioning, warranty administration, technical support, replacement parts, inventory management and UID.

8.2 Logistics Support

The Contractor shall provide Contractor Logistics Support (CLS) in support of legacy and production TACLAN systems. Once notified of a hardware failure, the Contractor shall provide the replacement item to the user organization. The Contractor shall ship the replacement item not later than close of business the following business day after being notified of the failure. The user organization shall then send the failed item to the TACLAN contractor. Through the CLS, the Contractor shall also provide depot-level evaluation and repair/disposition.

The Contractor shall coordinate with Property Control and/or the Property Manager at each gaining unit to establish and maintain property accountability for fielded equipment, to include COMSEC equipment.

The Contractor shall provide Level 3 reachback support, which may require contractor personnel dispatch to any USSOCOM location with a fielded TACLAN environment, both CONUS and OCONUS, including but not limited to any combination of USSOCOM Component and TSOCs facilities, to include designated areas of combat operations.

8.3 Failure and Maintenance Status Reporting

The Contractor shall document and report on all repair actions (reference sections 3.1, 3.2 and 3.3), to include trend analysis, occurring in a Failure and Maintenance Status Report [CDRL A0012]. The Failure and Maintenance Status Report shall include a listing of items returned (part number, serial number, description), reason for return (failed function), point of origin, dates received, item(s) repaired, repair action taken, and date repairable items were returned to the contractor. The Failure and Maintenance Status Report will reflect warranty and non-warranty items. The Contractor shall provide quarterly submissions of the Failure and Maintenance Status Report starting no later than 90 days after contract award for legacy systems and for new production TACLAN systems.

8.4 Provisioning and Spares

The Contractor shall provide Provisioning and Spares Lists (PSL) for all TACLAN systems. The Contractor shall provide a complete PSL with recommended on-board spares and pipeline spares [CDRL A0013]. The Contractor provided PSL shall be updated as required but at least annually. At a minimum, the PSL shall include part number, Commercial and Government Entity (CAGE) Code, and National Stock Number (NSN) (if applicable). The Contractor may use on-board spares levels to achieve required reliability. The Contractor shall recommend final determination of sparing strategies and actual spares quantities which shall be based on sparing analysis of actual procurement quantities of legacy and TACLAN Family Systems procured under this contract. The Contractor shall hold pipeline spares and repair parts at the Contractor's facility that shall be distributed as required to support organizational-level supply requisitions/demands.

8.5 Technical Manuals

The Contractor shall provide initial delivery of the O&M Manual for production systems [CDRL A0014]. Upon completion of BAT, the Government may provide additional comments for incorporation into the O&M Manual. The Contractor shall structure the O&M Manual so it can be easily updated as required by follow-on configuration changes.

The Contractor shall deliver one O&M Manual with each production TACLAN Suite or segment.

The Contractor shall also deliver an Installation Guide [CDRL A0015], VDD [CDRL A0009], and System Administrator Guide (SAG) [CDRL A0016] with each production TACLAN suite or segment.

The Contractor shall ensure the O&M Manual includes:

• equipment technical data

• equipment setup and installation procedures

• detailed menu field definitions, warnings and precautions

• all authorized operator level tasks/procedures and principles of operation

• all authorized organizational-level testing

• fault isolation

• support and test equipment

• removal and replacement procedures

• equipment warranty handling instructions

The Contractor shall provide updated documents whenever hardware or software components change.

9.0 TACLAN Program Management

The Contractor shall develop and implement a Program Management Plan (PMP) [CDRL A0017] that clearly defines how the TACLAN Program will be managed. The Contractor shall submit the PMP for Government approval. The PMP shall be consistent with the Contractor’s standards, detailing the nature, timing, and integration of all contract activities. At a minimum, the plan shall describe how/when the Contractor shall initiate vendor and subcontractor purchase orders and agreements, inspect/burn-in of received articles, fabricate in-house components, assemble system elements, and test and package final systems for delivery.

Additionally, the plan shall address system performance, hardware/software integration, IA, CM, C&A, testing, fielding, systems engineering, ILS, training, ITMO/SITEC ACA interaction and coordination. The Contractor shall implement an integrated master plan/schedule, included in the PMP, clearly defining all the tasks necessary to satisfy the requirements in this SOW.

The Contractor shall support the efficient and effective operations of the TACLAN program as well as prepare for, and participate in, critical review activities. Program-related meetings shall include, but are not limited to, those described in the paragraphs below. The Government may, at its option, be supported by designated support contractors at any meetings, conferences, reviews, audits, or inspections.

9.1 Monthly Funds Status Report

The Contractor shall prepare and submit a Monthly Funds Status Report [CDRL A0018].

Reports shall include a discussion of all issues, including suggested steps for mitigation or resolution.

9.2 Integrated Product Teams (IPT)

The Contractor shall participate in and support IPTs that include major sub-contractors and USSOCOM representatives managing and overseeing the design and integration effort for

TACLAN to ensure a quality product is delivered on schedule, meeting contractual and SOW requirements. The Contractor shall support four TACLAN IPT meetings or Conferences per year that requires CONUS travel. In addition, the Contractor shall support all Government required meetings and conferences that occur locally. The Contractor shall prepare agendas, briefings, and minutes in support of these meetings/Conferences [CDRL A0005].

9.3 Conferences, Reviews, and Audits

The Contractor shall conduct conferences, reviews, and audits and shall respond to all Government questions, comments, and issues. The Contractor shall host TACLAN-related meetings, prepare agendas and briefings, and provide minutes, as requested [CDRL A0005].

9.4 In-Progress Review (IPR)

The Contractor shall conduct IPRs as required to address technical or program issues identified by either the Government or the Contractor. The Contractor shall conduct all IPRs at the Contractor's facility unless otherwise directed by the Government, and IPRs shall be structured to reflect the scope of the production and ongoing Integrated Logistics Support (ILS) efforts. The Contractor shall prepare agendas, briefings and minutes for the reviews IAW [CDRL A0005].

9.5 Program Management Reviews (PMR)

The Contractor shall conduct PMRs with the Government at the Contractor's facility every quarter until after delivery of the first production system. After that time, the Contractor shall conduct PMRs at the Government's request. During PMRs, the Contractor shall report on progress of tasks covered by this SOW, problems encountered and/or anticipated, and corrective action plans. The Contractor shall prepare agendas, briefings and minutes for the reviews IAW [CDRL A0005].

9.6 Safety Assessment Report (SAR)

The Contractor shall perform a safety assessment of production TACLAN systems and prepare and submit to the Government for approval a Safety Assessment Report (SAR) [CDRL A0019].

The Contractor shall ensure the SAR evaluates the safety risks being assumed prior to test or operation of the system and provide specific controls or precautions to be followed.

The Contractor shall maintain a hazard tracking log and Material Safety Data Sheets for all hazardous materials or hazardous wastes, if any are identified.

The Contractor shall deliver the SAR to the Government in conjunction with delivery of the first production system.

The Contractor shall update the SAR as required throughout the entire lifecycle of the TACLAN FoS.

10.0 TACLAN Management Support

The Contractor shall provide TACLAN Management Support to USSOCOM for the service design management functions as described in the sub-sections below.

10.1 Planning and Analysis

The Contractor shall research, analyze, plan, coordinate, and recommend software, system, server, storage, and related process and services options and alternatives that offer opportunities to improve efficiency and effectiveness of TACLAN service delivery to meet USSOCOM's mission requirements.

The Contractor shall interact with the TACLAN PM and ITMO to identify improvement opportunities, analyze and solve problems, and develop plans and specifications for TACLAN processes and systems that meet requirements of end-users.

10.2 Project Management

The Contractor shall perform all project lifecycle management activities in support of TACLAN Project Management Services in accordance and compliance with applicable USSOCOM policies and procedures, and utilize applicable tools specified by USSOCOM.

The Contractor shall ensure that appropriate project success criteria are defined and can be measured objectively against achievement of goals and justify their decisions to move ahead, correct, or terminate a project.

The Contractor shall perform all project planning, execution, and closure phases in accordance with applicable USSOCOM and DOD requirements.

10.3 Requirements Definition

The Contractor shall perform all requirements definition lifecycle activities to ensure that it has gathered and documented sufficient information to ensure that USSOCOM requirement parameters are accurately reflected in the TACLAN Contractor’s requirements documentation.

10.4 TACLAN Design Specification

The Contractor shall develop, maintain, and update as required a TACLAN Design Specification that meets or exceeds the performance and functional requirements documented in the TACLAN System Specification (TSS). Within 30 days after CBR, the Contractor shall deliver a draft TACLAN Design Specification [CDRL A0020]. Final delivery of the TACLAN Design Specification shall be prior to full rate production. The Contractor shall be responsible for updating the TACLAN Design Specification as baseline changes are approved by the Government.

10.5 Initial Equipment Installation Planning, Sched uling, and Coordination

The Contractor shall provide initial TACLAN system deployment installation planning, scheduling, and coordination of services to the Government and all affected SIE IT service providers. The Contractor shall implement installation planning and scheduling policies and procedures for managing new and legacy TACLAN equipment, products, and services, which align with USSOCOM enterprise-wide policies and procedures.

10.6 Asset Tracking and Management

The Contractor shall record TACLAN system asset data records, for both legacy and new production systems and equipment, as part of a Contractor asset management system to ensure that all of the Government’s TACLAN Service Area asset data is captured, accurately recorded and updated on a timely basis throughout the entire asset lifecycle. This asset management system will be available for the Government to view on either the NIPR or SIPR networks. This includes all newly procured, as well as remanufactured or refurbished, equipment and newly licensed software which will incorporated into any TACLAN system (e.g., acquisition dates, hardware type/model, software and software licenses, vendor name, suite number, serial numbers, fielding data, CERP/replacement date, etc), manufacturer, asset identification number, asset location, network (e.g., NIPR, SIPR), associated software cross-walk, patch status, ownership information (contractor/Government—lease/purchase), asset cost information, maintenance information and history including the age of the asset, warranty information, transaction edit history (e.g., locations, billing and user), other billing information (e.g., Government-specific information), and IA compliancy status.

The Contractor shall uniformly and consistently use and comply with maintaining and updating all TACLAN asset records whenever any change is introduced into any USSOCOM TACLAN production environments. [CDRL A0021].

The Contractor shall provide TACLAN asset inventory control (including hardware and software license attributes), hardware and software asset lifecycle planning and management (e.g., timing of asset refresh, asset disposition), software version management, and identify opportunities for refresh or insertion of technology.

10.7 TACLAN Software License Management

The Contractor shall initially record software license/maintenance data repository provided by USSOCOM for enterprise-wide use for recording and tracking information regarding TACLAN-specific software licensing and support agreements (e.g., vendor name, software name and version, number of authorized users and/or devices covered, licensing fees, commencement and expiration date, etc.) [CDRL A0022]. The ITMO is responsible for establishing this repository and each SITEC IT Service Area provider, including the TACLAN Contractor, will be responsible for monitoring and managing the records that reflect the SITEC assets under their control.

10.8 Configuration Management

The Contractor shall perform all TACLAN Configuration Management activities for all TACLAN equipment and software until delivery, which shall be performed in accordance and compliance with USSOCOM’s enterprise-wide configuration management policies and procedures. The Contractor shall use USSOCOM’s configuration management system to record all TACLAN component configurations and all subsequent component configuration changes and coordinate all changes with the other SITEC IT Service Area providers. The Contractor shall record all TACLAN asset parameters as specified in Configuration Management (CM) requirements. The Contractor shall maintain an As-Built Configuration database, allowing requirements traceability of all hardware and software. The Contractor shall produce and maintain an As-Built Configuration list for each delivered item.

The Contractor shall include a logical model of TACLAN devices and their relationships by identifying, controlling, maintaining and verifying installed hardware, software, and documentation (i.e., maintenance contracts, SLA documents, etc.). The Contractor shall use the Configuration Management System to account for all TACLAN Assets and configurations to provide accurate information on configurations and provide a sound basis for Incident, Problem, Change and Release Management and to verify configuration records against the infrastructure and correct any exceptions [CDRL A0023].

The Contractor shall define, document, and manage all TACLAN equipment configurations throughout the service management lifecycle and shall manage and update the baseline of these configurations. For the initial deployment of a TACLAN suite or segment, the Contractor shall install, configure, test, and fully commission the TACLAN system and related end-user infrastructure equipment and software regardless of geographic location (i.e., CONUS and OCONUS including theatres of operations). The Contractor shall provide and coordinate delivery of TACLAN system configuration updates to other SITEC IT Service Area providers which are required subsequent to initial delivery and commissioning of TACLAN equipment to perform reconfiguration(s) and update respective configuration management database records.

10.9 Change Management

The Contractor shall perform all TACLAN change activities in accordance and compliance with USSOCOM’s enterprise-wide change management standardized methods and procedures for the efficient and prompt handling of all IT change requests (e.g., submitting, reviewing, prioritizing, approving, recording, managing the processes, etc.). The Contractor shall ensure that any change to be introduced into any TACLAN production environment has been tested and verified for integration compatibility, security, functionality, and performance in order to minimize the impact upon service quality.

The Contractor shall establish standardized methods and procedures for the efficient and prompt handling of all TACLAN related change requests (e.g., submitting, reviewing, prioritizing, approving, recording, managing the processes, etc.), in order to minimize the impact of change upon TACLAN service quality and consequently improve the day-to-day operations of

USSOCOM.

The Contractor shall incorporate USSOCOM-specified ITIL best practice processes and procedures for managing the introduction and implementation of all TACLAN-related changes, which include interfaces with the Release Management, Configuration Management, and Asset Management, Incident Management and Problem Management processes. The Contractor shall coordinate and obtain approval for its change management activities with the TACLAN PM and ITMO.

10.10 Implementation and Migration Management

The Contractor shall accomplish the initial installation of a TACLAN production system in coordination with the other SITEC IT Service Area providers. The Contractor shall adhere to and comply with implementation and migration management processes to be used enterprise-wide for the installation of new and upgraded TACLAN components.

10.11 Release Management

The Contractor shall implement, utilize, adhere to, and comply with USSOCOM-specified release management processes for integrating and testing new or reconfigured TACLAN equipment and/or software. The Contractor shall use a holistic process approach in performing Release Management activities, which includes and incorporates all of the technical and non-technical interdisciplinary processes impacted by a release when performing release planning to introduce any new capabilities or changes to new TACLAN production or legacy systems [CDRL A0024]. These processes include, but are not limited to, the following: Configuration management; System integration testing; IA security testing; Operations management of production systems; Service Desk support training; Training pertaining to operations, administration, and maintenance; and Compliance and accreditation policy and requirements.

In performing its Release Management obligations and activities, the Contractor shall collaborate and coordinate with all other SITEC IT Service Area providers directly affected or impacted by TACLAN Release Management activities. The Contractor shall incorporate a categorization methodology into the TACLAN Release Management process in alignment with the SITEC Release Management Process that accommodates various levels of importance for releases, and include at minimum the following release levels:

• Major software Releases and hardware upgrades or replacements, normally containing large areas of new functionality. A major upgrade or Release usually supersedes all preceding minor upgrades, Releases and emergency fixes.

• Minor software Releases and hardware upgrades, normally containing small enhancements and fixes, some of which may have already been issued as emergency fixes. A minor upgrade or Release usually supersedes all preceding emergency fixes.

• Emergency software and hardware fixes, normally containing the corrections to a small number of known problems.

10.12 Validation, Integration, and Testing

The Contractor shall maintain a quality management system that meets the requirements specified by International Standards Organization (ISO) 9001:2000. Additionally, the Contractor shall manage projects based on the principles of the Project Management Institute (PMI), the industry standard for project management training and certification.

The Contractor shall verify all TACLAN equipment and software to be introduced into any USSOCOM SIE environment operates according to USSOCOM requirements. TACLAN equipment introduced into the SIE shall be integrated without negative impact on any other IT production system or service, and shall not compromise system security, or otherwise impair, disrupt, or jeopardize USSOCOM’s mission.