Attachment K Functional and Technical Requirements
Definitions/Abbreviations/Acronyms
Acronym/Term Meaning
Account Executive The Representative appointed by the Contractor who is responsible for the daily management and
administrative functions of the Contract from the Contractor's perspective
BAFO Best and Final Offer
COMAR Code of Maryland Regulations available on line at www.dsd.state.md.us.
Contract The Contract awarded to a successful Offeror pursuant to the RFP. Please refer to attachment A in
the RFP.
Contract Administrator The State Representative for the project designated in Section 1.8 and who is primarily responsible
for Contract administration functions.
EMS Emergency Medical Services
EMSOP a jurisdictional EMS operational program approved under COMAR 30.03.02 or an institution,
agency, corporation, or other entity that is licensed by MIEMSS as a commercial service under
Education Article § 13-515, Annotated Code of Maryland
IT Information Technology
MIEMSS Maryland Institute for Emergency Medical Services Systems
MBE Minority Business Enterprise certified by the Maryland State Department of Transportation under
COMAR 21.11.03.
Offeror An entity that submits a proposal in response to this RFP
Procurement Officer The State representative designated in Section 1.7, who is responsible for the Contract, determining
scope issues, and is the only State representative that can authorize changes to the Contract.
MIEMSS may change the Procurement Officer at any time by written notice to the Contractor.
System For the purpose of the requirements document, the term "System" refers to the software,
applications, databases)), necessary utility programs and toolkits that provide the required
functionality, and which the offeror is authorized to sell and license to customers.
It excludes software that the vendor cannot license to the customer or other software already owned
by the customer and which is not part of the vendor product offering.
Multimedia Logging Recorder
Multimedia Logging Recorder
Project No. D53XXXXXXXX
Date______________
Attachment K Functional and Technical Requirements
Attachment K Functional and Technical Requirements
Requirements Matrix – Introduction
The purpose of this document is to provide Offerors a detailed list of requirements necessary to support future Multimedia Logging Recorder (MLR)
functions and processes. The terms below are used through the matrix and are defined below to ensure the correct interpretation for the purposes
of this document.
"Shall vs. Should" - The State uses the word "shall" to refer to must have requirements, and "should" to refer to desired functionality.
System - For the purpose of the requirements document, the term "System" refers to the hardware, firmware, software, applications, database(s),
documentation, necessary utility programs and toolkits that provide the required functionality of the Multimedia Logging Recorder, and which the
offeror is authorized to sell and license to customers.
It excludes products that the vendor cannot license to the customer or other products already owned by the customer and which is not part of the
vendor product offering.
Notify refers to the ability to produce notices and submit via mail, electronic mail and workflow. Notifications sent to employees, candidates,
contractors or other persons track in the database must include the ability to mail hard copy.
Instructions
Outlined below are specific instructions on how to complete each requirement.
1 Please check row heights on the worksheets to insure you can read all the text contained in each cell. Resize row heights if necessary.
2 Do not change the order of lines within the spreadsheets.
3 Provide answers in attachments or separate sheets if answers become extensive. Provide a reference to the technical or functional requirement
number.
Requirement# - This column indicates the State‘s unique identifier for each requirement. The letters indicate the functional area and the number
indicates the number within that functional area.
Description – This column documents the State‘s detailed requirement.
Offerors must respond to each requirement by placing and "X" in the appropriate column. Any explanation, and requested details
should be supplied in the comments section of the matrix. If you require additional space, you should reference the appropriate
attachment number in the comments section.
Standard Feature – The System achieves this requirement without modifications. Functionality is provided through standard features or a range of
defined parameters to achieve the functionality.
Configuration – The System achieves this requirement by requiring that some configuration (but not customization) is done. Configuration is
defined as using the vendor‘s toolset or procedures to tailor the system (e.g., changes to database, display screens, system connections and
actions, defining rules or using APIs). This configuration does NOT involve creating an external application, customized code or equipment or
using independent or third party applications or hardware to meet the requirement. No periodic maintenance is required to keep this functionality
working when maintenance packs/future release sets are applied.
Add On or Third Party Product – The Offeror‘s System meets this requirement through a separate module, system or third party product
integrated with the core System, provided by either the Offeror or a Third-Party vendor but supported by the Offeror. Please indicate the 3rd party
vendor and the hardware or software and version being provided in the comments column.
Planned Capability and Timeframe – The Offeror‘s System does not currently meet this requirement; however, the Offeror is currently developing
this capability within their System. Supply the date by which the Offeror will make this capability available.
Modification (Estimate Effort Level in Comments) – The Offeror‘s System does not meet this requirement; however, the Offeror knows that they
can meet this requirement through a modification. Provide an estimate of the number of total man hours required to meet this requirement in the
comments column.
Not Met – The Offeror‘s System does not meet this requirement.
Multi Media Logging Recorder
Multimedia Logging Recorder
Project No. D53XXXXXXXX
Date______________
Attachment K Functional and Technical Requirements
Comments – Any notes or comments the Offeror feels are significant and important for the State‘s evaluation of their ability to meet a requirement.
Multi Media Logging Recorder
Functional Requirements To Be Completed by Offeror
Modification
(Estimate the
Add-On Planned Level of Effort by
or 3rd Party Capability hours in the Not
Req.# Description Standard Feature Configuration Product and Timeframe Comments) Met Comments
FR.1 Ability to record 64 concurrent channels of analog audio (via passive tapping).
FR.2 Ability to log multimedia streams (video, computer displays, etc.)
FR.3 Power fail recovery ability without loss of prior data.
FR.4 Non ‗browser specific‘ web interface
FR.5 Time stamps included and displayed for each channel.
FR.6 Ability to record 64 concurrent IP streams (such as VoIP, RoIP, multimedia,
etc)
FR.7 Support is required for three separate networks. There shall be no packet
forwarding, bridging or other communications between the three networks.
FR.8 Remote alarm capability with messages sent to work stations.
FR.9 Remote alarm notification and management SNMP support
FR.10 SQL database with support for external queries.
FR.11 Timestamps recorded on all channels
FR.12 SNMP server support - alarm (via traps), normal operation (via polling),
FR.13 Cold standby MLR – as an option, price separately. Describe configuration and
requirements for maintenance and operation.
FR.14 Support for migration of up to 64 analog audio channels to IP channels as RoIP
(Radio over IP) evolves and replaces legacy radio equipment.
FR.15 Optional support for workstations operating in a Virtual Machine environment.
FR.16 Offerors should be capable of providing 24 x 7 support
FR.17 All equipment and software shall have at least a one year parts and labor
warranty from date of acceptance. Vendor shall include a quotation for an
extended warranty and/or maintenance contract.
FR.18 Minimum system usable service life expectancy of 10 years, with parts, service,
support contract available and renewable annually, for a period of ten years
from project completion.
FR.19 The Multimedia Logging Recorder must have the following access control:
a) An authentication process to verify the identity of users prior to initiating a
session or transaction;
b) An authorization process which specifically grants access to information
ensuring that access is strictly controlled, audited, and that it supports the
concepts of ―least possible privileges‖ and ―need-to-know‖; c) An audit trail
process to ensure accountability of Multimedia Logging Recorder and security-
related events;
d) A process for ensuring that the Multimedia Logging Recorder has the ability
to log and report specific security incidents and all attempted violations of
Multimedia Logging Recorder security. In addition, this capability must be
enabled at all times;
e) The processes to establish, manage, and document user id and password
administration;
f) A segregation of the functions of Multimedia Logging Recorder administration
and security administration to provide separation of duties;
Page 4
Multi Media Logging Recorder Attachment K - Functional and Technical Requirements
Functional Requirements To Be Completed by Offeror
Modification
(Estimate the
Add-On Planned Level of Effort by
or 3rd Party Capability hours in the Not
Req.# Description Standard Feature Configuration Product and Timeframe Comments) Met Comments
FR.20 The Multimedia Logging Recorder must provide an audit trail. The following
minimum set of events/actions must be logged and kept as required by State
and Federal laws/regulations:
a) Additions, changes or deletions to data produced by IT;
b) Identification and authentication processes;
c) Actions performed by operators, managers, engineers, technical support,
data security officers, and administrators;
d) Emergency actions performed by support personnel and highly privileged
Multimedia Logging Recorder and security resources.
The audit trails must include at least the following information:
a) Date and time of event;
b) User id of person performing the action;
c) Asset or resource name and type of access;
d) Success or failure of event;
e) Source (terminal, port, location, IP address) where technically feasible.
FR.21 Ability to record operators workstation screen captures to be stored and
transmitted to the server in a compressed format. Screen capture triggers must
be configurable based on time, keystroke activity, radio activity, telephone
activity, contact closure, or a combination of activities.
FR.22 Screen captures shall be transmitted to server without adversely affecting PC or
network performance.
FR.23 Analytic support for incident investigation, archiving, etc.
FR.24 Support for Management/Supervisor playback services
FR.25 Secure login with per channel access level privileges
FR.26 Player client supports a minimum of 16 different recordings simultaneously
along with recorded desktop displays
FR.27 Operator position screen capture/playback support
FR.28 Ability to archive channels to removable media (i.e. DVD or CD) based upon
access level privileges. Time stamps must be included on each channel
archived.
FR.29 Remote management via web interface. Various access/management
permissions configurable on a per user basis, unlimited in numbers.
FR.30 Remote monitoring of live-in progress calls
FR.31 Multi-channel playback, with channel specific security level controls
FR.32 Provide for tagging notations/comments onto any channel or activity
FR.33 Optional support for workstations operating in a Virtual Machine environment.
FR.34 Provide instant replay of audio on each workstation.
FR.35 Provide instant and delayed playback of recorded data/voice. Ability to slow
down playback to help resolve intelligibility issues
FR.36 Provide for book-marking of recoded data/voice
FR.37 Provisions for voice recording by telephone lines and capable of selective
recording such that only designated telephone lines are recorded. On all
recorded lines the system shall generate warning tone beep tones. Whenever
warning tone beeps are generated it shall be possible to filter the beep tone
such that beeps do not interfere with the speech being heard by the operator
and such that the far telephone party hears the tones.
FR.38
FR.39 Page 5
FR.40 Multi Media Logging Recorder Attachment K - Functional and Technical Requirements
Technical Requirements To Be Completed by Offeror
Modification
(Estimate the
Add-On Planned Level of Effort by
or 3rd Party Capability hours in the Not
Req.# Description Standard Feature Configuration Product and Timeframe Comments) Met Comments
TR.1 Minimum 64 analog audio channels (sources include 2 and 4 wire telephone,
two way radio, T-1 audio channels)
TR.2 Minimum 64 VoIP channels w/ Cisco Call Manager 7 integration
TR.3 Minimum 64 targeted IP channels
TR.4 Migration path from analog channels to IP recording (RoIP etc)
TR.5 The equipment should be able to accept nominal audio input levels of +5 to -20
dBmW.
TR.6 Audio recording triggered on VOX, voltage level, tone, off hook, or contact
closure.
TR.7 Audio compression/storage support for VoIP Codecs GSM, G.711, G.729
TR.8 Integration with Cisco Call Manager 7 or higher. Provide configurations, router
and switch prerequisites, and configurations necessary to record SIP VoIP
calls.
TR.9 NTP time support
TR.10 Optional integration with Asterisk PBX. Provide configurations, router and
switch prerequisites, and configurations necessary to record SIP VoIP calls.
TR.11 Archiving ability to Dual DVD-RW and external storage devices. Archives shall
be password protected.
TR.12 Hardware based RAID 5 (3 drive minimum) with Hot Swappable, drives with
minimum 30 day storage capability.
TR.13 Dual Hot Swap power supplies 100-250 VAC, and /or optional negative 48 VDC
supply
TR.14 Network support for two Gigabit Ethernet interfaces. There shall be no packet
forwarding, bridging or other communications between network interfaces.
TR.15 Server and interface equipment to be rack mounted in a server cabinet supplied
by vendor. Explain or attach drawings as necessary.
Multi Media Logging Recorder RFP Attachment K - Functional and Technical Requirements Page 3
Technical Requirements To Be Completed by Offeror
Modification
(Estimate the
Add-On Planned Level of Effort by
or 3rd Party Capability hours in the Not
Req.# Description Standard Feature Configuration Product and Timeframe Comments) Met Comments
TR.16 System Issues shall be classified as follows:
a) CRITICAL (Priority 1) — The problem results in extremely serious
interruptions to MIEMSS operations. Tasks that should be executed
immediately cannot be executed because of a complete crash of the system or
interruptions in main functions of the production system. Data integrity is
compromised and the service request requires immediate processing. Security
related issues that can compromise the access to or functions of the System or
its data.
b) URGENT (Priority 2) — The problem results in serious interruptions to
normal operations or will negatively impact MIEMSS operations. Important
tasks cannot be performed, but the error does not impair essential operations,
processing can still continue in a restricted manner, and data integrity may be
at risk. The service request requires timely processing, because the malfunction
could cause serious interruptions to critical processes or negatively impact
operational decisions.
c) IMPORTANT (Priority 3) — The problem causes interruptions in normal
operations. It does not prevent operation of a system, or there could be minor
degradation in performance. The error is attributed to malfunctioning or
incorrect behavior of the System.
d) MINOR (Priority 4) — The problem results in minimal or no interruptions to
normal operations (no operational impact). The issue consists of ―how to‖
questions, installation and configuration inquiries, enhancement requests, or
documentation questions. If Selected Offeror‘s Maintenance and Support
estimates that a reported technical issue or business situation requires
additional attention, an internal management escalation procedure will be
followed. A management escalation process may be enacted when response-
time targets are, or will be, exceeded or when you are dissatisfied with the
solution provided.
TR.17 For System maintenance the Contractor will provide on-call support twenty-four
hours a day, seven days a week for the System based on the priority levels set
forth above as follows:
a) Priority 3 and 4 classifications – one (1) business day.
b) Priority 1 and 2 classifications – one (1) hour.
TR.18
TR.19
TR.20
TR.21
TR.22
Multi Media Logging Recorder RFP Attachment K - Functional and Technical Requirements Page 3
REPORTS To Be Completed by Offeror
Report Report Name Report Description Delivered out of Modification to an Custom Not Comments
Number the Box existing report Met If Delivered, provide Report Name and
Number
Report 1 Offerors shall list any standard
reports available with the System.
Report 2 Offerors shall list any ad-hoc or user
generated report capability available
with the System.
Multi Media Logging Recorder Attachment K - Functional and Technical Requirements Page 4
To Be Completed by Offeror
Req.# Module Description
Modification
Independent (Estimate the Level
Delivered out of Module or Third Planned Capability of Effort by hours Not
the Box Configuration Party and Timeframe in the Comments) Met Comments
OM.1 Offerors shall list any optional modules, products or services available.
Multi Media Logging Recorder Attachment K - Functional and Technical Requirements Page 5