BSCW Classic
By Fraunhofer FIT and OrbiTeam Software
Initial Consultation: Discuss the organization’s needs, requirements, and project scope.
Planning: Define the implementation timeline, deliverables, and milestones.
Installation: Set up the BSCW Classic environment, which may be on-premises or hosted.
Configuration: Customize settings and user interfaces based on organizational requirements.
Data Migration: Transfer existing data into the BSCW Classic system if needed.
Integration: Connect BSCW Classic with other tools and systems in use at the organization.
Testing: Conduct thorough testing to ensure all elements function correctly and meet business needs.
Training: Provide training sessions for end users and administrators.
Go-Live: Officially launch the software for use.
User Roles and Permissions: Ability to tailor access rights for different users or groups.
Interface Customization: Modify the user interface to align with branding or operational workflows.
Workflow Automation: Create custom workflows to automate repetitive tasks specific to the organization.
Plugin Development: Opportunity to develop and integrate custom plugins for additional functionality.
Setup Fees: Generally applicable depending on the complexity of the installation and configuration; this can vary widely.
Maintenance Fees: Ongoing maintenance costs may be charged annually or monthly, often tied to support and updates.
User Documentation: Comprehensive manuals, FAQs, and guides available for self-learning.
Training Sessions: Workshops or webinars that can be scheduled, either online or in-person.
Help Desk Support: Access to customer support via email, chat, or phone for troubleshooting issues.
User Authentication: Strong authentication processes, including username and password requirements, possibly with two-factor authentication.
Data Encryption: Encrypted communications to safeguard data during transfer and storage.
Regular Updates: Frequent software updates to address security vulnerabilities and patch issues.
Access Control: Defined user roles and permissions to restrict access to sensitive information.
Update Frequency: BSCW Classic typically releases updates several times a year. The exact frequency can depend on user feedback, bug reports, and emerging security threats.
Management of Updates:
Notification: Users are usually notified in advance about upcoming updates and their expected impact.
Documentation: Each update comes with release notes outlining new features, improvements, and bug fixes
Data Ownership: Organizations typically retain full ownership of their data stored within BSCW Classic. The software does not claim ownership of user-generated content.
Users should have the ability to export their data in standard formats, facilitating migration to other platforms if necessary.
Scaling Up:
Organizations may add users or additional modules as needed.
Typically done through a tiered pricing model that corresponds to the number of users or functionalities in use
Notifications of upcoming changes and new features may be provided.
Scaling Down:
Reducing the number of users or modules usually requires notification in advance, which varies based on the contract terms.
Renewal Terms:
Contracts often include auto-renewal clauses unless a party gives prior notice (usually 30-90 days).
Renewal rates may be outlined in the contract, often linked to previous pricing or subject to a modest increase.
Cancellation Terms:
There might be stipulations that require settling any outstanding payments before cancellation is processed.
GDPR: Compliance with the General Data Protection Regulation for data privacy for users within the EU.
ISO 27001: Alignment with international standards for information security management systems.
HIPAA: For organizations handling health information in the United States, ensuring privacy and security of health data.
