ScienceCloud Implementation and Support
Summary: Requirements for setting up new ScienceCloud teams and projects. Includes a downloadable Excel spreadsheet (
ScienceCloud New Customer Creations v3.xlsx) for getting started.
Clicking a link will scroll the page to the relevant section.
- ScienceCloud System Overview
- ScienceCloud Team Setup
- Adding Users and Applications to Existing Accounts
- Removing User Access to ScienceCloud Projects
- Closing ScienceCloud Projects
The pharmaceutical industry is rapidly restructuring its discovery business model to a fully integrated, networked R&D system where significant parts of the discovery process are conducted through external collaborators and contract research organizations (CROs).
This rapid change presents significant challenges for deploying the systems required to support collaborative research and to ensure that networks can operate efficiently, accelerate innovation, and lower the costs of drug discovery.
ScienceCloud is uniquely positioned to help businesses and organizations overcome the informatics challenges presented by this fundamental shift in research business practices by offering the following:
- Collaborative project management – Secure project management and the ability to share project information (structured data and documents) using a unique social networking approach to scientific collaboration.
- Experiment and IP capture – A flexible, multi-disciplinary, low-cost-of-ownership electronic lab notebook application that empowers sponsor organizations and network partners to capture and share experimental methods.
- Custom business rules extension – The Pipeline Pilot application supports creating and managing scientific services, standard business rules implementation, and data integration between ScienceCloud and on-premises systems.
- Mobile device enablement – A mobile iOS application enables scientists to access ScienceCloud to execute tasks and share results with colleagues. An associated Mobile Collection for Pipeline Pilot allows developers to build scientific protocols that can be deployed to mobile devices, leveraging mobile capabilities, including sound and image capture, location services, and speech-to-text.
- Publishing and sharing services – ScienceCloud Exchange is an open portal where scientists can publish and share Pipeline Pilot protocols, such as reports created from ScienceCloud data, enhancing broad dissemination of essential research tools within the ScienceCloud community.
The following information needs to be provided when setting up a new ScienceCloud team.
- Team Information
- Project Information
- User Information (Permissions, Projects, Applications)
Tip: To perform these tasks, download the spreadsheet (
ScienceCloud New Customer Creations v3.xlsx).
The following information is required to set up a new team in ScienceCloud.
- Team ID, Organization, Name
- Session Timeout (default 60 minutes) and Protocol Access
- Naming convention for compound and batch (lots)
- Company logo
Note: This information applies to all projects and applications.
Team ID, Organization, Name
The Team ID is typically the company's name (maximum 50 characters). The Team Organization is the name of the organization the Team belongs to (maximum 50 characters). The Team Name is a descriptive team name that provides more detail (maximum 250 characters).
Session Timeout and Protocol Access
Session Timeout is the amount of time a user will be logged out for security purposes if the current log in session is inactive. By default, the timeout is 60 minutes, but can be customized by the company. Protocol Access determines if protocols assigned to your Pipeline Pilot group (as shown in Web Tasks and Tasks/Export in Project Data) can be viewed. Protocols can either be accessible within this team alone or can be accessible for all teams the user has access to.
Naming Convention for Compound and Batch (Lots)
Compounds can be named manually or automatically by sequence. Automatic assignment does not prevent manual assignment of the Compound identifiers. Compounds must have a prefix and padding zeroes for the number. Compound structures can match on a Project or Team level. Batches can be named manually, when a batch ID is not provided, or automatically (always). Batches require a separator and padding zeros for the number.
Note: When using automatic naming, the total number of characters allowed for a Compound ID is 50, and the total number allowed for the Batch ID is 50. The compound identifier should have a prefix and padding digits.
(Optional and can be added after team is set up). Provide a file with the logo that the company can use to show when users are logged into your Team on the Dashboard. Logo will be scaled proportionally to a maximum height of 60px and a maximum width of 210px.
ScienceCloud projects are an organized construct that determines who can see a given set of information. It is necessary to define at least one project during account setup. Additional projects can be added whenever necessary thereafter. Project ID has a maximum of 50 characters; Project Name has a maximum of 250 characters.
User Information (Permissions, Projects, Applications)
Each user will be given an account with access to projects. Users will have project-specific permissions and are given access to applications and optionally some permissions that are at the team level (i.e., across all projects they can access or all team projects).
The primary contact for a company or organization can request new projects, accounts for new users (with attendant roles, permissions, projects, and applications), and new applications for existing users.
Tip: To perform these tasks, download the spreadsheet available in this article (
ScienceCloud New Customer Creations v3.xlsx).
To remove user access from a ScienceCloud project, do any of the following:
- Use ScienceCloud Project Administration tools to remove permissions.
- Send a request to email@example.com to remove access to one or more projects or the entire team.
Note: When removing access to all projects, the application seats assigned to that user can be reassigned to a different user.
When a project ends, there are a number of options on how to deal with the project resources, including:
- Keep the project, but remove access for external partners. Optionally, make the Project Read-Only so that data can still be viewed but not modified.
- Archive the project. The project will no longer be accessible, but can be restored at a later date.
- Close the project, and do one of the following:
- Archive the data –Use the Export function in Project Data or create a custom export protocol in Pipeline Pilot to output project data in any file format or as a report.
- Delete the data – Send a request to firstname.lastname@example.org to delete all data associated with the project. Data will no longer be available in ScienceCloud. Data will be removed from all backups after 90 days.
- The 90-day backup limit is the same for all ScienceCloud users and cannot be changed.
- Archived projects are like regular projects except no one can access an archived project. Access can be reinstated. You can create reports and do anything else you typically do with a project.
- Restoring an archived project is not the same as restoring from a backup, which should be a last resort if data somehow gets deleted.