Severity: 8192
Message: Return type of CI_Session_files_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 132
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 292
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 166
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 235
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 315
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 356
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 282
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: Warning
Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 294
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 304
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 314
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 315
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 316
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 317
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 375
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: drivers/Session_files_driver.php
Line Number: 108
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: Warning
Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 110
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: Warning
Message: session_start(): Session cannot be started after headers have already been sent
Filename: Session/Session.php
Line Number: 143
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
When companies talk about cost cutting, they usually mean reducing operating expenses. While this may indeed help, very few take a look at their business processes, or “how everything is done” as another key area to consider. But cutting down the number of steps of any process could save time and cost—and is worthy of everyone’s attention.
We asked Michael Sibayan, a Six Sigma Black Belter who has years of experience in operations management, for some steps to follow to guide anyone who would like to embark on this endeavor.
Step 1: Document your current process
There are many benefits in documenting your processes. It serves as a calibration tool to all concerned individuals to ensure consistency of execution and output. It can also serve as a basis to check on what is the standard versus what is really happening. In doing process improvement, you need to start with documenting “what” is actually happening. Not “what should be” happening or “what we think should be” happening. This will help you effectively define the problem areas in your process.
Step 2: Define in detail the key elements of the process that you are improving.
You need to understand more about the business process. You can do this by identifying the five key elements in a process. That is, the Supplier, The Input, The Process Activities, The Output and the Customer. From here, measure and track the performance of the process output and see how it performs versus the set standards.
Step 3: Define the problem. Identify what is value adding and nonvalue adding
There are many methodologies and tools to use in improving a process. It depends on what you need to improve. And if it is related to productivity, quality, efficiency, or effectiveness. As a start, you can easily improve a process by defining and removing customer/business nonvalue add activities. Simply removing the activities or process steps that don’t add value to anybody can significantly affect both the process activity and the expected output—plus reduce costs.