Docstoc

functional Requirements

Document Sample
functional Requirements Powered By Docstoc
					                                   Key
       1     Compliant
       2     Non-Compliant
       3     Non-Applicable for Solution
    Business Business Requirement
     Req. #
            Description
                                                                Mandatory Requirements
    BR-1    The Solution must provide a measurement or
            estimate of the time it takes for a vehicle to
            travel from the end of the queue to arrival at
            the primary inspection booth.


1
     BR-2   The Solution must be a bi-national system
            providing wait times for both Northbound (into
            Canada) and Southbound (into the U.S.) traffic.
2
     BR-3   The Solution must have the necessary security
            protections: physical security, network,
            application, data, data encryption, and
3           operating system security.
     BR-4   The Solution must be configured such that the
            failure shall not affect enforcement procedures
            or other devices at the POE.

    BR-5    The Solution must be able to operate in severe
            weather conditions (snow, ice, wind, rain, etc.)




     BR-6   The Solution components must be adequately
            secured to prevent theft or misuse. The four
            agencies will not be responsible for equipment
            damage or theft. Existing integrated
            components, if any, will be the responsibility of
            the respective agencies.



     BR-7   The Solution must collect and store border wait
            time data within a single, central repository.
 BR-8   The Solution must provide status of network
        connectivity.

 BR-9   The Solution must provide the capability to
        control access to the collected data based on
        user type and individual user identity (e.g.
        report access to all or individual elements could
        be restricted to specified government users.

                                                            Other Considerations – Facilities
BR-10   Vendors should demonstrate how the Solution
        can be adapted to the unique operational
        environment (i.e., network infrastructure,
        physical environment, and vehicle traffic
        patterns, reduced line-of-sight, bridges,
        signalized intersections on the approach road,
        multiple approaches to the crossing, etc.) of all
        land border POEs.



BR-11   The Solution infrastructure, size, and
        appearance must be[1] architecturally and
        aesthetically comparable to the existing POE
        facility.



BR-12   The Solution should minimize the disruption to
        traffic during installation and maintenance, and
        minimize the time required for installation.




                                                              Other Considerations – Usability
BR-13   The Solution should provide a predictive
        estimate of the time it will take for the next
        vehicle arriving at the end of the queue to reach
        the primary inspection booth.

BR-14   The Solution should provide actual measures of
        the time it took a vehicle to travel from the end
        of the queue to the primary inspection booth,
        including date and time stamps of when it
        entered the queue and when it arrived at the
        primary inspection booth.
BR-15   The Solution should be able to predict wait
        times one hour into the future, as well as
        predict hour-by-hour wait times for the
        following day.



BR-16   The Solution shall[2] provide 100%
        automation for the measurement of wait
        times, eliminating the need for human
        intervention.

BR-17   The solution should include options for
        monitoring and measuring the wait times for
        passenger vehicles and commercial vehicles in
        real time.




BR-18   The Solution should include the capability to
        provide separate measures for vehicles going
        through expedited primary inspection booths,
        where they exist (e.g. FAST and NEXUS/SENTRI
        programs, empty trailers, etc.)

BR-19   The Solution should support existing wait
        time measurement feeds from measurement
        devices currently deployed at the POE.[3]

BR-20   The Solution model should be able to tie
        measurements to dissemination solution: BWT
        website, U.S. Department of Transportation
        Traffic Management Centers, variable message
        signs, I-95 Coalition website, 511, radio, etc.


BR-21   The solution should provide capability for
        automatic alert messages when wait times for a
        given crossing pass specific thresholds.
BR-22   The Solution should minimize the cost, both
        deployment costs (equipment, design,
        installation, software development) and ongoing
        costs (maintenance, power and
        communications, servicing, purchase of data).




BR-23   The Solution should minimize CBP and CBSA
        involvement in the installation, operation,
        maintenance, or support of data collection,
        analysis and integration.




BR-24   The Solution should be scalable. Vendors will
        need to demonstrate how the system is able to
        operate cost effectively at high and low volume
        crossings.




                                                             Other Considerations – Reporting
BR-25   The following is a list of system data elements of
        interest to the user, and could be reported
        alone or in any combination, sorted by specific
        times (date or range of dates, date/time or
        range of dates/times, or day of the week)
        and/or location and device collection type:
              Queue entry date and time
        ·      Queue exit date and time
        ·      Total time vehicle in queue
        ·      Queue entry location (distance from
        primary booth)
        ·      Number of lanes open (POV, commercial,
        NEXUS POV, FAST commercial)
        ·      Total number of lanes
        ·      Vehicle count (POV, commercial, NEXUS
        POV, FAST commercial) for each lane by hour
        ·      Total vehicle count (POV, commercial,
        NEXUS POV, FAST commercial) for each hour (all
        lanes)
        ·      Average wait time (POV, commercial,
        NEXUS, POV, FAST commercial) for each hour
        (all lanes)
        · License Plate Reader Image alerts via text
        mail/text messages (CBP)
BR-26   Internal user report data should be readily
        downloadable to standard software applications
        (e.g., Microsoft Excel.)




BR-27   The solution should have the capability for
        graphic reporting (e.g., line charts) of wait time
        data for internal users.



BR-28   The Solution should minimize the time from
        measurement to reporting.
BR-29   The Solution should report wait time measure in
        real time for data feeds.




BR-30   Publicly available reporting should provide the
        following data:

        ·    Time of wait time measurement
        ·    Port/crossing name
        ·    Port/crossing hours of operation
        ·    Maximum lanes
        ·    Number of lanes open
        ·    Commercial vehicle wait time
        ·    FAST vehicle wait time
        ·    Passenger vehicle wait time
        ·    NEXUS vehicle wait time

                                                          Other Considerations – Security
BR-31   The Solution should minimize the use of
        Personally Identifiable Information (PII)




BR-32   The Solution should not require the ability to
        capture and incorporate primary booth
        processing times. If the Solution captures
        primary processing times, these measures shall
        be immediately purged prior to calculating wait
        times.
Proposed Functional Requirements                                       Test Data Needs

                                Mandatory Requirements
System shall provide accurate information regarding time           System defined wait time
elapsed from arrival at end of queue to time arrived at
customs primary inspection. Accuracy is defined as system-
delivered wait time within +/- 10 % of actual ground truth
measurement, or 5 minutes, whichever is greater. Accuracy         Ground Truth Wait Time
must be demonstrated independent of time of day or day of         Time of System Measurement
week.
Business requirement does not relate specifically to the              See other data needs
function of the system; however, the system must meet all
functional requirements specified herein regardless of
direction of travel.
Business requirement does not relate specifically to the            Documentation and visible
function of the system; however, the system must                   evidence of existence of data
demonstrate evidence of compliance with accepted practices         encryption and system operating
for information and system security.                               security provisions
System failures shall not result in adverse effects on              Documentation of
enforcement procedures or operation of other                       interference events
systems/devices at crossing.

The system shall not suffer any degradation in performance          System defined wait time
due to adverse weather conditions, including heavy rain,           · Ground truth wait time
freezing rain, snow, icing, high winds, dust, or smoke.            · Time of system measurement
                                                                   · Log of system operation
                                                                   · Prevailing weather conditions
                                                                   at time of system measurement



Business requirement does not relate specifically to the            Documentation of
function of the system; however, note will be made of              component installation
installation methods.                                              configuration and security
                                                                   provisions




The system shall store all captured and calculated data for the     Documentation of system
duration of the test period and provide the data to the BWT        storage
Project Team in an electronic format
System shall have the ability to monitor its own operation, log      Documentation of downtime
all downtime, and alert test team when unavailable for use          events

The system shall demonstrate evidence of compliance with             Documentation of access
access control through username and password                        control features
administration, and shall provide multiple access levels (e.g.,
system administrator, system operator, system data user).


                             Other Considerations – Facilities
Business requirement does not relate specifically to the             Documentation of
function of the system; however, System shall not possess any       component installation
characteristics that prevent it from being deployed at locations    configuration
other than the test site. System should also include design
elements that allow it to accommodate crossing and approach
configurations different from those at the test site.




Business requirement does not relate specifically to the             Documentation of
function of the system; however, note will be made of               component installation
installation methods.                                               configuration visual appearance




Business requirement does not relate specifically to the             Documentation of
function of the system; however, note will be made of               component installation method
installation methods and time required.                             and timeline




                                 Other Considerations – Usability
The system should provide predictive information regarding
time elapsed from arrival at end of queue to time arrived at
customs primary inspection. Predicted wait time must be
applicable to the next vehicle that arrives at the end of queue

The system should provide accurate information regarding
time elapsed from arrival at end of queue to time arrived at
customs primary inspection. Accuracy is defined as system-
delivered wait time within +/- 10 % of actual ground truth
measurement, or 5 minutes, whichever is greater. Accuracy
must be demonstrated independent of time of day or day of
week.
The system should provide predictive information regarding
time elapsed from arrival at end of queue to time arrived at
customs primary inspection. Predictive wait time must be
applicable to times 60 minutes from the current time a vehicle
arrived at the end of queue, and by hour for the next day


System shall not require any manual data collection or data
manipulation to calculate wait time



The system should provide timely information regarding time
elapsed from arrival at end of queue to time arrived at
customs primary inspection. Timeliness is defined as system-
delivered historical wait time received from system within 2
minutes of any individual vehicle reaching the end of the
measurement zone, and current wait time within 5 minutes of
any individual vehicle reaching the start of the measurement
zone (i.e., end of queue). The system should also be able to
determine wait time values for automobiles and trucks
separately
The system should be able to discern real-time and predictive
wait time for different lanes (i.e., standard, NEXUS, FAST). It is
also desirable that the system is able to identify the number of
lanes of each type that is open at any particular point in time.



The system should demonstrate the capability to receive data
from existing wait time measurement systems already in place
at the crossing and integrate the data into its wait time
reporting (where those systems exist)
The system should provide wait time data with a location, time
and date stamp in XML format in compliance with traffic
detector data message structure and data elements from the
ITE Data Dictionary and the ITE Message Set.




The system should provide the capability to issue alerts when
travel times exceed predetermined thresholds for current and
predicted wait times
Business requirement does not relate specifically to the
function of the system; however, note will be made of
installation, operations, and potential maintenance
requirements.




System shall not require any manual data collection or
data manipulation to calculate wait time.[4] Remainder of
BR does not relate specifically to the function of the
system; however, note will be made of installation,
operations, and potential maintenance requirements.




Business requirement does not relate specifically to the
function of the system; however, System should not possess
any characteristics that prevent it from being deployed at
locations with different traffic volumes than that of the test
site. System should also include design elements that allow it
to accommodate crossing and approach configurations
different from those at the test site.




                           Other Considerations – Reporting
The system should possess the ability to generate pre-defined
and ad hoc reports that include the following data elements:
   Queue entry date and time
·    Queue exit date and time
·    Total time vehicle in queue
·    Queue entry location (distance from primary booth)
·    Number of lanes open (POV, commercial, NEXUS POV,
FAST commercial)
·    Total number of lanes
·    Vehicle count (POV, commercial, NEXUS POV, FAST
commercial) for each lane by hour
·    Total vehicle count (POV, commercial, NEXUS POV, FAST
commercial) for each hour (all lanes)
·    Average wait time (POV, commercial, NEXUS, POV, FAST
commercial) for each hour (all lanes)
· License Plate Reader Image alerts via text mail/text
messages (CBP)




The system should provide wait time data with a location, time
and date stamp in the following formats:
·    Comma-separated values (.csv)
·    Space-delimited values
·    Microsoft Excel files (xls, xlsx)

The system should possess the ability to generate pre-defined
and ad hoc reports that illustrate travel time under varying
conditions, indexed by user-defined parameters (e.g., time of
day, day of week, lane type, vehicle type, etc.)

The system should provide timely information regarding time
elapsed from arrival at end of queue to time arrived at
customs primary inspection. Timeliness is defined as system-
delivered historical wait time received from system within 2
minutes of any individual vehicle reaching the end of the
measurement zone, and current wait time within 5 minutes of
any individual vehicle reaching the start of the measurement
zone (i.e., end of queue). System shall output current and
predictive wait time values at a minimum frequency of 5
minutes
The system should provide timely information regarding time
elapsed from arrival at end of queue to time arrived at
customs primary inspection. Timeliness is defined as system-
delivered historical wait time received from system within 2
minutes of any individual vehicle reaching the end of the
measurement zone, and current wait time within 5 minutes of
any individual vehicle reaching the start of the measurement
zone (i.e., end of queue). System shall output current and
predictive wait time values at a minimum frequency of 5
minutes

The system should possess the ability to generate pre-defined
publicly available reports that include the following data
elements:
·     Time of wait time measurement
·     Port/crossing name
·     Port/crossing hours of operation
·     Maximum lanes
·     Number of lanes open
·     Commercial vehicle wait time
·     FAST vehicle wait time
·     Passenger vehicle wait time
·     NEXUS vehicle wait time

                            Other Considerations – Security
The system should be designed to the extent possible to rely
upon the capture and use of publicly available vehicle
information, and/or the use of techniques that do not require
the unique identification of vehicles, vehicle owners or
occupants



Business requirement does not relate specifically to the
function of the system; however, System should not possess
any characteristics or calculations that require it to use
primary booth processing times to calculate wait time.
Test Method Overview


Use manual method (TBD) to capture actual wait times
over a full day, several times during the 30-day test
period. Compare system-provided wait time data to
manually collected data.



See other test methods



Review of system technical documentation and vendor
demonstration of compliance with requirement
provisions.

Observation of existing systems, and interviews with
existing enforcement personnel and system
owners/operators to verify that no adverse effects
occurred
Test is not scheduled to be executed during winter
months, but note will be taken of function during any
severe weather events that occur during the 30-day test
period, and system data will be reviewed for
inaccuracies and anomalies.




Observation of system/component installation and
interviews with agency staff responsible for physical
security at mounting locations. Due to the temporary
nature of this test project, it is anticipated that some
vendor products and/or solutions may be installed in a
temporary configuration. To the extent feasible, the
test team will review engineering plans and assess
potential compliance with physical security
requirements.
Review of received wait time data and comparison of
received data to data stored in wait time measurement
system database
Observation of system operation, review of system logs,
and interviews with users to document downtime

Review of system technical documentation and vendor
demonstration of compliance with requirement
provisions.




Examination of system installation and operational
requirements with members of stakeholder body to
determine if any element is incompatible with any
known potential installation locations. Due to the
temporary nature of this test project, it is anticipated
that some vendor products and/or solutions may be
installed in a temporary configuration, and in only one
location. To the extent feasible, the test team will
review engineering plans and assess potential
compliance with adaptability requirements.
Observation of system/component installation. Due to
the temporary nature of this test project, it is
anticipated that some vendor products and/or solutions
may be installed in a temporary configuration. To the
extent feasible, the test team will review engineering
plans and assess potential compliance with appearance
requirements.
Observation of system/component installation. Due to
the temporary nature of this test project, it is
anticipated that some vendor products and/or solutions
may be installed in a temporary configuration. To the
extent feasible, the test team will review engineering
plans and assess potential compliance with
requirements related to disruption of operations.


Use manual method (TBD) to capture actual wait times
over a full day, several (TBD) times during the 30-day
test period. Compare system-provided predicted wait
time data to manually collected data for period
predicted.
Use manual method (TBD) to capture actual wait times
over a full day, several times during the 30-day test
period. Compare system-provided wait time data to
manually collected data.
Use manual method (TBD) to capture actual wait times
over a full day, several times during the 30-day test
period. Compare system-provided predictive wait time
data to manually collected data for period predicted.



Review of data provided by wait time measurement
system and verification that all data forwarded by
system was provided through automated means.


Use of manual method (TBD) to capture actual vehicle
positions over a full day, several (TBD) times during the
30-day test period. Compare system-provided time
stamp data to manually collected data.




Use manual method (TBD) to capture actual vehicle
positions and lane availability over a full day, several
(TBD) times during the 30-day test period. Compare
system-provided time stamp data to manually collected
data.

TBD



Verification of receipt of data from system in format
required




Review wait time data and threshold alert records to
determine whether alerts were issued, and when.
Observation and analysis of system/component
installation and use. Due to the temporary nature of
this test project, it is anticipated that some vendor
products and/or solutions may be installed in a
temporary configuration. To the extent feasible, the
test team will review engineering plans and assess
potential compliance with requirements related to
implementation and use costs.

Observation and analysis of system/component
installation and use. Due to the temporary nature of
this test project, it is anticipated that some vendor
products and/or solutions may be installed in a
temporary configuration. To the extent feasible, the
test team will review engineering plans and assess
potential compliance with requirements related to
implementation and use requirements.

Examination of system installation and operational
requirements with members of stakeholder body to
determine if any element is incompatible with any
known potential installation locations. Due to the
temporary nature of this test project, it is anticipated
that some vendor products and/or solutions may be
installed in a temporary configuration, and in only one
location. To the extent feasible, the test team will
review engineering plans and assess potential
compliance with adaptability requirements.




Creation and review of system-generated reports by
test team for determination of compliance with
reporting requirements
Verification of receipt of data from system in format
required




Creation and review of system-generated reports by
test team for determination of compliance with
reporting requirements



Use manual method (TBD) to capture actual vehicle
positions over a full day, several (TBD) times during the
30-day test period. Compare system-provided time
stamp data to manually collected data.
Use manual method (TBD) to capture actual vehicle
positions over a full day, several (TBD) times during the
30-day test period. Compare system-provided time
stamp data to manually collected data.




Not Applicable[5]




Review of data provided by wait time measurement
system and assessment of content of data forwarded
for PII minimization.




Examination of system operational requirements with
members of stakeholder body to determine if any
element requires the use of booth processing times. To
the extent feasible, the test team will review system
design documentation and assess compliance with
requirements.
                      Non-             N/A to
          Compliant Compliant         Solution
                Mandatory Requirements
BR - 1
BR - 2
BR - 3
BR - 4
BR - 5
BR - 6
BR - 7
BR - 8
BR - 9
             Other Considerations – Facilities
BR - 10
BR - 11
BR - 12
            Other Considerations – Usability
BR - 13
BR - 14
BR - 15
BR - 16
BR - 17
BR - 18
BR - 19
BR - 20
BR - 21
BR - 22
BR - 23
BR - 24
            Other Considerations – Reporting
BR - 25
BR - 26
BR - 27
BR - 28
BR - 29
BR - 30
             Other Considerations – Security
BR - 31
BR - 32

				
DOCUMENT INFO