1. Access and Compliance o Provide real-time, 24/7 access to SDS for all system employees and students. o Fully comply with OSHA regulations for SDS accessibility and management. o Be accessible through all major browsers and mobile devices. 2. System Structure o Support a multi-tenant architecture, enabling each college, university, or campus to: ▪ Maintain a separate SDS repository under a unified Minnesota State system account. ▪ Search, view, and manage SDS by institution-specific parameters. ▪ Independently manage their SDS content, including: ▪ Uploading/removing SDS files. ▪ Organizing or categorizing SDS. ▪ Assigning institution-specific user roles and permissions. 3. User Access & Permissions o Support role-based access controls (e.g., Administrator, Editor, Viewer) for different user types (e.g., students, EHS personnel, faculty). o Provide secure user authentication, with the ability to integrate with SSO (if feasible but not required). 4. Security and Data Protection o Comply with state cybersecurity and data privacy standards (e.g., FERPA where applicable). o Include safeguards for protecting institutional data and access logs. o Offer audit trails and activity tracking per user account. 5. Mobile and Offline Functionality o Support mobile-responsive design or provide dedicated apps. o Allow for offline access or downloadable SDSs for emergency response and remote locations. 6. Scalability and Reliability o Be capable of supporting all Minnesota State institutions without performance degradation. o Include a 99.9% uptime guarantee and clear service level agreements (SLAs). o Offer redundancy, backup, and disaster recovery protocols. 7. Training and Support Description o Provide implementation support, onboarding sessions, and user training (live or recorded). o Include administrator guides, training materials, and best practices documentation. o Offer ongoing technical support (phone, email, and/or ticket-based). o Identify any costs associated with training or support tiers. 8. System Implementation and Transition o Provide a detailed implementation timeline including setup, configuration, data import (if needed), and go-live support. o Describe tools and resources available to support migration from existing SDS systems (if applicable).
