PWS TENCAP IT Support 2.0_Revised.pdf

FA869125RB004 – Attachment 1

Performance Work Statement

FOR

AF TENCAP INFORMATION TECHNOLOGY

SUPPORT

1.0 INTRODUCTION

1.1 Background

Air Force (AF) Tactical Exploitation of National Capabilities (TENCAP), located at 2424 Garden of the Gods Road, Colorado Springs, CO is a congressionally mandated program which increases warfighter effectiveness through the exploitation of national capabilities and promotes cross-domain integration of these capabilities into military operations/training, intelligence, surveillance and reconnaissance (ISR) activities. AF TENCAP exploits existing air, space, cyber, national and global ISR and non-traditional ISR (NTISR) systems for operational and tactical applications through rapid prototyping and capability demonstration. These projects are intended to transition to warfighters and/or national intelligence agencies for operational use and appropriate acquisition Programs of Record (PoR) for further development. AF TENCAP projects can influence the design and operation of future air, space, cyber, national and global ISR and NTISR while providing awareness to warfighters and national intelligence agency organizations and units. AF TENCAP supports the AF and joint warfighter through the following mission areas:

• Support to special application/special access programs (SAP) and the development of projects/programs that involve access to one or more special access required (SAR) and SAP areas of interest. This requires cooperation and collaboration with the SAP/SAR DoD communities and similar Director of National Intelligence (DNI) programs that require enhanced combat and intelligence capabilities.

• Support to special operations forces (SOF). Direct engagement with SOF is required to obtain “street level” warfighter requirements and those requirements that can be met leveraging national capabilities.

• Support to the tactical warfighter. Leverage existing and emerging national and tactical systems by effectively exploiting and integrating space, national, global ISR, and NTISR assets to provide support to combatant commands and forward deployed tactical warfighters (e.g., Pacific Air Forces (PACAF), United States (US) Air Force Europe (USAFE), US Central Commander Air Forces (CENTAF), Air Force Southern (AFSOUTH) across all domains.

• Support to the national warfighter. Leverage existing and emerging national and tactical systems by effectively exploiting and integrating space, national, global ISR, and NTISR assets to provide CONUS based (Air Force Global Strike Command (AFGSC), Air Force Space Command (AFSPC), 24th Air Force (24AF) air forces and national intelligence agencies increase situational awareness across all domains.

• AF representative for the National Reconnaissance Office Military Exploitation of Reconnaissance and Intelligence Technology (NRO MERIT) program, sponsoring new projects that enhance tactical warfighting capabilities by leveraging national capabilities.

2.0 PROGRAM OBJECTIVES / DESCRIPTION OF SERVICES

TENCAP Information Technology (IT) section requires services in support of the numerous and diverse classified and unclassified systems, networks, exercises and developmental missions within the TENCAP work center, provides systems engineering, computer systems support, IT engineering, hardware operating systems, peripheral (HOSP) maintenance, video teleconferencing support, communications security (COMSEC), and audio/visual services to all units. Within these mission functional areas support includes, but is not limited to:

• Contract Management

• Requirements Analysis/Technical Solutions Development

• Information Technology Equipment Custodian I

• Audio Visual Services

• Hardware and Software Maintenance Support

• Technical Equipment Refresh

• Cybersecurity Support (A&A, Vulnerability management, computer security compliance)

It is understood that the provision of IT services to TENCAP under this contract shall be within the available level of effort (e.g. LCATS on this contract). The contract COR may prioritize (or reject) requests for service under this contract if necessary.

3.0 SCOPE

AF TENCAP requires professional services for this commercial, non-personal services, severable contract to support the program. AF TENCAP consists of approximately 75 people located in Colorado Springs, CO. All labor performed by the contractor pursuant to this PWS must cover all requirements listed within Section 4.0 including the task deliverables, known and unknown, stated in Section 5.0. The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform information technology service desk support and engineering services as defined in this Performance Work Statement except for those items specified as Government-furnished property and services.

IT is integral to the entire AF TENCAP mission. Additional IT effort may be required in support of projects in other areas of the PWS that are added as requirements and funding are identified. Additional requirements will be added based on mutual agreement between the government and the contractor.

Any and all data, databases, applications, and processes developed to render services as part of this contract shall be the property of the Government. All data rights assertions must be identified prior to start of specific limited data right action.

A minimum of TOP SECRET/SCI security clearances are required for contractor employees, including subcontractor employees, at the beginning of the contract performance period (POP start date) and throughout the life of the contract unless a waiver is granted at the Government’s discretion. AF TENCAP Security can nominate members for SCI. The contractor, at its own expense, is responsible for providing and maintaining personnel with the appropriate security clearances to ensure compliance with Government security regulations, as specified in this PWS. Where personnel are no longer able to retain either the Top Secret or where personnel are unable to obtain the Top Secret clearance, that employee can no longer remain working on the requirement and shall be replaced by another personnel.

4.0 REQUIREMENTS/SPECIFIC TASKS:

4.1 Contract Management

The contractor shall provide program management services under this contract. This includes the management and oversight of all activities performed by contractor personnel, including subcontractors, to satisfy the requirements identified in this Performance Work Statement (PWS).

4.1.1 Coordinate a Project Kick-Off Meeting

The contractor shall schedule, coordinate, and host a Project Kick-Off Meeting at the location approved by the CO, PM, or COR. The meeting shall provide an introduction between the contractor personnel and Government personnel who will be involved with the contract. The meeting shall provide the opportunity to discuss technical management, security issues, and travel authorization and reporting procedures. At a minimum, the attendees must include the contractor’s key personnel, representative(s) from TENCAP, the CO and COR.

At least three (3) business days prior to the Project Kick-Off Meeting, the contractor shall provide a Kick- Off Meeting Agenda for review and approval by the COR, CO, and the TENCAP Program. The agenda shall include, at a minimum, the following topics/deliverables:

● Points of contact (POCs) for all parties.

● Personnel discussion (i.e., roles and responsibilities and lines of communication between contractor and Government).

● Staffing Plan and status.

● Transition-In Plan and discussion.

● Security discussion and requirements (i.e., building access, badges, Common Access Cards

[CACs]).

● Invoicing requirements.

The Government shall provide the contractor with the number of Government participants for the Kick- Off meeting, and the contractor shall provide sufficient copies of the presentation for all present. The contractor shall draft and provide a Kick-Off Meeting Minutes Report (Table 5.1, Deliverables).

4.1.2 Convene Technical Status Meetings

The contractor’s designated PM for this contract shall convene a monthly Technical Status Meeting with the COR, CO, and other Government stakeholders as identified by the COR. The purpose of this meeting is to ensure all stakeholders are informed of the monthly activities and Monthly Status Report (MSR), provide opportunities to identify other activities and establish priorities and coordinate resolution of identified problems or opportunities.

4.1.3 Prepare and Update a Project Management Plan (PMP)

The contractor must document all support requirements in a PMP and provide it to the Government (See Table 5.1, Deliverables)

The PMP shall:

• Describe the proposed management approach and contractor organizational structure. This includes the contractor’s approach for quality management to ensure contract deliverables are of the highest quality in accordance with the Quality Assurance Surveillance Plan (QASP).

● Provide for an overall Work Breakdown Structure (WBS) with a minimum of three levels and associated responsibilities and partnerships between or among Government organizations.

● Contain detailed Standard Operating Procedures (SOPs) for all tasks and processes that require Government involvement and/or approval.

● Include milestones, tasks, and subtasks required in this contract.

● Describe in detail the contractor’s approach to risk management under this contract.

● Describe in detail the contractor’s approach to communications, including processes, procedures, communication approach, and other rules of engagement between the contractor and the Government.

The PMP is an evolutionary document that must be updated as changes in the program occur. The contractor must work from the latest Government-approved version of the PMP.

4.1.4 Prepare Trip Reports

Long-Distance travel is not expected at this time; however, occasional travel may be required. If the Government identifies the need for travel, a written Consent to Purchase (CTP) request must be submitted and a Trip Report generated. The contractor shall keep a summary of all Long-Distance Travel including, but not limited to, the name of the employee, location of travel, duration of trip, and Point of Contact (POC) at travel location. Trip Reports shall also contain Government approval authority, total cost of the trip, a detailed description of the purpose of the trip, and any knowledge gained.

4.1.5 Conduct Transition-In

The contractor must conduct transition-in activities, if any, as needed to ensure that there will be minimum service disruption to vital Government business and no service degradation during and after transition. The contractor must implement any necessary transition-in activities, if any, immediately after time of award (TOA) and all transition-in activities must be completed no later than 45 calendar days after TOA.

4.1.5.1 The Contractor shall provide their Transition Plan to the COR for approval within seven (7) days of TOA and the final approved version will be discussed at the kick-off meeting. The Transition Plan shall include milestones and when properly trained, qualified, and certified personnel will accomplish full assumption of responsibility (AOR) for all requirements identified in the PWS by 45 days after award (or other date agreed upon by the CO and COR). The Transition Plan shall include start up, mobilization schedule, and transition depicting the chronological sequence of events which the Contractor shall accomplish beginning on contract start date.

4.1.5.2 The Contractor shall demonstrate the ability to quickly staff the requirement to meet the transition schedule.

4.1.5.3 The Contractor shall demonstrate the ability to ensure proposed personnel are vetted to guarantee they meet the Air Force suitability and security clearance process thus aiding in a more expedient process.

4.1.5.4 Starting the first day of the transition period, the Contractor shall ensure necessary personnel actions, appropriate training, (including, but not limited to, any required certifications), as well as non-personnel considerations such as materials and supplies, equipment, subcontracts, environmental issues, safety, and security, etc. are accomplished in accordance with the transition plan.

4.1.5.5 In collaboration with the Contracting Officer, the COR, and the Government Project Manager will determine the specific timing for Contractor AOR post award. The Contractor shall meet with AF TENCAP representatives to determine how the transition will take place, develop schedules, and collaborate on execution of the transition requirements.

4.1.5.6 During Transition-In, the Contractor shall minimize service disruptions or degradations during and after the transition to this contract. The services provided under this PWS are vital to the AF TENCAP mission and must continue with minimal interruption or degradation of service.

4.1.5.7 The Contractor shall accept AOR in accordance with their Government-approved Transition Plan.

4.1.6 Conduct Transition-Out

The contractor must provide transition-out support when required by the Government. The Transition- Out Plan must facilitate the accomplishment of a seamless transition from the incumbent to incoming contractor/Government personnel at the expiration of the contract. The contractor must provide the Transition-Out Plan no later than 6-months after contract award and implement no later than 3-months prior to expiration of the contract.

In the Transition-Out Plan, the contractor must identify how it will coordinate with the incoming contractor and/or Government personnel to transfer knowledge regarding the following:

● Project management processes.

● Points of contact.

● Location of technical and project management documentation.

● Status of ongoing technical initiatives.

● Appropriate contractor–to-contractor coordination to ensure a seamless transition.

● Transition of key personnel.

● Schedules and milestones.

● Actions required of the Government.

The contractor shall also establish and maintain effective communication with the incoming contractor/Government personnel for the period of the transition via weekly status meetings or as often as necessary to ensure a seamless transition-out.

Note: The contractor shall implement its Transition-Out Plan NLT three months prior to expiration of the contract; or within 60 days of the end of an earlier Period of Performance, as directed by the Government, if notified the next option period will not be exercised.

4.2 Engineering, Development, Operation, Administration, Support and Maintenance of

Information Systems and Networks Supporting Internal/ External AF TENCAP Communications.

The contractor shall support AF TENCAP in system design, operation, administration and maintenance IAW AFGM2018-17-02, AFI 17-140, and AFI 17-130. In support of this effort the contractor shall operate, administer, and maintain networks at the unclassified, secret and top secret-SCI classification levels during core duty hours (0800 – 1700) and provide onsite before and after core hour support (1 hour before and 1 hour after core hours) performing unforeseen system repairs and troubleshooting with external networks. On occasion, the contractor may be required to provide after-hours, non-duty hours and on-call support as requested by the Government including but not limited to, test and exercise support, and unforeseen system repairs. Tasks include:

4.2.1 Maintain a Government-provided trouble ticket system as well as track and report customer survey results.

4.2.1.1 The contractor shall utilize the existing AF TENCAP PowerBI and MS TEAMS DoD/AFNETapproved customer service ticketing system to provide and manage help desk, remote desktop for real time troubleshooting, and version control capability.

4.2.1.2 The Contractor shall report monthly comprehensive service desk statistics with fields (report configuration), included in the monthly status report (MSR) as specified by the Government. Upon written request of the Government, the Contractor shall provide weekly comprehensive service desk statistics.

4.2.2 Perform client support administrator duties via a help desk function to serve as the AF TENCAP IT focal point for AF TENCAP customer support. The consolidated job control/help desk function shall be capable of handling tier 1 and tier 2 issues, and escalate those outside of their respective tiers. Duties of the helpdesk also include configuring mobile communication devices.

4.2.3 Support walk-up, telephone or e-mail customer problem resolution; receive, answer and transfer, when required, trouble calls and maintenance requests in support of all AF TENCAP missions and personnel; assign a ticket number and track communication system outages and repair actions until the issue is resolved.

4.2.4 Coordinate with internal and external agencies (i.e., third-party vendors, host base, and program management offices), to isolate faults, make repairs, and restore service to AF TENCAP systems; report the status of problem resolution to the affected customer and maintain a historical record of problem resolution.

4.2.5 Support other functions in the consolidated job control/help desk function to include:

developing and maintaining maintenance management continuity documentation; assigning helpdesk ticket numbers and proposing restoral priorities to AF TENCAP communication systems; tracking equipment and circuit outages; developing and implementing life cycle logistics support for AF TENCAP system acquisitions and modifications; conducting trend analysis to evaluate system performance and providing feedback to the Government through equipment status reports and job data documentation.

4.2.6 Oversee the overall security, integrity, and operations of DoD and AF systems and networks IAW AFGM2018-17-02, DAFMAN 17-1302-0, AFI 16-1405, AFI 17-130 and local policies and procedures and provide support in connecting AF TENCAP divisions with other agencies. This will include the certification and accreditation, patching, scanning and testing of systems, including but not limited to Commercial, NIPR, SIPR, JWICS networks. Any additional networks shall be proposed as an option.

4.2.7 Disconnect, move and connect equipment to networks; demonstrate expertise to install, configure, and maintain these systems as well as analyze, troubleshoot, and resolve software, hardware, and network anomalies; operate and maintain computer facilities, to include all current AF TENCAP IT system hardware and software as well as new hardware and software specified by the Government and added to AF TENCAP networks during the course of the contract. For any new systems added, the government will procure the appropriate training for the helpdesk/system administrator to maintain the system.

4.2.8 Perform systems administration on a myriad of platforms including on all systems in the TENCAP SCIF including but not limited to UNIX and Windows OS.

4.2.9 Configure, install, identify, assess, mitigate, and report all vulnerabilities of fiber, Ethernet and fast Ethernet networks; and troubleshoot and restore systems (e.g., servers, desktops, laptops, peripherals, scanners, plotters and printers) to normal operating conditions in minimal time.

4.2.10 Provide network administration and technical support. Support includes address and machine/domain name management, interfacing/coordinating with external agencies on WAN (and other long-haul communications links) issues and troubleshooting problems.

4.2.11 Perform communications system technical support, architecture design and troubleshooting.

Technical support includes operating system loading and (re) configuration, user account management, system backup and recovery, troubleshooting, removing and replacing components and peripherals, installing software, operating systems and drivers and coordinating any other maintenance support with internal and external agencies.

4.2.12 Determine the most appropriate, technically feasible, integrated, and cost-effective means of meeting the AF TENCAP IT needs at the unclassified, secret, TS-SCI level and SAP.

4.2.13 Develop and review communication system requirements, compare potential needs with existing infrastructure, identify shortfalls and excesses, integrate communication systems to achieve interoperability and establish continuity procedures and a reference library of pertinent policies, procedures, documents and architectures to properly plan for future communication systems.

4.2.14 Meet with customers/users on a regular basis to learn about their organizational structures, unit missions and requirements to gain a better understanding of their needs and to educate customers on the AF TENCAP processes and procedures.

4.2.15 Develop Communication System Requirement Document (CSRD) technical solutions and Communication and Information Systems Installation Records (CSIR) initially within 30 days of PoP start then review annually to provide network, computer system, financial, installation, outside agency coordination, information assurance and customer assistance. Provide all technical network and systems engineering expertise to the Government with a complete technical solution that meets the requirement or intent of the customer, provide recommendations to the Government regarding issues with a CSRD, and provide the Government with alternatives to meet the requirements outlined in the

CSRD

4.2.16 Perform facility layout and engineering for all AF TENCAP divisions. This includes accounting for and coordinating security accreditation issues, equipment placement, and equipment cooling and power requirements. Participate in planning forums, briefings, conferences, and meetings to keep informed on internal and external resources.

4.2.17 Perform systems architecture design and planning and develop and maintain an overall plan for systems upgrades to support long-term budgeting.

4.2.18 Update, maintain, and deliver CSIR and schematic operational, systems, and technical architecture drawings. Update, maintain, and deliver interface drawings between systems, connectivity drawings of equipment to various LANs and current configuration modifications IAW AFI 33-150 requirements derived from communication requirements and system accreditation processes to the level agreed upon by the Government and the contractor.

4.2.19 Administer, maintain, edit, and train AF TENCAP Operators on Microsoft platforms of PowerBI, PowerAPP, and PowerAutomate. These platforms are the foundation for Program Management Tools within the AF TENCAP Organization.

4.2.20 The contractor shall create (as directed), manage, maintain, and edit a web-based knowledge management portal on JWICS. The portal capabilities are expected to evolve and adapt to meet the mission needs of the Government. The portal shall be available to all approved AF TENCAP personnel, and Government access to the portal shall be approved by Mission Programs Division. The objective of the portal is to provide a central location for the Government and contractor to access an organized and configuration controlled current and historical project database.

4.2.21 The contractor shall create (as directed) manage, maintain, and edit a web-based organization information page, available on NIPR and JWICS. The webpage capabilities and information requirements are expected to evolve and adapt to meet the mission needs of the Government. The objective of the organization pages is to provide an overview and interface for customers and stakeholders to learn about AF TENCAP, its mission, projects, and contact information.

4.3 Computer Systems Acquisition, Management and Accountability

In support of this effort the contractor shall be responsible for all actions undertaken to configure/re-configure, field, account for, and turn in the AF TENCAP’s stand-alone and networked IT systems and equipment at the unclassified, secret and TS-SCI classification levels IAW Government procedures and systems (i.e., ITEC, Standard Base Supply System (SBSS) and Defense Reutilization and Marketing Office (DRMO)). Expected tasks include:

4.3.1 Plan and implement required technical refresh for AF TENCAP’s IT systems and equipment, to include, but not limited to, NIPR, SIPR, and JWICS, along with associated video teleconferencing equipment as needed. Assist with purchasing unique mission systems in support of AF TENCAP integration tasks associated with this PWS. All purchases will be made IAW the CSRD process and are reimbursed/accounted for as part of the ODC CLIN.

4.3.2 Establish a Configuration Management Office, appoint an AF TENCAP Configuration Manager, and support the Government with receiving customer/user-identified communication requirements using established processes and tools, develop/coordinate technical solutions for the requirements, and verify the systems will work within the AF TENCAP infrastructure. Deliver any and all technical solutions, software, designs, records, databases, manuals, guides, standard operating procedures and similar items developed in rendering Configuration Management Office services.

4.3.3 Support the Government with defining requirements, develop/find technical solutions, work plans that are consistent with architectural and information system security guidelines and policies, and update local procedures explaining how to prepare and process communication system requirements. Technical solution coordination shall include, as a minimum, information assurance and systems engineering review.

4.3.4 Monitor the requirement and inform the requesting organization of its status throughout the design, implementation, and accreditation stages. When checking integration efforts, the contractor shall take full account of their impact on the infrastructure and detail the methods and means of implementation to include system description, points of contact, actual or forecasted implementation dates, hardware and software requirements, funding and classification of information processed in this review.

4.3.5 Determine what resources are available for installation and maintenance of equipment and include in the work plan; consider what logistics support the system needs and coordinate maintenance planning, supply support, technical data, manpower, facilities, packaging, handling, storage, and transportation.

4.3.6 Support the Government with the management process applied throughout the life of an automated information system (AIS) and help determine whether benefits of the expected life of a system or facility are worth the cost, or if leased, whether length of the contract is worth the overall cost.

4.3.7 Maintain and update the existing configuration management database for all systems (hardware and software) and communications equipment (hardware and software) under AF TENCAP control. The inventory shall list the location and all required unique identifying characteristics necessary to link individual items of hardware and software to the system and its location. The database will be linked to the AF TENCAP Intranet web page.

4.3.8 Track and report software licensing and other pertinent data. The contractor shall update the database when changes occur to keep it accurate. Ensure all hardware and software is added to the inventory database prior to installation, dispose of excess hardware and software IAW AFM 33-153, and ensures the disposition is annotated in the database.

4.3.9 Package and ship defective parts and receive and distribute replacement parts for equipment under warranty. Any shipping costs will be at the direction of the Government and are reimbursed/accounted for as part of the ODC CLIN.

4.3.10 Appoint an AF TENCAP ADPE Equipment Custodian (EC) and alternates to fulfill the AF TENCAP

ADPE EC duties for the AF TENCAP ADPE located at 2424 Garden of the Gods Rd.. Serve as the AF TENCAP’s central point of contact with the Base Equipment Control Office (BECO) for all ADPE matters to include:

• receiving, storing, issuing and disposing of all ADPE assigned to the AF TENCAP;

• maintaining the inventory database, and ensuring all hardware is added to the database prior to installation;

• accomplishing semi-annual inventories of all the AF TENCAP’s systems and communications hardware to ensure accuracy of the database,

• providing a written report of these findings along with recommendations to resolve discrepancies;

• accomplishing quarterly 10% spot-check audits of operational areas to verify equipment accountability and control, and report the results to the Government;

• conducting inventories directed by the BECO and reconciling the AF TENCAP’s inventories with the installation’s inventories;

• reporting any discrepancies to the Government;

• disposing of excess hardware IAW DAFMAN 17-1203; and performing a 100% physical inventory of AF TENCAP ADPE assets prior to assuming responsibility for AF TENCAP ADPE assets.

4.3.11 Assist the Government with the AF Way (AFWAY) process in submitting requests for quotes, creating orders, tracking order status, and executing the AFWAY waiver process for buying ADPE outside of the AFWAY process.

4.4 System and Network Security.

In support of System and Network Security the contractor shall:

4.4.1 Comply with certification/education/training requirements as mandated in DoD 8570.01 M (i.e., commercial/industry certifications).

4.4.2 Support the Government in the development of certification and accreditation (C&A) packages IAW AF Policy Directive (AFPD) 17-1, AFSSI 7703, DoDI 8510.01, DODI 8500.01, Intelligence Community Directive (ICD) 503, SP 800-53v4 , DoD 8570-01 M, CNSSI 1253, and, DoD Joint Security Implementation Guide (DJSIG), and provide the Designated Approval Authority (DAA) and/or Certifying Authority with system certification and accreditation recommendations for all AF TENCAP-managed systems and networks at the unclassified, secret and TS-SCI level. Support AF TENCAP customers/users with their specific network and stand-alone system accreditations.

4.4.3 Maintain and update Trusted Facility Manuals, system descriptions, security policies, user guides, system architectures, and security-related documentation; support the Government in highlighting when changes to current packages are required IAW ICD 503, and DJSIG. Ensure all packages are submitted and coordinated with the accrediting authority for approval and monitor the current status of all accreditation packages.

4.4.4 Prepare and present training tailored for initial and periodic information awareness (IA), system administrator technical awareness and executive level IA training. At a minimum, the training shall include the threat to the AF TENCAP and its information systems, IA intrusion techniques used by intruders, and the procedures users can take to report (physical, procedural, technical) and protect against these intrusions.

4.4.5 Provide information to support system administrators, network managers, users, procurement staff, and security personnel; monitor, implement, and report on all security/configuration patches/changes (i.e., NOTAM, IAVA, and security/vulnerability advisories). Accomplishment timelines are identified in individual NOTAMs, IAVAs, etc.

4.4.6 Perform a weekly review of the audit trail of the AF TENCAP’s systems (servers, workstations/desktops, firewalls) for any abnormal activities and maintain the audit trail IAW AFPD 17-1, DoD I 8500.2, AFI 17- 130, DCID 6/3, CNSSI 1253, SP 800-53v4, ICD 503 and DJSIG.

4.4.7 Conduct vulnerability testing and risk analysis as part of the overall accreditation process on all networks and systems as determined by the Government IAW AFPD 17-1, DoDI 8500.2, AFI 17- 130, ICD 503, and Joint Department of Defense Intelligence Information System DODIIS/Cryptologic SCI Information Systems Security Standards (JDCSISSS). The certification test is to determine such things as system security weaknesses, vulnerabilities, procedural problem areas, and/or implementation flaws with the system’s architecture. Vulnerability testing and risk analysis shall be performed periodically, randomly, or as new systems are installed. The test and risk analysis shall include the architecture, its external and internal connections, and management processes and procedures to determine risk levels for operating networks and stand-alone systems.

4.4.8 Identify corrective actions for hardware, software and business management procedures required to correct or minimize the deficiencies, points-of-contact responsible for correcting identified problems and projected dates when identified problems will be corrected. Work with the Government, associated support contractors and identified points-of-contact to ensure proper implementation of the corrective actions.

4.4.9 Maintain and improve AF TENCAP computer system security baseline to include threat updates, security configuration control, and system security review for software/system purchases, evaluation, and integration; provide support in the investigation and documentation of network and stand-alone security incidents.

4.4.10 Support management of COMSEC materials in support of AF TENCAP operations to include:

accounting for and inventorying COMSEC material; keying cryptographic (CRYPTO) equipment;

troubleshooting system failures; destroying superseded keying material; documenting receipt, issue, inventory, and destruction of COMSEC material; creating messages for the COMSEC controlling authority's ability to issue keying material (keymat) to customers; supporting and training AF TENCAP users responsible for keying, safeguarding, troubleshooting, and destroying CRYPTO equipment; and supporting the Government in providing regularly scheduled training to all AF TENCAP-designated personnel responsible for keying, safeguarding, troubleshooting, and destroying CRYPTO equipment IAW DAFMAN 17-1302-0.

4.5 Software Engineering, Maintenance, Management and Support.

In support of this effort the contractor shall maintain and support the following programs:

o MS TEAMs/OneDrive The Contractor shall ensure that an access plan is in place to ensure that members have appropriate accesses to accounts. The contractor shall train new and existing AF TENCAP members on OneDrive use, best practices, and capabilities to ensure all members can effectively use the application.

o TENCAP Portfolio Management Tool

4.6 Hardware, Operating Systems, and their Peripherals (HOSP) Maintenance HOSP maintenance is Level 2 maintenance (i.e., testing, replacement of component parts, major system overhauls) done to sustain mission-ready equipment at the time and place it is needed. In addition to Level 2 maintenance, it also includes upgrades on existing and/or new hardware, operating systems and peripherals as well as preventive maintenance performed for the purpose of preventing problems before they occur by maintaining items (adjusting and replacing items) according to a regular schedule.

The contractor shall:

4.6.1 Support the Government in determining what level of maintenance individual HOSP systems will require. The level of maintenance shall, at a minimum, identify the mission criticality, acceptable downtime, spare parts, warehousing requirements and location for repair (i.e., on-site, depot, or vendor location).

4.6.2 Support the Government in coordinating with all HOSP system vendors to identify those HOSP systems to be placed on a vendor maintenance contract. The contractor shall coordinate with the HOSP system vendor to identify upgrade requirements necessary to place the HOSP systems on the vendor maintenance contract and notify the Government of all costs associated with the upgrade.

4.6.3 Designate an on-site Computer Maintenance Support Technician (CMST) with necessary test equipment and tools; establish an office to perform installation, maintenance, and troubleshooting of HOSP. The on-site CMST shall be certified and highly proficient in troubleshooting and repairing HOSPs anomalies and restoring specialized desktop workstations (SGI, SUN and Mac), specialized unique processors, and peripherals (printer, external drives). The labor category that will be used to fill this position is listed as the Telecommunication Equipment Installer and Repairer in table 5.3.

4.6.4 Coordinate with the Government to ensure that prior to any upgrade or new installation, documentation of the computer’s new configuration is properly processed/annotated. The contractor shall coordinate maintenance actions with the AF TENCAP consolidated job control/help desk function.

4.6.5 Coordinate warranty repair actions for equipment under warranty and submit a trouble report to the HQ AF TENCAP consolidated job control/help desk function, documenting repairs made to AF TENCAP computer equipment.

4.6.6 Move, remove and install all the AF TENCAP HOSP systems and peripherals (printer, external drives) in a condition capable of supporting AF TENCAP requirements; ensure a CSRD or trouble ticket number is submitted and used as a reference prior to any HOSP action regarding hardware or software upgrades.

4.6.7 Maintain the expertise to provide centralized A/V communication installation, routine support, tech refresh, and maintenance for AF TENCAP systems.

4.6.8 The contractor shall provide cable maintenance/management of existing infrastructure, planning, and management of all activities related to the communications infrastructure within the TENCAP facility. The contractor is responsible for the quality of workmanship, timeliness, tracking and reporting of the overall health and state of the communications infrastructure.

Duties are performed according to general policies approved by the Department of Defense, the Air Force, and the Air Combat Command.

4.6.9 The Contractor will provide video teleconferencing support to include:

• Scheduling, operations and maintenance.

• Troubleshoot outages and coordinate with external agencies for support.

• Training for unit personnel on scheduling and setting up VTCs for those systems within Building

2424.

• Collaborate with the customer in planning for systems upgrades and procurement.

5.0 DELIVERABLES/REPORTS

5.1 Deliverables

The contractor must prepare and deliver assigned deliverables in accordance with this PWS and the tables below. All deliverables must be reviewed by the AF TENCAP COR for adherence to the schedule and requirements. All physical deliverables will become the physical property of the Government and may contain a legend or similar marking identifying the contractor staff who prepared the deliverable including the first initial, last name, and employer.

The contractor must ensure that each deliverable is accurate and complete, technically sound, and free of clerical errors. The reviewer must notify the COR via e-mail that a review was completed. If such a review may not be performed on any deliverable, the contractor must contact the COR prior to submitting the deliverable. The contractor must immediately notify the COR if schedules for task completion may not be met, and upon learning of anything that might affect performance under this

PWS.

TABLES 5.1 and 5.2 Deliverables

Table 5.1: Contract and Project Management

MILESTONE/

DELIVERABLE

PWS

Section

Delivery Method/Format

Frequency/Date of Completion/Delivery

Performance Threshold*

1 Project Start At TOA

Kick-Off Meeting Agenda

4.1.1 Via Microsoft

Word/PDF At least three workdays prior to Kick-off Meeting 90%

Timely/Accurate

Kick-Off Meeting

4.1.1 In Person Within 30 workdays of TOA

100%

Timely/Accurate

Kick-Off Meeting

Minutes Report 4.1.1

Via Microsoft Word/PDF

NLT 5 workdays after Kick- Off Meeting

100% Timely/Accurate

Monthly Status

Report 5.1.3

Via Microsoft Word/PDF

Monthly submitted with invoice

90% Timely/Accurate

Technical

Status Meeting 4.1.2

Via Microsoft Word/PDF

Monthly 95%

Timely/Accurate

Technical

Status Meeting Minutes

4.1.2 Via Microsoft

Word/PDF

NLT 5 workdays after Monthly Technical Status

Meeting

95% Timely/Accurate

Project

Management Plan (PMP)

4.1.3 Via Microsoft

Word/PDF Due at Kick-Off meeting and updated as needed 95%

Timely/Accurate

9 Trip Report(s) 4.1.4 Via Microsoft

Word/PDF Due with invoice of associated PoP trip occurred 95%

Timely/Accurate

Transition-In

Plan 4.1.5

Via Microsoft Word/PDF

Once. Initial due 7 days after TOA. Final approved NLT

Kick-Off

95% Timely/Accurate

Transition-Out

Plan 4.1.6

Via Microsoft Word/PDF

Plan due NLT 6-Months after TOA & Implemented NLT 3-

Months Prior to Expiration of Contract

95% Timely/Accurate

Ticketing

System/Help Desk Plan

4.2.1.1

Via Microsoft Word/PDF

Or

As determined by the vendor

Within 30 days of Contract Award

95% Timely/Accurate

Quality Control

Plan (QCP) 5.1.4

Via Microsoft Word/PDF

Due at Kick-Off meeting and updated as needed

95% Timely/Accurate

Quality Control Matrix (QCM)

5.1.4 Via Microsoft

Word/PDF

Due at Kick-Off meeting, included in QCP and updated as needed

95% Timely/Accurate

15 Final Invoice 11.6 Via Microsoft

Word/PDF Due within 60 days after

Contract completion 100%

Timely/Accurate

Release of

Claims 11.7

Via Microsoft Word/PDF

Due within 15 calendar days of final payment

100% Timely Accurate

Table 5.2: IT Service and Support

MILESTONE/

DELIVERABLE

PWS

Section

Delivery Method/Format

Date of Completion/Delivery

Performance Threshold*

100% Physical Inventory

Report 4.3.10

Via Microsoft Word/PDF

Within 14 Days of PoP Start

100%

** The method of surveillance for each of the primary tasks the contractor is required to perform under Section 4 of this PWS is disclosed/included in the Quality Assurance Surveillance Plan ((QASP).

5.1.1 Delivery Instructions

The contractor must deliver each report in accordance with the direction in the charts in Table 5.1 and

5.2 Deliverables. These deliverables are to be transmitted with a cover letter, on the prime contractor’s letterhead, describing the contents. The contractor must deliver electronic versions by electronic mail (email), removable electronic media, and/or placing in the AF TENCAPS’s designated repository. The following are the required electronic formats, whose version must be compatible with the latest, commonly available version on the market.

● Text/Microsoft (MS) Word, PDF

Hardware Inventory / Recommendation Report

4.3.10 Via Microsoft

Word/PDF Semi-Annual

100% Timely/Accurate

Operational Area Spot-

Check Audit Report 4.3.10

Via Microsoft Word/PDF

Quarterly 100%

Timely/Accurate

BECO Directed

Inventory/Reconciliation Report

4.3.10 Direct to

COR/Customer As Requested

100% Timely/Accurate

5 System Security Plans 4.4.7 Direct to

COR/Customer As

Required/Requested 100%

Timely/Accurate

Certification &

Accreditation (C&A) Documentation

4.4.2 Direct to

COR/Customer As

Required/Requested 100%

Timely/Accurate

7 CSRD and CSIR 4.2.15 Direct to

COR/Customer

Initial Development within 30 days PoP start and then Annual Review

95% Timely/Accurate

8 Service Desk Statistics 4.2.1.2 Direct to

COR/Customer

Monthly at time of associated invoice with monthly status report. Weekly upon written request with at least three (3) business days’ notice

95%

● Spreadsheets/MS Excel

● Briefings/MS PowerPoint

● Drawings/MS Visio

● Schedules/MS Project

The contractor must mark all deliverables listed in the above table to indicate authorship by contractor (i.e., non-Government) personnel; provided, however, that no deliverable must contain any proprietary markings inconsistent with the Government’s data rights set forth in this contract. The Government reserves the right to treat non-conforming markings in accordance with Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7013 and 252.227-7014.

5.1.2 Inspection and Acceptance of Services

All reports and task deliverables must be inspected, tested (where applicable), reviewed, and accepted by the Government within a reasonable period of time in accordance with FAR 52.212-4 and the acceptance criteria set forth in the QASP. The Contractor must only tender for acceptance those items that conform to the requirements of this contract. The Government reserves the right to inspect or test any supplies or services that have been tendered for acceptance. The Government may require repair or replacement of nonconforming supplies or re-performance of nonconforming services at no increase in contract price. If repair/replacement or re-performance will not correct the defects or is not possible, the government may seek an equitable price reduction or adequate consideration for acceptance of nonconforming supplies or services. The Government must exercise its post-acceptance rights within a reasonable time, after the defect was discovered or should have been discovered and before any substantial change occurs in the condition of the item, unless the change is due to the defect in the item. Only the COR, their designated alternate, or the CO has the authority to inspect, accept, or reject all deliverables. Final acceptance of all deliverables will be provided in writing, or in electronic format, to the CO and COR within 30 days from the end of the contract.

5.1.3 Monthly Status Reports

The contractor shall prepare and submit an MSR. The MSR shall be used by the Government to review and evaluate the technical progress and schedule status of the deliverables. The report format shall be coordinated with the COR. The MSR shall include:

• List of Labor Categories

• Personnel gains, losses, and statuses (security clearance, etc.)

• Technical progress made and schedule status per deliverable (major tasks, milestones, and deliverables; include planned and actual start and completion dates for each)

• Summary of trips taken, conferences attended, etc. (attach Trip Reports to the MSR for reporting period).

• Funding compared to current CLIN dollar value ceiling, actual expenditures by CLIN

• Accumulated invoiced cost for each CLIN up to the previous month

• Cost information and burn rate (the amount of money left on the contract)

• Projected cost of each CLIN for the current month

• Deliverable titles and numbers completed within the previous month, and the deliverables scheduled to be delivered during the upcoming month

• Activities during reporting period, by task (include ongoing activities, new activities, activities completed, and progress to date on all the activities listed). Each section must start with a brief description of the task

• Service Desk Statistics

• Problems and corrective actions taken. Also include issues or concerns and proposed resolutions to address them

• Government actions required

5.1.4 Contractor Quality Control Requirements

The contractor must develop and maintain a quality process to ensure services are performed in accordance with commonly accepted commercial practices and existing quality control systems throughout the life of the contract. The contractor must develop and implement procedures to identify, prevent and ensure non-recurrence of defective services.

The contractor must establish and maintain a complete Quality Control Plan (QCP) to ensure the services are performed in accordance with PWS and commonly accepted commercial practices, throughout the life of the contract. The QCP must include a Quality Control Matrix (QCM) that addresses all deliverables in Table 5.1. The QCM must reflect the method by which the contractor will meet the level of required performance and quality reflected in Table 5.1.

The QCP must be developed using the contractor’s internal quality control methods and must address surveillance of all deliverables under the terms of this contract. The contractor may modify the minimum standards of performance compliance as appropriate to improve the required compliance level, however, the compliance levels may not be adjusted down.

The QCP must be submitted to the CO and COR no later than the date of the kickoff meeting, for approval.

5.2 Contractor Staffing

The contractor must provide a program management team with contract authority to make decisions regarding the execution of this contract. The contractor must provide all personnel positions, to include those listed in Table 5.3. Additionally, at the start of each option year, the contractor must provide to the CO, AF TENCAP COR a listing of key personnel who will perform the functions outlined in this PWS.

The list must contain the full name of each key personnel employee, job title or position held, work assignment, and level of security clearance. The contractor must maintain this list throughout the life of the contract and must notify the CO and COR, in writing, of any addition, deletion, or change within seven (7) calendar days of such change. The COR and CO must approve any change in key personnel prior to any changes.

This contract requires that all assigned contractor personnel possess a minimum active Top Secret (TS) Security clearance at the time of POP Start Date with the ability to be granted access to SCI material post award. The contract requires cleared personnel with the IT training/background to work with SAP network equipment (e.g. servers/storage/peripherals/ /multimedia) and software (e.g. server virtualization, network management, network defense, collaboration, and security). The contractor must provide certified IT personnel IAW DoDM 8570.0 and DoDD 8140.01.

5.3 Labor Hours/Categories

The Government anticipates the vendor will require a total level of effort (LOE) as identified in Appendix A, Workload Data Estimate, to complete this task. The pricing Worksheet delineates each labor category and is considered a labor category ceiling. This is only an estimate and actual LOE required in performance of the contract may vary from the proposal estimate.

The Government considers 1880 hours (excludes federal holidays) as full time equivalent (FTE).

Labor shall be performed at the rate agreed to at the time of contract award for the base period (and any option periods, if applicable), and no additional rate increases shall be allowed after award. All awarded rates shall be fully-burdened Labor Hour rates, and the rates shall not be subject to “finalized audited rates” by the Defense Contract Management Agency (DCAA) or other third party auditor.

Requirement Type Base Year Option 1 Option 2 Option 3…