Main Content

ACCP FAQ - Platform Developers Call

General

1. Who will be the users of the cloud services platform described in this CfP?

The users of the platform will be researchers from Canadian higher education institutions who have responded to and been accepted to the Pilot via a forthcoming CfP for researchers. They will be using the platform to run their research computation while evaluating the platform and providing feedback on improvements.

2. If I have any questions not answered in this FAQ, where can I direct my questions?

Please direct all inquiries via email to the Pilot project manager, Oludolapo Obaseki, ACCP@alliancecan.ca

Relevant questions and responses shared with the community.

3. Can I get assistance in building my proposal for the CfP?

Limited support is available in the form of feedback on proposal drafts. Please contact Oludolapo Obaseki ACCP@alliancecan.ca to initiate.

4. How is the sponsor/project management/technical leadership/financial authority structured for this project and what are the contacts for these?

5. How will communications regarding the pilot be coordinated between the Alliance and the participants in the pilot?

The project manager will manage general communications, Oludolapo Obaseki oludolapo.obaseki@alliancecan.ca. All general communications should go through the Pilot email, ACCP@alliancecan.ca

Software development, IT architecture, etc. will be managed using the tools described below. This will be led by the Pilot technical lead, Glen Newton glen.newton@alliancecan.ca 

 

Eligibility

1. My organization/company has never received funding from the Alliance: what are the eligibility requirements for receiving funding from the Alliance for this pilot?

Two categories of participants are expected in this pilot:

  1. Individuals or teams affiliated with a university, post-secondary college or educational institution, hospital, or non-profit organization that is situated in Canada and that carries on, or is capable of carrying on, meaningful research.
  2. Commercial entities that offer goods, services, or intellectual property that are relevant to the pilot.

For selected participants in category 1, the Alliance will enter into a standard funding agreement with the institution the individual or team is affiliated with.

For selected participants in category 2, the Alliance will enter into a procurement agreement (including but not limited to a purchase order, service level agreement, etc.).

2. I manage a research team at a Canadian university that has developed a set of researcher-facing services that serves an active research community. Can I propose the extension of these services to multi-cloud deployment and/or integration into the ACCP portal as part of the ACCP Platform call?

Researcher-facing services (category 2) are a fundamental part of the ACCP, with researching-facing services that are not directly listed (e.g. Galaxy, Jupyter, Magic Castle) classified under Component #5 - Other Services. Proposals involving such services are eligible and will be considered where relevance, cost and community support justifies their inclusion in the pilot. Please describe the services, how they serve the research community, and how they would be integrated into the multi-cloud platform in your letter of interest (LOI). We suggest that you reach out to ACCP@alliancecan.ca before submitting an LOI to receive feedback on your service.

3. I am an individual: can I participate in the CfP and subsequent pilot activities?

Individuals need to be either:

  • affiliated with a university, post-secondary college or educational institution, hospital or non-profit organization that is situated in Canada and that carries on, or is capable of carrying on, meaningful research.
  • operating as a legal commercial entity that offers goods, services, or intellectual property that are relevant to the pilot.

4. My research team is interested in contributing to only one of the components: is this possible?

Yes, the Alliance expects some teams will be interested in contributing to only a subset of the components and only contributing to one is acceptable.

Please be sure to make this clear in your letter of interest (LOI).

5. My team is interested in contributing to several but not all of the components: is this possible?

Yes, the Alliance expects some teams will be interested in contributing to only a subset of the components.

Please be sure to make this clear in your letter of interest (LOI).

6. My company would like to participate in the pilot: is this possible?

Commercial entities that offer goods, services, or intellectual property that are relevant to the pilot can participate in it.

 

Procurement/Financial

1. Will the Platform CfP provide any funding to the participants?

As per Section 3.1 of the CfP document, this CfP is neither a procurement call nor is it a funding call. The financial discussion for the Pilot occurs in Stage 2. Stage 1 will focus on bringing together participants with expertise, experience and who will add value to the pilot project. In Stage 2, selected participants will form teams to deliver components and a budget for each component (and each team contributing to that component) will be established. Funding will flow to participants based on this plan through the funding mechanisms described below.

2. Where can I find more information on the Alliance funding mechanisms available as part of this pilot?

For selected participants in category 1, the Alliance will enter into a standard funding agreement with the institution the individual or team is affiliated with.

For selected participants in category 2, the Alliance will enter into a procurement agreement (including but not limited to a purchase order, service level agreement, etc.).

More information on funding arrangements will be provided to participants who are invited to Stage 2.

 3. Can funding be used to purchase equipment?

No.  The funding is made available to cover operating expenses related to the initiative.

4. What expenses are eligible to be paid for as part of the pilot?

For participants in category 1 (individual or team affiliated with an institution), eligible expenses include:

  • Salaries of scientific, professional, technical, and administrative personnel directly involved in the pilot.
  • Benefits costs as charged by the host institutions, up to a maximum of 22% of eligible direct labour costs.
  • Software subscriptions and licenses
  • Supplies and consumables

For participants in category 2, all expenses will need to be outlined in a Statement of Work as part of a procurement process.

5. For teams that enter into financial arrangements/contracts with the Alliance, what are the requirements for reporting?

Participants in category 1 (individual or team affiliated with an institution) will have to provide periodic progress and financial reports. Further details will be provided to participants who are invited to Stage 2.

6. My team includes graduate students: can these be funded as part of our participation in the pilot?

No. Trainee stipends (undergraduates, graduates and postdoctoral fellows) are not eligible expenses.

7. Does every team need to provide monetary and/or non-monetary (in-kind) match contributions as part of the CfP response?

No. As per Section 4.1, ISED has made available $5M to the Alliance for the ACCP project, which if leveraged fully, would require a match of approximately $2M. In order for the ACCP to leverage the full amount from ISED, it is necessary for the entire project (including the CSP CfP) to achieve this level of match. All participants are encouraged to consider how their organizations can contribute to providing a match, but all responses are not required to provide a match.

8. My institution is providing monetary and/or non-monetary (in-kind) contributions for this project. How do I attach a letter to demonstrate their commitment to my project?

The LOI is designed for respondents to express their interest and commitment to the ACCP and to provide an overview of how their contribution will add to the success of the project. Section 7.1 states that Respondents should provide a high-level description of remuneration and match. Detailed letters of support will be required during Stage 2 of the project.

9. Are travel expenses part of the expenses covered by the pilot?

No. Travel expenses are not eligible expenses.

10. How will financial oversight work for organizations that receive funds as part of the pilot? What kind and frequency of reporting will be needed?

Participants in category 1 (individual or team affiliated with an institution) will have to provide periodic progress and financial reports. Further details will be provided to participants who are invited to Stage 2.

The financial reporting comprises total contributions received (i.e. Alliance contributions and match contributions) and total expenses incurred (from all sources of contributions).

The institution must maintain a verifiable audit trail for all expenses and contributions (including non-monetary) reported. It must also maintain separate project accounts for the project. Financial records must reconcile to the financial report submitted to the Alliance.

The institution must be prepared to provide supporting documentation for expenditures and contributions related to each eligible item included in the budget or financial report. The institution must keep on file the original documentation for audit purposes and provide it upon request.

11. Will any retroactive expenses be eligible as part of the pilot?

No. Retroactive expenses are not eligible expenses.

 

Component Delivery

1. Who will be leading the component teams?

The component teams will be co-led by an individual from one of the component external participants and a representative of the Alliance.

2. What is the approval process for the component proposals?

An Alliance-led review team will review the proposals. The review team will need to interact with the submission team’s post-submission for additional information.

At the review stage, teams with strong competing component proposals will be encouraged to merge their proposals. The review team and Alliance technical staff will facilitate this process.

3. Is there an expectation to develop "in the open", for example, in a publicly visible GitHub repository(ies)?

Yes - with exceptions for specific items, primarily security oriented - all code (software, configuration, deployment, etc.) is expected to be developed in publicly facing code repositories.

4. What issue tracking software will be used for the components?

Once the component teams have formed, they will (each) agree on what issue tracking infrastructure they will use for their component. The chosen system must be supported by monday.com integration.  Note that different component teams may choose different issue tracking systems.

The plan is also to create a Slack channel for each component and one overall channel for the Platform project. A discussion with the component teams with respect to the best model and communications platform for this will be used to decide the approach to take.

See Q.3 of the Project management section for more information on monday.com and its integration with issue management software.

5. The integration of the components is integral to this pilot: how will the integration be coordinated?

Coordination of the integration will be the responsibility of the technical lead. Automated tests for the integration of the components must be part of the component proposal. Teams building components #1, #6, #7 will need to communicate the integration mechanisms with which the component teams building components #2, #3, #4, #5 need to integrate. Components #1, #6, #7 may also require a certain amount of integration with each other.

6. The component my team is interested in working on will have to integrate with the Identity and access management (AIM) component. However, the team does not have a lot of IAM experience: Will there be support to assist us in doing this?

The IAM component is a particularly special component. The Alliance will provide a resource to support the IAM integration across the various components. This resource will primarily consult with component teams: implementation responsibility still will reside with the component teams.

7. Will the component teams be operating in an iterative/incremental (agile) style of software development?

Component teams are encouraged to use software engineering best practices. Component teams will need to propose the type of software development and this will be reviewed by the project manager and technical lead. Iterating discussions may be required to come to mutually agreeable development practices.

8. When are the components expected to be available in beta form, stood up in the cloud and available for evaluation by researchers?

Components are expected to have beta releases by mid-August 2024.

 

Operations

1. What is the operational time frame of the pilot (i.e. the period of time when the built system will be used by users)?

Users are expected to be using the system from September 2024 to March 2025.

2. Who will operate the components for the duration of the pilot?

The component teams will be expected to operate their components for the duration of the pilot. The cost of the operations of the pilots and who from the team will be providing this support should be included in the component proposals.

3. Will there be funding available to those providing operational support for the duration of the pilot?

Yes. As part of the component proposals there should be a line item in the budget for the costs associated with pilot operations.

4. How will support be managed/coordinated for the duration of the pilot?

An Alliance resource will be assigned to triage and coordinate support with the component teams and the overall pilot project. Issue management infrastructure will be put in place for pilot operations after discussions with the operations component teams.

 

Intellectual Property

1. What is the relationship between the activities described in the Platform CfP, the Providers CfP and the Research CfP?

These three CfPs make up the ACCP Pilot. Researchers that participate in the Researcher CfP will use the services built by the Platform CfP. These services will run on the cloud service providers that respond to the Providers CfP. Researchers will also be able to directly use the cloud service providers’ native services.

2. Who owns the (copyright) rights to the intellectual property developed from this CfP?

All new code developed from funding for this CfP will be copyright the Digital Research Alliance of Canada. All of this code - with the possible exception of some security restrictions - will be Open Sourced. See below question regarding the Open Source licensing of code, etc.

3. Are the new code, software or systems developed expected to be Open Sourced?

Yes, these are all expected to be licensed with an MIT license.

For software developed as part of the pilot that is extending or contributing to existing software whose community has decided to use a different Open Source license, then this license of the community will be used.

4. What are the expectations from the Alliance should any publications arise from activities related to the pilot?

Publication authors are expected to acknowledge the support received from the Alliance in any publications.

Any publications, presentations, etc. derived from the Pilot are expected to follow standard academic guidelines with respect to authorship, attribution, ethics. An excellent reference for this is the Tri-Agency Panel on Responsible Conduct of Research (PRCR)’s Publication Guidelines.

Project Management

1. What is the relationship between the component co-leads and the overall pilot project manager and technical lead?

The component co-leads are responsible for delivering their component, which includes directing the software engineering activities of their team. They are expected to build out and update their component issue tracking tools in a timely fashion, and to communicate progress, challenges and risks to the project manager and the technical lead.

The project manager is primarily responsible for building the overall project plan (in coordination with the technical lead and the component co-leads) and verifying that deliverables are completed on time and on-budget.

The technical lead is responsible for the overall architecture, technology choices, software engineering practices and IT security. Component architecture and technologies proposed by the component teams must be authorized for use in the Pilot by the technical lead. The project manager and technical lead are expected to collaborate with one another as well as with the component teams.

2. What online tool(s) will be used for project management?

The project management of the Pilot will be using monday.com. This project plan will capture deliverables at a fairly high level. Each of these deliverables will correspond to a number of software issues.

Once the component teams have formed, they will agree on what issue tracking tool they will use. The chosen tool must be supported by monday.com integration.  

3. Is there a final report as part of the overall project as well as for each of the components?

Yes, the technical lead is responsible for a final project report. This will be developed during the Pilot with the support of the component co-leads, project manager, researchers and other participants.

4. How will deviations from the proposed budget be managed?

Deviations in the budget in either direction should be communicated to the project manager as soon as they are discovered. An analysis and explanation as to the reason for the deviations should be done and communicated to the project manager as soon as possible.

5. How will the component teams be formed?

The component teams will be formed at the Pilot Platform workshop. For each component, the LOI teams that were accepted will share their vision for the component, as well as their capacity to build it. Once all the teams for the component have shared, these teams, the technical lead, the project manager and various Alliance technical resources will negotiate what the solution will be. The goal will be to create component teams (and solutions) from a merger of the LOI teams and their visions. It is possible that at this point some LOI teams may choose not to proceed in participating in the development of the component.