Workflow Sample: How Long does it Take to Approve, in Average?

Folks naturally think this and that about the 'way it should be', when trying to promote RINGI-system (Decision Making method) into paperless.

Especially in corporations of Japan, they must reconsider from the basics first, either (a) to inherit the style of traditional Japanese which seeking approval also by the directors of other departments, or, (b) to migrate to the system of obtaining an instantaneous decision only from the approval authority.

The following Business Process definition is a flow to obtain a judgement of approval directly from approver who is right above the proposer in the Organization tree, when a 'Proposal (Project)' was submitted to the Firm. That is, it's a flow diagram focused on speed which does not inherit the Japanese traditional style. Even though you can call it as a 'RINGI- system', of course, but we dare to call it a 'Project Approval system'. An excellent point is the mechanism that it automatically calculates the time it took to approve.

In addition, some people would like to give a Split Condition for the case that the proposer and the approver is the same person. However, there are different Roles and Characters in a person, so it is good enough to propose by oneself and to approve as well.

[Project Approval flow]

[Project Approval flow;'1. Submit Project' screen]

The indicators of evaluation for the approver, are (1) the time it took to the approval and (2) the effectiveness of budget allocation.

For (2) the effectiveness of budget allocation, there are no other way than to overview the Approved project. On the other hand, about (1) the time it took to the approval, it should be recognized successively throughout the accounting period. In this example, the time it took to approval is calculated automatically and are automatically recorded as data of each Issue. However, when a proposal is submitted in the late night, senseless long time will be recorded, if simply calculating the time between 'Accepted time' and 'Approved time'. And the data mean nothing for statistics. Thus, in this example, the calculation formula does not include the time between 23 pm and 7 am, to the total time.

<Sample Script>

var OpeningOfBusiness = 9; // 9:00
var CloseOfBusiness = 21; // 21:00
var offerDatetime = data.get("9");
var endDatetime = data.get("10");

//Start time for calc d1
var d1 = offerDatetime;
if(offerDatetime.getHours() < OpeningOfBusiness)
{
d1 = offerDatetime.getFirstTimeInDate().addHours(OpeningOfBusiness);
}
else if(CloseOfBusiness <= offerDatetime.getHours() )
{
d1 = offerDatetime.addDays(1).getFirstTimeInDate().addHours(OpeningOfBusiness);
}

//Start time for calc d2
var d2 = endDatetime;
if(CloseOfBusiness <= endDatetime.getHours() )
{
d2 = endDatetime.getFirstTimeInDate().addHours(CloseOfBusiness);
}
else if( endDatetime.getHours() < OpeningOfBusiness )
{
d2 = endDatetime.addDays(-1).getFirstTimeInDate().addHours(CloseOfBusiness);

//Approval time without night hour
var intervalDate = ( Math.floor(d2.getTime() / 1000 /3600 /24 ) - Math.floor(d1.getTime() / 1000 /3600 /24) ) ;
var intervalHour = ( d2.getTime() - d1.getTime() ) / 1000 / 3600;
var netIntervalHour = intervalHour - intervalDate * (24 - CloseOfBusiness + OpeningOfBusiness);
var netIntervalHour2 = Math.floor( netIntervalHour * 100 + 0.5 ) / 100;
if(netIntervalHour2 < 0){netIntervalHour2 = 0;}
retVal.put("11", java.math.BigDecimal( netIntervalHour2 ) );