Hosting Service Description (Infrastructure)
Service Level: L3 — Full-Managed Cloud Service
This Service Description defines the Full-Managed Hosting & Infrastructure package, enabling clients to host physical hardware test rigs (Assemblies) directly inside Vector's secure datacenter.
L3 extends L2
This document covers the additional Hosting services only. The full capabilities of the WebService (Platform) L2 are a prerequisite and are included in every L3 engagement. Refer to the WebService Service Description for the platform-level terms, SLAs, and support scope.
Pilot Phase — No Binding SLA
This service is currently in Pilot Phase (Closed Beta). No legally binding availability levels are guaranteed during this period. Vector makes all commercially reasonable efforts to meet the target values stated below.
1. Subject and Scope
1.1 Scope of Agreement
In addition to the WebService (Platform) capabilities, the contractor offers turn-key physical hosting of development Workspaces and Assemblies. This represents the Full-Managed (Hosting) deployment tier (L3).
1.2 Service Boundary
The contractor takes full responsibility for provisioning, operating, and maintaining the physical hardware environment.
- Contractor Responsibility: Datacenter facilities, racks, network switches, Execution Environments (NUCs), remote power relay cards, and Hardware Automation Interfaces (HAI).
- Client Responsibility: Proprietary target hardware (e.g., ECUs, customized wiring harnesses, target debugger units) provided for installation inside the datacenter.
1.3 Usage Rights and Physical Restrictions
- Authorized Personnel Only: Physical access to racks and systems is restricted to certified datacenter staff.
- Client Access: Client engineers access their hosted hardware exclusively via secure web interfaces, remote terminals, or API channels. Direct physical client access is not permitted unless specifically agreed upon for audit purposes.
- Internal Use Only / Reselling Prohibition / Geographic Restrictions: As defined in the WebService Service Description §1.3.
2. Definitions
| Term | Definition |
|---|---|
| Workspace Slot | A standardized rack unit (1 U / 1 HE) designated to house client assemblies. Used as the base unit for Assembly sizing and pricing. |
| Execution Environment (EE) | A fully managed physical compute node (e.g., Intel NUC) situated directly next to the test rig to ensure low-latency flashing and debugging. |
| Physical Assembly | The client's actual electronic test setup, comprising ECUs, power units, cabling, and communication interfaces. |
All further terms (Application Service, vHaaS Agent, HAI, Assembly Profile, Request Profile, Workspace) are defined in the WebService Service Description §2.
3. Scope of Hosting Services
3.1 Datacenter & Rack Operations
The infrastructure is operated within professional, enterprise-grade carrier hotels in Stuttgart, Germany.
- Environmental Controls: Redundant climate control, dust filtration, and uninterrupted power supply (UPS).
- Physical Security: Multiple physical perimeters, strict badge access controls, and continuous video monitoring.
- Network Isolation: Strictly isolated Layer-2 VLANs assigned per client tenant.
3.2 Workspace Architecture
Each hosted Workspace includes the following standard infrastructure components:
- A fully managed Execution Environment (EE)
- The physical Assembly operated by Vector
- Hardware Automation Interface (HAI) integration for device control
- A local, isolated high-speed network (10 GbE) for internal component communication
┌────────────────────────────────────────────────────────┐
│ Secure Workspace │
│ │
│ ┌──────────────────┐ Outbound only ┌────────────┐ │
│ │ vHaaS Agent │◄──────────────────►│ vHaaS AS │ │
│ │ (Intel NUC EE) │ │ (Cloud) │ │
│ └────────┬─────────┘ └────────────┘ │
│ │ │
│ │ Isolated 10 GbE LAN │
│ │ (no direct internet / intranet access) │
│ ▼ │
│ ┌────────────────────────────────────────────────────┐ │
│ │ Client Hardware Assembly │ │
│ │ ┌──────────┐ ┌──────────┐ ┌────────────────┐ │ │
│ │ │Target ECU│ │ Debugger │ │Relays & Meters │ │ │
│ │ └──────────┘ └──────────┘ └────────────────┘ │ │
│ └────────────────────────────────────────────────────┘ │
└────────────────────────────────────────────────────────┘
3.3 Setup, Cabling & Assembly Integration
3.3.1 Physical Setup
The contractor's technical team performs physical rack placement, professional cabling, and power hookups according to documentation supplied by the client. The setup is performed strictly following the client's specifications.
3.3.2 Network Isolation & Security
Critical Security Concept
By default, the network segment of a Physical Assembly has no direct routing to the public internet or corporate networks. This prevents external interference, protects intellectual property, and guarantees a noise-free test environment.
Any required outbound connectivity (e.g., external license servers, package repositories, source code) is securely proxied exclusively via the vHaaS Agent or dedicated outbound gateways.
3.3.3 Digital Twin Modeling
Following physical deployment, the contractor digitally models the cabling topology in the platform. Client teams can then control power, trigger resets, and monitor electrical state directly from the Web UI via the HAI.
3.4 Hardware Intake & Handover Process
All client hardware delivered to the Vector datacenter undergoes a documented intake process:
- Delivery Coordination: The client schedules hardware delivery in advance via the ticket system. Unannounced deliveries cannot be accepted.
- Incoming Inspection: Upon arrival, Vector staff perform a visual inspection and document the condition of all received components (type, quantity, visible damage). The client receives a signed Incoming Goods Protocol (Wareneingangsprotokoll) confirming receipt.
- Responsibility Transfer: Vector assumes operational responsibility for the hardware from the point of confirmed receipt. The client is responsible for ensuring that hardware is delivered in functional condition with all necessary documentation (wiring diagrams, pin assignments, configuration requirements).
- Inventory Management: All client-owned hardware is tracked in an internal inventory register and is clearly labelled to prevent mix-ups between tenants.
Note
The client is responsible for ensuring adequate export compliance and shipping documentation for any hardware subject to customs or export control regulations.
4. Service Level Agreement (SLA)
4.1 Provisioning Lead Times
Initial Assembly setup begins once the client has delivered all required hardware components and sufficient schematic documentation.
| Setup Size | Complexity | Lead Time (Target) |
|---|---|---|
| Small | Up to 5 devices (e.g., 1 ECU + Debugger) | ≤ 10 working days |
| Medium | Up to 10 devices (e.g., ECU + VT-System + VN-Box) | ≤ 20 working days |
| Complex | Custom multi-component systems | Project-based agreement |
Capacity Planning
Ad-hoc availability of additional resources (rack space, NUCs, HAIs, support capacity) is not guaranteed by default. Scaling the environment requires prior coordination and adequate lead time.
4.2 Operational Availability
| Component | Target Annual Availability | Recovery Time Objective (RTO) |
|---|---|---|
| Execution Environment (EE) | 95.0% | Subject to contract / Best Effort |
| Physical Assembly | 95.0% | Subject to contract / Best Effort |
| Local Rack Network | 95.0% | Subject to contract / Best Effort |
All hosted environments are monitored 24/7 via Prometheus and Grafana. Announced maintenance windows are excluded from availability calculations.
Hardware Replacement Times
No guaranteed replacement times for defective hardware components (e.g., NUC, relay card, cabling) are defined at this service level. Vector will address hardware failures on a best-effort basis and communicate expected resolution timelines to the client as soon as they are known. Clients with specific recovery time requirements should raise this during the onboarding scoping discussion.
5. Maintenance & Patching
5.1 Execution Environment (EE) Updates
| Update Type | Cycle | Notice Period | Description |
|---|---|---|---|
| Patch Update | 1st Wednesday of the month | 1 week | OS security updates, package updates, driver maintenance. |
| Unplanned Maintenance | As needed | 3 days | Urgent datacenter work, power switchover, network routing changes. |
| Security Update | As needed | Prior to rollout | Critical CVE remediation; applied within 3 days of disclosure. |
5.2 Assembly & HAI Updates
Scheduled immediately after the EE patch window on the same day.
| Update Type | Cycle | Notice Period | Description |
|---|---|---|---|
| Patch Update | 1st Wednesday of the month | 1 week | Calibration, hardware tests, configuration updates for managed components. |
| Unplanned Maintenance | As needed | 3 days | Hardware swap, urgent repairs, or infrastructure changes. |
| Security Update | As needed | Prior to rollout | Critical CVE remediation; applied within 3 days of disclosure. |
6. Support & Change Management
6.1 Incident Severity Classification
The L3 service uses the same platform-level severity classification as L2, extended with hosting-specific criteria:
| Priority | Definition | Initial Response (Target) | Resolution (Target) |
|---|---|---|---|
| P1 — Critical | Complete loss of access to a hosted workspace; no workaround available. Includes total EE or network failure. | 1 hour | Best Effort (hardware-dependent) |
| P2 — High | Significant degradation of EE performance or partial Assembly failure impacting active work. | 2 hours | Best Effort (hardware-dependent) |
| P3 — Medium | Non-critical component failure with available workaround; limited operational impact. | 4 hours | 3 business days |
| P4 — Low | General queries, configuration questions, minor adjustments. | 1 business day | Best Effort |
Support window: Mon – Fri, 08:00 – 17:00 CET. Contact via ticket system; phone escalation for P1/P2.
Note
Physical hardware incidents (P1/P2) may have resolution times beyond the platform targets due to the time required for on-site diagnosis and component sourcing. Vector will provide regular status updates until resolution.
6.2 Problem Management
For P1 and P2 incidents affecting hosted infrastructure, Vector conducts a root cause analysis and provides the client with a written Post-Incident Report (PIR) within 5 business days of resolution. The PIR covers the incident timeline, identified root cause, impact assessment, and corrective or preventive actions taken.
6.3 Support Matrix
| Support Type | Scope | Contact | Response Time (Target) |
|---|---|---|---|
| Standard Support | Application Service and Execution Environment incidents. On-site excluded. | Ticket system; phone for critical issues. | 4 hours within support window |
| Hosting Support | Incidents related to network, EE, Assemblies, and their hardware components. | Ticket system; phone for critical issues. | 8 hours (on-site dispatch) within support window |
| Support Window | Mon – Fri, 08:00 – 17:00 CET | — | — |
On-site hands-on support is available on request for hardware swaps, manual jumper configuration, or temporary measurement instrument integration.
6.4 Change Requests
Hardware changes after initial setup must be requested by the client in writing (e.g., via ticket system). Minor adjustments can be billed against a pre-agreed support budget. Larger modifications are quoted separately.
7. Pricing & Workspace Configurator
Each vHaaS Workspace consists of two components: a mandatory Execution Environment and an optional Physical Assembly. Pricing is modular and based on the chosen configuration. All costs are in addition to the L2 user license.
7.1 Component 1: Execution Environment
Minimum commitment: 1 year.
| Tier | Specifications | Annual Cost (Ubuntu) | Annual Cost (Windows Server) |
|---|---|---|---|
| Medium | Intel® Core™ Ultra 5 (14 cores), 32 GB RAM, 500 GB SSD | On request | On request |
| Large | Intel® Core™ Ultra 7 (20 cores), 64 GB RAM, 1 TB SSD | On request | On request |
7.2 Component 2: Assembly Hosting (Rack & Power)
Base hosting costs include rack space, power, cooling, cabling, and full operational service.
| Workspace Size | Recommended Use Case | Annual Fee |
|---|---|---|
| Small (1 U) | Single ECU + debugger. Ideal for modular unit testing. | On request |
| Medium (2 U) | ECU + VT-System card or VN interface box. | On request |
| High (4 U) | Multiple ECUs, high-voltage relays, complex test boards. | On request |
| Individual | Custom multi-cabinet HIL racks. | On request |
7.3 Optional Hardware Extensions
| Component | Manufacturer | Description | Cost |
|---|---|---|---|
| Board Status Pin | Vector | Visual "alive" LED readable from the platform Web UI for fast diagnosis. | On request |
| vHaaS Multiplexer | Vector | Software-controlled signal/bus-line routing between Assembly components. Significantly increases automation potential. | On request |
| VIO / VT-System Cards | Vector | Real-time I/O simulation of sensor and actuator signals for deep HIL testing. | On request |
| Logic Analyzer | Third-party | Precise trace and timing analysis of digital communication lines (I²C, SPI). | On request |
| Oscilloscope | Third-party | Voltage curve tracing and analog signal validation. | On request |
8. Reference Use Cases
Use Case 1: Standard ECU Development (HIL)
Goal: Development, routine debugging, and firmware flashing on a single physical ECU.
Recommended configuration: EE Medium + Small Assembly (1 U)
Use Case 2: Multi-ECU System Integration
Goal: Fully automated system validation of networked ECUs within a CI/CD pipeline.
Recommended configuration: EE Large + High Assembly (4 U), optionally extended with VT-System I/O cards.
9. Third-Party Providers & Licenses
| Provider / Technology | Role | Data Protection Relevance |
|---|---|---|
| CISCO | Network infrastructure (switches, rack networking) | Infrastructure sub-processor |
| Microsoft | Windows Server OS for EEs | Operating system provider |
| Canonical | Ubuntu OS for EEs | Operating system provider |
| Versatel | Internet connectivity (primary) | Internet provider |
| Telekom | Internet connectivity (redundant) | Internet provider |
For cloud-layer third-party providers (AWS, Cloudflare, identity providers), refer to the WebService Service Description §8.
Security & Data Protection
For the full security architecture, GDPR/DSGVO compliance details, Technical and Organizational Measures (TOMs), and certification status, refer to the Security & Compliance section.
10. Service Reporting
In addition to the platform-level reporting defined in the WebService Service Description §11, clients with an active L3 Hosting engagement receive a monthly hosting report covering:
- Infrastructure Availability: Measured uptime per hosted component (EE, Assembly, network) against the 95% target, excluding planned maintenance.
- Incident Summary: All P1 and P2 hosting incidents, including duration, root cause status, and resolution.
- Maintenance Overview: Completed EE and Assembly patch windows, plus any unplanned maintenance activities.
- Hardware Inventory Status: Current inventory of client-owned hardware components held at the Vector datacenter, including condition flags from the most recent inspection.
Pilot Phase
During the pilot phase, hosting reports are provided on a best-effort basis. Format and delivery cadence may evolve as the service matures.
11. Offboarding & Hardware Return
Upon contract termination or explicit client request, the following offboarding process applies:
- Termination Notice: The client submits a written offboarding request via the ticket system, specifying the desired return date and shipping destination.
- Workspace Decommissioning: Vector decommissions the workspace in the platform, disconnects all cabling, and removes the client's physical hardware from the rack. A decommissioning date is agreed upon with a minimum lead time of 10 business days.
- Condition Inspection: Before shipping, Vector staff perform a visual inspection of all client hardware and document the condition. The client receives a signed Outgoing Goods Protocol (Warenausgangsprotokoll).
- Return Shipment: Client hardware is packaged and shipped to the address designated by the client. Shipping costs and any insurance for the return transport are borne by the client unless otherwise agreed.
- Data Deletion: All configuration data and platform records associated with the decommissioned workspace are deleted within 30 days of the final decommission date. A deletion confirmation is provided upon request.
Warning
Vector-owned infrastructure components (NUCs, HAI relay cards, network switches, racks) remain the property of Vector and are not included in the return shipment.