New procurement and delivery of software for managing international mobility at SDU
Published deadline passed
The published deadline has passed. For multi-stage competitions a later tender deadline may still apply — check the notice or portal for the current phase.
- Deadline
- Jan 22,Expired
- Award
- Price 30%
Brief
Syddansk Universitet needs a new international mobility management system for 8 years, with a maximum total value of 1.2 million DKK, to support all forms of international mobility (incoming and outgoing) and all process steps in the administration of international mobility for students and staff. The system should be delivered in Fyn. Tenders will be evaluated based on price (30%) and quality (70%). Suppliers must demonstrate relevant expertise from a similar assignment with three references within the last three years, including a description of the delivery, customer name, value, and delivery/framework agreement period.
IT-drift og support
Custom Assessment Criteria
Get answers to your bid/no-bid criteria
Set them up once and Cobrief answers them in every tender
Will you bid?
The agent sets up the bid and writes the first draft. Free for 14 days.
Qualification requirements
Description
It is a minimum requirement that the Tenderer has relevant expertise from a similar assignment to the one being tendered demonstrated by three (3) references within the last three (3) years. With relevant expertise within the categories, the Contracting Authority understands similar tasks that include deliveries to both the public and/or private sectors as well as single deliveries and/or deliveries on framework agreements. The references must include: - Description of the delivery - Name of the customer - Value - Date of delivery and/or period of framework agreement (start and end date).
Documentation Requirement
Three (3) references within the last three (3) years, including: - Description of the delivery - Name of the customer - Value - Date of delivery and/or period of framework agreement (start and end date).
Source
No source found in the documents. Check the requirement against the tender documents.
Award Criteria
Description
4.5.1 User-friendliness – administrative users/general 4.5.2 User-friendliness – applicants 4.5.3 User guides 4.5.4 Customising the public user interface 4.5.5 Personal user interface/ dashboard – administrative users 4.5.6 Personal user interface/ dashboard – administrative faculty users 4.5.7 Overviews in connection with applications 4.5.9 Administrative search functionality - incoming applications 4.5.10 Administrative search functionality - outgoing applications 4.5.12 Publicly available search functionality 4.5.13 Application process – incoming 4.5.14 Application process – outgoing 4.5.15 Save draft 4.5.16 Prioritisation for incoming applicants – courses 4.5.17 Prioritisation for incoming 4.5.18 Prioritisation for incoming applicants – Clinical stay 4.5.20 Applicant's access to communication 4.5.22 Seek guidance 4.5.23 Additional services, incoming 4.5.24 Uploading documents 4.5.25 Viewing document 4.5.26 Reporting/evaluation of mobility and Functionality (4.6)• 4.6.3 Workflows 4.6.4 Workflows 4.6.5 Workflows 4.6.6 Forms 4.6.7 Automated processes 4.6.10 Application – outgoing exchange 4.6.11 Managing available outgoing exchange spots 4.6.12 Grade point average ranking for outgoing exchange 4.6.13 Limitations to available outgoing exchange spots 4.6.14 Linking applications for outgoing exchange 4.6.15 Communication 4.6.16 Reminders for administrative users 4.6.17 Event invitation and registration 4.6.18 Reporting 4.6.20 Case processing of applications 4.6.21 Previous exchanges 4.6.22 Educational options for incoming students 4.6.26 Proposal for alternative application 4.6.27 Deviations 4.6.28 Buddy 4.6.31 Academic assessment in iterations 4.6.32 Register academic assessment 4.6.33 Register academic assessment 4.6.34 Register academic assessment 4.6.36 Incoming nomination 4.6.37 Distribution of nomination information 4.6.40 Supplementary information 4.6.41 Supplementary information 4.6.42 Producing exchange agreements 4.6.43 Producing exchange agreements 4.6.44 Producing exchange agreements 4.6.45 Export of exchange agreements 4.6.46 Export of exchange agreements 4.6.48 Multiple funds for the same type of mobility 4.6.49 Supplementary information for funds 4.6.50 Grant calculation rules 4.6.52 Calculation of grant size 4.6.54 Allocation of grants 4.6.56 Payout information Non-functionality:• Collaboration and training (4.4), Non-functional requirements (4.7) and Service levels (4.8) 30 % Collaboration and training (4.4), 4.4.2 Training for administrative users 4.4.3 Form of training Non-functional requirements (4.7), 4.7.1 Roadmap 4.7.4 Description of the environments 4.7.5 Configuration of the Customer's test environment 4.7.10 Browser support 4.7.12 Disability accessibility requirement 4.7.13 Customer attributes 4.7.14 Hypercare period 4.7.15 Hypercare period 4.7.18 Backup 4.7.20 Backup (availability) 4.7.22 Disaster Recovery 4.7.24 Export of the Customer's data 4.7.27 Data integrity 4.7.29 Audit log 4.7.31 Log (storage and security) 4.7.33 Export of logging data 4.7.34 Encryption 4.7.35 BYOK Bring Your Own Encryption 4.7.36 Microsoft Entra ID authentication of Customer's administrative users 4.7.37 Role-based authorisation 4.7.39 Users who are both students and employees 4.7.40 Access management 4.7.41 Authentication 4.7.44 Security by Design principles• 4.7.45 Security by Design principles 4.7.46 Default settings 4.7.47 Information Lifecycle Management 4.7.48 Privacy-enhancing technologies 4.7.51 Customer’s integration platform 4.7.52 Authentication of calls to the Customer's web services 4.7.54 System API (application programming interface) 4.7.55 Authentication of calls to the System API 4.7.56 System API call – data transfer from the System to Costumer’s integration platform 4.7.57 System API call – data transfer from Costumer’s integration platform to the System 4.7.58 System API call – data transfer from Costumer’s integration platform to the System 4.7.59 System API call – data transfer from Costumer’s integration platform to the System 4.7.60 Transfer technology and integration with Microsoft 365 and Service levels (4.8), 4.8.4 System availability and Testing and documentation (4.10)• 5 % 4.10.1 Test cases 4.10.2 Documentation Terms:• Delivery and terms, configuration (4.2)•and Information Security (4.9) 15 % Delivery and terms, configuration (4.2) 4.2.2 Configuration – collaboration 4.2.4 Timeline Data:• Information Security (4.9)• 4.9.3 Information Security Standard• 4.9.7 Mobile security••• 4.9.10 Data centre
Source
No source found in the documents. Check the weight against the tender documents.
Description
Price for delivery and implementation of the system for mobility management 90 % Option on data export when contract expires/collaboration ends 10 %
Source
No source found in the documents. Check the weight against the tender documents.
Previous winners
Who are you up against?
The suppliers who have won similar contracts at Syddansk Universitet
From the notice
SDU is seeking an international mobility management system that supports all forms of international mobility (incoming and outgoing) and all the Customer's process steps in the administration of incoming and outgoing students’ and staff’s international mobility. The system and the requirements for it are described further in appendix 1 - the requirements specification.
Contact
Christina From-Nielsencfro@sdu.dk- CompetitionType
- FynLocation
- 48000000Main codeSoftware package and information systems
- 72250000System and support services72253200Systems support services