Newspaper is the primary source of General Knowledge. : Newspaper Distribution Process for City/Town/Area.

Just AUTOMATIC 

::  Newspaper is the primary source of General Knowledge.  ::  

: Newspaper Distribution Process for City/Town/Area :

-> Print & Pack:

* Each Newspaper will have a (highly secured) 'Barcode / QR code' with basic information (Name, Date, Time, No. of Pages, Place, etc.).

* Finally, complete Newspaper will get soft-packed (for example, Inland Postal letter).

-> Required Devices: 

* Device 1: Waterproof Basket-device: A Basket/Box device (with features: ON/OFF and able to identify Newspaper) will be outside of Customer premises.  It can have a (remote) lock.  

* Device 2: Salesman-device: Newspaper Area Salesman/Distributor will have a device that can identify the status (location/availability) of all basket-devices; and can make a note of both Newspaper and basket information, whenever required Newspaper is dropped in basket.

-> Benefits:

* Status of each Newspaper will be recorded, from 'start of printing' to reach Customer.  i.e., Date, Time (Printed [Pages-wise], Released from Press, Transport, Area Salesman/Distributor Received, Paperboy Assigned, Delivered, Customer Received), Pages, Person, etc.  It's helpful to optimise the Newspaper delivery process.

* Both devices can identify the required/specific Newspaper that is requested by Customer.  It's helpful to avoid duplication/mismatch of Newspaper.

* Whenever Paperboy drops the required Newspaper in Customer basket, the Salesman-device can make a note of both Newspaper and basket information; and make a missed call to Customer mobile, informing about arrival of Newspaper.

* Salesman-device: As Salesman-device will display all the baskets information (i.e., place, customer, status, required Newspaper, etc.), it is easy process for the new Paperboy also.

* Basket-device:

+ Newspaper is dropped into the Customer basket.  Due to this, (i) Paperboy can drop the Newspaper at exact Customer location, without any mistake; (ii) Others can't take it; (iii) Newspaper will be in good condition even in Rains.

+ Customer can switch OFF basket-device, whenever Newspaper is not required.

+ On previous day evening, Area Salesman/Distributor can verify the status of baskets (Unavailability:  basket-device is switched OFF, Newspaper is not removed from basket); and inform Customers through message.

- Customer can switch ON basket-device based on need, if it is switched OFF on some purpose and forgot to ON it.

- It's helpful to know if there are any issues with basket-device.

- If the Newspaper is not removed from basket, Paperboy need not place another Newspaper in it.  

- Area Salesman/Distributor can know the prior information about required Newspapers for next day.  So that, (i) Newspaper Company can print Newspapers as per requirement.  (ii) Paperboy can visit only that required/specific places on that day.  

- It makes the Newspaper delivery fast.

* Due to soft-pack, there will be no missing/duplication of internal papers in Newspaper.  Area Salesman/Distributor need not spend additional time to combine internal papers with main paper. 

* If there is no delivery of Newspaper due to any reason (Public Holiday, etc.), there will be no record.  

* No wastage:  Prevention of wastage in Newspaper printing & delivery.  It saves money of Newspaper Company and Customer.

* Size of the basket depends on the number of Newspapers.

* Billing will be easy process for Customer and Area Salesman/Distributor.

* Due to the transparency process and early delivery, more customers may want the Newspaper.  

* Due to more clarity in Newspaper Circulations, Customer can choose specific (distribution) area for Advertisement. It improves the possibilities for more Advertisement.

* Newspaper price will be minimized.  Advertisement cost can be minimized.

* On Customer request, Salesman can collect old Newspapers for recycling business.

* It creates a best platform for subscription and bulk distribution for a city/area.

* Security: 

+ In Crime locations, the 'Barcode / QR code' on Newspaper can help to trace the details. 

+ Caution: Area Salesman/Distributor need to maintain confidentiality about the details of door-locked/unavailable Customers, from Burglars. 

-> Online (Web, Mobile, etc.) App Benefits:  Many Newspaper Companies  vs  One Area-wise Salesman/Distributor  vs  Many Customers. 

* Communication between them will be easy.

* Complete up to date info about Newspaper Circulations.

* App functionalities:

+ Today: Displays info (selected Newspaper and their 'expected delivery' or delivered Time) related to that day. 

+ View: Customer can view all available/selected Newspaper.

+ Change: Customer can add/reduce/change the Newspaper based on requirement, continuously (or) for specific dates.

+ Start: New Customers can raise a request for Registration.  So that, related Area Salesman/Distributor can interact with Customer.

+ Pause/Stop: Customer can inform, if Newspaper is not required temporarily/permanently.

+ Transfer: Customer can inform for Change of Address, in/to same/different area.  So that, Newspaper will be stopped in current place on specific date, and initiated at new place from specific date.  

+ Billing/Payments.

+ Holidays info.

+ Customer can raise the request for collecting old Newspapers.

+ Advertisement: Customer can verify samples, and raise the request for advertisement in Newspaper.

+ Map: Newspaper Companies can choose best Newspaper drop points to improve speed in delivery.

+ Job: Salesmen/Saleswomen vacancies can be filled easily.

* Additional commodities (Weekly/Biweekly/Monthly/Yearly Magazine, Milk, Curd, etc.) can be made available for subscribers of city/area, along with Newspaper.

* If the Customer is not having Online App facility, Area Salesman/Distributor can take the requests.  The payment can be Digital payment.

-> A Tollfree Number:  Benefits:

* New Customer can raise the request for Newspaper Registration.

* Registered Customer can perform most of the App functionalities through the Tollfree number.

-> For Newspaper Companies, it's easy way to reach Customers.

-> Area Salesmen/Distributors can be part of e-Commerce business at different time intervals.

-> Applications for Basket/Box feature: 

* This feature can be extended to Postal and Courier Services.  

* This feature can be useful in 'Waste Management (Collect/Recycle) System'.  Through this feature, Waste collection people can visit only (partially/fully) filled Bins by skipping empty Bins, for fast clearance.  

* * * * *

Process Automation : e-Commerce : Order Management : Issue in 'Bulk Order loading Process' is Resolved, with Batch processing automation.

Just AUTOMATIC

--------------------------------------------------------------------------------------------------------------------------

e-Commerce Business Order Management

--------------------------------------------------------------------------------------------------------------------------

:: Order Loading ::

Concept:

Batch processing automation in 'Bulk Order loading Process'.

e-Commerce B2B online application:  

Enduser can select the items; and place the orders by online.  Application is having two possible ways of order processing.  (i) Manual Order Process, (ii) Bulk Order loading Process.  

In 'Manual Order Process', enduser can choose the items selectively at front-end system, while placing the order.  This process is helpful if the order is having very less/limited number of items.  

In 'Bulk Order loading Process', B2B client has to provide prior inform about the order(s) to the 'Application Administrator' in the form of specific TXT format.  Then the TXT formatted orders will be loaded in to the System.  The successful loaded orders will appear at front-end system.  Now, enduser can place the order with (selected) items, at front-end system.  This process is helpful for bulk orders; and also, if the order is having bulk number of items.  

      

Issue & Risk: 

While loading Bulk orders, the process is getting terminated after sometime by showing (DB CURSOR) ERROR, without loading all the Orders.  Very few Orders are getting loaded in this case.  Due to this, 'Application Administrator' has to restart the process all the time.  It's very hectic.

Problem Statement:

*) The issue is arising in only live System.  (1) Because, lakhs of Orders will be loaded in live system at a time.  (2) It's very difficult to reproduce the issue at Development environment.  (3) It's very difficult to verify the Resolution.

Challenges:  

*) No documentation available.  So, every step is a 'trail and make' process.  

*) Each process is the combination of multiple customizations; those are related to different Clients.  So, I need to take care about impact analysis while taking a decision at each level.  

Root Cause Analysis (Q&A): 

*) Is the issue reoccurring ?

No. The issue is occurring only when loading the bulk (lakhs of) orders at a time.    

*) Is it possible to load the specific amount of Orders based on Scheduler ?

No.  In general, Scheduler initiates the process at specific time.  But, in this 'Bulk Order loading Process' scenario, the number of Orders are variable; and, the number of Items in each Order is also variable.  The availability of Orders is not time based.  So, the Time based Scheduler may not be helpful to resolve the issue.  

*) Try for a solution at Google and Forums ?

Suitable solution is not available.

Requirement: 

*) It is required to load the specific (configured) amount of Orders, at a time.

*) The 'Bulk Order loading Process' has to be continued till all the Orders are loaded.

*) Time based Scheduler is not suitable.  

*) There is a provision to enable/disable this particular customization.

Concept for Issue Resolution: 

*) I thought about Batch processing automation in 'Bulk Order loading Process'.  

*) Whenever the 'Bulk Order loading Process' is initiated, the process selects the specific amount of Orders for loading.  Once the orders are loaded, the process reinitiates itself automatically, for next iteration of same loading process.  The process continuous till all the (available) Orders are loaded into the System.  A configuration element is required to enable/disable this particular customization.  

Concept Implementation: Simple change for Greater impact: 

*) Based on Requirements,  

Present Scenario:  Select all the Orders & Load the Orders.

Proposed Scenario: Select the specific amount of Orders & Load the Orders.  Make this process automatic till END.  A configuration element to enable/disable this.   

*) Application Changes are implemented as follows: 

-> Step 1: Instead of selecting all the Orders at a time, Application will select specific amount of Orders for loading, based on configuration.

-> Step 2: Reinitiate the Step 1 automatically, till all the (available) Orders are loaded into the System.      

-> Step 3: Make a configuration to enable/disable the Steps 1 & 2.

*) 'Bulk Order loading Process' is a Java Application program.  It is the combination of hierarchical of many Classes.  The Base Class is having the selection of Orders for loading.  The Derived Classes are having completely customized Order loading process, configured differently for different Clients.  Steps 1 & 2 are implemented at Base Class.  Reinitiating method has been overridden in Derived Classes.  So, the Concept implementation became simpler with OOP (Object Oriented Programming) Concepts, Inheritance and Polymorphism.

*) The impact analysis (to verify the concept for all the Clients' scenarios) is a major task here. 

Finally, the Issue Resolution is created a greater impact.

Benefit:

The specified issue has been resolved completely.  'Application Administrator' work became simple.  

The Results created excitement in everyone.

Thus, the concept (Batch processing automation) is very much helpful to improve the accuracy with rapidness, in 'Bulk Order loading Process' without any issues.  

Conclusion: 

The Bulk Order loading Process is completely automated, with the Batch processing automation.

In fact, 'Batch processing automation' is an everlasting load balancing concept.

--------------------------------------------------------------------------------------------------------------------------

Kudos to my Team Member Mr. Niraj Kumar for his sincere involvement.

Process Automation : e-Commerce : Order Management : Order Loading and Order Extraction

Just AUTOMATIC

--------------------------------------------------------------------------------------------------------------------------

e-Commerce Business Order Management

--------------------------------------------------------------------------------------------------------------------------

:: Order Loading ::

Concept:

Order reloading Process Automation.

Existing Process: 

It's a e-Commerce B2B online application.  Enduser can select the items; and place the orders by online.  Application is having two possible ways of order processing.  (i) Manual Order Process, (ii) Bulk Order loading Process.  

In 'Manual Order Process', enduser can choose the items selectively at front-end system, while placing the order.  This process is helpful if the order is having very less/limited number of items.  

In 'Bulk Order loading Process', B2B client has to provide prior inform about the order(s) to the 'Application Administrator' in the form of specific TXT format.  Then the TXT formatted orders will be loaded in to the system.  The successful loaded orders will appear at front-end system.  Now, enduser can place the order with (selected) items, at front-end system.  This process is helpful for bulk orders; and also, if the order is having bulk number of items.  

      

Issue & Risk: 

While loading orders through 'Bulk Order loading Process', orders may 'failed to load' into the system, due to many reasons, i.e., (i) mis-configurations in the system; (ii) missing required/mandatory data at TXT; (iii) remarks in TXT formatted data; or any.    

After fixing the required configuration issues, 'Application Administrator' will reload the orders by selecting specific orders through separate tool.  It's a manual process.  It's a risk in case of handling Bulk orders.              

Challenges:

*) No documentation available.  So, every step is a 'trail and make' process.
*) Each process is the combination of multiple customizations, those are related to different clients.  So, I need to take care about impact analysis while taking a decision at each level.

Requirement: 

Order reloading process has to be automated.  

Issue Resolution: 

Order reloading process is incorporated as part of the basic Order loading process.  Now, 'Application Administrator' need not worry about Order reloading process.  Once the configuration issues are fixed by him/her, order loading process will collect the 'Issue-Fixed Orders'; and then, revalidate and reloaded them into the system....... automatically.       

Conclusion: 

The concept is very much helpful to improve the 'accuracy with rapidness' in 'order reloading' process.  

Benefit:

Complete 'order reloading' process is automated.

--------------------------------------------------------------------------------------------------------------------------

:: Order Extraction :: 

Concept:

IPP Order extraction Process Automation.

Existing Process: 

Once the endusers have placed the orders at front-end system, the orders will be extracted in the form of flat text files and then passed on to legacy system for processing.
    

Issue & Risk: 

While performing extraction of orders, orders may 'failed to extract' from the system, due to some specific mis-configuration reasons.    

After fixing the required configuration issues, 'Application Administrator' will make some changes at database to initiate re-extraction process.  It's a manual process.  It's a risk in case of handling Bulk orders.              

Challenge:

No documentation available.  So, every step is a 'trail and make' process.

Requirement: 

Order re-extraction process has to be automated.  

Issue Resolution: 

Order re-extraction process is incorporated as part of the basic Order extraction process.  Now, 'Application Administrator' need not worry about Order re-extraction process.  Once the configuration issues are fixed by him/her, order extraction process will collect the 'Issue-Fixed Orders for Extraction'; and then, revalidate and re-extract them for the legacy system....... automatically.
And also, make a provision to extract the specific order(s) at any point of time, for the convenience of 'Application Administrator'.       

Conclusion: 

The concept is very much helpful to improve the 'accuracy with rapidness' in 'order re-extraction' process.

Benefits:
Complete 'order re-extraction' process is automated.

--------------------------------------------------------------------------------------------------------------------------