N00421-19-Q-0231.docx

N0042119Q0231

Section A - Solicitation/Contract Form

SOLICITATION REQUIREMENTS

Solicitation N00421-19-Q-0231 is issued as a brand name procurement. This solicitation is reserved for small business respondents only. The Government intends to purchase on a firm fixed-price basis, and to solicit and negotiate the proposed purchase order on a brand name basis for Ivanti Certified Consultant for Professional Services, under the authority implemented by Federal Acquisition Regulation (FAR) Part 12, FAR Part 13, and FAR Part 52.219-6.

This is a firm fixed-price procurement, therefore, the offeror’s initial offer should represent the vendor’s best quote in terms of price and technical acceptability. It should identify if an alternate item or substituted item is being offered. You must quote enough technical information to evaluate your quote. Your quote will only be evaluated on the information you submit.

Award will be made to the vendor that submits the lowest, aggregate, firm fixed-price, brand name quote. If two or more quotes are equal the award shall be made by drawing of lot limited to valid quotes. The drawing shall be witnessed by 3 persons, and the contract file shall contain the names and addresses of the witnesses and the person supervising the drawing.

Please provide the following information with your response.

(1) FOB: ______________________

(2) Shipping Cost: ______________

(3) Tax ID# ____________________

(4) Dun & Bradstreet # _____________________

(5) Cage Code: _________ You must be registered in System for Award Management (Sam.Gov)

(6) Business Size: Small Business Yes or No

(7) GSA Contract # if quoting on a GSA Schedule: ________________________

(8) Estimated delivery time after issuance of purchase order ____________________

(9) Published Price list.

*YOU MUST SUBMIT SIGNED DOCUMENTATION VERIFYING YOU ARE AN AUTHORIZED DISTRIBUTOR*

Section B - Supplies or Services and Prices

Ivanti Professional Services

FFP

1>Prof Services Project Mgmt - Enterprise (SVCS-PROSVCS-PMENT)

QTY. 1

2>ProServices ITSM - Daily Rate (SVCS-ITSM)

QTY. 42

3>ProServices Project Management - Hourly (SVCS-PM)

QTY> 64

4>Professional Services Daily Expenses (SVCS-T-E)

QTY. 42

POP: Six months from DOA NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination

PURCHASE REQUEST NUMBER: 1300773674

ADDITIONAL MARKINGS: TPOC:Tammy Manahan tammy.manahan@navy.mil 301-757-9278

PSC CD: D319

NET AMT

Section C - Descriptions and Specifications

S.O.W.

Statement of Work for Ivanti Service Manager Professional Services

Background:

US Navy - NAWCAD (“Customer”) has requested the Ivant Certified Consultant (“Consultant”) to provide days of Ivanti Professional Services consultancy on a time and materials basis as defined in the following Statement of Work (“SOW”). The vendor resources assigned to this project will be under the direction of both Ivanti Project Management and the Customer Project Manager.

This engagement will focus on the design, configuration and implementation of a highly developed Service Request workflow within Customer’s Ivanti Service Manager (“ISM”) instance to replace Customer’s existing externally hosted Integrated Move Management Workflow Website.

An initial analysis of customer requirements was done by Ivanti Professional Services to determine overall feasibility of creating a functional replacement of the existing solution based on Customer provided documentation.

This solution is not intended to be a like-for-like feature replacement of Customer’s existing solution.

Consultant will implement the solution using framework, specifications, and configuration changes mutually agreed to during an interactive planning and design workshop.

Tasks:

This section describes the expected tasks planned for the Vendor engagement.

Scope:

This section describes the activities in scope for the Consultant engagement Planning and Design Workshop Project Scoping, Workshop and Design: Consultant, working with Customer personnel, will conduct a Workshop to further define Customer requirements.

Planning and Design Meeting The Planning and Design Meeting includes all the tasks required to meet with the project’s key stakeholders and determine the final design of the system prior to beginning the software implementation.

High Level work breakdown structure:

· Discussion of Objective and Strategy

· Long Term Goals and Objectives

· Data Model (Users, Groups, Customers, Filters, Partitioning, CI’s etc., Supporting DB objects, Lookup tables, data import requirements)

· Implementation Model

· Workshop Preparation

Design Document: Consultant will generate design documentation defining the specifics of configuration work to be performed as agreed to during the design workshop. The document will be used to govern implementation of Customer’s Solution

Design Review: Discuss and document the conceptual design based on specific needs and objectives, and conduct design review meeting to discuss and identify any gaps.

Request Management A Request Offering is an item that describes the item, assistance, or action available to Self Service users from the Service Catalog. Request Offerings are normally placed in logical groups of Services.

The Service Catalog lists all Request Offerings, such as requests for software, computers, or other requests for non-IT related services provided in your organization. The Service Catalog is how customers order products and services. You control the customer experience within the Service Catalog, defining for each item an image, description, price, other fields, and workflow.

Design Workshop:

Attendees: Service Desk Manager, Service Desk Analysts, Department Liaisons Discussion Items and factors of design include but are not limited to the following:

· Service Catalog – Self Service Portal

· Request Offering Specifics

· Workflow Specifications

· Location Data

· Supporting tables and Lookup data

· Population and Maintenance

· Seat count and inventory calculations

· Portal form look and feel and data validation

· Handling of “on behalf of” Requests and associated process

· Approval Workflow Process

· Task Workflow Process

· Notifications

· Status

· Roles and Security

Configure and Review Request Management and Service Catalog

· Configure Customer’s IMM request workflow using framework, specifications, and configuration changes agreed to during the design workshop and per the design document. Implementation of Custom requests of high complexity typically includes but is not limited to the following features:

· Creation of Request from Customer Portal

· Status Lifecycle

· Customer relationship configuration to the Service Request

· Priority configuration

· Create and assign Tasks fulfill the request

· Create Journals

· Add Attachments to the request

· Resolve Tasks and updating status

· Automated email template process for new request

· Automated email template process for fulfillment of request

· Automated email template process on creation of Assignment

· Request Closure Process

· Create Dashboard with View/drill for Request Process

· Configure SLA including Response and Resolution times for request

· Review and configure settings for Audit History

· Configuring Role based-access for request data and functionality

User Validation Testing The last phase of the software testing process. UVT will focus on testing Ivanti Service Manager in real world scenarios. During this phase the Customer will run through a series of tests and note any minor improvements/modifications necessary or possible misconfiguration. Issues will be logged and then adjusted by the consultant.

System Testing: Test all Configured features and functions for documented behavior. Perform empirical investigation of each feature and service to validate the state and behavior of the product against the Service Manager specification, detect any software failures, and ensure the satisfaction of Customer requirements.

Consultant will make agreed to configuration changes as required from UVT

Go-Live Support “Go live" takes place at the end phase or completion of the project. The presence of a vendor consultant/deployment engineer on site will provide the customer project team and users of the solution with extra support and a source of expertise. The following activities are included in this section:

Phase - Go-live – up to three (3) days

· Clear Test Data

· Communicate to Customers

· Provide Go-Live Support

Enterprise Plus Project Management

Project Kick-off Meeting: Conduct project kickoff meeting with Consultant and Customer staff to establish guidelines for managing and monitoring progress, establish a project management plan to include: communication and information distribution, risk monitoring and mitigation plan, change control, and quality control. A Project Information Packet will be provided to the Customer Project team. Communicate key milestones to be met on the project. A strategic phased project plan including discovery, planning, pilot and execution will be established when necessary.

Direct and Manage Project Execution: Work directly with Consultant resources to adhere to the project management plan so as to meet project objectives. Note: This is an iterative process involving ongoing review of the project management plan, change requests, and other factors to ensure that the work is being performed as directed. Additionally, this would involve working with the project team to gather, analyze, update, and store project information.

Manage Project Team: Manage project team through constant communication and observation. Manage work attitude, productivity, conflicts, interpersonal issues, and accomplishments.

Distribute Project Information: Manage the flow of information as set forth in the project management plan. Ensure that the proper information is being distributed to the right people at the right time. Update relevant project documentation as necessary.

Monitor and Control Project Activities: Regularly monitor project performance, compare to project plan and recommend necessary actions. Analyze, track and monitor risks to ensure that they are being recognized and reported, and that response plans are being executed. Maintain accurate project information and integrity. Provide information to support status reporting, progress and forecasting. Monitor and execute approved changes as they occur. Maintain project scope. Manage project schedule. Clearly communicate daily/weekly task associated with key milestones.

Manage Risk: Monitor project work for new and changing risks. Manage the execution of alternate strategies, contingency plans, or corrective action to keep the project on track.

Conduct Weekly Project Status Meetings: Conduct weekly project status meetings with Consultant and Customer team members to review progress made throughout the week, project schedule, status of new and outstanding issues, and reviewing project risks and adjust project plan as necessary. Document and distribution meeting minutes to specified stakeholders. An Executive Summary will be provided to Customer staff for reporting to staff members.

Assumptions The project will proceed with the following identified assumptions. Any further assumptions that are identified as the project progresses will be subject to a change control and an impact analysis, which may affect the cost and timescales of the project. Where these changes were not reasonably identifiable by Consultant then the Customer will bear any costs.

credentials, IP addresses, and server names to the Ivanti Certified Consultant as reasonably requested.

regarding the configuration and usage of the software.

consultant as necessary in order to enable the completion of required tasks

Customer Project Management Responsibilities Customer will designate a person to whom all Consultant communications will be addressed and who has the authority to act for Customer in all aspects of this Statement of Work (the “Customer Project Manager”).

The Customer Project Manager will:

· Create and maintain an estimated schedule for the overall project.

· Provide sufficient notice for rescheduling. Rescheduling requires minimum of ten (10) business days’ notice. Failure to notify Consultant of need to reschedule can result in additional charges as stated in services Terms and Conditions.

· Work with the Consultant Project Manager to identify resource requirements and desired skill sets. Consultant recommends a two (2) week lead time to schedule consultants and make travel arrangements when adding resources.

· Schedule resources in segments of no less than five (5) business days unless agreed to by both Consultant and Customer.

· Schedule and facilitate completion of this engagement within the respective number of months from date of signing the PO

· With Consultant, administer Change Control and authorize Project Change requests.

· Provide access to Customer facilities consistent with the estimated schedule for all resources. Consultants may require access to Customer facilities and systems outside normal business hours.

Project Progress Reporting A regular meeting or a teleconference will be scheduled to discuss the Project status; the format will be jointly agreed between the Consultant Project Manager and Customer Project Manager.

Depending on project complexity the daily status reports may include:

· General progress to plan and causes for any Project delays.

· Project Plan updates for all tasks due or started ahead of schedule (actual days worked, percentage of completion for each major task, estimated completion dates, and actual completion dates).

· Issues and action items to resolve change order control items reviewed or for review, including any tasks to be worked on that are not included in the Detailed Project Plan and any tasks that will negatively impact the allotted budget.

Delivery Schedule This SOW will deliver days of time and material consulting over a maximum period of six (6) months from the date when the Customer places the order.

For invoicing purposes, a person day is defined to be 8.00 working hours per resource. For both onsite and remote engagements billable hours will be recorded in half day or full day increments.

Note: Vendors submitting pricing are required to submit a Validation letter from Ivanti confirming the vendor's " Ivanti " Partner Reseller relationship. Letter from Ivanti confirming Authorized Reseller status is required and must be submitted with vendor's proposal to be considered and before the deadline.

Appendix A: IMM Functionality summary and related responses Customer provided the following Specification around functionality that they were either unsure of how to implement in ISM or were not possible within the ISM Portal framework. As well as Ivanti Professional Services Responses to the document

“IMM and Planned Functionality Notes”

Site Access Users with active NHDSM profile where EDIPI (passed by BigIP header) matches NHDSM profile, and where user has view of IMM Request Offering (ORG Unit based on Site) IMM website has ability to look at the “Site” in the profile and allow access to move forward. NHDSM would restrict the request offering based on a “View” ability. Someone HAS to maintain who has that view. This is an account management process in NHDSM whereas IMM website is an automated check.

Person Move

Once Person Move is selected, the drop down box allows us to select Move Existing and the site displays:

NOTE: the user guide can be located in Knowledge and easily accessible to self service

NHDSM Request Offering would be specifically for IMM, as other items like Equipment Moves would fall under the Desktop Voice request offerings. NHDSM request offerings have the same ability to ask if the request is for that end user or someone else.

If “Someone Else” is selected and that profile does not exist, IMM site is able to collect all that information and write it to the database when it writes all other data to the database for the move request. NHDSM cannot submit a request without an employee record already existing and tie it to that employee. It would only exist in the requestor’s name.

Concern: NHDSM cannot move forward in the IMM request offering if their profile doesn’t exist, end user would have to cancel that request, go to the create/update profile request offering and complete that before being able to proceed with IMM request. This is mostly an inconvenience to end users and they may complain about having to cancel, create a profile for a user, wait for that profile to have the correct view/roles, and then attempt to enter the request again.

Will have to look into how to redirect user to new profile request – through red alert text box. IMM currently does it by providing a link to create a profile. Have question open with support regarding custom error

Moving From and Moving To locations in IMM website are based upon many constraints beginning with Employee Group and then including: Employment Organization, Employment Competency, Site, Building, Floor, Room, Cube. The result is a specific Space ID. This is aligned to the resulting Cube selected and there could be more than one space for a cube selection. IMM website has floor, room and cube as either validated lists (if tenant owned building) or as free text fields (nontenant owned) while NHDSM can only have one or the other – cannot alternate validated list or free text field for the same building – must be one or the other. This would have to be a validated list in NHDSM, unsure of level of impact to end users that are non-tenant.

NHDSM has not successfully been able to apply multiple constraints. This is something that works fine within “Incident” such as detail screens, but Service Requests treat webforms differently and constraints on these webforms do not function the same. Have been working with support, they have another customer with the same issue and no ideas how to resolve at this time.

IMM is able to open FloorPlan viewer in the same window, allow a user to select a visual space and that location information and space ID are then automatically entered on the IMM website.

CONCERN: NHDSM is able to provide a hyperlink to a website that can open in a window, but nothing that occurs in that window can populate fields on the NHDSM website. Vendor had previously stated this could not be done. Reached out to vendor to determine if this could be done with custom code via professional services engagement. They stated we could request this type of functionality for a future version or PS engagement, but no timeline on the development of this type of functionality in either scenario.

IMM website validates that users existing space is tied to their profile and APM data – if what is entered is not correct, an error pops up. Unsure of the ability for NHDSM to query a table and have a pop up error to end user. Have this question open with support

IMM website calendaring allows ability to remove weekend and holidays as well as set the date no less than 10 days from current date. NHDSM will allow setting no less than # days – but does not remove weekends or holidays. Have question open with support

IMM website will perform calculation on seat count, seat occupancy from tables, but will also query all open tickets for any moves to or moves from for that space id. NHDSM can perform table lookups within the request offering, but cannot also query open requests and then combine that data and perform calculation after the query. The calculation would have to already be in a table that is loaded in the request offering. Unsure of the level of effort to perform this and maintain tables.

NHDSM does not appear to have the capability of pop up messages that allow two separate actions in Request Offerings. Have question open with support

The upcoming release of IMM includes the ability to “Seat” someone such as on-boarding. If that person is already mapped to a seat in APM, IMM will give an error and have them redirected to IMM for a Move. This is a new service that NHDSM did not have in the development pipeline – but the concern here is that NHDSM would have to have that field fed into the request as soon as it is selected, and then the workflow could perform a check on that field – NHDSM cannot query a table after a request offering is already in progress. Unsure of the time it would take to create the large table and maintenance of these tables via the DataWarehouse

There are field requirements such as “NMCI Computer Name” that indicate letters and numbers in certain positions of the field – NHDSM can specify field length and overall character/numeric requirements, but not position within the field. Have question open with support, but does not appear to be a feature at this time.

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

Section F - Deliveries or Performance

DELIVERY INFORMATION

27-SEP-2019

TAMMY MANAHAN

47762 RANCH RD BLDG 1490 RM 102

PATUXENT RIVER MD 20670

301-757-1228 FOB: Destination N00421

CLAUSES INCORPORATED BY REFERENCE

Section G - Contract Administration Data

CLAUSES INCORPORATED BY FULL TEXT

252.232-7003 ELECTRONIC SUBMISSION OF PAYMENT REQUESTS AND RECEIVING REPORTS (DEC 2018)

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

Contract financing payment means an authorized Government disbursement of monies to a contractor prior to acceptance of supplies or services by the Government.

(1) Contract financing payments include--

(i) Advance payments;

(ii) Performance-based payments;

(iii) Commercial advance and interim payments;

(iv) Progress payments based on cost under the clause at Federal Acquisition Regulation (FAR) 52.232-16, Progress Payments;

(v) Progress payments based on a percentage or stage of completion (see FAR 32.102(e)), except those made under the clause at FAR 52.232-5, Payments Under Fixed-Price Construction Contracts, or the clause at FAR 52.232-10, Payments Under Fixed-Price Architect-Engineer Contracts; and

(vi) Interim payments under a cost reimbursement contract, except for a cost reimbursement contract for services when Alternate I of the clause at FAR 52.232-25, Prompt Payment, is used.

(2) Contract financing payments do not include--

(i) Invoice payments;

(ii) Payments for partial deliveries; or

(iii) Lease and rental payments.

Electronic form means any automated system that transmits information electronically from the initiating system to affected systems.

Invoice payment means a Government disbursement of monies to a contractor under a contract or other authorization for supplies or services accepted by the Government.

(1) Invoice payments include--

(i) Payments for partial deliveries that have been accepted by the Government;

(ii) Final cost or fee payments where amounts owed have been settled between the Government and the contractor;

(iii) For purposes of subpart 32.9 only, all payments made under the clause at 52.232-5, Payments Under Fixed-Price Construction Contracts, and the clause at 52.232-10, Payments Under Fixed-Price Architect-Engineer Contracts; and

(iv) Interim payments under a cost-reimbursement contract for services when Alternate I of the clause at 52.232-25, Prompt Payment, is used.

(2) Invoice payments do not include contract financing payments.

Payment request means any request for contract financing payment or invoice payment submitted by the Contractor under this contract or task or delivery order.

Receiving report means the data prepared in the manner and to the extent required by Appendix F, Material Inspection and Receiving Report, of the Defense Federal Acquisition Regulation Supplement.

(b) Except as provided in paragraph (d) of this clause, the Contractor shall submit payment requests and receiving reports in electronic form using Wide Area WorkFlow (WAWF). The Contractor shall prepare and furnish to the Government a receiving report at the time of each delivery of supplies or services under this contract or task or delivery order.

(c) Submit payment requests and receiving reports to WAWF in one of the following electronic formats:

(1) Electronic Data Interchange.

(2) Secure File Transfer Protocol.

(3) Direct input through the WAWF website.

(d) The Contractor may submit a payment request and receiving report using methods other than WAWF only when--

(1) The Contractor has requested permission in writing to do so, and the Contracting Officer has provided instructions for a temporary alternative method of submission of payment requests and receiving reports in the contract administration data section of this contract or task or delivery order;

(2) DoD makes payment for commercial transportation services provided under a Government rate tender or a contract for transportation services using a DoD-approved electronic third party payment system or other exempted vendor payment/invoicing system (e.g., PowerTrack, Transportation Financial Management System, and Cargo and Billing System);

(3) DoD makes payment on a contract or task or delivery order for rendered health care services using the TRICARE Encounter Data System; or

(4) The Governmentwide commercial purchase card is used as the method of payment, in which case submission of only the receiving report in WAWF is required.

(e) Information regarding WAWF is available at https://wawf.eb.mil/.

(f) In addition to the requirements of this clause, the Contractor shall meet the requirements of the appropriate payment clauses in this contract when submitting payment requests.

(End of clause)

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (DEC 2018)

(a) Definitions. As used in this clause—

“Department of Defense Activity Address Code (DoDAAC)” is a six position code that uniquely identifies a unit, activity, or organization.

“Document type” means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

“Local processing office (LPO)” is the office responsible for payment certification when payment certification is done external to the entitlement system.

“Payment request” and “receiving report” are defined in the clause at 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(b) Electronic invoicing. The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation Supplement (DFARS) 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) WAWF access. To access WAWF, the Contractor shall—

(1) Have a designated electronic business point of contact in the System for Award Management at https://www.sam.gov; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this web site.

(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the “Web Based Training” link on the WAWF home page at https://wawf.eb.mil/.

(e) WAWF methods of document submission. Document submissions may be via web entry, Electronic Data Interchange, or File Transfer Protocol.

(f) WAWF payment instructions. The Contractor shall use the following information when submitting payment requests and receiving reports in WAWF for this contract or task or delivery order:

(1) Document type. The Contractor shall submit payment requests using the following document type(s): Combo

(i) For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.

(ii) For fixed price line items—

(A) That require shipment of a deliverable, submit the invoice and receiving report specified by the Contracting Officer.

COMBO_______________________________________________________

(Contracting Officer: Insert applicable invoice and receiving report document type(s) for fixed price line items that require shipment of a deliverable.)

(B) For services that do not require shipment of a deliverable, submit either the Invoice 2in1, which meets the requirements for the invoice and receiving report, or the applicable invoice and receiving report, as specified by the Contracting Officer.

SEE SECTION E____________________________________________________________

(Contracting Officer: Insert either “Invoice 2in1” or the applicable invoice and receiving report document type(s) for fixed price line items for services.)

(iii) For customary progress payments based on costs incurred, submit a progress payment request.

(iv) For performance based payments, submit a performance based payment request.

(v) For commercial item financing, submit a commercial item financing request.

(2) Fast Pay requests are only permitted when Federal Acquisition Regulation (FAR) 52.213-1 is included in the contract.

[Note: The Contractor may use a WAWF “combo” document type to create some combinations of invoice and receiving report in one step.]

(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.

Routing Data Table*

(*Contracting Officer: Insert applicable DoDAAC information. If multiple ship to/acceptance locations apply, insert “See Schedule” or “Not applicable.”) (**Contracting Officer: If the contract provides for progress payments or performance-based payments, insert the DoDAAC for the contract administration office assigned the functions under FAR 42.302(a)(13).)

(4) Payment request. The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in accordance with the payment clause, contract financing clause, or Federal Acquisition Regulation 52.216-7, Allowable Cost and Payment, as applicable.

(5) Receiving report. The Contractor shall ensure a receiving report meets the requirements of DFARS Appendix F.

(g) WAWF point of contact: tammy.manahan@navy.mil Phone: 301-757-9278

(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity’s WAWF point of contact.

james.mizelle@navy.mil ___________________________________________ (Contracting Officer: Insert applicable information or “Not applicable.”)

(2) Contact the WAWF helpdesk at 866-618-5988, if assistance is needed

Section I - Contract Clauses

CLAUSES INCORPORATED BY REFERENCE

52.204-13 SYSTEM FOR AWARD MANAGEMENT MAINTENANCE (OCT 2018)

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

Electronic Funds Transfer (EFT) indicator means a four-character suffix to the unique entity identifier. The suffix is assigned at the discretion of the commercial, nonprofit, or Government entity to establish additional System for Award Management (SAM) records for identifying alternative EFT accounts (see subpart 32.11) for the same entity.

Registered in the System for Award Management (SAM) means that--

(1) The Contractor has entered all mandatory information, including the unique entity identifier and the EFT indicator (if applicable), the Commercial and Government Entity (CAGE) code, as well as data required by the Federal Funding Accountability and Transparency Act of 2006 (see subpart 4.14), into SAM;

(2) The Contractor has completed the Core, Assertions, Representations and Certifications, and Points of Contact sections of the registration in SAM;

(3) The Government has validated all mandatory data fields, to include validation of the Taxpayer Identification Number (TIN) with the Internal Revenue Service (IRS). The Contractor will be required to provide consent for TIN validation to the Government as a part of the SAM registration process; and

(4) The Government has marked the record ``Active''.

System for Award Management (SAM) means the primary Government repository for prospective Federal awardee and Federal awardee information and the centralized Government system for certain contracting, grants, and other assistance-related processes. It includes—

(1) Data collected from prospective Federal awardees required for the conduct of business with the Government;

(2) Prospective contractor-submitted annual representations and certifications in accordance with FAR subpart 4.12; and

(3) Identification of those parties excluded from receiving Federal contracts, certain subcontracts, and certain types of Federal financial and non-financial assistance and benefits.

Unique entity identifier means a number or other identifier used to identify a specific commercial, nonprofit, or Government entity. See www.sam.gov for the designated entity for establishing unique entity identifiers.

(b) If the solicitation for this contract contained the provision 52.204-7 with its Alternate I, and the Contractor was unable to register prior to award, the Contractor shall be registered in SAM within 30 days after award or before three days prior to submission of the first invoice, whichever occurs first.

(c) The Contractor shall maintain registration in SAM during contract performance and through final payment of any contract, basic agreement, basic ordering agreement, or blanket purchasing agreement. The Contractor is responsible for the currency, accuracy and completeness of the data within SAM, and for any liability resulting from the Government's reliance on inaccurate or incomplete data. To remain registered in SAM after the initial registration, the Contractor is required to review and update on an annual basis, from the date of initial registration or subsequent updates, its information in SAM to ensure it is current, accurate and complete. Updating information in SAM does not alter the terms and conditions of this contract and is not a substitute for a properly executed contractual document.

(d)(1)(i) If a Contractor has legally changed its business name or ``doing business as'' name (whichever is shown on the contract), or has transferred the assets used in performing the contract, but has not completed the necessary requirements regarding novation and change-of-name agreements in subpart 42.12, the Contractor shall provide the responsible Contracting Officer a minimum of one business day's written notification of its intention to--

(A) Change the name in SAM;

(B) Comply with the requirements of subpart 42.12 of the FAR; and

(C) Agree in writing to the timeline and procedures specified by the responsible Contracting Officer. The Contractor shall provide with the notification sufficient documentation to support the legally changed name.

(ii) If the Contractor fails to comply with the requirements of paragraph (d)(1)(i) of this clause, or fails to perform the agreement at paragraph (d)(1)(i)(C) of this clause, and, in the absence of a properly executed novation or change-of-name agreement, the SAM information that shows the Contractor to be other than the Contractor indicated in the contract will be considered to be incorrect information within the meaning of the ``Suspension of Payment'' paragraph of the electronic funds transfer (EFT) clause of this contract.

(2) The Contractor shall not change the name or address for EFT payments or manual payments, as appropriate, in the SAM record to reflect an assignee for the purpose of assignment of claims (see FAR subpart 32.8, Assignment of Claims). Assignees shall be separately registered in SAM. Information provided to the Contractor's SAM record that indicates payments, including those made by EFT, to an ultimate recipient other than that Contractor will be considered to be incorrect information within the meaning of the ``Suspension of Payment'' paragraph of the EFT clause of this contract.

(3) The Contractor shall ensure that the unique entity identifier is maintained with the entity designated at www.sam.gov for establishment of the unique entity identifier throughout the life of the contract. The Contractor shall communicate any change to the unique entity identifier to the Contracting Officer within 30 days after the change, so an appropriate modification can be issued to update the data on the contract. A change in the unique entity identifier does not necessarily require a novation be accomplished.

(e) Contractors may obtain additional information on registration and annual confirmation requirements at https://www.sam.gov.

52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR EXECUTIVE ORDERS--COMMERCIAL ITEMS (AUG 2018)

(a) The Contractor shall comply with the following Federal Acquisition Regulation (FAR) clauses, which are incorporated in this contract by reference, to implement provisions of law or Executive orders applicable to acquisitions of commercial items:

(1) 52.203-19, Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements (JAN 2017) (section 743 of Division E, Title VII, of the Consolidated and Further Continuing Appropriations Act, 2015 (Pub. L. 113-235) and its successor provisions in subsequent appropriations acts (and as extended in continuing resolutions)).

(2) 52.204-23, Prohibition on Contracting for Hardware, Software, and Services Developed or Provided by Kaspersky Lab and Other Covered Entities (Jul 2018) (Section 1634 of Pub. L. 115-91).

(3) 52.209-10, Prohibition on Contracting with Inverted Domestic Corporations (Nov 2015).

(4) 52.233-3, Protest After Award (AUG 1996) (31 U.S.C. 3553).

(5) 52.233-4, Applicable Law for Breach of Contract Claim (OCT 2004) (Public Laws 108-77 and 108-78 (19 U.S.C. 3805 note)).

(b) The Contractor shall comply with the FAR clauses in this paragraph (b) that the Contracting Officer has indicated as being incorporated in this contract by reference to implement provisions of law or Executive orders applicable to acquisitions of commercial items: (Contracting Officer check as appropriate.)

___ (1) 52.203-6, Restrictions on Subcontractor Sales to the Government (Sept 2006), with Alternate I (Oct 1995) (41 U.S.C. 4704 and 10 U.S.C. 2402).

____ (2) 52.203-13, Contractor Code of Business Ethics and Conduct (Oct 2015) (41 U.S.C. 3509).

____ (3) 52.203-15, Whistleblower Protections under the American Recovery and Reinvestment Act of 2009 (June 2010) (Section 1553 of Pub. L. 111-5). (Applies to contracts funded by the American Recovery and Reinvestment Act of 2009.)

___ (4) 52.204-10, Reporting Executive Compensation and First-Tier Subcontract Awards (Oct 2016) (Pub. L. 109-282) (31 U.S.C. 6101 note).

___ (5) [Reserved]

___ (6) 52.204-14, Service Contract Reporting Requirements (Oct 2016) (Pub. L. 111-117, section 743 of Div. C).

___ (7) 52.204-15, Service Contract Reporting Requirements for Indefinite-Delivery Contracts (Oct 2016) (Pub. L. 111-117, section 743 of Div. C).

___ (8) 52.209-6, Protecting the Government's Interest When Subcontracting with Contractors Debarred, Suspended, or Proposed for Debarment. (Oct 2015) (31 U.S.C. 6101 note).

____ (9) 52.209-9, Updates of Publicly Available Information Regarding Responsibility Matters (July 2013) (41 U.S.C. 2313).

____ (10) [Reserved]

____ (11)(i) 52.219-3, Notice of HUBZone Set-Aside or Sole-Source Award (NOV 2011) (15 U.S.C. 657a).

____ (ii) Alternate I (NOV 2011) of 52.219-3.

____ (12) (i) 52.219-4, Notice of Price Evaluation Preference for HUBZone Small Business Concerns (OCT 2014) (if the offeror elects to waive the preference, it shall so indicate in its offer) (15 U.S.C. 657a).

____ (ii) Alternate I (JAN 2011) of 52.219-4.

____ (13) [Reserved]

____ (14)(i) 52.219-6, Notice of Total Small Business Set-Aside (NOV 2011) (15 U.S.C. 644).

____ (ii) Alternate I (NOV 2011).

____ (iii) Alternate II (NOV 2011).

____ (15)(i) 52.219-7, Notice of Partial Small Business Set-Aside (June 2003) (15 U.S.C. 644).

____ (ii) Alternate I (Oct 1995) of 52.219-7.

____ (iii) Alternate II (Mar 2004) of 52.219-7.

____ (16) 52.219-8, Utilization of Small Business Concerns (Nov 2016) (15 U.S.C. 637(d)(2) and (3)).

____ (17)(i) 52.219-9, Small Business Subcontracting Plan (Aug 2018) (15 U.S.C. 637(d)(4)).

____ (ii) Alternate I (Nov 2016) of 52.219-9.

____ (iii) Alternate II (Nov 2016) of 52.219-9.

____ (iv) Alternate III (Nov 2016) of 52.219-9.

____ (v) Alternate IV (Aug 2018) of 52.219-9.

____ (18) 52.219-13, Notice of Set-Aside of Orders (NOV 2011) (15 U.S.C. 644(r)).

____ (19) 52.219-14, Limitations on Subcontracting (JAN 2017) (15 U.S.C. 637(a)(14)).

____ (20) 52.219-16, Liquidated Damages—Subcon-tracting Plan (Jan 1999) (15 U.S.C. 637(d)(4)(F)(i)).

____ (21) 52.219-27, Notice of Service-Disabled Veteran-Owned Small Business Set-Aside (NOV 2011) (15 U.S.C. 657f).

____ (22) 52.219-28, Post Award Small Business Program Rerepresentation (July 2013) (15 U.S.C. 632(a)(2)).

____ (23) 52.219-29, Notice of Set-Aside for, or Sole Source Award to, Economically Disadvantaged Women-Owned Small Business Concerns (Dec 2015) (15 U.S.C. 637(m)).

____(24) 52.219-30, Notice of Set-Aside for, or Sole Source Award to, Women-Owned Small Business Concerns Eligible Under the Women-Owned Small Business Program (Dec 2015) (15 U.S.C. 637(m)).

(25) 52.222-3, Convict Labor (June 2003) (E.O. 11755).

(26) 52.222-19, Child Labor--Cooperation with Authorities and Remedies (Jan 2018) (E.O. 13126).

(27) 52.222-21, Prohibition of Segregated Facilities (Apr 2015).

(28)(i) 52.222-26, Equal Opportunity (SEPT 2016) (E.O. 11246).

____ (ii) Alternate I (Feb 1999) of 52.222-26.

(29)(i) 52.222-35, Equal Opportunity for Veterans (OCT 2015)(38 U.S.C. 4212).

____ (ii) Alternate I (July 2014) of 52.222-35.

(30)(i) 52.222-36, Equal Opportunity for Workers with Disabilities (JUL 2014) (29 U.S.C. 793).

____ (ii) Alternate I (July 2014) of 52.222-36.

(31) 52.222-37, Employment Reports on Veterans (FEB 2016) (38 U.S.C. 4212).

(32) 52.222-40, Notification of Employee Rights Under the National Labor Relations Act (Dec 2010) (E.O. 13496).

(33)(i) 52.222-50, Combating Trafficking in Persons (March 2, 2015) (22 U.S.C. chapter 78 and E.O. 13627).

____ (ii) Alternate I (March 2, 2015) of 52.222-50 (22 U.S.C. chapter 78 and E.O. 13627).

____ (34) 52.222-54, Employment Eligibility Verification (Oct 2015). (E. O. 12989). (Not applicable to the acquisition of commercially available off-the-shelf items or certain other types of commercial items as prescribed in 22.1803.)

____ (35)(i) 52.223-9, Estimate of Percentage of Recovered Material Content for EPA–Designated Items (May 2008) (42 U.S.C. 6962(c)(3)(A)(ii)). (Not applicable to the acquisition of commercially available off-the-shelf items.)

____ (ii) Alternate I (May 2008) of 52.223-9 (42 U.S.C. 6962(i)(2)(C)). (Not applicable to the acquisition of commercially available off-the-shelf items.)

____ (36) 52.223-11, Ozone-Depleting Substances and High Global Warming Potential Hydrofluorocarbons (June, 2016) (E.O. 13693).

____ (37) 52.223-12, Maintenance, Service, Repair, or Disposal of Refrigeration Equipment and Air Conditioners (June, 2016) (E.O. 13693).

____ (38) (i) 52.223-13, Acquisition of EPEAT® Registered Imaging Equipment (Jun 2014) (E.O.s 13423 and 13514).

____ (ii) Alternate I (OCT 2015) of 52.223-13.

____ (39)(i) 52.223-14, Acquisition of EPEAT® Registered Televisions (Jun 2014) (E.O.s 13423 and 13514).

____ (ii) Alternate I (Jun 2014) of 52.223-14.

(40) 52.223-15, Energy Efficiency in Energy-Consuming Products (Dec 2007) (42 U.S.C. 8259b).

____ (41)(i) 52.223-16, Acquisition of EPEAT[supreg]-Registered Personal Computer Products (OCT 2015) (E.O.s 13423 and 13514).

____ (ii) Alternate I (Jun 2014) of 52.223-16.

(42) 52.223-18, Encouraging Contractor Policies to Ban Text Messaging While Driving (Aug 2011) (E.O. 13513).

____ (43) 52.223-20, Aerosols (June, 2016) (E.O. 13693).

____ (44) 52.223-21, Foams (June, 2016) (E.O. 13693).

____ (45)(i) 52.224-3, Privacy Training (JAN 2017) (5 U.S.C. 552a).

____ (ii) Alternate I (JAN 2017) of 52.224-3.

(46) 52.225-1, Buy American--Supplies (May 2014) (41 U.S.C. chapter 83).

____ (47) (i) 52.225-3, Buy American--Free Trade Agreements--Israeli Trade Act (May 2014) (41 U.S.C. chapter 83, 19 U.S.C. 3301 note, 19 U.S.C. 2112 note, 19 U.S.C. 3805 note, 19 U.S.C. 4001 note, Pub. L.

103-182, 108-77, 108-78, 108-286, 108-302, 109-53, 109-169, 109-283, 110-138, 112-41, 112-42, and 112-43.

____ (ii) Alternate I (May 2014) of 52.225-3.

____ (iii) Alternate II (May 2014) of 52.225-3.

____ (iv) Alternate III (May 2014) of 52.225-3.

____ (48) 52.225-5, Trade Agreements (AUG 2018) 19 U.S.C. 2501, et seq., 19 U.S.C. 3301 note).

(49) 52.225-13, Restrictions on Certain Foreign Purchases (JUNE 2008) (E.O.'s, proclamations, and statutes administered by the Office of Foreign Assets Control of the Department of the Treasury).

____ (50) 52.225-26, Contractors Performing Private Security Functions Outside the United States (Oct 2016) (Section 862, as amended, of the National Defense Authorization Act for Fiscal Year 2008; 10 U.S.C. 2302 Note).

____ (51) 52.226-4, Notice of Disaster or Emergency Area Set-Aside (Nov 2007) (42 U.S.C. 5150

____ (52) 52.226-5, Restrictions on Subcontracting Outside Disaster or Emergency Area (Nov 2007) (42 U.S.C. 5150).

____ (53) 52.232-29, Terms for Financing of Purchases of Commercial Items (Feb 2002) (41 U.S.C. 4505, 10 U.S.C. 2307(f)).

____ (54) 52.232-30, Installment Payments for Commercial Items (Jan 2017) (41 U.S.C. 4505, 10 U.S.C. 2307(f)).

(55) 52.232-33, Payment by Electronic Funds Transfer—System for Award Management (July 2013) (31 U.S.C. 3332).

____ (56) 52.232-34, Payment by Electronic Funds Transfer—Other than System for Award Management (July 2013) (31 U.S.C. 3332).

____ (57) 52.232-36, Payment by Third Party (MAY 2014) (31 U.S.C. 3332).

____ (58) 52.239-1, Privacy or Security Safeguards (Aug 1996) (5 U.S.C. 552a).

____ (59) 52.242-5, Payments to Small Business Subcontractors (JAN 2017)(15 U.S.C. 637(d)(12)).

____ (60)(i) 52.247-64, Preference for Privately Owned U.S.-Flag Commercial Vessels (Feb 2006) (46 U.S.C. Appx. 1241(b) and 10 U.S.C. 2631).

____ (ii) Alternate I (Apr 2003) of 52.247-64.

____ (iii) Alternate II (Feb 2006) of 52.247-64.

(c) The Contractor shall comply with the FAR clauses in this paragraph (c), applicable to commercial services, that the Contracting Officer has indicated as being incorporated in this contract by reference to implement provisions of law or Executive orders applicable to acquisitions of commercial items: (Contracting Officer check as appropriate.)

_____ (1) 52.222-17, Nondisplacement of Qualified Workers (May 2014) (E.O. 13495).

_____ (2) 52.222-41, Service Contract Labor Standards (AUG 2018) (41 U.S.C. chapter 67).

_____ (3) 52.222-42, Statement of Equivalent Rates for Federal Hires (MAY 2014) (29 U.S.C. 206 and 41 U.S.C. chapter 67).

_____ (4) 52.222-43, Fair Labor Standards Act and Service Contract Labor Standards--Price Adjustment (Multiple Year and Option Contracts) (AUG 2018) (29 U.S.C. 206 and 41 U.S.C. chapter 67).

_____ (5) 52.222-44, Fair Labor Standards Act and Service Contract Labor Standards--Price Adjustment (MAY 2014) (29 U.S.C 206 and 41 U.S.C. chapter 67).

_____ (6) 52.222-51, Exemption from Application of the Service Contract Labor Standards to Contracts for Maintenance, Calibration, or Repair of Certain Equipment--Requirements (MAY 2014) (41 U.S.C. chapter 67).

_____ (7) 52.222-53, Exemption from Application of the Service Contract Labor Standards to Contracts for Certain Services--Requirements (MAY 2014) (41 U.S.C. chapter 67).

_____(8) 52.222-55, Minimum Wages Under Executive Order 13658 (DEC 2015) (E.O. 13658).

_____ (9) 52.222-62, Paid Sick Leave Under Executive Order 13706 (JAN 2017) (E.O. 13706).

_____ (10) 52.226-6, Promoting Excess Food Donation to Nonprofit Organizations (MAY 2014) (42 U.S.C. 1792).

_____ (11)…