HT001420R0001 Amendment.pdf

HT001420R0001

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose for this Amendment is as follow s;

1. To add DFARS 252.204-7012 (Dec 2019) Safeguarding Covered Defense Information and Cyber Incident Reporting.

2. To update Question(s) Submission Deadline in Addendum 52.212-1 from 24 February 2020 to 03 March 2020.

See Summary of Changes

1. CONTRACT ID CODE PAGE OF PAGES

1 77

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 21-Feb-2020

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HT001420R0001

X 9B. DATED (SEE ITEM 11)

13-Feb-2020

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 2 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

19-Feb-2020

CODE

DHA CONTRACTING OFFICE-(NCR-CD) HT0014

8111 GATEHOUSE ROAD

2ND FLOOR

FALLS CHURCH VA 22042

HT0014 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been added by full text:

252.204-7012 SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT

REPORTING (DEC 2019)

(a) Definitions. As used in this clause--

Adequate security means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information.

Compromise means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred.

Contractor attributional/proprietary information means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company.

Controlled technical information means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination.

Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions.

Covered contractor information system means an unclassified information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.

Covered defense information means unclassified controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry at http://www.archives.gov/cui/registry/category-list.html, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies, and is--

(1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or

(2) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract.

Cyber incident means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein.

Forensic analysis means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data.

Information system means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information.

http://www.archives.gov/cui/registry/category-list.html

Malicious software means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware.

Media means physical devices or writing surfaces including, but is not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which covered defense information is recorded, stored, or printed within a covered contractor information system.

Operationally critical support means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.

Rapidly report means within 72 hours of discovery of any cyber incident.

Technical information means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013, Rights in Technical Data--Noncommercial Items, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.

(b) Adequate security. The Contractor shall provide adequate security on all covered contractor information systems.

To provide adequate security, the Contractor shall implement, at a minimum, the following information security protections:

(1) For covered contractor information systems that are part of an information technology (IT) service or system operated on behalf of the Government, the following security requirements apply:

(i) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract.

(ii) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract.

(2) For covered contractor information systems that are not part of an IT service or system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1) of this clause, the following security requirements apply:

(i) Except as provided in paragraph (b)(2)(ii) of this clause, the covered contractor information system shall be subject to the security requirements in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations” (available via the internet at http://dx.doi.org/10.6028/NIST.SP.800-171) in effect at the time the solicitation is issued or as authorized by the Contracting Officer.

(ii)(A) The Contractor shall implement NIST SP 800-171, as soon as practical, but not later than December 31, 2017. For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award.

(B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO. The Contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be nonapplicable or to have an alternative, but equally effective, security measure that may be implemented in its place.

http://dx.doi.org/10.6028/NIST.SP.800-171 mailto:osd.dibcsia@mail.mil

(C) If the DoD CIO has previously adjudicated the contractor's requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the Contracting Officer when requesting its recognition under this contract.

(D) If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information in performance of this contract, the Contractor shall require and ensure that the cloud service provider meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline (https://www.fedramp.gov/resources/documents/) and that the cloud service provider complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection, access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment.

(3) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraphs (b)(1) and (2) of this clause, may be required to provide adequate security in a dynamic environment or to accommodate special circumstances (e.g., medical devices) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability. These measures may be addressed in a system security plan.

(c) Cyber incident reporting requirement.

(1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor's ability to perform the requirements of the contract that are designated as operationally critical support and identified in the contract, the Contractor shall--

(i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor's network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor's ability to provide operationally critical support; and

(ii) Rapidly report cyber incidents to DoD at https://dibnet.dod.mil.

(2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at https://dibnet.dod.mil.

(3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see https://public.cyber.mil/eca/.

(d) Malicious software. When the Contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DoD Cyber Crime Center (DC3) in accordance with instructions provided by DC3 or the Contracting Officer. Do not send the malicious software to the Contracting Officer.

(e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.

(f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the Contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis.

https://www.fedramp.gov/resources/documents/ http://dibnet.dod.mil/ http://dibnet.dod.mil/ https://public.cyber.mil/eca/

(g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.

(h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released.

(i) Use and release of contractor attributional/proprietary information not created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD--

(1) To entities with missions that may be affected by such information;

(2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents;

(3) To Government entities that conduct counterintelligence or law enforcement investigations;

(4) For national security purposes, including cyber situational awareness and defense purposes (including with Defense Industrial Base (DIB) participants in the program at 32 CFR part 236); or

(5) To a support services contractor (“recipient”) that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information.

(j) Use and release of contractor attributional/proprietary information created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government purpose or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government's use and release of such information.

(k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data.

(l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor's responsibility for other safeguarding or cyber incident reporting pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements.

(m) Subcontracts. The Contractor shall--

(1) Include this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve covered defense information, including subcontracts for commercial items, without alteration, except to identify the parties. The Contractor shall determine if the information required for subcontractor performance retains its identity as covered defense information and will require protection under this clause, and, if necessary, consult with the Contracting Officer; and

(2) Require subcontractors to--

(i) Notify the prime Contractor (or next higher-tier subcontractor) when submitting a request to vary from a NIST SP 800-171 security requirement to the Contracting Officer, in accordance with paragraph (b)(2)(ii)(B) of this clause; and

(ii) Provide the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable, when reporting a cyber incident to DoD as required in paragraph (c) of this clause.

(End of clause)

The following have been modified:

ADDENDUM 52.212-1

Addenda to FAR 52.212-1 Instructions to Offerors

(a) Paragraph 52.212-1(c), “Period for Acceptance of Offers,” “The offeror agrees to hold the prices in its proposal firm for 180 calendar days from the issuance date of this solicitation.”

(b) All instances of “offeror,” and/or “offer” in 52.212-1 refer to Table A for holder submitting a proposal in response to this solicitation.

(c) 52.212-1(e) - Single Offer. Respondents shall submit one proposal presenting terms and conditions for commercial items/services satisfying the requirements of this solicitation. In the event a respondent submits more than one proposal, only the last complete proposal submitted prior to the due date and time for proposals will be evaluated.

(d) 52.212-1(g) - Award. The Government intends to evaluate proposals and select the awardee without communication between the Government and respondents. Therefore, the respondent’s initial proposal should contain the respondent’s best terms from a price and technical standpoint. However, the Government reserves the right to seek information through clarifications or communications with respondents, or hold discussions if later determined by the Contracting Officer to be in the interest of the Government. The Government may reject any or all proposals if such action is in the public interest; accept other than the lowest proposal; and waive informalities and minor irregularities in proposals received.

(e) 52.212-1(1) - Explanation of the Basis for Award. Unsuccessful respondents to the solicitation who request information will receive a debriefing of the award decision in accordance with FAR 16.505(b)(6)(ii).

(f) The following is inserted as new paragraph (m) of the provision:

“(m) Proposal Preparation Instructions.

A. To assure timely and equitable evaluation of proposals, offerors must follow the instructions contained herein.

Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors. The response shall consist of four (4) separate parts; Part I – Summary of Information and Proposal Table of Contents, Part II –Price Proposal, Part III – Compensation Part IV-Past Performance.

B. Specific Instructions:

1. PART I – SUMMARY AND MISCELLANEOUS DATA. Limited to no more than 10 pages overall.

Submit original electronic copy.

(a) The offeror shall provide a concise summary of contents of the entire proposal.

(b) Standard Form (SF) 1449. Complete blocks 12, 17a, 30a, 30b, and 30c. In doing so, the offeror accedes to the terms and conditions as written in the solicitation.

(c) Complete the necessary fill-ins and certifications in provisions and in the on-line Representations and Certifications at www.sam.gov. For other provisions and clauses in the solicitation, the offeror is required to submit the pages that require an offeror fill-in.

(d) Submit an acknowledgment of the all solicitation amendments, if issued.

2. PART II – PRICE SUBMISSION - Limited to no more than 7 pages. Submit original electronic copy.

(a) Insert proposed unit prices in the Price Matrix (attachment 1) for each labor category, including all option periods. Do not enter dollar amounts on the SF 1449.

2. PART II – COMPENSATION SUBMISSION - Limited to no more than 7 pages. Submit original electronic copy.

(c) Insert base labor rate in the Labor Category Minimum Compensation Matrix (attachment 2). If your proposed base hourly rate, for a given labor category at a given location is below the hourly rate identified in the Labor Category Minimum Compensation Matrix, offeror shall provide a justification showing evidence of why proposed compensation to workers is adequate to obtain and retain qualified workers.

4. PART IV– PAST PERFORMANCE SUBMISSION - Limited to no more than 5 past performance references.

(a) Quality and Satisfaction Rating of Contracts: Information currently available (letters, metrics, customer surveys, independent surveys, etc.) that demonstrates customer satisfaction with overall job performance and/or quality of completed and/or ongoing contracts. In addition, explain corrective actions taken in the past, if any, for substandard performance and any current performance problems, such as cost overruns, extended performance periods, numerous warranty calls, etc. (See 52.212-2(d)(4))

(b) Performance Surveys/Questionnaires: Past Performance Questionnaires (PPQs) shall be used by the offeror in obtaining and providing past performance information.

PPQs shall be submitted to the Government as part of offeror’s past performance submission response, and will not count towards the overall page count of this part.

(c) Past Performance Information: Provide a list of no more than five (5) contracts performed for any customer. (See addendum to 52.212-2, paragraph (d)(4)). A completed, if available, PPQ should be submitted to the Government for each reference.

Furnish the following information for each contract listed:

a) Company/Division name

b) Product/Service

c) Contracting Agency/Customer

d) Contract Number

e) Contract Dollar Value

f) Labor categories (including brief description of labor category) and number of workers per labor category

g) Period of Performance

h) Verified, up-to-date name, mailing and e-mail addresses, and telephone number of the contracting officer (Point-of-Contact)

i) Comments regarding compliance with contract terms and conditions

j) Comments regarding any known performance deemed unacceptable to the customer, or not in accordance with the contract terms and conditions.

k) Include rationale supporting your assertion of relevance and identify aspects (scope, magnitude of effort, and complexity) of the contracts deemed relevant and how they relate to the submitted effort.

If an offeror has no past performance history of relevance, the offeror must state affirmatively it possesses no past performance history of relevance.

(d) If a teaming arrangement is contemplated, provide complete information as to the arrangement.

(e) Subcontractor Consent: Past performance information pertaining to a subcontractor cannot be disclosed to the prime offeror without the subcontractor’s consent. Provide with the submission a letter from each subcontractor that will perform major or critical aspects of the requirement, consenting to the release of its past performance information to the prime contractor.

C. Documents submitted in response to this RFP must be consistent with the following:

1.Requirements of the solicitation (CLINs and PWS) and government standards and regulations pertaining to the

PWS.

2. FAR 52.212-2, Evaluation – Commercial Items, of this solicitation.

3. If part of a submission exceeds the specified page limit cited in Table A below, excess pages will NOT be evaluated.

(a) Each Part of the submission shall be separately labeled and clearly identified. Each Part shall contain a Table of Contents and a list of Tables and Drawings (if applicable). Cover pages and Table of Contents will not be counted against the page limits. However, pages depicting tables, charts, graphs and figures will count toward the page limit.

(b) The submissions will be printable on 8 1/2” x 11” paper.

(c) A page is defined as one face of a sheet of paper containing information (when printed).

(d) Page margins shall be a minimum of 1 inch top, bottom, and each side. The font shall be Times New Roman at a font size no smaller than 12.

(e) The proposal shall be submitted in a format readable by Microsoft Office 2010 which includes software programs such as WORD, EXCEL, or PowerPoint or in Adobe Acrobat Portable Document Files (.pdf).

The electronic version shall be submitted, and only accepted, via E-mail. USB flash drives, Compact Disk (CD and/or DVD), floppy disks, and zip disks are not acceptable. Individual files are not to exceed

5 MB.

(f) Each Part shall be complete in itself and shall not reference information contained in other Parts. Page 1 of a Part is defined as the first page after the Table of Contents. All pages shall be numbered.

(g) Price data of any kind shall be presented only in the Price Submission Part.

(h) Elaborate formats, bindings, and color presentations are not desired or required.

TABLE A - The following table summarizes the proposal submission:

PART TITLE ELECTRONIC

COPY

PAPER

COPY

PAGE LIMIT DUE DATE

I Summary and Misc Data (File Name: Part I)

Original Copy Only Not Accepted

10 Pages Refer to Block 8 of Page 1 of the SF

II

Price (File Name: Part II)

Electronic Copy EXCEL File

Not Accepted

7 Pages (page limit does not apply to price matrix or compensation matrix)

Refer to Block 8 of Page 1 of the SF

III

Compensation (File Name: Part III)

Electronic Copy EXCEL File

Not Accepted 7 Pages (page limit does not apply to price matrix or compensation matrix)

Refer to Block 8 of

IV

Past Performance (File Name: Part III)

Original Copy Only Not Accepted

15 Pages (page limit does not apply to PPQs or subcontractor consent)

Refer to Block 8 of

D. General Information:

1. Information regarding submission of Proposals: Proposals must be delivered to the following E-mail addresses:

Conracting Officer - Carlos Sikaffy - carlos.s.sikaffy.civ@mail.mil;

Contract Specialist - Phil York – Phillip.w.york2.civ@mail.mil;

Contract Specialist - Rhonda Cato – Rhonda.r.cato.civ@mail.mil.

2. Questions: Questions should be submitted no later than 4:00 p.m. (Eastern Standard Time) on 03 March 2020.

Answers will be published after that date as an update to the original RFP. Any questions received after this date/time need not be answered by the Government.

Answers will not be provided directly to companies, firms, or individuals.

3. FEDERAL HOLIDAYS: The following Federal Legal Holidays are observed by this base:

New Year’s Day 1 January Birthday of Martin Luther King Third Monday in January Washington’s Birthday Third Monday in February Memorial Day Last Monday in May Independence Day 4 July Labor Day First Monday in September Columbus Day Second Monday in October Veterans Day 11 November Thanksgiving Day Fourth Thursday in November Christmas Day 25 December

(End of Addenda)

PWS

PART 1

1.0 GENERAL INFORMATION

1.1 This is a non-personal services contract to provide comprehensive Information Management and Information Technology (IM/IT) Support Services to the Department of Defense (DoD) and Defense Health Agency (DHA) mailto:carlos.s.sikaffy.civ@mail.mil mailto:Phillip.w.york2.civ@mail.mil

Joint Medical Facilities and other components within the national Capital Area (NCA) and National Capital Region (NCR) – primarily for the Walter Reed National Military Medical Center (WRNMMC). The NCA/NCR has an immediate need for comprehensive technical and function IM/IT support, and associated project management support in the execution of its mission. This initiative will provide support to both existing and ongoing, but also emerging, NCA/NCR program requirements. Specific areas of coverage range include, but are not limited to, Application and Web Development, Clinical Informatics, Clinical/Business Systems, Data Center Operations, End User Devices, Information Assurance, IT Help Desk, IT Management and Transformation, Network Operations, Project and Program Management, Telecommunications, and Video Teleconferencing Support. All work will be performed within the Continental United States (CONUS).

1.2 Description of services/introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform IT related support services as defined in this Performance Work Statement (PWS) except for those items specified as government furnished property and services. The contractor shall perform to the standards in this PWS.

1.3 Background: WRNMMC leads military medicine through outstanding patient-centered care, innovation, and excellence in education and research. WRNMMC’s top priority is to care for the Wounded Warriors, Active Duty and Veterans. WRNMMC maintains around-the-clock casualty care to restore the health and well-being of those they treat. Its mission is to ensure maximum operation readiness of our country’s uniformed serves; delivery quality, customer-focused, primary and tertiary medical care; provide distinguished undergraduate and graduate medical education, professional education, and research; and develop and export innovations in healthcare services and clinical informatics throughout the nation.

WRNMMC maintains a vision to serve as America’s academic health center and the global leader. It is the world’s largest military hospital of its kind, located on 243 acres and with more than 2.4 million square feet of clinical spaces, providing care to over a million beneficiaries per year in the Washington, D.C. area, across the country and around the globe in over 100 clinics and specialties. WRNMMC serves approximately nine primary care clinics, seven occupational health clinics and dental treatment facilities, three Navy Health Clinics, four outpatient pharmacy services, six base housing/lodging halls and other remote users spanning five thousand square miles and covering five states. In addition, WRNMMC serves as the point of presence for many tenant commands located on and beyond its Bethesda campus. The remote sites and tenant commands include:

• Primary Care Clinics − Naval Surface Warfare Center, Dahlgren, VA − Naval Weapons Station Earle, Colts Neck, NJ − Naval Air Engineering Station, Lakehurst, NJ − Naval Support Activity Mechanicsburg, PA − Naval Air Facility (NAF) Andrews Air Force Base, Washington, D.C.

− Washington Navy Yard, Washington, D.C.

− Naval Security Group Activity, Sugar Grove, WV − Arlington Annex DiLorenzo Tri-care Health Clinic, Washington, D.C.

− Pentagon Tri-service Dental Clinic, Pentagon, Washington, D.C.

• Occupational Health Clinics − Carderock, West Bethesda, MD − Naval Research Lab, Washington, D.C.

− Philadelphia Naval Business Center (PNBC), Philadelphia, PA − Uniformed Services University of Health Sciences, Bethesda, MD − Anacostia, Washington, D.C.

− Indian Head, MD − Carderock, MD

• Naval Health Facilities − Annapolis, MD − Patuxent River, MD − Quantico, VA

• WRNMMC Bethesda Outpatient Pharmacy Services − Arrowhead Pharmacy

− America Pharmacy − Walter Reed Bethesda Satellite Pharmacy at the Navy Exchange − Drive-thru Refill Pickup

• WRNMMC Bethesda Base Housing, Lodging & Accommodations − Tranquility Hall − Mercy Hall − Comfort Hall − Solace Hall − Fisher House − Executive Houses (Quarters)

Point of presence is provided for the following tenant commands on Naval Support Activity (NSA) Bethesda:

Bureau of Medicine and Surgery (BUMED), Medical Inspector General (MED IG), Uniformed Services University of the Health Services (USUHS), Defense Health Agency (DHA) National Capital Region (NCR), Navy Medicine Information Systems Support Activity (NAVMISSA), Armed Forced Radiobiology Research Institute (AFRRI), Armed Services Blood Bank (ASBP), Navy Blood-borne Infection Management Center (NBIMC), Naval Dosimetry Center (NDC), Navy Medical Research Center (NMRC), Navy Medicine Professional Development Center (NMPDC), Army Education Services (AES), Navy College, Personnel Support Detachment (PSD), Naval Support Activity (NSA) Bethesda, HRO-Washington (HRO-W), Naval Criminal Investigation Service (NCIS), Naval Medical Logistics Command (NMLC), Navy Medicine Manpower, Personnel, Training and Education Command (NM MPT&E), Department of Defense (DoD), Deployment Health Clinical Center (DHCC) of the Defense Centers of Excellence (DCoE), Visual Information Directorate, Fleet & Family Support Center Services, Child Development Center (CDC) at WRNMMC, Bethesda Naval Bowling Center Administration Office Bethesda, American Red Cross at Bethesda, Navy/Marine Corps Relief Society, and any other tenant commands based at WRNMMC Bethesda that may require IT service and support.

Support is also to be provided in the following areas:

• JTF CapMed remote sites including DiLorenzo, Armed Forces Retirement Home, Dalecarlia, etc.

• JTF CapMed, Integrated Referral Management and Appointing Center (IRMAC), Bethesda, MD

• The National Intrepid Center of Excellence (NICoE), the newest component center of the Defense

Centers of Excellence (DCoE) for Psychological Health (PH) and Traumatic Brain Injury (TBI)

• Base and WRNMMC Bethesda hospital renovations and new construction initiatives

In addition to WRNMMC and its supported facilities as listed above, IMIT support may also be required at Fort Belvoir Community Hospital (FBCH) located in Fort Belvoir, VA. FBCH is a joint-service healthcare network hospital providing world-class medical care to the nation's wounded, active-duty service members, retirees and family members. As a result of the Base Realignment and Closure recommendations released by the DoD in 2005, the decision was made to consolidate and realign medical infrastructure, staff and resources in the NCR to form the new WRNMMC in Bethesda, MD and, newly construct FBCH as a state-of-the-art medical facility. Designed to increase inpatient and outpatient care needs, FBCH began serving patients in August of 2011 on its 1.2 million square foot facilities, which includes 120 modern inpatient rooms, ICU and operating rooms, four ambulatory clinical centers, seven-story inpatient tower, cancer care center, and a full range of primary care, medical, and surgical subspecialty centers. Together with WRNMMC, FBCH forms a significant part of NCR’s medical sphere.

1.4 Objectives: The objective of this contract is to procure support services via the use of task orders issued under the basic contract that will cover all types of IM/IT functions for the NCA/NCR (activities defined above). The contractor is required to maintain an up-to-date awareness of DoD, Navy and Army policies, procedures, regulations and laws pertaining to the IT field and keep current with emerging technologies. The contractor shall provide on-call support for each of the following major areas of focus. The details of the required support for each area will be provided in the associated task orders:

IT Support Services

• Task Area 1: Application and Web Development Support Services

• Task Area 2: Data Center Operations Support Services

• Task Area 3: IT Help Desk End User Device Support Services

• Task Area 4: Information Assurance Support Services

• Task Area 5: Network Operations Support Services

• Task Area 6: Telecommunications Support Services

• Task Area 7: Interagency Support

Information Management Clinical

• Task Area 8: Clinical Informatics Support Services

Information Business Operations

• Task Area 9: Information Business Operations

The contractor shall perform work and submit deliverables pursuant to each individual task order. Each task order will identify the specific work to be performed and the deliverables that are due. This is a Level of Effort Indefinite Delivery Indefinite Quantity (IDIQ), single award task order contract (SATOC) with Firm Fixed Price (FFP) task orders.

1.5 Scope: This initiative will provide support to both existing and ongoing, but also emerging, NCA/NCR program requirements. Specific areas of coverage range include, but are not limited to, Application and Web Development, Clinical Informatics, Clinical/Business Systems, Data Center Operations, End User Devices, Information Assurance, IT Help Desk, IT Management and Transformation, Network Operations, Project and Program Management, Telecommunications, and Video Teleconferencing Support. All work will be performed within the Continental United States (CONUS). Services include the IM/IT tasks listed in both Sections 1.4 and 5.0 of this PWS.

1.6 Period of Performance: The Period of Performance (PoP) for the IDIQ contract will include one (1) Base Period of twelve (12) months and four (1) twelve-month Option Periods. All work must be scheduled and completed within this period.

Task Area 1: Application and Web Development Support Services

Base Period: 01AUG 2020 – 30 SEP 2020 Option Period 1: 01 OCT 2020 – 30 SEP 2021 Option Period 2: 01 OCT 2021 – 30 SEP 2022

Task Area 2: Data Center Operations Support Services Base Period: 01 AUG 2020 – 30 SEP 2020 Option Period 1: 01 OCT 2020 – 30 SEP 2021 Option Period 2: 01 OCT 2021 – 30 SEP 2022

Task Area 3: IT Help Desk End User Device Support Services Base Period: 01 AUG 2020 – 30 SEP 2020 Option Period 1: 01 OCT 2020 – 30 SEP 2021 Option Period 2: 01 OCT 2021 – 30 SEP 2022

Task Area 4: Information Assurance Support Services Base Period: 01 AUG 2020 – 30 SEP 2020 Option Period 1: 01 OCT 2020 – 30 SEP 2021 Option Period 2: 01 OCT 2021 – 30 SEP 2022

Task Area 5: Network Operations Support Services Base Period: 01 AUG 2020 – 30 SEP 2020 Option Period 1: 01 OCT 2020 – 30 SEP 2021 Option Period 2: 01 OCT 2021 – 30 SEP 2022

Task Area 6: Telecommunications Support Services Base Period: 01 AUG 2020 – 30 SEP 2020 Option Period 1: 01 OCT 2020 – 30 SEP 2021 Option Period 2: 01 OCT 2021 – 30 SEP 2022

Task Area 7: Interagency Support Base Period: 01 AUG 2020 – 30 SEP 2020 Option Period 1: 01 OCT 2020 – 30 SEP 2021 Option Period 2: 01 OCT 2021 – 30 SEP 2022

Task Area 8: Task Area 8: Clinical Informatics Support Services

Base Period: 01 AUG 2020 – 30 SEP 2020 Option Period 1: 01 OCT 2020 – 30 SEP 2021 Option Period 2: 01 OCT 2021 – 30 SEP 2022

Task Area 9: Information Business Operations Base Period: 01 AUG 2020 – 30 SEP 2020 Option Period 1: 01 OCT 2020 – 30 SEP 2021 Option Period 2: 01 OCT 2021 – 30 SEP 2022

1.6.1 Transition-In/Transition-Out Period

The Contractor shall submit a Transition Plan for transition-in and transition-out of their proposed services with their proposal response.

1.6.1.1 Transition-in period. The period between the award date and full performance start date constitutes the transition-in period. The transition-in period is estimated to be 60 calendar days. Full performance start date is anticipated to be 01 JUL 2020. Transition-in performance is defined as the actions required to prepare and align resources to ensure there is no gap or disruption in services and operations for the customer when a contract change occurs. The goal of transition-in is to ensure contractor services will be fully delivered on the identified performance start date. Transition-in performance may include activities such as staff hiring, incumbent capture, resource review, security processing, staff training, program office standup, systems standup, and preparation of program plans, documentation, and other templates. Transition-in performance criteria includes the following:

− Complete on-boarding of all key personnel within 14 days after contract award (DACA) and No Later Than (NLT) full performance start date

− Fill 90% of all non-key personnel positions by 30 DACA and NLT full performance start date − Fill all contract positions within 60 DACA and NLT full performance start date

During the transition-in period, the contractor shall prepare to meet all contract requirements and ensure incoming personnel are functionally trained and qualified on the full performance start date. Any remaining incoming personnel shall be trained and qualified within 14 days. The Government will make all facilities, equipment, and materials accessible to the contractor during the transition-in period.

1.6.1.2 Transition-out period. The transition-out plan shall facilitate the accomplishment of a seamless transition from the incumbent to an incoming contractor/Government personnel at the expiration of the contract. The contractor shall provide a draft transition-out plan within six months of the end of the contract or option period if the next option is not to be renewed by the Government.

1.7 Administrative specifications

1.7.1 Place of performance: The work shall be performed at primarily:

Walter Reed National Military Medical Center 4655 Taylor Road Bethesda, MD 20889-5600

Alternate worksites may include any of the associated components of the NCA/NCR identified within PWS 1.3 or identified as part of the NCA/NCR organizational structuring.

1.7.2 Recognized Federal holidays: The Contractor is not required to perform services on the holidays listed below, except in accordance with the terms included herein for emergency incident response:

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

1.7.3 Hours of operation: The contractor is responsible for conducting business 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. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons.

1.7.3.1 Core Business Hours:

WRNMMC core business hours are Monday-Friday 0600 to 1800 (6:00 am – 6:00 pm). The specific time block represents the numerous customers serviced by WRNMMC. These hours are provided to assist the Contractor in determining work schedule. Normal operating hours for each requirement’s physical location will be confirmed with the assigned COR once the TO is issued. Contractor shall remain onsite during normal business hours.

1.7.3.2 Hours outside of normal operating hours:

Tasks may require work to be accomplished outside of normal operating hours. For example, fiscal year-end workload and migration of services. The Contractor must coordinate to minimize service impacts on WRNMMC customers. The Contractor shall coordinate with the COR to ensure site accessibility and work may not be scheduled for the weekend without the COR’s official concurrence.

1.7.3.3 Teleworking:

Teleworking may be authorized for certain projects. COR concurrence must be approved before telework is authorized and telework must be in accordance with WRNMMC policies.

1.7.4 Emergency Services: On occasion, services may be required to support an activation or exercise of contingency plans outside other normal duty hours.

1.7.5 Conduct: Contractor personnel shall adhere to standards of conduct as established by the DHA Commander.

The Contractor shall re-perform or resubmit, at no additional cost to the government, any activity, software product or deliverable that is determined to be insufficient to meet the requirements.

The Contractor shall adhere to published guidelines regarding appropriate dress, using proper phone etiquette, and showing respect to others in the workplace while on site and while communicating with stakeholders.

The Contractor shall ensure that the work products are professional in nature without typographical and grammatical errors. They shall also ensure that documents are formatted according to WRNMMC standards and best business practices.

Contractor PM shall be accessible and responsive to requests, emails, phone calls, and other communications within one business day of communication.

1.8 Contractor Travel

Travel for this effort is task order dependent. Any travel within a 50 miles radius of primary reporting place shall not be considered TDY. The task order-level PWS will contain the location of the work site(s) to allow the contractor to project and schedule travel. The contractor shall project and schedule travel as part of the task order firm-fixed price.

Government-directed travel that is un-projected or un-scheduled will be handled as a task order modification.

Allowable travel costs, as an element of the price, shall follow the requirements of FAR 31.205-46. All travel shall be approved in writing by the COR in advance of any costs being incurred by the Contractor.

1.9 Security Requirements

1.9.1 Security Clearance: Contractor personnel performing work under this contract must have, at minimum, active Interim DoD Secret/Confidential Clearance Eligibility (Revised Federal Investigative Standards (FIS) Tier 3 (T3) prior to beginning any work on this requirement and must maintain this level of security for the duration of their tenure on this contract. Contractor must have, at minimum, a SECRET Facility Clearance at time of proposal submission, and shall maintain the level of security required for the life of the contract. The security requirements are in accordance with the attached DD254. Please see Part 6 Information Technology & Security for more information.

1.9.2 Security Qualifications: All contractor and associated subcontractor employees working Cybersecurity (Information Assurance (IA))/Cyberspace functions must comply with DoD training requirements in Department of Defense Directive (DoDD) 8140.01, and DoD 8570.01-M. All contractor staff shall have acquired the baseline certification for their position level prior to the beginning of their contract support and shall maintain the active certification for the duration of their performance on the contract.

1.9.3 Physical Security: The contractor shall provide physical security for all material, equipment, data and information handled during contract performance, in accordance with AR 190-13, The Army Physical Security Program, AR 190-51, Security of Unclassified Army Property (Sensitive and Non-sensitive), and command policies, procedures and regulations.

1.9.3.1 Key control: The Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE:

All references to keys include key cards. No keys issued to the Contractor by the Government shall be duplicated.

The Contractor shall develop procedures covering key control that shall be included in the QCP. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the CO.

1.9.3.1.1 In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the CO, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying.