Qualifications and Curriculum Development Agency

Last updated: 24 September 2009

If you are new to the Diploma aggregation service (DAS), you may find it useful to read our factsheet first (see ‘Related Documents’), then come back for further information on the options available to you for integrating existing MI systems with DAS.

Introduction
Centres are responsible for creating and maintaining learner accounts on DAS. They will input information on the learner (line and level of learning), record the completion of work experience and personal, learning and thinking skills (PLTS), and trigger a Diploma claim on behalf of the learner. Centre users will typically access DAS via a web browser.

As an MIS supplier to schools and colleges offering Diplomas or an own provider working within a centre, you may want to enhance your system to help make Diploma administration easier for your users. You could include functionality to create a batch file of learner information to upload to DAS. The service will respond with a similar file confirming all the transactions completed that can be downloaded as an audit trail. Alternatively, you could establish a direct interface (API) between your MIS and DAS, and avoid users from having to make duplicate entries.

There are three methods by which a centre can use DAS:

1. Manual retrieval of learner information from existing MIS and access to DAS to create learner accounts via a web browser
2. Creation of batch files (.csv format) containing information on many learners downloaded from existing MIS, then uploaded to DAS via a web browser
3. Direct interface (API) between existing MIS and DAS, enabling users to open and maintain learner accounts without leaving the MIS environment 

Prerequisites
Using DAS involves centres and awarding bodies sharing information through a single system. All users are must sign up to legal agreements to protect their own commercial interests and also the interests of the Diploma learner and other parties involved in developing and supporting the service. MIS suppliers and own providers using the batch file method will be covered by their centre’s agreement. However, those using the direct interface will be asked to sign up to the following:

• Participation Agreement: this is essentially a non-disclosure agreement and a prerequisite for gaining access to detailed system documentation, including functional specification and API documentation.
  
• Method of Access (API) Agreement: this details the services available, testing requirements and conditions of live operation (see 'Related documents').

MIS suppliers and own providers who develop a direct interface will become 'authorised users' of DAS and will be invited to participate in the User Group.

Options for integrating existing MIS with DAS

1. Supporting batch files upload/download:
   In order to create batch files for upload/download to DAS you will need to request a copy of the Batch File Definitions (see ‘Key Documents’). You will have to decide whether to upload batch files only or upload and download information, and whether to use batch files for just some or all transactions with DAS. Once you have developed your file formats, please check that these have been developed in line with DAS requirements before exchanging information.
   
2. If you are considering establishing a direct interface between your MIS and DAS, please contact us at DAS_Service_Management_Team@qcda.gov.uk to talk about the 'on-boarding' process. The first steps of this are to sign a Participation Agreement to access the API and to review the accompanying API Guide, which explains how the API has been set up.

Compatibility Testing is required for a direct interface to demonstrate that your system is compatible with DAS and can be used effectively to complete all the tasks required for Diploma administration. As part of the 'on-boarding' process, you will need to arrange a convenient testing window with us.

Key Documents
You can access the following from this website:

• Batch File Definitions (for uploading/downloading of information. Versions are available for both DAS Release 2 and Release 3)

Further detailed documentation is available via the dasdocs secure area):

• Functional Specification (including System Use Cases)
• API (Application Programming Interface)
• API Guide

You will need a username and password to access the documentation in dasdocs. These can be requested from the DAS Service Management Team. If you are considering the API option, you will need to sign a Participation Agreement, which is also available from the Service Management Team at DAS_Service_Management_Team@qcda.gov.uk.