<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>All Posts on sumicare-blog</title><link>https://neoboi76.github.io/blog/</link><description>Recent content in All Posts on sumicare-blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://neoboi76.github.io/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>01-16-26 - 01-21-26</title><link>https://neoboi76.github.io/blog/qna-01-16-26---01-21-26/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/blog/qna-01-16-26---01-21-26/</guid><description>&lt;p>&lt;strong>Q1.&lt;/strong> Can we integrate transaction (cashier) operations into our system, essentially eliminating the need for a POS?&lt;/p>
&lt;ul>
&lt;li>Is the POS connected to inventory/stock? If yes, can this also be integrated into our system?&lt;br>
**&lt;br>
A1**. POS is stand alone registered system and BIR registered too. POS already integrates and is connected to the inventory.*&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Q2.&lt;/strong> If yes to Q1, what is the process for this? Is the client willing to undergo the process of integrating transaction management into our system?&lt;/p></description></item><item><title>01-21-26 - 01-21-26</title><link>https://neoboi76.github.io/blog/qna-01-21-26---01-21-26/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/blog/qna-01-21-26---01-21-26/</guid><description>&lt;p>&lt;strong>General note:&lt;/strong> Clients can never use their real names, only their nicknames. Even in treatment slips.&lt;/p>
&lt;p>&lt;strong>Regarding the Public frontend website (booking system)&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>This is possible under certain conditions: clients must either fully pay (&lt;em>hard reservation)&lt;/em> to reserve their slots, OR do a &lt;em>soft reservation&lt;/em>, which serves to only inform Lasema that a customer is set to attend on a certain date, &lt;em>without claiming the slot&lt;/em> (see walk-in problem)&lt;em>.&lt;/em>
*
*
* &amp;ldquo;The &lt;strong>walk-in problem&lt;/strong>: what if a client is late or does not attend their appointment? &lt;strong>Solution&lt;/strong>: The client should be present at least 10 to 20 minutes prior to the appointment time and date. Failure to do so will deprive the client of the appointment and be given to new walk-ins. &lt;strong>Another solution:&lt;/strong> Partial payment, down payment/security deposit for services. (Note: This should factor in the 15-minute period of cleaning in between massage services, i.e., if a massage is scheduled at 10:00 AM, it will, in actuality, start at 10:15 AM).&amp;rdquo;&lt;/li>
&lt;li>Clients will be identified based on their &lt;em>nicknames&lt;/em>. If a common nickname is used (meaning that it is already taken in the system), another nickname shall be used, and the client shall also be given the option to enter their Facebook accounts for extra identification. [Include data privacy clause and consent form when client enters the website]. This can be implemented through account creation (email) or simple guest user creation. Emails can also be another source of unique identification.&lt;/li>
&lt;li>Data privacy clause and consent form should popup and include accept or decline choices. The client should be made explicit that their data may be used for recommendation and application purposes.&lt;/li>
&lt;li>System must track the most frequent clients and their patterns, that is, what time of the day they usually avail of Lasema services, what day of the week, what months are most frequent, which massage services are most availed, which therapist, etc (Must explicitly ask permission to use data upon account creation).&lt;/li>
&lt;li>If clients are late for the appointment (&lt;em>hard reservation&lt;/em>), then, say, a client enters 30 minutes late to a massage that&amp;rsquo;s supposed to last one hour, then the client will only be entitled to the remaining thirty minutes (unless the client wishes to extend), but the payment will be for the full hour.&lt;/li>
&lt;li>There is a 15-minute period to clean and prepare the room. So an appointment will always begin at 15 minutes after the designated time, so, say, an 8:00 AM appointment begins at 8:15 AM, and ends at 9:15 AM.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Regarding the Personalized Recommendation System&lt;/strong>&lt;/p></description></item><item><title>09-22-25 - 09-22-25</title><link>https://neoboi76.github.io/blog/qna-09-22-25---09-22-25/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/blog/qna-09-22-25---09-22-25/</guid><description>&lt;h2 id="asked-on-09222025---answered-on-09222025">Asked on 09/22/2025 - Answered on 09/22/2025&lt;/h2>
&lt;ul>
&lt;li>&lt;em>Q: About the client &amp;ldquo;locker number&amp;rdquo; - what does this look like? Give me a sample.&lt;/em>
*&lt;/li>
&lt;li>&lt;em>Q: What about therapists? Do we show it too? Their number next to the client&amp;rsquo;s locker number during an occupied table (i.e., massage session)?&lt;/em>
&lt;ul>
&lt;li>&lt;strong>A: (CLIENTS NUMBER + I prefer Therapist nickname shall be displayed)&lt;/strong>&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>&lt;em>Q: Is there is special payment (in terms of commission. I know all therapists have commissions) for a therapist who is specifically requested as opposed to the ones arbitrarily chosen?&lt;/em>
&lt;ul>
&lt;li>&lt;strong>A: Is there a special commission rate for therapists who are specifically requested by clients, compared to those assigned arbitrarily? (No special Commission) The explanation&lt;br>
Pls. note in regular massage sometime client extends the massage service half or 1 hour. Half hour rate = 120/2 = additional 60 pesos for therapist commission.&lt;br>
Below are Regular massage commission rate @ P120.00/hour&lt;br>
Foot Reflex (1hr) 120&lt;br>
Shiatsu (1hr) 120&lt;br>
Swedish (1hr) 120&lt;br>
Deep Tissue (1hr) 120&lt;br>
Lomi-Lomi (1hr) 120&lt;br>
Lymphatic (1hr) 120&lt;br>
Combination (1hr) 120&lt;br>
Salt Glow Scrub (1hr) 120&lt;br>
Milk Bath Scrub (1hr) 120&lt;br>
Services marked in red below are not included in regular massage and the rates and time are fixed.&lt;br>
Dae Mi DI (Korean Scrub) (30mins) 200&lt;br>
Thai Massage (1hr15min) 150&lt;br>
Aromatheraphy w/ Relflex (1hr30min) 180&lt;br>
Ventosa Massage (1hr30min) 220&lt;br>
Tandem Massage (1hr) This requires 2 Therapist 240&lt;/strong> (refer to therapist booking.xlsx)&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>&lt;em>Q: Confirm this - if there are still available therapists in shift 1, but shift 2 just opened, shift 2 would immediately go in front of the shift 1 line. Is this how the lineup system works as envisioned by our clients?&lt;/em>
&lt;ul>
&lt;li>&lt;strong>A: Can you confirm if this is correct: if there are still available therapists in Shift 1, but Shift 2 just opened, then Shift 2 would immediately take priority over Shift 1 in the lineup system? YES RIGHT. Pls. see therapist schedule &lt;sup id="fnref:1">&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref">1&lt;/a>&lt;/sup>&lt;br>
7am – 5pm&lt;br>
12noon – 10 pm&lt;br>
2:30pm-12:30 midnight&lt;br>
5pm – 3 am&lt;br>
7:30 am – 7pm&lt;/strong>&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>&lt;em>Q: Can a female therapist work with a male client, and vice versa?&lt;/em>
&lt;ul>
&lt;li>&lt;strong>A: It’s absolute that Male Therapist shall massage the Male client But occasionally some female client requests a male therapist too. Female therapist can perform the massage both on Female and Male Client&lt;/strong>&lt;/li>
&lt;li>&lt;em>Give me the specific details regarding the treatment slip and to procure a sample of the receipt for emulation.&lt;/em>&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>*Q: Could you provide the specific details regarding the treatment slip and a sample of the receipt for reference and emulation, along with the cutoff report?
&lt;ul>
&lt;li>A:&lt;/li>
&lt;li>&lt;/li>
&lt;li>&lt;/li>
&lt;li>&lt;/li>
&lt;li>&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>&lt;em>Q: Though I forget it - about the holiday function for analytics? Calendar system? (Low priority question)&lt;/em>
&lt;ul>
&lt;li>&lt;strong>A: It’s like this before holiday we expect high volume of client before holiday day and the holiday day itself. Especially if holiday fall on long weekend.&lt;/strong>&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>&lt;em>Q: What the default commission. Is the commission per hour or the service as a whole? Also, is the commission higher if a therapist is specifically requested?&lt;/em>
&lt;ul>
&lt;li>&lt;strong>A: Commission is based on kind of massage and duration per service. There is no special pay if the Therapist is requested instead the service they provided for request is counted as their extra work plus their decking&lt;sup id="fnref:2">&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref">2&lt;/a>&lt;/sup>. It’s like this if the therapist is in the line 1-5 but if he or she will be requested after serving his/her client she is still on the line-up. So, meaning therapist will have additional client. We need to know the summary of this at the end of the day. Regularly every end of the year top 10 most requested therapist will get bonuses from the management.&lt;sup id="fnref:3">&lt;a href="#fn:3" class="footnote-ref" role="doc-noteref">3&lt;/a>&lt;/sup>&lt;/strong> [clarify this with franz]&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>&lt;em>Q: Do backup therapists have a specific number like regular staff?&lt;/em>
&lt;ul>
&lt;li>&lt;strong>A: Back-up therapist is not in the line-up but if there is an immediate need, we will insert their name in the lineup. As long as there is a need of extra therapist, every therapist is ready to serve. But it’s not absolute that they are the same person every day.&lt;sup id="fnref:4">&lt;a href="#fn:4" class="footnote-ref" role="doc-noteref">4&lt;/a>&lt;/sup>&lt;/strong>&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Q: &lt;em>About full name of Sir Darwin and contact no.? (low priority question)&lt;/em>
&lt;ul>
&lt;li>A: &lt;strong>Could you provide the full name of Sir Darwin and his contact number? I will talk to him first. A busy person u can talk to him at midnight only. You can message him whenever you have question in his Viber&lt;/strong>&lt;/li>
&lt;li>&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;div class="footnotes" role="doc-endnotes">
&lt;hr>
&lt;ol>
&lt;li id="fn:1">
&lt;p>Our lineup algorithm is probably going to take the form of some kind of priority preemptive scheduling. Where:&lt;/p></description></item><item><title>09-22-25 - 10-03-25</title><link>https://neoboi76.github.io/blog/qna-09-22-25---10-03-25/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/blog/qna-09-22-25---10-03-25/</guid><description>&lt;h3 id="note">Note:&lt;/h3>
&lt;pre>&lt;code>From now on, Automation = Computerization
&lt;/code>&lt;/pre>
&lt;p>&lt;em>2. Business Needs&lt;/em>&lt;/p>
&lt;p>Q: What problem or manual process do you think SumiCare could assist in improving for your organization?&lt;/p>
&lt;p>A: SumiCare could assist us in consolidating the booking system, that is, in &lt;del>automating&lt;/del> processes such as digital task assignment, &lt;del>automated&lt;/del> treatment slip production, and &lt;del>automated&lt;/del> production of reports for every cut-off and working day. [RETCONED! DO NOT USE &amp;ldquo;AUTOMATE&amp;rdquo;]&lt;/p>
&lt;p>Q: If you implemented SumiCare what are you hoping to implement?&lt;/p></description></item><item><title>Booking Subsystem (semi-outdated)</title><link>https://neoboi76.github.io/blog/overview-booking-subsystem-semi-outdated/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/blog/overview-booking-subsystem-semi-outdated/</guid><description>&lt;ol>
&lt;li>The booking system is divided into two main &lt;em>views&lt;/em>: &lt;a href="Booking%20Subsystem%20%28semi-outdated%29.md#receptionist-view">receptionist&lt;/a> and &lt;a href="Booking%20Subsystem%20%28semi-outdated%29.md#staff-view">staff&lt;/a> views and systems.&lt;/li>
&lt;/ol>
&lt;h1 id="receptionist-view">Receptionist View&lt;/h1>
&lt;ol start="2">
&lt;li>
&lt;p>The receptionist view is concerned with the following functions: assigning clients to rooms, assigning therapists to clients, producing a treatment slip with necessary info (the receipt shown), &amp;ldquo;skipping&amp;rdquo; a therapist, adjusting time set if in case therapist and/or client is late for their appointment, set if a therapist has been specially &amp;ldquo;requested&amp;rdquo;, and request for back up therapists.&lt;/p></description></item><item><title>complete_overview</title><link>https://neoboi76.github.io/blog/overview-complete_overview/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/blog/overview-complete_overview/</guid><description>&lt;h3 id="introduction">Introduction&lt;/h3>
&lt;p>SumiCare is a web-based spa operations management platform used for managing the day-to-day operations of a spa, such as but not limited to: client appointment scheduling, task completion monitoring, reports generation, therapist and room allocation, and end-to-end transaction management. This platform can be utilized and customized by the target consumers of this product (who are predominantly enterprises operating in the wellness industry, such as spas) to suit their own particular needs. For the duration of this project, testing and implementation of SumiCare will be focused on the particular characteristics and needs of New Lasema Spa Jjimjilbang. Thus, in the creation and testing of SumiCare, the developers will cater to the needs of the aforementioned spa to shape the general platform, which can be implemented by other spas. Thus, there may be said to be a general and New Lasema Spa version of SumiCare. However, this documentation will be focused primarily on the features and structure of the general version.&lt;/p></description></item><item><title>Frontend Online Booking Subsystem</title><link>https://neoboi76.github.io/blog/overview-frontend-online-booking-subsystem/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/blog/overview-frontend-online-booking-subsystem/</guid><description/></item><item><title>Genesis</title><link>https://neoboi76.github.io/blog/overview-genesis/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/blog/overview-genesis/</guid><description>&lt;p>SumiCare is divided into three main parts: The &lt;a href="Booking%20Subsystem%20%28semi-outdated%29.md">Booking (assignment and reassignment) subsystem&lt;/a>, the Frontend online booking system (which includes the personalized recommendation system), and the End-to-End Transaction Management subsystem. The booking subsystem is the most significant and, therefore, the most labor-intensive.****&lt;/p></description></item><item><title>List of what I need from Franz</title><link>https://neoboi76.github.io/blog/overview-list-of-what-i-need-from-franz/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/blog/overview-list-of-what-i-need-from-franz/</guid><description>&lt;p>What I need:&lt;/p>
&lt;ul>
&lt;li>Exact font style use. If N/A, give the closest equivalent&lt;/li>
&lt;li>Exact color scheme. Preferrable if color codes or hex values are used to accurately reproduce the color on the UI.&lt;/li>
&lt;li>Official La sema logo&lt;/li>
&lt;li>Text for consent/data privacy clause for public booking website.&lt;/li>
&lt;/ul></description></item><item><title>system_architecture</title><link>https://neoboi76.github.io/blog/overview-system_architecture/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/blog/overview-system_architecture/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>SumiCare is a web-based spa operations management platform designed to computerize the previously paper-based operational workflows of wellness enterprises such as New Lasema Spa Jjimjilbang. The platform encompasses two interconnected surfaces: a public-facing client booking website and a role-restricted internal operations system. Given this dual-surface structure, the complexity of its business rules (therapist decking, shift-based scheduling, multi-tier reporting, role-based access), and the constraints of an academic development timeline, SumiCare&amp;rsquo;s architecture has been deliberately designed to balance domain expressiveness, developer ergonomics, security, and deployability.&lt;/p></description></item><item><title>Tech Stack (tentative)</title><link>https://neoboi76.github.io/blog/overview-tech-stack-tentative/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/blog/overview-tech-stack-tentative/</guid><description>&lt;h1 id="frontend">Frontend&lt;/h1>
&lt;ul>
&lt;li>Angular Framework
&lt;ul>
&lt;li>Typescript&lt;/li>
&lt;li>Javascript&lt;/li>
&lt;li>HTML&lt;/li>
&lt;li>CSS (Tailwind css with ui component libraries)&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;h1 id="backend">Backend&lt;/h1>
&lt;ul>
&lt;li>Java Springboot
&lt;ul>
&lt;li>Java&lt;/li>
&lt;li>Spring Security&lt;/li>
&lt;li>Sprint Data JPA&lt;/li>
&lt;li>. . .&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;h1 id="database">Database&lt;/h1>
&lt;ul>
&lt;li>Using PostgreSQL with PgAdmin4 (for local hosting and testing)&lt;/li>
&lt;li>Use supabase as production database&lt;/li>
&lt;/ul>
&lt;h1 id="deployment">Deployment&lt;/h1>
&lt;ul>
&lt;li>Docker (and/or kubernetes)&lt;/li>
&lt;li>If using on-premise server
&lt;ul>
&lt;li>Either Local installation or Docker&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>If using local cloud server (either in one server or separate)
&lt;ul>
&lt;li>Docker and/or Kubernetes&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>If using mixed
&lt;ul>
&lt;li>Most likely frontend would be hosted on the cloud, while backend and db be hosted on the on premise server, Or&lt;/li>
&lt;li>Backend and frontend hosted on the cloud (as well as all microservices), while database would be hosted locally.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul></description></item><item><title>UI Stuff</title><link>https://neoboi76.github.io/blog/overview-ui-stuff/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/blog/overview-ui-stuff/</guid><description>&lt;p>What I need:&lt;/p>
&lt;ul>
&lt;li>Exact font style use. If N/A, give the closest equivalent&lt;/li>
&lt;li>Exact color scheme. Preferrable if color codes or hex values are used to accurately reproduce the color on the UI.&lt;/li>
&lt;li>Official La sema logo&lt;/li>
&lt;/ul>
&lt;p>'&lt;/p>
&lt;h3 id="five-main-user-types">Five main user types&lt;/h3>
&lt;ul>
&lt;li>
&lt;ul>
&lt;li>Superadmin (IT Manager)
&lt;ul>
&lt;li>Superadmin basically has unrestricted access to the system (all other functions below, including the ability to manage admins)&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>admin (IT)
&lt;ul>
&lt;li>Admin has all access to the system as mentioned below, but can also manage users below its tier, as well as access to the logs of the system (for non-repudiation purposes). Admin cannot manage other admins.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Manager
&lt;ul>
&lt;li>Manager has all the functionalities of receptionists and staff, but can manage them, as well as see and utilize a reports page detailing the projected revenue of la sema. They also have a comprehensive view of the transactions made encoded by the receptionist.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Receptionist
&lt;ul>
&lt;li>Receptionists can only do one thing, and that is to schedule sessions by assigning a therapist, a massage, and a room to a client, all while recording the whole transaction, producing a treatment slip manually (other reports, such as the cut-off report, are produced automatically).&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Staff
&lt;ul>
&lt;li>The staff view needs no account. In fact, it is merely a view or interface where staff can view tasks assigned to them and acknowledge their task. Shown on one big TV, the view is merely there to inform them, and their interactions with the system are very limited. Hence, very limited permissions.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;h3 id="entry-pages">Entry pages&lt;/h3>
&lt;p>Sign in page&lt;/p></description></item></channel></rss>