The primary purpose of these roles will be to help with developing necessary integrations between Colleague and associated applications, as well as support needed to prepare Colleague for the migration. This may include data remediation and process changes necessary to be SaaS compliant. The college anticipates positions could be assigned a minimum of 40 hours per week, more hours could be added based on demand and budget. Work will be done as a remote position with regularly scheduled check-in meetings. it is preferred all augmented staff will have a minimum of 5 years of experience with SaaS migrations of Colleague.

Supplier shall provide professional resumes for proposed individuals or at minimum the process to obtain candidates for presentation to the College. The College has the right to approve and or request new programmers throughout the term of the contract

The following are the current guidelines as supplied by Ellucian on the types of remediation that that may be needed and should be considered a guide for all work but not an exhaustive list:

Custom Subroutines used in hooks are permitted (i.e. on a parameter form such as a transcript print subroutine, AP check print subroutine). The custom subroutine cannot perform updates to any data, but may do so indirectly by calling a base product subroutine that updates data.

Custom Computed Columns are permitted. In SaaS custom computed columns are mainly used in run-time on rules, communications management, etc. Computed columns that were used for queries/ reporting are typically replaced by SQL views or table joins.

Custom IS-Subroutines to be used by custom computed columns are permitted.

Custom Entities, most commonly co-files, are permitted. Data can be maintained on MEDF/MEDC or a custom UI form.

UI forms are permitted. Custom forms can only update custom entities. Elements from Ellucian-delivered entities can be displayed on the form, but not updated.

Custom Report Process are permitted. Custom report processes must be read-only.

Custom Batch Processes are NOT permitted.

Custom Colleague Transactions (CTX) are NOT permitted.

The use of VOC Synonyms is NOT permitted.

Custom Stored Computed Columns, defined on a custom entity, are permitted Custom ELF specifications for imports and exports are permitted. Delivered ELF specification cannot be modified. Custom imports must be through the delivered intermediate database.

Custom Valcode Tables, List Specifications, LookUp Resolutions, Workflows, Menus and Messages are permitted. You cannot modify Ellucian-delivered records.

Custom Hyperlinks are permitted. Typically not needed. For SelfService hyperlinks will be defined through the sitemap or through a parameter form such as FSSL or STFL.

Client built SQL Views using Colleague Forms DOTV, DOVS are permitted.

Manually created SQL views on the ODS SQL instance are NOT permitted.

Stored procedures in ODS are NOT permitted.

Editing records using EDRC is NOT permitted.

CTSM (Create Summary) is NOT permitted, it can only be used against UniData.