BASIS PWS061126 CM051120261134.pdf

CUI

PERFORMANCE WORK STATEMENT

Business Administration and Support Integrated Services

Defense Innovation Unit

June 5, 2026

PART 1

GENERAL INFORMATION

1 INTRODUCTION: This is a non-personal services contract to provide administrative and support services to DIU personnel in fulfillment of its mission areas. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn, is responsible to the Government.

1.1 BACKGROUND: The Defense Innovation Unit (DIU) facilitates collaborative partnerships between the Department of War (DoW), venture-backed technology companies, and other non-traditional innovation communities to expand the national security innovation base and address national security challenges. Doing so enables the DoW to leverage its unique acquisition process, reducing procurement timelines, and accelerating the integration of commercial solutions into defense operations. The DIU enterprise encompasses expertise, capabilities, and relationships across several commercial technology areas; public and private sectors; academia; and other communities of interest both United States (U.S.)-based and internationally.

In 2023, the Secretary of War (SecWar) realigned the Defense Innovation Unit (DIU) to report directly to the SecWar, reinforcing its role as the DoW’s primary gateway for commercial technology adoption. This realignment expanded DIU’s authority and responsibilities to accelerate the fielding of emerging technologies at scale, ensuring faster access to commercially developed capabilities that meet national security needs.

With offices in Silicon Valley at Mountain View, CA (MV), and the National Capital Region around Washington DC (NCR), DIU serves as the DoW’s central hub for engaging commercial innovators. DIU continues to strengthen national security by bridging commercial sector innovation with DoW mission requirements, ensuring the rapid deployment of technology solutions that enhance U.S. defense capabilities.

Services include:

a. Direct support to the core functions of DIU Functional Areas to include, but not limited to:

1. Information Technology

2. Security

3. Facilities

4. Contracting and Acquisitions

5. Program Management Support

6. Strategic Communications

7. Congressional Affairs

8. Resource Management

9. Business Operations and Records Management

10. Office of the General Counsel

11. Human Resources

12. FAR-Based Contract Management

1.2 AGENCY MISSION: DIU strengthens national security by accelerating the adoption of commercial technology across the U.S. military and bolstering our allied and national security innovation bases. DIU partners with organizations across the DoW to rapidly prototype and field dual-use capabilities that solve operational challenges at speed and scale. With offices in MV and NCR, DIU is the DoW’s gateway to leading technology companies across the country.

DIU is the only DoW organization focused exclusively on fielding and scaling commercial technology across the U.S. military at commercial speeds. Our expert team, working in nine critical technology sectors, engages directly within the venture capital and commercial technology innovation ecosystem, many of which are working with the DoW for the first time. Our streamlined process delivers prototypes to our DoW partners, along with scalable revenue opportunities for our commercial vendors, within 12 to 24 months.

1.3 DESCRIPTION OF SERVICES: The Contractor shall provide administrative and support services to DIU personnel in fulfillment of its mission areas as defined in this PWS. The Contractor shall perform to the standards in this contract.

1.4 OBJECTIVES: The purpose of this contract is to provide back-office support services for DIU, so DIU can meet its objectives of accelerating the identification, acquisition, prototype, and transition of stable commercial technologies across the DoW, thus, delivering innovation at commercial speeds and greater scale with an emphasis on solutions most effective in a joint-warfighting environment.

1.5 SCOPE: The contractor shall provide administrative and other support services as defined in this PWS.

The contractor shall provide support in the areas of information technology (IT), security and facilities, contracting and acquisitions, program management support, strategic communications, Congressional affairs, resource management, human resources, office of the general counsel, and records management.

1.6 PERIOD OF PERFORMANCE: The anticipated Period of Performance (PoP) shall consist of a 12-month Base period, and four (4) 12- month option years. The contractor shall commence work on the first day of the PoP. The projected PoP is as follows:

Base Period: February 19, 2027 through February 18, 2028 Option Period 1: February 19, 2028 through February 18, 2029 Option Period 2: February 19, 2029 through February 18, 2030 Option Period 3: February 19, 2030 through February 18, 2031 Option Period 4: February 19, 2031 through February 18, 2032

1.7 CONTRACT TYPE: The government will award a hybrid type contract consisting of Firm Fixed Price (FFP), cost reimbursable Other Direct Costs (ODC), and Labor Hour (LH) contract line-item numbers (CLINs).

● LH CLIN: The contract will include “not-to exceed” ceiling in an amount established by the Government for ODC(s) and Travel. If the contractor exceeds the ceiling price for T&M CLINs, the contractor will do so at its own risk.

● ODC CLIN: The contract will include CLINs for other direct costs (ODCs) used for the purchase of conference fees, subscriptions, equipment, materials, software licenses, and related supplies critical and related to the services being acquired under the TO. If the contractor initiates a purchase within the scope of this TO, the contractor shall submit to the COR a request to initiate purchase (RIP). Templates will be provided on contractor request.

The RIP shall:

o Be prepared in a legible manner o Include the purpose of the purchase o Specify the items being purchased o Show the estimated cost of the purchase o Include a cost comparison o Show the rationale behind the purchase

The contractor shall not make any purchase without an approved RIP from the COR. RIPs shall be submitted for approval via email.

● Travel CLIN: The contract will include CLINs for travel costs.

1.8 PLACE OF PERFORMANCE: The work to be performed under this contract will be performed at Government sites as well as the Contractor site(s). Government office spaces will be provided in MV and the NCR.

1.9 TELEWORK: The Government may permit telecommuting (telework) or remote work for contractors when determined to be in the best interest of the Government in meeting requirements depending on the description of work that needs to be performed. The Contractor must have an established telework agreement subject to review by the Government. The telework agreement must be approved by the Contracting Officer Representative (COR). Telework and remote work must be approved in writing by the COR in advance and will be at no additional cost to the Government. Prior to approving telework, contractors will be required to take employer provided telework training.

1.10 RECOGNIZED HOLIDAYS: Government personnel observe the following holidays as governed by 5

U.S.C. § 6103. Government facilities will be closed and unavailable to Contractor personnel:

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day Washington’s Birthday Veterans Day Memorial Day Thanksgiving Day Juneteenth Independence Day Christmas Day

*If the date falls on a Saturday, the Government holiday is the preceding Friday. If the date falls on a Sunday, the Government holiday is the following Monday.

In addition to the days designated as holidays, the Government observes the following days:

• Any other day designated by Federal Statute

• Any other day designated by Executive Order

• Any other day designated by the President’s Proclamation

1.11 QUALITY CONTROL/ASSURANCE:

1.11.1 Quality Control: The contractor shall identify and implement its approach for providing and ensuring quality throughout its solution to meet the requirements of the TO. The contractor shall provide a QMP and maintain and update it as changes in the program processes are identified (Section 7, Deliverable 07). The contractor’s QMP shall describe the application of the appropriate methodology (e.g., quality control and/or quality assurance) for accomplishing TO performance expectations and objectives. The QMP shall describe how the appropriate methodology integrates with the Government’s requirements.

1.12 PERSONNEL MATTERS

1.12.1 Key Personnel: The following are the minimum personnel who shall be designated as “Key.” The Government does not intend to dictate the composition of the ideal team to perform this TO. If the offeror proposes additional Key Personnel, the contractor shall provide the specialized experience and the corresponding qualifications for this experience. The Government will consider up to three additional Key Personnel (for a total of four Key Personnel). The Government may unilaterally incorporate the proposed additional Key Personnel qualifications and experience into the TO at award. The proposed Key Personnel shall possess all required qualifications (those designated as “required”) at time of proposal submission. The Government desires that Key Personnel be assigned for the duration of the TO.

1.12.2 The Contract Program Manager is considered key personnel by the government. The contractor shall identify a contract program manager by name who shall provide management, direction, administration, quality assurance, and leadership of the execution of this TO, including assigning tasks to contractor personnel, supervising ongoing technical efforts, and managing overall TO performance. The contract program manager shall be responsible for the quality and efficiency of the TO, including technical issues and business processes. It is required that the contract program manager be an employee of the prime contractor and have the authority to make decisions for the contractor’s organization in response to Government issues, concerns, and comments, as well as be proactive in alerting the Government to potential contractual, programmatic, and resource limitation issues.

It is required that the contract program manager has the following qualifications:

● A minimum of five years of experience, within the last ten years, managing projects that are of a similar scope and complexity to the Section 5 requirements, such as working on DoW projects supporting operations, information, and innovation of technologies.

● A current Project Management Institute (PMI) Project Management Professional or Program Management Professional (PgMP) certification.

1.12.3 The contractor shall not replace any personnel designated as Key Personnel without the written concurrence of the Contracting Officer. Prior to utilizing other than the Key Personnel specified in its proposal in response to the task order request (TOR), the contractor shall notify the CO and COR. This notification shall be no later than ten calendar days in advance of any proposed substitution and shall include justification (including resume(s) and labor category of proposed substitution(s)) in sufficient detail to permit evaluation of the impact on TO performance.

Substitute Key Personnel qualifications shall be equal to, or greater than, those of the Key

Personnel substituted. If the CO and the COR determine that a proposed substitute Key Personnel is unacceptable, or that the reduction of effort would be so substantial as to impair the successful performance of the work under the TO, the contractor may be subject to default action as prescribed by FAR 52.249-8.

1.12.4 Identification of Contractor Employees: All contract personnel attending meetings, answering

Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as contractors to avoid creating an impression in the minds of members of the public that they are Government officials. Contractors must also ensure that all documents or reports produced are suitably marked as contractor products and that contractor participation is appropriately disclosed. Contractor personnel will be required to obtain, use, and display a CAC in the performance of this contract. Contractor email signatures shall be standard and consistent for current and future Contractor employees. As stated in 48 CFR 211.106, Purchase Descriptions for Service Contracts, contractor personnel shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and by displaying distinguishing badges or other visible identification for meetings with Government personnel. Contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

1.13 SECURITY:

1.13.1 Defense Contractors performing on classified efforts are required to comply with the 32 CFR Part 117 National Industrial Security Operating Manual (NISPOM). The Contractor is required to obtain and maintain a TOP SECRET (TS) Facility Clearance (FCL) for the duration of the period of performance.

Contractor personnel are not authorized to access classified information until such time as the FCL is issued. Contractor personnel supporting classified efforts are required to obtain and maintain personnel security clearance eligibility at the level required to perform their job duties. Personnel access level will not exceed the Contractor’s FCL. The security requirements are in accordance with the attached DD Form 254.

Requirements Exceeding the NISPOM: (1) Contractors requiring routine physical access to government facilities are required to complete Antiterrorism Level I training. (2) Elements of this effort are protected by an operational security (OPSEC) critical information list (CIL). The Contractor is required to implement OPSEC protection measures as directed by the government information owner.

Other Required Security Access: Communications Security (COMSEC), Sensitive Compartmented Information (SCI), Special Access Program (SAP)

Classified Performance Locations:

● Defense Innovation Unit - 230 RT Jones Road, Mountain View, CA 94043

● Defense Innovation Unit - 4800 Mark Center Drive, Alexandria, VA 22350

● Defense Innovation Unit - 1000 Defense Pentagon, Washington, D.C.20301

Visit Requests: The contractor must maintain a perm cert/long term visit request in the Defense Information System for Security (DISS) for all personnel supporting classified performance. The perm cert should be updated as employees on/off board and be checked for accuracy periodically. Follow these instructions:

● Create New Visit

● Find Hosting Security Management Office (SMO): DDAADIU

● Existing SMO Location: Select ‘No location’

● Visit Name: Perm Cert (YOUR CAGE CODE)

● End Date: One year from submission date

● Access Level: The clearance level as identified in block 1a of the DD254

● Reason: Select ‘Other’

● 8: Visit Notes: Enter Prime Contract Number

● Add employees

Additional security requirements and guidance are reflected in the attached DD Form 254.

Contractor personnel performing work under this contract must have the appropriate security clearance eligibility and must maintain the level of security required for the life of the requirement. Personnel working in a SCI Facility (SCIF) or providing SCIF support will require TS with SCI eligibility at the start of performance. The contractor shall propose appropriate clearance levels for contract personnel in the staffing plan.

The Contractor shall notify the COR of all terminations/ resignations, etc., within five (5) calendar days of occurrence. The Contractor will return any expired government issued Common Access Card (CAC), or those of terminated employees to the COR. If an identification card or building pass is not available to be returned, a report must be submitted to the COR, referencing the pass or card number, name of individual to whom issued, and the last known location and disposition of the pass or card. The COR will return the identification cards and building passes in accordance with facility policies.

Prior to onboarding with DIU, all contractors must have an approved Single Agency Check (SAC) in order to be provisioned a Department of Defense Common Access Card (CAC).

The Contractor shall provide a written detailed report of any adverse information related to its employees to the CO, as soon as possible. The report shall contain detailed and relevant information.

The subsequent termination of employment of an employee does not obviate the requirement to submit this report.

The Contractor is required to report certain events that have an impact on the status of the facility clearance (FCL) and/ or the status of the contract employee’s personnel security clearance as outlined by National Industrial Security Program Operating Manual (DOW 5220.22-M) Chapters 1-3, Reporting Requirements. Contractors shall establish internal procedures as are necessary to ensure that cleared personnel are aware of their responsibilities for reporting pertinent information to the Facility Security Officer and other federal authorities as required. CORs will ensure reports are included in COR files.

The Contractor shall be responsible for safeguarding all government equipment, information, and property provided for the Contractor’s use. At the close of each work period, government facilities, equipment, and materials shall be secured.

Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as contractors to avoid creating an impression in the minds of members of the public that they are Government officials. Contractors must also ensure that all documents or reports produced are suitably marked as contractor products and that contractor participation is appropriately disclosed. Contractor personnel will be required to obtain, use, and display a CAC in the performance of this contract. Contractor email signatures shall be standard and consistent for current and future Contractor employees. As stated in 48 CFR 211.106, Purchase Descriptions for Service Contracts, contractor personnel shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and by displaying distinguishing badges or other visible identification for meetings with Government personnel. Contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

1.13.2 Physical Security: The Contractor shall be responsible for safeguarding all Government equipment, information and property provided for Contractor use. At the close of each work period, Government facilities, equipment, and materials shall be secured.

1.14 TRAVEL/TDY/DEPLOYMENT

1.14.1 Contractor personnel may be required to travel during the performance of this contract in support of DoW organizations and Combatant Commands. Anticipated travel locations include continental US (CONUS) and outside CONUS (OCONUS) and include but are not limited to travel between MV and other DIU locations, U.S. Government (USG)/DoW installations, and commercial locations. Historically, OCONUS locations included Poland, India, and Europe. The contractor shall obtain, at its own expense, all passports unless considerations for exceptions are coordinated with the COR and approved by the CO. The contractor shall obtain visas or other documents necessary to enter and/or exit any area(s) identified by the COR for contractor personnel. These items will be reimbursed by the Government as approved by the CO.

1.14.2 The Contractor shall be reimbursed for actual allowable, allocable, and reasonable travel costs incurred during performance of this effort in accordance with the FAR 31.205-46 "Travel Costs."

Requests for approval of costs in excess of maximum per diem rates in accordance with the procedures contained in FAR 31.205-46(a)(3) must be submitted to the COR for final approval prior to commencement of travel.

Every travel request requires a Trip Authorization, which shall be submitted to the COR at least two (2) weeks prior to the travel start date and must be approved by the COR prior to travel start date. The contractor shall use only the minimum number of travelers and rental cars needed to accomplish the task(s). A subsequent Trip Voucher shall be submitted with the monthly invoice.

No payment will be made without documented receipts. For this contract, per FAR Subpart Part 31.205- 46(a)(1), costs for transportation will be based on actual costs incurred provided the method used results in a reasonable charge (i.e., the cost a prudent person would pay). Costs for lodging, meals, and incidental expenses are based on per diem. Contractor’s travelers are required to exercise the same care in incurring expenses that a prudent person would exercise if traveling on personal business when making official travel arrangements, and therefore, should consider the least expensive class of travel that meets their needs. Actual travel will be coordinated with the COR and pre-approved by the COR. The COR shall approve travel (in writing or via DIU-preferred workflow management tool/process).

NOTE: The Contractor shall keep on file all backup support documentation for travel made on behalf of the Government under the terms of the contract.

All travel requests shall be submitted to the COR by the travel management services in accordance with the provisions of the Federal Travel Regulation (FTR), JTR, and the limitation of funds specified in this contract. The government will reimburse the Contractor for all other travel outside the 50-mile limitation that was authorized in advance by the COR, for reasonable travel related expenses. Each Trip Authorization shall include:

● Date of travel and place (city, town, or other similar designation) of the expenses, purpose of the trip, and name of person on trip and that person’s title or relationship to the Contractor (FAR Subpart 31.205-46 (a)(7)); and

● Attachment of requested flights, from Kayak.com or similar fare aggregator and travel metasearch engine.

Trip Voucher: The Contractor shall be reimbursed for actual allowable, allocable, and reasonable travel costs incurred during performance of this effort in accordance with the FAR Part 31.205- 46 Travel Costs. The trip vouchers shall be submitted with the monthly invoice using the Wide Area Workflow e-Business Suite. Each trip voucher shall include receipts for expenses over $75.00, including hotel, airline, and rental car receipts.

1.14.3 All local travel in support of this contract (i.e., any travel within a 50-mile radius of the NCR) is included in the price of this contract and is not reimbursable. All local travel costs shall be borne by the Contractor, nor will the Government reimburse Contractor personnel commuting costs (i.e., parking expenses, public transportation fares such as Metro, Virginia Rail Express, vanpool or bus, and/or highway tolls, etc.).

1.15 CONFLICT OF INTEREST/NON-DISCLOSURE AGREEMENT:

1.15.1 Organizational Conflict of Interest/Personal Conflict of Interest: Contractor and Subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interest (OCI) as defined in FAR Subpart 9.5 as well as personal conflicts of interest. Using the Contractor OCI/ COI Disclosure Form, the Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential conflict and shall promptly submit the conflict-of-interest disclosure form to the Contracting Officer to avoid or mitigate any such conflict.

1.15.2 The work under this TO may create a future OCI that could prohibit the contractor including any subcontractors, from competing for, or being awarded future DIU contracts/TOs or DIU sponsored or funded activities. While, in these situations, OCI determinations will be made by the CO for that future order, the PMO support contractor shall provide an OCI mitigation plan that addresses the contractor’s approach to active OCI management, avoidance, and neutralization throughout the course of performance of this TO. The intent of this plan is to ensure active management of OCI minimization techniques are utilized in order to reduce the contractor’s risk of preclusion from future work.

Additionally, at any time during the performance of the TO if an actual, potential, or apparent

OCI is identified whether by the CO, the contractor or otherwise, the contractor shall submit a mitigation plan within 30 days unless otherwise specified by the CO. It is the contractor’s responsibility under the terms and conditions to provide timely notification to the CO of those OCIs that are self-identified. The CO will notify the contractor regarding the specifics for submission. The CO will review the submission at which time a determination will be made whether an OCI has been satisfactorily mitigated or if further action is necessary and will notify the contractor accordingly.

In cases where an OCI cannot be, or has not been, mitigated to the Government’s satisfaction, the

CO may take the following actions (this list is not all inclusive inclusive):

● Request a waiver in accordance with FAR 9.503 Waiver, from the Head of the Contracting Activity.

● Make changes to the requirements of the TO.

● Require a subcontractor change (if the conflict lies with the subcontractor).

● Terminate the TO in whole or in part.

1.15.3 In addition, Contractors shall conduct internal reviews as necessary to identify financial interests and determine if any personal conflicts of interest exist or may arise. The Contractor shall ensure that the organization has analyzed each financial disclosure to determine whether actual or potential conflicts exist. Information should be gathered and analyzed for all governing body members (e.g., board of directors, trustees, etc.) and principals of the organization as defined by FAR 52.203-13 and for each manager and key personnel who would be or are involved with the performance of the contract.

1.15.4 If the contractor acts on behalf of, or provides advice with respect to any phase of an agency procurement, as defined in FAR 3.104-4, then the contractor shall execute and submit a Corporate Non-Disclosure Agreement (NDA) Form (Section J, Attachment B) and ensure that all its personnel (including subcontractors, teaming partners, and consultants) who will be personally and substantially involved in the performance of the TO:

● Are instructed in the FAR 3.104 requirements for disclosure, protection, and marking of contractor bid or proposal information, or source selection information.

● Are instructed in FAR Part 9 for third-party disclosures when acting in an advisory capacity.

All proposed replacement contractor personnel shall also be instructed in the requirements of FAR 3.104. Any information provided by contractors in the performance of this TO or obtained from the Government is only to be used in the performance of the TO. The contractor shall put in place appropriate procedures for the protection of such information and shall be liable to the Government for any misuse or unauthorized disclosure of such information by its personnel, as defined above.

Personnel working on this TO may be required to sign an NDA prior to beginning work under the TO depending on the specific function or role. The DIU COR will identify all functions/roles that require an NDA.

1.16 SURGE SUPPORT:

1.16.1 DIU supports emerging technologies to ensure that DoW can leverage the best of commercial technology and innovation. As a result, flexibility is required to effectively respond to the dynamic nature of its mission and anticipated organizational changes. Emerging requirements driven by Congressional mandates, Secretary of Defense priorities, and potential reorganization of assignments under the Executive Administration may necessitate a surge that may require a quick ramp up to increased support to accomplish tasks and projects.

1.16.2 The contractor shall provide surge support upon the COR request. All PWS Part 5 tasks are subject to surge support. Surge activities are limited to the tasks within the scope of the contract, but exceed the established FFP mission support levels as proposed.

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS: [List any terms used within the PWS that require further definition. At a minimum, insert the definitions provided below].

2.1.1. CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.2. CONTRACTING OFFICER. A person with authority to enter into, administer, and terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.3. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the Contracting Officer to assists in administering the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.4. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.5. DELIVERABLE. Anything that can be physically delivered but may include non-manufactured things such as meeting minutes or reports.

2.1.6. KEY PERSONNEL. Contractor personnel required to be used in the performance of the contract as indicated in the Key Personnel section listed in the PWS.

2.1.7. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.1.8. QUALITY ASSURANCE. The Government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.9. QUALITY ASSURANCE Surveillance Plan (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of Contractor performance.

2.1.10. QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.11. SUBCONTRACTOR. One that enters into a contract with a prime Contractor. The Government does not have privity of contract with the Subcontractor.

2.1.12. WORK WEEK. Monday through Friday, unless specified otherwise.

2.2. ACRONYMS: [List all acronyms used in the PWS and what they represent. At a minimum, insert the acronyms provided below, unless they do not appear in the document.]

ACOR Alternate Contracting Officer's Representative APO/FPO Army/Air Post Office / Fleet Post Office BCTF Boards, Commissions, and Task Forces CA Company Administrator CCDR Combatant Commander CFR Code of Federal Regulations CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative COTS Commercial-Off-the-Shelf DD 254 Department of Defense Contract Security Classification Specification (DD Form 254) DFAC Dining Facility DFARS Defense Federal Acquisition Regulation Supplement DMDC Defense Manpower Data Center DOW Department of War DPO Diplomatic Post Office EM Enterprise Management Directorate FAR Federal Acquisition Regulation FTE Full Time Employee GFM Government Furnished Meals HIPAA Health Insurance Portability and Accountability Act of 1996 CO Contracting Officer LCAT Labor Category MILAIR Military Airlift MWR Morale, Welfare, and Recreation NCR National Capital Region OCI Organizational Conflict of Interest OCONUS Outside Continental United States (includes Alaska and Hawaii) ODC Other Direct Costs PIPO Phase In/Phase Out POC Point of Contact PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Program SOFA Status of Forces Agreement SPOT Synchronized Predeployment Operational Tracker TDY Temporary Duty Travel TE Technical Exhibit WHS Washington Headquarters Services

3. USE OF GOVERNMENT FURNISHED COMPUTERS:

3.1 Computers furnished under this contract shall be used for official business only. Contractor personnel shall not use computers furnished under this contract for any use other than to perform the requirements of this contract. Contractor personnel shall not install any software on Government furnished computers unless consent is obtained from the CO or COR.

3.2 Information services available on the Government furnished computers shall only be used for official business only. Examples of information services include Internet, Intranet, World Wide Web, and electronic mail.

3.3 Access to Government information services is granted as a privilege, and use of such services constitutes consent to monitoring. Information services use will be monitored to ensure the protection of networks and information and to verify and enforce compliance with this contractual requirement.

3.4 In the event Contractor personnel use Government furnished computers and/or information services for other than official business, the Contractor shall remedy the situation. In addition, if requested by the CO, the Contractor shall be required to replace the individual who misused the Government furnished computers and/or information services within ten (10) business days.

The following are examples of misuse of information services:

1. Illegal, fraudulent, or malicious activities.

2. Partisan political activity, political or religious lobbying or advocacy, or activities on behalf of organizations having no affiliation with DIU or DoW.

3. Activities whose purposes are for personal or commercial financial gain. These activities may include chain letters, solicitation of business or services, sales of personal property.

4. Unauthorized fundraising or similar activities, whether for commercial, personal, or charitable purposes.

5. Accessing, storing, processing, displaying or distributing offensive or obscene material such as pornography and hate literature.

6. Annoying or harassing another person, e.g., by sending or displaying uninvited e-mail of a personal nature or by using lewd or offensive language in an e-mail message.

7. Using another person’s account or identity without his or her explicit permission, e.g., by forging e-mail.

8. Viewing, damaging, or deleting files or communications belonging to others without appropriate authorization or permission.

9. Permitting any unauthorized person to access a DoW-owned system.

4. PRESS/NEWS RELEASE

The contractor shall not make any press/news release pertaining to this TO without prior Government approval and only in coordination with the CO. No news release (including photographs and films, public announcements, denial or confirmation of same) on any part of the subject matter of this contract or any phase of any program hereunder shall be made without the prior written approval of the Contracting Officer and DIU Public Affairs Office (PAO). See also Section I, DFARS clause 252.204-7000 “Disclosure of Information”. Contractor also must comply with DFARS 252.204-7000, Disclosure of Information, concerning Contractor’s responsibilities for handling unclassified information and DFARS 252.204-7003, Control of government personnel work product.

5. SPECIFIC TASKS:

Task 1: TO Program Management Task 2: Enterprise Services Support

5.1 TASK 1 – PROGRAM MANAGEMENT

The contractor shall provide program management support under this TO. 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).

5.1.1 SUBTASK 1 – ACCOUNTING FOR SERVICE CONTRACT REPORTING

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the DIU. The contractor shall completely fill in all required data fields using SAM.gov. Reporting inputs will be for the labor executed during the period of performance during each Government Fiscal Year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the SAM.gov support desk.

5.1.2 SUBTASK 2 – COORDINATE A PROJECT KICK-OFF MEETING

The contractor shall schedule, coordinate, and host a Project Kick-Off Meeting at a location approved by the Government (Section 7, Deliverable 02). The meeting shall provide an introduction between the contractor personnel and Government personnel who will be involved with the TO. The meeting shall provide the opportunity to discuss technical, management, and security issues, and travel authorization and reporting procedures. At a minimum, the attendees shall include the contractor’s Key Personnel, the DIU Technical Point of Contact (TPOC), other relevant Government personnel, the CO, and the COR.

The contractor shall provide a Project Kick-Off Meeting Agenda for review and approval by the COR and the DIU TPOC (Section 7, Deliverable 01). The agenda shall include, at a minimum, the following topics/deliverables:

a. Points of Contact (POCs) for all parties.

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

c. Project Staffing Plan and status.

d. Transition-In Plan and discussion (Section 7, Deliverable 08).

e. Security discussion and requirements (e.g., building access, badges, Common Access Cards (CACs)).

f. Financial reporting and invoicing requirements.

g. Quality Management Plan (QMP) (Section 7, Deliverable 07).

The Government will provide the contractor with the number of Government participants for the Project Kick- Off Meeting, and the contractor shall provide copies of the presentation for all present.

The contractor shall draft and provide a Project Kick-Off Meeting Minutes Report documenting the Project Kick-Off Meeting discussion and capturing any action items (Section 7, Deliverable 03).

5.1.3 SUBTASK 3 – PREPARE A MONTHLY STATUS REPORT (MSR)

The contractor shall develop and provide an MSR (Section 7, Deliverable 04). The MSR shall include the following:

a. Progress to date on all activities during the reporting period, by task, including ongoing activities, new activities, and completed activities. Each section shall start with a brief description of the task.

b. Problems and corrective actions taken, as well as issues or concerns and proposed resolutions to address them.

c. Personnel roster with name, contract/subcontract, duty title, labor category, duty location, portfolio, Government lead, clearance, email, phone number, burdened rate. Departed personnel will remain on the roster with “vice” until replaced.

d. Government actions required.

e. Schedule that shows major tasks, milestones, and deliverables with planned and actual start and completion dates for each.

f. Summary of trips taken, conferences attended, and other relevant trip information. Attach Trip Reports to the MSR for the reporting period.

g. 60 calendar days prior to the end of each Option Period, identify any recurring, definitive requirements that may be eligible to transition to an alternate contract type.

h. Accumulated invoiced cost for each CLIN up to the previous month.

i. Projected cost of each CLIN for the current month.

5.1.4 SUBTASK 4 – CONVENE TECHNICAL STATUS MEETINGS

The contractor Program Manager (PM) shall convene a monthly Technical Status Meeting with the DIU TPOC, COR, and other Government stakeholders (Section 7, Deliverable 05). The purpose of this meeting is to ensure all stakeholders are informed of the monthly activities and MSR, provide opportunities to identify other activities and establish priorities, and coordinate resolution of identified problems or opportunities. The contractor PM shall provide minutes of these meetings, including attendance, issues discussed, decisions made, and action items assigned, to the COR (Section 7, Deliverable 06).

5.1.5 SUBTASK 5 – PROVIDE QUALITY MANAGEMENT

The contractor shall identify and implement its approach for providing and ensuring quality throughout its solution to meet the requirements of the TO. The contractor shall provide a QMP and maintain and update it as changes in the program processes are identified (Section 7, Deliverable 07). The contractor’s QMP shall describe the application of the appropriate methodology (e.g., quality control and/or quality assurance) for accomplishing TO performance expectations and objectives. The QMP shall describe how the appropriate methodology integrates with the Government’s requirements.

5.1.6 SUBTASK 6 – TRANSITION-IN

The contractor shall provide a Transition-In Plan (Section 7, Deliverable 08). The contractor shall ensure that there will be minimum service disruption to vital Government business and no service degradation during and after transition. The contractor shall implement its Transition-In Plan No Later Than (NLT) 5 calendar days after award, and all transition activities shall be completed 60 calendar days after Task Order Award (TOA).

5.1.7 SUBTASK 7 – TRANSITION-OUT

The contractor shall provide transition-out support when required by the Government. The Transition-Out Plan shall facilitate the accomplishment of a seamless transition from the incumbent to incoming contractor/Government personnel at the expiration of the TO. The contractor shall provide a Transition-Out Plan (Section 7, Deliverable 09). The contractor shall review and update the Transition-Out Plan in accordance with the specifications in Sections E and F.

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

a. Project management processes.

b. POCs.

c. Location of technical and project management documentation.

d. Status of ongoing technical initiatives.

e. Appropriate contractor-to-contractor coordination to ensure a seamless transition.

f. Transition of Key Personnel roles and responsibilities.

g. Schedules and milestones.

h. Actions required of the Government.

i. Software acquired POP dates

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.

The contractor shall implement its Transition-Out Plan NLT six months prior to expiration of the TO.

5.2 TASK 2 – ENTERPRISE SERVICES SUPPORT

5.2.1 SUBTASK 1 – INFORMATION TECHNOLOGY

The contractor shall provide IT Support for the Defense Innovation Unit (DIU), exercising technical responsibility for systems, to include hardware, software, and cloud-based Software-as-a-Service (SaaS) applications used by DIU personnel. DIU operates at the commercial, Controlled Unclassified Information (CUI), Secret, and TS level. Predominantly, work is done on the DIU.mil commercial, Software as a Service, cloud-based environment with 500 user endpoints. Connected by VPN and 250 mobile phones. Support for the CUI, Secret, and TS level is as a consumer of Defense Information Systems Agency (DISA) and Defense Intelligence Agency (DIA) services, so our principal role is to request, coordinate, and trouble shoot those services. Our user base is a blend of on-site personnel in the NCR and Mountain View and remote personnel.

Very Important Person (VI)P Support to senior leaders requires rapid response and schedule flexibility. While this does not require a standing 24/7 on site operation, this does require on call support. Core business hours requiring on-site support are from 8am eastern time to 4pm Pacific time 5 days a week. DIU expects a cascaded/staggered schedule. On site at Mountain View, network is provided by commercial internet service provider and wifi connection to end points. In the NCR, network is provided via a wired connection by DISA and DIA. DIU has the following makeup:

Network/capability Users DIU.mil - Cloud office productivity, cloud file storage, Identity provider, access control, IT Service Management, Customer Relationship Management, Intranet, Public Affairs website

DIU smart phones 300 DISA Non-Classified Internet Protocol Router (NIPR) 125 DISA Secret Internet Protocol Router (SIPR) 75 WINDAR-S (secure laptops) 15 DISA Joint Worldwide Intelligence Communications System (JWICS) 40

DIA SIPR 50

DIA Common Operating Environment (COE) JWICS 75

5.2.1.1 IT Architecture and Design

The contractor shall:

1. Document As-Is and To-Be architecture: networks, systems, applications.

2. Forecast capability needs.

3. Evaluate technology options and make recommendations to the Chief Information Officer (CIO).

4. Assist in the design of secure system and network architectures and provide relevant security policy recommendations.

5. Create and provide technical documentation for physical and logical server topologies for all information systems and associated applications.

5.2.1.2 Engineering

1. Serve as the technical expert, security strategist, and client system, server, and application manager for on-premises network and cloud-based services.

2. Select, plan, deploy, and decommission IT services.

3. Provide software and hardware configuration and recommendations.

4. Analyze network equipment and software reliability and utilization reports to identify and remediate issues and update the environment for technological changes to keep up with best practices.

5. Provide ancillary, non-legal policy analysis and recommendations in direct support of the enactment of DIU technology policy and operations.

6. Provide tier 3 trouble shooting across architectural components between commercial and Government on-prem and cloud environments at multiple classification levels.

7. Support development of artifacts and engage with DoW CIO in support of exceptions to policy.

5.2.1.3 IT Operations, Administration, and Change and Configuration Management

1. Administer SaaS applications and computers, mobile devices, ICAM (identity credential and access management), network equipment, etc.

2. Perform system administrative tasks, manage user IDs and access rights, and oversee software upgrades, security updates, and patches.

3. Advise and assist service provider in analyzing, testing, troubleshooting, and evaluating existing network systems, such as local area network (LAN), wide area network (WAN), and Internet systems.

4. Define, implement, provide, and improve comprehensive IT configuration management services to include identification, documentation, and control of configuration items (CIs), in accordance with DIU Change Management processes.

5. Perform administrator role access to SaaS platforms in support of technical search in support of Freedom of Information Act (FOIA) requests, litigation holds, investigations, etc.

6. Establish and manage a process to gather, consolidate, and represent DIU user requirements for new services or changes to existing services.

7. Apply applicable DISA Security Technical Implementation Guides (STIGs) and make recommendations to justify the technical need for applying or omitting each.

5.2.1.4 DIU Process Management

1. The contractor shall build and maintain a library of DIU cross functional organizational processes for example onboarding/offboarding (Human Resources, Security, IT equities).

2. The contractor shall champion process and build support across functional organizations in support of

DIU leadership.

5.2.1.5 IT Asset Management

1. Provide IT asset management services to ensure the proper tracking, management, and optimization of IT assets (hardware, network, software) throughout their lifecycle.

2. Ensure that all applicable assets are actively tracked and accounted for within the Defense Property Accountability System (DPAS).

3. Be capable of issuing and managing DD1149 and DD1150 Property forms to maintain proper accountability for DPAS.

4. Perform property management of the internal DIU accounting system (e.g., ServiceNow).

5. Manage an estimated property inventory consisting of 1,000 laptops, 500 mobile phones, 1,000 monitors, and approximately <200 other high-value items. Not all inventory is currently issued to users, so equipment numbers do not coincide with users.

5.2.1.6 Secure Communications and Video Teleconferencing (VTC)

1. The contractor shall provide support to Secure Communications systems, including managing classified services, circuits, and COMSEC to establish and maintain secure SIPRNet and JWICS environments. DIU receives COMSEC account support from Travis Air Force Base (AFB). The contractor shall support the COMSEC inventory process and coordinate account management with Travis.

2. The contractor shall provide support in establishing, maintaining, and managing Video Tele- Conference (VTC) sessions and systems.