01repeat input Enter the same information multiple times
Copy and recheck between Excel, Messenger, and existing programs
ERP, can it be solved by just changing the program?
Is your system efficient and future-ready?
RIS diagnoses scattered tasks, reduces repetitive input and waiting for confirmation, and leaves operating standards and data as the basis for handover and automation.
Are you still stuck with these difficulties?
02Waiting for confirmation Ask someone about progress
Invisible processing status, check the increasing number of calls and messengers
03Dependent on person in charge When people change, work becomes unstable.
Task sequence and exception handling that remain only in human memory
04Extension constraints There are no business standards to attach new skills to.
Tasks and data that need to be reorganized every time a new technology is added.
Before increasing employees, leave work standards first.
Even if employees change and the company grows,
Must be able to work on the same basis
ERP, not a grand programThe company's work order and standards
It is a system that collects everything in one place.
It is a system that collects everything in one place.
Repeat input / recheck progress status
Same standards, handover, automation base
After construction, the work will change like this
- Save work timeEnter once and use in all your work
- Improved verification speedCheck progress at a glance
- Simplifying handoverSame standards even if the person in charge changes
- Secure expansion baseDirect connection between automation and new technologies
Leave repetitive tasks to the system and leave the CEO’s know-how as the company’s competitive edge.
Prove with results, not explanations
Operational issue previously identified;
RIS answers with real-life examples
Case 01Integration of existing work and student data connection
Gongdangi Busan Academy
Connects academy work divided into multiple programs and Excel into one flow.
- Efficiency goal
- One flow from counseling to student management
- Core method
- Business sequence redesign (BPR) · Baseline data integration (SSOT) · Cloud transformation
- Existing data/system diagnosis
- Cloud operating environment
- Employee ERP
- Student management
- Online lecture platform design
Problem Diagnosis
I was moving student information several times and checking back on progress.
- Old operating environmentStructure becomes more difficult to manage as work increases
As the number of students and data increased, system management and expansion became difficult.
- Broken workflowRepeated input and confirmation at each work step
Student information was moved to multiple materials and checked again.
- Scattered student dataStudent information that was different for each program
There was no standard for linking operating records to online courses.
Conversion process
I converted the problem into four steps.
- Business diagnosis
- Switch environment
- Data Integration
- Expansion design
step01Current workflow analysis and process redesignWe followed the flow from consultation to follow-up guidance and looked for bottlenecks and repetitive inputs.
step02Step-by-step cloud transitionWe moved the data and distribution environment to AWS and established backup and verification standards.
step03ERP/student management integration based on single standard informationStudent information has been integrated so that it can be entered once and continued in consultation, registration, course attendance, and attendance.
step04Scalable platform structure designWe designed a module structure that can be expanded into courses, content, progress, and payment.
Effects and results after deployment
Student information is entered once and used continuously from consultation to attendance.
Case 02Improving old apps and normalizing distribution and maintenance
Bagstrap
We changed the structure to redistribute and manage apps that are blocked from updating.
- Efficiency goal
- Blocked app updates and difficult maintenance
- Core method
- Relieve technical debt · Switch to Flutter environment · Standardize code structure
- Codebase diagnostics
- Switching Flutter execution environment
- library replacement
- Structure standardization
- Deployment Documentation
Problem Diagnosis
The service was operating, but updating and modifying the app was becoming increasingly difficult.
- Outdated execution environmentStore distribution rejection warning
Store update was blocked due to compatibility issues with older versions of Flutter.
- Discontinued partsExternal library not updatable
Simple update was difficult due to end-of-support libraries.
- Development standards mismatchDifferent working methods for each developer
Handover and modification were difficult due to different implementation standards.
Conversion process
I converted the problem into four steps.
- Structural diagnosis
- Switch environment
- Structure maintenance
- Distribution/handover
step01Code structure and dependency diagnosisChecked version, compatibility, and distribution warnings and determined the order of improvement.
step02Staged execution environment transitionFlutter runtime and library were converted step by step while conducting regression testing.
step03Reorganize application structureCleaned up state management and data flow and replaced common functionality with a reusable structure.
step04Distribution stabilization and operation handoverFixed deployment warnings and security issues and documented change structure.
Effects and results after deployment
App updates can now be restarted and managed by the next person in charge.
Before adding features, eliminate waste first
More than new features,
Reduce wasted time
01Starting standard
What should I look for first?
How to create functions firstCreate from the requested screen
RIS that reduces work wasteLook for time-consuming tasks first.
Results that actually remain in the companyIt becomes clear which tasks need to be changed first
02Scope of improvement
How much can I change at once?
How to create functions firstCreate all necessary functions at once
RIS that reduces work wasteChange tasks from those with the greatest effect to the smallest.
Results that actually remain in the companyStart small and see real results
03Data conversion
How do I transfer existing Excel and data?
How to create functions firstMove existing data as is
RIS that reduces work wasteI am organizing only the materials I will use and transferring the exam.
Results that actually remain in the companyData that can be used immediately for work remains
04Operation/Expansion
What do I do after creating the system?
How to create functions firstProject ends when features are delivered
RIS that reduces work wasteWe even check what employees actually write
Results that actually remain in the companyEven if the person in charge changes, operational standards remain.
On-site diagnosis comes first before contracting.
From diagnosis to operational handover,
The CEO and employees will confirm and proceed.
Confirm workCheck out what CEOs and employees actually do
STEP 01Check out what CEOs and employees actually do
Check repeat/wait/missing points
Standard cleanupOrganize who judges what, when, and when
STEP 02Organize who judges what, when, and when
Design of work order, responsibility, and exception handling standards
Apply firstStart with tasks that save time
STEP 03Start with tasks that save time
Apply first to tasks that employees will feel first.
Take over operationCheck what employees are writing and pass on operation methods
STEP 04Check what employees are writing and pass on operation methods
Exception correction, operation handover, next improvement decision