<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02153nam a22001817a 4500</leader>
  <controlfield tag="003">OSt</controlfield>
  <controlfield tag="005">20250327083101.0</controlfield>
  <controlfield tag="008">250327b        |||||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="c">NVSU</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Resuello, Hercules S.</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Awareness and perspectives of stakeholders on campus security management of a State University: basis of security operational plan/</subfield>
    <subfield code="c">Hercules S. Resuello</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"> Bayombong:</subfield>
    <subfield code="b">Nueva Vizcaya State University,</subfield>
    <subfield code="c">2023.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">xii, 103 leaves :</subfield>
    <subfield code="b">illustrations, photos ;</subfield>
    <subfield code="c">28 cm.</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">In this study, the perspectives and awareness of students, faculty, and staff members of a state university on campus security management in terms of physical, information, and personnel were explored. This study presented other issues on security and recommended a university management plan that could be used in the University's security management and could be applied in other school campuses.

As a result, the security management situation of NVSU was excellent in that the university had consistent strategies that were created, and departments had all adopted excellent practices. The NVSU's stakeholders agreed that they were aware of the campus security management of the university in terms of personnel, information, and physical security. The NVSU's stakeholders agreed with the information provided regarding their perspective on campus security. Moreover, other issues and concerns were identified, like the university's traffic congestion and parking rules, lack of security and firefighting equipment on the university's premises, especially in the academic buildings.

Based on the results of the study, the researcher recommended university security operational plan purposely to set the security countermeasures, purpose, operational objectives, and concept of operations, organization, and assignment of responsibilities.

Keywords: Campus Security Management, Security Operational Plan, Awareness and Perspectives of Stakeholders

</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Thesis (Master in Management - Public Management)</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">Includes appendices and bibliographical references.</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">ddc</subfield>
    <subfield code="c">TH</subfield>
    <subfield code="n">0</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">397</subfield>
    <subfield code="d">397</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">ddc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">NVSUBAY</subfield>
    <subfield code="b">NVSUBAY</subfield>
    <subfield code="c">GS</subfield>
    <subfield code="d">2025-03-27</subfield>
    <subfield code="e">Donation</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">T R436a 2023</subfield>
    <subfield code="p">T1022</subfield>
    <subfield code="r">2025-03-27 08:32:06</subfield>
    <subfield code="w">2025-03-27</subfield>
    <subfield code="y">TH</subfield>
  </datafield>
</record>
