Program Management System

The Vendor is required to provide program management system for its unique educational framework, students, faculty, and administrative needs.
- This system will centralize all programmatic data from multiple inputs, providing an all-encompassing platform for assessments, student progress tracking, volunteer coordination, accreditation reporting, and employment tracking.
- Technical requirements
A. User interface
1. Browser compatibility (if UI is browser based)
•    Offers shall identify all platforms and browsers compatible with proposed solution
2. Client (if UI is installed on local systems)
•    Offerors shall identify all operating systems and platforms compatible with proposed solution 
•    Solution should not require client-side java but if required, shall be compatible with the then current version of java 
•    Solution should not require client-side flash but if required, shall be compatible with the then current version of flash
3. Mobile compatibility
•    Offerors shall identify all mobile platforms compatible with proposed solution. 
•    Prefer iOS because > 80% of all mobile traffic on campus is iOS, but should also support other platforms.
4. Virtual desktop compatibility
•    Offerors shall identify if virtual desktop configuration is possible and if so, what virtual desktop configurations are compatible with proposed solution.
B. Application architecture
•    Solution shall utilize currently supported versions of application frameworks (java, PHP, etc.) 
•    Any compatibility or interoperability with desktop productivity tools (Microsoft office, etc.) 
•    The application programming interface (API) if available. 
•    The application server environment required for the proposed solution. 
•    Software sold or licensed to city to be installed, maintained, or run by to personnel must not have a dependency on oracle java, unless licensing and maintenance costs for oracle java, for the life of the product, are included in the purchase price. 
•    Preference for software based on java technology will be given to vendors utilizing the OpenJDK framework. 
•    Recommended architectural designs provided by the offeror shall be resilient and able to be run with a minimum of downtime in a cloud environment. 
•    No flash
C. Database services
•    Solution shall be compatible with one of the following currently supported database technologies: oracle or MS SQL 
•    Provide technical documentation regarding configuration and installation including backup and maintenance scripts for proposed solution
D. Web services
•    Solution shall be compatible with cu’s web server hosting requirements:
o    For Linux-based systems
o    For windows-based systems
•    Oracle enterprise Linux is a variant of RedHat enterprise Linux (RHEL)
E. Accessibility
1. Provide an accessibility conformance report (ACR) for their solution
•    The ACR must be based on a voluntary product accessibility template® (VPAT®) version 2.3 or higher, provided by the industry technology industry council (ITIC). 
•    The ACR must include conformance to web content accessibility guidelines (WCAG) version 2.3 levels A and AA. 
•    The ACR must be completed according to the instructions. 
•    If the solution has multiple forms (i.e. Web version, desktop version, and mobile app), then either the provided ACR clearly covers the results of each form or an ACR for each form is provided.
2. Provide a supplemental accessibility statement including the following:
•    The offeror’s commitment to providing accessible solutions.
•    Processes and practices used to ensure accessibility, including the frequency in which the ACR is renewed.
•    A list of any unsupported or partially supported criteria in the ACR that have since been remediated.
•    A roadmap, including target dates, for remediation of all applicable criteria in the ACR that are not listed as supported.
•    Any accessibility or usability features provided by the solution.
•    Any known accessibility limitations of the solution.
•    Any configuration or installation requirements to provide accessibility.
•    Contact information for reporting accessibility issues.
3. If the solution is an authoring tool used to generate electronic content (e.g. Documents, web pages, multimedia):
•    The solution generates accessible content. 
•    Provide documentation to guide end users in the generation of accessible content. 
•    Provide samples of accessible generated content.
F. Disaster recovery
•    Software shall be compatible with current cu disaster recovery strategies that can meet the business expected recovery time objective (RTO) and recovery point objective (RPO).
G. Integration
•    Authentication
o    Solution shall support one of the following for end-user authentication (not required for administrator access)
•    Shibboleth (preferred)
•    Active directory authentication integration (preferred)
•    Secure LDAP authentication
o    Sha-1 user and password hashing - any stored passwords must be encrypted
•    API for provisioning - solution should support one of the following
o    Rest (preferred)
o    Soap
o    NETIQ IDM driver
o    Other http based protocols.