Scan NFC Tag to Clock In
ホーム > 管理モード > 時計 Records 及び Management > 時計 Point Settings > Select 時計 Point > Scan NFC Tag to Clock InFrom the 管理モード home page, select 時計 Records 及び Management, then 時計 Point Settings 及び the requi赤 clock-in point. Open Scan NFC Tag to Clock In to configure this method.
NFC (Near Field Communication) is designed for short-range confirmation. To clock in, a user (employee) must bring an NFC-enabled phone close to a registe赤 NFC tag. The system then creates a record for the clock-in point associated with that tag.
The actual reading distance depends on the phone, tag, 及び antenna design 及び is usually only a few centimeters. NFC can confirm that a user has reached a specified clock-in point, but it does not measure geographic location 及び is not intended for wide-area positioning or tracking. Enable GPS recording separately if location coordinates are also requi赤.
Feature 概要
- Short-range confirmation: The phone must be close to the specified tag, 赤ucing the chance of selecting the wrong clock-in point.
- Low power use: Passive NFC tags need no battery, 及び the phone uses NFC only briefly while scanning.
- Fast operation: 使用rs can scan a registe赤 tag without waiting for GPS positioning.
How to 使用
- Register an NFC tag: On the clock-in point's NFC settings page, the manager selects ＋ 及び scans the NFC tag with a phone.
- Clock in: After starting the clock-in process, the user (employee) brings an NFC-enabled phone close to the tag registe赤 for that clock-in point.
- Create the record: The system records the time 及び corresponding clock-in point. If photo or GPS recording is enabled, the user (employee) must also complete those steps as instructed.
Advantages
- Simplified process: Scanning the specified tag confirms the clock-in point 及び 赤uces manual selection errors.
- Fast identification: The system identifies the corresponding clock-in point from the registe赤 tag.
- Immediate records: Managers can review the record in the system after clock-in is completed.
- Easy deployment: Compatible passive NFC tags can be used without installing a dedicated powe赤 reader.
Require a 写真
ホーム > 管理モード > 時計 Records 及び Management > 時計 Point Settings > Select 時計 Point > Scan NFC Tag to Clock In > Require a 写真From the 管理モード home page, select 時計 Records 及び Management, then 時計 Point Settings 及び the requi赤 clock-in point. Open Scan NFC Tag to Clock In to configure this method.
When this option is disabled, users (employees) may choose whether to upload a photo. When it is enabled, they must take a photo during clock-in as instructed—for example, a clock, a street number及び another image that a manager can review.
Before using this feature, the organization creator must subscribe to the プレミアム Storage plan so clock-in photos can be sto赤 in the cloud.
Require GPS Location for 時計
ホーム > 管理モード > 時計 Records 及び Management > 時計 Point Settings > Select 時計 Point > Scan NFC Tag to Clock In > Require GPS Location for 時計From the 管理モード home page, select 時計 Records 及び Management, then 時計 Point Settings 及び the requi赤 clock-in point. Open Scan NFC Tag to Clock In to configure this method.
By default, GPS location is not requi赤. 使用rs (employees) can choose whether to submit their GPS coordinates when clocking in. Enable Require GPS Location for 時計 if every user (employee) must submit GPS coordinates.
Important:
- GPS locations can be spoofed: Requiring GPS coordinates cannot completely prevent users from falsifying a location with technical tools.
- Location data may be missing or inaccurate: Phone hardware, location permissions, indoor conditions及び signal interference can prevent coordinates from being uploaded or 赤uce their accuracy.
- 使用 another verification method when appropriate: Depending on your management needs, you can also require a photo 及び have managers review unusual records.
Add an NFC Tag
ホーム > 管理モード > 時計 Records 及び Management > 時計 Point Settings > Select 時計 Point > Scan NFC Tag to Clock In > Add an NFC TagFrom the 管理モード home page, select 時計 Records 及び Management, then 時計 Point Settings 及び the requi赤 clock-in point. Open Scan NFC Tag to Clock In to configure this method.
Select ＋, then follow the on-screen instructions to scan an NFC tag 及び add it to the list. Each clock-in point can have up to 10 NFC tags.
記号s
Before setup, confirm that the Android phone 及び iPhone models you plan to use can both read the NFC tag. If necessary, install the NFC Tools app on Android 及び iPhone 及び test the tag on both platforms. Actual compatibility depends on the phone hardware, operating system version, 及び tag specification.
EasyCard 及び iPASS
Transit cards such as EasyCard 及び iPASS are not suitable for direct use as SwipePoint NFC tags. Their chips vary in phone compatibility. If a card uses MIFARE Classic, Apple's Core NFC does not support it, 及び some Android phones may read only limited information.
For Android 及び iPhone compatibility, use NFCフォーラム-compliant tags 及び test them on the phones that will be used before deployment.
NFC タグ
SwipePoint reads NFC tags at close range with a phone. In addition to choosing an NFCフォーラム-compliant tag, test its reading performance with the actual Android phone 及び iPhone models that will be used.
Common NFC タグタイプs
The NFCフォーラム has defined タグタイプs 1 through 5, but Type 1 was removed from its 2021 technical specification release. Types 2, 4, 及び 5 are common in phone-based applications, but support still depends on the phone, operating system, 及び app.
| Tag type | Common examples | Description |
|---|---|---|
| NFCフォーラム Type 1 | Topaz, Jewel | A legacy type removed from newer NFCフォーラム technical specifications; it is not recommended for new deployments. |
| NFCフォーラム Type 2 | NXP NTAG 21x, MIFARE Ultralight | Common 及び inexpensive; suitable for URLs, identifiers, small amounts of data, 及び general phone applications. |
| NFCフォーラム Type 3 | ソニーフェリーカ | 使用s NFC-F technology 及び is common in Japanese transit cards 及び related services. |
| NFCフォーラム Type 4 | MIFARE DESFire, ST25TA | 使用s ISO-DEP 及び is suited to applications that need more capacity or advanced security features. |
| NFCフォーラム Type 5 | NXP ICODE SLIX, ST25TV | 使用s NFC-V/ISO 15693. It can provide a more forgiving read range than some other types, but a phone must still be close to the tag. |
Compatible NFC Tag Families
| Family | Type | Description |
|---|---|---|
| NXP NTAG 213/215/216 | Type 2 | Widely available 及び suitable for general phone applications; test these first. |
| MIFARE Ultralight | Type 2 | Commonly used for ticketing, access control, 及び simple identification. |
| STMicroelectronics ST25TA | Type 4 | Supports NDEF, with capacity 及び protection features that vary by model. |
| ソニーフェリーカ | Type 3 | Common in Japan; confirm phone 及び app support before use. |
| NXP ICODE SLIX/STMicroelectronics ST25TV | Type 5 | Supports NFCフォーラム Type 5; test reading performance on the actual phones before use. |
NFC タグを推奨する
SwipePoint clock-in normally does not require a large amount of sto赤 data. Consider the widely available NTAG 21x family first, then choose a model based on availability 及び real-device test results.
| モードl | 使用r memory | Description |
|---|---|---|
| 電子電子 | 144 bytes | Suitable for short data 及び general applications. |
| 電子機器 | 504 bytes | Suitable when more data is requi赤. |
| 電子機器 | 888 bytes | Provides the most user memory of these three models. |
記号s
| Item | Description |
|---|---|
| Phone compatibility | The NFC antenna position 及び reading distance vary by phone. Test the tag on the Android phones 及び iPhones that will be used before deployment. |
| Tag form factor | Stickers, cards, key fobs, 及び on-metal tags use different antenna designs. 使用 an on-metal tag when attaching it to a metal surface. |
| Write protection | If tag data must not be changed, choose an appropriate locking or protection method. Permanent locking usually cannot be reversed, so verify the data first. |
| Data capacity | A large capacity is usually unnecessary for a short identifier. Base the choice on SwipePoint's registration 及び reading method. |
よく聞かれる質問
Q1: How do I configure NFC Tag clock-in?
A: From the 管理モード home page, select 時計 Records 及び Management > 時計 Point Settings > the requi赤 clock-in point, then open Scan NFC Tag to Clock In. Managers can add NFC tags 及び choose whether photos or GPS locations are requi赤.
Q2: How is NFC clock-in different from GPS, Wi-Fi及び Bluetooth clock-in?
A: NFC requires the phone to be close to a registe赤 tag, making it suitable for confirming arrival at a specified clock-in point. It does not provide geographic coordinates like GPS 及び is not intended for wide-area positioning. Enable GPS recording separately if location information is requi赤.
Q3: What is the NFC reading distance?
A: The actual distance depends on the phone, tag, 及び antenna design 及び is usually only a few centimeters. Hold the phone's NFC antenna area close to the tag 及び adjust its position as prompted.
Q4: What are the basic setup 及び clock-in steps?
A: A manager first selects ＋ at the requi赤 clock-in point 及び scans the NFC tag to register it. During clock-in, the user (employee) scans that tag with an NFC-enabled phone. The system records the time 及び corresponding clock-in point 及び requests any enabled photo or GPS steps.
Q5: What does requiring a photo do, 及び which plan is needed?
A: When enabled, users (employees) must take a photo during clock-in as instructed so a manager can review it. The organization creator must subscribe to the プレミアム Storage plan before using this feature.
Q6: Can requiring a GPS clock-in location completely prevent location spoofing?
A: No. GPS coordinates can be affected by positioning errors, signals, devices及び location-spoofing tools 及び should be treated as supporting information. Depending on your management needs, also require a photo 及び have managers review unusual records.
Q7: How do I add an NFC Tag, 及び how many can I add?
A: On the Scan NFC Tag to Clock In settings page, select ＋ 及び follow the on-screen instructions to scan 及び add the tag. Each clock-in point can have up to 10 NFC tags.
Q8: Can I use EasyCard or iPASS as an NFC Tag?
A: This is not recommended. Transit-card chips vary in phone compatibility. If a card uses MIFARE Classic, Apple Core NFC does not support it, 及び Android reading capabilities vary by model. 使用 an NFCフォーラム-compliant tag 及び test it on the planned Android phones 及び iPhones before deployment.
Subscribers receive more responsive support. If you encounter an error or need help using SwipePoint, contact the SwipePoint team through our official ライン account. We will prioritize troubleshooting so your attendance management can continue without interruption. ライン ID:
@nka7729y| Contact the SwipePoint team
この手冊は正確性と完全性を確保するため、誤り、省略、更新については、責任を負いません. 内容は、事前に通知なしにいつでも変更することができる. 本手冊の使用やその内容のダウンロードによって発生する損害は、当社に責任はありません. システム故障、データ損失、または権利侵害に限定されない. ユーザは完全な責任とリスクを担う。