BluSKY Automation Integration Options
Integrating with BluSKY enhances operational efficiency, streamlines access management, and ensures seamless communication between your systems and ours. To cater to the diverse needs of organizations, we offer four distinct integration options, each designed to fit varying requirements in terms of cost, setup complexity, data completeness, and ongoing maintenance.
The first option, SCIM Interface, is a cost-effective and straightforward choice for companies using Microsoft Azure, providing basic personnel and access level integration. For greater flexibility, the BluSKY API enables robust, bi-directional integration, allowing complete control over data, including card numbers and advanced access configurations.
If you need both simplicity and the ability to manage card numbers, our Hybrid Model combines the ease of SCIM with the power of the API, offering a balanced solution. For unique cases where automated options are not feasible, we provide CSV File-Based Integration, allowing updates through daily file processing.
Each option is tailored to ensure your company can choose the best fit based on your specific needs, whether you prioritize ease of use, flexibility, or full data integration. By integrating with BluSKY, you unlock the potential to enhance your operations while maintaining control over costs and resources.
SCIM Interface Integration
SCIM Interface Integration
Description: Uses a standard interface to integrate with Microsoft Azure. Two levels of integration:
- Company and personnel data.
- Company, personnel data, and access levels via Active Directory groups.
Cost: One-time software cost + ~8 hours of integration services.
Pros:
- Simple and easy to set up.
- Pre-approved and documented integration.
- Least expensive option.
- Ideal for basic employee data (names, photos, access levels).
Cons:
- Does not include card number integration.
- Card numbers must be assigned separately.
BluSKY API Integration
Description: A bi-directional, flexible integration for adding and retrieving data from BluSKY. Allows complete control over employee, visitor, card number, access level, and group integrations.
Cost: One-time software cost + ~24 hours of integration services including:
- Sandbox setup.
- Certification process.
- Note: Requires customer-side programming efforts.
Pros:
- Highly flexible and robust.
- Allows full data integration, including card numbers.
- Supports advanced use cases for employee and visitor data.
Cons:
- Higher initial integration cost.
- Requires customer-side programming.
- More time-intensive to set up.
Hybrid Model: SCIM + API for Card Numbers
Description: Combines SCIM for basic company and personnel data integration with API specifically to associate card numbers with employees. SCIM handles initial personnel import and updates, while the API fills the gap for card number assignment and advanced customizations.
Cost: One-time software cost + ~32 hours of integration services including:
- Sandbox setup.
- Certification process.
- Note: Requires customer-side programming efforts.
Pros:
- Leverages the simplicity of SCIM for initial setup.
- Adds the flexibility of the API for card number management.
- More cost-effective than full API integration when only card numbers need to be added.
- Reduces risk by offloading most data updates to SCIM.
Cons:
- Still requires some customer-side programming for API usage.
- Slightly higher initial setup cost than SCIM alone.
- Less flexible than full API integration for advanced use cases.
CSV File-Based Integration
Description: The customer sends a daily CSV file with personnel updates, and BluB0X processes it using APIs to update records in BluSKY.
Cost: Highest initial and ongoing costs due to:
- Custom development.
- Ongoing file comparisons and updates.
Pros:
- No programming needed on the customer’s side.
- Allows complete integration of employee data, including card numbers.
Cons:
- Most expensive option.
- Resource-intensive and risky due to dependency on file accuracy and comparison routines.
- Higher ongoing support costs.
| Feature | SCIM Interface | BluSKY API | Hybrid Model (SCIM + API) | CSV Integration |
| Description | Standard interface for Azure integration. | Flexible bi-directional integration via API. | Combines SCIM simplicity with API flexibility. | Daily CSV file processing for updates. |
| Data Included | Names, photos, access levels (no card numbers). | Full employee, visitor, card number, and access data. | SCIM for basic data + API for card numbers. | Full employee and access data. |
| Ease of Setup | Simplest to set up, minimal support required. | Requires programming and certification. | SCIM simplicity with moderate API setup. | Custom setup, resource-intensive. |
| Flexibility | Basic integration only. | Highly flexible and robust. | Moderate flexibility. | Limited to data in CSV files. |
| One-Time Costs | Low (software + ~8 hours of support). | Moderate (software + sandbox + certification). | Moderate (same as API). | High (custom development). |
| Ongoing Costs | Minimal. | Minimal after setup. | Minimal after setup. | High (daily comparisons + file processing). |
| Customer Effort | Minimal (if using Azure AD). | Requires programming resources. | Requires minimal programming for API portion. | Minimal (providing accurate CSVs). |
| Risk Level | Low (well-defined and pre-approved). | Low (robust API functionality). | Low (most tasks handled by SCIM). | High (file errors and comparison issues). |
| Card Number Support | Not included. | Fully supported. | Supported via API integration. | Fully supported. |
| Initial Setup Time | Short (pre-approved integration). | Moderate (setup + certification process). | Moderate (similar to API setup). | Long (custom development required). |
| Best Use Case | Basic, cost-effective integration for Azure users. | Advanced, custom use cases requiring flexibility. | Adding card numbers to SCIM-based integration. | When SCIM/API is not an option. |