microsoft word - intransa-storstac-aande-specification-v11.doc

www.intransa.com 1

Intransa StorStac™ Shared External IP Storage

Architecture and Equipment Specification

November 2008

www.intransa.com 2

Contents

1. Introduction 3

2. StorStac Description 4

2.1 Product Description 4 2.2 Applicable Environments 4

3. Shared, External IP Storage Product Requirements 5 3.1 Requirement Overview 5 3.2 Scalability 5 3.3 Independent Scalability of Performance and Capacity 6 3.4 Connectivity and Data Transfer 6 3.5 Administration and Management 7 3.6 Storage Utilization and Operation 8 3.7 Integration and Certification 10 3.8 Operation and Playback 10 3.9 Infrastructure Selection 11 3.10 Data Protection 11 3.11 Connectivity, Application and Protocol Support 12

4. Environmental and Physical Requirements 16 4.1 Power Consumption 16 4.2 HVAC Requirements 16 4.3 Floorspace / Rackspace Consumption 16 4.4 Electrical and Safety Certification Specifications 16 4.5 Environmental Specifications 17 4.6 Intransa Shared, External IP Storage Specifications 17

4.7 Intransa StorStac System Configurations 17

5. Pricing Considerations 20 5.1 Capital Expenditure (CapEx) 20

5.2 Operating Expenditure (OpEx) 20

www.intransa.com 3

1. Introduction

This Architecture and Equipment Specification details high-level, general requirements for Intransa shared, external IP storage when deployed in a physical security environment.

Intransa StorStac™ shared, external IP shared storage forms the underlying backbone of all of these system requirements, delivering increased reliability, scalable retention, and improved video quality with reduced administration.

www.intransa.com 4

2. StorStac Description

2.1 Product Description

Intransa StorStac shared, external IP storage is a proven, optimized video recording and playback infrastructure and retention platform for use in video surveillance and other physical security application environments. StorStac solutions support both standard 1GbE (1 Gigabit Ethernet) and high bandwidth 10GbE (10 Gigabit Ethernet) IP network infrastructures. StorStac shared, external IP storage provides scalable system throughput of 220MB/s (220 Megabyte/second) to 3,000MB/s for a wide variety of application requirements. StorStac provides modular video storage scalability from 6TB (Terabytes, each 1,000GB) to 1,500TB (or 1.5PB) of RAID protected, hot-swap disk drives and components for non-stop, 24x7x365 retention and playback. StorStac BuildingBlock (left) is designed to support 1GbE IP network infrastructures. StorStac PerformanceBlock (right) supports 10GbE IP infrastructures. Both use identical Storage Capacity Enclosures. 2.2 Applicable Environments StorStac has been designed for and is currently implemented around the world for applications including:

� CCTV video surveillance system storage upgrades for increased retention capacity, maximum resolution and frame rate, and improved reliability. StorStac accomplishes this without replacing existing infrastructure including cameras, DVRs/NVRs, and software to protect investment, while creating a hybrid environment that delivers the benefits of both IP and analog devices;

� Direct-from-IP-camera recording to leverage the capabilities of approved IP network

and megapixel cameras, video analytics and video management systems from leading manufacturers and up-and-coming vendors;

� All-IP physical security deployments as the storage infrastructure providing storage

capacity for access control, biometrics, life safety, physical security information management systems, video analytics, and video surveillance systems.

www.intransa.com 5

3. Shared, External IP Storage Product Requirements

3.1 Requirement Overview

Intransa StorStac shared, external IP storage will provide the features, functions, and basic capabilities required by the cameras, DVRs, NVRs or the Video Management System application and is simultaneously sharable by multiple “host” servers or NVRs running the Video Management System. 3.2 Scalability The shared, external IP storage must be cost effective from a small to large deployment. It must be able to scale easily, from support for a single DVR or NVR with a few cameras, to grow to support thousands of cameras and hundreds of DVRs and NVRs, with days to weeks, months or years of retention and instant playback. This will allow support for future growth and changes in requirements, without replacing the physical storage infrastructure. Storage capacity of the shared, external IP storage should grow from as little as 6TB of RAID protected, hot swap disk drives modularly to 1,500TB (1.5PB). In order to support additional physical security applications that may need to be added to the storage infrastructure as future requirements change, system throughput must be able to scale from a minimum performance capability of 220MB/second to 3,000MB/second byadding or upgrading the shared, external IP storage system without forklift replacement. StorStac system performance can be increased by adding additional Performance Controller Units (PCUs). A single StorStac shared, external IP storage system can support up to 4 PCUs, each adding system performance capability, without adding extra storage capacity that is not yet required.

StorStac shared, external IP storage systems can grow capacity for video retention by adding individual storage capacity enclosures (SCEs) without requiring additional, unneeded system performance.

www.intransa.com 6

The security practitioner or operator must be able to increase storage performance without interfering with the work of the Video Management System or DVR application. Such non-disruptive upgrades allow the addition of capacity or performance enhancement hardware to the shared, external IP storage system without halting video recording/playback operations. 3.3 Independent Scalability of Performance and Capacity The security practitioner or operator must be able to increase overall throughput performance of the shared, external IP storage independent of capacity. As camera counts, bandwidth usage, or video retention requirements increase, the shared, external IP storage must scale performance accordingly, without requiring the addition of un-needed storage capacity (disks) and incurring the additional cost of that capacity before it is actually needed. Shared, external IP storage should be capable of being modularly grown for either performance – by adding Performance Controller Units (left) - or for capacity – by adding Storage Capacity Enclosures (right) – independently of one another. This avoids being required to buy more performance or capacity before it is needed. The shared, external IP storage must allow for the addition of an unlimited number of storage controllers (performance controller units) to the system to address any increase in throughput requirements. 3.4 Connectivity and Data Transfer The shared, external IP storage must also provide data transfer functions either from remote branch office (such as a individual bank branch or retail store) to a central location (such as a security operations center/SOC or video repository), or from one shared, external IP storage system to another. Asynchronous data replication over fault resilient IP communication infrastructure must be provided.

www.intransa.com 7

3.5 Administration and Management The shared, external IP storage must be physical security oriented and easy to use and monitor by security practitioners and operators, without specialized IT knowledge. The shared, external IP storage should be easy be maintain, with a configuration and administration interface that uses physical security terminology (frame rate, resolution, retention, compression, number of cameras, etc.) and not complicated IT network or storage terminology to deliver basic functionality.

� Single Management Tool Regardless of how many instances or the sizes of the shared, external IP storage systems that are deployed, the entire video surveillance storage environment must be manageable through a single, graphical user interface (GUI).

� Web Based Access

The shared, external IP storage should provide a Web-based browser access (such as by Microsoft Internet Explorer) GUI that can be integrated with the existing video management system GUI. There must be a single system view and storage virtualization across all storage enclosures. A single image does not represent a GUI with access to all enclosures but rather the ability of any interface/enclosure to access data across any other enclosure.

www.intransa.com 8

� Storage Estimation Tool

The shared, external IP storage must provide a tool for the security practitioner or operator to use in order to estimate the total space needed for specific scenarios (e.g. number of cameras, video quality, FPS, retention). The output of this estimating tool should automatically configure the underlying storage arrays without detailed storage knowledge. This estimate should also be automatically monitored and analyzed as the scenario changes and the shared, external IP storage must be able to warn the security practitioner or operator of negative conditions, such as impending disk storage shortages impacting overall retention.

� Alerting

The shared, external IP storage must provide alerts to the user interface GUI, through email/pager connections, and through SNMP to management frameworks. At a minimum, alerts should be issued by the storage system for system failures, component failures (e.g. disk crashes), “failing” conditions, threshold maximums and pre-set minimum available space, performance, or other system conditions.

� Reporting

The system should provide reporting for routine metrics including capacity utilization, CPU utilization, storage volume configurations, disk groups, etc. that the security practitioner or operator can use to easily understand storage system status.

3.6 Storage Utilization and Operation The shared, external IP storage must provide the best storage capacity utilization, leveraging advanced features that include load balancing, global hot disk sparing, storage consolidation and virtualization. The shared, external IP storage should not regularly require system shutdown or impose major performance degradation for routine applications such as defragmentation of storage. Transparent to the Video Management System (VMS) application or the NVR(s), the shared, external IP storage must provide several capabilities for the creation and management of storage volumes. Further, all these functions must be accomplished without interruption of service to the application for non-stop operation. The required capabilities include:

� Adding or Provisioning Storage Volumes

The security practitioner or operator must be able to provision any number of storage volumes (e.g. drive E:, drive F:) of any size in the shared, external IP storage.

The addition of volumes to the installed system must happen in real time with zero down time of the system and the recording of video to the storage device must not be interrupted during the process.

� Growing or Expanding the Size of Storage Volumes The shared, external IP storage must be able to increase space utilization by growing the size of the storage volume.

Growing volumes to accommodate an increase storage demand from a set of cameras due to a number of reasons must be supported by the system in real time.

www.intransa.com 9

This methodology would allow the user to only use the space immediately required instead of buying and allocating excess capacity in advance.

For video management systems that require a “lifetime maximum LUN size” is specified when the storage volume is created, a “thin provisioning” capability must be provided to overcome this limitation, optimizing utilization by the shared, external IP storage.

For video management systems or NVRs that do not require a “lifetime maximum LUN size” at time of storage volume creation, a “grow volume” capability must be provided to optimize utilization in an ongoing manner.

� Moving Storage Volumes

Security practitioners or operators must be able to migrate or move storage volumes from one storage system to another.

� Concatenating Storage Volumes

To support large scale storage needs, the shared, external IP storage needs to support storage volumes be spread across multiple disk groups within the storage system.

� Cloning Storage Volumes For upgrades, technology refresh, backup, or disaster recovery operations, the shared, external IP storage must support storage volume cloning, or enable the creation of a full copy of the volume in real time.

� Automatic Load Balancing The Shared, external IP storage must provide automatic load balancing, supporting seamless performance delivery when:

1) The security administrator or operator is adding performance capability; 2) When a failure occurs and the storage system automatically fails over to another storage performance controller unit, and automatically load balances between remaining devices to minimize impact on the current video record/playback workload.

� Dynamic Reconfiguration

Security practitioners and operators must be able to add performance to the surveillance system without interrupting service, including recording and playback. The shared, external IP storage must dynamically accept additional performance controllers and additional storage capacity without requiring a system reboot or interrupting current recording, playback or system performance.

� Recording Latency

Any frame loss due to recording latency should be measurable on a statistical basis. The shared, external IP storage should support Zero Frame Loss operation. Additionally, the system should provide a toolset to analyze and estimate the necessary number of disk drives or enclosures to ensure a tolerable frame loss ratio as defined by the specific application environment or operator.

www.intransa.com 10

� Remote Boot

The shared, external IP storage system should support remote boot functionality. Remote reboot, also referred to as “iSCSI boot” or “diskless operation”, enables the recording platform (such as a DVR or NVR) to be launched using the shared, external IP storage and eliminating the need for such devices to have local disk drives. This reduces cost, improves system reliability and decrease administrative burden. The shared, external IP storage should support booting several servers (DVRs or NVRs) simultaneously without any downtime for the whole system.

3.7 Integration and Certification In addition to video data recording, the shared, external IP storage should support other physical security applications, including storage of files and databases, to allow maximum utilization of the system, now and in the future. The shared, external IP storage must be tested and certified with a wide range of 3

rd party

applications and hardware in this manner to ensure proper integration. These applications should include access control, authentication, biometrics, imaging, infrastructure providers, IP megapixel cameras, IP network cameras, IT, network video recorders (NVRs), physical security infrastructure management systems (PSIMS), physical security utilities, video analytics and video management systems (VMS). The shared, external IP storage must be able to integrate with the other components of the physical security system at both hardware (Ethernet, IP, iSCSI) and software (GUI, API, SNMP) levels. Intransa shared, external IP storage is certified through the StorAlliance Technology partner labs with nearly 100 physical security, imaging, and IT applications and products (as of November 2008). Intransa StorStac systems are also certified by the independent IPVS Magazine labs. 3.8 Operation and Playback The shared, external IP storage must allow fast access to recorded video data. The shared, external IP storage must be able to provide fast simultaneous retrieval and recording from several locations or video streams without compromising recording speed.

www.intransa.com 11

The shared, external IP storage recording capability should not be affected by the retrieval process under normal conditions. The system must continue recording video streams while the security practitioner or operation is retrieving/viewing stored video. 3.9 Infrastructure Selection The security practitioner or operator must be able to choose when and where to deploy standard Ethernet (1GbE) infrastructure or higher bandwidth infrastructure (10GbE) without having to change storage solutions. The shared, external IP storage must be able to support an increase in network controller Performance, allowing for support of 1GbE, 10GbE, and any future increases in standards-based IP throughput/bandwidth technology. 3.10 Data Protection The shared, external IP storage must provide advanced data protection including fault resilient RAID (Redundant Array of Independent Disk) protection levels 0, 1, 5, 10 for video loss prevention. The storage must also be designed with OEM-grade components for increased reliability rather than less dependable PC- or consumer grade devices.

� Availability & Redundancy

The shared, external IP storage must be able to be reconfigured for support of fault resilient to highly available configurations without interrupting system availability.

� Fault Resilient Configurations

The shared, external IP storage must support fault resilient single data path, non-redundant hardware and software configurations, with hot swap disk drives, power supplies and fans, and field replaceable components.

� High Availability Configurations

The shared, external IP storage must support non-stop operational environments with multiple data paths for hardware and software configurations, with fully redundant, hot swap hardware components and automatic failover capability. The shared, external IP storage must support redundant pathways to ensure that the storage is always accessible and provide redundant storage management tools so that even with multiple component failure the video recording/playback traffic is directed through alternative routes and is able to continue.

Intransa StorStac shared, external IP storage systems feature hot-swap disk drives with global hot sparing.

www.intransa.com 12

High availability configurations must eliminate all single points of failure.

� Disk Groups

The shared, external IP storage should support disk groups of multiple sizes and numbers of disk drives. A disk group can be made to appear to a VMS, DVR or NVR as a single drive letter or volume (e.g. Drive E:), yet actually be composed of multiple disk drives in a single enclosure or multiple enclosures.

� RAID Levels for Data Reliability

The shared, external IP storage must allow data redundancy and enable data restoration in case of disk failure by supporting RAID protection. The RAID level (0, 1, 5 & 10) must be selectable by the security practitioner or operator to meet individual application or volume requirements. The shared, external IP storage must provide automatic data recovery from individual disk failures with no downtime of the overall system. Global sparing should be provided across a single or multiple enclosures to reduce the amount of standby drives required for RAID support.

� Disk Drive Reliability

The meantime between failures (MTBF) should be as high as commercially available, typically exceeding 1 million hours of operation for OEM-grade disk drives used in the shared, external IP storage solution.

� RAID 5 Rebuild Performance

After any disk failure, the shared, external IP storage should continue to operate without interfering with the video streams or the VMS, NVR or DVR system. Video channels or recording streams should not be forced off line and frames should not be dropped/lost during a RAID5 rebuild to recover lost video.

3.11 Connectivity, Application and Protocol Support

� Physical Connections

The principal physical connection will be standard 1GbE Ethernet. In anticipation of the growing adoption of 10GbE network infrastructures in physical security, the shared, external IP storage must be upgradeable to also support 10GbE IP networks.

Intransa StorStac fault resilient shared, external IP storage systems feature hot-swap disk drives, power supplies and fans and field replaceable data path units. Intransa StorStac high reliability shared, external IP storage systems feature hot-swap disk drives, power supplies, fans, and data path units.

www.intransa.com 13

� Communications Protocols

IP running over both 1 & 10GbE network infrastructure is required. The shared, external IP storage should support SNMP and traps.

� Video Standards

The shared, external IP storage must support recording in all common standards via the surveillance and monitoring applications. These standards included 2CIF, CIF, QCIF, 4CIF and 8CIF compression and standard graphics file formats including JPEG, MPEG, MPEG-1,-2,-4 & BMP in multiple real time/time lapse formats. CCTV still, motion, full motion, time lapse, pan/tilt/zoom day/night/infrared digital and analog camera feeds with multiple FPS and resolution rates is supported. New standards such as H.264 must also be supported.

� Video Management Systems

The shared, external IP storage must support leading VMS, PSIM, infrastructure, analytics, access control, compression, and other physical security hardware and software providers. These should include some or all of the following vendor certifications to ensure proper integration and post-sale support.

www.intransa.com 14

All of these vendors have one or more products which have completed Intransa StorAlliance Technology Lab testing and are members of the StorAlliance.

� Storage Protocols

The system must provide the iSCSI target side of the iSCSI standard infrastructure. Standard IP network infrastructure, in both 1 and 10GbE, should be supported.

� WQHL

The shared, external IP storage must support Microsoft WHQL certification.

www.intransa.com 15

� iSCSI Initiator Support

The shared, external IP storage must support standard Linux and Windows iSCSI initiators commonly used by non-proprietary operating system based DVR and NVR systems. These include:

Operating System Initiator Microsoft Windows 2008 64bit Windows iSCSI Initiator Default

Microsoft Windows 2008 Windows iSCSI Initiator Default

Microsoft Windows Vista SP1 64bit Windows iSCSI Initiator Default

Microsoft Windows Vista SP1 Windows iSCSI Initiator Default

Microsoft Windows 2003 SP2 64bit Windows iSCSI Initiator - latest

Microsoft Windows 2003 SP2 Windows iSCSI Initiator - latest

Microsoft Windows XP SP2 Windows iSCSI Initiator - latest

Red Hat RHEL3 Linux iSCSI Initiator - latest

Red Hat RHEL4 Linux iSCSI Initiator- latest

SUSE Linux 9.2 Linux iSCSI Initiator - latest

Solaris 10 for x86 Solaris iscsiadm version- latest

� Disk Drive Density Support

The shared, external IP storage should be capable of being configured with a minimum of multiple 750GB, and 1TB or larger SATA-II disk drives. Enclosures must support at least 12 disk drives in a 2U footprint or 15 drives in a 3U footprint. All disk technology in the shared, external IP storage should be Enterprise or OEM grade. The shared, external IP storage should be capable of being configured with SATA-II or SAS drive technologies with 7.2K, 10K, or 15K rotation speeds.

www.intransa.com 16

4. Environmental and Physical Requirements The shared, external IP storage will provide environmentally-friendly architectures and technologies.

4.1 Power Consumption

The security practitioner or operator should consider the consumption of power by the shared, external IP storage as a green IT technology. The system must be as electrically efficient as commercially possible. Low energy consuming IP infrastructure (in place of analog coax or high energy consuming Fibre Channel) is mandatory. High density designs should make maximum disk drive capacities available such as 750GB or 1TB disk drives in tight 2U or 3U spaces to reduce the cost and energy consumption per terabyte. High performance network infrastructure options such as 10GbE IP should be available in the solution options so as to reduce the number of network switches, servers, controllers and other physical platforms supporting large numbers of cameras or high bandwidth requirements.

4.2 HVAC Requirements

The security practitioner or operator should also consider HVAC (heating, ventilation, and air conditioning systems) requirements of the shared, external IP storage. The system must radiate a minimum of heat (BTU), within normal IT-grade bounds for efficient storage solutions. Well designed configurations that only require additional processor/throughput capacity (such as Performance Controller Units) or storage enclosures when additional capacity is required (such as Storage Capacity Enclosures) to be added when needed are highly valued. Systems requiring larger footprints with unused capacity or performance and which therefore waste heating and cooling energy by providing more than is immediately required are to be avoided.

4.3 Floorspace / Rackspace Consumption

The security practitioner or operation should consider the amount floorspace or rackspace required by the shared, external IP storage. The system must provide high density technology and compact packaging consuming a minimum of RUs (rack units). Usage of global hot spare disk drives required for RAID configurations, and consolidation and virtualization features, to reduce overall floor and rackspace consumed are key features.

4.4 Electrical and Safety Certification Specifications

Standard equipment certification must be applicable to the shared, external IP storage. These should be at a minimum:

� FCC Class A � EN 55033 Class A � CE Mark, � ICES-003 Class A (Canada)

www.intransa.com 17

� RoHS

4.5 Environmental Specifications

The shared, external IP storage solution should operate in a wide range of normal business environmental specifications.

� Temperature - 10 to 35°C (50 to 104°F) � Humidity - 10% to 90% non-condensing

4.6 Intransa Shared, External IP Storage Specifications

Maximum performance capability is 4 PCUs, either BuildingBlock or PerformanceBlock. Maximum capacity is 1,500 terabytes, either BuildingBlock or PerformanceBlock. 4.7 Intransa StorStac System Configurations

STORSTAC BASE SYSTEMS Each StorStac BuildingBlock (1GbE) and PerformanceBlock (10GbE) shared, external IP storage system is available in either Fault Resilient or High Availability configurations. Each StorStac shared, external IP system requires a minimum of one BuildingBlock or PerformanceBlock Base System and one SCE Storage Capacity Enclosure. For best performance/reliability, Fault Resilient and High Availability configurations should not be mixed in a single StorStac shared, external IP storage system.

StorStac BuildingBlock Fault Resilient Configuration Base System

PCU25 Performance Controller Unit with 2x 1GbE ports, dual hot swap power supplies and fans, switched interconnect, 220MB/second total system throughput

3RU

Maximum 350 watts total power consumption

StorStac BuildingBlock High Availability Configuration Base System

Dual PCU25 Performance Controller Units each with 2x 1GbE ports, dual hot swap power supplies and fans, dual switched interconnect, 440MB/second total system throughput

6RU


StorStac Performance Block Fault Resilient Configuration Base System

PCU100 Performance Controller Unit with 1x 1GbE port, dual hot swap power supplies and fans, switched interconnect, 750MB/second total system throughput

4RU


www.intransa.com 18

StorStac Performance Block High Availability Configuration Base System

Dual PCU100 Performance Controller Units each with 1x 1GbE port, dual hot swap power supplies and fans, dual switched interconnect

8RU


STORSTAC STORAGE CAPACITY ENCLOSURES One SCE Storage Capacity Enclosure required per base system.

StorStac BuildingBlock/PerformanceBlock Fault Resilient Storage Capacity Enclosure

SCE Storage Capacity Enclosure with dual power supplies and fans, maximum 15 hot swap drive slot enclosures for SATA-II or SAS drives. RAID 0, 1, 5 and 10 with global hot sparing. Single, field replaceable data path unit.

3RU


StorStac BuildingBlock/PerformanceBlock High Availability Storage Capacity Enclosure

SCE Storage Capacity Enclosure with dual power supplies and fans, maximum 15 hot swap drive slot enclosures for SATA-II or SAS drives. RAID 0, 1, 5 and 10 with global hot sparing. Dual, hot swap data path units.

3RU


STORSTAC STORAGE EXPANSION ENCLOSURES Each SCE can support up to three SEE Storage Expansion Enclosures. StorStac BuildingBlock/PerformanceBlock Fault Resilient Storage Expansion Enclosures

SEE Storage Expansion Enclosure with dual power supplies and fans, maximum 12 hot swap drive slot enclosures for SATA-II or SAS drives. RAID 0, 1, 5 and 10 with global hot sparing. Single, field replaceable data path unit.

2RU


StorStac BuildingBlock/PerformanceBlock High Availability Storage Capacity Enclosure

SEE Storage Expansion Enclosure with dual power supplies and fans, maximum 12 hot swap drive slot enclosures for SATA-II or SAS drives. RAID 0, 1, 5 and 10 with global hot sparing. Dual, hot swap data path units.

2RU


www.intransa.com 19

STORSTAC PERFORMANCE CONTROLLER UNITS Up to 3 additional PCUs can be added to all Fault Resilient StorStac BuildingBlock / PerformanceBlock configurations for a maximum of 4 PCUs. Up to 2 additional PCUs can be added to High Availability StorStac BuildingBlock / PerformanceBlock configurations for a maximum of 4 PCUs. For best performance/reliability, individual StorStac systems should be all BuildingBlock (PCU25 1GbE) or PerformanceBlock (PCU100 10GbE) based without mixing PCU types. StorStac BuildingBlock PCU25 Performance Controller Unit

PCU25 Performance Controller Unit with dual hot swap power supplies and fans with 2x 1GbE ports for BuildingBlock systems

1RU


StorStac PerformanceBlock PCU100 Performance Controller Unit

PCU100 Performance Controller Unit with dual hot swap power supplies and fans with 1x 10GbE port for PerformanceBlock systems

2RU


Intransa PCU25, front view.

Intransa PCU100, rear view with cover removed, showing dual hot swap power supplies, also found in PCU25s.

www.intransa.com 20

5. Pricing Considerations

5. 1 Capital Expenditure (CapEx)

CapEx represents the direct costs of acquisition of the initial shared, external IP storage. The video surveillance marketplace is highly competitive and therefore CapEx or product price can be a major factor in customer decisions. For accuracy, CapEx must include all the hardware, software, and any infrastructure needed for the shared, external IP storage to run, plus any installation or integration costs.

� Hardware

The shared, external IP storage hardware Bill of Materials should include all hardware required to make the full system operational. This includes all enclosures, cables, connectors, power connections, etc.

� Software

The shared, external IP storage software Bill of Materials should include all software required to make the full system operational.

� Installation

Installation itemization should include all steps, procedures, or other operations necessary to bring the shared, external IP storage online and available to the Video Management System, DVR or NVR.

5.2 Operating Expenditure (OpEx)

These are the costs of managing and maintaining the Shared, external IP storage over the lifetime of the system. These costs include customer support, hardware, software updates, etc.

� Annual Maintenance

All maintenance costs should be identified including all spares, FRUs, or other support items. Intransa shared, external IP storage includes 3 years of customer hardware protection, including spare parts, telephone support and web access standard.

� Software Upgrades

All upgrades to the shared, external IP storage software must be itemized for major, minor and maintenance releases during and after the initial warranty period. Intransa shared, external IP storage includes 1 year of customer software protection, including major, minor and maintenance releases standard.

� Labor Costs

The Total Cost of Ownership (TCO) calculation includes the cost of labor to operate the system.

This is the cost of any labor beyond Installation of the system. All such costs must be itemized and either a fixed rate or a “guesstimate” should be provided.

www.intransa.com 21

Intransa, Inc. Corporate Headquarters 2870 Zanker Road, Suite 200, San Jose, CA 95134-2114 866 446 7726 or 408 678 8600 / www.intransa.com / [email protected] © 2008 Intransa, Inc. All rights reserved.

microsoft word - intransa-storstac-aande-specification-v11.doc

Documents