<?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>02245nam a22002057a 4500</leader>
  <controlfield tag="001">16574</controlfield>
  <controlfield tag="003">OCLRC</controlfield>
  <controlfield tag="005">20260731013039.0</controlfield>
  <controlfield tag="008">250726t        xxu||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">OCLRC</subfield>
  </datafield>
  <datafield tag="082" ind1=" " ind2=" ">
    <subfield code="a">T 004 2024 0142 </subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Rodriguez, John Albert</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Implementation  of GPS real-time tracking:</subfield>
    <subfield code="b">enhanced work productivity/</subfield>
    <subfield code="c">John Albert Rodriguez, Joemar Bruce Rogacion, and John Michael Teano.</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Paran&#xCC;&#x83;aque City:</subfield>
    <subfield code="b">Olivarez College.</subfield>
    <subfield code="c">2024.</subfield>
  </datafield>
  <datafield tag="502" ind1=" " ind2=" ">
    <subfield code="a">Undergraduate thesis.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">The main goal is to spend time and effort completing the online attendance system with our team. Since the issue is primarily about attendance, it may also cause arguments because they don{92}t have proper time in and log out, which makes it unfair to all of them. To address this, our team met right away and decided on a system. An online attendance website that includes GPS tracking, ghost employees and smoothed attendance can be taken into consideration. Clocking in and out, examining attendance records and leave requests, and updating personal information are all features of such an employee portal.            The administrator dashboard{92}s functions include real-time viewing and tracking, report generating, profile management, leave approval, and GPS position tracking, GPS tracking would be linked with them. They would have real-time time and position tracking and monitoring, geofencing by work zones, which would automatically alert them to any absences or locations outside of the zone for which they are deployed, among other abnormalities. It is even possible to incorporate biometric authentication for optional use. It will have features like shift shifting, automated leave accrual and deductions, flexible shift scheduling and overtime tracking, and enforced leave regulations.           Strong notification features will also be included in the system to notify users of attendance irregularities, approve leave requests, and provide other pertinent warnings; reporting and data analytics will be integrated to provide critical information for decision-making.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Rogacion, Joemar Bruce</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Teano, John Micahel</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">THES</subfield>
    <subfield code="j">T 004 2024 0142 </subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">16574</subfield>
    <subfield code="d">16574</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">LRC</subfield>
    <subfield code="b">GR</subfield>
    <subfield code="d">2026-07-31</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">T 004 2024 0142</subfield>
    <subfield code="r">2026-07-31 01:30:39</subfield>
    <subfield code="w">2026-07-31</subfield>
    <subfield code="y">THES</subfield>
  </datafield>
</record>
