SF18 - N0042124Q0067 (NISE Training).pdf
PDF 462 KB Posted
- Attached to
- Professional Management, Education & Training Federal contract opportunity
- Solicitation number
- N0042124Q0067
About this file
This is a request for quotations issued by the Department of the Navy Naval Air Systems Command Naval Air Warfare Center. It seeks a fixed-price quote to provide an 18-seat NISE training program. The training program will cover topics such as rapid response project milestone event support, high maturity project planning and tracking using agile methods, the accelerated systems engineer program, model-based systems engineering support, and performance and process improvement. Quotes are due by close of business on December 12, 2023. The period of performance for the training is through September 30, 2024. The solicitation includes standard contract clauses on inspection, assignment, changes, disputes, definitions, excusable delays, invoicing, patent indemnity, payment terms, risk of loss, taxes, termination for convenience, termination for cause, title, warranty, limitation of liability, compliance with laws, and order of precedence.
View the file
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
1301127514
REQUEST FOR QUOTATIONS
(THIS IS NOT AN ORDER) 1
PAGE OF PAGES
1. REQUEST NO. 2. DATE ISSUED RATING
N0042124Q0067 08-Dec-2023 5a. ISSUED BY
8. TO: NAME AND ADDRESS, INCLUDING ZIP CODE
SEE SCHEDULE
IMPORTANT: This is a request for information, and quotations furnished are not offers. If you are unable to quote, please so indicate on this form and return it to the address in Block 5a. This request does not commit the Government to pay any costs incurred in the preparation of the submission of this quotation or to contract for supplies or services. Supplies are of domestic origin unless otherwise indicated by quoter. Any representations and/or certifications attached to this
Request for Quotations must be completed by the quoter.
11. SCHEDULE (Include applicable Federal, State, and local taxes)
ITEM NO.
(a)
SUPPLIES/ SERVICES
(b)
QUANTITY
(c)
UNIT
(d)
UNIT PRICE
(e) (f)
SEE SCHEDULE
AMOUNT
% No. %
NOTE: Additional provisions and representations [ ] are [ ] are not attached.
13. NAME AND ADDRESS OF QUOTER (Street, City, County, State, and ZIP Code)
14. SIGNATURE OF PERSON AUTHORIZED TO
SIGN QUOTATION
15. DATE OF
QUOTATION
16. NAME AND TITLE OF SIGNER (Type or print) (Include area code)
TELEPHONE NO.
AUTHORIZED FOR LOCAL REPRODUCTION STANDARD FORM 18 (REV. 6-95)
PREVIOUS EDITION NOT USABLE Prescribed by GSA FAR (48 CFR) 53.215-1(a)
THIS RFQ [ ] IS X[ ] IS NOT A SMALL BUSINESS SET-ASIDE
6. DELIVER BY (Date)
SEE SCHEDULE
AND/OR DMS REG. 1
UNDER BDSA REG. 2
4. CERT. FOR NAT. DEF.3. REQUISITION/PURCHASE
REQUEST NO.
NAWCAD PROCUREMENT GROUP
21983 BUNDY ROAD, BLDG 441
PATUXENT RIVER MD 20670
9. DESTINATION (Consignee and address, including ZIP Code)
7. DELIVERY
[ ]X FOB
DESTINATION
[ ] OTHER
(See Schedule)
12-Dec-2023(Date)
PLEASE FURNISH QUOTATIONS TO THE ISSUING OFFICE IN BLOCK 5a ON OR BEFORE CLOSE OF BUSINESS:10.
NICOLE HARTMANN-HARDING
(Name and Telephone no.) (No collect calls)5b. FOR INFORMATION CALL:
d. CALENDAR DAYSc. 30 CALENDAR DAYSb. 20 CALENDAR DAYS12. DISCOUNT FOR PROMPT PAYMENT a. 10 CALENDAR DAYS
Section A - Solicitation/Contract Form
PURCHASE AGREEMENT
Block 6, Issued by, to include the following information:
Nicole Hartmann-Harding Email: Nicole.C.Hartmann-Harding.civ@us.navy.mil
Block 9, Contractor, to include the following information:
Vendor:
UEID:
CAGE:
Company POC:
Phone:
Email:
Technical POC:
Name:
Phone:
Email:
WAWF POC:
Name:
Phone:
Email:
PAYMENT/INVOICING ISSUES: PLEASE CONTACT COMPTROLLER BELOW.
N64142 NAWCAD
COMPTROLLER
INTERNAL ENTITLEMENTS TEAM BLDG 440 ROOM 25
47122 LILJENCRANTZ ROAD
PATUXENT RIVER, MD 20670-1549
INTERNAL ENTITLEMENTS TEAM 301-342-9586
EMAIL: PAXR_ACCT_INTERNAL_ENTITLEMENTS@NAVY.MIL
WAWF Invoicing Help & Instructions:
Visit the website at https://wawf.eb.mil/ and you can find help via the link "Vendors - Getting Started Help" under the New User section. The WAWF helpdesk for vendors is 1-866-618-5988
Section B - Supplies or Services and Prices
ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
0001 1 Each NISE Training Project
FFP
NISE Training Program - 18 Seats FOB: Destination
PURCHASE REQUEST NUMBER: 1301127514
PSC CD: U099
NET AMT
Section C - Descriptions and Specifications
STATEMENT OF WORK
Statement of Work
NAWCAD Systems Engineering Department
NISE Project 219WFD‐TR‐23‐041
Version: FY 2024
1.0 BACKGROUND AND GENERAL SCOPE OF WORK
1.1 BACKGROUND:
This statement of work (SOW) defines the tasks in support of NAWCAD Systems Engineering Department NISE Project 219WFD-TR-23-041. The SED provides NAWCAD enterprise-wide engineering support, innovation and project performance. The SED supports the mission to “Transform Systems Engineering across NAWCAD to be able to Innovate and Develop Faster and Better than the Enemy!”
GENERAL SCOPE OF WORK: The contractor shall provide training and associated resources for improving systems and software engineering knowledge, innovation, and performance. The contractor will support the following objectives:
● Improve Speed and Predictability of Projects:
o Rapid Response Projects Milestone Event Support o High Maturity Project Planning & Tracking using Agile Methods
● Close the Wisdom Gap:
o Accelerated Systems Engineer Program (ASE) o Accelerated Technical Warrant Holder (ATWH)
● Improve Engineering to have Higher Quality Faster:
o MBSE support with Methodology and SysML training, knowledge, community o Exceptional Learning Experience into the future (slow-fast) o Building Communities of Practices to network Systems Engineering Wisdom
(SE cohorts and SME mentors) Performance & Process Improvement Support
2.0 APPLICABLE DOCUMENTS
2.1 SPECIFICATIONS, STANDARDS, AND HANDBOOKS: N/A
2.2 OTHER DOCUMENTS, DRAWINGS, AND PUBLICATIONS:
2.2.1 Lead with Speed (Alan Willett)
2.2.2 Leading the Unleadable (Alan Willett)
2.2.3 Balancing Agility and Discipline (Barry Boehm)
2.2.4 TSP: Leading a Development Team (Watts Humphrey)
2.2.5 TSP: Coaching Development Teams (Watts Humphrey)
2.2.6 TPI (David Saint-Amand)
2.2.7 PSP: A Self-Improvement Process for Software Engineers (Watts Humphrey)
2.2.8 100+ Questions that lead teams build SMART, Aggressive Project Plans (Alan
Willett)
2.2.9 The Exceptional Engineer’s Field Guide to Systems Engineering at NAWCWD:
The Essence of Systems Engineering (Rick Kelly)
2.2.10 Leadership Teams and Trust (James Over, Watts Humphrey)
3.0 REQUIREMENTS
3.1 Objectives: The contractor will provide NAVAIR NAWCAD engineers the skills, methods, and coaching to accelerate their ability to create high‐performance teams with exceptional results.
This must be accomplished using three interrelated course objectives. Our requirements are education programs that are
3.1.1 Engineering focused programs (cannot be “general management or leadership”)
3.1.2 Based on the same Foundation as the TPI/TSP methodologies previously developed and applied at NAVAIR since 2001
3.1.3 System engineering-centric (not software-centric)
3.1.4 Delivered in the following ways
3.1.4.1 Must be spread across a number of weeks/months with breaks between the lessons. This is to enable maximum learning and application
3.1.4.2 Focused on real-work - must be applied to “on the job training”
3.1.4.3 Must provide expert level coaching to each individual
3.1.4.4 Distinct coverage for engineers in each of the following roles:
Individual System Engineers, Systems Engineering Team Leads responsible for engineering within a single project, and Lead Systems Engineers responsible for engineering across multiple projects
3.1.5 Cohesive with NAWCAD ASE offerings.
3.1.5.1 ASE Sprint 1 overview…The Threat
3.1.5.2 ASE Sprint 2 overview…The SE Day-Job
3.1.5.3 ASE Sprint 3 overview…Outside the SE Day-Job
3.1.5.4 ASE Sprint 4 overview…Understanding the NAVAIR SE
Community
3.1.5.5 ASE Sprint 5 overview…Transition to the ASE Community of Practice
3.1.6 Offerings must be delivered by trainers with extensive personal experience in multiple system engineering projects
3.2 Training for Individual Engineers. There must be training in the underlying concepts that are true across all engineering disciplines. The training must be applicable to all engineering disciplines such as hardware, electrical, software, and more. The following are the key requirements for training for project leaders.
3.2.1 Engineers will master methods that enable them and their teams to make commitments that they can keep or beat.
3.2.2 Engineers will learn methods for delivering high quality systems and solutions
3.2.3 Engineers will learn how to develop multiple engineering strategies to give management multiple paths to achieve best speed to value
3.2.4 Engineers will understand the economics of quality and speed and how to collect personal and team data to drive speed to value.
3.2.5 Engineers will learn design principles and methodologies that lead to best value for organizations and stakeholders.
3.2.6 Engineers will develop a deep understanding of the 7+ types of technical debt and how to measure debt, control debt, and eliminate technical debt
3.2.7 Engineers will develop methods to learnings to manage a diverse portfolio of projects including product enhancements and go faster initiatives..
3.2.8 Engineers will learn how to create positive, energizing work environments for themselves and those around them
3.2.9 Engineers will develop skills that enable them to amplify the abilities of their own teams and the teams around them.
3.3 Training as Systems Engineering Team Leads. These system engineers are responsible for projects and project teams that range in size from 2 people to over 200 people. Leaders must learn how to create and run high-performance teams. The following are the key requirements for training for project leaders.
3.3.1 Team leaders will internalize the meaning and value of being an Exceptional Leader
3.3.2 Team leaders must learn how to launch teams with methodologies that are compatible with NAVAIR’s TPI methods.
3.3.3 Team leaders will learn the methods to engrain in each team member the relentless pursuit of value to the organization and its customers
3.3.4 Team leaders will learn multiple ways to lead teams to turn over every rock, looking for and finding ways to go faster
3.3.5 Team leaders will master the means to enable teams to make commitments they will keep or beat.
3.3.6 Team leaders will learn multiple methods for estimating that empower teams to vastly improve their forecasting ability.
3.3.7 Team leaders will become masters of personal time management and delegation.
N0042124Q0067
3.3.8 Team leaders will develop the certainty and skills to lead teams through friction points resulting in the constructing innovation from conflict.
3.3.9 Team leaders will be empowered to take responsibility for their own destiny with a heightened ability to lead teams to success.
3.4 Training as Lead Systems Engineers. These systems engineers are responsible for multiple engineering projects or engineers that report into multiple engineering projects. The following are the key requirements for training for these Leads.
3.4.1 Provide Lead Systems Engineers with the mindset and methods to create a high-performance organization.
3.4.2 Lead Systems Engineers will develop a deep understanding of what a high-performance organization looks like through behaviors and data
3.4.3 Lead Systems Engineers will learn about NAVAIR’s TPI
measurement framework and how data feeds high-performance projects.
3.4.4 Lead Systems Engineers will know what data to ask for and how to ensure the data is honest, accurate, and used to improve
3.4.5 Lead Systems Engineers will learn specific methods in how to inspire the relentless pursuit of value in project leadership and their teams
3.4.6 Lead Systems Engineers will know the key factors for gaining speed in their projects
3.4.7 Lead Systems Engineers will learn the 100+ questions to ask that lead your teams to make smart, aggressive commitments that they keep
3.4.8 Lead Systems Engineers will understand when and how to recognize (and sometimes reward) results over sweat
3.4.9 Lead Systems Engineers will develop skills to create an environment that attracts and retains top talent
3.4.10 Lead Systems Engineers will master skills to coach, mentor, and empower your protégés to excel
3.4.11 Lead Systems Engineers will be empowered to take responsibility for their own destiny and that of their organizations
4.0 SPECIAL CONSIDERATIONS
4.1 Place of Performance – All deliveries are video-conferencing with individual; remote support.
5.0 SECURITY
None.
6.0 Travel
None.
Section E - Inspection and Acceptance
INSPECTION AND ACCEPTANCE TERMS
Supplies/services will be inspected/accepted at:
CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY
0001 Destination Government Destination Government
Section F - Deliveries or Performance
DELIVERY INFORMATION
CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /
CAGE
0001 30-SEP-2024 1 N/A
FOB: Destination
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 (JAN 2023)
(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):
(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.
(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.
(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 financing, submit a commercial 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*
Field Name in WAWF Data to be entered in WAWF
Pay Official DoDAAC ____
Issue By DoDAAC ____
Admin DoDAAC** ____
Inspect By DoDAAC ____
Ship To Code ____
Ship From Code ____
Mark For Code ____
Service Approver (DoDAAC) ____
Service Acceptor (DoDAAC) ____
Accept at Other DoDAAC ____
LPO DoDAAC ____
DCAA Auditor DoDAAC ____
Other DoDAAC(s) ____
(*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.
(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity’s WAWF point of contact.
(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 FULL TEXT
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.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR INFORMATION SYSTEMS (NOV 2021)
Covered contractor information system means an information system that is owned or operated by a contractor that processes, stores, or transmits Federal contract information.
Federal contract information means information, not intended for public release, that is provided by or generated for the Government under a contract to develop or deliver a product or service to the Government, but not including information provided by the Government to the public (such as on public websites) or simple transactional information, such as necessary to process payments.
Information means any communication or representation of knowledge such as facts, data, or opinions, in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audiovisual (Committee on National Security Systems Instruction (CNSSI) 4009).
Information system means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information (44 U.S.C. 3502).
Safeguarding means measures or controls that are prescribed to protect information systems.
(b) Safeguarding requirements and procedures.
(1) The Contractor shall apply the following basic safeguarding requirements and procedures to protect covered contractor information systems. Requirements and procedures for basic safeguarding of covered contractor information systems shall include, at a minimum, the following security controls:
(i) Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).
(ii) Limit information system access to the types of transactions and functions that authorized users are permitted to execute.
(iii) Verify and control/limit connections to and use of external information systems.
(iv) Control information posted or processed on publicly accessible information systems.
(v) Identify information system users, processes acting on behalf of users, or devices.
(vi) Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.
(vii) Sanitize or destroy information system media containing Federal Contract Information before disposal or release for reuse.
(viii) Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals.
(ix) Escort visitors and monitor visitor activity; maintain audit logs of physical access; and control and manage physical access devices.
(x) Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems.
(xi) Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.
(xii) Identify, report, and correct information and information system flaws in a timely manner.
(xiii) Provide protection from malicious code at appropriate locations within organizational information systems.
(xiv) Update malicious code protection mechanisms when new releases are available.
(xv) Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed.
(2) Other requirements. This clause does not relieve the Contractor of any other specific safeguarding requirements specified by Federal agencies and departments relating to covered contractor information systems generally or other Federal safeguarding requirements for controlled unclassified information (CUI) as established by Executive Order 13556.
(c) Subcontracts. The Contractor shall include the substance of this clause, including this paragraph (c), in subcontracts under this contract (including subcontracts for the acquisition of commercial products or commercial services, other than commercially available off-the-shelf items), in which the subcontractor may have Federal contract information residing in or transiting through its information system.
52.204-24 REPRESENTATION REGARDING CERTAIN TELECOMMUNICATIONS AND VIDEO
SURVEILLANCE SERVICES OR EQUIPMENT (NOV 2021)
The Offeror shall not complete the representation at paragraph (d)(1) of this provision if the Offeror has represented that it "does not provide covered telecommunications equipment or services as a part of its offered products or services to the Government in the performance of any contract, subcontract, or other contractual instrument" in paragraph (c)(1) in the provision at 52.204-26, Covered Telecommunications Equipment or Services-- Representation, or in paragraph (v)(2)(i) of the provision at 52.212-3, Offeror Representations and Certifications- Commercial Products and Commercial Services. The Offeror shall not complete the representation in paragraph (d)(2) of this provision if the Offeror has represented that it "does not use covered telecommunications equipment or services, or any equipment, system, or service that uses covered telecommunications equipment or services" in paragraph (c)(2) of the provision at 52.204-26, or in paragraph (v)(2)(ii) of the provision at 52.212-3.
(a) Definitions. As used in this provision-
Backhaul, covered telecommunications equipment or services, critical technology, interconnection arrangements, reasonable inquiry, roaming, and substantial or essential component have the meanings provided in the clause 52.204-25, Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or Equipment.
(b) Prohibition.
(1) Section 889(a)(1)(A) of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 (Pub. L.
115-232) prohibits the head of an executive agency on or after August 13, 2019, from procuring or obtaining, or extending or renewing a contract to procure or obtain, any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system. Nothing in the prohibition shall be construed to--
(i) Prohibit the head of an executive agency from procuring with an entity to provide a service that connects to the facilities of a third-party, such as backhaul, roaming, or interconnection arrangements; or
(ii) Cover telecommunications equipment that cannot route or redirect user data traffic or cannot permit visibility into any user data or packets that such equipment transmits or otherwise handles.
(2) Section 889(a)(1)(B) of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 (Pub. L.
115-232) prohibits the head of an executive agency on or after August 13, 2020, from entering into a contract or extending or renewing a contract with an entity that uses any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system. This prohibition applies to the use of covered telecommunications equipment or services, regardless of whether that use is in performance of work under a Federal contract. Nothing in the prohibition shall be construed to--
(i) Prohibit the head of an executive agency from procuring with an entity to provide a service that connects to the facilities of a third-party, such as backhaul, roaming, or interconnection arrangements; or
(ii) Cover telecommunications equipment that cannot route or redirect user data traffic or cannot permit visibility into any user data or packets that such equipment transmits or otherwise handles.
(c) Procedures. The Offeror shall review the list of excluded parties in the System for Award Management (SAM) (https://www.sam.gov) for entities excluded from receiving federal awards for "covered telecommunications equipment or services."
(d) Representations. The Offeror represents that--
(1) It [ ___ ] will, [ ___ ] will not provide covered telecommunications equipment or services to the Government in the performance of any contract, subcontract or other contractual instrument resulting from this solicitation. The Offeror shall provide the additional disclosure information required at paragraph (e)(1) of this section if the Offeror responds "will" in paragraph (d)(1) of this section; and
(2) After conducting a reasonable inquiry, for purposes of this representation, the Offeror represents that--
It [ ___ ] does, [ ___ ] does not use covered telecommunications equipment or services, or use any equipment, system, or service that uses covered telecommunications equipment or services. The Offeror shall provide the additional disclosure information required at paragraph (e)(2) of this section if the Offeror responds "does" in paragraph (d)(2) of this section.
(e) Disclosures.
(1) Disclosure for the representation in paragraph (d)(1) of this provision. If the Offeror has responded "will" in the representation in paragraph (d)(1) of this provision, the Offeror shall provide the following information as part of the offer:
(i) For covered equipment--
(A) The entity that produced the covered telecommunications equipment (include entity name, unique entity identifier, CAGE code, and whether the entity was the original equipment manufacturer (OEM) or a distributor, if known);
(B) A description of all covered telecommunications equipment offered (include brand; model number, such as OEM number, manufacturer part number, or wholesaler number; and item description, as applicable); and
(C) Explanation of the proposed use of covered telecommunications equipment and any factors relevant to determining if such use would be permissible under the prohibition in paragraph (b)(1) of this provision.
(ii) For covered services--
(A) If the service is related to item maintenance: A description of all covered telecommunications services offered (include on the item being maintained: Brand; model number, such as OEM number, manufacturer part number, or wholesaler number; and item description, as applicable); or
(B) If not associated with maintenance, the Product Service Code (PSC) of the service being provided; and explanation of the proposed use of covered telecommunications services and any factors relevant to determining if such use would be permissible under the prohibition in paragraph (b)(1) of this provision.
(2) Disclosure for the representation in paragraph (d)(2) of this provision. If the Offeror has responded "does" in the representation in paragraph (d)(2) of this provision, the Offeror shall provide the following information as part of the offer:
(i) For covered equipment--
(A) The entity that produced the covered telecommunications equipment (include entity name, unique entity identifier, CAGE code, and whether the entity was the OEM or a distributor, if known);
(B) A description of all covered telecommunications equipment offered (include brand; model number, such as OEM number, manufacturer part number, or wholesaler number; and item description, as applicable); and
(C) Explanation of the proposed use of covered telecommunications equipment and any factors relevant to determining if such use would be permissible under the prohibition in paragraph (b)(2) of this provision.
(ii) For covered services--
(A) If the service is related to item maintenance: A description of all covered telecommunications services offered (include on the item being maintained: Brand; model number, such as OEM number, manufacturer part number, or wholesaler number; and item description, as applicable); or
(B) If not associated with maintenance, the PSC of the service being provided; and explanation of the proposed use of covered telecommunications services and any factors relevant to determining if such use would be permissible under the prohibition in paragraph (b)(2) of this provision.
(End of provision)
52.204-25 PROHIBITION ON CONTRACTING FOR CERTAIN TELECOMMUNICATIONS AND VIDEO
SURVEILLANCE SERVICES OR EQUIPMENT (NOV 2021)
(a) Definitions. As used in this clause--
Backhaul means intermediate links between the core network, or backbone network, and the small subnetworks at the edge of the network (e.g., connecting cell phones/towers to the core telephone network). Backhaul can be wireless (e.g., microwave) or wired (e.g., fiber optic, coaxial cable, Ethernet).
Covered foreign country means The People's Republic of China.
Covered telecommunications equipment or services means--
(1) Telecommunications equipment produced by Huawei Technologies Company or ZTE Corporation (or any subsidiary or affiliate of such entities);
(2) For the purpose of public safety, security of Government facilities, physical security surveillance of critical infrastructure, and other national security purposes, video surveillance and telecommunications equipment produced by Hytera Communications Corporation, Hangzhou Hikvision Digital Technology Company, or Dahua Technology Company (or any subsidiary or affiliate of such entities);
(3) Telecommunications or video surveillance services provided by such entities or using such equipment; or
(4) Telecommunications or video surveillance equipment or services produced or provided by an entity that the Secretary of Defense, in consultation with the Director of National Intelligence or the Director of the Federal Bureau of Investigation, reasonably believes to be an entity owned or controlled by, or otherwise connected to, the government of a covered foreign country.
Critical technology means--
(1) Defense articles or defense services included on the United States Munitions List set forth in the International Traffic in Arms Regulations under subchapter M of chapter I of title 22, Code of Federal Regulations;
(2) Items included on the Commerce Control List set forth in Supplement No. 1 to part 774 of the Export Administration Regulations under subchapter C of chapter VII of title 15, Code of Federal Regulations, and controlled--
(i) Pursuant to multilateral regimes, including for reasons relating to national security, chemical and biological weapons proliferation, nuclear nonproliferation, or missile technology; or
(ii) For reasons relating to regional stability or surreptitious listening;
(3) Specially designed and prepared nuclear equipment, parts and components, materials, software, and technology covered by part 810 of title 10, Code of Federal Regulations (relating to assistance to foreign atomic energy activities);
(4) Nuclear facilities, equipment, and material covered by part 110 of title 10, Code of Federal Regulations (relating to export and import of nuclear equipment and material);
(5) Select agents and toxins covered by part 331 of title 7, Code of Federal Regulations, part 121 of title 9 of such Code, or part 73 of title 42 of such Code; or
(6) Emerging and foundational technologies controlled pursuant to section 1758 of the Export Control Reform Act of 2018 (50 U.S.C. 4817).
Interconnection arrangements means arrangements governing the physical connection of two or more networks to allow the use of another's network to hand off traffic where it is ultimately delivered (e.g., connection of a customer of telephone provider A to a customer of telephone company B) or sharing data and other information resources.
Reasonable inquiry means an inquiry designed to uncover any information in the entity's possession about the identity of the producer or provider of covered telecommunications equipment or services used by the entity that excludes the need to include an internal or third-party audit.
Roaming means cellular communications services (e.g., voice, video, data) received from a visited network when unable to connect to the facilities of the home network either because signal coverage is too weak or because traffic is too high.
Substantial or essential component means any component necessary for the proper function or performance of a piece of equipment, system, or service.
(b) Prohibition.
(1) Section 889(a)(1)(A) of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 (Pub. L.
115-232) prohibits the head of an executive agency on or after August 13, 2019, from procuring or obtaining, or extending or renewing a contract to procure or obtain, any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system. The Contractor is prohibited from providing to the Government any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system, unless an exception at paragraph (c) of this clause applies or the covered telecommunication equipment or services are covered by a waiver described in FAR 4.2104.
(2) Section 889(a)(1)(B) of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 (Pub. L.
115-232) prohibits the head of an executive agency on or after August 13, 2020, from entering into a contract, or extending or renewing a contract, with an entity that uses any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system, unless an exception at paragraph (c) of this clause applies or the covered telecommunication equipment or services are covered by a waiver described in FAR 4.2104. This prohibition applies to the use of covered telecommunications equipment or services, regardless of whether that use is in performance of work under a Federal contract.
(c) Exceptions. This clause does not prohibit contractors from providing--
(1) A service that connects to the facilities of a third-party, such as backhaul, roaming, or interconnection arrangements; or
(2) Telecommunications equipment that cannot route or redirect user data traffic or permit visibility into any user data or packets that such equipment transmits or otherwise handles.
(d) Reporting requirement.
(1) In the event the Contractor identifies covered telecommunications equipment or services used as a substantial or essential component of any system, or as critical technology as part of any system, during contract performance, or the Contractor is notified of such by a subcontractor at any tier or by any other source, the Contractor shall report the information in paragraph (d)(2) of this clause to the Contracting Officer, unless elsewhere in this contract are established procedures for reporting the information; in the case of the Department of Defense, the Contractor shall report to the website at https://dibnet.dod.mil. For indefinite delivery contracts, the Contractor shall report to the Contracting Officer for the indefinite delivery contract and the Contracting Officer(s) for any affected order or, in the case of the Department of Defense, identify both the indefinite delivery contract and any affected orders in the report provided at https://dibnet.dod.mil.
(2) The Contractor shall report the following information pursuant to paragraph (d)(1) of this clause:
(i) Within one business day from the date of such identification or notification: The contract number; the order number(s), if applicable; supplier name; supplier unique entity identifier (if known); supplier Commercial and Government Entity (CAGE) code (if known); brand; model number (original equipment manufacturer number, manufacturer part number, or wholesaler number); item description; and any readily available information about mitigation actions undertaken or recommended.
(ii) Within 10 business days of submitting the information in paragraph (d)(2)(i) of this clause: Any further available information about mitigation actions undertaken or recommended. In addition, the Contractor shall describe the efforts it undertook to prevent use or submission of covered telecommunications equipment or services, and any additional efforts that will be incorporated to prevent future use or submission of covered telecommunications equipment or services.
(e) Subcontracts. The Contractor shall insert the substance of this clause, including this paragraph (e) and excluding paragraph (b)(2), in all subcontracts and other contractual instruments, including subcontracts for the acquisition of commercial products or commercial services.
52.204-27 PROHIBITION ON A BYTEDANCE COVERED APPLICATION (JUN 2023)
Covered application means the social networking service TikTok or any successor application or service developed or provided by ByteDance Limited or an entity owned by ByteDance Limited.
Information technology, as defined in 40 U.S.C. 11101(6)--
(1) Means any equipment or interconnected system or subsystem of equipment, used in the automatic acquisition, storage, analysis, evaluation, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information by the executive agency, if the equipment is used by the executive agency directly or is used by a contractor under a contract with the executive agency that requires the use-
(i) Of that equipment; or
(ii) Of that equipment to a significant extent in the performance of a service or the furnishing of a product;
(2) Includes computers, ancillary equipment (including imaging peripherals, input, output, and storage devices necessary for security and surveillance), peripheral equipment designed to be controlled by the central processing unit of a computer, software, firmware and similar procedures, services (including support services), and related resources; but
(3) Does not include any equipment acquired by a Federal contractor incidental to a Federal contract.
(b) Prohibition. Section 102 of Division R of the Consolidated Appropriations Act, 2023 (Pub. L. 117-328), the No TikTok on Government Devices Act, and its implementing guidance under Office of Management and Budget (OMB) Memorandum M-23-13, dated February 27, 2023, "No TikTok on Government Devices" Implementation Guidance, collectively prohibit the presence or use of a covered application on executive agency information technology, including certain equipment used by Federal contractors. The Contractor is prohibited from having or using a covered application on any information technology owned or managed by the Government, or on any information technology used or provided by the Contractor under this contract, including equipment provided by the Contractor's employees; however, this prohibition does not apply if the Contracting Officer provides written notification to the Contractor that an exception has been granted in accordance with OMB Memorandum M-23-13.
(c) Subcontracts. The Contractor shall insert the substance of this clause, including this paragraph (c), in all subcontracts, including subcontracts for the acquisition of commercial products or commercial services.
5…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .