Structured reservations
Capture the project, device model, board count, duration, preferred time, and execution script. Separate demand from confirmed assignment.
iPlan
Palladium emulator time management
Bring reservations, allocation decisions, execution monitoring, and utilization into one workflow. Give engineers a clear request process and administrators a practical way to govern shared Z1/Z2 capacity.
Palladium board and time visibility. English labels are localized from an actual product screenshot for illustration; confirm available UI languages during evaluation.
From competing requests to usable device time
Allocation strategies
Choose priority, fair share, or assignment-rate policies. Review candidate schedules and handle exceptions before publishing.
Backfill
Match released time to eligible waiting requests that accept backfill and fit the remaining window.
Maintenance planning
Make unavailable device time visible in the calendar so reservations and scheduling reflect operational constraints.
Execution monitoring
Connect server and worker services to collected device state. Observe starts, no-shows, releases, and order outcomes.
Utilization reporting
Review user and emulator utilization trends, then use the evidence to improve allocation rules and capacity decisions.
A daily workflow with administrator control
Request
Engineers submit device and timing requirements. Competing reservations are allowed.
Lock
A configured cutoff freezes eligible requests for the next allocation cycle.
Allocate
The selected policy generates a candidate schedule from capacity and request constraints.
Review
Administrators inspect allocations and handle permitted adjustments before publication.
Execute
Users receive results; runtime collection supports state checks and backfill handling.
Measure
Review utilization and exceptions to refine priorities, limits, and reservation behavior.
One order record for requests and outcomes
English-localized illustration based on the existing order interface, not a screenshot of a released English UI.
For engineers
Submit and track requests, inspect the calendar, copy orders with updated time preferences, and release unused assigned time. Actions follow ownership and order state.
For administrators
Maintain projects and limits, schedule maintenance, select allocation policies, and adjust future capacity. Lock windows keep the daily review controlled.
Run in your environment
Deploy the server and worker services on premises. Integrate with configured enterprise identity and device collectors.
- JWT authentication, LDAP, and role-based access controls
- Separate server and worker services, with REST and gRPC interfaces
- Device and order state collection for supported emulator environments
- In-app notifications and documented Feishu integration
Scope the integration before rollout
Confirm emulator versions, board topology, authentication, time zone, language needs, and notification channels. Feishu is documented; Lark and other messaging integrations need separate validation.
English product and user documentation is available. A scoped quote can cover implementation, training, and support expectations for your environment.
Measure value with a representative pilot
Start with a device group, projects, and a real allocation period. Establish a baseline and agree on acceptance criteria before expanding deployment.
- Automatic assignment
- How many eligible requests are assigned without manual intervention?
- Idle capacity
- How much available device time remains unused?
- Backfill outcomes
- How often is released capacity successfully reused?
- Manual exceptions
- Where do administrators need to change the generated schedule?
- Assigned versus used
- What is the difference between the schedule and observed usage?
- Planning effort
- How much operator time does an allocation cycle require?