Axibase Time Series Database

Axibase Time Series Database implementation process:

1. Initial Assessment and Planning:

   • Requirement Analysis: Understanding the specific needs of the business, including data volume, frequency, and types of metrics to be collected.

   • Infrastructure Planning: Determining the hardware and software requirements, including server specifications, storage needs, and network configurations.

2. Installation and Configuration:

   • Software Installation: Installing the ATSD software on the designated servers. This can be done on-premises or in a cloud environment.

   • Configuration: Setting up the database parameters, including data retention policies, indexing options, and security settings.

3. Data Integration:

   • Data Source Connection: Connecting ATSD to various data sources such as IoT devices, applications, and other databases.

   • Data Ingestion: Configuring data collectors and agents to start ingesting data into ATSD. This may involve setting up APIs, file imports, or streaming data pipelines.

4. Customization and Optimization:

   • Custom Dashboards and Reports: Creating custom dashboards, visualizations, and reports tailored to the business needs.

   • Performance Tuning: Optimizing the database performance by adjusting configurations, indexing strategies, and query optimizations.

5. Testing and Validation:

   • Functional Testing: Ensuring that the database is correctly ingesting and storing data.

   • Performance Testing: Validating the performance under expected load conditions.

   • User Acceptance Testing (UAT): Getting feedback from end-users to ensure the system meets their requirements.

6. Deployment and Training:

   • Production Deployment: Moving the system to a production environment.

   • User Training: Training the end-users and administrators on how to use and manage the ATSD system.

7. Ongoing Support and Maintenance:

   • Monitoring and Support: Providing ongoing monitoring, support, and maintenance to ensure the system runs smoothly.

   • Updates and Upgrades: Applying software updates and upgrades as needed.

Duration:

The duration of the implementation process can vary widely based on several factors, including the complexity of the data sources, the scale of the deployment, and the level of customization required. A typical implementation might take anywhere from a few weeks to several months. For smaller, less complex deployments, the process might be completed in a few weeks, while larger, more complex implementations could take several months.

Axibase Time Series Database customization process:

• Custom Data Collectors: Developing custom data collectors to integrate with specific data sources.

• Custom Dashboards and Visualizations: Creating tailored dashboards and visualizations to meet specific business requirements.

• Alerting and Notification: Setting up custom alerting and notification rules based on specific conditions and thresholds.

• Integration with Other Systems: Integrating ATSD with other business systems and applications through APIs and connectors.

• Data Retention Policies: Customizing data retention policies to meet regulatory and business requirements.

• Security Settings: Configuring custom security settings to ensure data privacy and compliance with industry standards.

• Licensing Fees: These areusually basedon the numberof cores/servers orthe volume ofdata processed.

• Setup Fees: Professionalservices forinitial setupand configurationmight incur additionalcosts.

• Maintenance Fees: Annual maintenancefees for softwareupdates and support.

• Support Charges: Differentlevels of support(e.g., standard, premium) mightcome with varyingcosts.

• Documentation and Guides: Detailed documentation and user guides are available to help users understand and utilize ATSD's various features.

• Customer Support: Axibase offers ongoing customer support to assist with issues or questions that may arise during and after implementation.

• User Setup: Axibase can help create user groups, set permissions, and configure user accounts during the setup process.

• Role-Based Access Control (RBAC): Granular access permissions to control what data and functionality each user can access.

• Data Encryption: Encryption of data both at rest and in transit to prevent unauthorized access.

• Monitoring and Auditing: Continuous monitoring of database activity and security audits to detect threats.

• Authentication: Strong authentication mechanisms like two-factor authentication to verify user identities.

• Compliance: Ability to configure security settings to meet regulatory requirements like GDPR.

• Major Releases: These might occur annually or biannually and include significant new features and improvements.

• Minor Updates: These could be released more frequently, such as quarterly or monthly, and include bug fixes, minor enhancements, and security patches.

• Patch Releases: These are often released as needed to address critical issues or vulnerabilities.

• Data Ownership: Typically, the data collected and stored in the database remains the property of the customer. The database provider ensures that the data is securely stored and managed.

• Data Portability: Many time-series databases offer features to export data in standard formats (e.g., CSV, JSON) to facilitate data portability. This allows customers to move their data to other systems or platforms if needed.

Axibase Time Series Database (ATSD) offers a subscription service with specific terms and conditions regarding contract renewal and cancellation, which vary depending on the edition of the software used.

Contract Renewal

1. Automatic Renewal: Contracts are generally subject to automatic renewal unless otherwise specified. Clients are typically notified before the renewal date.

2. Notification: Axibase may require users to provide notice of non-renewal prior to the contract renewal date. The exact notice period is often defined in the contract but can vary.

3. Change in Terms: Any changes to the terms upon renewal, such as pricing or service modifications, are usually communicated to the customers in advance.

Contract Cancellation

1. Cancellation Process: Users can often cancel their subscription by providing written notice to Axibase. The specifics regarding how to submit this notice may be detailed in the service agreement.

2. Refund Policy: The terms regarding refunds upon cancellation may differ based on the time of cancellation. Typically, if a subscription is canceled before the end of the billing cycle, users may not receive a refund for any remaining days.

3. Liabilities Upon Cancellation: Users may be required to settle any outstanding payments or obligations related to their use of the service up to the cancellation date.

Additional Considerations

• Support Services: The level of support may change upon renewal, and users might need to reassess their service package to ensure adequate support for their needs.

• Custom Terms: Larger enterprises may negotiate custom terms regarding renewal and cancellation, which can differ significantly from standard agreements.

The Axibase Time Series Database (ATSD) meets various compliance standards that focus on security and data integrity. Here are the key compliance aspects:

1. GDPR Compliance: Axibase emphasizes its commitment to the General Data Protection Regulation (GDPR), which is critical for companies handling data from EU citizens. This involves implementing measures to protect personal data and ensuring users have control over their data.

2. ISO/IEC 27001 Certification: Axibase aims to adhere to the ISO/IEC 27001 standard for information security management systems (ISMS). This certification involves comprehensive risk management practices and policies to protect sensitive information.

3. Data Protection Regulations: The software complies with various data protection regulations, ensuring that data collection, storage, and processing are performed responsibly and ethically​

4. Security Practices: Axibase includes features for monitoring and compliance, such as intercepting lifecycle events of Docker containers to ensure compliance with pre-approved configurations and preventing unauthorized access to sensitive data