A10 SSN - IP S Series - FOR SAM - 13AUG2025.pdf

Intellectual Property and S-Series Specifications Analysis for Product Support

SOURCES SOUGHT NOTICE

1:3

This is not a solicitation for proposals, abstracts, or quotations. This Sources Sought Notice is solely for market research purposes and should not be interpreted as a Request for Proposal (RFP) or a commitment by the issuing party to procure any goods or services. If an RFP is released, it will be issued through the appropriate Government Contracting Office and posted on the designated Government Point of Entry (GPE). The issuing party does not intend to compensate for the information requested herein. All submitted information is for Government planning purposes only. Proprietary information, if provided, should be clearly marked as “Proprietary – For Government Use Only.”

Responses are welcomed from all sources, including Small Businesses, 8(a) Small Businesses, HUBZone, Service-Disabled Veteran-Owned Small Businesses (SDVOSB), Women-Owned Small Businesses, and Economically Disadvantaged Women-Owned Small Businesses (EDWOSB). While non-responsiveness to this notice does not preclude participation in any future Request for Proposal (RFP), interested and capable firms are strongly encouraged to respond to contribute to the market research and acquisition planning process.

I. INTRODUCTION

The Department of Defense (DoD), Washington Headquarters Services (WHS) Acquisition Directorate (AD), is issuing this Sources Sought Notice to gather information and assist in identifying the most suitable acquisition method for support services related to the subject Sources Sought Notice. The period of performance shall be for a 12-month base period and four (4) 12-month option period. Please reference the draft Performance Work Statement (PWS) for specific details as it pertains to the requirements of this request.

II. INSTRUCTIONS

SUBMISSION REQUIREMENTS: Interested firms should submit responses to include a capabilities statement covering experience and staffing capabilities. Businesses having the capabilities necessary to perform the stated requirements may submit capability statements via email to the following email address:

• Jasmine Sadat at jasmine.s.sadat.civ@mail.mil

Responses must be submitted not later than August 27, 2025, at 12:00 p.m. noon Eastern Time.

Capability statements will not be returned. No phone calls related to this Sources Sought Notice will be accepted. All correspondence shall be via email. Respondents must submit documents in Word or PDF format. Neither zipped files will be accepted, nor telephone requests be honored.

Responses are limited to ten (10) pages, using a minimum font size of 12, left-justified, with one-inch margins.

2:3

CAPABILITY STATEMENT REQUIREMENTS: Vendors must submit clearly numbered responses corresponding to the following sections [below]:

A. ADMINISTRATIVE

1. Company Information:

a) Legal name and address.

b) Commercial and Government Entity (CAGE) Code.

c) North American Industry Classification System (NAICS) codes associated with the company.

d) Small business status under the identified NAICS code (e.g., 8(a), SDVOSB, HUBZone, SDB, VOSB, WOSB).

B. INDUSTRY FEEDBACK

2. Indicate whether these services are commercially available (Yes/No) and provide a rationale.

3. Recommended contract type (e.g., FFP, Cost, T&M, LOE) based on the draft PWS.

4. Confirm whether the proposed NAICS code 541690 – Other Scientific and Technical

Consulting Services is appropriate for this effort. If not, recommend an alternative NAICS code with justification.

5. Provide any feedback or questions regarding the draft PWS requirements.

6. Identify anything in the draft PWS that could be considered a deviation from industry standard.

C. INDUSTRY CAPABILITY

7. A synopsis of similar work performed, demonstrating your ability to provide qualified staff with subject matter expertise. Provide specific examples of prior efforts similar to the requirements outlined in the draft PWS. Not to exceed 3 pages.

8. Identify whether all items needed to fulfill this requirement are available on a GSA contract and, if applicable, provide the GSA contract number.

9. Recommend Government-Wide Acquisition Contracts (GWACs) under which these services can be procured. Provide contract numbers for reference.

10. Please indicate how much time your firm would need to prepare a competitive response to a

Request for Quotation (RFQ).

3:3

11. Would your firm need a transition period? If yes, how long? For example: 15 days / 30 days.

12. Provide a point of contact (name, phone, and email) for individuals who can verify the capabilities identified in your response.

D. SUBCONTRACTING OPPORTUNITIES

The following information will assist WHS/AD in establishing a basis for developing set-asides and/or subcontracting opportunities, as appropriate. Failure to provide complete, clearly numbered responses for each section may result in the Government deeming the vendor “not capable.”

Please address all sections under the ‘TASKS’ section of draft PWS section.

Complete the following table when answering questions #13 and #14.

Task Number

Tasking categories

Anticipated % of Subcontracting

If known, list potential subcontractor by name, teaming partner, joint venture arrangement, etc. with applicable business size

13. Identify which specific sections that your firm will handle as the prime contractor and those where subcontracting (e.g., small business collaboration) will occur. Explain the rationale for selecting certain areas to be performed as the prime contractor versus those handled through teaming arrangements or joint ventures.

14. If subcontractors are anticipated, specify:

a. The task areas they will perform.

b. The estimated percentage of subcontracting required.

15. Please highlight any information that is unduly restrictive to small business as listed in the draft PWS.

16. Provide details (including approximate total contract value) of at least two (2) contracts where your company has acted as the prime contractor (either solely or as part of a joint venture) within the past three years for similar requirements.

Intellectual Property and S-Series Specifications Analysis for Product Support 1:15 | Page

PERFORMANCE WORK STATEMENT (PWS)

26 February 2025

1.0 BACKGROUND

The Assistant Secretary of Defense for Sustainment plays a key collaborative role with the Military Services and Program Managers in assisting with successfully fielding available, reliable, and combat ready weapons systems. This role includes providing insight and guidance to effectively implement Secretary of Defense (OSD) priorities to rebuild our military and reestablish deterrence through implementation of various Department of Defense Directives/Instructions along with National Defense Authorization Acts, Government Accountability Office (GAO) recommendations and other OSD direction. The Deputy Assistant Secretary of Defense for Product Support (DASD(PS)) is responsible for Weapon System Life Cycle Support that optimizes affordability and materiel readiness that supports Joint Warfighter requirements. Specifically, DASD(PS), is the focal point for developing acquisition and sustainment Life Cycle Product Support Strategies through Policy, Guidance, Direction and providing implementation assistance to OSD, Military Services, and Components Product Support Managers (PSMs) through the development and assessment of Product Support Strategies and program affordability covering all acquisition and sustainment phases.

2.0 SCOPE

Intellectual Property (IP). Obtaining adequate intellectual property license rights and associated technical data from our industry partners is critical to ensure product support for our major weapons systems are efficient, affordable, and adaptable to meet warfighter needs. Additionally, Congress is also concerned about these matters and recently wrote legislation encouraging customized intellectual property strategies.

When we do not secure appropriate rights in technical data and computer software, we become dependent on incumbent contractors for the operation, maintenance, training, and sustainment of our major weapon systems. Through these "vendor lock" actions, incumbent contractors can drive non-competitive prices for years or even decades after our major weapon systems are deployed. We must prevent this by obtaining all appropriate intellectual property rights to which the government is entitled to, and that Congress has deemed essential through legislative actions. By obtaining intellectual property licensing to the maximum extent, we can achieve significant cost savings by competing sustainment of our major weapon systems programs throughout their life cycles.

Department of Defense Instruction (DoDI) 5010.44, Intellectual Property (IP) Acquisition and Licensing requires that, "each DoD program will have a robust IP strategy to identify and manage the full spectrum of IP and related matters (e.g., technical data and computer software deliverables, patented technologies, and license rights) from the inception of a program and updated throughout entire product life cycle— initially as part of the acquisition strategy, and during the operations and support phase as part of the life-cycle sustainment plan." PSMs for a weapon system must ensure that programs address data rights and data delivery, as well as the use of any proprietary data. Providing IP expertise to DASD(PS) will greatly enhance policy, associated guidebooks, and tools to support PSMs product support strategies that optimize weapon system affordability and materiel readiness.

S-Series Specifications. The cancellation of the Department of Defense (DoD) standards after the release of National Technology Transfer Advancement Act (NTTAA) of 1993 resulted in the development of the S-Series Product Specifications for product support by European industries. The S-Series intent will allow industry stakeholders to leverage a common architecture and core data model, which will enable common

Intellectual Property and S-Series Specifications Analysis for Product Support 2:15 | Page product support processes across a system’s life cycle. Previously, the European military community was reliant on the cancelled US Military standards for their contracts.

The Aerospace, Security and Defense Industries Association of Europe (ASD) developed the S-Series specifications to become self-deterministic vice reliant on the DoD. Later, US based Aerospace Industries Association (AIA) joined with ASD to provide significant input into the development process of these specifications.

Through coordinated maturation activities, between governments and industry, these specifications are becoming more integrated and harmonized across the S-Series suite, including maturity of the Common Data Model for all specifications. If successfully matured and implemented, the S-Series approach could enable interoperability, reduce complexity, enhance collaboration, and reduce reliance on proprietary tools and processes, while supporting use of digital threads. The S-Series Specifications suite of standards for product support are comprised of the following:

SX000i - Integrated Product Support (overarching guidance and data model) S1000D - Technical Manuals S2000M - Material Management (Supply Support & Provisioning) S3000L - Logistics Support Analysis S4000P - Preventative Maintenance S5000F - In-Service Feedback S6000T - Training Analysis and Design

Given the interest in the S-Series by both Congress and industry, DASD(PS) must be postured to effectively provide analysis and solutions for its possible implementation within DoD, industry, allies, and partners.

DASD(PS) will also be expected to provide leadership and expertise as the S-Series are incorporated in DOD policies, instructions, manuals, and guidebooks. This is especially relevant with the ongoing work with establishing the Regional Sustainment Frame (RSF) with our allies and partners for weapon system sustainment.

3.0 TASKS

3.1 Intellectual Property (IP) and Technical Data Support

The Contractor shall provide subject matter expertise and technical analysis on intellectual property/technical data matters related to product support for weapon systems to DASD(PS) to support the following activities and tasks:

Support and participate in intellectual property and product support Working Groups and Tiger Teams.

Identify alternatives to improve DoD access to sustainment technical data.

Work with Military Services and DoD stakeholders to identify potential policy changes and/or legislative proposals to define and secure sufficient technical data for product support.

Collaborate with the OSD IP Cadre on addressing technical data and intellectual property inquiries, challenges, and development of IP solutions within the DoD.

Identify best practices related to intellectual property and product support across DoD.

Identify and support the development IP equities in International Agreements in support of the

Regional Sustainment Framework (RSF) efforts.

Support the Joint Sustainment and Supply Chain Forum IP Community of Practice case study efforts and development of RSF implementation guidance and guidebooks.

Assist RSF Team on implementation planning with IP identification to meet all COCOM requirements.

Provide IP updates to DoD Instruction (DoDI) 5000.91 and Product Support Guidebooks.

Intellectual Property and S-Series Specifications Analysis for Product Support 3:15 | Page

Provide congressional support to include review and analysis of all relevant draft and enacted Congressional bills, statutes, legislation, etc., insight and analysis on impacts for policy, Statement of Administration Position (SAP), and any actions in support of Congressional engagements. Assist with drafting legislative proposals to update US Code Title 10 statutes.

Prepare briefings, reports, information papers, memorandums, talking points, and other forms of communication to inform leadership and the broader life-cycle logistics community on IP related updates.

Review, assess, and draft comments as required on DoD Directions, Instructions, Manuals, Handbooks and Guidebooks staffed through the DASD(PS) office for impacts to Product Support policy.

Review and assess applicable GAO and IG recommendations related to policy and provide feedback on policy impacts to DoDI 5000.91 and associated guidebooks.

Provide IP support and expertise to the Defense Acquisition University on Product Support course development and updates. This includes engineering courses that address Product Support.

Estimated Full Time Equivalent (FTE) workload for Task 3.1: 1.0 Onsite

3.2 S-Series Specification Assessment and Application to Product Support

The contractor shall provide subject matter expertise and technical analysis for the continued assessment of the S-Series specifications related to product support to DASD(PS) on the following activities and tasks:

Support the execution of a follow-on independent assessment for the sustainment enterprise, to include analyzing current military standards and specifications and providing courses of actions.

Ensure courses of actions support standards, best practices, and DoD strategic objectives.

Identify opportunities and risks associated with the adoption and implementation of the S-Series suite of specifications.

Work with Military Services and DoD stakeholders to identify implementation strategies, potential policy changes and/or legislative proposals.

Collaborate with International Partners and Industry on addressing S-Series challenges, and solutions within the DoD.

Prepare briefings, reports, information papers, memorandums, talking points, and other forms of communication to inform leadership and the broader life-cycle logistics community on S-Series related updates.

Coordinate responses to congressional inquiries, reports, and senior leader correspondences.

Support maturation of the S-Series standards to include:

o Engagement with both AIA and ASD governance activities in Integrated Product Support (IPS) Council meetings, including working with each of the Committees responsible for the development of each of the S-Series Specifications thereby giving a voice from a US DoD needs perspective.

o Working closely with the Data Management Exchange Working Group (DMEWG) to better improve the Common Data Architecture, and Core Data Model to ensure DoD needs are reflected in those models.

o Assuring that the language in each of the specifications is contractible by DoD by separating Normative (shall) from Informative (guidance) language in each specification.

o Assisting with the development of Business Rules for each specification which will enable the implementation of each specification.

o Outreach, engagement, and coordination with international organizations (NATO, ISO, Intellectual Property and S-Series Specifications Analysis for Product Support 4:15 | Page

DIG) to ensure international agreements are aligned with US DoD needs.

Estimated Full Time Equivalent (FTE) workload for Task 3.2: 2.0 Onsite

3.3 Optional Surge and Special Projects

During contract execution, the Government may require surge support or special project support due to critical emergent requirements or mandates levied by the President, Congress, Secretary of Defense, and the Under Secretary of Defense for Acquisition and Sustainment, Surge is defined as an increase to the workload beyond what was originally quoted by the contractor. In the event such support is needed, the Government will execute a contract modification to add the support to the contract.

3.4 Key Personnel

The Contractor shall provide qualified personnel for the key positions under this contract. The Contractor shall ensure that the human capital to be provided possesses the skills, knowledge, training, and certification(s) required to satisfactorily perform all services required by the contract.

During the first 90 calendar days of performance, the contractor shall make no substitutions of key personnel without the approval of the Contracting Officer (KO), unless illness, death, or termination of employment necessitates the substitution. The contractor shall notify the KO as soon as possible after the occurrence of any of these events and provide the information required below.

After the initial 90 calendar day period, the contractor may propose a substitution. The contractor shall notify the KO in writing of any proposed substitution at least thirty (30) days in advance of the proposed substitution. The contractor shall provide a detailed explanation of the circumstances necessitating the proposed substitutions, complete resumes for the proposed substitutes, and any additional information requested by the KO.

The contractor shall, prior to making any substitution permanent, demonstrate to the satisfaction of the KO, that the qualifications of the proposed substitute personnel is equal to or better than the qualifications of the personnel originally identified for the position. The personnel must also meet the PWS requirements for the position. The KO will notify the contractor within 15 calendar days after receipt of all required information of the decision on proposed substitutions.

Subject Matter Expert - Level IV (One FTE, Supporting Task 3.1 – Intellectual Property (IP) Support)

Provides technical/management leadership and expertise on major tasks associated with this PWS. Has domain and expert technical knowledge with policies, procedures, and applicable laws for the acquisition of intellectual property, technical data, and computer data necessary for DoD weapon system sustainment.

Technical data includes any recorded information of a scientific or technical nature (e.g., product design or maintenance data, computer databases, and computer software documentation). Computer software includes executable code, source code, code listings, design details, processes, flow charts, and related material that would enable the software to be reproduced, recreated or recompiled, but excludes computer databases or computer software documentation. The contractor will also have experience with briefing and interfacing with senior leadership. Interpersonal skills and experience for achieving consensus with stakeholder views and interest is highly desired.

Intellectual Property and S-Series Specifications Analysis for Product Support 5:15 | Page

More than ten years of relevant experience. Master’s degree required. Must be able to obtain and maintain a DoD SECRET Clearance and Common Access Card. A PhD degree can be substituted for two years of experience.

Subject Matter Expert - Level IV (Two FTE, Supporting Task 3.2 – S-Series Support)

Provides technical/management leadership and expertise on major tasks associated with this PWS. Has domain and expert technical knowledge and experience with the S-Series Specification suite and its application to weapon systems. Experience with legacy DoD military standards and Mil-standards particularly with Integrated Logistic Support. The experience may include Foreign Military Sales, Direct Commercial Sales, or Cooperative programs with emphasis on the logistics aspects of those activities. The contractor will also have experience with briefing and interfacing with senior leadership. Interpersonal skills and experience for achieving consensus with stakeholder views and interest is highly desired.

More than ten years of relevant experience. Bachelor’s degree required. Engineering degree preferred, however; non-engineer degree may be substituted if the vendor demonstrates sustainment planning and execution experience with the S-Series Specifications. Must be able to obtain and maintain a DoD SECRET Clearance and Common Access Card. A PhD degree can be substituted for two years of experience.

4.0 REQUIREMENTS

4.1 Monthly Status Report. Monthly status reports shall be submitted to the Government Technical Representative (GTR), no later than 10 days after the end of the month. The contractor shall provide a monthly status report identifying tasks worked, accomplished, and identify any issues/problems experienced, labor and labor hours used. An integrated master plan should be included to show task assignments. The report format shall be agreed upon at the contract kick-off or period of performance meeting once awarded. All travel shall be documented in the report, to include number of personnel, location, and dates of travel. Additional data to be included in the report are:

Progress for the period: detailed progress report of findings, activities, accomplishments during the reporting period, and summary of work accomplished during the reporting period and percent complete.

Any problems encountered: identification of any problems, issues or delays and recommendations as to their resolution, and any corrective action that was taken to correct identified problems.

All activities planned for the next reporting period: planned activities, as well as the status of any/all deliverables, including planned delivery date(s) and actual and/or anticipated delivery date(s).

Strategy revisions: recommended changes to include any lessons learned.

Additionally, the government may have quarterly reviews, as needed, and shall be conducted between the contractor representatives, technical representative, GTR and CO. The meeting shall be held at either the contractor facility or Government program office location. At the meeting, the program status shall be briefed by the contractor and any potential problems shall be identified that may adversely impact the program cost and schedules.

4.2 Period of Performance. The period of performance shall be for one (1) Base Period of 12 months and four (4) 12-month option periods. Yearly evaluations will be conducted to confirm that the use of the vehicle is still in the best interest of the Government.

4.2.1 Place of Performance. Work will be performed at Pentagon, the contractor’s site, or other designated sites within the National Capital Region (NCR). The term NCR means the geographic area located within

Intellectual Property and S-Series Specifications Analysis for Product Support 6:15 | Page the boundaries of (A) the District of Columbia, (B) Montgomery and Prince George’s Counties in the State of Maryland, (C) Arlington, Fairfax, Loudoun, and Prince William Counties and the City of Alexandria in the Commonwealth of Virginia, and (D) all cities and other units of government within the geographic areas of such District, Counties, and City.

Telework may be permitted as required and upon the Government representative approval, and in accordance with DoD telework policy. Telework is at the sole discretion of the Government.

4.2.2 Hours of Operations. The contractor is responsible for conducting project management support between the core hours of 8:00 am to 5:00 pm, Monday through Friday, except legal Federal Holidays or official Government facility closures, which are defined as any other day/time designated by Federal statute, Executive Order, or Presidential Proclamation and any adverse weather conditions or national emergencies may also require Government facilities to close. Recognized Federal holidays are as follows:

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

Federal Holidays are as specified at OPM’s website: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/

The contractor must always maintain an adequate work force for the uninterrupted performance of all tasks defined within this PWS, except during legal holidays and Government facility closures. During periods of inclement weather, the contractor shall be provided the DoD policy. The contractor may be required or authorized to work when their assigned facility is on holiday or closed.

5.0 DELIVERABLES & PERFORMANCE REQUIREMENTS SUMMARY

All deliverables must meet professional standards and satisfy the requirements set forth in contractual documentation. The contractor shall be responsible for delivering all items specified. All deliverables developed under specific orders become the property of the US Government. The dates by which specific deliverables must be submitted shall be as mutually agreed upon between the Government and the contractor. The Contractor shall provide the deliverables identified in this section. All deliverables shall be submitted to the Government Technical Representative (GTR) unless otherwise agreed upon. In addition, monthly status reports shall also be provided to the Contracting Officer’s Representative (COR).

Unless otherwise specified, the Government shall have a maximum of ten (10) working days from the day the draft deliverable is received to review the document, provide comments back to the contractor, approve or disapprove the deliverable(s). The contractor shall also have a maximum of ten (10) working days from the day comments are received to incorporate all changes and submit the final deliverable to the Government.

The format for individual deliverables shall be determined through consultation between the GTR /COR and the contractor. Products used by the DASD(PS) Office in the execution of responsibilities as outlined in the above task statements (e.g., handbooks or reports to Congress) shall be in a specified Government

Intellectual Property and S-Series Specifications Analysis for Product Support 7:15 | Page format. All documents shall be provided in the appropriate Microsoft Office format (e.g., Word or PowerPoint); if appropriate, the Government may ask that they be provided in compressed or PDF format.

In fulfillment of this effort, the contractor shall provide specific deliverables as identified by each individual Task Order. All deliverables shall be submitted to the COR, the GTR and selected representatives, unless otherwise agreed upon. In addition to the reports listed below, additional reports/products may be requested as deemed necessary.

Government Remedies. Per Federal Acquisition Regulation (FAR) 52.246-4, Inspection of the Services- Fixed Price, the Government reserves the right to inspect all deliverables and request that the contractor take action to correct any defects found in the deliverables.

The table below identifies the deliverables resulting from PWS task sections 3.1 and 3.2)

PWS

TASK

DELIVERABLE DUE DATES

3.1 Update DoDI 5000.91 and Product Support

Guidebooks (IP sections)

As required to meet established deadlines. Usually after the yearly NDAA is signed into law.

(Approximately 1/year)

3.1 Update Guidebooks (IP sections) (major revisions)

As required to meet established deadlines. Usually after the yearly NDAA is signed into law.

(Approximately 1/year)

3.1 Briefings, reports, analysis, information papers, talking points, memorandums, etc. related to IP policy, strategic messaging, and congressional engagement

As required to meet established deadlines.

(Approximately 6 talking point papers, 6 memorandums, 6 briefings, 12 information papers.)

3.1 Congressional report inputs As required to meet established deadlines.

Usually, 3 months after the NDAA is signed into law. (Approximately 1/year)

3.1 Review of other DoD Directions, Instructions, Manuals, Handbooks, and Guidebooks that have IP equities related to Product Support

As required (Approximately 6/year)

3.1 Participate and represent DASD PS in IP related

workshops, working groups, Tiger teams, and Military Service/Component engagements, and DASD PS PSM Workshop

As required (Approximately 18/year)

3.2 Briefings, reports, analysis, information papers, talking points, memorandums, etc. related to S- Series policy, strategic messaging

As required to meet established deadlines.

(Approximately 6 talking point papers, 6 memorandums, 6 briefings, 12 information papers.)

3.2 Follow-on Congressional report inputs and

responses to inquiries

As required to meet established deadlines.

Usually, 3 months after the NDAA is signed into law.

3.2 Participate and represent DASD PS in S-Series

related meetings, workshops, working groups, Military Service/Component engagements, and DASD PS PSM Workshop

As required. (Approximately 18/year)

3.2 Maturation of S-Series engagements/meetings

with:

AIA and ASD

DMEWG

International Partners and Forums

As required. (Approximately 30/year)

4.0 Monthly Status Report Monthly

Intellectual Property and S-Series Specifications Analysis for Product Support 8:15 | Page

Deliverables marked “As Required” will be determined based on project assignments and due dates. At that time, the project manager, GTR/COR will work with the Contractor to determine and identify the product deliverables prior to the start of the assignment. Additionally, most due dates shall be 10 days after the completion of the task unless specified otherwise. The contractor shall comply with the provisions of FAR 52.204-14 Service Contract Reporting Requirements.

6.0 PERFORMANCE STANDARDS AND QUALITY MEASUREMENT

6.1 Inspection and Acceptance Criteria. Final inspection and acceptance of all work performed, reports and other deliverables shall be performed at the place of delivery by the GTR.

6.2 General Acceptance Criteria. General quality measures, as set forth below, shall be applied to each work product received from the contractor under this Performance Work Statement.

Accuracy - Work Products shall be accurate in presentation, technical content, and adherence to accepted elements of style.

Clarity - Work Products shall be clear and concise. Any/all diagrams shall be easy to understand and be relevant to the supporting narrative.

Consistency to Requirements - All work products must satisfy the requirements of this Performance Work Statement.

File Editing - All text and diagrammatic files shall be editable by the Government.

Format - Work Products shall be submitted in hard copy (where applicable) and in media mutually agreed upon prior to submission. Hard copy formats shall follow any specified Directives or Manuals.

Timeliness - Work Products shall be submitted on or before the due date specified in this Performance Work Statement or submitted in accordance with a later scheduled date determined by the Government.

6.3 Contractor Performance Assessment Report (CPARS). Interim, and final evaluations of contractor performance will be prepared by the government representative in accordance with FAR Subpart 42.1500.

Addendum evaluations will be performed when appropriate. Interim evaluations will be completed at the end of each period of performance under this contract. A final performance evaluation will be prepared by the GTR/or COR, at the time of completion of each task order. Any disagreements will be handled according to the CPAR guidance and resolution will be handled through the government contracting office of responsibility.

6.4 Contractor Quality Control Plan (QCP). The Contractor shall institute a complete QC Program to ensure that the requirements of this contract are fulfilled as specified. At a minimum, the Contractor shall include the following elements in the program:

A comprehensive inspection system of all scheduled and unscheduled services required in this document.

Name and contact information of designated QC Inspector and backup performing inspections.

A proactive methodology to identify and correct problems before the Government identifies these problems. Contractor shall notify the Government of any problems.

An organized, current file of all Contractor conducted inspections, corrective actions taken, and follow-up inspections.

Government receipt of all QC reports same day generated.

How projects will be managed to minimize layers of management and oversight, while still providing for accountability How orders will be managed to provide for a clear communication between the contractor, Government program office, and Ordering Contracting Office

Intellectual Property and S-Series Specifications Analysis for Product Support 9:15 | Page

The contractor shall submit a QCP within 10 business days of contract award. This plan shall describe the Contractor’s methodology for compliance with the Deliverables and Performance Requirements Summary outlined above. The GTR will notify the contractor of concurrence or required modifications to the QCP within 10 business days of receipt. The contractor shall make appropriate modifications within 5 business days of the GTR’s notification and provide a revised QCP within 5 business days.

6.5 Organizational Conflicts of Interest (OCI). The contractor shall not employ any person who is an employee of the United States Government if the employment of that person would create a conflict of interest. The employment of individuals that create conflicts of interest have the potential to lead to exclusion from future work on BPA task orders.

6.5.1 The Contractor acknowledges that it is familiar with FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest, and agrees to avoid, neutralize, or mitigate such conflicts of interest in accordance with the principles set forth in the FAR.

6.5.2 If performance of any call order requires the contractor (to include subcontractors) to supply technical support related to systems or projects with which the contractor is already directly concerned, either prime or subcontract, the contractor shall immediately inform the KO. The order may be withdrawn if a conflict is found. The Contractor shall not undertake performance of any task which requires it to supply technical support regarding such systems until the notice is given and written consent to proceed is issued by the KO.

6.5.3 If the Contractor discovers an organizational conflict of interest or potential conflict of interest after award, a prompt and full disclosure shall be made in writing to the KO. This disclosure shall be made on the OCI Analysis/ Disclosure Form provided as an Attachment to the contract and shall include a description of the mitigation plan the Contractor has taken or proposes to take to avoid or mitigate such conflicts. See the OCI clause below for more details.

7.0 ADMINISTRATIVE AND OTHER PERFORMANCE REQUIREMENTS

7.1 Contractor Interfaces. The contractor may be required as part of the performance of this effort to work with other contractors working for the Government. Such other contractors shall not direct this contractor in any manner. Also, this contractor shall not direct the work of other contractors in any manner.

7.2 Disclosure of Information. Information made available to the contractor by the Government for the performance or administration of this effort shall be used only for those purposes and shall not be used in any other way without the written agreement of the KO. The contractor agrees to assume responsibility for protecting the confidentiality of Government records, which are not public information. Each contractor or employee of the contractor to whom information may be made available or disclosed shall be notified in writing by the contractor that such information may be disclosed only for a purpose and to the extent authorized herein.

7.3 Limited Use of Data. Performance of this effort may require the contractor to access and use data and information proprietary to a government agency or Government contractor which is of such a nature that its dissemination or use, other than in performance of this effort, would be adverse to the interests of the Government and/or others. Contractor and/or contractor personnel shall not divulge, or release data or information developed or obtained in performance of this effort, until made public by the Government, except to authorize Government personnel or upon written approval of the KO. The contractor shall not use, disclose, or reproduce proprietary data that bears a restrictive legend, other than as required in the performance of this effort. Nothing herein shall preclude the use of any data independently acquired by the

Intellectual Property and S-Series Specifications Analysis for Product Support 10:15 | Page contractor without such limitations or prohibit an agreement at no cost to the Government between the contractor and the data owner which provides for greater rights to the contractor.

7.4 Invoicing, Travel & Other Direct Costs (ODC). The Contractor shall invoice no less than monthly.

Invoices shall clearly identify hours, rates and materials charged during the period. All invoices shall provide detail to include all receipts, and other documentation which clears describes location, personnel, costs, and services in the invoice. Contractors should ensure their invoices have sufficient internal control reviews prior to submission into WAWF to prevent invoices being rejected. At the contract kick-off DASD(PS) will review invoice submission processes and provide formats for invoice documentation submission.

For FFP items, the Contractor must submit 2-in-1 or combo invoices according to the WAWF clause. For T&M, LH, or Cost items, the contractor must submit cost vouchers with the same WAWF coding as the FFP items, Approver, Acceptor, etc. (if possible, on a cost voucher), but the cost voucher must also include the DCAA DODAAC under the "DCAA Auditor DODAAC" entry in WAWF. To find the appropriate DCAA office, use the DCAA Office Locator at: http://www.dcaa.mil/home/locator. The contractor must also, simultaneously, provide a copy of any cost voucher and supporting documentation (including but not limited to all documentation necessary to substantiate any travel or ODC invoice to DCAA) to the COR and alternate COR. FAR 52.215-2 – Audit and Records – Negotiation – is in full force and effect.

7.4. Travel. Local travel requirements include travel to and from the Pentagon, the contractor’s site, and other Government facilities within the NCR. Travel within the NCR will not be reimbursed.

Travel outside the NCR (CONUS and OCONUS) may be required under this contract. The contractor shall be reimbursed for actual, allowable, allocable, and reasonable travel costs incurred during performance of this effort in accordance with FAR 31.205-46 “Travel Costs” and any other applicable laws or regulations.

7.5 Clearances. Contractor personnel on this task order shall be required to have a minimum of Secret.

The Contractor shall have the capability to transport classified information to and from their corporate offices and store classified materials up to “Secret” level at their off-site office spaces. Security procedures will be in accordance with DoD policies.

7.6 Facility Clearance. Secret Clearance is required. A contractor shall possess or acquire a facility clearance equal to the requirement on the DD254.

7.7 Security Requirements. Contractor personnel and their subcontractors must identify themselves as contractors during meetings, telephone conversations, in electronic messages, or correspondence related to the individual call order they are working on. Government supplied badges shall be worn by onsite contractor and subcontractor personnel and always visible. The COR will provide a finalized DD254 detailing and documenting the security requirements of the contract upon award.

The contractor is required to comply with all applicable laws and regulations pertaining to classified information.

The contractor is also responsible for complying with all applicable DoD manuals, regulations, and instructions, including but not limited to the documents listed below:

DoD Manual 5200.01 Vol 3 DoD Information Security Program: Protection of Classified Information

DoD Manual 5200.01 Vol 1 DoD Information Security Program: Overview, Classification, and Declassification

Intellectual Property and S-Series Specifications Analysis for Product Support 11:15 |

DoD Manual 5200.01 Vol 2 DoD Information Security Program: Marking of Information DoD Manual 5200.01 Vol 3 DoD Information Security Program: Protection of Classified

Information DoD Manual 5200.01, Volume 4, “DoD Information Security Program: Controlled Unclassified

Information DOD INSTRUCTION 5200.48 Controlled Unclassified Information (CUI) DoD Directive 5210.50 Management of Serious Security Incidents Involving Classified

Information

7.8 Physical Security: The contractor shall be responsible for safeguarding all Government property provided for contractor use. At the close of each work period, Government facilities (if required), equipment, and materials shall be secured.

7.9 Keys, Badge, and Common Access Card (CACs) Control: The Contractor shall be able to establish and implement methods of making sure all keys, badges and CACs issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall be able to develop procedures covering key, badge and CAC control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys, badges, and CACs by personnel who no longer require access. The Contractor shall immediately report any occurrences of loss or other issues to the KO.

7.9.1 Lock Combinations: The Contractor shall be able to establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons.

7.9.2 Disclosure of Information: Information made available to the Contractor by the Government for the performance or administration of this effort shall be used only for those purposes and shall not be used in any other way without the written consent of the KO. Contractor and/or contractor personnel shall not divulge, or release data or information developed or obtained in performance of this effort, until made public by the Government, except to authorized Government personnel or upon written approval of the KO.

The contractor will not use, disclose, or reproduce proprietary data that bears a restrictive legend, other than as required in the performance of efforts within this BPA. Nothing herein will preclude the use of any data independently acquired by the contractor without such limitations or prohibit an agreement at no cost to the Government between the contractor and the data owner which provides for greater rights to the contractor.

The Contractor agrees to assume responsibility for protecting the confidentiality of Government records, which are not considered public information. Each Contractor or employee of the Contractor to whom information may be made available or disclosed, shall be notified in writing by the Contractor that such information may be disclosed only for purposes and to the extent authorized within the individual call order.

The Contractor shall not release any information received through any call order on the BPA to the public, media or other unauthorized persons or organizations unless the Government has conducted the appropriate security review and granted written approval (e.g., posting information to a public website). Performance of this effort may require the contractor to access and use data and information proprietary to a Government agency or Government contractor, which is of such a nature that its dissemination or use, other than in performance of this effort, would be adverse to the interests of the Government and/or others. The contractor will sign non-disclosure agreements at the beginning of each call order certifying that none of the information received through their work on a call order many be disseminated in any manner other than as allowed in the order.

7.9.3 Government Furnished Property. The Government will provide IT support to maintain Government furnished Property (GFP) that may include laptops and smart phones. Government furnished IT equipment

Intellectual Property and S-Series Specifications Analysis for Product Support 12:15 | provided in support of this TO that will be removed from the Government facilities is considered GFP. All GFP will be furnished in as is condition and physical inspection instructions may be provided by the provider of the GFP. All GFP will be processed by the COR. Details of the actual GFP will be provided at the time of the GFP processing and the contract will be modified to add the GFP Attachments. The Contractor is responsible for the proper care, maintenance and use of Government property in its possession or control from time of receipt until properly relieved of responsibility in accordance with the terms of the contract. The Contractor shall pay all costs for repair or replacement of Government furnished property that is damaged or destroyed due to Contractor negligence.

7.9.4 Insurance.

a. In accordance with FAR 52.228-5, Insurance - Work on a Government Installation, and FAR 52.228-7, Insurance - Liability to Third Persons, insurance policies with the following types and minimum amounts shall be furnished to the Contracting Officer within 30 days of award and maintained during the period of performance of the Basic Contract:

(1) Worker’s Compensation and Employer’s Liability, specified at FAR 28.307-2(a) of not less than $100,000 for each occurrence.

(2) General Liability, specified at FAR 28.307-2(b) of not less than $500,000 for each occurrence;

(3) Automobile Liability, specified at FAR 28.307-2(c) of not less than $200,000 per person and $500,000 for each occurrence, and property damage liability insurance of not less than $20,000 for each occurrence;

(4) Aircraft public and passenger liability, specified at FAR 28.307-2(d), when aircraft are used in connection with performing the contract, the Contracting Officer shall require aircraft public and passenger liability insurance. Coverage shall be at least $200,000 per person and $500,000 per occurrence for bodily injury, other than passenger liability, and $200,000 per occurrence for property damage. Coverage for passenger liability bodily injury shall be at least $200,000 multiplied by the number of seats or passengers, whichever is greater;

(5) Vessel liability, specified at FAR 28.307-2(e), when contract performance involves the use of vessels, the Contracting Officer shall require, as determined by the agency, vessel collision liability and protection and indemnity liability insurance.

b. Defense Base Act Insurance. Pursuant to FAR 28.305, Defense Base Act insurance coverage provides workers’ compensation benefits (medical, disability, death) in the event of a work-related injury or illness outside the United States. The Government requires that employees hired by Contractors and Subcontractors who work internationally be protected by the Defense Base Act coverage, regardless of their assignment and/or location unless a waiver has been obtained by the U.S. Department of Labor. DBA insurance shall be at no direct cost to the Government and shall be furnished to the Contracting Officer within 30 days of award of an Order.

8.0 NON-PERSONAL SERVICE STATEMENT.

Contractor employees performing on call orders under this PWS will be controlled, directed, and supervised at all times by management personnel of the contractor. Contractor management will ensure that employees properly comply with the performance work standards outlined in this PWS, and within the individual call orders. Contractor employees will perform their duties independent of, and without the supervision of, any Government official. The tasks, duties, and responsibilities set forth in specific call orders may not be

Intellectual Property and S-Series Specifications Analysis for Product Support 13:15 | interpreted or implemented in any manner that results in any contractor employee creating or modifying Federal policy, obligating the appropriated funds of the U.S. Government, overseeing work of Federal employees, providing direct personal services to any Federal employee, or otherwise violating the prohibitions set forth in Part 7.5 and 37.1 of the FAR. The Government will perform the inspection and acceptance of the deliverables provided.

9.0 PERSONNEL REQUIREMENTS.

Contractor will provide personnel consistent with requirements of this PWS and the staffing plans in the contractor’s technical proposal/quote.