Performance Work Statement.pdf

CUI

PERFORMANCE WORK STATEMENT (PWS)

for

THUNDER COMMERCIALLY AUGMENTED MISSION PLATFORM (CAMP):

DEVSECOPS SOFTWARE LICENSE

PROCUREMENT AND MANAGEMENT SERVICES

U.S. AIR FORCE

1/28/2026

Distribution Statement D applies. Distribution authorized to the Department of Defense and U.S.

DoD Contractors only, Critical Technology, 1 January 2024, other requests for this document shall be referred to 76 SWEG, 7532 Joint Stars Dr, Tinker AFB OK 73145

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Performance Work Statement for DevSecOps Software License Procurement and Management Services (Revision 1.0)

CUI

CUI

Revision Table Revision

# Date Change Activity

1.0 28 January 2025 Original

CUI

CUI

Table of Contents

Introduction

1.1 Background

1.2 Scope

Performance Requirements

2.1 General Software License Management

2.2 Procurement of Existing Software Renewals

2.3 Software License Expiration

2.4 Evaluation Software Licenses

2.5 Procurement Research of New Software Selection

2.6 Software License/Support Delivery

2.7 Software Vendors

2.8 Software License Management Records

2.9 Supply Chain Risk Management

2.10 Weekly Status Meeting

2.11 Weekly Status Report

General Requirements

3.1 Program Management

3.2 Contractor Identification

3.3 Base and Network Access

3.4 Personnel

3.5 Standard Operating Hours

3.6 Financial Reporting

3.7 Risk Management

3.8 Quality Control

3.9 Data Management

3.10 Security Requirements

3.11 Contractor Manpower Reporting (FY11 NDAA Section 8108)

Service Summary

CDRL Summary

Managed Initial Software Tools

Introduction

1.1 Background

Thunder CAMP is a 76th Software Engineering Group (76 SWEG) team that was organized as a Cloud Infrastructure pathfinder for embedded weapons systems. Thunder CAMP provides several mission critical Program Offices (customers) an innovative customizable cloud environment, allowing them to push past constraints and maintain/develop new technologies to defend national security. To overcome standard software procurement timeframes, Thunder CAMP leveraged Platform One's Basic Ordering Agreement (BOA) to establish a contract action by which software could be procured more rapidly.

Thunder CAMP has customers with fast-moving requirements and would be unable to support the multiple customer requirements without the ability to utilize a BOA.

1.2 Scope

This Performance Work Statement (PWS) identifies the requirements for the 76 SWEG / Thunder CAMP Software Toolchain Procurment and Management Services to include: preparation of software approval packages, software license procurement, and assist 76th SWEG with their software license management responsibilities. Software licenses will consist of Commercial Off the Shelf (COTS) software applications to support the 76 SWEG / Thunder CAMP. This PWS is to identify the support needed to augment the 76 SWEG / Thunder CAMP Software team as it pertains to software license procurement and software license management services. The total Period of Performance (PoP) shall be 6 months.

1.2.1 Objective

This effort requires identification, selection, procurement, and management of various DevSecOps related software tools. Because of changing technologies, requirements, and users, software licenses must be carefully managed. Under this order, the Contractor shall perform software license management services.

1.2.2 Work Location

The Contractor shall perform the necessary services to support the existing and evolving commercially available software needs. The Contractor shall be located at the Contractor’s facilities, or in other facilities as specified or allowed by the Contractor’s policies. The Government will not provide facilities, facility space, or equipment for the Contractor’s work related to this PWS.

1.2.3 Software Definition

In this document, “Software” and, interchangeably, “Software Tools” refer to any software-related items such as applications, code, scripts, plug-ins, software support/services, and subscription services, in a broad sense of the terms; items that may require “licenses” or license management.

1.2.4 Contractor Participation

The contractor shall work remotely (i.e. not at Tinker AFB); however, the contractor is expected to participate in team culture including all virtual meetings as required to support the requirements of this

CUI

CUI

PWS as well as other Software team meetings as deemed necessary by 76 SWEG/ Thunder CAMP’s Software Program Manager (PM). The contractor’s Quality Assurance Surveillance Plan (QASP) performance threshold will not be impacted due to meetings with less than 2 business days advance notice but will be expected to make any and all reasonable accommodation to attend meetings with less than 1 business day advance notice.

CUI

CUI

Performance Requirements

2.1 General Software License Management

The Contractor shall perform the necessary actions to assist in managing the existing and evolving Software Toolchain(s) in all stages (procurement, delivery, renewal). The contractor shall support an Agile environment where the scope of work can and will change at any time as needed. Outlined below are some of the critical requirements for this work.

The initial list of Software Tools listed in Table 6-1 shall be managed, in addition to any new Software Tools requested by the Procurement Contracting Officer (PCO).

2.2 Procurement of Existing Software Renewals

When notified by the PCO, the Contractor shall procure license renewals for software which have previously been purchased by the Government or by the Contractor through this PWS. The initial list of software in Table 6-1 has already been purchased and is expected to change as new software is procured by the Government or by the Contractor. The Contractor shall deliver, within five (5) business days of Government notification, the license keys, installable software (if needed), and other information required to install and use the software tool.

2.3 Software License Expiration

For all licenses managed or procured under this contract, the Contractor shall monitor individual software license expiration. This shall be included as part of the Weekly Status Report. Upcoming expirations shall be tracked at 120-140 calendar days, and then again at 90-100 calendar days prior to expiration in the report, giving the Government PM time to determine whether all license information is correct and if renewal is required. Renewals shall not be automatic.

2.4 Evaluation Software Licenses

In some cases, the Government may acquire, or have acquired, no-cost trial Software licenses for assessment and/or testing purposes. In other cases, the Government PM may request the Contractor to provide trial licenses, at no cost to the Government. The Contractor shall manage trial licenses the same as other licenses, as applicable, under this order. The Contractor shall work to help ensure seamless transition of trial licenses to purchased/full licenses, if such full licenses are requested under this order.

Trial Software licenses and their status shall be tracked as part of the Weekly Status Report.

2.5 Procurement Research of New Software Selection

When the Government has a new software tool requirement, the Government PM will contact the Contractor and either 1) provide a set of requirements for the Contractor to provide a recommendation via market research, or 2) provide a specific software specification for the Contractor to provide a quote.

Price quote requests shall be tracked and monitored as part of the Weekly Status Report.

CUI

CUI

2.5.1 Software Market Research

When tasked by email from the Government PM, the Contractor shall generate a Software Market Research Report. This report shall be due within ten business days from tasking and all software market research taskings shall be included in the Weekly Status Report.

Taskings for software market research reports include performing the market research and assessing COTS solutions available to meet outlined needs from a functional, enterprise and security standpoint.

Tasks may include but are not limited to:

• The report shall include a market research summary with an assessment of any available alternative solutions and support for any recommendations

• The report shall include a list of potential solutions that best meet the capability need

• The report may include researching opportunities for price breaks with ladder pricing or quantity breaks that may reduce overall Government software license costs

• The Contractor shall notify the Government of all communications with existing and potential

COTS vendors

• The report shall note any COTS solution where the Air Force has an existing software licensing agreement in place (i.e. DoD Enterprise Software Initiative, ESI.mil)

• The Contractor shall use existing enterprise level software licensing agreements that fulfill the identified need where possible

2.5.2 Software Quote Report

When tasked by email from the Government PM, the Contractor shall generate a Software Quote. The quote shall be due within seven business days from tasking and all Software Quote taskings shall be included in the Weekly Status Report.

All software quotes shall contain at a minimum but not limited to the following: SKU, Desciption, POP Start, POP End, Quantity, Unit Cost, Total Line Item cost, Total cost of all line items, Quote expiration date, and link to EULA. When providing a Software Quote, the Contractor shall also provide ladder pricing (quantity breaks) for additional software purchases of different quantities when available. Cost quotes provided (and thus cost paid for by the Government) shall not be greater than typical government pricing or commercial pricing.

2.5.3 Software Maintenance and Support

If available from a software vendor, along with software license delivery, the Contractor shall also inquire about software vendors providing yearly maintenance and support for software. The Contractor shall provide support information in the Procurement Research Report.

2.5.3.1 Software Support and Maintenance

In addition to the procurement and management of licenses, the Contractor shall propose a method to provide software support, as requested, for tasks that may not be included in the price of the license to include but not limited to Help Desk, customer support, Enterprise Software Support, and reach back support during business days/hours. Software Support and Maintenance can also be utilized when the Government determines that the workload of the Software Engineer/License Manager or Procurement

CUI

CUI

Manager is at maximum capacity, and the increased need for temporary technical/specialized expertise or additional manpower (permanent or temporary) may be justified. Effective support requires the coordination with outside resources to mobilize staff and, in some cases, coordinate with outside resources to fulfil a need. Any software support/maintenance issues shall be addressed and/or negotiated through the PCO, when needed.

2.6 Software License/Support Delivery

When notified by the PCO to deliver specific/new software licenses (reference PWS paragraphs 2.5) and available software support (PWS paragraph 2.5.3), the Contractor shall deliver, within five (5) business days, the license keys, installable software (if needed), and other information required to install and use the software tool.

All deliveries of software licenses shall be made in accordance with (IAW) the individual purchase order.

Upon receipt of order confirmation of new licenses or renewals, the Contractor shall inform the Government PM and Contracting Officer Representative (COR) by email notifying successful purchase.

Government SLM shall notify Government PM when license deliveries are complete and accurate.

2.7 Software Vendors

Third party vendors providing licenses must be authorized Original Equipment Manufacturer (OEM) resellers or distributors of the required software at the time of purchase and must provide proof of authorization. To deliver licenses, the Contractor shall utilize any existing software licensing agreements or Government Acquisition vehicles already in place to include the original equipment manufacturer or authorized Government distributors, if necessary.

2.8 Software License Management Records

Along with license delivery, the Contractor shall deliver copies of Proof of Purchase collaterals and license agreements for all licenses to the Government PM and the COR.

After delivery, the Contractor shall work with the Government PM and/or software license manager to gather information needed to assist the 76th SWEG properly manage software licenses throughout their life. The Contractor shall keep license records that, at a minimum, include manufacturer, name of software, version of software, part number (if applicable), license type, vendor, acquired date, expiration date, cost, and Government POC (name, email, and phone number). Upon request by the Government PM or COR, the Contractor shall provide a copy of any software license management records to the Government PM and COR within three (3) business days of request.

CUI

CUI

2.9 Supply Chain Risk Management

2.9.1 The Contractor shall report all suspected malicious/counterfeit vendors and/or materials/items to the Government PM, COR, and program office via email to the PCO within five (5) business days of discovery. The Contractor shall prominently identify, segregate and label all suspected malicious/counterfeit material/items/correspondence and separate from all other supplies. The Contractor shall not return or dispose of suspected or confirmed counterfeit material/items/correspondence to the supplier but hold such items for Government analysis and investigation. The Contractor shall aid the Government investigation including providing all documents associated with the purchase, shipping, and other relevant data on the counterfeit materials/items/correspondence. The PCO will provide final disposition instructions for confirmed malicious/counterfeit material/items/correspondence to include turnover to the Government.

2.9.2 Supply Chain Security: Key Requirements

2.9.2.1 Diverse Sourcing: the Contractor shall use multiple suppliers for systems, components, and services whenever possible to reduce targeting risk and impact from events. Example: Multiple software resellers.

2.9.2.2 Harm Limitation: The Contractor shall employ controls against supply chain attacks. Example:

Use approved vendor lists when possible (DoD ESI, NASA SEWP).

2.9.2.3 Tiered Control Flow: the Contractor shall ensure supply chain risk management controls are enforced across all supplier tiers. Example: Contractors must vet all sources.

2.9.3 Counterfeit Material Investigation

At least annually, the Contractor shall evaluate all vendors currently in use to verify software/licenses were acquired from genuine sources. The Contractor shall include a statement certifying authenticity for each of the evaluated vendors in the Weekly Status Report at the beginning of the following quarter.

2.10 Weekly Status Meeting

The Contractor shall participate in a one-hour weekly meeting using Microsoft TEAMS. The intent of this meeting is to coordinate and update on-going efforts with the Government PM team and their Software License Managers (SLM)s. The Government PM may ask the Contractor to host this meeting and may cancel the meeting when it is determined the meeting is not needed. The meeting will discuss, and coordinate items included on the Weekly Status Report.

2.10.1 Technical Coordination Meetings

The Contractor shall support additional Technical Coordination Meetings as required to discuss software versions, needs, or other technical details to ensure effective and accurate acquisition of software tools.

All meetings shall be coordinated through the Government PM, COR, or any designated Government teams, to include but not limited to the SLM(s).

CUI

CUI

2.11 Weekly Status Report

The Contractor shall provide a Weekly Status Report that includes the status of on-going efforts related to this contract. The Contractor shall update the report each week and provide it to the Government PM and COR before each Weekly Status Meeting.

Each Weekly Status Report shall include at minimum the following elements:

• Software License Renewal & Expiration (Ref 2.2 & 2.3)

• Evaluation Software Licenses (Ref 2.4)

• Procurement Research Status (Ref 2.5)

• Software Delivery Status (Ref 2.6)

• Counterfeit Material Investigation (Ref 2.9.2)

• Minutes from the previous week’s Status Meeting (Ref 2.10)

• Technical Coordination Meetings (Ref 2.10.1)

• Program Management (Ref 3.1)

• Financial Reporting (Ref 3.6)

• Identified Risks (Ref 3.7)

CDRL A001 Weekly Status Report

CUI

CUI

General Requirements

3.1 Program Management

The Contractor shall provide any equipment, materials, and supplies deemed necessary to meet the requirements of the PWS. The Contractor shall integrate and coordinate all activity required to execute this contract and manage the timeliness, completeness, and quality of problem identification. The Contractor shall provide corrective action plans, timely identification of issues, and effective management of subcontractors. The Contractor shall have a single point of contact between the Government and Contractor personnel to support business relations.

3.2 Contractor Identification

If the Contractor meets with Government personnel and/or other Government partners, the Contractor personnel shall identify themselves as “Contractors”.

3.3 Base and Network Access

A Contractor Common Access Card (CAC) may be required to access Government networks with shared databases.

• For a CAC to be issued to Contractor personnel, an MP-ICAM Form will be submitted to Security Forces, Pass and Registration through the COR.

• The Government Program Manager, or designee, will assist contractor personnel in processing the necessary DoD forms to obtain base or area badges for access to Government network.

• The Contractor shall comply with all DoD, Air Force, and location specific security requirements

• The contractor must have at a minimum a Favorable Clearance to have access to the Thunder

CAMP environment

• When the period of performance is complete or contractor personnel leave work on this project, they will have five (5) working days to terminate all their network user account and to return all access cards and base identification badges.

3.4 Personnel

The Contractor shall ensure personnel are assigned that can perform the requirements of this PWS without any gaps in service. The contractor must be able to maintain a Favorable Clearance.

3.5 Standard Operating Hours

The Contractor shall be available during operating hours between 8:00 AM and 4:00 PM Central Time (CST), Monday through Friday, excluding observed Federal holidays (New Year’s Day, Martin Luther King Day, President’s Day, Memorial Day, Juneteenth Day, Independence Day, Labor Day, Columbus Day, Veterans’ Day, Thanksgiving, and Christmas). Preferred communication methods include but are not limited to: Microsoft Outlook, Microsoft Teams instant messaging, video conference calls, Mattermost, text, and voice calls. The Contractor may be required to operate after normal business hours if the need arises. The Government COR will coordinate other-than-normal operating hours with the Contractor as far in advance of need as practicable. Overtime should not be used, but if required, shall be justified to, coordinated with and approved by the PCO beforehand.

3.6 Financial Reporting

The Contractor shall submit cost reports as part of the Weekly Status Reports. Cost reporting shall include detailed expenditures incurred in the previous 12 months. Cost reporting shall also include funds expended and committed during the previous 12 months annotated at the sub-CLIN level.

3.7 Risk Management

The Contractor shall utilize risk management procedures, techniques, controls, and metrics to provide for the early identification of program risks. A list of identified risks along with their impact and probability shall be included in the Weekly Status Report.

3.8 Quality Control

The Contractor shall conduct quality control inspections that ensures that all aspects of contract performance are being met. The methods used by the Government to assess performance and resolve issues, or unacceptable performance is outlined in the QASP.

3.9 Data Management

The Contractor shall use sound data management for developing, acquiring, controlling, and delivering all required technical, management and other data. The Contractor shall ensure on-time delivery of data; data quality; accurate updates and revisions and corrections to data as required; and proper identification, marking and control of proprietary, For Official Use Only, and classified data.

3.10 Security Requirements

The Contractor performing work under this contract must comply with all applicable security requirements.

3.10.1 Operations Security (OPSEC)

The Contractor shall ensure OPSEC is incorporated into the appropriate area of the contract IAW DoD Directive 5205.02E, DoD Operations Security (OPSEC) Program and AFI 10-701 Air Force OPSEC Program. The Contractor shall flow down all OPSEC requirements to subcontractors that handle Critical Information (CI). CI is defined as specific facts about friendly intentions, capabilities, or activities needed by adversaries to plan and act effectively against friendly mission accomplishment.

3.10.2 Controlled Unclassified Information (CUI)

The Contractor shall comply with DoDM 5200.01, Volume 4, DoD Information Security Program: CUI, Enclosures 3 & 4, for identification, protection, and training requirements of CUI. The Contractor shall be responsible for training their personnel and accomplishment of the out-processing procedures identified in DoDM 5200.01, Volume 4, Enclosure 4. The Contractor shall comply with DoDM 5400.07/Air Force Manual 33-302, DoD Freedom of Information Act (FOIA) Program requirements. Protection of unclassified DoD information not approved for public release on non-DoD Information Systems will be protected IAW DoDI 8582.01, Security of Unclassified DoD Information on non-DoD Information Systems, Enclosure 3.

CUI

CUI

The Contractor shall distribute controlled unclassified information IAW DoD Instruction 3200.14, Principles and Operational Parameters of the DoD Scientific and Technical Information Program, and DoD Instruction 2040.02, International Transfer of Technology, Articles, and Services. The Contractor shall properly mark all such documents IAW DoD Instruction 5230.24, Distribution Statements on Technical Documents. Technical documents not subject to distribution are defined in DoD Instruction 5230.24, DoD Directive 5230.25, and DoD Manual 5010.12-M, Procedures for the Acquisition and Management of Technical Data.

The Contractor shall provide to the Government, a system security plan (or extract thereof) and any associated plans of action developed to satisfy the adequate security requirements of DFARS 252.204- 7012, and in accordance with NIST Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations” in effect at the time the solicitation is issued or as authorized by the PCO, to describe the Contractor’s unclassified information system(s)/network(s) where covered defense information associated with the execution and performance of this contract is processed, stored, or transmitted. t

CDRL A002 Contractor’s System Security Plan

3.10.3 Disseminating Scientific and Technical Information (STINFO)

The Contractor shall use AFI 61-204, Disseminating Scientific and Technical Information and DoDI 5230.24, Distribution Statements on Technical Documents, when developing, reviewing, or assisting the US Government and other supporting Contractors, to identify any “sensitive” media that should not be placed into the Public Domain (e.g., Classified, For Official Use Only), as well as ensuring applicable Distribution Statement, Handling and Destruction Notice, Warning Statement (for technical information with Space/Military Application under the International Traffic Arms Regulation (ITAR) or the Export Arms Regulation for dual-use technologies), along with the Expanded Exemption Statement are applied.

The Contractor shall consult with the Government PM to determine the appropriate Distribution Statement for the media. From the time of creation by the Contractor, the Contractor shall properly mark, properly handle, secure, and dispose of any sensitive media in the Contractor’s immediate control. The Contractor shall advise and alert the Government, and other supporting Contractors of these requirements, for any sensitive media received which is not appropriately marked.

3.11 Contractor Manpower Reporting (FY11 NDAA Section 8108)

The Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The Contractor is required to completely fill in all required data fields in the Service Contract Report (SCR) at www.SAM.gov.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year Contractors may direct questions to the SAM.gov service desk (https://www.fsd.gov/fsd-gov/home.do).

*Reporting Period: Contractors are required to input data by 31 October of each year.

CUI

CUI

Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and Contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the Contractor name and contract number associated with the data.

User Guide: Data for Air Force service requirements must be input at www.sam.gov. A quick start user guide is available at on the SAM.gov website at https://sam.gov/SAM/transcript/SCR_QSG.pdf. In addition, a full user guides for Contractors and Government personnel are available at https://www.sam.gov/SAM/pages/public/help/samUserGuides.jsf.

CUI

CUI

Service Summary

The methods used to assess performance and resolve issues, or unacceptable performance is outlined in detail in the QASP for this effort.

Performance Objective

PWS

Para

Performance Threshold

Surveillanc e Method

SS-1. Procure Software Renewals:

Deliver, within five business days of Government notification, the license keys, installable software (if needed), and other information.

2.2 Delivery: 100% of the time.

Within Schedule:

Satisfactory: 95% percent of deliverables shall be delivered within five business days.

Marginal: The remaining 5% of deliverables shall be delivered within three business days after initial suspense date.

NOTE 1: For this objective, a late submission is when the deliverable is not delivered to the Govt within the specified suspense date (11:59 PM Central).

NOTE 2: For purposes of calculating performance threshold requirements, cumulative calculations will be used for each contract year. All fractional numbers shall be rounded up to the next whole number.

100% Inspection

SS-2. Procurement Research of New Software:

Deliver market research reports within ten business days

2.5.1 Delivery: 100% of the time.

Within Schedule:

Satisfactory: 95% percent of deliverables shall be delivered on time.

Marginal: The remaining 5% of deliverables shall be delivered within five business days after initial suspense date.

NOTE 1: For this objective, a late submission is when the deliverable is not delivered to the Govt within the specified suspense date (11:59 PM Central).

100% Inspection

CUI

CUI

NOTE 2: For purposes of calculating performance threshold requirements, cumulative calculations will be used for each contract year. All fractional numbers shall be rounded up to the next whole number.

SS-3. Provide Quotes:

The contractor shall deliver quotes within seven business days.

2.5.2 Delivery: 100% of the time.

Within Schedule:

Satisfactory: 95% percent of deliverables shall be delivered within seven business days.

Marginal: The remaining 5% of deliverables shall be delivered within three business days after initial suspense date.

NOTE 1: For this objective, a late submission is when the deliverable is not delivered to the Govt within the specified suspense date (11:59 PM Central).

NOTE 2: For purposes of calculating performance threshold requirements, fractional numbers shall be rounded up to the next whole number.

100% Inspection

SS-4. Weekly Status Reports:

The Contractor shall deliver a Weekly Status Report that includes all elements outlined in paragraph 2.11

2.11 Delivery: 100% of the time (except in cases

where expressly excused by the Government PM or COR).

Satisfactory: 95% of reported elements are included and are accurate.

Marginal: The remaining 5% shall remain rejected until corrected and resubmitted in the following Weekly Status Report.

Unsatisfactory: Identified deficiencies are not corrected in the next Weekly Status Report.

NOTE 1: For purposes of calculating performance threshold requirements, fractional numbers shall be rounded up to the next whole number.

100% Inspection

CUI

CUI

CDRL Summary

Contract information data shall be delivered electronically in accordance with the corresponding requirement for each Data Item listed in Table 5-1 (below). The contractor shall have no more than one error per quarter for all CDRL submittals. The contractor shall submit CDRLs according to the due date indicated. Grammatical errors do not count as an error. Substantive mistakes shall be corrected within two business days and corrective action taken to prevent recurrence of inaccurate late CDRLs.

Table 5-1

CDRL Title PWS Paragraph

CDRL A001 Weekly Status Report 2.3, 2.4, 2.5, 2.9.1, 2.10, 2.11, 3.6, 3.7, SS-4

CDRL A002 Contractor System Security Plan 3.10.2

CUI

CUI

Managed Initial Software Tools

The Government will provide the Contractor with an initial list of software to be managed by the Contractor after the contract is awarded. The Contractor shall procure licenses for at least three (3) separate cloud environments at the outset, and the number of cloud environments is expected to grow by at least two (2) per year. Each cloud environment will support approximately 50 different software titles in varying counts of as few as 1 license of a given title to as many as 3,000 licenses or more (e.g.

Atlassian products to support all users in each environment). No individual license purchased through this contract shall exceed a cost of $250,000 per license, and no purchase of perpetual license shall be equal or greater than $250,000 per purchase in accordance with the Capital Investment Program (CIP) Policy.

Each cloud environment is customized to the needs of the customer utilizing the service and always evolving. Every license procured for these environments shall be managed in accordance with the PWS.

This list is subject to change as this contract proceeds.

2.9.3 Counterfeit Material Investigation

2.11 Weekly Status Report

3.11 Contractor Manpower Reporting (FY11 NDAA Section 8108)