Attachment+A+-+Enterprise+Specifications.docx
DOCX document 32 KB Posted
- Attached to
- Hematology Analyzer
- Solicitation number
- 325-24-900-080
- Issued by
- Stutsman County, North Dakota
About this file
This is an Enterprise Specifications document (Attachment A) detailing technical requirements for an IT solution proposal. The document outlines specifications across five main areas: Enterprise IT Standards, Architecture, Data, Artificial Intelligence, and Security. The specifications require integration with the State's Azure Active Directory/Active Directory for user authentication and detail requirements for architecture, data management, and security controls.
The document is formatted as a questionnaire with 16 detailed response items that offerors must complete, focusing on technical capabilities including system architecture, data accessibility, security measures, and compliance requirements. Notable requirements include FedRAMP, HITRUST, or StateRAMP authorization considerations, detailed security controls, data classification protocols, and specific provisions for handling sensitive information. The document does not include pricing terms, set-asides, incumbent information, or specific funding requirements.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Amendment+2+extension+deadline.docx | DOCX document | |
| Amendment+1+QandA.docx | DOCX document | |
| IFB+325-24-900-080_Hematology+Analyzer_Final.docx | DOCX document | |
| Amendment+3+extension+deadline_2-4-25.docx | DOCX document | |
| Amendment+4+extension+deadline_2-7-25.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
ATTACHMENT A
ENTERPRISE SPECIFICATIONS
Offerors shall provide answers to each question.
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:
B. Architecture
| 2 |
| 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.
| 3 |
| Offeror must describe the solution’s integration points with other applications or datasets, and other external dependencies. |
Offeror Response:
| 4 |
| Offeror must describe the solution’s ability to provide high availability. |
Offeror Response:
| 5 |
| Offeror must describe the solution’s ability to be enhanced to implement changing business and technical requirements. |
Offeror Response:
| 6 |
| 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
| 7 |
| 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:
| 8 |
| Offeror must describe the controls used to ensure data is properly classified and how sensitive/confidential data is safeguarded. |
Offeror Response:
| 9 |
| 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
| 10 |
| Offeror must indicate if the proposed solution uses GenAI technology, model, or service. |
Offeror Response:
E. Security
| 11 |
| 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:
| 12 |
| 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:
| 13 |
| Offeror must describe the controls used to manage operational logs for troubleshooting and regulatory compliance. |
Offeror Response:
| 14 |
| Offeror must describe the controls used to ensure that privileged users cannot perform unauthorized or unlawful activities. |
Offeror Response:
| 15 |
| Offeror must describe in detail the ability to configure and implement a session timeout due to inactivity. |
Offeror Response:
| 16 |
| Offeror must describe in detail the proposed solution's privacy and consent controls. |
Offeror Response:
File details come from the government source that posted it. Updated .