Where this offering fits
Horizon is BlueCat’s SaaS-first NetOps platform positioning across core network services, security and visibility. A proposal should identify the particular functions required now, rather than treating a platform description as a complete entitlement list. Existing DDI and network dependencies still need a migration plan.
Architecture and rollout decisions
Confirm connected services, processing arrangements and administrator permissions. Pilot a representative operational task with the teams that maintain the underlying network. Test unavailable connections and the effect on local service. Document the subscription scope and the boundary between platform administration and customer network changes.
An evaluation scenario for this offering
Choose one day-to-day NetOps task for the Horizon pilot, such as reviewing and approving a change to a test service record. Identify the local services and management connections involved before starting. Have two authorised roles carry out the request and review steps, then temporarily interrupt the test management connection. Ask the local operator to verify the actual service state independently. On reconnection, reconcile the central record and any pending work. Acceptance should identify what the hosted platform manages, which functions remain local and how stale information is recognised, rather than assuming a SaaS console removes all site-level operating duties.
Evidence to request for this scope
- Obtain a current function and subscription schedule.
- Validate integrations with retained services.
- Define local continuity and central access recovery.