Appendix J

APPENDIX J - MOBILE DIGITAL CAMPUS ASSUMPTIONS


  • Member will provide a publicly accessible Unifyed Studio Middleware URL to Unifyed after deploying the middleware.
    • 2 vCPUs
    • OS: Linux/Ubuntu
    • RAM: 4 GB
    • Hard Disk: 10 GB
    • Software: JDK 7, Tomcat 7.x
    • SSL certificate: SHA256
  • Downtime: If downtime is required, it will be scheduled on weekends and/or during afterhours.
  • If services are required to be performed on-site, travel, lodging, meals/per-diem, and incidentals are billed in addition on actuals at the Member’s expense.
  • Upon execution of this SOW, Unifyed will need to schedule resources for this and will then appropriately slate timelines for the execution of this project.
  • Support cost does not include any enhancements.
  • Any Enhancement that the Member would want on their Mobile Application would be at additional cost based on the scope.
  • Additional Mobile Apps when rolled out will be made available to the Member. However, Professional Services for Implementation and Configuration of Additional Apps will be chargeable. Unifyed team will get the Unifyed Mobile Application approved on the Apple App Store, Android Google play.
  • Unifyed will be responsible for any technical issues during Application approval process in case the application is rejected or returned by any of the listed App Stores on technical grounds.
  • The Member will be responsible for the network connection and access between the Mobile Gateway Server and LDAP applications.
  • The Member will be responsible for sharing required information for the implementation of the mobile app for example RSS feeds, Application Web URLs, test account, etc.
  • Should additional hours be needed per a change request or via support, please see Appendix A: A-La-Carte Add-Ons
  • Maintenance of the mobile app will be covered by Unifyed.
  • Only two rounds of feedback are allowed once the first build is submitted to the Member