Cameras Integrated with Specialized Software Make Amusement Park Safer

July 3, 2015

For those having the time of their life frolicking fancy-free at Knoebels Amusement Resort, security is likely the last thing on their minds. And that’s exactly how it should be for patrons of America’s largest free admission amusement park, which is nestled in an idyllic wooded setting within Elysburg, Pa. To see it stays that way, behind the scenes Knoebels management enlisted Vector Security to deploy a parkwide integrated video and access management system that ensures safety and enhances customer service. The project allowed Vector Security to bag an SSI Integrated Installation of the Year Award.

In operation since 1926, Knoebels Amusement Resort is one of the nation’s most unique and exciting facilities of its kind. Besides featuring a 900,000-gallon crystal pool filled with refreshing mountain stream water, two overnight campgrounds accommodating cabins and more than 800 campsites, Knoebels contains 60+ rides, award-winning food, games and gift shops. In addition, visitors can hit the links at Knoebels Three Ponds Golf Club located adjacently to the park.

Addressing improved efficiencies as they relate to public liability, loss prevention and safety issues were the objectives that drove Vector Security’s system design. It included video management software (VMS), VMS server, IP megapixel cameras with IR and 360⁰ functionality, encoders, access control software, card readers, electronic locks and custom-developed integration software.

Discover the advantages of choosing a wireless access control system.

Integrator Queues Up

Knoebels was looking for an integrator that could support its growing needs and meet budgetary requirements. The choice of vendor was predicated on the ability to consult, design, install and service the system now and into the future. In late 2013, Knoebels began discussions with Vector Security to review its current system, develop a more comprehensive plan for upgrading current infrastructure and set objectives for further system integration.

The result of hours of discussion and planning between the Knoebels team and Vector Security resulted in commencement of the project in early 2014. The job would entail consultation and coordination with all manufacturers and custom software developers, as well as Knoebels’ park safety, IT, loss prevention, maintenance, engineering and staff electrician personnel.

“We work with these groups from design through implementation of the systems for input on design requirements to installation infrastructure requirements,” says Vector Security Integrated System Coordinator Gary Shipierski. “This includes IT WAN support, POS interface support and engineering’s support on system integration with the park’s ride control systems.”

In addition to Shipierski, key Vector Security personnel involved in the planning, design and installation included Sales Representative Scott Christian, and Installation Technicians Brian Peet and Joseph Tweedle. According to Shipierski, the project, which would total out at more than 400 labor hours, was a very collaborative process.

“The customer had an idea of the system and end result of the systems design, but didn’t have specific products selected to accomplish their final objective,” he says. “They knew how the system should look and operate, but looked to Vector Security to provide the solution. The manufacturers were also very important in providing support in both the design and installation phases of the project.”

An Amusing Environment

Though Vector Security is well versed in integrated solutions for a wide swath of vertical market clients and monitors 275,000 customers, the Knoebels amusement park venue was a unique undertaking.

“A challenge of the project was utilizing products primarily designed for use in the security industry, making modification of their use to not only work for security but also to be used in the amusement park industry for more than just security. The system is used for security, but used more for liability and safety purposes,” says Shipierski.

Working through the winter and early spring months to meet a late April deadline also presented challenges. And the solution had to adhere to the customer’s site and ride safety plans.

“There were several difficult aspects associated with this project. A large portion of the work was outdoors and it all had to be completed in a short period from when the project was awarded to when the park opened for business for the season,” says Shipierski. “We had to work with manufacturers and suppliers to ensure longer lead times so equipment would be available to meet the timeline. And we had to work with the customer and custom software developer to ensure software met expectations.”

Shipierski credits hard work by the project team on tasks ranging from placement of equipment orders to the implementations of the systems by the technicians as being critical to overcoming the job’s challenges.


IMPORTANT! This model requires non-standard firmware. Do Not Install standard firmware (e.g. v.4.1.xx) on this model. Doing so will permanently damage your system. You must use custom firmware v.4.1.25 from the iDS-9632NXI-I8/16S product page.

View the most updated version of this document here:


The I-series NVR (such as the DS-7716NI-I4) is one of Hikvision's most popular and feature-rich recorders. As such, many firmware revisions have been introduced over the years to continually ensure the product is compatible with the newest technology available. Due to the many revisions, we recommend that the user closely follows the instructions below in order to reduce the amount of time spent as well as the chance of failure.


Database Optimization and Repair

As more affordable IP cameras are introduced over time with greater video resolution and data sizes, more efficient database management also becomes necessary. The introduction of firmware v4.0 brought about a new database architecture in order to be futureproof.


After upgrading to v4.X, the recorder database will need to be converted and optimized. If you are experiencing issues where playback is expected but not found, make sure "Database Repair" is performed as indicated in the procedures and scenarios below.


Preparing the Upgrade

Before proceeding with upgrade, it is recommended that NVR configuration file is exported from the NVR over the network or on to a local USB drive.


Upgrading from v3.4.92 build 170518 or Older

  1. All recorders must reach v3.4.92 before proceeding further. Upgrading from versions before v3.4.92 directly to any version of v4.X will likely cause the recorder to fail.
  2. If the recorder is already at v3.4.92, a full factory default is highly recommended before upgrading to any version of v4.X. There is a high chance of unit failure (requiring RMA) if the unit is not defaulted before upgrade.
  3. After reaching v3.4.92 and performing a full factory default, an upgrade directly to v4.50.00 is acceptable.
  4. After the upgrade is completed and the recorder is reprogrammed, it may be beneficial to perform a Database Repair. For details, refer to the section "Database Optimization and Repair" above.
  5. To verify repair progress, you may refer to the HDD status, or search the recorder log for repair started and stopped entries. Note that while the HDD is repairing, new recordings are still being made, but some existing recordings may not be searchable until repair is complete.
  6. If you continue to observe playback issues after database repair, ensure there are no power, network, or motion detection issues. Should the problem persist, contact technical support.


Upgrading from Any v4.X Build to v4.50.00.

  1. Any v4.X build can be upgraded directly to v4.50.00.
  2. Export configuration is highly recommended before performing the upgrade.
  3. If upgrading from any v4.X version that was not v4.22.005, a Database Repair is recommended. Refer to Step 4 and onwards in the previous section.



Downgrading is not recommended. Due to new features and parameters constantly being added, downgrading may cause the NVR to factory default itself or require a manual default to operate properly.

View the most updated version of this document here:
K-Series DVR upgrade instruction
The Turbo 4 Hybrid DVR K series has multiple models and across different platform and chipset. It also has similar firmware development of other recording product line; DVR K series has also introduced the GUI4.0 to ensure the series to be compatible to the newest technology available. The new database architecture is also brought into the DVR firmware v4.0 to be future proof and for better recording search experience. 

Database Optimization and Repair

As more affordable cameras introduced over time with greater video resolution and data sizes, more efficient database management also becomes necessary. The introduction of firmware v4.0 brought about a new database architecture in order to be futureproof.
After upgrading to v4.X, the recorder database will need to be converted and optimize. If you are experiencing issues, where playback is expected but not found, please make sure to perform "Database Rebuild" as indicated in the procedures and scenarios below.

Preparing the Upgrade

Before proceeding with upgrade, it is recommend exporting DVR configuration file from the DVR over the network or on to a local USB drive.


Action after firmware upgraded 

1. Upgrade the DVR according to the chart above. 

2. Reconfirming Channel's Recording Schedule 

    - Confirm channel's recording schedule is enable. 

    - Check if the channel is on correct recording schedule.

3. Double Check Storage Setting

    - Make sure all channel are assigned to record on its HDD group when the Storage setting is under Group Mode. 

4. Perform Database Rebuild locally. 

    • Some version above support Database Rebuild via web access - K51 and K72

    • Perform Database Rebuild regardless if system is having any database issue symptom. 

    • Database Rebuild process is average ~30 to 60min per TB. The process may still varies depends recording data.

    • After Database Rebuild - Check log to confirm Database Rebuild has went thru properly. 

    • If Database Rebuild Started and Stopped log has been log only within few minutes. Database rebuild may not has been completed properly. It is strongly recommend performing the Database Rebuild again.

    • To check log > System > Log > Information > Database Rebuild Started and Stopped.

    • If the log option is not available - access system via SSH can also obtain similar result.

5. Recording Data is still missing after database rebuild process. 

If the data has not been recorded or has been overwritten, Database rebuild process is not able retrieve those lost data. Have the system upgraded to the latest available firmware version above to prevent any future data lost is strongly recommended for all application.





By downloading and using software and other materials available via this website, you agree to be legally bound by HIKVISION General Terms of Use . If you don’t agree to these terms, you may not download or use any of those materials.

If you are agreeing on behalf of your company, you represent and warrant that you have legal authority to bind your company to the General Terms of Use above. Also you represent and warrant that you are of the legal age of majority in the jurisdiction in which you reside (at least 18 years of age in many countries).