Attachment+1+-+Scope+of+Work.xlsx

XLSX spreadsheet 55 KB Posted Dec 17, 2025

Attached to: Days of our Legacy
Solicitation number: 110.7-25-084
Issued by: North Dakota

About this file

Written by GovTribe AI · Dec 19, 2025

Summary

This is a Scope of Work document for the State of North Dakota's "Days of our Legacy" website building and data management project. The solicitation seeks proposals for two primary categories: Category A—Website Creation/Management and Category B—Data Management. The project requires the development of a publicly accessible website available 24/7 with comprehensive content management capabilities, including an "About Us" section, Legacy Fund history, funding information, glossary, and dynamic investment holdings data with advanced filtering, visualization, and reporting functionalities. The solution must support multiple user roles, governance processes, mobile optimization, ADA compliance, and adherence to W3C standards and North Dakota State Brand Guidelines. The contractor must implement the complete website by September 30, 2026, and provide ongoing support including data aggregation and transformation services on either an annual or quarterly schedule. The project requires a Project Management Institute-certified Project Manager and compliance with the state's Project Management Body of Knowledge methodology and Risk Management Framework following NIST 800-37R2 standards.

Offerors must submit responses to all required specifications across IT Solution, Enterprise Specifications, Product Support, and Experience and Qualifications sections, with all costs clearly defined in a separate Cost Proposal Attachment. Mandatory experience requirements include five years of website development and data management experience in government or public sectors, with minimum examples provided (two URLs for Category A). The contractor must provide three professional references per category and detailed resumes for all key personnel. The solution must integrate with the state's Azure Active Directory for authentication, be hosted under the nd.gov domain, and comply with all state security, data classification, and operational standards. Warranty coverage of minimum 90 days is required for both categories, along with comprehensive technical support, service level agreements, documentation, training programs, and maintenance services including regular patches and upgrades.

View the file

Other files

File	Type	Posted
Attachment+3+-+Proposal+Evaluation+Worksheet.xlsx	XLSX spreadsheet	Dec 17, 2025
Attachment+5+-+ND-State-Brand-Guidelines.pdf	PDF	Dec 17, 2025
Attachment+2+-+Cost+Proposal.xlsx	XLSX spreadsheet	Dec 17, 2025
Attachment+4+-+Technology+Contract.docx	DOCX document	Dec 17, 2025
Days+of+our+Legacy+RFP.docx	DOCX document	Dec 17, 2025
Attachment+6+-+Invest.+Holdings+sample.xlsx	XLSX spreadsheet	Dec 17, 2025

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Instructions

INSTRUCTIONS:

Offeror will complete and return this Scope of Work.

Offeror must respond in the "Offeror Response" sections within tabs 3.3 - 3.6 as to how the proposed solution meets each specification and respond in the Offeror Response row. Do not simply restate the specification, but rather provide details on how your solution meets or will meet the specification. Provide any additional technical details required of your proposed solution that you feel the STATE should consider. Offerors must provide a full response to each specification without cross referencing other sections of Offeror's proposal. Offeror may cite other sections of proposal that elaborates on this explanation.

&"Arial,Regular"Requirements Matrix Attachment &K0070C0#

3.3 IT Solution

3.3	INFORMATION TECHNOLOGY SOLUTION
Offerors must provide a full response to each item number without cross referencing other sections of the proposal. Offerors must use the table format and maintain numbering provided by the STATE to respond to each item number. Attachments, documents, or samples must be clearly referenced where in the response they can be found in the applicable item number.
No.	A. SOLUTION Category A - Website Creation/Management
1	Offeror must be able to implement a publicly accessible website, available 24/7.
	Offeror Response:
2	The Offeror’s solution shall provide the capability for RIO staff to update website content at any time without requiring Contractor's or ITD's involvement
	Offeror Response:
3	The Contractor shall provide a comprehensive website solution and ongoing support for the website.
	Offeror Response:
4	The Contractor must implement and maintain an agency-approved governance process to review, validate, and authorize all website updates prior to publication, ensuring compliance with RIOs policies and standards.
	Offeror Response:
5	The Offeror’s solution shall support multiple user roles with configurable permissions, ensuring that all content modifications are subject to review and approval by designated content administrators within RIO prior to publication
	Offeror Response:
9	The Offeror’s solution must provide full optimization for mobile devices, ensuring seamless performance, usability, and accessibility across all major mobile platforms and screen sizes.
	Offeror Response:
10	The Offeror’s solution must support full optimization for a wide range of screen sizes, ensuring consistent functionality, accessibility, and usability across all device types and display resolutions.
	Offeror Response:
11	The Offeror’s solution must include the capability to host and manage multiple website pages, supporting scalable content architecture and future expansion.
	Offeror Response:
12	The Offeror’s solution shall include an ‘About Us’ section with detailed information regarding fund management, including the entities responsible for oversight, their roles, and their responsibilities.
	Offeror Response:
13	The Offeror’s solution must include a dedicated section presenting the history of the Legacy Fund, including background information and a timeline of legislative changes. The solution shall allow this section to be easily updated as new legislation is enacted.
	Offeror Response:
14	The Offeror’s solution shall provide a section that explains how the Legacy Fund is funded, the determination of interest earnings, and the process by which earnings are allocated by the State Legislature, ensuring information is accurate, accessible, and easy for the public to understand.
	Offeror Response:
15	The Offeror’s solution must include a glossary that defines key terms, concepts, and terminology related to investments, presented in a clear and accessible format.
	Offeror Response:
16	The Offeror’s solution must provide dynamic investment holdings data incorporating multiple data points.
	Offeror Response:
17	The Offeror's solution must provide users with flexible filtering functionality to view investment holdings information including but not limited to company, asset class, geography, country, and sector.
	Offeror Response:
18	The Offeror’s solution shall provide functionality to attribute investments to a country of origin (or location), including the ability to display country-level breakdowns, utilize mapping/GIS-enabled dashboards, plot assets on map visualizations, and aggregate holdings data by country.
	Offeror Response:
19	The Offeror’s solution shall provide the capability to display data through interactive visualizations, including maps, charts, choropleth maps, country heatmaps, and other graphical representations, and shall support dynamic drill-down, zoom in/out, and similar advanced data-exploration features.
	Offeror Response:
20	The Offeror's solution shall enable public to download investment holdings reports in commonly used formats such as Excel and CSV.
	Offeror Response:
21	The Offeror's solution shall ensure the integrity of data and provide appropriate contextual information to support user understanding.
	Offeror Response:
22	The Offeror’s solution shall provide the capability to manage, store, and retain historical investment holdings data for a minimum period of six (6) years.
	Offeror Response:
23	The Offeror’s solution shall provide the flexibility for RIO to determine the frequency of investment holdings data updates displayed on the website, including support for either:

(a) annual updates utilizing June 30 data, with publication no later than September 30; or

(b) quarterly updates, with publication no later than three (3) months after the end of each quarter.

	Offeror Response:
24	The Offeror’s solution must implement robust security, governance, and approval controls to ensure that all data displayed on the website is authorized, validated, and protected in accordance with ITD security and data confidentiality requirements.
	Offeror Response:
25	The Offeror's solution shall provide flexible options for requesting feedback, including features that allow for the analysis of the collected data.
	Offeror Response:
26	The Offeror's solution shall gather feedback from users regarding their experience, ease of use and areas for improvement.
	Offeror Response:
27	Offeror must acknowledge that they have reviewed and will comply with Attachment 5 - ND State Brand Guidelines including but not limited to color choices-Primary - State's Harvest Orange, with Accent of Agency's - Summer Green and State Logo.
	Offeror Response:
28	Offeror must acknowledge that they will complete the full implementation of the website by September 30, 2026
	Offeror Response:
No.	B. SOLUTION Category B - Data Management
29	The Offeror's solution must have the functionality to aggregate and transform investment holdings data from various sources, including separately managed accounts and commingled funds.
	Offeror Response:
30	The Offeror’s solution shall provide the capability to automate data aggregation and transformation processes
	Offeror Response:
31	The Offeror’s solution must provide the capability to define and enforce data aggregation rules, enabling validation and verification to ensure the accuracy
	Offeror Response:
32	The Offeror’s solution must provide the capability to define and enforce a data aggregation approval process, supporting ongoing validation, review, and authorization of data prior to publication, in order to ensure accuracy, completeness, and compliance with organizational policies.
	Offeror Response:
33	The Offeror’s solution must implement robust security, governance, and approval controls to ensure that all data designated as confidential is properly protected and is not published or displayed on the website. The solution shall enforce role-based access, review workflows, and administrative safeguards to prevent unauthorized disclosure of restricted information.
	Offeror Response:
34	The Offeror’s solution shall provide the capability to automatically deliver approved data to the website in a format that is compatible with and optimized for the website’s structure.
	Offeror Response:
35	The Offeror’s solution shall provide ongoing data aggregation and transformation services, supporting either of the following publication schedules:

(a) Annual updates using June 30 data, with transformed data delivered to the website for publication no later than September 30; or

(b) Quarterly updates, with transformed data delivered to the website for publication no later than three (3) months following the end of each quarter.

The solution shall ensure that all aggregated and transformed data is accurate, complete, and formatted for seamless integration with the website.

	Offeror Response:
36	The Offeror’s solution shall provide the capability to determine, or allow flexibility in determining, the frequency of website data updates, supporting either annual or quarterly update schedules, as defined by RIO, and ensuring timely and accurate publication of information.
	Offeror Response:
No.	C. LICENSING/SUBSCRIPTION
37	Offeror must describe in detail whether a license or subscription is being offered, including what is covered. Ensure all licensing/subscriptions required to meet the requirements of this RFP are included in your response.
	Offeror Response:

38	Offeror must describe in detail the process to add licensing/subscriptions throughout the term of the Contract.
	Offeror Response:

39	Offeror must describe if any additional licenses/subscriptions purchased during the term of the Contract can be co-termed with the other licenses.
	Offeror Response:

No.	D. PROFESSIONAL SERVICES
40	The STATE seeks professional services provided by the contractor to meet the deliverables as defined in the Contract Deliverables and Estimated Schedule below. Describe your strategy for accomplishing the professional services.
	Offeror Response:
No.	E. PROJECT MANAGEMENT

Project Management for the awarded Contract will be done following the state Project Management methodology as described in the Project Management for Information Technology Standard.

41	Offeror must acknowledge that they are required to provide a Project Manager that is Project Management Institute, Project Management Professional certified during the implementation of this project.
	Offeror Response:
42	Offeror must acknowledge the project shall follow the Project Management Institute’s (PMI) Project Management Body of Knowledge (PMBOK). The Technology Contract - Attachment 4 includes provisions related to Project Management.
	The State’s project manager will prepare a Project Management Plan using the State’s methodology and applicable template: Project Management \| North Dakota Information Technology (nd.gov). The contractor will need to provide information necessary to prepare the plan.
	The State’s project manager will direct and manage the project on a day-to-day basis and will have the primary responsibility for management of the project. The contractor’s project manager and lead consultants will report to the State’s project manager within the project’s governance structure.
	Contractor shall be responsible for the project management related tasks/information specified below.
	a. Collaborate in the development of detailed schedule with fixed deadlines to include:
	i. A work breakdown structure;
	ii. Schedule including tasks, activities, activity duration, sequencing and dependencies;
	iii. Completion date of each task;
	iv. Milestones; including entrance and exit criteria for specific milestones;
	b. Collaborate in the development of the Human Resources Plan to include:
	i. Staff assigned and their location and schedule;
	ii. The project resources required;
	iii. Resource allocation percentage by role;
	iv. Contractor’s resources;
	v. State’s resources.
	c. Collaborate in the development of a Communication Plan including: a plan for generation, documentation, storage, transmission and disposal of project information.
	d. Collaborate in and review of the Risk Management Plan to ensure that risks are identified, planned for, analyzed, communicated and acted upon effectively.
	e. Collaborate in the development of the Training Plan.
	f. Provide a Quality Management Plan to include the methodology for maintaining quality of the code and workmanship, and related subcontractor(s) activities where appropriate.
	g. Provide a Test Management Plan which describes how the contractor, and the STATE shall verify the product meets the requirements.
	h. Collaborate in the development of the Implementation Plan.
	i. Collaborate in the development of the (Organizational) Change Management Plan.
	j. Collaborate in the development of the Transition Plan. This plan shall describe the steps necessary to turn the final deliverables over to the STATE. The plan shall contain sufficient information to assure that all necessary steps are identified and that each step has sufficient resources assigned.
	k. Collaborate in the development of the Project Closeout Report to include participation in the lessons learned exercise.
	Offeror Response:
43	Describe your strategy for accomplishing the Project Management requirements. Provide examples of project management methodologies, tools, and templates used in previous projects that support offeror’s ability to function successfully within North Dakota’s project management framework, including your work breakdown structure and schedule.
	Offeror Response:
No.	F. Contract Deliverables

The STATE has identified the following deliverables which are significant work products or milestones in the project. The STATE requests these deliverables be addressed in the Contract Schedule, as a minimum. The following deliverables may be modified based on contractor’s implementation strategy. These deliverables will be identified within the Scope of Work in the Technology Contract – Attachment 4. The STATE and contractor will agree upon expectations and acceptance criteria for deliverables.

44	a. Project ‘Kick Off’ meeting: within two weeks of Effective Date agreed upon by the parties in the Contract
	b. Project Plan
	i. Integrated project management plan
	ii. Integrated project schedule
	c. Gap Analysis
	d. Solution Design
	e. Interface Design
	f. Environment Set-up
	g. Solution Configuration
	h. Interface Development and Release
	i. Testing Management Plan
	j. Acceptance Testing
	k. Training Management Plan
	l. Training (Train the Trainer Scenario)
	m. Implementation and Transition Plan (Estimated Implementation: September 2026)
	n. Implementation
	o. Post Implementation Report
	p. Project Closeout Meeting
	q. Final Acceptance
	Describe any expectations from the STATE related to each deliverable or milestone.
	Offeror Response:
No.	G. Estimated Schedule Requirements

The contractor shall develop an estimated schedule for accomplishing the Scope of Work, including the identified deliverables.

Upon award, the successful offeror’s proposed project schedule will be reviewed and refined during the planning phase.

45	The draft schedule must contain the following:
	a. A timeline in the number of days or weeks with start and finish dates for deliverables
	b. Contractor and State resources or roles required to perform the tasks in the proposed schedule
	c. Predecessors on all tasks (except summary tasks) to determine critical path and go live
	d. No use of constraints
	Offeror must submit a draft schedule that addresses the deliverables and milestones specifically described in the Scope of Work. The proposed schedule may incorporate other deliverables, work products, milestones, or work breakdown that the offeror feels are significant in the project.
	Offeror must describe in detail the number of STATE staff required to perform work including roles, tasks, hours needed on a weekly basis in the proposed schedule.
	Offeror acknowledges they have reviewed and will follow the steps and best practices for scheduling projects as outlined in the ND PMO Schedule Best Practices document.
	The draft work schedule will cover both offeror and the STATE tasks and responsibilities.
	Offeror Response:
No.	H. Contract
46	The Awardee shall be required to sign a Contract substantially similar to the Contract attached to this RFP (Attachment 4). Offeror must acknowledge that the STATE and the awarded Offeror will execute one Contract for the services necessary to deliver the proposed solution.
	Offeror must acknowledge they have reviewed the Technology Contract – Attachment 4 and included a copy completed according to the instructions in the attachment.
	Offeror Response:

47	Offeror acknowledges they have reviewed and provided requested information in the draft Statement of Work (SOW) in Attachment 4, for their plan to implement the proposed solution.
	Offeror Response:

48	Offeror must describe in detail any end user licensing agreements required. Offeror must acknowledge that they have included any end user licensing agreements required in their response.
	Offeror Response:

No.	I. Risk Management Framework (RMF)
49	RMF follows NIST 800-37R2 and provides business, IT, vendors, and risk management visibility into all stages of the project. The seven-step process includes collaboration from all stakeholders on the following:
	a. Preparing the system (roles and responsibilities)
	b. Categorize the system (Low, Moderate, High)
	c. Select controls to reduce risk
	d. Implementation of controls
	e. Assess controls
	f. Authorize system by the business owner (authorization official)
	g. Continuous monitoring of system controls post go-live
	Artifacts required:
	h. Network diagram
	i. Data flow diagram
	Offeror must acknowledge that they understand the STATE's Risk Management Framework and will assist with documentation on vendor-owned controls to ultimately assist STATE with creating a System Security Plan.
	Offeror Response:
No.	J. COST
50	Offeror must acknowledge that ALL costs are included in the cost proposal and be clearly defined in Cost Proposal Attachment 2. This includes any items that are optional. If the cost is not clearly defined in the Cost Proposal then that feature, item, etc. is included as a part of the solution at no cost.
	Offeror Response:

51	Offeror must acknowledge that have included all of the hourly rates applicable to any of the services in this section in their Cost Proposal. This includes any items that are optional.
	Offeror Response:

K. ADA Compliance

CONTRACTOR (upon award) shall ensure that all public-facing components of the solution comply with the Americans with Disabilities Act (ADA) and conform to current Web Content Accessibility Guidelines at a minimum. Accessibility compliance shall be verified through automated and manual testing prior to delivery and reports provided to STATE quarterly or as mutually agreed upon by STATE and CONTRACTOR. If a compliance issue is discovered, CONTRACTOR will provide a remediation plan, including timelines and impacts, to STATE.

Offeror must acknowledge that they have reviewed and will comply with ADA Compliance.

Offeror Response:

	L. Location of Work
53	While the work itself is not required to take place in Bismarck, ND any proposed trainings or presentations must occur either in-state or online. The Offeror must ensure that all associated costs are clearly detailed in Attachment 2 - Cost Proposal.

The STATE will provide a workspace for the Contractor, if needed.

Offeror Response:

54 M. Value-Added Features The proposed solution may include value-added features. Value-added features include any functionality, products, services, optional modules, or upgrades that are not part of the IT requirements in this RFP. Describe any additional functionality, products, optional modules, upgrades or services that you offer and are not a part of the RFP requirements that you believe would add value to your proposed work on this project.

a.	Offeror shall list the cost of value-added features separately in the Cost Proposal.
b.	The STATE shall not consider these costs as part of cost evaluation scoring.
c.	The STATE reserves the right to include value-added features from the proposals during contract negotiations.
		Offeror Response:

Page &P of &N https://www.ndit.nd.gov/services/professional-services/project-management../../../../-Tm-ITD-Procurement-Collaboration/Shared%20Documents/Procurement%20Templates/Working%20Docs/ND%20PMO%20Schedule%20Best%20Practices

3.4 Enterprise Specs

3.4 ENTERPRISE SPECIFICATIONS

tc={464E9755-2C60-4442-90AE-E3C3CBED65BA}: [Threaded comment]

Your version of Excel allows you to read this threaded comment; however, any edits to it will get removed if the file is opened in a newer version of Excel. Learn more: https://go.microsoft.com/fwlink/?linkid=870924

[Tasks]

There is a task anchored to this comment that cannot be viewed in your client.

Comment:

@Backman, Kevin L. Does vendor has to follow these web development standards for this project? If so, were they included in this tab? If not, do you want me to include it here or I can make this as an attachment for vendors to review and acknowledge.

IT:Standard - Web Development - Team ND - ND Wiki Reply:

Yes, the vendor will have to comply with the web development standard. I think it makes sense to add the standard into this enterprise specs section so that the vendor is aware of the requirements and can provide a response confirming their offered solution will comply with the standard.

Reply:

Can you please specify what exactly needs to be in here from that link?

Reply:

Please use this text:

The solution must follow World Wide Web Consortium (W3C) standards for HTML and CSS. Each public webpage must show the official state banner and may not include advertisements. Every public webpage must also include a link to or display contact information (including address, phone, and email), a privacy policy, a home page link, a security policy, and a disclaimer.

Reply:

@Backman, Kevin L. please review this tab and let me know if anything is missing. Just wanted to make sure that we provide all the IT standards information for offerors to review and acknowledge.

Reply:

This looks good. Nothing is missing.

Reply:

Sounds good!

Offerors must provide a full response to each item number without cross referencing other sections of the proposal. Offerors must use the table format and maintain numbering provided by the STATE to respond to each item number. Attachments, documents, or samples must be clearly referenced where in the response they can be found in the applicable item number.
	A. Enterprise IT Standards
1	The solution will only authenticate state users by integrating with the STATE's Azure Active Directory and/or Active Directory. A state user is any state official, state employee or other person authorized to act on behalf of the state.

Offeror must describe how the proposed solution will comply with the STATE's State Entity Authentication standard.

	Offeror Response:
2	The solution must follow World Wide Web Consortium (W3C) standards for HTML and CSS. Each public webpage must show the official state banner and may not include advertisements. Every public webpage must also include a link to or display contact information (including address, phone, and email), a privacy policy, a home page link, a security policy, and a disclaimer.
	Offeror Response:
3	All publicly accessible services provided by the solution will be served under the STATE's nd.gov domain name.

Offeror must describe how the proposed solution will comply with the STATE's Domain Name standard.

	Offeror Response:
	B. Architecture
4	Offeror must describe in detail the architecture of the proposed solution and supporting infrastructure.
	a. Include the technology stack, including the software products used to create the solution
	b. Include the network architecture, including security levels, connectivity points, and capacity
	c. Include the storage architecture, including security controls (i.e. encryption)
	d. Include related architectural diagrams
	Offeror Response:
	a.
	b.
	c.
	d.
5	Offeror must describe the solution’s integration points with other applications or datasets, and other external dependencies.
	Offeror Response:
6	Offeror must describe the solution’s ability to provide high availability.
	Offeror Response:
7	Offeror must describe the solution’s ability to be enhanced to implement changing business and technical requirements.
	Offeror Response:
8	Offeror must describe the solution’s ability or limitations for migrating solution elsewhere in the future with regard to either party terminating services.
	Offeror Response:
	C. Data
9	Any DATA provided by the STATE must be accessible to the STATE at any time.

Offeror must describe how the proposed solution ensures the STATE can access all provided data anytime (API, SQL, batch export, etc.) and detail data export options (formats, ETL, encryption, required software) for portability evaluation by the STATE.

	Offeror Response:
10	Offeror must describe the controls used to insure data is properly classified and how sensitive/confidential data is safeguarded.
	Offeror Response:
11	Offeror must describe the practices and procedures used to provide Electronic Discovery of specific records or data, and any legal positions regarding subpoenas, jurisdiction and potential confiscation of data.
	Offeror Response:
	D. Artificial Intelligence
12	Offeror must indicate if the proposed solution uses Artificial Intelligence (AI) and Machine Learning (ML) technology, model, or service. If yes, answer the remaining questions in this section.
	Offeror Response:
13	Offeror must indicate AI and/or ML model name.
	Offeror Response:
14	Offeror must indicate model owner.
	Offeror Response:
15	Offeror must describe in detail the purpose.
	Offeror Response:
16	Offeror must describe in detail the intended domain.
	Offeror Response:
17	Offeror must describe in detail the model training data.
	Offeror Response:
18	Offeror must describe in detail the model information.
	Offeror Response:
19	Offeror must describe in detail the inputs and outputs.
	Offeror Response:
20	Offeror must describe in detail the performance metrics.
	Offeror Response:
21	Offeror must describe in detail the optimal conditions.
	Offeror Response:
22	Offeror must describe in detail the poor conditions.
	Offeror Response:
23	Offeror must describe in detail the bias.
	Offeror Response:
24	Offeror must describe in detail the test data.
	Offeror Response:
	E. Security
25	Offeror must describe if the proposed solution is FedRAMP, HITRUST, or StateRAMP authorized.

If no, are there plans to seek authorization?

SaaS solutions containing Federal Tax Information, Social Security Administration, or Criminal Justice Information must be FedRAMP authorized.

	Offeror Response:
26	Offeror must describe the controls used to measure and meet regulatory requirements and certifications. Include any Application Scanning reports, Vulnerability Scanning reports, and Penetration Testing reports. Include schedules for recurring/updated reports.
	Offeror Response:
27	Offeror must describe the controls used to manage operational logs for troubleshooting and regulatory compliance.
	Offeror Response:
28	Offeror must describe the controls used to ensure that privileged users cannot perform unauthorized or unlawful activities.
	Offeror Response:
29	Offeror must describe in detail the ability to configure and implement a session timeout due to inactivity.
	Offeror Response:
30	Offeror must describe in detail the proposed solution's privacy and consent controls.
	Offeror Response:
	F. Non-State Hosted Solutions. State law, N.D.C.C. § 54-59-22 requires ITD or an ITD approved vendor host all information technology systems unless a hosting exemption is granted. If the hosting exemption is not approved, the STATE will reject the proposal as being not responsive to this hosting approval requirement.
31	Offeror must describe in detail :
	a. The hosting location
	b. If the hosting locations distributed geographically
	c. If hosted by a third party list the name of hosting party
	Offeror Response:
	a.
	b.
	c.
32	Offeror must describe the data center operational controls and policies, and provide any relevant audit reports, including Statement on Standards for Attestation Engagements (SSAE) Service Organization Control (SOC) 2 Type II audit or equivalent such as ISO 27001 for the primary vendor and any 3rd party providers/partners. Include any options for the STATE to access the vendor datacenter(s). Include any “Right to Audit” clauses available to the STATE.
	Offeror Response:
33	Offeror must describe the backup procedures, including off-site storage, encryption, and the frequency of restore testing.
	Offeror Response:
34	Offeror must describe the practices and procedures used to manage/monitor data retention schedules and the purging or archival of data when retention schedules are met.
	Offeror Response:
35	Offeror must describe any options for the STATE to run application security scanning software against the hosted solution.
	Offeror Response:
36	Offeror must describe the controls, tools, and procedures in place to handle natural disasters and maintain business continuity. Include the Recovery Point Objective (RPO) and Recovery Time Objective (RTO).
	Offeror Response:

IT:Standard - Web Development - Team ND - ND Wiki

1827263036Yes, the vendor will have to comply with the web development standard. I think it makes sense to add the standard into this enterprise specs section so that the vendor is aware of the requirements and can provide a response confirming their offered solution will comply with the standard.

Can you please specify what exactly needs to be in here from that link?

Please use this text:

@Backman, Kevin L. please review this tab and let me know if anything is missing. Just wanted to make sure that we provide all the IT standards information for offerors to review and acknowledge.

This looks good. Nothing is missing.

Sounds good!

3.5 Prod Support

3.5	PRODUCT SUPPORT
Offerors must provide a full response to each item number without cross referencing other sections of the proposal. Offerors must use the table format and maintain numbering provided by the STATE to respond to each item number. Attachments, documents, or samples must be clearly referenced where in the response they can be found in the applicable item number.
No.	A. WARRANTY
1	Offeror must provide a minimum 90 day warranty for category A ONLY. The STATE will consider options for additional warranty coverage. Describe the offered warranty period and what is covered under warranty
	Offeror Response:
2	Offeror must provide a minimum 90 day warranty for category B ONLY. The STATE will consider options for additional warranty coverage. Describe the offered warranty period and what is covered under warranty
	Offeror Response:
3	Offeror must describe any differences between warranty benefits and software maintenance benefits.
	Offeror Response:
4	Offeror must describe the suggested warranty language for incorporation into the Contract.
	Offeror Response:
5	Offeror must describe any warranty exclusions.
	Offeror Response:
6	Offeror must confirm all costs associated with warranties are clearly outlined in the Cost Propopsal.
	Offeror Response:
	B. TECHNICAL SUPPORT
7	Offeror must describe in detail the following:
	a. What are your technical support options for handling inquiries and maintenance support? Also provide a problem resolution process diagram.
	b. Offerors must describe in detail the service level agreements for the proposed solution and include how service level credits are issued if the service levels are not achieved.
	c. Is documentation available for the system administrator and support for end users (i.e. online knowledge base help and user’s manuals, etc.…)? Please explain.
	d. Is your support staff located at a call center? If so, where?
	e. What are your support hours?
	f. Describe if you meet the response times listed in the Technology Contract – Attachment 4 and describe any reports available to STATE for validation. Do you offer anything above those listed?
	g. Provide help desk employees’ qualifications.
	Offeror Response:
	a.
	b.
	c.
	d.
	e.
	f.
	g.
	C. Training
8	a. Offeror must describe Initial training and start-up services.

b. Offeror must describe Ongoing training programs.

	Offeror Response:
	a.
	b.
	D. Maintenance and Upgrades
9	Offeror must describe in detail how software maintenance is handled.
	Offeror Response:

10	Offeror must describe in detail when the STATE will be required to pay for maintenance prior to first production use and the maintenance payment process.
	Offeror Response:

11	Offeror must describe in detail the upgrades and technical support that is included with the software maintenance.
	Offeror Response:

12	Offeror must describe in detail any software maintenance requirements.
	Offeror Response:

13	Offeror must describe in detail the process for issuing maintenance releases and patches.
	Offeror Response:

14	Offeror must describe in detail your major and minor release cycles, including the frequency of upgrades or release cycles.
	Offeror Response:

15	Offeror must describe in detail the typical down time required for major and minor upgrades.
	Offeror Response:

16	Offeror must describe in detail the estimated level-of-effort required to perform an upgrade.
	Offeror Response:

17	Offeror must describe in detail the process for upgrading and applying patches to solution.
	Offeror Response:

18	Offeror must describe in detail how are the customizations or configurations maintained during an upgrade.
	Offeror Response:

19	Describe the controls and processes used to detect, report, and resolve disruptions in service, including scheduled outages.
	Offeror Response:

	E. Customer Service & Account/Contract Representative Support
20	Describe the following:
	a. Account representative experience with the products and services being offered.
	b. Vendor process for handling customer inquiries and response time.
	c. Ongoing product updates and strategic planning.
	d. Reports related to technical support performance under the contract.
	e. A website for sales and customer support of the contract.
	Offeror Response:

	a.
	b.
	c.
	d.
	e.
21	Offeror must provide information on the point of contact for questions relating to the proposal:
	a. name,
	b. title,
	c. phone number,
	d. e-mail address
	Offeror Response:
	a.
	b.
	c.
	d.
22	Offeror must provide a narrative of the dedicated contract representative and include:
	a. name,
	b. title,
	c. phone number,
	d. e-mail address
	Offeror Response:
	a.
	b.
	c.
	d.

3.6 Exp & Qual

3.6	EXPERIENCE AND QUALIFICATIONS
Offerors must provide a full response to each item number without cross referencing other sections of the proposal. Offerors must use the table format and maintain numbering provided by the STATE to respond to each item number. Attachments, documents, or samples must be clearly referenced where in the response they can be found in the applicable item number.
No.	A. PRIOR EXPERIENCE
1

Offerors must meet the following mandatory experience and qualification requirements: Category A In order for the STATE to consider offers to be responsive, Offerors must meet the minimum prior experience requirements. An Offeror’s failure to meet these minimum prior experience requirements will cause the STATE to consider its proposal non-responsive and the STATE will reject its proposal. The minimum experience requirements are:

Five-years of experience in website development in government sector or public organization.

Offeror will be required to provide minimum of two URLs of sites the firm developed describing the degree of firm’s involvement.

	Offeror Response:
2

Offerors must meet the following mandatory experience and qualification requirements: Category B In order for the STATE to consider offers to be responsive, Offerors must meet the minimum prior experience requirements. An Offeror’s failure to meet these minimum prior experience requirements will cause the STATE to consider its proposal non-responsive and the STATE will reject its proposal. The minimum experience requirements are:

Five-years of experience in data management in government sector or public organization.

	Offeror Response:
3	Describe the number of years the offeror has provided the type of work requested in this RFP. Describe specific experience of their firm in completing similar projects. Provide a description of the project, approximate time frame of the project, and contact information for the customer.
	Offeror Response:
4	Offeror must list and describe in detail projects similar to those sought by this RFP that the Offeror has provided to governmental entities.
	Offeror Response:
5	The Offeror must provide the following general background information:
	a. Name, address, telephone number, and e-mail address of the Offeror including all d/b/a’s or assumed names or other operating names of the Offeror and any local addresses and phone numbers.
	b. Number of years in business.
	c. The location(s) including address and telephone numbers of the offices and other facilities that relate to the Offeror’s performance under the terms of this RFP.
	Offeror Response:
	a.
	b.
	c.
6	Offeror must indicate if they intend to use subcontractors, the offeror must identify in the proposal the names of the subcontractors and the portions of the work the subcontractors will perform.
	Offeror must provide a statement that the offeror will ensure that the subcontractor has or will obtain any required licenses and registrations, including registration with the North Dakota Secretary of State.
	Offeror Response:
No.	B. PROJECT TEAM - Cat A
7	Offeror must provide a designated executive level contact that will act as a point of contact for any issues that need escalation or to discuss the needs of the STATE. This point of contact will be required to participate in any requested demonstration or presentation requested during the RFP process. They will discuss how the contract will be supported and how the Offeror and STATE will work together to ensure a successful outcome.
	Offeror Response:
8	Provide a narrative or organizational chart that describes the organization of the proposed project team. Provide information for key project team members, including:
	a. Description of anticipated work they will perform and approximate estimated hours;
	b. Resume or description of the relevant education, training, experience, skills and qualifications;
	c. If the offeror has vacant positions, identify the job description and minimum qualifications for staff members to be recruited;
	d. Subcontractors. If an offeror intends to use subcontractors, the offeror must identify in the proposal the names of the subcontractors and the portions of the work the subcontractors will perform. Provide a statement that the offeror will ensure that the subcontractor has or will obtain any required licenses and registrations, including registration with the North Dakota Secretary of State; and
	e. Joint Venture. If submitting a proposal as a joint venture, offeror must submit a copy of the joint venture agreement that identifies the parties involved and its rights and responsibilities regarding performance and payment.
	Offeror Response:
	a.
	b.
	c.
	d.
	e.
9	The Offeror must provide resumes for all key personnel of the Offeror who will be involved in providing the goods and/or services contemplated by this RFP. The personnel listed must be the people that will perform/provide goods and services for the STATE. The following information must be included in the resumes:
	a. Full name
	b. Role
	c. Education including degrees, relevant certifications, and the institution from which they were obtained
	d. Years of experience and employment history particularly as it relates to the requirements of the RFP
	e. Description of the type of work the individual shall perform
	f. A detailed description of relative experience in the items listed in this RFP
	Offeror Response:
10	If the Offeror is proposing any subcontractors, Offeror must provide resumes for all subcontractors who will be involved in providing the goods and/or services contemplated by this RFP. The personnel listed must be the people that will perform/provide goods and services for the STATE. The following information must be included in the resumes:
	a. Company Name
	b. Full name
	c. Role
	d. Education including degrees, relevant certifications, and the institution from which they were obtained
	e. Years of experience and employment history particularly as it relates to the requirements of the RFP
	f. Description of the type of work the individual shall perform
	g. A detailed description of relative experience in the items listed in this RFP
	Offeror Response:
11	Joint Venture. If submitting a proposal as a joint venture, offeror must submit a copy of the joint venture agreement that identifies the parties involved and its rights and responsibilities regarding performance and payment.
	Offeror Response:
No.	B. PROJECT TEAM - Cat B
12	Offeror must provide a designated executive level contact that will act as a point of contact for any issues that need escalation or to discuss the needs of the STATE. This point of contact will be required to participate in any requested demonstration or presentation requested during the RFP process. They will discuss how the contract will be supported and how the Offeror and STATE will work together to ensure a successful outcome.
	Offeror Response:
13	Provide a narrative or organizational chart that describes the organization of the proposed project team. Provide information for key project team members, including:
	a. Description of anticipated work they will perform and approximate estimated hours;
	b. Resume or description of the relevant education, training, experience, skills and qualifications;
	c. If the offeror has vacant positions, identify the job description and minimum qualifications for staff members to be recruited;
	d. Subcontractors. If an offeror intends to use subcontractors, the offeror must identify in the proposal the names of the subcontractors and the portions of the work the subcontractors will perform. Provide a statement that the offeror will ensure that the subcontractor has or will obtain any required licenses and registrations, including registration with the North Dakota Secretary of State; and
	e. Joint Venture. If submitting a proposal as a joint venture, offeror must submit a copy of the joint venture agreement that identifies the parties involved and its rights and responsibilities regarding performance and payment.
	Offeror Response:
	a.
	b.
	c.
	d.
	e.
14	The Offeror must provide resumes for all key personnel of the Offeror who will be involved in providing the goods and/or services contemplated by this RFP. The personnel listed must be the people that will perform/provide goods and services for the STATE. The following information must be included in the resumes:
	a. Full name
	b. Role
	c. Education including degrees, relevant certifications, and the institution from which they were obtained
	d. Years of experience and employment history particularly as it relates to the requirements of the RFP
	e. Description of the type of work the individual shall perform
	f. A detailed description of relative experience in the items listed in this RFP
	Offeror Response:
15	If the Offeror is proposing any subcontractors, Offeror must provide resumes for all subcontractors who will be involved in providing the goods and/or services contemplated by this RFP. The personnel listed must be the people that will perform/provide goods and services for the STATE. The following information must be included in the resumes:
	a. Company Name
	b. Full name
	c. Role
	d. Education including degrees, relevant certifications, and the institution from which they were obtained
	e. Years of experience and employment history particularly as it relates to the requirements of the RFP
	f. Description of the type of work the individual shall perform
	g. A detailed description of relative experience in the items listed in this RFP
	Offeror Response:
16	Joint Venture. If submitting a proposal as a joint venture, offeror must submit a copy of the joint venture agreement that identifies the parties involved and its rights and responsibilities regarding performance and payment.
	Offeror Response:
	D. REFERENCES - Cat A
17	Offeror must provide three (3) references for similar projects. The Offeror must include the following contact information for each reference:
	a. person's name
	b. telephone number
	c. e-mail address
	d. A narrative of the project
	The Offeror must verify the accuracy of all contact information.
	The STATE reserves the right to contact other state and local government agencies and entities regarding engagements they may have had with the Offeror’s company in the past, in addition to the references provided in the proposal.
	Offerors are instructed to notify the reference that the STATE will be contacting them. Evaluation will be impacted if the STATE is unable to contact the reference or the reference does not timely provide the requested information.
	Offeror Response:
	Reference 1
	a.
	b.
	c.
	d.
	Reference 2
	a.
	b.
	c.
	d.
	Reference 3
	a.
	b.
	c.
	d.
18	Offeror must provide one (1) reference for a similar project for every proposed subcontractor. The subcontractor must include the following contact information for each reference:
	a. person's name
	b. telephone number
	c. e-mail address
	d. A narrative of the project
	The Offeror must verify the accuracy of all contact information.
	The STATE reserves the right to contact other state and local government agencies and entities regarding engagements they may have had with the Offeror’s company in the past, in addition to the references provided in the proposal.
	Offerors are instructed to notify the reference that the STATE will be contacting them. Evaluation will be impacted if the STATE is unable to contact the reference or the reference does not timely provide the requested information.
	Offeror Response:
	Reference 1
	a.
	b.
	c.
	d.
	D. REFERENCES - Cat B
17	Offeror must provide three (3) references for similar projects. The Offeror must include the following contact information for each reference:
	a. person's name
	b. telephone number
	c. e-mail address
	d. A narrative of the project
	The Offeror must verify the accuracy of all contact information.
	The STATE reserves the right to contact other state and local government agencies and entities regarding engagements they may have had with the Offeror’s company in the past, in addition to the references provided in the proposal.
	Offerors are instructed to notify the reference that the STATE will be contacting them. Evaluation will be impacted if the STATE is unable to contact the reference or the reference does not timely provide the requested information.
	Offeror Response:
	Reference 1
	a.
	b.
	c.
	d.
	Reference 2
	a.
	b.
	c.
	d.
	Reference 3
	a.
	b.
	c.
	d.
18	Offeror must provide one (1) reference for a similar project for every proposed subcontractor. The subcontractor must include the following contact information for each reference:
	a. person's name
	b. telephone number
	c. e-mail address
	d. A narrative of the project
	The Offeror must verify the accuracy of all contact information.
	The STATE reserves the right to contact other state and local government agencies and entities regarding engagements they may have had with the Offeror’s company in the past, in addition to the references provided in the proposal.
	Offerors are instructed to notify the reference that the STATE will be contacting them. Evaluation will be impacted if the STATE is unable to contact the reference or the reference does not timely provide the requested information.
	Offeror Response:
	Reference 1
	a.
	b.
	c.
	d.

File details come from the government source that posted it. Updated Dec 19, 2025.