security camera equipment & installation...

REQUEST FOR PROPOSALS Solicitation No: RFP 2017-15

For the Provision of

Security Camera Equipment & Installation Services

McMinnville School District No. 40 McMinnville, Oregon

Issued: July 14, 2017 Proposals Due: August 8, 2017 at 2:00 PM, PST

Single Point of Contact (SPC): Susan Escure, Finance Director Label for Proposal: RFP #2017-15 – Security Cameras Address: 800 NE Lafayette Ave, McMinnville OR, 97128 Email: [email protected] Phone: 503-565-4005 Fax: 503-565-4030

RFP 2017-15 SECURITY CAMERAS of 32

mailto:[email protected]

REQUEST FOR PROPOSAL

TABLE OF CONTENTS

Section 1 General Information Section 2 Authority, Overview and Scope Section 3 Procurement Requirements and Evaluation Section 4 Award and Negotiations Section 5 Additional Information Section 6 List of Attachments


SECTION 1 GENERAL INFORMATION

1.01 ANNOUNCEMENT

July 14, 2017

MCMINNVILLE SCHOOL DISTRICT No. 40

REQUEST FOR PROPOSALS Security Camera Equipment & Installation Services

Solicitation No: RFP 2017-15

The purpose of this Request for Proposals (Solicitation) is to obtain competitive Offers from qualified Firms (Proposers) interested in the provision of Security Cameras on a requirements basis. This project is subject to prevailing wage rates as defined in ORS 279C.800 to ORS 279C.870. The RFP packet is available by contacting Susan Escure, Finance Director, email [email protected], phone 503-565-4005. A mandatory pre-proposal conference will be held on July 20, 2017 at 10:00 AM PST at the McMinnville School District Admin Office, 800 NE Lafayette Ave, McMinnville, Oregon, 97128.

Proposals shall be submitted in a sealed envelope and received by the McMinnville School District at 800 NE Lafayette, McMinnville Oregon, 97128, prior to closing.

SOLICITATION DUE DATE AND TIME (CLOSING) August 8, 2017 at 2:00 PM Pacific Time

The McMinnville School District may reject any proposal not in compliance with prescribed procedures and requirements and may reject for good cause any and all proposals upon a finding of the McMinnville School District that is in the public interest to do so.



1.02 INTRODUCTION The McMinnville School District serves 6,700 students in six elementary schools, two middle schools and one high school. The District passed a bond measure in May 2016 which includes funding to improve school safety and security district-wide, including upgrading security cameras, intercoms, emergency phone systems and door Security Cameras. This solicitation is for the purpose of retaining a contractor to furnish, install, manage and coordinate all work relating to Security Camera systems as shown in the attached documents on behalf of the McMinnville School District. 1.03 SCHEDULE OF EVENTS July 14, 2017 Advertise in the Daily Journal of Commerce and News Register July 20, 2017 10:00 AM –Mandatory Pre-proposal Conference July 27, 2017 Questions/Requests for Clarification Due August 2, 2017 Issue Addenda August 8, 2017 2:00 PM Closing (Proposals Due) August 11, 2016 Issuance of Notice of Intent to Award (approximate) August 18, 2016 Award Protest Period Ends (or 7 days after award) 1.04 PROPOSAL DELIVERY All proposals may be hand-delivered or mailed with the following label or subject heading: “RFP 2017-15 Security Cameras” to the following address:

McMinnville School District No. 40 800 NE Lafayette Ave McMinnville, Oregon 97128 Attn: Susan Escure, Business Service Specialist RFP 2017-15 Security Cameras 1.05 DISTRICT SINGLE POINT OF CONTACT (SPC) There will be only one point of contact during this procurement process for questions concerning the procurement process, change, clarification, award process and any other questions that may arise. Contact Susan Escure, in writing by email [email protected], fax 503-565-4030 or regular mail delivered to: 800 NE Lafayette Ave, McMinnville, OR 97128.

End of Section 1



SECTION 2 AUTHORITY, OVERVIEW, AND SCOPE OF WORK

2.01 AUTHORITY AND METHOD This McMinnville School District is issuing this RFP under the Competitive Sealed Proposals method, pursuant to ORS 279B.060 and OAR 137-047-0260. 2.02 PROJECT OVERVIEW AND BACKGROUND The District serves approximately 6,700 students with six elementary schools, two middle schools, one high school, facility department building and a district administration office. The McMinnville School District seeks proposals for an integrated Security Camera system. Potential work is to be performed on an as needed basis at any of these sites and any future properties or interests. The District currently uses various versions of March Networks DVR/NVRs along with mostly analog cameras and a few IP cameras at most buildings. Two buildings use newer IC Realtime NVRs with IP cameras. The District is interested in transitioning to an open architecture based solution that is hardware independent. McMinnville School District is looking for a vendor to maintain and replace current Security Camera system. The District’s Facility Warehouse requires a new installation and an addition at the McMinnville High School will be completed August of 2019. Current sites with security cameras include:

Buel Elementary Duniway Middle School MSD Conference Ctr Columbus Elementary Patton Middle School District Annex Grandhaven Elementary McMinnville High School Evans St Learning Ctr Memorial Elementary Adams Campus Newby Elementary Facility Department Building Wascher Elementary District Office 2.03 SCOPE OF WORK The District is requesting proposals to supply, install, configure, and maintain an Security Camera system to provide the ability to accurately identify individuals and their actions while on district property. The surveillance system should also act as a deterrent to disruptive and illegal activities.

a. SEE ATTACHMENT D – VIDEO STANDARDS.

b. The scope of this RFP includes replacement of existing equipment as well as new construction and renovations. Vendor will need to include all equipment, labor, materials, services and training necessary to install and operate an integrated security camera solution.

c. The camera system must be easily accessed for viewing on a variety of devices and form factors including tablets. A web interface that does not require specific plug-ins to view live and recorded video is a must. The system should also be able to be viewed


over the internal wired and wireless network providing access to the system when not physically in the building. Access for district officials from a single location of all building cameras is required.

d. Integration with the access control system is also desired. When access cards are presented at doorways an image of the card holder should be captured and entered into the access control logs for identity verification.

e. Recordings from all cameras must be maintained for a minimum of 30 days at all times. Feature sets such as recording only when human related activity is detected should be utilized.

f. The District’s standard construction divisions will apply to new construction and renovation portions of the work.

g. The proposed solution shall be a best fit of quality technology components that work together to create a well-designed, comprehensive and effective security system which is able to integrate with access controls and communications systems.

h. Component equipment must be provided by manufacturers who do not limit the District’s access to a particular reseller or integrator.

i. Installation will need to follow the District’s wiring standards. Installation should not utilize existing pathways, J-hooks, cable trays, etc. where available. Core drills and conduit may be necessary in some instances and additional patch panels may be required in the IDFs at some locations.

j. Proposer will provide formal training to District technical staff on the management of devices.

k. Proposer shall provide ongoing maintenance and support including, but not limited to equipment replacement, software upgrade and system troubleshooting.

l. The successful Proposer will be required to secure and maintain appropriate insurance coverage acceptable to the District.

m. The District provides no guarantee of work. Award of a contract does not prevent the District from obtaining the services of another Contractor for any other project if the District so desires and/or is in the public interest to do so.

2.04 CONTRACT TERM It is the intent of the District to have a multiple year agreement for equipment and services. The initial term of this agreement will be 12 months, the District may renew for up to four additional one year periods. The pricing provided in your response shall remain in effect for the first 12 months of this agreement. Pricing may not be adjusted without written notice provided at least thirty (30) days in advance of the change. The notice must contain the new pricing and the reason for the change. The District reserves the right to accept the change, or to not accept the change and to cancel the agreement.


2.05 PROJECT PROCEDURE During the contract period, individual Projects will arise on an as needed basis as determined by the District IT Director, or designee.

a. Quote: Contractor shall be required to prepare and submit a written quotation for each project. The District IT Director will provide a written scope of work to the Contractor. The Contractor shall provide a written price quote to include all costs to complete the project.

b. Notice to Proceed: The District IT Director will provide the Contractor a notice to proceed by issuing a Purchase Order.

c. Scheduling of Work: Contractor shall cooperate with School Officials in performing work so that interference with the normal program will be held to a minimum.

End of Section 2


SECTION 3 PROPOSAL REQUIREMENTS AND EVALUATION

3.1 MINIMUM PROPOSER QUALIFICATIONS The District reserves the right to disqualify proposals failing to meet minimum requirements. To be considered for evaluation, Proposal must demonstrate how Proposer meets all requirements of this section:

1. Proposer shall have a minimum of five years of experience in design, installation, testing and maintenance of Security Camera systems.

2. Proposer must attend mandatory pre-proposal conference. 3. Proposer shall meet the full scope of work listed herein. The District shall not accept

proposals that offer to provide only a portion of the work. 4. Proposers must maintain a local service facility within 100 miles of McMinnville which

stocks spare devices and/or components for servicing systems. 5. Proposer must have performed successful installation and maintenance of at least

three (3) projects similar in scope and size and provide references to document these projects.

3.2 MINIMUM SUBMISSION REQUIREMENTS

A. Proposal Format

Proposer shall submit its Proposal without extensive art work, unusual printing or other materials not essential to the utility and clarity of the Proposal. Proposer shall submit an original on white 8 ½” by 11” paper, bearing the Proposer’s authorized representative’s signature, three (3) copies and an electronic copy on electronic media such as thumb drive or CD.

In addition, if Proposer believes any of its Proposal is exempt from disclosure under Oregon Public Records Law (ORS 192.410 through 192.505). Proposer shall complete and submit the Affidavit of Trade Secret and a fully redacted version of its Proposal, clearly identified as the redacted version.

Proposer shall submit its Proposal in a sealed package addressed to the Single Point of Contact with the Proposer’s name and the RFP name clearly visible on the outside of the package.

Proposer’s electronic copy of the Proposal by USB drive must be formatted using Adobe Acrobat (pdf), Microsoft Word (docx), or Microsoft Excel (xlsx).

B. Authorized Representative

The Proposer Certification Form (Attachment A) shall be signed with ink as follows or the bid will be rejected.

● In the case of an individual Proposer, by the individual Proposer.

● In the case of a partnership, the name of the partnership must be listed and the


proposal shall be signed in the name of the partnership by at least one general partner. In addition, the names of all general and limited partners must be listed.

● In the case of a corporation, the corporate name shall be subscribed by the

president or other managing officer and, under the signature of such officer, the name of the office such individual holds or the capacity in which he or she acts for the corporation.

3.3 PROCUREMENT PROCESS

A. Public Notice

Notice of the RFP has been advertised in the News Register (McMinnville, OR), the Daily Journal of Commerce.

B. Questions / Requests for Clarification

All inquiries, whether relating to the RFP process, administration, deadline or method of award, or to the intent or technical aspects of the RFP must:Be delivered to the SPC via email, mailed or hand-delivered in writing

● Reference the RFP name ● Identify Proposer’s name and contact information ● Be sent by an authorized representative ● Refer to the specific area of the RFP being questioned; and ● Be received by the due date and time for Questions/Requests for Clarification .

C. Pre-Proposal Conference (Mandatory)

A mandatory pre-proposal conference will be held at the date and time listed in the Schedule. Prospective Proposers’ participation in this conference is mandatory. The purpose of the pre-proposal conference is to:

● Provide additional description of the project; ● Explain the RFP process; and ● Answer any questions Proposers may have related to the project or the process.

Statements made at the pre-proposal conference are not binding upon the District unless such statements are confirmed by written Addendum to the RFP.

Attendance at the pre-proposal conference is mandatory. The conference will be held July 20, 2017 at 10:00 AM at the District Administrative Office located at 800 NE Lafayette Avenue, McMinnville, OR 97128.

D. Solicitation Protests

Prospective Proposer may submit a written protest of anything contained in this RFP, including but not limited to, the RFP process, Specifications, Scope of Work, and the proposed terms and conditions of the proposed Contract/Price Agreement. This is a prospective Proposer’s only opportunity to protest the provisions of the RFP, except for protests of Addenda or the terms and conditions of the proposed Contract/Price Agreement, as provided below.


Protests to Addenda: Prospective Proposer may submit a written protest of anything contained in the respective Addendum. Protests of matters not added or modified by the respective Addendum will not be considered.

Protests must:

● Be delivered to the SPC via email, facsimile, hard copy ● Reference the RFP name ● Identify prospective Proposer’s name and contact information ● Be sent by an authorized representative ● State the reason for the protest, including: the grounds that demonstrate how the

Procurement Process is contrary to law, unnecessarily restrictive, legally flawed, or improperly specifies a brand name; and evidence or documentation that supports the grounds on which the protest is based

● State the proposed changes to the RFP provisions or other relief sought ● Protests to the RFP must be received by the due date and time identified in the

Schedule ● Protests to Addenda must be received by the due date identified in the respective

Addendum

Agency will respond timely to all protests submitted by the due date and time listed in the Schedule. Protests that are not received timely or do not include the required information may not be considered.

E. Proposal Submission Options

Proposer is solely responsible for ensuring its Proposal is received by the SPC in accordance with the RFP requirements before Closing. The District is not responsible for any delays in mail or by common carriers or by transmission errors or delays or mistaken delivery. Proposal submitted by any means not authorized will be rejected.

Proposal may be submitted through the mail or via parcel carrier, and must be clearly labeled and submitted in a sealed envelope, package or box. The outside of the sealed submission must clearly identify the Proposer’s name and the RFP name. It must be sent to the attention of the SPC at the address listed on the Cover Page.

Proposal may be hand delivered, and must be clearly labeled and submitted in a sealed envelope, package or box. Proposal will be accepted, prior to Closing, during District’s normal Monday – Friday business hours of 7:00 am to 5:00 pm Pacific Time, except during District holidays and other times when the District office is closed. The outside of the sealed submission must clearly identify the Proposer’s name and the RFP name. It must be delivered to the attention of the SPC at the address listed on the Cover Page.

F. Proposal Modification or Withdrawal

Any Proposer who wishes to make modifications to a Proposal already received by Agency shall submit its modification in one of the manners listed in the Proposal Submission Options section and must denote the specific change(s) to the Proposal submission.

If a Proposer wishes to withdraw a submitted Proposal, it shall do so prior to Closing. The Proposer shall submit a written notice Signed by an authorized representative of its


intent to withdraw its Proposal in accordance with OAR 137-047-0440. The notice must include the RFP name and be submitted to the SPC.

G. Proposal Due

Proposal and all required submittal items must be received by the SPC on or before Closing. Proposal received after the Closing will not be accepted. All Proposal modifications or withdrawals must be completed prior to Closing. Proposals received after Closing are considered LATE and will NOT be accepted for evaluation. Late Proposals will be returned to the respective Proposer or destroyed.

H. Proposal Rejection

The District may reject a Proposal for any of the following reasons:

● Proposer fails to substantially comply with all prescribed RFP procedures and requirements, including but not limited to the requirement that Proposer’s authorized representative sign the Proposal in ink.

● Proposer fails to meet the responsibility requirements of ORS 279B.110. ● Proposer makes any contact regarding this RFP with other District employees or

officials other than the SPC or those the SPC authorizes. ● Proposer attempts to inappropriately influence a member of the Evaluation

Committee.

I. Opening of Proposal

There will be no public Opening of Proposals. Proposals received will not be available for inspection until after the evaluation process has been completed and the Notice of Intent to Award is issued pursuant to OAR 137-047-0630. However, the District will record and make available the identity of all Proposers after Opening.

3.4 PROPOSAL CONTENT REQUIREMENTS

A. Proposal Content

The proposal must address each of the items listed in this section and all other requirements set forth in this RFP. Proposer shall describe the Goods to be provided and the Services to be performed. A Proposal that merely offers to provide the goods or services as stated in this RFP will be considered non-Responsive to this RFP and will not be considered further. The proposal shall be organized as follows:

1. Proposal Certification Sheet (Attachment A): with signature of authorized

representative.

2. Construction Contractor’s Registration Information: Provide copy of license with Oregon CCB.

3. References: Provide five (5) professional references from current or former customers for similar projects. These contacts shall be used by the District for


reference checks. Provide company name, contact name, current telephone and email address and years of service to this customer. References must verify the quality of previous, related work. The District may check to determine if references provided support Proposer’s ability to comply with the requirements of this RFP. The District may use references to obtain additional information, break tie scores, or verify any information needed.

4. Proposer Qualifications:

Please provide a brief overview of your firm’s history and personnel. This should include but is not limited to the following information:

a. How long has your firm been in business? b. How long has your firm represented the system that will be provided? c. Describe Proposer’s responsibilities and scope of work for three (3)

customers listed in Item 2 - References, preferably organizations of similar size, school districts or other educational organizations.

d. Provide the number of K-12 education installations Proposer has installed within the last year.

5. Key Personnel: a. Name the person who will be in direct charge of work and will serve as

the Supervisor for work performed under this contract. i. Detail relevant qualifications and experience, including the length

of time in this position and relevant degrees, certifications and licenses.

b. List all other key individuals who will serve under this contract and describe the individual’s relevant qualifications.

6. Security Camera Equipment: Provide specifications for equipment and installation. Include a quick reference showing the various equipment in your response. Equipment may include but is not limited to, the following:

a. Proximity card readers b. Door Locks c. Magnetic Door Locks d. Request to Exit Controllers e. Emergency Door Releases f. Security Camera Panels and Enclosures as necessary g. Camera/Intercom entry system that can interface with District’s existing

phone system.

7. Installation: Discuss your ability to provide installation. The District transition to a new Security Camera system will occur in phases. Work may be available for a single site or for multiple sites. Describe your firm’s capacity, number of employees, certifications, how you fill staffing gaps for multiple installations, and how you will ensure consistent quality across all installations.

8. Maintenance: Describe your ability to respond to District service requests for repair and troubleshooting.


9. Warranties: All warranties by Proposer and manufacturer on both products and

labor must be specified in the proposal. The Proposer’s warranties shall commence with acceptance of/or payment for the work in full. Minimum acceptable warranty on hardware, parts, and labor is 1 years.

10. Price: Provide an itemized price list for the specified equipment, costs for

installation services and labor costs for ongoing repairs and troubleshooting services. For installation services, be sure to reflect prevailing wage rates where applicable. For repair services, do not include prevailing wage rates and specify if travel time is billed as a separate line item.

B. Public Record/Confidential or Proprietary Information

All Proposals are public record and are subject to public inspection after the District issues the Notice of the Intent to Award. If a Proposer believes that any portion of its Proposal contains any information that is a trade secret under ORS Chapter 192.501(2) or otherwise is exempt from disclosure under the Oregon Public Records Law (ORS 192.410 through 192.505), Proposer shall complete and submit an Affidavit of Trade Secrets and a fully redacted version of its Proposal.

3.5 EVALUATION PROCESS A. Responsiveness and Responsibility Determination

Proposals received prior to Closing will be reviewed for Responsiveness to all RFP requirements including compliance with Minimum Requirements section and Proposal Content Requirements section. If the Proposal is unclear, the SPC may request clarification from Proposer. However, clarifications may not be used to rehabilitate a non-Responsive Proposal. If the SPC finds the Proposal non-Responsive, the Proposal may be rejected, however, Agency may waive mistakes in accordance with OAR 137-047-0470.

At any time prior to award, Agency may reject a Proposer found to be not Responsible.

A. Evaluation Criteria Proposals meeting the requirements outlined in the Proposal Content Requirements section will be evaluated by an Evaluation Committee. Each proposal will be evaluated by criteria and priorities as defined by the District, who will choose the submission that, taken as a whole, and in the District sole opinion, is in the best interest of the organization. Proposals should address the evaluation criteria listed on the following page. The SPC will conduct the price evaluation. The score for price will be based on the percentage of the proposed total cost as compared to the lowest Proposer’s cost using the following formula: lowest price / price being scored X price points possible.

The SPC may request further clarification to assist the Evaluation Committee in gaining additional understanding of Proposals. A response to a clarification request must be to


clarify or explain portions of the already submitted Proposal and may not contain new information not included in the original Proposal. The District may determine Apparent Successful Proposer at the conclusion of their evaluation, or the District may conduct interviews if it is in the best interest of the District.

EVALUATION CRITERIA Points

30% Price 30

15% Proposer Qualifications/References 15

15% Proposer Experience with K12 Customers 15

30% Equipment 30

10% Installation & Ongoing Repair/Troubleshooting Services

10

100% TOTAL POINTS POSSIBLE 100

End of Section 3


SECTION 4 AWARD AND NEGOTIATION

4.1 AWARD NOTIFICATION PROCESS

A. Intent to Award Notice The District, if it awards a contract, shall award to the highest ranking Responsible Proposer based upon the evaluation criteria described in Section 3. The District may award less than the full scope defined in this RFP. The District will notify all Proposers in writing of intent to award a contract to the selected Proposer subject to successful negotiation of any negotiable provisions.

B. Intent to Award Protest

An affected Proposer shall have seven (7) calendar days from the date of the intent to award notice to file a written protest and specify the grounds for the protest as set forth in ORS 279B 410(1). Protests must be delivered to the SPC via email or hardcopy, reference the RFP name, identify the Proposer’s name and contact information, be signed by an authorized representative, specify the grounds for the protest and be received within seven (7) calendar days from the intent of award notice. The District will address all timely submitted protests within a reasonable time and will issue a written decision to the respective Proposer.

4.2 APPARENT SUCCESSFUL PROPOSER SUBMISSION REQUIREMENTS

A. Insurance Prior to the execution of the Contract, the apparent successful Proposer shall secure and demonstrate to Agency proof of insurance coverage meeting the requirements identified in the RFP or as otherwise negotiated.

B. Taxpayer Identification Number The apparent successful Proposer shall provide its Taxpayer Identification Number (TIN) and backup withholding status on a completed W-9 form. District will not make any payment until a properly completed W-9 form is received.

End of Section 4


SECTION 5 ADDITIONAL INFORMATION

5.1 GOVERNING LAWS AND REGULATIONS

This RFP is governed by the laws of the State of Oregon. Venue for any administrative or judicial action relating to this RFP, evaluation and award is the Circuit Court of Yamhill County for the State of Oregon.

5.2 OWNERSHIP/PERMISSION TO USE MATERIALS

All Proposals submitted in response to this RFP become the property of the District. By submitting an Proposal in response to this RFP, Proposer grants the District a non-exclusive, perpetual, irrevocable, royalty-free license for the rights to copy, distribute, display, prepare derivative works of and transmit the Proposal solely for the purpose of evaluating the Proposal, negotiating an Agreement, if awarded to Proposer, or as otherwise needed to administer the RFP process, and to fulfill obligations under Oregon Public Records Law (ORS 192.410 through 192.505). Proposals, including supporting materials, will not be returned to Proposer unless the Proposal is submitted late.

5.3 CANCELLATION OF RFP

Pursuant to ORS 279B.100, the District may reject any or all Proposals in-whole or in-part, or may cancel this RFP at any time when the rejection or cancellation is in the best interest of the District. The District is not liable to any Proposer for any loss or expense caused by or resulting from the delay, suspension, or cancellation of the RFP, award, or rejection of any Proposal.

5.4 COST OF PROPOSAL

Proposer shall pay all the costs in submitting its Proposal, including, but not limited to, the costs to prepare and submit the Proposal, costs of samples and other supporting materials, costs to participate in demonstrations, or costs associated with protests.

5.5 CONTRACT All specifications, terms and conditions contained in the Request for Proposal shall be

incorporated by reference and made a part of a contract awarded to the successful bidder. A copy of our sample contract is attached to this document.

End of Section 5


SECTION 6 LIST OF ATTACHMENTS

ATTACHMENT A PROPOSER CERTIFICATION SHEET

ATTACHMENT B SAMPLE CONTRACT

ATTACHMENT C INSURANCE REQUIREMENTS

ATTACHMENT D VIDEO STANDARDS


ATTACHMENT A PROPOSER CERTIFICATION SHEET

The undersigned further certifies that he/she has read, understands and agrees to abide by all terms and conditions of this Request for Proposal if awarded. Acknowledgment of Addendum: None _____ 1. _____ 2. _____ 3. _____ Proposal is FIRM for 180 days following the Closing.

Proposer certifies that all contents of the Proposal (including any other forms or documentation, if required under this RFP) and this Proposal Certification Sheet, are truthful and accurate and have been prepared independently from all other Proposers, and without collusion, fraud, or other dishonesty.

The Proposer certifies that it does not discriminate against any employee or applicant for employment because of race, color, religion, sex, sexual orientation, national origin, marital status, age or disability or other non-job-related factors as per ORS 659 and 42 U.S. C. 2000e.

If awarded a contract, Proposer agrees to perform the scope of work and meet the performance standards set forth in the final negotiated contract and statement of work.

Company Name (DBA): Legal Name: Address: Type of Organization (Circle One): Sole Proprietor / Partnership / Corporation If Corporation, State of Incorporation If Partnership, attach list of all general and limited partners. Is the proposer an Oregon resident bidder as provided in ORS 279A.120 (ie.paid unemployment taxes or income taxes in Oregon during the 12 calendar months immediately preceding submission of the proposal, and has a business address in Oregon) ?: YES __ NO __ BY: TITLE: Signature BY: DATED: Print/type name CONTACT PERSON: Name: Telephone: E-mail: Fax Number:


1

ATTACHMENT B SAMPLE CONTRACT

This contract is between the McMinnville School District, hereinafter called SCHOOL DISTRICT, and ___________________ hereinafter called CONTRACTOR. This contract and all amendments and exhibits, including all specifications, terms and conditions contained in the Request for Proposal shall be incorporated by reference and made a part of a contract awarded to the successful bidder. TERM OF AGREEMENT The initial term of this agreement will be 12 months from the date the contract is signed, the District may renew for up to four additional one year periods. The attached pricing shall remain in effect for the first 12 months of this agreement. Pricing may not be adjusted without written notice provided at least thirty (30) days in advance of the change. The notice must contain the new pricing and the reason for the change. The District reserves the right to accept the change, or to not accept the change and to cancel the agreement.

COMPLIANCE WITH STATUTES AND RULES All applicable provisions of ORS chapters 279A, 279B, and 279C and all other terms and condition necessary to be inserted into public contracts in the State of Oregon, are hereby incorporated as if such provision were a part of this Contract. The SCHOOL DISTRICT and the CONTRACTOR agree to comply with the provisions of this Contract and all applicable federal, state, and local statutes and regulations and rules. Unless otherwise specified, responsibility for all taxes, assessment, and any other charges imposed by law upon employers shall be the sole responsibility of the CONTRACTOR. Failure of the CONTRACTOR or the SCHOOL DISTRICT to comply with the provisions of this contract and all applicable federal, state, and local statutes and rules shall be cause for termination of this contract as specified in sections concerning recovery of funds and termination. SECURITY CLEARANCE As required by ORS 326.603, Contractor shall ensure that Contractor, any subcontractors, and their officers, employees, and agents will have no direct, unsupervised contact with students while on District property. Contractor shall work with the District to ensure compliance with this requirement.

1. Prior to entry of a Contractor’s employees onto a jobsite, the Contractor authorizes the District to obtain information about contractor personnel to conduct the appropriate criminal history verification per the District standards for background clearance as follows:

2. Contractors, consultants and their employees must have a Fingerprint-Based Criminal History Verification in addition to a Nationwide Criminal History Verification if they are to be given unsupervised entry access to any school site.

3. All other employees of the contractor or consultant who will be working on site must have successfully completed a Nationwide Criminal History Verification.

4. Furthermore, Contractor shall provide timely notification to District once they become aware that an employee providing services within the District has been arrested or charged with a crime listed in ORS 342.143, and remove said individual from District premises until the issue is resolved.

5. The District will process the background checks and provide contractor personnel with photo id badges at the District’s expense.


2

IN WITNESS WHEREOF, this Agreement has been duly executed by the above-named parties, on the day and year first above written.

CONTRACTOR: DISTRICT:

By: By:

Dated: Dated:

Federal Tax ID #


3

McMinnville School District Contract Terms and Conditions

1. Termination of Contract for Cause – If, through any cause, the

contractor fails to fulfill in a timely and proper manner the obligations under this contract or if the contractor violates any of the covenants, agreements, or stipulations of this contract, the District shall thereupon have the right to terminate this contract by giving written notice to the Contractor of such termination and specifying the effective date. In such event, all finished or unfinished documents, data, studies, and reports prepared by the Contractor under this contract shall, at the option of the District, become its property and the Contractor shall be entitled to receive just and equitable compensation for any satisfactory work completed on such documents.

Notwithstanding the above, the Contractor shall not be relieved of liability to the District for damages sustained by the District by virtue of any breach of the contract by the Contractor, and the District may withhold any payments to the Contractor until such time as the exact amount of damages due the District from the Contractor is determined.

Termination for convenience: Either party may terminate not for cause upon thirty days written notice.

Cancellation does not relieve either part from obligations incurred under this contract.

2. Changes – The District may, from time to time, request changes to

the scope of the services of the Contractor to be performed hereunder. The terms of this contract shall not be waived, altered, modified, supplemented, or amended, in any manner whatsoever, except by written agreement signed by both parties.

3. Payment of Suppliers – The Contractor shall make payment

promptly, as due, to all persons supplying to such Contractor labor or material for the prosecution of the work provided for in such contract. ORS 279B.220 (1).

4. Workers’ Compensation – The Contractor shall pay all

contributions or amounts due the Industrial Accident Fund from such Contractor or subcontractor incurred in the performance of the contract. ORS 279B.220 (2). The Contractor is not covered by the District’s workers’ compensation insurance. It is the responsibility of the Contractor to provide workers’ compensation insurance for the Contractor and their employees.

5. Liens or Claims – The Contractor shall not permit any lien or

claim to be filed or prosecuted against the state, county, school district, municipality, municipal corporation or subdivision thereof, on account of any labor or material furnished. 279B.220 (3)

6. Tax Withholding – The Contractor shall pay to the Department of

Revenue all sums withheld from employees pursuant to ORS 316.167. ORS 279B.220 (4). The independent contractor is not an employee of the district and therefore the District will not withhold state, federal, FICA, self-employment taxes from payments.

7. Hours of Work – The Contractor shall pay any employees for

overtime work performed under this public contract in accordance with ORS 653.010 to 653.261 and the Fair labor Standards Act of 1938 (29 U.S.C. 201 et seq.). Contractor will comply with the provisions of ORS 279C.520(1) and (2).

8. Payment of Services – The Contractor shall promptly, as due,

make payment to any person, co-partnership, association, or corporation, furnishing medical, surgical and hospital care, or other needed care and attention, incident to sickness or injury to the employees of the Contractor, of all sums which the Contractor agrees to pay for such services and all monies and sums which the Contractor collected or deducted from the wages of his employees pursuant to law, contract, or agreement for the purpose of providing or paying of such service.

9. Invoice Required – The Contractor must submit an invoice for

payment of services.

10. Applicability – In construing this contract and where the context

so requires, the singular includes the plural, the masculine and the feminine, and all grammatical changes shall be implied to make the provisions hereof apply equally to corporations and individuals.

11. Affirmative Action – Contractor certifies conformance to the

applicable Federal Acts, Executive Orders and Oregon Statutes and Regulations concerning Affirmative Action toward equal employment opportunities. All information and reports required by Federal or Oregon state governments, having responsibility for enforcement of such laws, shall be supplied to the District upon request for purposes of investigation to ascertain compliance with such acts, regulations, and orders.

12 Indemnity/Hold Harmless – To the fullest extent permitted by

law, the undersigned contractor agrees to indemnify and hold the McMinnville School District 40, its employees, agents, representatives, volunteers, and others harmless for any incidents, accidents, losses, expenses, and/or liabilities for which negligence can be attributed directly or indirectly in whole or in part to the contractor’s organization which may arise during the course of this agreement. Also, the McMinnville School District 40 agrees to indemnify and hold the contractor, its employees, agents, representatives, volunteers, and others harmless for any incidents, accidents, losses, expenses, and/or liabilities for which negligence can be attributed directly or indirectly in whole or in part to the District during the course of this agreement.

13. Subcontracts and Assignment – Contractor may not assign or

delegate any of contractor’s rights or obligations under this agreement to any other person or organization without the prior written consent of the District which the district may withhold at its sole discretion.

14. Other Requirements – This contract is governed by the laws of

the State of Oregon and any lawsuits regarding it have to be filed in the Yamhill County Circuit Court. Any exhibits or attachments indicated on the front page of this contract are attached and by this reference made a part hereof.

15. Mediation – Any claim, dispute or other matter in question arising

out of or related to this Agreement shall be subject to mediation as a condition precedent to arbitration or the institution of legal or equitable proceedings by either party. The parties shall share the mediator’s fee and any filing fees equally. The mediation shall take place in McMinnville, Oregon.

16. Litigation – Any legal action or proceeding of any type seeking to

enforce any provision of, or based upon any right arising out of this contract shall be brought against either of the parties in the Yamhill County Circuit Court of the State of Oregon.

17. Complete Agreement – This agreement with the attached

exhibits constitute the entire agreement between the parties. No waiver, consent or modification or change of terms shall bind either party unless they are in writing and signed by both parties.


EXHIBIT 4 INSURANCE REQUIREMENTS

Contractor shall at all times maintain in force at Contractor’s expense, each insurance noted below:

Workers Compensation insurance in compliance with ORS 656.017, which requires subject employers to provide workers’ compensation coverage in accordance with ORS Chapter 656 for all subject workers. Contractor and all subcontractors of Contractor with one or more employees must have this insurance unless exempt under ORS 656.027. THIS COVERAGE IS REQUIRED. Attach Certificate of Insurance. If Contractor does not have coverage and claims to be exempt, attach Exhibit 4 in lieu of Certificate.

Professional Liability / Errors & Omissions (E&O) insurance with a combined single limit of not less than:

$500,000, $1,000,000, $2,000,000 each claim, incident, or occurrence, with an annual aggregate limit of $500,000, $1,000,000, $2,000,000. This is to cover damages caused by error, omission, or negligent

acts related to professional services provided under this Contract. The policy must provide extended reporting period coverage for claims made within two years after this Contract is completed.

Required by District Not required by District By: Date:

Commercial General Liability insurance, on an occurrence basis, with a combined single limit of not less than: $100,000, $500,000, $1,000,000, $5,000,000 each occurrence for Bodily/Personal Injury and Property

Damage, with an annual aggregate limit of $500,000, $1,000,000, $2,000,000. This insurance must include contractual liability coverage.

Required by District Not required by District

Commercial Automobile Liability insurance with a combined single limit, or the equivalent of not less than:

$500,000, $1,000,000, $2,000,000 each occurrence for Bodily Injury / Personal Injury, and Property Damage, including coverage for owned, hired or non-owned vehicles.

Required by District Not required by District By: Date:

Builders All-Risk The District will provide this insurance

Additional Requirements. Coverage must be provided by an insurance company admitted to do business in Oregon or rated A- or better by Best’s Insurance Rating. Contractor shall pay all deductibles and retentions. A cross-liability clause or separation of insured's condition must be included in all commercial general liability policies required by this Contract. Contractor’s coverage will be primary in the event of loss. Certificate(s) of Insurance Required. Contractor shall furnish a current Certificate(s) of Insurance to the District prior to contract execution. The Certificate(s) shall provide that there shall be no cancellation, termination, material change, or reduction of limits of the insurance coverage without 30 days written notice from the Contractor’s insurer to the District. The Certificate(s) shall also state the deductible or retention level. For commercial general liability, the Certificate and by this Contract, shall also provide that the District, its agents, officers, and employees are Additional Insureds with respect to Contractor’s services to be provided under this Contract. Complete copies of insurance policies shall be provided to the District.


sescure

Typewritten Text

ATTACHMENT C

sescure

Typewritten Text

sescure

Typewritten Text

ATTACHEMENT D Video System

1. The NVMS software application can be installed on any open platform hardware, and

does not require hardware multiplexer or time-division technology for video or audio. 2. The NVMS shall support increasing recording storage capacity without additional

licenses. 3. The NVMS shall decompress H.264 video through the client graphics card / graphical

processing unit. 4. The NVMS shall be an enterprise level software solution that shall be scalable 5. Indefinite number of concurrent client to Site connections, limited only by the bandwidth

capability of the network and server 6. The NVMS server and client software applications can be installed and run on the same

computer or on separate computers. 7. The NVMS shall secure video and audio data by securely transmitting all command and

control data via TCP/IP using cryptographic keys based on SSL to prevent eavesdropping or tampering.

8. The NVMS shall support industry standard video compression formats, including but not limited to:

a. JPEG2000 b. MJPEG c. MPEG-4 d. H.264

9. The NVMS shall perform dynamic video stream management. a. Dynamic video stream management shall reduce the system bandwidth and

storage usage by only transmitting video to the client as required. b. The client shall communicate the maximum monitor resolution to the server and

the server shall act as a video proxy and stream the required video resolution. c. The NVMS shall tile multi-megapixel videos streams and only transmit the

requested portion of the video stream to the client. d. Recorded video storage is extended by dynamically reducing the quality of the

recorded video over time so that video is still viable but uses less storage. e. JPEG and JPEG2000 video image rate is reduced to one half or one quarter of

the original image rate. f. H.264 video records a high quality stream and a low quality stream. The high

quality stream is discarded after a set amount of time. g. Shall be available for local users, remote users and mobile devices.

10. The NVMS shall support recording and management of video and audio sources through the use of industry standard drivers. These drivers shall include:

a. ONVIF Profile S b. Publically Published API

11. The NVMS shall support monitoring video and audio sources from: a. Avigilon H4 HD cams b. Avigilon self-learning analytics cameras


c. Avigilon IP H.264/JPEG2000 cameras and encoders d. Rialto video analytics appliances e. ACTi cameras/encoders f. Arecont cameras g. Axis cameras/encoders h. Bosch cameras/encoders i. IQInvision cameras j. Mobotix cameras k. ONVIF 1.00, 1.01, and 1.02 cameras l. Panasonic cameras/encoders m. Pelco cameras n. Samsung cameras/encoders o. Samsung Techwin cameras p. Sanyo cameras q. Scallop cameras r. Sightlogix cameras s. Sony cameras t. VideoIQ cameras/encoders

12. The NVMS shall support de-warping of live and recorded video. a. From supported cameras fitted with an Immervision Panomorph lens. b. From cameras with a fixed fisheye lens

13. The NVMS shall provide the ability to configure and manage alarms and events. a. Individual alarms from a third party system (access control, etc.) can be pre-

selected and configured to be monitored. b. Can define alarm and event triggers. c. Can configure resulting video operations. d. Detect if the video or audio signal is lost and alert the system administrator. e. Support receiving Simple Network Management Protocol (SNMP) messages

from servers and alert users. f. Alarm and event notifications can be customized and forwarded to:

i. Users logged into the client application ii. Users logged into the mobile application iii. Configured email addresses iv. External entities and third party software, such as central monitoring

stations and call centers g. Can escalate alarms from one user or group to another if the alarm is

unacknowledged for a preset duration. h. Email notifications can be configured to:

i. Notify users and system administrators when an event or system health error occurs.

ii. Schedule when email notifications are sent. iii. Include camera images in email notifications.

i. Support receiving digital input triggers and triggering digital outputs from: i. An input/output board


ii. Supported IP camera or encoder iii. Integrated system

14. The NVMS shall provide the ability to send central monitoring stations heartbeat messages, or regular notification to confirm the system connection and that there are no events of note.

15. The NVMS shall maintain an event log and allow users to use the log events as triggers for specific event actions

16. The NVMS shall have the ability assign actions in response to specific event triggers 17. The NVMS shall support conditional event triggers based on the selected digital input

status. 18. The NVMS shall monitor events and alarms based on a user configurable schedule. 19. The NVMS shall provide a maintenance log and audit trail of all system errors and

events. 20. The NVMS shall support software level integration with third-party applications using the

NVMS software development kit (SDK). The SDK shall provide the following features to the third-party software:

a. Connection – auto-discover servers, login and authentication b. Video streaming – auto-discover connected cameras, live and recorded video

(RAW or MJPEG format; H.264 only to a windowed applications) c. Video overlays – display overlays over streaming video (classified object

bounding boxes, motion detection, camera name/location, timestamp) d. PTZ Control – control PTZ cameras (pan/tilt, zoom, presets, patterns, iris and

lock PTZ) e. Audio streaming – stream audio from the third-party system to an NVMS camera

(camera to third-party system only in windowed application) f. Alarm Management – list, query, trigger, assign, acknowledge & purge alarms g. Event Management – list, query, subscribe for notification on events (camera,

server, administrative, digital I/O, video analytics, license plate recognition, point of sale)

h. Bookmark management – list, query, create, delete i. Digital output – trigger digital outputs j. Backup/export – trigger backup or export in NVMS native export video format or

generic video/image formats including AVI, PNG, TIFF, JPEG. 21. The NVMS should support integration with the following systems:

a. AvigilonAccess Control Manager b. AvigilonControl Center License Plate Recognition c. AMAG Symmetry 7 d. CommScope iPatch e. DDS Amadeus f. DSX g. Gallagher FT Command Center h. Hirsch Velocity i. Interlogix Forcefield j. Jacques VoIP Voice Communication System


k. Lenel Facility Commander Wnx v7.x platform l. Lenel OnGuard m. Paxton Net2 n. RS2 AccessIT! o. S2 Netbox p. Software House CCure 9000 q. Stentofon AlphaCom XE

22. The NVMS shall provide a process for upgrading versions: a. Upgrading server software shall not require physical access to the servers.

i. Upgrades shall be launched from the client interface. ii. All connected servers and clients shall receive a distribution of the new

version upgrade. 1. The administrator can manually trigger the upgrade of each

server. iii. The user shall be able to monitor the upgrade progress from the client

interface. b. Upgrading the number of connected devices or upgrading to enterprise version

only requires a change in license key. c. During upgrade process, the NVMS shall continue to record and pass alarm,

video and operational data to the users, monitors, and third party applications. d. Upgrade from one version to another occurs without having to uninstall:

i. The application. ii. The previous version.

e. Automatically upgrade the connected video or audio source firmware. f. Automatically prompt the user to upgrade the client application if it is out of date

with respect to the server software. 23. The NVMS shall run as a service configured to automatically start when the server or

workstation is powered on. 24. The NVMS shall allow users to monitor and administer the system from:

a. A single client application for monitoring live and recorded video and audio. b. A single window for administrating all system connections. c. A single tab for monitoring overall system health and connected sites in parent-

child relationships. d. Any client with access to a local or distributed network.

25. The NVMS should provide multiple levels of system redundancy: a. Cluster and synchronize up to 100 servers into a unified site.

i. In the event of a server failure, the system is able to continue running and allow other servers can take over the failed server’s tasks.

b. Centralized system administration i. Site and server configuration details are replicated to all servers in the

site. ii. Sites can be organized in a hierarchical parent-child relationship where

the parent can always control child site settings.


c. Connect a video or audio source to multiple servers to achieve redundant recording.

d. Create a failover connection for a video or audio source between servers in a site.

26. The NVMS shall support the following video and audio recording options: a. The ability to manually trigger recording. b. Provide a pre-event and post-event recording option. c. Provide a reference frame recording option in the absence of events. d. Create a recording schedule that can be defined individually for each video

source. 27. Where analytics are required, the NVMS shall support the following video analytic event

types when captured by supported cameras: a. Objects in area b. Object loitering c. Objects crossing defined line d. Object appears or enters area e. Object not present in area f. Objects enter area g. Objects leave area h. Object stops in area i. Anticipated direction of travel is violated j. Scene dramatically changes in an unexpected fashion

28. The NVMS shall authenticate users before granting access to the system. 29. The NVMS shall provide access rights that can be tailored to each user or group of

users 30. The NVMS shall provide the ability to rank access rights based on a user’s position

within a configured hierarchy. a. Ranked users may only administer changes to users and groups that are

subordinate in rank. b. The corporate hierarchy can be used to enforce the authority of a parent site over

the user and group settings of one or more child sites. 31. The NVMS shall support multiple credentials to gain access to the system including, but

not limited to: a. The ability to import members of Active Directory groups as users in the NVMS.

i. Changes made to members in the Active Directory are automatically synced with the NVMS.

ii. Users imported from the Active Directory can be added directly to existing permission groups.

b. Using Windows credentials to authenticate users. c. Accept user credentials entered into the NVMS user database.

32. The NVMS shall provide the ability to schedule archive of recorded video with associated events to a local folder or mapped network drive.

33. The NVMS shall provide the ability to backup settings and configuration for each server, including:


a. All site settings such as users/groups, maps and web pages. b. All server settings including device connections. c. Ability to encrypt the backup to maintain security of information

34. The NVMS shall support the ability to share the application window display in a joint session with other users for collaborative investigations.

35. The NVMS shall provide a system tree of video sources, maps, saved views and web pages in the video monitoring tab.

a. The system tree display can be configured. b. The system tree can be organized into virtual folders that are represented as

branches within the Site. c. Users can be granted access to individual items or entire folders within the

system tree. 36. The NVMS shall support an unlimited number of monitors used for monitoring video and

audio streams connected to a single workstation. a. Display all video sources connected to the system. b. Support the ability to drag and drop items from the system tree into the video

monitoring area. c. Support monitoring live and recorded video and audio streams simultaneously on

the same monitor. d. Support viewing the same live or recorded video stream at different zoom levels

and areas of interest. e. Support the ability to switch from live to recorded video on demand for an instant

replay of recently recorded video. f. Support the creation of unlimited views with unique layouts of video streams. g. Support the ability to toggle between tiled and full-screen view. h. Support the ability to save the configured display setting. i. Support the ability to cycle through views (guard tour) based on a specified

interval. j. Support live or recorded video monitoring of 1 to 64 video streams

simultaneously on a single monitor. k. Support displaying videos streams in the following standard layouts:

i. Full Screen ii. 2 x 2 iii. 3 x 3 iv. 4 x 4 v. 5 x 5 vi. 6 x 6 vii. 8 x 8 viii. 1 + 5 ix. 1 + 7 x. 1 + 12 xi. 2 + 8

l. Shall provide tools to build custom video monitoring layouts. 37. The NVMS shall provide a Virtual Matrix application module:


a. Supporting remote control of multiple monitor displays, including video walls. b. Connected monitor displays shall be able to simultaneously display video

streams from multiple sites. 38. The NVMS shall provide the option to display overlays on top of video images. Including

but not limited to the following information: a. Camera name b. Camera location c. Playback timestamp

i. Shall provide the option of displaying device time or local time. d. Live timestamp

i. Shall provide the option of displaying device time or local time. e. Recording indicator f. Motion activity g. Video analytics activity

i. Shall provide color-coded bounding boxes around moving objects classified as humans (red) or vehicles (blue).

h. Detected license plate 39. The NVMS shall support alarm management operations through the video monitoring

interface. Including but not limited to: a. Designated tab for reviewing alarms. b. Interface shall support sequential viewing of alarms. c. Interface shall support sorting of alarms by:

i. Priority ii. Activation time iii. Status

d. Interface shall support filtering alarms by status in the following priority: i. Assigned to me, ii. Active alarms (unassigned), iii. Alarms assigned to others, iv. Acknowledged alarms

e. Support the ability to assign alarms to users. f. Support the ability to acknowledge alarms. g. Support the ability to bookmark alarms. h. Designate one or more regions in the video display area for displaying video

directly linked to triggered alarms or rules. i. Support the ability to acknowledge alarms from the designated video

display area. 40. The NVMS shall support the ability to manually trigger digital output through any of the

following: a. A pre-configured software control. b. A physical trigger that is connected to a supported input/output device.

41. The NVMS shall support creating bookmarks for recorded video and audio. Bookmarks can be:

a. Viewed from multiple sources


b. Displayed on the timeline during playback c. Used as a search criteria for recorded video and audio. Search criteria can

include but are not limited to: i. Name ii. Description iii. Bookmark creator

d. Support protecting a bookmark so the associated video and audio data is never overwritten.

e. Support private bookmarks that are only visible to the user who designated the bookmark as private, and the system administrator.

42. The NVMS shall support the ability to create a map that represents the physical location of cameras and other devices throughout the surveillance system.

a. Maps shall be created from images in the following image formats: i. JPEG ii. BMP iii. PNG iv. GIF

b. The map image size shall be no more than 3000 x 3000 or 9 MP. c. Maps shall have the ability to create a hierarchy of interlinked maps. d. Maps shall support the ability to drag and drop objects in the system tree onto

the map. e. Maps shall support the ability to click and display objects from the map. f. Maps shall support the ability to drag and drop a video source from the map into

the video viewing area. g. Maps shall support the ability to display a preset area of the selected video

source. h. Cameras in a map are highlighted when an alarm linked to the camera is

triggered. 43. The NVMS shall support pan-tilt-zoom (PTZ) cameras and provide the following:

a. Support controlling mechanical PTZ, iris and focus as well as setting presets and patterns

b. Provide the ability to name PTZ presets. c. Support the ability to create PTZ guard tours by combining a set number of

presets that are run in order or random sequence. d. Support the ability to center a PTZ camera’s field of view by clicking anywhere on

the video image. e. Support the ability to click and drag to define an area for the PTZ camera to

mechanically zoom and center on. f. Support controlling mechanical PTZ camera on-screen display and auxiliary

controls. g. Support locking PTZ controls. h. Support using a USB joystick to control PTZ functions.


44. The NVMS shall be sized to retain all recorded video for a minimum of 30 days and allow for simple expansion of storage. There should be no licensing fees to expand storage.

45. The NVMS shall support playback of recorded video and audio. a. Forward and reverse playback of recorded video and audio at variable speeds. b. Video and audio shall playback synchronously when video and audio sources are

linked. 46. The NVMS shall support the following methods for navigating recorded video:

a. Selectable calendar b. Horizontal, scrollable timeline

i. Timeline shall list all displayed video sources ii. Timeline shall highlight motion and events in the recorded video. iii. The NVMS shall support a timeline that can display down to quarter

second increments. iv. The NVMS shall support a timeline that can synchronize video displayed

on multiple tabs to the same point in time. c. Search

47. The NVMS shall support recorded video search. a. Video search shall support the following selectable parameters:

i. Time ii. Date iii. Video source iv. Alarm v. Event type vi. Visual search based on a pre-defined image area, or image thumbnail

1. Thumbnails can be based on the entire image region or a pre-selected area.

2. Thumbnails can be stacked to support an automatic secondary search when looking at a large timespan of video.

vii. Pixel motion in user defined areas viii. Classified object motion detection on supported video analytics sources ix. Point of sale transactions x. License plate detection events. xi. Bookmarks

48. The NVMS shall support the ability to export media and provide the following options: a. Export recorded video in the following formats:

i. Native (AVE) ii. JPEG iii. PNG iv. TIFF v. AVI vi. Print

b. Export recorded audio in the following formats: i. WAV


ii. Native (AVE) iii. AVI

c. Export a still frame of video as displayed in the video preview area: i. Native (AVE) ii. JPEG iii. PNG iv. TIFF

d. Native (AVE) format exports shall: i. Digitally sign recorded video and audio using 256-bit encryption so video

can be authenticated for evidentiary purposes. ii. Be able to export video from one or multiple camera streams

simultaneously. iii. Support exporting multiple video segments from different spans of time. iv. Support reviewing of exported or backed-up video and audio in a

dedicated player. v. Support playback of exported clips in synchronized, sequential time. vi. Support playback of multiple clips in continuous, sequential order. vii. Support exporting of video in lower frame-rates than originally recorded. viii. Support exporting of a designated area from the camera’s recorded field

of view. ix. Support re-export into Native or other supported formats. x. Provide a record of the video source properties, including but not limited

to: 1. Camera model 2. Firmware version 3. Location 4. MAC address 5. Serial number 6. Resolution


security camera equipment & installation...

Documents