URS - UPDATED
Federal opportunity from Central Procurement Office • Tennessee Department of General Services. Place of performance: TN.
- Source
- Open on official portal →
- Solicitation
- tn_cpo__RFP 33101-25105FAS3
- Performance
- TN
- Response
- No due date posted
Point of Contact
Agency & Office
Applicable wage determinations
Best public WD match for the notice location and scope.
View more WD detail3 more WD matches and 7 more rate previews.↓
Description
02-20-20 CI-POST Event RFP 33101 -25105FAS3 SOLICITATION NOTICE March 27, 2026 Service Providers : The State of Tennessee is issuing a solicitation to provide services to the S tate. Please note the fo llowing solicitation highlights: SOLICITATION ID # Confidential RFP 33101 -25105FAS3 Scope of Goods or Service URS Procuring State Agency Department of Education Response Deadline NDA deadline: March 27 – April 10, 202 6 Response deadline: May 1 9, 2026 Solicitation Coordinator Contact Information Genell Jordan | Sourcing Account Specialist Central Procurement Office Tennessee Tower, 3rd Floor 312 Rosa L. Parks Ave., Nashville, TN 37243 Phone: 615-532-7202 Email: Genell.Jordan@tn.gov This solicitation is unique in that it has been identified by the Department of Finance and Administration, Strategic Technology Solutions as containing information that is confidential under Tenn. Code Ann. § 10 -7- 504(i). Therefore , a non-disclosure agreement must be signed before the solicitation details may be disclosed by the State. If you are interested in responding to this solicitation , please complete the attached non-disclosure agreement and return it to the Solicitation Coordinator . The above solicitation includes a document on “How to Register to do Business with the State of Tennessee .” Please note that it can take approximately 10 -14 days to become registered . We appreciate your inter est in doing business with the S tate of Tennessee and hope that you wi ll consider responding to this solicitation . THE STATE OF TENNESSEE NONDISCLOSURE AGREEMENT This Nondisclosure Agreement for RFP 33101 -25105FAS3 (hereinafter referred to as the "Agreement") is effective upon signature by the SUPPLIER LEGAL ENTITY NAME (Supplier having its principal place of business at SUPPLIER ’S ADDRESS (“Supplier ”). The Supplier agree s as follows: 1. Material s, records, notes, logs, diagrams, drawings and any other information or records , regardless of form, medium or method of communication, provided to the Supplier by the State or acquired by the Supplier on behalf of the State , as well as all information derived or resulting from merges, matches, or other uses of the information shall be regarded as Confidential State Data . Confidential State Data shall also include , but shall not be limited to: (i) electronic information processing systems, telecommunications systems, or other communications systems of the State (collectively, “Government Property”) ; (ii) plans, security codes, passwords, combinations, or computer programs used to protect electronic information and Government Property; (iii) information that would identify those areas of structural or operational vulnerability that would permit unlawful disruption to, or interference with, the services provided by a governmental entity; (iv) information that could be used to disrupt, interfere with, or gain unauthorized access to electronic information or Government Property; and (v) the identity of another Supplier providing goods and services to the State that are used to protect electronic information processing systems, telecommunication and other communication systems, data storage systems, government employee information, or information related any person or entity. 2. The Supplier shall safeguard and hold in strict confidence all Confidential State Data and shall not disclose the Confidential State Data to third parties without the written consent of the State. The Supplier shall further restrict disclosure of Confidential State Data to only those employees who have a need to know and who have executed a nondisclosure agreement to protect the Confidential State Data with terms equivalent to this Agreement. 3. Nothing in this Agreement shall permit the Supplier to disclose any Confidential State Data , regardless of whether it has been disclosed or made available to the Supplier due to intentional or negligent actions or inactions of agents of the State or third parties. Confidential State Data shall not be disclosed except as required under state or federal law. To the fullest extent allowable under applicable law or regulation, the Supplier shall promptly notify and provide to the State a reasonable opportunity to oppose any disclosure required under state or federal law. 4. The Supplier acknowledges that Confidential State Data delivered by the State to the Supplier shall be for the purpose of exploration of business opportunities involving the State and the Supplier . No other use of the Confidential State Data is granted without the written consent of the State. In the event the State gives its approval for the Supplier to disclose Confidential State Data to a third party, the Supplier shall ensure that all such disclosures are marked with appropriate legends, the receiving third party enters into an non -disclosure agreement to protect Confidential State Data with terms as least as protective as those contained this Agreement, and any other conditions reasonably required by the State in order to preserve the confidential nature of the information and the State's rights therein. 5. All obligations set forth under this Agreement shall survive any termination of th is Agreement . Upon termination, t he Supplier shall promptly destroy all Confidential State Data it holds (including any copies such as backups) in accordance with the current version of National Institute of Standards and Technology Special Publication 800 -88. 6. This Agreement shall not be construed as a teaming, joint venture or other such arrangement; rather, the parties hereto expressly agree that this Agreement is for the purpose of protecting Confidential State Data only. 7. If any terms and conditions of this Agreement are held to be invalid or unenforceable as a matter of law, the other terms and conditions of this Agreement shall not be affected and shall remain in full force and effect. The terms and conditions of this A greement are severable. 8. This Agreement shall be governed by and construed in accordance with the laws of the State of Tennessee , without regard to its conflict or choice of law rules . The Tennessee Claims Commission or the state or federal courts in Tennessee shall be the venue for all claims, disputes, or disagreements arising under this Agreement. The Supplier acknowledges and agrees that any rights, claims, or remedies against the State of Tennessee or its employees arising under this Agreement shall be subject to and limited to those rights and remedies available under Tenn. Code Ann. §§ 9 -8-101 - 408. 9. Nothing in this Agreement shall be construed to convey to Supplier any right, title or interest or copyright in the Confidential State Data , or any license to use, sell, exploit, copy or further develop the Confidential State Data . 10. This Agreement is complete and contains the entire understanding between the Parties relating to its subject matter, including all the terms and conditions of the Parties’ agreement. This Agreement may only be modified by a written amendment signed by the Supplier and approved by all applicable State officials. IN WITNESS WHEREOF , this Agreement has been executed by the Supplier and is effective as of the date signed below: INSERT SUPPLIER LEGAL ENTITY NAME By: Name: Title: Date:
Pricing and bid posture
Contractor-side estimate from visible notice metadata, NAICS/PSC, contract type, schedule hints, and BidPulsar workpaper assumptions. Not an IGCE, incumbent price, award value, or government budget.
This advisory bid range is visible page text for contractors and search engines: it summarizes the modeled floor, target, and premium bid posture for this solicitation.
Market snapshot
Baseline awarded-market signal across all contracting (sample of 400 recent awards; refreshed periodically).
Files
Files size/type shown when available.
BidPulsar Analysis
A practical, capture-style breakdown of fit, requirements, risks, and next steps.
This opportunity is a Central Procurement Office notice titled “URS” with notice_id “tn_cpo__RFP 33101-25105FAS3.” The only scope detail provided in the brief is “URS,” and the only available document is an attachment named “RFP_33101-25105FAS3_Universal Screener.pdf” at the provided TN.gov link. No posted date, response deadline, NAICS/PSC, set-aside, place of performance, or period of performance details are included in the brief. The immediate next step for capture is to review the attached PDF to extract mandatory requirements, submission instructions, and evaluation criteria before making a bid/no-bid decision.
Based strictly on the brief text and attachment filename, the buyer (Central Procurement Office) appears to be soliciting something associated with a “Universal Screener” under RFP 33101-25105FAS3 (abbreviated as “URS” in the description/title).
- Firms that can credibly deliver the “Universal Screener” solution described in “RFP_33101-25105FAS3_Universal Screener.pdf” and can comply with Central Procurement Office solicitation requirements as written in that attachment.
- Download and review the attachment: “RFP_33101-25105FAS3_Universal Screener.pdf.”
- Extract from the PDF: scope of work, required deliverables, implementation/operational expectations (if any), and any technical/functional requirements tied to “Universal Screener.”
- Identify administrative requirements: proposal volumes, forms, required certifications, signatures, and submission method/portal (if specified in the PDF).
- Extract evaluation criteria and scoring approach from the PDF to shape win themes and compliance matrix.
- Build a compliance matrix keyed to the RFP section numbering found in the PDF and map each requirement to proposal sections/owners.
- Clarify any ambiguities via Q&A process (if the PDF provides Q&A deadlines and contact).
- Finalize pricing approach only after confirming whether this is goods, software/SaaS, services, or a combination, as defined in the PDF.
- Completed proposal response as instructed in “RFP_33101-25105FAS3_Universal Screener.pdf” (volumes/format per RFP).
- Compliance matrix mapped to each RFP requirement section from the PDF.
- Completed required forms/attachments referenced within the PDF (including any signatures).
- Pricing response in the exact format required by the PDF (line items, rate sheets, or cost tables if specified).
- Any required technical documentation specific to the “Universal Screener” (only as requested in the PDF).
More BidPulsar strategy notesCompliance, pricing, teaming, risks, questions, and coverage notes
- The brief does not include submission deadlines, delivery method, or required forms; these must be taken from “RFP_33101-25105FAS3_Universal Screener.pdf.”
- Treat the attachment as the controlling document for all compliance items (format, page limits, file naming, signatures, addenda acknowledgement if applicable).
- Pricing strategy cannot be responsibly set from the brief alone; confirm from the PDF whether this is a one-time purchase, subscription, services engagement, or multi-year arrangement, and whether pricing is evaluated competitively on total cost, line items, or other basis.
- Consider teaming only after the PDF clarifies scope: e.g., if “Universal Screener” requires implementation services, integrations, hosting, accessibility/security documentation, or ongoing support, identify specialist subs aligned to those named requirements in the RFP attachment.
- High scope ambiguity risk: the opportunity brief contains only “URS” and provides no requirements beyond the attached PDF title.
- High compliance risk until the PDF is reviewed: missing deadline, submission instructions, and required forms could lead to rejection if mishandled.
- Potential misalignment risk: “URS” could be interpreted in multiple ways; do not commit bid resources until the PDF confirms what the buyer means by “Universal Screener.”
- In “RFP_33101-25105FAS3_Universal Screener.pdf,” what is the defined scope of “Universal Screener” (product, service, or both), and what are the required deliverables?
- What are the proposal submission instructions and exact due date/time (as stated in the PDF)?
- What evaluation criteria and weighting are specified in the PDF (technical vs. cost vs. other factors)?
- Is there an implementation timeline, acceptance criteria, and required support/service levels specified in the PDF?
- Are there mandatory vendor qualifications, prior experience thresholds, or compliance standards required in the PDF?
Some notices publish limited source detail. Confirm these points before final bid/no-bid decisions.
- The actual requirements, submission instructions, deadlines, evaluation criteria, and pricing format are not present in the brief and must be extracted from the attached “RFP_33101-25105FAS3_Universal Screener.pdf.”
Service match
Optional support routes matched to this notice after the core solicitation details.
Related hubs & trends
Navigate the lattice: hubs for browsing, trends for pricing signals.