IT ENTERPRISE ARCHITECTURE MODELING TOOL FOR THE CITY OF DURHAM
| Location: | North Carolina |
|---|---|
| Posted: | Dec 18, 2025 |
| Due: | Jan 9, 2026 |
| Agency: | City of Durham |
| Type of Government: | State & Local |
| Category: |
|
| Solicitation No: | 26-1010 |
| Publication URL: | To access bid details, please log in. |
| Bid Number: |
26-1010
|
| Bid Title: |
IT ENTERPRISE ARCHITECTURE MODELING TOOL FOR THE CITY OF DURHAM
|
| Category: | Requests for Proposals/Qualifications and Services |
| Status: | Open |
|
Attachment Preview
City of Durham
Request for Proposal (RFP) #26-1010
Date of Issue: December 15, 2025
Due Date: December 22, 2025
TO PROVIDE AN IT ENTERPRISE ARCHITECTURE MODELING TOOL FOR THE CITY OF DURHAM
Through this RFP, the City of Durham is seeking proposals from vendors for an IT enterprise architecture
modeling tool.
Questions about this RFP should be directed to:
Project Manager
Austin Regnerus
Title
IT Project Manager
Department
Technology Solutions Department
Address
101 City Hall Plaza, Durham, NC 27701
Telephone
919-560-4122 ext 33213
Email
Austin.Regnerus@durhamnc.gov
page 1
Enterprise Architecture Modeling Tool
Contents
10. Date of RFP..........................................................................................................................3
20. Project Manager and Contact with City...............................................................................3
30. Project ..................................................................................................................................3
40. Scope of Work. ....................................................................................................................3
50. Compensation Amount and Schedule..................................................................................4
70. Contract................................................................................................................................4
80. Trade Secrets and Confidentiality........................................................................................4
85. Reserved...............................................................................................................................5
90. Bonds. ..................................................................................................................................5
100. Insurance. ...........................................................................................................................5
110. Discretion of the City.........................................................................................................6
120. Schedule.............................................................................................................................7
130. Keeping Proposals Open....................................................................................................7
140. Deadline to Submit Proposals............................................................................................7
150. Questions............................................................................................................................7
160. Reserved.............................................................................................................................7
170. Updates and revisions to RFP. ...........................................................................................7
180. Evaluation Criteria .............................................................................................................7
190 – 230. Reserved...................................................................................................................8
240. Contents of Proposal. .........................................................................................................8
250. Cover letter.........................................................................................................................9
260. Addendums ......................................................................................................................10
270. How to submit a proposal. ...............................................................................................10
280. Format. .............................................................................................................................10
290. Alternative Proposals. ......................................................................................................10
300. Candidate to Bear Expense; No Claims against City.......................................................10
310. State Treasurer’s lists regarding Iran and Boycott of Israel. ..........................................10
320. Notice Under the Americans with Disabilities Act..........................................................11
330. Values of City of Durham regarding Treatment of Employees of Contractors ...............11
page 2
Enterprise Architecture Modeling Tool
10. Date of RFP: December 15, 2025
20. Project Manager and Contact with City. Questions about this RFP. Direct questions and concerns to
Attn: Austin Regnerus
Technology Solutions
City of Durham
101 City Hall Plaza
Durham, NC 27701-3329
Email: Austin.Regnerus@durhamnc.gov
Phone: 919-560-4122 ext 33213
If you have concerns about this RFP that you believe are not being addressed by the project manager, please contact
Mitch Smith
Technology Solutions
City of Durham
101 City Hall Plaza
Durham, NC 27701-3329
Email: mitch.smith@durhamnc.gov
Phone: (919) 817-5581
DESCRIPTION OF PROJECT AND NATURE OF RFP
30. Project. The City of Durham is seeking proposals from qualified vendors capable of providing an enterprise architecture
modeling tool.
Background: The current process for enterprise architecture planning is manual and fragmented, leading to inefficiency,
inconsistency, and lack of comprehensive visibility into the City's technology. This leads to increased operational
costs, delayed projects and difficulty maintaining compliance with industry standards. An architecture modeling tool will
allow for complete, unified mapping of the City’s IT landscape.
40. Scope of Work.
The City of Durham is looking for a vendor to provide an enterprise architecture modeling tool for full application,
hardware, data, and operational mapping. The selected tool should have the following capabilities:
• Portfolio and Lifecycle Management
o Track and manage business capabilities, applications, technologies, and information portfolios.
o Support application rationalization—deciding whether to invest, sustain, migrate, or retire applications
based on performance and strategic alignment.
o Provide visual modeling (e.g., Gantt charts, bubble charts) to assess lifecycle stages and dependencies
• Tool Overlap Identification and ROI Optimization
o Map existing tools across departments and identify functional overlaps.
o Support asset rationalization by analyzing usage, cost, and redundancy
o Enable scenario modeling to forecast cost savings and performance improvements from consolidation
• Governance and Compliance
o Ensure auditability and transparency in decision-making.
o Align with public sector procurement cycles, union rules, and regulatory requirements
• Integration and Interoperability
o Support open standards (e.g., TOGAF, ArchiMate, BPMN).
o Integrate with existing ERP, GIS, and asset management platforms used by the City
The City plans to utilize the tool to:
• Facilitate servicing, relocating, and modifying existing IT setup
• Enable management of all operational costs via identification of potential cost savings
• Provide information needed to prioritize cost savings opportunities
• Speed project implementation time, eliminating surprises in infrastructure involved
• Assist in ensuring compliance with industry standards, including:
o National Institute of Standards and Technology - Cybersecurity Framework (NIST CSF)
page 3
Enterprise Architecture Modeling Tool
o Criminal Justice Information Systems (CJIS)
o The Open Group Architecture Framework (TOGAF)
The City is likely to prefer proposals that:
• Have automated data ingestion capabilities
• Outline training and support resources
50. Compensation Amount and Schedule.
Compensation for services proposed in this RFP should be based on the completion of milestones or deliverables which
must be described in the RFP response.
Proposal Costs
Based upon the Scope of Work, briefly describe the effort and show
the associated cost for you to implement your solution to fit the
requested Scope of Work.
Description
Qty or
Hours
Rate
Cost
eg. Engineering Services
eg. Project Management
Services
eg. After hour Engineering
Services
eg., Other Services
Total:
Vendors note: Please add additional lines as necessary to support your proposal.
60. Definitions in this RFP: City, RFP, Proposal, Candidate, Contractor, Should. Unless the context indicates otherwise –
(a) The expressions “RFP,” “this RFP,” and “the RFP” refer to this document as it may be amended or updated. (b) “City”
and “city” mean the City of Durham. (c) The “proposal” or "Bid" is the response of a person, firm, or corporation proposing
to provide the services sought by this RFP. (d) The word “Candidate” or “candidate” is the person, firm, or corporation that
submits a proposal or that is considering submitting a proposal. (e) The word “Contractor” or “contractor” is the person,
firm, or corporation with which the City enters into a contract to provide the services sought by this RFP. That is,
“contractor” generally refers to a successful candidate that has obtained a fully executed contract with the City, while
“candidate” is generally reserved to the stage before a contract has been signed. (f) The word “should” is used to tell
candidates what the City thinks it wants and/or what the project manager thinks is best. Candidates that want to increase
the likelihood of being selected will, in general, do what the RFP says candidates “should” do, but failure to comply with all
“should” will not necessarily and automatically result in rejection.
70. Contract. The City anticipates that the conclusion of the RFP process will be a contract between the City and the
successful candidate under which the successful candidate will provide the goods and services generally described in this
RFP. It is the City’s intention to use the contract that is attached as Exhibit A, modified and filled in to reflect the RFP and
the proposal. If a candidate objects to any of the contract, it should state the objections in its proposal.
80. Trade Secrets and Confidentiality. As a general rule, all submissions to the City are available to any member of the
public. However, if materials qualify as provided in this section, the City will take reasonable steps to keep trade secrets
confidential.
Definitions.
In this section (Trade Secrets and Confidentiality) –
The term “candidate” includes the candidate as contractor (that is, after it is a party to a contract with the City).
The term “trade secret” means business or technical information, including but not limited to a formula, pattern,
program, device, compilation of information, method, technique, or process that:
a. Derives independent actual or potential commercial value from not being generally known or readily
ascertainable through independent development or reverse engineering by persons who can obtain economic
value from its disclosure or use; and
page 4
Enterprise Architecture Modeling Tool
b. Is the subject of efforts that are reasonable under the circumstances to maintain its secrecy.
The existence of a trade secret shall not be negated merely because the information comprising the trade
secret has also been developed, used, or owned independently by more than one person, or licensed to other
persons.
The term “record” means all documents, papers, letters, maps, books, photographs, films, sound recordings, magnetic
or other tapes, electronic data-processing records, artifacts, or other documentary material, regardless of physical form
or characteristics, received by the City of Durham in connection with the candidate’s proposal.
(a) Designation of Confidential Records. To the extent that the candidate wishes to maintain the confidentiality
of trade secrets contained in materials provided to the City, the candidate shall prominently designate the
material with the words “trade secrets” at the time of its initial disclosure to the City. The candidate shall not
designate any material provided to the City as trade secrets unless the candidate has a reasonable and good-faith
belief that the material contains a trade secret. When requested by the City, the candidate shall promptly
disclose to the City the candidate’s reasoning for designating material as trade secrets; the candidate may need to
label parts of that reasoning as trade secrets. In providing materials to the City, the candidate shall make
reasonable efforts to separate those designated as trade secrets from those not so designated, both to facilitate
the City’s use of the materials and to minimize the opportunity for accidental disclosure. For instance, if only a
sentence or paragraph on a page is a trade secret, the page must be marked clearly to communicate that
distinction. To avoid mistake or confusion, it is generally best to have only trade secret information on a page and
nothing else on that page.
To the extent authorized by applicable state and federal law, the City shall maintain the confidentiality of records
designated “trade secrets” in accordance with this section. Whenever the candidate ceases to have a good-faith
belief that a particular record contains a trade secret, it shall promptly notify the City.
(b) Request by Public for Access to Record. When any person requests the City to provide access to a record
designated as a trade secret in accordance with subsection (a) above, the City may
(1) decline the request for access,
(2) notify the candidate of the request and that the City has provided, or intends to provide, the person
access to the record because applicable law requires that the access be granted, or
(3) notify the candidate of the request and that the City intends to decline the request.
Before declining the request, the City may require the candidate to give further assurances so that the City can be
certain that the candidate will comply with subsection (c) below.
(c) Defense of City. If the City declines the request for access to a record designated as trade secrets in
accordance with subsection (a), then, in consideration of the promises in (b) above and for considering the
candidate’s proposal, the candidate agrees that it shall defend, indemnify, and save harmless Indemnitees from
and against all Charges that arise in any manner from, in connection with, or out of the City’s non-disclosure of
the records. In providing that defense, the candidate shall at its sole expense defend Indemnitees with legal
counsel. The legal counsel shall be limited to attorneys reasonably acceptable to the City Attorney.
Definitions. As used in this subsection (c), “Charges" means claims, judgments, costs, damages, losses, demands,
liabilities, fines, penalties, settlements, expenses, attorneys’ fees, and interest. Indemnitees" means the City, and
officers, officials, independent contractors, agents, and employees, of the City. “Indemnitees” does not include
the candidate. The City may require the candidate to provide proof of the candidate’s ability to pay the amounts
that may reasonably be expected to become monetary obligations of the candidate pursuant to this section. If
the candidate fails to provide that proof in a timely manner, the City shall not be required to keep confidential the
records whose non-disclosure gives rise to the potential monetary obligation. Nothing in this agreement shall
require the City to require any person (including the City itself) to be placed in substantial risk of imprisonment, of
being found by a court to be in contempt, or of being in violation of a court order. This subsection (c) is separate
from and is to be construed separately from any other indemnification and warranty provisions in the contract
between the City and the candidate.
85. Reserved.
90. Bonds. No performance bond or payment bond is required for this contract.
100. Insurance. The Contractor agrees to maintain on a primary basis, at its sole expense, and at all times during the life of
this contract the following applicable coverages and limits. The requirements contained herein, as well as the City’s review
or acceptance of insurance maintained by the Contractor, is not intended to, and shall not in any manner, limit or qualify
the liabilities or obligations assumed by the Contractor under this contract.
page 5
Enterprise Architecture Modeling Tool
This is the opportunity summary page. It provides an overview of this opportunity and a preview of the attached documentation.
Daily notification on new contract opportunities
With GovernmentContracts, you can:
- Find more opportunities and win more business
- Receive daily alerts for all new bid opportunities
- Get contract opportunities matched to your business
See also
..., Landscape Architecture, and Related Comprehensive Design and Construction Administration Services for Town... ...
State Government of North Carolina
Bid Due: 6/08/2026
..., professional architectural support services ("Services") to the CLT Architecture Team. All Services... ...
City of Charlotte
Bid Due: 6/24/2026
...Qualifications Category: Architecture, Engineering, & Survey Services Department: Aviation Commodity...
City of Charlotte
Bid Due: 6/23/2026
..., professional architectural support services ("Services") to the CLT Architecture Team. All Services... ...
City of Charlotte
Bid Due: 6/24/2026
* Disclaimer: Information regarding bids, requests for proposals (RFPs), or requests for qualifications (RFQs) is provided on this website only for convenience and does not constitute official public notice. Persons wishing to respond to or inquire about bids, RFPs, or RFQs should contact the appropriate government department.