2-Scedule D General Technical Requirements- ASD12192025HM.pdf

PDF 198 KB Posted

Attached to
Facility & Construction Management Platform Alpine School District
Solicitation number
ASD12192025HM
Issued by
Utah County, Utah

About this file

This is Schedule D of a Request for Proposal issued by Alpine School District in Utah for a Facility & Construction Management Platform (Solicitation #ASD12192025HM). The District, which serves approximately 9,000 employees, 85,000 students, and over 100 buildings/sites, seeks a qualified vendor to provide an AI-enabled facility and construction management platform. The proposal closing date is Friday, December 19, 2025, at 2:00 PM Mountain Time. The resulting contract will be for a maximum of five years, with provisions allowing any newly formed districts resulting from an anticipated reconfiguration of Alpine School District into three separate districts (West, Central, and South) effective July 1, 2027, to enter into agreements with the awarded vendor under identical terms and pricing.

Schedule D outlines comprehensive general technical requirements that bidders must address, covering application integration capabilities including RESTful APIs, identity management solutions, extensible attributes, integration with Alpine's Alio/Linq HR/Finance System, and data migration from current systems. Vendors must detail client and server infrastructure requirements, including whether the solution is SaaS or on-premise based, required equipment and licenses, browser and device compatibility, development environments, and server operating system and database platform specifications. Additional requirements encompass technical support models and escalation processes, security standards including encryption mechanisms, authentication methods (SAML, OAuth, multi-factor authentication), Active Directory integration, incident response procedures, and compliance with the National Data Privacy Agreement. The proposal also requires vendors to address scalability and performance for environments comparable to Alpine's size, auto-provisioning and account management capabilities, role-based access control implementation, and submission of administrative and end-user login screens.

View the file

Other files

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

Alpine School District RFP for:

Facility & Construction Management Platform ASD12192025HM P 6 of 8

490 N State Street, Lindon, UT, 84042 phone (801) 610-8049 fax (801) 796-3116

SCHEDULE ‘D’ – GENERAL TECHNICAL REQUIREMENTS

Name of Bidder: Date:

Phone: Email:

Please answer the following questions. If there is a question or requirement that is not applicable to your platform, please indicate with either N/A or ‘Not Applicable’.

Background Information:

Alpine School District has approximately 9,000 employees, 85,000 students, and over 100 buildings/sites.

Employees have Google and Active Directory accounts.

Application Integration:

1. Alpine is prepared to integrate with RESTful apis. Describe what RESTful apis are currently available for the product. Explain all the input mechanisms available where Alpine may input data into the product. Explain all the output mechanisms. Describe and include the fields available for both date models.

2. Explain how an Identity Management solution would integrate this product. Detail IDM products that have been integrated with the proposed solution.

3. Explain how extensible attributes are used in this product (DB extension).

4. Explain how this product is or can be integrated with Alio/Linq (Alpine’s HR/Finance System).

Explain integration options like those of clever, etc.

5. Explain how data from Alpine’s current system will be consumed by the new system and detail

Alpine’s involvement. Explain how the old system would be phased out.

6. Explain the scope of effort required by Alpine, to implement and integrate (if applicable) the proposed solution. Detail the number of people, time required and what expertise will be required.

7. Explain mobile capabilities both from an administrative perspective and end-user perspective.

Client, Server and Network Infrastructure:

1. Is the solution SaaS or On Premise based, Or are both options proposed and/or available?

2. If the product is to be a local Alpine installation, please include a list of all equipment Alpine must install and any associated licenses/fees for the installation.

3. Explain requirements for the clients (plug-ins, extensions, local software install, dependencies on other software on the workstation (e.g. java), and workstation resources). List devices, browsers, and software that are not supported. (This may be done in general terms).

4. Does the product offer a DEV environment so Alpine can test features before deployment? If so, include in the cost of the product and include any limitations of the DEV environment.

5. Outline all URLs, Ports, protocols, and domains associated with the solution being proposed and how each is used within the network or solution.

6. Detail server OS and DB platforms required for the proposed solution.

7. What system housekeeping of the servers, firmware, and patches would Alpine be expected to complete, and which updates and patches would you as a solutions provider be required to

ASD12192025HM P 7 of 8 perform? Please include EDR, Firewall expectations, ports needed for network traffic, and URL expectations needed to make the product function properly.

8. If the patches and updates are performed by the solution provider, how is this process pursued?

9. Explain the testing that has been done to ensure Alpine will not run into scale or performance issues.

Installation and Support:

1. Explain the tech support model and how Alpine would access support. Explain the escalation process and timeframes associated with support.

2. What is Alpine’s engineering/support obligation for implementation and support of the proposed system?

3. When are the next major changes to the proposed solution going to be released for general use?

4. Explain how maintenance on the product is done such as patches, fixes, and upgrades.

5. Explain any archival capabilities, features and/or requirements.

6. Detail the proposed integration timeline and integration process.

7. Will you commit a dedicated project manager from start to full implementation of the solution?

8. Explain how updates are managed on the system including application software, OS updates, and device firmware. Are there any update limitations to keep in mind? (example: Cannot upgrade the OS past Windows 10 without breaking the software).

Security:

1. Vendor is willing to sign (without modification) the National Data Privacy Agreement (NDPA).

2. How does your organization stay informed about and address emerging security threats and vulnerabilities relevant to the software solutions you provide?

3. Does your organization have documented security policies and procedures in place? If so, can you provide a summary or share relevant documentation?

4. What encryption mechanisms are employed to protect data both in transit and at rest within your software solution?

5. How is sensitive information, such as user credentials and personally identifiable information

(PII), protected within your software solution?

6. Describe the access control mechanisms implemented in your software solution. How are user roles and permissions managed?

7. What authentication methods are supported by your software, such as SAML, OAuth, etc.?

Explain the multi-factor authentication options that are available with the product.

8. Can your solution be integrated with existing identity management systems, such as LDAP, Active Directory, ADFS, or others?

9. What is your organization’s incident response plan? How are security incidents handled, and what is the communication process in the event of a security breach?

10. Describe the login and monitoring capabilities within your software solution. What types of events and activities are logged, and how are logs protected?

11. Does your solution provide support for a SIEM for centralizing logs?

12. What measures are in place to address and remediate security vulnerabilities identified during development or through third-part testing?

13. How does your organization handle data retention and disposal, especially concerning sensitive or personally identifiable information?

14. Where is the software hosted, and what security measures are in place to protect the hosting infrastructure?

ASD12192025HM P 8 of 8

Scalability and Performance:

1. From current installations of this product, describe performance and scalability in environments of the size comparable to Alpine.

2. Explain any known or identified performance issues documented indicating that interaction with an Antivirus/Malware solution may interfere with the solution that you are proposing.

User Accounts – Authentication and Authorization:

1. Alpine depends on auto-provisioning user accounts. The number of accounts in Alpine makes manual provisioning prohibitive. Explain how Alpine can automatically provision, manage, and inactivate user accounts. This would include provisioning new users, deactivating users, and changing user attributes. Confirm that unique User IDs are used as a primary key and give an example of a unique user ID. Include requirements needed to do this including formats of files apis available, etc. Alpine uses employee email prefixes as user long IDs.

2. Explain how user groups are created and maintained.

3. Alpine currently assigns ‘roles’ to each employee. Roles are used for authorization and approvals. Explain the role-based implementation of the product. Explain how the product can consume Alpine’s roles on a regular basis and how Alpine will manage rights for those roles.

4. Submit the login screens for administrative users and end-users.

File details come from the government source that posted it. Updated .