Skip to content
  • There are no suggestions because the search field is empty.

Source Input List

Overview

The Source Input List is used to define all content sources that will be made available within your visability environment.

This document is a key input into system configuration, ensuring that all required sources are properly identified, prioritized, and prepared ahead of deployment.

Template for Download: Source Input List

Purpose

The Source Input List allows the project team to clearly understand:

  • What sources need to be available
  • Where those sources originate
  • Who is responsible for them
  • How critical each source is to operations

Providing this information upfront supports accurate system configuration and helps streamline deployment and commissioning activities.

Defining Your Sources

Each row in the Source Input List represents a source or group of sources that will be available in the system.

Typical sources include (See Source Types for more Information):

  • Video streams (cameras, encoders, RTSP feeds)
  • Physical inputs (HDMI-connected devices)
  • Web-based dashboards
  • Applications
  • Interactive systems (KVM-enabled sources)

Grouping Similar Sources

In environments with a large number of similar feeds (such as camera systems), it is not necessary to list every individual source.

Instead, a single row can be used to represent a group of similar inputs.

Example:

  • Security Cameras (100 Feeds)
  • Traffic Cameras – Citywide

When grouping sources, include:

  • The stream type (e.g., RTSP, multicast)
  • The vendor or system (e.g., Axis, Hanwha, Milestone, Genetec)

This keeps the document focused on system configuration rather than detailed inventory tracking.

Information to Provide

When completing the Source Input List, ensure the following fields are populated:

  • Source ID – Unique identifier for each source
  • Source Name – Clear, recognizable name
  • Source Type – Selected from the provided dropdown
  • Location – Where the source originates
  • Owner – Responsible team or individual
  • Priority – Operational importance (High, Medium, Low)
  • Notes – Any additional relevant details

Providing complete and accurate information in these fields enables efficient setup and reduces the need for follow-up during deployment.

Submission

Once the Source Input List has been completed, it should be shared with the appropriate project team members for review.

Once this form is complete, please send the finalized document to all required project stakeholders, including the integrator and vis|ability personnel, to support review, validation, and successful commissioning.