A03 PWS_DSCU Knowledge Portal Final.pdf

PDF 313 KB Posted

Attached to
Knowledge Portal Support Services
Solicitation number
HQ003425PE129
Issued by

About this file

This Performance Work Statement (PWS) is for the Defense Security Cooperation University (DSCU) Brigadier Charles Young Institute Knowledge Portal project, issued by the Defense Security Cooperation Agency (DSCA). The non-personal services contract aims to develop knowledge management portals supporting security cooperation workforce needs over a 6-month base period with one 6-month option period.

Key objectives include: 1) Using evidence-based customer personas and existing government systems to identify and curate security cooperation-relevant evidence and information, 2) Developing a multichannel engagement strategy to deliver content to workforce members, and 3) Preparing data to support public, Controlled Unclassified Information (CUI), and classified knowledge portals. The contract requires a Project Manager, Analyst IV (Senior), and Analyst I, all with specific educational and experience requirements. Personnel must have a Secret security clearance, be U.S. citizens, and comply with strict government security and operations security protocols. The contract is firm-fixed price, with an estimated 1,872 hours per year across the three labor categories.

View the file

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

PERIOD OF PERFORMANCE (PWS)

FOR

Defense Security Cooperation University (DSCU) Brigadier Charles Young Institute (CYI) Knowledge Portal

Defense Security Cooperation Agency (DSCA)

PART 1

GENERAL INFORMATION

1. GENERAL: This is a non-personal services contract to provide Knowledge Management Portal support services. 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 Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, material, supervision, and any other items or non-personal services necessary to perform the tasks outlined in this performance work statement except for those items specified as Government furnished property and services. The contractor shall perform to the standards in this contract.

1.2 Background: The Defense Security Cooperation University (DSCU) is the Department of Defense’s Center of Excellence for security cooperation education and training. The contractor will collaborate with DSCU’s BG Charles Young Research, Analysis, and Lessons Learned Institute (Young Institute) to develop public, CUI, and classified knowledge portals. This work will develop future security cooperation workforce needs and requirements over a six-month period, in preparation for a longer-term project, subject to competitive bid, to provide workforce members the knowledge and information they need to achieve program outcomes and advance U.S. national security interests.

1.3 Objectives: DSCU requires contract support to successfully implement the following:

• Using evidence-based customer personas and existing government systems, identify and curate security cooperation–relevant evidence and information.

• Develop a multichannel engagement strategy to deliver security cooperation– relevant evidence and information to workforce members.

• Prepare data to support public, CUI, and classified knowledge portals.

1.4 Scope: As directed by DSCA, DSCU manages, implements, and supports a variety of programs, initiatives, and systems related to its mission areas. DSCU requires specialized subject matter expertise in the areas of KMP development. The DSCU knowledge portals will require data management, knowledge curation and integration, and web dissemination on specific user personas and test users. The key is developing the processes, tagging procedures, and knowledge curation that DSCU needs for the longer-term project to succeed

1.5 Period of Performance: The period of performance shall be for be for one (1) Base Period of 6 months and one (1), 6-month option period.

1.6 General Information:

1.6.1 Quality Control: The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program is the means by which he assures himself that his work complies with the requirement of the contract. The QCP shall be delivered via electronic mail within 30 days of contract award. Amendments/changes to the QCP shall be delivered to the COR and KO within five (5) working days when changes are made thereafter. After acceptance of the quality control plan the contractor shall receive the contracting officer’s acceptance in writing of any proposed change to his QC system.

1.6.2 Quality Assurance: The Government shall evaluate the Contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the Government must do to ensure that the Contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.2.1 Identification of Non-Disclosure Requirements:

The activities in this PWS will require the contractor to receive Government furnished information (GFI), and access data and information proprietary to other contractors or government agencies and/or of such a nature that its dissemination or use, other than in performance of this PWS, would be averse to the interests of the government and/or others. The contractor, including contractor personnel, subcontractors, and consultants, will not divulge or release data or information developed or obtained in performance of this PWS except to government authorized personnel or upon written approval of the Contracting Officer (KO) or Contracting Officer Representative (COR). The contractor will not use, disclose, or reproduce proprietary data, which bears a restrictive legend, other than as required in the performance of this PWS. The limitations above do not apply to data or information that has been made public by the government. All products, deliverables and work produced, as well as associated back-up documentation, will be considered the property of the Government. Contractors will be expected to sign Non-Disclosure Agreements as part of their on-boarding process.

1.6.3 Recognized Holidays: Contractor is not required to work on federal holidays. However, if a program occurs over a holiday period, a limited number of personnel may be needed to support a program. Prior coordination shall be made and approved between the COR and KO

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Juneteenth National Independence Day Christmas Day Independence Day

1.6.4 Hours of Operation: The contractor is responsible for conducting business, between the hours of 8:00 AM to 5:00 PM, Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. Situational telework will be implemented when warranted by conditions. For the duration of the contract period of performance, the contractor shall maintain an adequate workforce for the uninterrupted performance of all tasks defined within the PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.6.5 Place of Performance: The work to be performed under this contract will be performed primarily at the DSCU campus located in Arlington, Virginia. Some tasks may be performed at the contractor’s facility or at other CONUS Government facilities as necessary to achieve the objectives of the contract, but the primary duty location for the Contractor’s personnel supporting this contract shall be at a DSCU campus, and daily physical presence of the Contractor’s workforce at the primary duty location is required. Telework may be authorized at the discretion of the Government.

Performance of some tasks under this contract may require contractor personnel to travel away from their primary duty location at DSCU’s discretion.

1.6.5.1 Telework: The government may permit telecommuting (telework) to contractors when determined to be in the best interest of the Government in meeting work requirements.

The contractor must identify to the COR any task/work requirements that may be performed at an alternate location.

The Individual Contractor Personnel shall provide services from their authorized telework worksite location IAW Department of Defense Instructions (DoDI)1035.1 Telework Policy.

1.6 Type of Contract: The government will award a contract type of Firm Fixed Price (FFP).

1.7 Security Requirements: Contractor personnel performing work under this contract must have a Secret Clearance at time of the proposal submission and must maintain the level of security required for the life of the contract. The security requirements are in accordance with the attached

DD254.

1.7.1 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.8 Special Qualifications: Within ten (10) working days of award of this contract or 10 days of employment, the Contractor shall insure that all Contractor employees complete annual Government-furnished training in Information Assurance, Privacy Act, Operational Security, and other assigned training required. Any Contractor behavior deviating from standards taught in the course shall be grounds for termination of the contract. Contractor must maintain a cyber-threat plan security awareness certification plan.

1.9 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced.

Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.10 Contracting Officer Representative (COR): The (COR) will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance: maintain written and oral communications with the Contractor concerning technical aspects of the contract: issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially regarding changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.11 Key Personnel: The Contractor shall provide resumes of Key Personnel. Personnel identified as Key Personnel are essential to the work being performed and must meet or exceed the required levels of experience and education outlined below. It is expected that key personnel presented within the contractor’s response will perform the work if a contract is awarded. Prior to changing an individual identified as Key Personnel, the Contractor shall notify the Contracting Officer in no less than 30 business days and will submit written justification as to the reason for substitution.

Substitution within the first 90 days will only be considered for reasons of illness, death, or termination of employment. The Justification must include the name and qualifications of the proposed substitute(s). The proposed substitute(s) will possess qualifications equal to or superior to those of the Key person being replaced. The Contractor shall not substitute Key personnel without written consent from the Contracting Officer. No change in fixed unit prices may occur because of key personnel substitution. The key personnel may, with the consent of the contracting parties, be amended from time to time during this contract to either add or delete personnel, as appropriate, provided that the contracting officer is notified 30 days in advance and an adequate substitution is presented and accepted by the Contracting Officer. Substitutions of Key Personnel shall be equal to or have greater qualifications than the personnel being replaced.

POSITION MINIMUM QUALIFICATIONS SUPPORT TASK SECURITY

Project Manager

Master’s degree is required in International Relations, International Affairs, International Politics, Operations Research, or related field.

Minimum 5 years of experience in data transformation and organizational change.

Minimum 3 years’ experience directly supporting international programs, foreign military sales or security cooperation programs

Minimum 3 years’ experience executing and supporting training and education activities.

Minimum 3 experience executing and supporting training and education activities.

Minimum 3 experience executing and supporting workforce development initiatives.

5.1, 5.1.1,5.1.2,5.1.3,5.1.

Current Secret Security

Clearance

Analyst IV (Senior) (Transformation Analyst)

Bachelor’s degree in international relations, International Affairs, International Politics, Operations Research, Statistics, Accounting, or related field.

Minimum 5 years of experience in data transformation and organizational change.

5.2,5.2.1,5.2.2,5.2.3, 5.3,5.3.1,5.3.2,5.3.3, 5.4.1

Current Secret Security

Clearance

Minimum 3 years’ experience directly supporting data transformation projects.

Minimum 3 years’ experience executing and supporting workforce development or training and education activities.

Minimum 3 years’ experience analyzing data systems and supporting requirements definition for system enhancements.

3 years of working knowledge or experience with: Training and Education; International Affairs; Data Collection and Analysis;

Quantitative and Qualitative Research Methods; Report Writing and Briefing Preparation; Systems Analysis and Requirements Definition; Microsoft Office 365 (DoD MS Office 365 preferred), especially Excel and SharePoint. The ability to develop lists in SharePoint and integrate them into web delivery is particularly important.

1.11.1The Contractor is expected to provide a fully trained workforce to the government;

therefore, personal development training costs and hours are not billable to the government. The following key positions have been identified:

1.11.2 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 such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. When on government-occupied property, badges will be worn identifying the staff as visiting contractors.

1.12 Contractor Travel: Contractor will not be required to travel.

1.13 Other Direct Costs: N/A All ODCs must be preapproved by the KO prior to expending funding. This category includes travel, reproduction, shipping expenses associated with training activities, data/code offline transfers, and visits to contractor facilities are authorized.

1.14 Data Rights: Please see Solicitation/award clause for details on Data Rights.

1.15 Organizational 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, EckerJL Cross-Out

EckerJL Highlight specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.16 Phase in Period: To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall have personnel on board, during the 30-day phase in periods. During the phase in period, the Contractor shall become familiar with performance requirements in order to commence full performance of services on the contract start date.

PART 2

DEFINITIONS & ACRONYMS

2.DEFINITIONS AND ACRONYMS:

2.1 DEFINITIONS:

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 or 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 administer 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.2 DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

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

2.1.4KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

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

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

2.1.7 QUALITY ASSURANCE Surveillance Plan (QASP). An organized, written document specifying the surveillance methodology used for surveillance of contractor performance.

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

2.1.9 SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.1.10 WORKDAY. The number of hours per day the Contractor provides services in accordance with the contract.

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

2.1. ACRONYMS:

A-129 Circular A-129 Policies for federal Credit Programs and Non-Tax Receivables CAC Common Access Card CFR Code of Federal Regulations CI Classified Information CLIN Contract Line-Item Numbers CO Contracting Officer CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative CSC Credit Subsidy Calculator CUI Controlled Unclassified Information DAAPM Defense Assessment and Authorization Process Manual DCSA Defense Counterintelligence and Security Agency DD Form 254 Department of Defense Contract Security Requirement List DFARS Defense Federal Acquisition Regulation Supplement DISS Defense Information System for Security DOD Department of Defense DODI Department of Defense Instructions DSCA Defense Security Cooperation Agency ERP Enterprise Resource Planning EST Eastern Standard Time FAR Federal Acquisition Regulation FFP Firm Fixed Price FMR Financial Management Regulations FOIA Freedom of Information Act FOUO For Official Use Only FSO Facility Security Officer FY Fiscal Year GFE Government Furnished Equipment IAW In Accordance With ITP Insider Threat Program KO Contracting Officer NCR National Capital Region NDA Non-Disclosure Agreements NISPOM National Industrial Security Program Operating Manual NIST National Institute of Science and Technology OBO Office of Business Operations OCI Organizational Conflict of Interest OCONUS Outside Continental United States (includes Alaska and Hawaii) ODC Other Direct Costs OPSEC Operational Security 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 SC Security Cooperation SOP Standard Operating Procedure

RCM Risk and Control Metrics T3 Tier 3 T3R Secret Periodic Reinvestigations TPOC Technical Point of Contact US United States USC United States Code USG United States Government VAR Visitor Authorization Request

PART 3

GOVERNMENT FURNISHED PROPERTY,

EQUIPMENT, AND SERVICES

3.GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1 The Government may provide, as Government Furnished Equipment (GFE): Secure laptop with access to the required portals, networks, and business application. The Government will furnish relevant internal documents and datasets that will serve as the knowledge base foundation for the vendor. Internet connection will not be furnished;

therefore, Internet access shall be provided by the Contractor.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 General - The Contractor shall furnish all supplies, non-IT equipment, facilities and services required to perform work under this contract that are not listed under Section 3 of this PWS.

4.2. Materials - The Contractor shall provide paper, printers, and other basic office equipment needed for productivity.

PART 5

SPECIFIC TASKS

5.1 Task 1: Provide project leadership and management.

5.1.1 The contractor shall provide the following Program Management support services:

Management and oversight of all activities performed by contractor personnel, including subcontractors, to satisfy requirements.

• Providing overall direction, administration, quality assurance, and leadership for all work outlined in this Performance Work Statement (PWS).

• Provide management, direction, administration, quality assurance (QA), and leadership in the execution of this Performance Work Statement (PWS).

• Facilitate Government and contractor communications and all activities necessary to ensure the accomplishment of timely and effective support.

• Use industry best-standards and proven methodologies to assure all activities are identified, documented, and tracked. The project will continuously be evaluated and monitored for timely and quality service.

• Notify the Contracting Officer (KO), Contracting Officer’s Representative (COR) in writing of any technical, financial, personnel, or general managerial problems.

• Ensure successful onboarding and off boarding of contactor employees

5.1.2 Technical Contract Kick-Off Meeting: The contractor shall schedule, coordinate, and host a Kick-off Meeting no later than (NLT) ten days after the award, at the location approved by the COR. The meeting shall provide the opportunity to discuss technical, management, and logistic issues, and reporting procedures. At a minimum, the attendees shall include key contractor personnel, key Government representatives, CO, and COR. The contractor shall provide a Project Kick-Off Meeting Agenda NLT five (5) days after award that will include, but not limited to, the following:

• Introduction of personnel

• Overview of project tasks

• Overview of organization (complexity)

• Schedule

• Performance metrics

• Discussion of draft Program Management Plan (PMP)

• Government-furnished information (GFI)

• Security requirements (Building access, badges, Common Access Cards [CAC]

• Invoice procedures

• Monthly meeting date

• Reporting Requirements, e.g., Monthly Status Report (MSR)

• POCs to include name, phone, email and role.

• Roles and Responsibilities

• Overview of incoming Transition Plan to include process and timeframes.

• Prioritization of contractor activities

• Any initial deliverables

• Other logistic issues

• Sensitivity and protection of information

5.1.3 Monthly Status Report: The PM shall develop and deliver a MSR using Microsoft (MS) Office Suite applications by the 10th day of each month or the following business day (if the 10th day falls on a Saturday or Sunday) via electronic mail (email) to the COR. The report shall briefly summarize, by task, the management and technical work conducted during the month. The contractor shall provide at a minimum the following information:

• Activities during reporting period, by task to include a brief description of the task, on-going activities, new activities, activities completed, deliverables submitted for that period, and progress to date on all above-mentioned activities.

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

• Government actions required.

• Schedule (shows major tasks, milestones, and deliverables; planned and actual start and completion dates for each).

• Summary of trips taken, conferences attended, etc. (attach trip reports to the reporting period MSR).

• Current and projected utilization of each CLIN by month.

• Financial status including cumulative (total-to-date) invoiced costs for each CLIN.

• Monthly Performance Reporting (MPR). As part of the MSR the contractor PM shall prepare a MPR, which addresses how the contractor met the Acceptable Quality Levels (AQL) for each Performance Requirement in the QASP during the month. This information will be used, in conjunction with feedback from TPOC and other Government personnel, to assess the contractor’s performance. The performance requirements, standards and methods of measurement for this PWS will be located in the QASP.

• Any comparison data /monthly performance reports.

5.1.4 Technical Status Meetings: The contractor PM shall host a contract activity and status meeting with the TPOC and other key DSCA stakeholders within ten days after each engagement to be identified. The purpose of this meeting is to ensure all stakeholders are informed of the current activities of concern, status, and provide opportunities to identify other activities as well as establish priorities and coordinate resolution of identified problems or opportunities. The meeting shall provide an opportunity to discuss and respond to questions and inquiries from stakeholder, requirements initiatives on the planning of activities per specific time periods, and work with DSCA to better define requirements. The contractor PM shall provide minutes of these meetings, including attendance, issues discussed, decisions made, and action items assigned, to the COR NLT 24 hours following each meeting.

5.2 Task 2: Using evidence-based customer personas and existing government systems, identify and curate security cooperation–relevant evidence and information.

5.2.1 The contractor will develop a framework for identifying, organizing, and curating security cooperation–relevant evidence and information for future access on public and CUI sites. This framework will rely on existing government information systems, in particular SharePoint, and will center on the development of evidence-based customer personas. The intent is to curate evidence-based research for customers to apply in security cooperation practice. These customer personas will be developed in conjunction with the government and will include all the personas necessary, in the government’s estimation, to tailor user experience to key groups in the security cooperation workforce. These personas include, but are not limited to, portfolio directors, faculty, planners, and security cooperation officers.

5.2.2 Evidence-based theories of change undergird the framework to identify, organize, and curate security cooperation–relevant evidence and information. The contractor will demonstrate this in the maintenance and development of data codebooks (to govern language standardization and definitions) and standard operating procedures (to govern data management and metadata development standards), and in establishing processes to identify and curate new and existing evidence. The contractor will also distinguish between knowledge, evidence, and information to customize user experience.

5.2.3 Beginning no more than 30 days after kickoff and continuing till the end of the period of performance, the contractor will maintain a data codebook and reference guide to define personas, govern tagging and curation, and provide consistency to evidence and data management. The intent is to maintain a consistent look, feel, and user experience, while preventing vendor lock-in and giving the government the tools it needs to continue the work after the period of performance. The contractor will submit the latest draft of this data codebook quarterly, beginning three months after kickoff, with a final draft submitted prior to the end of the period of performance.

5.3 Task 3: Develop a multichannel engagement strategy to deliver security cooperation– relevant evidence and information to workforce members.

5.3.1 The contractor will develop a strategy to deliver content to members of the security cooperation workforce. This includes integrating existing web presence with email outreach, event delivery, and content production activities at the Young Institute. The objective is to “deliver the right evidence, at the right time, to the right person” to empower security cooperation professionals.

5.3.2 As part of this engagement strategy, the contractor will create and maintain a feedback mechanism to continually improve and target content. The contractor will use measurement and data to achieve this, including observed user behavior and survey feedback. In principle, the Young Institute needs to understand what brings security cooperation professionals to its content and what keeps them coming back.

5.3.3 The contractor will develop and iterate with the government on a multichannel strategy to engage in nonpublic fora, beginning no more than 30 days from kickoff and continuing till the end of the period of performance. This analytical planning document could include trends in feedback and anecdotal success stories. The intent is to generate a body of evidence justifying expanded access to content for the workforce while avoiding vendor lock-in and providing a means of consolidating a common approach to communication and outreach. The contractor will capture this strategy quarterly, beginning three months after kickoff, with a final draft submitted prior to the end of the period of performance.

5.4 Task 3: Prepare data to support public, CUI, and classified knowledge portals.

5.4.1. The contractor will organize data for public, CUI, and classified knowledge portals, preparatory to the eventual stand-up of knowledge portals. In following government policies and instructions related to information assurance and security, the contractor will develop a concept for information to flow up the classification chain, but not down. Sufficient air-gapping between public, CUI, and classified systems is essential. The contractor will develop knowledge portal data records & security concept and provide them to the PM.

PART 6

APPLICATIONS

6.APPLICABLE PUBLICATIONS:

6.1 The Contractor must abide by all statutes, applicable regulations, publications, manuals, and federal policies, procedures.

PART 7

ATTACHMENT/TECHNICAL EXHIBIT LISTING

7. Attachment/Technical Exhibit List:

7.1 Technical Exhibit 1 – Performance Requirements Summary

7.2 Technical Exhibit 2 – Deliverables Schedule

7.3 Technical Exhibit 3 – Estimated Workload Data

7.4 Technical Exhibit 4 – Security Requirements

TECHNICAL EXHIBIT 1

PERFORMANCE REQUIREMENTS SUMMARY

Performance Requirements Summary (PRS) This summary identifies critical factors for contract success. It identifies both the performance objectives for those factors and the performance threshold required for each performance objective.

The absence of any contract requirement from the PRS shall not detract from its enforceability nor limit the rights or remedies of the Government under any other provision of the contract including the clauses entitled "Inspection of Services" and "Default". The Government reserves the right to surveil all services called for in the contract to determine whether the performance objectives and goals were met.

The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success and are as shown:

Performance Objectives Standard Performance Threshold

Method of Surveillance

PRS#1

Onboarding and Offboarding process: Contractor onboarding process for each performance location

Contractor shall document the necessary steps to onboard at each location in accordance with DSCA Security and Installation guidance, policy, and practices

Development no later than 30 days. Final

Version 30 days after government review.

Updates and changes within 30 days from notification.

Initial Development – 100% Inspection

Final Versions – 100% Inspection

Updates and Changes – 100% Inspection

PRS#2

Monthly Status Report (MSR)

100% on time delivery based on required delivery date set by GOV POC.

Additional changes and rework with timeline will be set by Gov POC.

Adherence to DSCU curriculum templates.

Information Storage and file control on DSCU One Drive

Updates and Drafts in a timeline set by Gov POC prior to final due dates.

0 % deviation from on- time delivery standards set and modified by Gov

POC.

Initial Development – 100% Inspection

Final Versions – 100% Inspection

Updates and Changes

– 100% Inspection

Validated by Young Institute Evidence

Manager and/or Gov

POC

PRS #3 Technical Status Meetings 100% delivery on time

Contractor must conduct meetings NLT 10 days after award.

Meeting minutes delivered to the COR NLT 24 hours after meeting.

0% deviation from on-time delivery standards.

100% inspection

PRS #4:

Prepare and Submit tasks and deliverables related to Evidence Management (Young Institute) that is outlined in the PWS.

• Data Codebook & Resource Guide

• Outreach Strategy

• Knowledge Portal Data

Architecture and Security Concepts

100% on time delivery based on required delivery date.

Adherence to DSCU curriculum templates.

Information Storage and file control on DSCU One Drive

0% deviation from on-standards.

Manager

PRS #5:

The Contractor shall attend all contract tasks related meetings and provide the meeting minutes to Government withing 48 hours of meeting.

100% on time delivery based on required delivery date.

Adherence to DSCU curriculum templates.

Information Storage and file control on DSCU One Drive

0% deviation from on-standards

Manager

TECHNICAL EXHIBIT 2

Deliverable Schedule

The Contractor shall provide deliverables as specified in the PWS. All deliverables shall be due to the DSCA COR(s) for the applicable task no later than 5:00 p.m. (1700 hours) as appropriate for the time of year (standard or daylight savings time) and primary performance location for the deliverable (i.e., 5:00 p.m. Central time zone for Scott Air Force Base (AFB), IL deliverables on Task Order 0009, etc.). If a deliverable due date falls on a weekend or holiday, the Contractor shall submit the deliverable on the last workday prior to the due date.

The Contractor shall develop and provide thorough and detailed deliverables that are in editable and searchable versions of Microsoft Office 2013 (Word, Excel, PowerPoint, Access) or the latest Government version, Portable Document Format (PDF) using Acrobat Adobe X (or the latest Government version). Use of Visio and Project may be necessary. The Contractor shall not provide or submit any documents in a zip file format unless specifically pre- approved by the COR. The PWS deliverable requirements are as follows:

Task Deliverable Title Format Due Date Distribution and Copies

5.1 Project Kick-off

Meeting

Editable and Final Word, Excel, or PDF NLT 5 days of award Copy to the PM KO

5.1 Monthly Status Report Editable and Final

Word, Excel, or PDF

NLT the last day of each month during performance period

Copy to the PM, COR and

KO

5.2 Data Codebook &

Resource Guide

Electronic delivery on OneDrive

NLT 30 days after kickoff meeting and recorded in nonpublic forum quarterly.

Final draft due before end of performance.

Copy to the PM and KO

5.3 Outreach Strategy Electronic Delivery

on OneDrive

NLT 30 days after kickoff meeting and recorded in nonpublic forum quarterly.

Final draft due before end of performance.

Copy to the PM and KO

5.4 Knowledge Portal Data

Records & Security Concept

Electronic delivery on OneDrive

NLT 30 days after kickoff meeting and recorded in nonpublic forum quarterly.

Final draft due before end of performance.

Copy to the and KO

TECHNICAL EXHIBIT 3

Workload Data Information

Projected Level of Effort: The data provided is an estimate of what it may take to perform the requirements listed in the Performance Work Statement. The labor categories and units provided below are only estimates and should not be viewed as mandated for proposers. All proposals should include the labor mix and hours appropriate and necessary for the proposing performer to complete the required work. Hours required may be lower or higher than those estimates indicated below; as such, these estimates may not be construed as a guarantee of labor requirements. The contractor shall have in place the capability to fulfill the requirements of the contract.

Full Time Equivalent (FTE) estimated is 1,872 hours per year.

Projected for 6 Month Base Period (Firm-Fixed Price)

PWS Task

ID

CLIN Type Labor Category FTEs (Estimated)

Hours

5.1–5.3

FFP

Program Manager

Analyst IV (Senior)

5.1, 5.3

Analyst I

Projected for 6-Month Option Periods One (1) (Firm-Fixed

Price)

PWS Task

ID

CLIN Type Labor Category FTEs (Estimated)

Hours

Program Manager

Analyst IV (Senior)

5.1, 5.3

Analyst I

TECHNICAL EXHIBIT 5

SECURITY LANGUAGE

Security Requirements:

The overall classification of work associated with this PWS is at the SECRET level. The Contractor shall have a current facility clearance of SECRET at the time of proposal to work this effort. All personnel assigned to this contract must be U.S. citizens.

Investigation Requirements:

Contractor personnel working in support of this contract shall have at least a favorably completed FBI fingerprint check, credit check, lived in the United States for a minimum of 3 years, and either a National Agency Check and Inquiries (NACI) or Tier 1 (T1).

The Contractor Facility Security Officer (FSO) is required to submit a signed Visitor Authorization Request (VAR) to the duty station Security Office, verifying the Contractor(s) personnel security credentials prior to the beginning of each contracting/task order period of performance and as new Contractor employees are assigned to the contract.

The contractor is required to have personnel cleared with a temporary or final SECRET clearance at the contract start date. During the performance of the contract, any released contract personnel’s replacement should also have temporary or final clearance at the level of Secret.

The Contractor Facility Security Officer (FSO) is required to submit a signed Visitor Authorization Request (VAR) to the duty station Security Office, verifying the Contractor(s) personnel security credentials prior to the beginning of each contracting/task order period of performance and as new Contractor employees are assigned to the contract temporary SECRET eligibility may be accepted provided it has been awarded by the DCSA CAS, and DISS reflects the information for the contract awarded company.

Visit Authorization Request (VAR):

Visit Authorization Request (VAR) is required prior to the beginning of each contract/task order period of performance and for any new contract personnel assigned to the contract during the duration after initial VAR submission.

The Facility Security Officer must submit a VAR per the processes outlined below:

The Contractor may use their format with all of the following information provided on company letterhead:

• Company Name, address, telephone number, assigned Commercial and Government Entity code, facility security clearance

• Contract/Task Order Number

• Name, Rank, Title or Position, Email, Social Security Number, Date of Birth, Place of Birth, Nationality, Citizenship

• Clearance and Date

• Purpose of visit

• Date/Duration of visit

• Name of COR/Alternate COR

DSCA Security personnel can be contacted for Industrial or Personnel Security related issues at dsca.ncr.odam.mbx.industrial-security@mail.mil.

All Contractor employees with an incident report in DISS who have had their access to classified suspended will not be permitted access on a DSCA facility or project. The FSO is required to report any derogatory information on all individuals associated with this contract to DSCA COR and DSCA Security.

Information Security and other miscellaneous requirements:

Contractor employees will be required to comply with all Government security regulations and requirement to include NISPOM, 32 CFR 117, and other government security guidelines as directed. Initial and security training and briefings will be provided by Government security personnel. Contractor employees will not transmit or receive any government documents to any personally owned devices. Contractor employees will be required to complete all initial and periodic security training and briefings.

Failure to comply with Government security regulations and requirements shall require the company to provide the Government with a written remediation/corrective action plan;

furthermore, failure to comply with such requirements can be cause for removal, and the Contractor will not be able to provide service on this contract/order.

DSCA retains the right to request removal of contractor personnel regardless of prior clearance or adjudication status, whose actions, while assigned to this contract, clearly conflicts with the interest of the Government.

The Contractor shall comply with DOD 5400.7-R, Chapter 4, DOD Freedom of Information Act (FOIA) Program, and DOD 5200.48, Controlled Unclassified Information requirements. This regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding CUI and FOUO material.

Contractor personnel shall report to an appropriate authority any information or circumstances of which they are aware may pose a threat to the security of DOD personnel, Contractor personnel, resources, and classified or unclassified defense information. This also includes the loss of any DOD identification cards.

Physical Security:

The contractor shall be responsible for safeguarding all government property provided for the contractor’s use. Government facilities, property, and materials shall be protected in accordance with government security procedures. The Government will provide contractor personnel with appropriate identification badges that allow access to the facility for the period of performance of the contract. All badges are to be displayed at all times while in DSCA spaces. The Contractor shall also ensure all Government equipment and materials are secured at the end of each day.

Contractor employees departing DSCA will be required to out process with DSCA Security. The Common Access Card (CAC), DSCA Badge, and other access cards issued to contractor personnel are government property and must be returned either upon departure from the program or at the conclusion of the contract (whichever comes first).

The contractor shall immediately report the occurrence of a lost access badge to the Contracting Officer Representative (COR), or other government security personnel.

Personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 522a and applicable agency rules and regulations.

Operations Security:

The contractor must comply with the requirements in DoD 5220.22, National Industrial Security Program; and DoD 5205.02, Operations Security (OPSEC) Program during the performance of work. The contractor will adhere to the following minimum requirements in support of the DSCA OPSEC Program:

a. Personal electronic devices into government spaces, laptops, tablet PCs, cellular phones, two-way radios, cameras, recording devices, and data recording/storage devices is STRICTLY controlled and forbidden in most cases. Company issued equipment required for the performance of work must be approved by the government Security Officer.

Photography and recording are not allowed except for official and approved use only.

b. Contractor personnel shall not discuss government operations in public or over unprotected or unencrypted communications. Official Business and controlled unclassified information may only be transmitted as directed in the PWS or designated by the government official.

c. The Contractor shall not post to company websites, publications, newsletters or other media any images, data or information that reveal sensitive government operations, personnel, equipment, and/or classified or controlled unclassified information, refer to paragraph (d) below. When in doubt, company press releases related to this contract should be coordinated through the Contracting Officer Representative (COR) or Technical Point of Contact, as applicable.

d. Because observation of events, operations, physical changes, etc. may reveal National Security information, specific restrictions are needed to preclude unintentional release of this information to unauthorized parties. (Unauthorized disclosure and transfer of National Security Information is punishable under 18 USC § 793.) Therefore, contractor personnel shall not disclose to unauthorized third parties, post to unofficial sites (including Social Networking sites) any images, data or information, or observed events that reveal sensitive government operations, personnel, equipment, including, but not limited to:

1. Tactics, techniques and procedures, production or work schedules, any visible or concealed modifications, upgrades, additions to vessels, aircraft, or weapons or equipment;

increases, change, or decreases in work/deployment frequency or government personnel, vehicle, vessel or aircraft movements; specialized equipment orders, deliveries, shipments, etc., Unauthorized disclosures and attempts to solicit this type of information by unauthorized third parties or others not affiliated with this contract shall be reported to government Security Office, contract point of contact, and your company Facility Security Officer and/or the Defense Counterintelligence and Security Agency. Non-Disclosure requirements remain in effect during the duration of this contract and indefinitely thereafter.

e. Government issued badges, identification shall be removed and/or concealed from plain sight when off station and shall not be left in vehicles or unprotected. Badges and passes may not be duplicated or copied or loaned to others. Lost or stolen identification badges must be immediately reported to the DSCA Security Office.

f. Practice OPSEC and implement countermeasures to protect CI and other sensitive unclassified information and execution of military operations performed or supported by the contractor in support of the mission. Protection of CI will include the adherence to and execution of countermeasures which the contractor initiates or as provided by the DSCA Security Office, for CI on or related to the PWS.

g. At contract termination all government information, badges, and equipment must be returned to the government at the government’s discretion.

Insider Threat:

The contractor must comply with the Insider Threat Program (ITP) requirements identified 32 Code of Federal Regulation Part 117, National Industrial Security Program Operating Manual (NISPOM), also known as the “NISPOM rule.” This program will prevent espionage, violent acts against the Nation, or the unauthorized disclosure of classified information and controlled unclassified information; deter cleared employees from becoming insider threats; detect employees who pose a risk to classified information systems; and mitigate the risks to the security of classified information through administrative, investigative, or other responses. The ITP will meet or exceed the minimum standards for such programs, as defined in § 117.7 (d) of the NISPOM rule with additional guidance provided in Industrial Security Letter (ISL) 2016-02 and Defense Counterintelligence and Security Agency (DCSA) Assessment and Authorization Process Manual (DAAPM) under the NISPOM rule.

PART 2
2.DEFINITIONS AND ACRONYMS:
PART 3
3.GOVERNMENT FURNISHED ITEMS AND SERVICES:
PART 4
4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:
PART 5
6.APPLICABLE PUBLICATIONS:
PART 7
TECHNICAL EXHIBIT 1
PERFORMANCE REQUIREMENTS SUMMARY
Performance Requirements Summary (PRS)

File details come from the government source that posted it. Updated .