Attachment A.pdf

ATTACHMENT A –

Program Requirements (Submit with offer)

Program Requirements - Offeror will indicate a “Yes” or “No” response for each technical feature in the table below.

Technical Feature Yes No

1. Web-based user interface

2. Support for the latest versions of Edge

3. Support for the latest versions of Firefox

4. Support for the latest versions of Safari

5. Support for the latest versions of Chrome

6. Secured log-in and role-based permissions

7. Single sign-on with other applications

8. LDAP server integration

9. Active Directory integration

10. ADFS server integration

11. Uses 3rd party SSL certificate encryption

12. No programming required from IT staff

13. All Export and Import programming provided by vendor

17. Support for mobile devices

18. Installed as hosted solution

19. Installed as a SaaS solution

20. Installed at PTC on VM Platform

21. Installed on Stand Alone Servers

22. Experience with higher education and Ellucian’s Banner system

23. Solution supports Ellucian Ethos API Integration with Banner

Offeror will provide responses to the questions below. (If the question is not applicable to the solution being offered, please make a notation to that effect. Do not leave questions unanswered.)

Cloud/Saas Service Questions Offeror Responses

1. Security

i. Please explain the security built into the software to protect data.

ii. How is data uploaded to your environment?

iii. Please explain your data and physical security practices?

iv. Please provide procedures for data and system access, data retention, disposal and replacement of hard drives and disposal of backup tapes.

v. What are the firewall port requirements?

vi. Do you have specific IP’s that can be matched to firewall rules?

vii. For full functionality of your solution do any existing systems at PTC need to be exposed through the firewall?

(Such as LDAP to make PTC work)

viii. Is the system in a shared environment or will PTC have a dedicated system or instance of your solution?

2. Solutions Provider Database

i. Explain how the data is stored and secured within the database.

ii. What database software is used and are the security patches applied regularly if the DB is integrated into the product?

3. Supportability / IT Roadmap

i. What service level agreements do you provide for hosted or cloud based solutions?

ii. What are the levels of technical support? Please include any

iii. SLA’s, hours of support and response times.

4. System Requirements

i. Are there any limitations on file storage or file size?

ii. Are there any additional charges if the college uses more space than originally predicted?

iii. If the client is required to install a client package, please describe the package and all requirements.

iv. If the client is browser based, what other software or browser Plug-ins are needed?

v. What browsers are supported?

vi. Do you support the release channels for Internet

Explorer, Firefox and Chrome?

vii. Describe all integration methodologies required by the software.

5. Single Sign On

i. Does the solution support single sign-on?

ii. Do you support SSO through Active Directory federation services?

6. Physical Security

i. The equipment hosting the application for PTC must be located in a physically secure facility. Please describe the physical security of the environment. Include information regarding generator backup, fire suppression system, and redundant cooling systems, if applicable.

ii. The contractor must list the physical locations where any of PTC data is stored, primary and DR sites. Note: No PTC data can be stored outside the continental United States.

7. Data Ownership, Usage, and Breach Notification

i. PTC will retain all rights and ownership of data.

If/When the contract terminates, the vendor must provide assistance to PTC in retrieving all data in a usable format. PTC will pay no additional fees for this service.

ii. Contractor must provide a copy of the data in a usable format. Acceptable formats are CSV files, Access Database, or Excel Spreadsheets.

iii. The Contractor will not use or share PTC data for or by any other means other than expressed in the policy.

iv. If the Contractor utilizes a third party provider to help provide service to the application PTC must be notified and approve in writing of the data sharing prior to any exchange taking place.

v. Upon PTC leaving the Contract or upon request in writing, and after PTC retrieves it’s data, the Contractor must destroy all data utilizing secure erasure. This includes all backup media as well.

vi. PTC must be notified of any breach taken place with the Contractor. All notification from the Contractor and Piedmont Technical College of a data breach is governed by the State of South Carolina law. If the Contractor is located in another state the Contractor must agree to adhere to the standards and timelines set forth by the State of South Carolina.

vii. All PTC data must be housed, transmitted, and processed in the United States of America only.

8. Disaster Recovery

1. The Contractor must provide a copy of the Disaster Recovery plan or a detailed technical overview of the plan including any updates or changes on-going. Plans must be produced to the Chief Information Officer.