PCSE-24-00023-PWS-Grants Operations-4-2-2024_BM-final version.docx
DOCX document 127 KB Posted
- Attached to
- CISA Grants Operations Support Services
- Solicitation number
- PCSE-24-00023
About this file
This document is a Performance Work Statement (PWS) for a federal contract opportunity to provide Grants Operations Support Services to the Department of Homeland Security (DHS) Cybersecurity and Infrastructure Security Agency (CISA).
The PWS outlines the scope, objectives, and specific tasks required under this contract, which include strategy formulation, policy development, performance and project management, and technical support for CISA's Stakeholder Engagement Division (SED) to execute the State and Local Cybersecurity Grant Program and Tribal Cybersecurity Grant Program. Key tasks include contract management, leadership group support, operations section support, analysis section support, and communications support. The contract has a one-year base period with three one-year option periods. The primary place of performance is CISA facilities in the National Capital Region, with some telework permitted. The government will provide facilities, equipment, and supplies, while the contractor shall furnish all other necessary resources. Proposal submission and award details are not included in this document.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Sources Sought Notice SED-Grant Operations Support Services.docx | DOCX document |
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
DEPARTMENT OF HOMELAND SECURITY (DHS)
CYBERSECURITY AND INFRASTRUCTURE SECURITY AGENCY (CISA)
Performance Work Statement (PWS) For Grants Operations Support
1.0 GENERAL
1.1 BACKGROUND
CISA’s mission is to lead the national effort to protect and enhance the resilience of the nation’s physical and cyber infrastructure. CISA includes the CISA Mission Enabling Offices (MEOs) and six Divisions: the Cybersecurity Division (CSD), the Emergency Communications Division (ECD), the Integrated Operations Division (IOD), Infrastructure Security Division (ISD), the Stakeholder Engagement Division (SED), as well as, the National Risk Management Center (NRMC), which are headquartered with the National Capital Region (NCR).
The Cybersecurity and Infrastructure Security Agency (CISA) leads the national effort to understand, manage, and reduce risk to our cyber and physical infrastructure. We connect our stakeholders in industry and U.S. government to each other and to resources, analyses, and tools to help them build their own cyber, communications, and physical security and resilience, in turn helping to ensure a secure and resilient infrastructure for the American people. CISA’s Stakeholder Engagement Division (SED) develops partnerships, facilitates dialogue, convenes stakeholders, and promotes awareness to help CISA achieve a secure and resilient infrastructure for the American people.
Strategic Relations (SR) manages a national awareness program and related campaigns as well as national association partnerships, academic partnerships, and stakeholder analytics giving voice to diverse state, local, Tribal, and territorial (SLTT) stakeholder groups. The Grant Operations Branch within SR is tasked with the management of the State and Local Cybersecurity Grant Program and Tribal Cybersecurity Grant Program, a $1B, 4 year, first of its kind dedicated cybersecurity grant for SLTT partners.
1.2 SCOPE
The Contractor shall assist the Government with strategy formulation, policy development, performance and project management, and technical support that SED requires to successfully execute the State, Local and Tribal Cybersecurity Grant Programs. The Contractor shall provide the cybersecurity and stakeholder expertise; support the execution of grant program; provide the administrative, analysis, and communication support to the Grants Operations Program Office. This support is programmatic and analytic in nature and does not include financial management of grant awards.
1.3 OBJECTIVE
The objective of this action is to complete the tasking described in Section II of this Performance Work Statement (PWS).
1.4 APPLICABLE DOCUMENTS
1.4.1 Compliance Documents
The following documents provide specifications, standards, or guidelines that must be complied with in order to meet the requirements of this contract:
· N/A
1.4.2 Reference Documents
The following documents may be helpful to the Contractor in performing the work described in this document:
Knowledge of various authorities and frameworks such as the Federal Advisory Committee Act, Homeland Security Act of 2002, Presidential Policy Directive (PPD) 21 “Critical Infrastructure Security and Resilience,” 2013 National Infrastructure Protection Plan, PPD-41 “United States Cyber Incident Coordination,” National Cyber Incident Response Plan; Cybersecurity Act 2015, Cybersecurity and Infrastructure Security Agency Act of 2018, and Presidential Executive Orders (EO) that mandate some of the program activities and tasks such as EO 13636, EO 13800, EO 12382, and EO 13691.
· CISA's 2023 ~ 2025 Strategic Plan
· CISA Cybersecurity Strategic Plan FY2024-2026
· CISA's Information Technology Transition Memo (Jan 13th, 2023)
· CISANet Strategy
· CISA Enterprise Conceptual Data Model V 1.1
· Other documents/artifacts such as SED Mission Statement, Policies, Memos, and Guidance to provide an overview of works.
· Notice of Funding Opportunity (NOFO) announcements for the State and Local Cybersecurity Grant Program (SLCGP) and the Tribal Cybersecurity Grant Program (TCGP)
· H.R.3684 - Infrastructure Investment and Jobs Act/Bipartisan Infrastructure Law
1.5 PERFORMANCE REQUIREMENTS SUMMARY.
This contract includes a Performance Requirements Summary (PRS) at PWS 11.0. The PRS plays an integral role in the administration of the contract. In addition to any applicable inspection clauses or other related terms and conditions contained in the contract, the PRS shall serve as a primary tool for inspection and acceptance of services as facilitated by the Contracting Officer’s Representative (COR). Evaluation of the Contractor’s overall performance shall be in accordance with the performance standards set forth in the PRS, and will be conducted by the COR. The PRS constitutes a material aspect of the contract and will not be changed or otherwise modified without prior written approval of the Contracting Officer.
2.0 SPECIFIC REQUIREMENTS/TASKS
The Contractor shall provide the resources necessary to accomplish the tasks as described in this PWS.
2.1 TASK ONE - CONTRACT MANAGEMENT
This task support requires a Favorable DHS Fitness Determination (Public Trust).
The contractor shall manage the contract process by maintaining cost control, schedule, and quality of all services and products. The contractor shall determine the project organization and overall management required. The Contractor shall provide productivity and management tools to include monthly status reports and quarterly program reviews.
2.1.2 Project Management Plan
The contractor shall provide a draft Project Management Plan (PMP) during Post Award Conference for Government review. The Contractor shall provide a final PMP to the COR no later than thirty (30) business days post award. The contractor shall deliver an updated PMP upon request from the Government.
The PMP shall include the following:
· Contract work breakdown structure (WBS), an organizational chart identifying relationships, authorities, and responsibilities
· Description of the management controls that the contractor shall employ to meet the performance, cost, and schedule requirements
· Other areas the contractor deems relevant and important to the management of the tasking The contractor shall establish common processes across tasks for system-wide, cross-task activities such as: risk management, subcontractor management, and quality assurance via a PMP.
The contactor shall deliver updates when re-planning any activities. The contractor shall ensure the PMP is maintained as necessary to ensure the PMP is up to date.
2.1.3 Monthly Status Reports
The Project Manager shall provide a monthly status report to the CO and COR via electronic mail.
The contractor is required to participate in a monthly Program Management Review (PMR) meeting for the contract. In addition to the monthly PMR meeting for this contract, the contractor shall prepare and deliver a Monthly Status Report (MSR) to the COR and CO for the entire contract. This report shall include: (1) a summary of all project milestones and their anticipated completion dates, (2) data on cumulative funding and expenditure rates and status, (3) invoicing data, (4) an assessment of current month and future month activities, and (5) a discussion of any issues or recommendations related to contract performance or administration. In addition, the MSR typically contains, but is not limited to, the following information:
· the contractor’s staffing roster to include attrition rates;
· the previous month’s progress;
· deviance from previous month’s planned progress (either positive or negative);
· the current month’s planned progress;
· issues and recommendations;
· status of the procurement plan;
· summary of items anticipated for purchase in the next month with estimated costs;
· schedule performance (schedule variance);
· estimated costs versus actual costs (cost variance); and
· program risks, updates to the risk registry, risk mitigation plans, and risk mitigation actions taken.
The MSR shall also include a monthly Financial Status Report (FSR). The FSR shall include all recurring and non-recurring costs, cumulative cost, total labor hours, and cumulative labor hours for each Performance Work Statement (PWS) task and WBS element for the previous month.
Additionally, the contractor shall deliver additional financial and management reports upon request from the Government.
The MSR shall be delivered to the Government by the 15th of the following month.
2.1.4 Staffing
The contractor shall designate and provide, as key personnel, and the program manager (PM) who shall be responsible for the performance of the work and provide overall direction to contractor personnel working under this contract. The name and resume of this person and of an alternate(s), who shall act for the PM when they are unavailable, shall be designated in writing to the Contracting Officer (CO) for approval prior to the contract start date.
The contractor shall ensure that its staff and subcontractors maintain any generally required professional certifications, accreditations, and proficiency relative to their areas of expertise. The contractor shall retain documentation of such records. The Government will not pay expenses to meet this requirement. On-site seating may be limited due to space constraints.
The contractor shall ensure that the key personnel proposed by the contractor in the performance of the contract shall be accessible by the government on a full-time basis. Prior to removing, replacing, or diverting any of the specified individuals, the contractor shall notify the CO and COR The Contractor shall coordinate the replacement of key personnel with the COR/CO.
The government retains the right, at its discretion, to reject any proposed replacements of key personnel.
The contractor shall submit a staffing plan that addresses staffing requirements to perform the work on the contract and includes a plan for staffing multiple tasks and, at a minimum, the following information:
· Labor category descriptions/qualifications proposed;
· Proposed approach for staffing multiple tasks;
The staffing plan shall be updated for each Monthly Status Report.
2.2 TASK TWO. Leadership Group Support
This task support requires a Favorable DHS Fitness Determination (Public Trust).
· Assist the federal program lead in overall program execution, ensuring all milestones are met and program risks are managed.
· Assist the program lead with keeping senior CISA leadership updated, coordinate with senior DHS Federal Emergency Management Agency (FEMA) officials, and represent the agency externally.
· Ensure all support billets are filled with qualified personnel.
2.3 TASK THREE. Operations Section Support
This task support requires a Favorable DHS Fitness Determination (Public Trust).
· Support the execution of State/Local and Tribal Cybersecurity Grant Programs
· Assist in cybersecurity program guidance and documentation production, to include production of Notice of Funding Opportunities and all associated appendices, technical subject matter expertise reviews of applications, entity wide cybersecurity plans, and individual cybersecurity project plans, and other activities associated with managing the process up to the award phase. All documents and supporting materials must be prepared in a timely manner with little or no corrections.
· Support cybersecurity program coordination with other government agencies such as FEMA to represent CISA interests and determine and identify potential problem areas to leadership. Key on significant events for special attention.
· Support CISA coordination with CISA leadership and other divisions and MEOs with the same level of detail as above.
· Support promotion of CISA products and services to guide better investment of grant resources as a means to support needs in the field and better utilize scarce CISA resources.
· Provide cybersecurity expertise to the GMO and draft guidance documents to properly reflect the application of technology and processes, messaging is consistent with best practices, and specificity is maximized.
· Provide stakeholder expertise to the operations section as per the following:
· Provide consultation and engagement expertise in a timely and accurate manner, supporting the cybersecurity program objectives.
· Develop training material and other resources to field personnel (Regional staff) in a clear and concise manner.
· Provide training materials and interface with Cybersecurity Advisors/Cybersecurity Coordinators field personnel (CSAs/CSCs) and grant recipients as necessary to correctly answer questions and eliminate confusion or expand their knowledge on Notices of Funding Opportunities and their appendices.
· Provide timely and accurate administrative support to the operations section such as drafts, mock-ups, final documents, and other inputs to briefing and awareness materials.
2.4 TASK FOUR. Analysis Section Support
This task support requires a Favorable DHS Fitness Determination (Public Trust).
· Support the evaluation of the program through established evaluation criteria contained in the evaluation plan in order to determine cybersecurity program outcomes and evaluate and improve the program effectiveness, as directed.
· Maintain accurate and current data repositories, spreadsheets, and data bases as necessary.
· Recall data from repositories to determine new and existing trends, anomalies, and gaps so that the information may be presented to audiences that can enhance the effectiveness of the program.
· Conduct site visits with FEMA personnel to determine the use and effectiveness of resources so that overall improvements to the cybersecurity program can be instituted.
· Work closely with subject matter experts to adapt tools for effective and accurate electronic extraction of data from free text in .pdf, Word (.docx), Excel (.xlsx) or other similar formats.
· Prepare reports, analytics, and other input for congressional and leadership documents and briefings that present concise and actionable information.
2.5 TASK FIVE. Communications Section Support
This task support requires a Favorable DHS Fitness Determination (Public Trust).
· Prepare external correspondence for the division, agency, and department leadership according to direction for the leadership group.
· Build and maintain briefing materials, fact sheets, frequently asked questions, and talking points so that they are current and in an easy-to-retrieve posture at all times.
· Support maintainence of the programs’s web presence, prepare social media messaging, and support strategic communications efforts to ensure communications to users is current, accurate, and understandable.
2.6 TASK SIX - Analysis and Metrics Work Support (Optional) to start after 7/1/2026
This task support requires a Favorable DHS Fitness Determination (Public Trust).
The contractor shall use specialized program evaluation expertise to design, implement, and collect data (when applicable), conduct analysis, and report on one or more program evaluations to assess implementation, outcomes, and effectiveness of SLCGP.
For evaluation, the contractor will support to either develop the evaluation question(s) and initial concept details or update any provided by the Government.
The Contractor shall prepare a draft and final evaluation design report. The Government will review the draft report and provide comments to be incorporated into the final version; the Government will review and approve the final version. The evaluation design report shall include, but may not be limited to, the following elements:
· Project Plan covering key tasks and milestones, responsible parties, and timeline
· Summary of background research, including a list of all sources consulted
· Explanation of final evaluation question(s) the study will address
· Description and explanation of methodology for the evaluation
· Analysis strategy
· Data sources to be used and how they will support the methodology and analysis strategy
· Data Collection Planning package (See also 2.2 Task Two: Data Collection)
· Quality assurance plan
· Identification of potential risks or limitations related to the evaluation design and identified mitigation strategies
The Contractor shall conduct a final presentation for the Government to review and discuss the final evaluation design.
2.7 TASK SEVEN - Transition Support (OPTIONAL)
This task support requires the same level of clearance as PWS 2.1 – 2.6.
In the event that responsibility for fulfillment of the tasks described in this PWS, either in whole or in part, is transferred to a new contractor or the government, the contractor shall participate in transition meetings with the program manager, project staff, and representatives of the successor Contractor and/or government personnel. The purpose of these meetings is to review project materials and take preparatory steps to ensure an effective transition in contractor support.
As requested, the contractor shall develop, document and monitor the execution of a transition-out plan that may be used to transition related tasks and materials described in this PWS to a new contractor, or to the government. The plan shall incorporate an inventory of all services and materials required to fully perform the contract requirements. The plan shall include a schedule of briefings, including dates, times, and resources allotted, that will be required to fully transition all materials developed to the follow-on contractor, and shall provide the names of individuals that will be responsible for fully briefing their follow-on counterparts. The plan is to ensure that the follow-on contractor, or the government, will be provided sufficient information and be fully briefed prior to the current expiration date of the contract, to provide adequate time for the new contractor to have their personnel completely familiar with the requirements and in place on the turnover date. The contractor shall plan for up to a 90-day transition period. The plan shall provide the contact information for contractor individuals who will be assigned to the transition team and identify their roles in the transition.
2.8 TASK EIGHT - Surge Support (OPTIONAL)
This task is optional and may be exercised partially. The task is not required to be fully exercised when additional support is required.
The surge requirements will remain the same as tasks 2.1 through 2.7, to include the clearance requirements.
The dynamic nature of various programs and/or sections including additional programs, sections, or task forces incorporated to prevent cyber-attacks against America’s critical infrastructure under SED may require additional resources. This optional Surge support is for the Government to request additional services to complete tasks in this PWS during any period of performance under this task order. Surge efforts will be awarded on a Not to Exceed Labor Hour basis. The Government will define the work to be performed, working hours, labor categories, deliverables and duration of assignment in writing prior to authorizing performance. The Government may authorize a ceiling price for additional work in support of mission support services. The contractor shall only be authorized to work to the amount funded for the Surge CLIN.
3.0 CONTRACTOR PERSONNEL
3.1 Qualified Personnel
The Contractor shall provide qualified personnel to perform all requirements specified in this PWS.
3.2 Continuity of Support
The Contractor shall ensure that the contractually required level of support for this requirement is maintained at all times. The Contractor shall ensure that all contract support personnel are present for all hours of the workday. If for any reason the Contractor staffing levels are not maintained due to vacation, leave, appointments, etc., and replacement personnel will not be provided, the Contractor shall provide e-mail notification to the Contracting Officer’s Representative (COR) prior to employee absence. Otherwise, the Contractor shall provide a fully qualified replacement.
3.3 Key Personnel
Before replacing any individual designated as Key by the Government, the Contractor shall notify the Contracting Officer no less than 15 business days in advance, submit written justification for replacement, and provide the name and qualifications of any proposed substitute(s). All proposed substitutes shall possess qualifications equal to or superior to those of the Key person being replaced, unless otherwise approved by the Contracting Officer. The Contractor shall not replace Key Contractor personnel without approval from the Contracting Officer. The following Contractor personnel are designated as Key for this requirement. Note: The Government may designate additional Contractor personnel as Key at the time of award.
· Program Manager (PM/SME)
3.3.1 Contractor Key personnel shall not be assigned by the Contractor to more than one key position for this requirement.
3.4 Subject Matter Expert (SME) Program Manager
The Contractor shall provide a Program Manager who shall be responsible for all Contractor work performed under this PWS. It is anticipated a senior level Program Manager shall be provided by the Contractor for this work effort. The Program Manager shall provide subject matter expertise, program management, program analysis and reporting, documentation, and/or strategic planning and overall management as required to support to the SED Mission Support Services task order. The Program Manager shall be a single point of contact for the Contracting Officer and the COR. The Program Manager is further designated as Key by the Government. During any absence of the Program Manager, only one alternate subject matter expert shall have full authority to act for the Contractor on all matters relating to work performed under this contract. The Program Manager and all designated alternates shall be able to read, write, speak and understand English. Additionally, the Contractor shall not replace the Program Manager without prior approval from the Contracting Officer.
The Program Manager shall be available to the COR via telephone between the hours of 0830 and 1700 EST, Monday through Friday, and shall respond to a request for discussion or resolution of technical problems within 4 hours of notification.
The Contractor shall provide a Program Manager to include the following:
· Must have at least 10 years of experience and a MA/MS degree.
· Must be able to provide strategic advice, technical guidance and expertise to program and project staff; provide detailed analysis, evaluation and recommendations for improvements, optimization development, and/or maintenance efforts for client-specific or mission critical challenges/issues; provide timely budgetary forecasting and spend information upon Government request; consult with client to define need or problem; supervise studies and leads surveys to collect and analyze data to provide advice and recommend solutions.
The name of the Program Manager, and the name(s) of any alternate(s) who shall act for the Contractor in the absence of the Program Manager, shall be provided to the Government as part of the Contractor's proposal.
3.5 Employee Identification
3.5.1 Contractor employees visiting Government facilities shall wear an identification badge that, at a minimum, displays the Contractor name, the employee’s photo, name, clearance-level and badge expiration date. Visiting Contractor employees shall comply with all Government escort rules and requirements. All Contractor employees shall identify themselves as Contractors when their status is not readily apparent and display all identification and visitor badges in plain view above the waist at all times.
3.5.2 Contractor employees working on-site at Government facilities shall wear a Government issued identification badge. All Contractor employees shall identify themselves as Contractors when their status is not readily apparent (in meetings, when answering Government telephones, in e-mail messages, etc.) and display the Government issued badge in plain view above the waist at all times.
3.6 Employee Conduct
Contractor’s employees shall comply with all applicable Government regulations, policies and procedures (e.g., fire, safety, sanitation, environmental protection, security, “off limits” areas, wearing of parts of DHS uniforms, and possession of weapons) when visiting or working at Government facilities. The Contractor shall ensure Contractor employees present a professional appearance at all times and that their conduct shall not reflect discredit on the United States or the Department of Homeland Security. The Project Manager shall ensure Contractor employees understand and abide by Department of Homeland Security established rules, regulations and policies concerning safety and security.
3.7 Removing Employees for Misconduct or Security Reasons
The Government may, at its sole discretion (via the Contracting Officer), direct the Contractor to remove any Contractor employee from DHS facilities for misconduct or security reasons. Removal does not relieve the Contractor of the responsibility to continue providing the services required under the contract. The Contracting Officer will provide the Contractor with a written explanation to support any request to remove an employee.
4.0 OTHER APPLICABLE CONDITIONS
FAR CLAUSE 52.204.2 Security Requirements.
4.1 SECURITY
The contractor staff working under this requirement will only require DHS Suitability or Public Trust.
Sensitive Information is defined in the DHS Instruction Handbook, 121-01-007, “The Department of Homeland Security, Personnel Security, Suitability and Fitness Program” as “Any information, the loss, misuse, disclosure, unauthorized access to, or modification of, which could adversely affect the national or homeland security interest, the conduct of Federal programs, or the privacy to which individuals are entitled under section 552a of Title 5, United States Code (the Privacy Act), but which has not been specifically authorized under criteria by an Executive Order or an Act of Congress to be kept secret in the interests of national defense, homeland security, or foreign policy. This definition includes one of the following categories of information:
A. Protected Critical Infrastructure Information (PCII) as described in the Critical Infrastructure Information Act of 2002, 6 U.S.C. section 21 1-224; its implementing regulations, 6 C.F.R. Part 29; or the applicable PCII Procedures Manual; or
B. Sensitive Security Information (SSI), as described in 49 C.F.R. Part 1520; or
C. Sensitive but Unclassified Information (SBU) -For Official Use Only -, which consists of any other information which:
(1 ) If provided by the government to the contractor, is marked in such a way to place a reasonable person on notice of its sensitive nature;
(2) Is designated "sensitive" in accordance with subsequently adopted homeland security information handling requirements.”
Contractor access to classified information may be required under this PWS. The details will be provided in a Department of Defense (DD) Form 254.
POST-AWARD INSTRUCTIONS REGARDING SECURITY REQUIREMENTS FOR CONTRACTS/ORDERS
1. The procedures outlined below shall be followed for the DHS Office of the Chief Security Officer (OCSO), Personnel Security Division (PSD) to process background investigations, Entry on Duty determinations, and Fitness determinations, as required, in a timely and efficient manner.
2. Carefully read the security clauses in the contract. Compliance with the security clauses in the contract is not optional.
3. Contractor employees (to include applicants, temporaries, part-time and replacement employees) under the contract, requiring access to sensitive information, shall undergo a position-sensitivity analysis based on the duties each individual will perform on the contract. The results of the position sensitivity analysis shall identify the appropriate background investigation to be conducted. All background investigations will be processed through the DHS OCSO/PSD. Prospective contractor employees shall submit the below completed forms to the DHS OCSO/PSD. The Standard Form (SF) 85-P must be completed electronically through the Office of Personnel Management’s e-QIP SYSTEM. The SF-85P signature pages and other completed forms must be given to the OSCO/PSD no less than thirty (30) days before the start date of the contract or thirty (30) days prior to the requested entry on duty date, for all contractor employees whether a replacement, addition, subcontractor employee, or vendor:
· Standard Form (SF) 85-P, ―Questionnaire for Public Trust Positions‖
· SF-85P Certification
· SF-85P Authorization for Release of Information
· FD Form 258, ―Fingerprint Card (2 copies)
· DHS Form 11000-6 ―Conditional Access To Sensitive But Unclassified Information Non-Disclosure Agreement
· DHS Form 11000-9, ―Disclosure and Authorization Pertaining to Consumer Reports Pursuant to the Fair Credit Reporting Act
4. Only complete packages will be accepted by the DHS OCSO/PSD. Specific instructions on submission of packages will be provided upon award of the contract.
5. The DHS OCSO/PSD may, as it deems appropriate, authorize and grant a favorable Entry on Duty (EOD) decision based on preliminary checks. A favorable EOD decision allows a contractor employee to commence work temporarily prior to the completion of the full background investigation. The granting of a favorable EOD decision shall not be considered as assurance that a favorable Fitness determination will follow. In addition, a favorable EOD or Fitness determination shall in no way prevent, preclude, or bar DHS from withdrawing or terminating access to government facilities or information, at any time during the term of the contract. No employee of the Contractor shall be allowed unescorted access to a Government facility without a favorable EOD or Fitness determination by the DHS OCSO/PSD.
6. Limited access to Government buildings is allowable without an EOD decision if the Contractor is escorted by a Government employee and the purpose of the visit is to attend a limited number of required briefings or nonrecurring meetings in order to facilitate the transition of a contract The intent of this statement is to allow a minimum amount of meeting / transition attendances to prepare for the new contract.
7. The DHS OCSO/PSD shall be notified of all terminations/resignations within five (5) days of occurrence. The Contractor shall return to the Contracting Officer’s Representative (COR) all DHS issued identification cards and building passes that have either expired or have been collected from terminated employees. If an identification card or building pass is not available to be returned, a report shall be submitted to the COR, referencing the pass or card number, name of individual to whom it was issued and the last known location and disposition of the pass or card.
4.2 PERIOD OF PERFORMANCE
The period of performance for this contract is a one-year base period with three one-year option periods as follows:
| Base Period | August 31, 2024 - August 30, 2025 | |
| Option Period One | August 31, 2025 - August 30, 2026 | |
| Option Period Two | August 31, 2026 - August 30, 2027 | |
| Option Period Three | August 31, 2027 - August 30, 2028 |
4.3 PLACE OF PERFORMANCE
The primary place of performance will be a combination of CISA Facilities at 4200 Wilson Boulevard, Arlington, Virginia, and Teleworking at Contractor’s Personal Residences within the Local Washington Commuting Area (i.e., National Capital Region).
4.4 CONTRACTOR TELECOMMUTING – REMOTE PERSONAL RESIDENCE WORK LOCATIONS.
Telecommuting for federal government contractors will be considered on a situational basis to the extent practicable to meet DHS mission needs. Telecommuting allows contractor personnel to perform their contractual requirements outside of CISA office locations, typically at a contractor’s personal residence or a corporate telecommuting office location. Telecommuting for contractor personnel provides the government flexibility to meet unique CISA organizational and facility needs and requirements. The goal of telecommuting for contractor personnel is to enhance the delivery of services that support the DHS mission. Telecommuting is permitted under this contract in accordance with the requirements below.
All work performed outside of the identified contractor and / or government facility (s) will be performed at the Unclassified FOUO level and ensuring access to personnel who are authorized access.
Additionally, the provision to permit contractor telecommuting may be revoked at any time if the Government makes such determination. The telecommuting provision does not change any contract requirements; all other terms and conditions of the contact remain in full force and effect.
4.5 CONTRACTOR LABOR RATES CHARGED WHILE TELECOMMUTING
The contractor shall charge the same applicable fixed hourly rate as for a Government site for those contractor personnel when they telecommute at their designated telecommuting location.
4.4 HOURS OF OPERATION
Contractor employees shall generally perform all work between the hours of 0800 and 1700 EST, Monday through Friday (except Federal holidays). However, there may be occasions when Contractor employees shall be required to work other than normal business hours, including weekends and holidays, to fulfill requirements under this PWS.
4.6 TRAVEL
Contractor travel may be required to support this requirement. All travel required by the Government outside the local commuting area(s) will be reimbursed to the Contractor in accordance with the Federal Travel Regulations. The Contractor shall be responsible for obtaining COR approval (electronic mail is acceptable) for all reimbursable travel in advance of each travel event.
4.7 POST AWARD CONFERENCE
The Contractor shall attend a Post Award Conference with the Contracting Officer and the COR no later than 10 business days after the date of award. The purpose of the Post Award Conference, which will be chaired by the Contracting Officer, is to discuss technical and contracting objectives of this contract and review the Contractor's draft project plan. The Post Award Conference will be held at the Government’s facility, located at 4200 Wilson Blvd, Arlington, Va 22201 or via teleconference.
4.8 PROJECT PLAN
The Contractor shall provide a draft Project Plan at the Post Award Conference for Government review and comment. The Contractor shall provide a final Project Plan to the COR not later than 10 business days after the Post Award Conference.
4.9 BUSINESS CONTINUITY PLAN
The Contractor shall prepare and submit a Business Continuity Plan (BCP) to the Government. The BCP Plan shall be due 15 business days after the date of award and will be updated on an annual basis. The BCP shall document Contractor plans and procedures to maintain support during an emergency, including natural disasters and acts of terrorism. The BCP, at a minimum, shall include the following: A list of primary and alternate Contractor points of contact, each with primary and alternate:
· Telephone numbers
· E-mail addresses
4.9.1 Individual BCPs shall be activated immediately after determining that an emergency has occurred, shall be operational within 24 hours of activation or as directed by the Government, and shall be sustainable until the emergency situation is resolved and normal conditions are restored or the contract is terminated, whichever comes first. In case of a life-threatening emergency, the COR shall immediately make contact with the Contractor Project Manager to ascertain the status of any Contractor personnel who were located in Government controlled space affected by the emergency. When any disruption of normal, daily operations occurs the Contractor Program Manager and the COR shall promptly open an effective means of communication and verify:
• Key points of contact (Government and contractor)
• Temporary work locations (alternate office spaces, telework, virtual offices, etc.)
• Means of communication available under the circumstances (e.g., email, webmail, telephone, FAX, courier, etc.)
• Essential Contractor work products expected to be continued, by priority
4.9.2 The Government and Contractor Program Manager shall make use of the resources and tools available to continue contracted functions to the maximum extent possible under emergency circumstances. Contractors shall obtain approval from the Contracting Officer prior to incurring costs over and above those allowed for under the terms of this contract. Regardless of contract type, and of work location, Contractors performing work in support of authorized tasks within the scope of their contract shall charge those hours accurately in accordance with the terms of this contract.
4.10 PROGRESS REPORTS
The Program Manager shall provide a monthly progress report to the Contracting Officer and COR via electronic mail by the 15th of each month. This report shall include a summary of all Contractor work performed, including a breakdown of labor hours by labor category, all direct costs by line item, an assessment of technical progress, schedule status, any travel conducted and any Contractor concerns or recommendations for the previous reporting period.
4.11 PROGRESS MEETINGS
The Program Manager shall be available to meet with the COR upon request to present deliverables, discuss progress, exchange information and resolve emergent technical problems and issues. These meetings shall take place via phone or in person at 4200 Wilson Boulevard, Arlington, Virginia.
4.12 GENERAL REPORT REQUIREMENTS
The Contractor shall provide all written reports in electronic format with read/write capability using applications that are compatible with DHS workstations (Windows XP and Microsoft Office Applications).
4.13 INTELLECTUAL PROPERTY
All Contractor developed processes and procedures and other forms of intellectual property developed during this contract shall be Government property. All documentation and electronic data and information collected by the Contractor and generated in support of this contract shall be Government property and shall be returned to the Government at the end of the performance period or when specified in the contract.
4.14 PROTECTION OF INFORMATION
The Government will provide all necessary information, data and documents to the Contractor for work required under this contract.
The Contractor shall use Government furnished information, data and documents only for the performance of work under this contract and shall be responsible for returning all Government furnished information, data and documents to the Government at the end of the performance period. The Contractor shall not release Government furnished information, data and documents to outside parties without the prior and explicit consent of the Contracting Officer.
Contractor access to proprietary information is required under this PWS. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with DHS MD 11042.1, Safeguarding Sensitive but Unclassified (For Official Use Only) Information. The Contractor shall ensure that all Contractor personnel having access to business or procurement sensitive information sign a non-disclosure agreement (DHS Form 11000-6).
4.15 OTHER DIRECT COST
Other direct cost purchases may be required to attend conferences, meetings, briefings, and training and make emergency purchases as approved by the COR or his/her designee(s) to accomplish assigned tasks.
5.0 GOVERNMENT TERMS & DEFINITIONS
| ACRONYM |
| DEFINITION |
| CCC |
| Coordination Control Center |
| CI |
| Critical Infrastructure |
| CISA |
| Cybersecurity and Infrastructure Security Agency |
| CIKR |
| Critical Infrastructure and Key Resources |
| CIPAC |
| Critical Infrastructure Partnership Advisory Council |
| CO |
| Contracting Officer |
| COR |
| Contracting Officer’s Representative |
| COS |
| Chief of Staff |
| DHS |
| Department of Homeland Security |
| ESF |
| Enduring Security Framework |
| FACA |
| Federal Advisory Committee Act |
| FSLC |
| Federal Senior Leadership Council |
| FSR |
| Financial Status Reports |
| MSR |
| Monthly Status Reports |
| NIAC |
| National Infrastructure Advisory Council |
| NICE |
| National Initiative for Cybersecurity Education |
| NIPP |
| National Infrastructure Protection Plan |
| NIST |
| National Institute for Standards and Technology |
| NSIE |
| Network Security Information Exchange |
| NSTAC |
| National Security Telecommunication Advisory Committee |
| OMB |
| Office of Management and Budget |
| PPD |
| Presidential Policy Directive |
| PMP |
| Project Management Plan |
| PWD |
| Workforce Development Program |
| RC3 |
| Regional Consortiums Coordinating Council |
| SED |
| Stakeholder Engagement Division |
6.0 GOVERNMENT FURNISHED RESOURCES
The Government will provide the workspace, equipment and supplies necessary to perform the on-site portion of Contractor services required in this contract, unless specifically stated otherwise in this work statement.
6.1 Property Inventory
Contractor/Servicing Agency must establish and maintain an accurate master inventory of all property purchase for CISA under this Contract.
6.2 Monthly Asset Management Report
Contractor/Servicing Agency will ensure personnel prepare a monthly Asset Management Report, which contains accurate information for all CISA property located at their facility. At a minimum, this report must include:
· DHS Barcode
· Acquisition Date
· Acquisition Status
· Asset Condition
· Manufacturer Name
· Manufacturer Model
· Asset Description
· Serial Number
· Asset Cost
· Location
7.0 CONTRACTOR FURNISHED PROPERTY
The Contractor shall furnish all facilities, materials, equipment and services necessary to fulfill the requirements of this contract, except for the Government Furnished Resources specified in PWS 2.0 and PWS 6.0.
7.1 Property Inventory
The Contractor/Servicing Agency will ensure personnel apply a DHS-supplied barcode to all property purchased for CISA. Contractor/Servicing Agency must establish and maintain an accurate master inventory of all property purchase for CISA under this Contract.
7.2 Notification of Property Receipt
Contractor/Servicing Agency will confirm receipt of CISA property purchased under this PWS with the assigned CISA Accountable Property Officer (APO) and COR within 5 business days of receipt.
APO Name & Contact Information
7.3 Monthly Asset Management Report
Contractor/Servicing Agency will prepare a monthly Asset Management Report, which contains accurate information for all CISA property located at their facility. At a minimum, this report must include:
· DHS Barcode
· Acquisition Date
· Acquisition Status
· Asset Condition
· Manufacturer Name
· Manufacturer Model
· Asset Description
· Serial Number
· Asset Cost
· Location
7.4 Invoice/Receipts
Contractor/Servicing Agency will ensure copies of all invoices/packing slips/receipts for property purchased for CISA accompanies the Monthly Asset Management Report.
8.0 INVOICES AND PAYMENT PROVISIONS
Invoices shall be prepared per Section VII, Contract Clauses; Paragraph A. entitled “FAR CLAUSES INCORPORATED BY REFERENCE,” FAR Clause 52.232-25 Prompt Payment, and FAR Clause 52.232-7, Payments under Time and Materials and Labor-Hours. In addition to invoice preparation as required by the FAR, the Contractor’s invoice shall include the following information:
1) Cover sheet identifying DHS;
2) Contract Number;
3) Modification Number, if any;
4) DUNS Number;
5) Month services provided
6) CLIN and Accounting Classifications
7) Contract Line Item Number (CLIN) and description for each billed item.
8) Any additional backup information as required by this contract.
9) ATTN: CISA/OUS
The contractor shall submit invoices monthly. The Contractor shall submit the invoice electronically to the address below:
E-mail: CISAInvoice.Consolidation@ice.dhs.gov
Simultaneously the Contractor shall provide an electronic copy of the invoice to the following individuals at the addresses below:
E-mail: Contract Officer Contract Specialist- COR: Vandai Luong – vandai.luong@cisa.dhs.gov ACOR: Susan Muerdler - susan.muerdler@cisa.dhs.gov
The contractor shall submit invoices to the email addresses above. Additionally, the contractor shall prepare and submit a sufficient and procurement regulatory compliant invoice and receiving report for technical certification of inspection/acceptance of services and approval for payment. The contractor shall attach back up information to the invoices and receiving reports substantiating all costs for services performed. The receiving agency’s written or electronic acceptance by the COR and date of acceptance shall be included as part of the backup documentation.
If the invoice is submitted without all required back up documentation, the invoice shall be rejected. The Government reserves the right to have all invoices and backup documentation reviewed by the Contracting Officer prior to payment approval.
9.0 GOVERNMENT ACCEPTANCE PERIOD
The COR will review deliverables prior to acceptance and provide the contractor with an e-mail that provides documented reasons for non-acceptance. If the deliverable is acceptable, the COR will send an e-mail to the Contractor notifying it that the deliverable has been accepted.
9.1 The COR will have the right to reject or require correction of any deficiencies found in the deliverables that are contrary to the information contained in the Contractor’s accepted proposal. In the event of a rejected deliverable, the Contractor will be notified in writing by the COR of the specific reasons for rejection. The Contractor may have an opportunity to correct the rejected deliverable and return it per delivery instructions.
9.2 The COR will have 3 business days to review deliverables and make comments. The Contractor shall have 1 business day to make corrections and redeliver.
9.3 All other review times and schedules for deliverables shall be agreed upon by the parties based on the final approved Project Plan. The Contractor shall be responsible for timely delivery to Government personnel in the agreed upon review chain, at each stage of the review. The Contractor shall work with personnel reviewing the deliverables to assure that the established schedule is maintained.
10.0 DELIVERABLES
The Contractor shall consider items in BOLD as having mandatory due dates. Items in italics are deliverables or events that must be reviewed and/or approved by the COR prior to proceeding to next deliverable or event in this PWS.
| ITEM |
| PWS REFERENCE |
| DELIVERABLE / EVENT |
| DUE BY |
DISTRIBUTION
| 1 |
| 2.1 |
| Post Award Conference |
| Within 10 business days of award |
N/A
| 2 |
| 2.1 |
| Monthly Status Report |
| Due the 15th of every month |
| COR, Contracting Officer |
| 3 |
| 2.1 |
| Staffing Plan |
| Included in Monthly Status Report due the 15th of every month |
| COR, Contracting Officer |
| 4 |
| 2.1, 4.8 |
| Draft Project Plan |
| Due upon the Post Award Conference |
COR, Contracting Officer
| 5 |
| 4.8 |
| Final Project Plan |
| Within 10 business days after Post Award Conference |
| COR, Contracting Officer |
| 6 |
| 4.10 |
| Progress Reports |
| Due the 15th of every month |
| COR, Contracting Officer |
| 8 |
| 4.9 |
| Business Continuity Plan |
| 15 days after contract award |
COR, PM/Task Lead
| 9 |
| 4.9 |
| Updated Business Continuity Plan |
| Annually per option period |
| COR, PM/Task Lead |
| 9 |
| 2.3 |
| Notice of Funding Opportunity |
| Complete 10-20 days after the task is issued |
| PM/Task Lead |
| 10 |
| 2.3 |
| Training Materials for CSCs/CSAs to explain NOFO requirements |
| Complete 10-20 days after the task is issued |
| PM/Task Lead |
| 11 |
| 2.4 |
| Data Repository |
| Complete 10-20 days after task is issued |
| PM/Task Lead |
| 12 |
| 2.4 |
| Site evaluation reports |
| Complete 10 days after site visit |
| PM/Task Lead |
| 13 |
| 2.4 |
| Word Parser |
| Complete 5 days after grants are submitted |
| PM/Task Lead |
| 14 |
| 2.4 |
| Analytics report |
| Complete 5 days after task is issued |
| PM/Task Lead |
| 15 |
| 2.5 |
| Briefing materials |
| Complete 3 days after task is issued |
| PM/Task Lead |
| 16 |
| 2.5 |
| Fact Sheets |
| Complete 5 days after task is issued |
| PM/Task Lead |
| 17 |
| 2.5 |
| Frequently Asked Questions Sheets |
| Complete 5 days after task is issued |
| PM/Task Lead |
| 18 |
| 2.5 |
| Talking Points |
| Complete 3 days after task is issued |
| PM/Task Lead |
| 19 |
| 2.5 |
| Web site content |
| Complete |
3 days after task is issued
PM/Task Lead
| 20 |
| 2.5 |
Social Media messaging
2 days after task is issued Requesting Agency (CISA/SED)
| 21 |
| 2.6 |
| Draft Evaluation Design Report |
| 10-15 business days after task is issued |
| Program Manager or |
Task Lead
| 22 |
| 2.6 |
| Final Evaluation Design Report |
| 5 business days after Government’s comments on draft report are returned |
| Program Manager or |
Task Lead
| 23 |
| 2.6 |
| Draft Evaluation Report Package |
| 1-6 months after Final Evaluation Design Report is approved |
| Program Manager or |
Task Lead
| 24 |
| 2.6 |
| Final Evaluation Report Package |
| 10 business days after Government’s comments on draft Evaluation Report Package are returned |
| Program Manager or |
Task Lead
| 25 |
| 2.6 |
| Final Evaluation Presentation |
| 5 business days after Final Evaluation Report Package is approved |
| Program Manager or |
Task Lead
| 26 |
| 2.6 |
| Draft Data Collection Planning Package |
| 10-20 business days after task is issued |
| Program Manager or |
Task Lead
| 27 |
| 2.6 |
| Final Data Collection Planning Package |
| 5 business days after Government’s comments on draft package are returned |
| Program Manager or |
Task Lead
| 28 |
| 2.6 |
| Draft Data Collecton Report |
| 1-6 months after Final Evaluation Design Report is approved |
| Program Manager or |
Task Lead
| 29 |
| 2.6 |
| Final Data Collection Report |
| 5 business days after Government’s comments on draft report are returned |
| Program Manager or |
Task Lead
11.0 PERFORMANCE REQUIREMENTS SUMMARY (PRS).
The PRS establishes key elements of Contractor performance that represent “mission essential” service requirements, which are identified in the table below in the “Service Output” column. The “Performance Objective” column represents the standard against which Contractor performance will be measured in relation to accomplishment of the corresponding service output. The performance objective or “standard” describes the minimum acceptable level of service by the Contractor for satisfactory performance. The “Acceptable Quality Level (AQL)” column displays the maximum allowable deviation from the performance objective, which, if exceeded, evokes the negative incentive specified in the table below.
| Service Output |
| Performance Objective |
| Method of Surveilance |
| Performance Metric/ Acceptable Quality Level (AQL) |
| Positive/Negative incentive |
| 1. Project Management Plan (PWS 2.1.2) |
| Reports / plans shall be submitted accurately and timely in accordance with the PWS |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .