Monday, March 20, 2017

What can a Project Manager learn from the Toshiba Accounting Scandal (2015)?


Standard Accounting for a firm deals with the accounting for a company as a whole, usually within a fixed time period (i.e. quarterly or annually). On the other hand, Project Accounting monitors the financials of individual projects throughout the life-cycle of the project. 

These days more and more companies are earning significant revenues through project implementations. Mostly, such companies have Projectized or Matrix organizational structures and the majority of the organization’s resources are involved in project work. The project work is generally completed for the benefit of an external customer and in such organizations, Project Managers have greater autonomy to run the projects. Nevertheless, the project financials are coupled with organizational financial considerations. Therefore, it is important for Project Managers not only to have an in-depth understanding of project accounting but also to have a reasonably good understanding of Standard Accounting. 

In recent past, many Financial Accounting Experts have done analysis on Toshiba's Accounting Scandal (year 2015). Going through following compilation of some of findings of this scandal can be interesting for project management professionals. They may find it useful to link the significance of day to day project accounting with larger perspective of standard accounting. 

So, the story in short is that the global economic crisis in the year 2008 and an earthquake that triggered a tsunami in the year 2011 had a significant impact on the operations and businesses of Toshiba. Despite this, Toshiba’s performance improved and was profitable from the year 2010-11. Later on, it was revealed on investigation by Securities and Exchange Surveillance Commission (SESC) that Toshiba inflated earnings by at least $1.2 billion during the period 2009-2014. 

The rest of the blog is an attempt to illustrate some of the points on the scandal that could be relevant for Project Management: - 

  1. 1) Faulty use of the percentage-of-completion method of accounting - A large part of the problem stemmed from improper use of an accounting method called “percentage-of-completion”, which is commonly used in long-term projects. More specifically under this non-cash flow method, the accounting treatment for contract work in a fiscal year is estimated and the income and cost of the contract for the current accounting period is reported on that basis. Toshiba claimed that the problem was caused by work in electricity generation, railways and related projects; these groups had focused too much on attaining their profit targets by improperly lowering expenses in the near-term periods. Managers did this in the knowledge that it violated the principles of the percentage-of-completion approach. (Ref - Global Advanced Research Journal of Management and Business Studies (ISSN: 2315-5086) Vol. 5(4) pp. 088-101, April, 2016) 

Related Points to Note for a Project Manager - Complex projects may have multiple inter-dependent parts or certain aspects involving organizational change management, engineering work, process re-engineering or automation related work (or all of these complexities). For such projects, at many instances, it becomes extremely difficult to assess the extent of completion of work (and forecasting on following related pieces of work), even with data available through reasonably good project management metrics. In addition, quite often Project Managers have to take a judgement on percentage of completion of work for a certain duration of time (Quarter, Annual). These time periods are not always in sync with the project delivery timelines or project milestones. Moreover, any project manager will tell that the applying accounting principal of conservatism for financial reporting is strongly contested by increasing expectations of the client and senior management (of the organization responsible to execute the project) to see the project going in line (or doing better) as per estimated cost, time and quality. 

Therefore, a Project Manager must take cognizance of the fact that an accurate and well-judged reporting of percentage-of-completion (by most of the projects) becomes basis for correct accrual entries ensuring certainty of realization of revenue. 

  1. 2) Padded Accounts for Accommodating Stopgap Measures - The Company (also) padded accounts by adjusting the inventory records of its semiconductor business. However, stopgap measures implemented for the sake of temporarily boosting profits had to be accounted for in subsequent accounting periods. And as a result, Toshiba found itself in the position of needing to continue padding its books.(Ref- www.nippon.com/en/in-depth/a04802) 

Related Points to Note for a Project Manager - A project is a Temporary Organization with a definite beginning and a definite end but the point to note is that the organizations having stake on the project are not temporary (in nature). Many times these organizations have their own interest on different outcomes of the project and they exert pressure to see the outcome of their own interest getting realized without giving heed to fulfilment of overall objective of the project. In such a circumstance, a Project Manager should avoid getting lured to stopgap measures as an arrangement to manage much more powerful and demanding stakeholders. 

In this regards, it is observed that many a times, contrary to expectations of a Project Manager, even cautiously manipulated project accounts for stopgap measures get difficult to do away with over the due course of time (the assumption of either getting space to hide the stopgap measures in future project accounting entries or to garner a relevant justification to justify stopgap measure does not always succeed). 

  1. 3) Carryover to delay Expenditure - Toshiba’s television manufacturing unit put off booking losses by using “carryovers,” requesting vendors, for example, to postpone issuing invoices for advertisement, distribution, or other services until the next quarter, while moving up projected discounts on parts to the current accounting period. In addition, it inflated profits by boosting prices of products sold to overseas affiliates. (Ref- www.nippon.com/en/in-depth/a04802) 

Related Points to Note for a Project Manager - Financial accounts are assumed to portray the reality of financial transactions. A deliberate attempt to manipulate different component of transactions to make the project financial look healthy by many project managers of an organization can always lead to inflated financial statements of the organization. Adherence to accounting principal of matching must be observed to the best possible extent. 

  1. 4) Inappropriate Recording of Outsourcing Transactions - In its personal computer business, the company inflated revenues through transactions with manufacturers producing Toshiba-brand computers under contract. Toshiba sells the manufacturers key parts for the computers and then buys the finished products from them. To avoid revealing the actual prices of its parts to competitors, the company sells them at an inflated “masking price” to the manufacturers and it buys the finished computers from them at a price that adds production and other costs to this inflated amount. Since the high masking price for the parts is offset by a correspondingly inflated price for the finished product, the gains on these sales of parts cannot properly be booked as profits. But that is what Toshiba did. Over the years the company raised its masking prices until they were almost five times the actual cost of the parts. And by forcing manufacturers to buy more parts than they needed, Toshiba was able to make its profits for the current accounting period look bigger. (Ref- www.nippon.com/en/in-depth/a04802) 

Related Points to Note for a Project Manager - Project Managers dealing with turnkey projects have to depend on external entities for executing project. It is not very common for a company to have specialization on the whole gamut of product, services, skills and expertise required for any turnkey projects. Project Managers must ensure principals of accounting (like conservatism, matching) are followed while recoding transactions with external vendors (for both suppliers of products and services). Appropriate controls and checks and balances should be put in place to ensure that the business relationship with vendors remain in strict conformance to the contractual obligations. Wherever it is deemed appropriate reasonability of rates and appropriate quantity of product and services must be verified. 

  1. 5) Business Environment and Work Culture - In the Japanese business community, subordinate employees are expected to demonstrate a deep level of commitment and loyalty to their corporate managers. Under the (Japanese) principles of makoto, it is disrespectful for an employee to speak or act outside the scope of his or her prescribed position. This belief system prevents many individuals from challenging the decisions of their superiors, and discourages them from disclosing any problems that may arise. In return, superiors will often reward their most loyal employees with respect, appreciation, and even promotions. Thus corporate managers are able to consolidate their power by surrounding themselves with employees who are committed to following their orders. In addition to the values of makoto, Japanese ideas of cultural harmony also play a big role in facilitating corporate misconduct. At its core, cultural harmony can be best described by the Japanese proverb, “the nail that sticks out gets hammed down,”—meaning that its better to follow the group than to stand out. Thus, “groupthink” dominates Japanese corporate culture. (Ref- www.law.emory.edu/ecgar/_documents/volumes/3/3/essays/engelberg.pdf) 

Related Points to Note for a Project Manager - It may be noted that time and again cases of corporate governance failures have provided evidence that good corporate governance structure does not necessarily lead to good corporate governance. But, (to support good governance,) regional business culture and organizational culture is a critical determinant of the quality of corporate governance.  

Within organizations, its the People, who follow processes. It may be noted that when it comes to following the accepted processes in true spirit, it has been widely observed that among so many tempting and directive forces trying to influence an employee to deviate from adherence to processes (or regulations), usually most employees eventually end acting in accordance to cultural norms. Project Managers therefore must be empowered to promote a culture of ethical corporate values. 

In addition, an independent and sensible internal audit team may be given adequate powers to conduct independent audit. It is important that highly experienced and industry-experts must be part of the audit team. Internal audit can function independently only if the audit committee is capable, independent and effective. This is possible only if the internal audit-team reports to an independent body (say audit committee separately functioning in parallel to executive hierarchy). Project Managers must be open for audit and advice by audit team on critical decision making. 

 

 

References:- 

 

 

/********************/



The blog-post was published on the Website of IPE Global Limited on 20 MAR 2017. Please click at the following link to view the blog-post on IPE website:-

http://www.ipeglobal.com/blogs/what-can-a-project-manager-learn-from-toshiba-s-accounting-scandal-2015-28.php

Monday, August 8, 2016

5 Points to Consider for IT Services Sales to Government Organizations


I have been working in government sector for last six years. In my opinion, the business landscape for sales of IT services in different governments / government organizations in India has been slowly changing over these years. Based on these observations, I have tried to list following five points for consideration of IT Services Sales professionals:-  
1.     Go Beyond the Power Point Presentations – Companies use Power Point Presentations (PPP) to explain their understanding about the assignment and to explain the solution they propose. Probably, now is time to go beyond Power Point Presentations (PPP) to explain the government customers about the capabilities of a company to perform any assignment. This means, while explaining the solution, in addition to the slide-pack, a live demonstration of functional products similar to the assignment or closely associated with the assignment could add meaningful value to the presentation session. Similarly, display of relevant papers (clear, concise and conclusive white papers or research results) published in reputed journals (and available online with comments, discussions and responses) help in establishing a company as a sensible and credible organization in professional fraternity.
2.     Go for Strategic Specialization - Government organizations are now having much better grip on understanding of IT (Information Technology) implementation and on managing IT projects. Critical differentiations in products and services, which result in enhanced project outcome do not go unnoticed by those professionals, who manage projects from government side. Similarly, advantages due to grip on industry vertical or excellence in project execution through tried and tested methodologies or improved quality of deliverables due to unique contributions from experienced professionals get recognized much better than ever before. Consistency in maintaining such type of differentiations in competitive market is not possible unless a focused and conscious effort to specialize in niche area, strategically suited to a company, is practiced with utmost sincerity. Time and again, it is stablished that in long runs Specialist beats Generalist. Therefore, it is worth to invest in specialization for improving long term business prospects.
3.     Go Market-Pull Way in Government Business Now – IT vendors and government organizations now have a better understanding on challenges of implementation of IT initiatives in government sector. At the same time, technology diffusion and technology adoption by larger population in recent times seem to be bringing socio-cultural changes in favor of extensive use of technology (by citizens at large) for getting associated with different agencies. Even many employees feel more comfortable to communicate through electronic means for day to day working in government offices. These developments seem to have made implementation of IT projects easier than ever before. But more importantly, these changes are indicating vendors for a shift from Technology Push towards Market (Public) Pull strategy as the demand for technology is getting generated at the level of beneficiaries (or at times end users of product and services). So, now the companies having aspirations to become a vendor for governments can identify a need and develop (or customize) products and services to best fit the identified need in the proposals sent to government organizations. If public procurement is done at right timing and if a suitable product / services with right positioning in market is selected through procurement process, public pull may help in ensuring successful implementation of IT projects. This is in contrast to earlier times, when vendors had promising technology at hand for government organizations to use but making the government organizations and end users (beneficiaries) understand the value added benefits from technology used to be quite a challenge. In those times, vendors used to “push” technology through the bureaucratic (government) organizations first and if they succeeded then they used to push the technology down to implementing team and eventually to beneficiaries.
4.     Go Beyond Conventional Turnkey Projects and Look for Smaller Opportunities – The latest trend in IT related government procurement appears to be in favor of avoiding large RFPs (Request for Proposals) with multiple consortium partners, with hidden complexities, with unknown risks and with detailed requirements (which takes a year to gather). Instead, the preference is shifting towards developing agile procurement capability to deliver incremental agency value on a regular basis through bringing on-board specialized vendors for every logical piece of work. IT hardware procurement (which is more of a product purchase with huge Capex expenditure) is usually segregated from IT software services (which is more of a service purchase with dominant Opex expenditure). In the new arrangement of small and specific tenders, mid-sized niche players get a chance to compete, to perform their piece of task with perfection and get the payment released quickly.
5.     Go for Excellence in Delivery – Nothing can establish a company much better than the quality of delivery. In long run, this holds true even for government sector, which is increasingly getting quality conscious. In this regards, many experts believe that pressure to perform on government organizations is slowly changing the way public procurement is done in government organizations and concerns of departments are shifting towards delivered products / services in addition to the budget and UCs (Utilization Certificates).  
I believe that despite the fact that procurement is done through free and fair tenders in government sector (in which pricing is believed to play critical role despite QCBS – Quality and Cost Based System of procurement), the relative excellence in delivery holds the backbone for continuous business prospects. All this is more relevant to IT product / services where quality of professionals and professional services make the critical difference.  
In my opinion, howsoever good the sales team be or how so good the management be, the genuine competitive advantage for an IT Service Company can be attributed to a clear strategy and to the quality of delivery (of product and services) done by the technical team. Therefore, strategic investment on technology excellence and on nurturing technical team to boost performance and to acquire new skills contributes significantly to continuous sales prospects in larger span of time.   
 
/*************************/

Monday, May 2, 2016

Correlation of e-Gov Transactions with Some Other State Wise Data of Indian States


This is an attempt to find correlation of some of the aspects of State Wise Data of Indian States with e-Gov Transactions data available at e-taal website (e-taal is a web portal for dissemination of e-Transactions statistics of National and State level e-Governance Projects including Mission Mode Projects). The respective correlation coefficients are given in the table (TABLE - 1) below. The details are displayed in excel sheet in the following list:-
 
 
 TABLE - 1
Correlation Coefficients of eTransaction/1000 Population* (eTx) with respect to some of  State Wise Data of Indian States
eTx with Population 0.082481
eTx with Sex-Ratio 0.270576
eTx with Literacy 0.20019
eTx with Urbanization 0.247364
eTX with Density of Population 0.036462
eTx with Area of State 0.126776
References : -
http://www.census2011.co.in/states.php
 
*STATE WISE eTRANSACTION / 1000 POPULATION (source-e-Taal, 1 JAN 2015 till 31 MAR 2016)

Provisional data released by Census India, Census 2011 (http://indiafacts.in/india-census-2011/urban-rural-population-o-india/)   

 
Some more correlation coefficients are given in the tables (TABLE - 2 & 3) below. Related investigations on the data are details in the sheet that can be accessed through following link:-

Correlation of eGov Transaction Data with some of the State Wise Data of Indian States with other related calculations (for TABLE - 2 and TABLE - 3)

TABLE - 2
Correlation Coefficient of eTransaction/1000 Population* (eTx) with respect to some of  State Wise Data of Indian States
eTx with (Literacy + Urbanization) 0.28110838
eTx with (Literacy + Urbanization + % Sex-Ratio) 0.34426227
eTx with (Urbanization + % Sex-Ratio) 0.34116737

TABLE - 3
Some other related Correlation Coefficients 
% Sex-Ratio with Urbanization  -0.187446439
Literacy(%) with Urbanization  0.62547127
% Sex-Ratio with Literacy -0.025630917


An attempt to assess the above data has been made in the points below. However, based on the following discussions, it may not be possible to reach to conclusions:-
  1. From TABLE - 1, Correlation Coefficients of eTransaction/1000 Population (eTx) with respect to Sex-Ratio and Urbanization have been observed to be having higher values (0.27 & 0.25 respectively). NeGP (National e-Governance Plan) was initiated in 2008. In 2015, the next phase of e-Governance Initiative has been started under Digital India program. Let us assume that by now more or less similar e-Government service facilities are available across India for rendering basic government services. Therefore, the correlation figures may suggest that e-Governance services are seen to have been used more extensively in the states with higher  Urbanization and better Sex-Ratios.
  2. TABLE - 3 suggest marginal negative correlation between Sex-Ratio and Urbanization. This can be explained through many studies. Evidence show that the practice of sex-selective abortions is more prevalent in urban areas and amongst the well educated women. (Guilmoto, C.Z. (2007), “Characteristics of sex- ratio imbalance in India and future scenarios”,UNFPA and Jha, P., Kumar,R., Vasa,P., Dhingra,N., Thiruchelvam,D. and Moineddin, R. (2006), “Low maleto-female sex ratio of children born in India: national survey of 1.1 million households”, The Lancet, 367 (9506): 211- 218 )  
  3. In an attempt to understand better correlation between eTx and Sex-Ratio (observed in point - 1 above), if it could be assumed that better Sex-Ratio indicate Gender Equality and similarly, use of eTransaction by more and more people indicate general inclination for more accessible, friendly and service oriented democratic institutions, then the work on Gender Equality and Democracy by  Ronald Inglehart; Pippa Norris and Christian Welzel indicating that growing emphasis on gender equality is a central component of the process of democratization seems to be holding true. (Source - Comparative Sociology, Volume 1, Issue 3, pages 321 – 345; 2002; ISSN: 1569-1322 E-ISSN: 1569-1330)
  4. The correlation between eTx and Urbanization can be attributed to a strong digital divide in urban population with respect to rural population in India. At national level, there is no single (digital) divide, but multiple (digital) divides: for instance; within countries, between men and women, young and elderly, rich and poor and most importantly rural and urban (Dr. Sumanjeet Singh, Ramjas College Digital Divide in India: Measurement, Determinants and Policy for Addressing the Challenges in Bridging the Digital Divide; JEL Codes: R58; Z13; O33; I38). The phrase “digital divide” refers to the unique and disproportionate pace of development in societies in having access to digital infrastructure and services (Paul,J .2002). 

References:-

http://www2.hw.ac.uk/sml/downloads/economics/HW_DP_2012_01.pdf
http://www.ijsrp.org/research-paper-1213/ijsrp-p2471.pdf
http://booksandjournals.brillonline.com/content/journals/10.1163/156913302100418628
https://pdfs.semanticscholar.org/dc77/1e7870961e84b4134bb22939f0ef8db4b370.pdf
Image - http://www.shutterstock.com/

 /*****************************/

Saturday, March 26, 2016

5 Points to keep in mind while Conceptualizing a Project



Conceptualization of a project is the first and a critical stage in a project life-cycle. This is also termed as DPR phase in some of government projects, which involves preparation of DPR (Detailed Project Report). During this stage, a series of activities are carried out to establish that idea of the project is feasible and to ensure that outcome of the project will yield intended benefits. Consensus on the project idea and feasibility among stakeholders is sought, scope is defined and verified, deliverable are broadly finalized, tentative estimate related to time-cost-quality are finalized, project design and execution methodology is approved and major risks are identified. There are many tools and technologies available to help the Project Managers in the Project Conceptualization and most of the managers use them to be thorough and convincing with their proposals on conceptualization. However, it may be noted that project managers keep on learning and are consistently trying for perfecting themselves in project management approach and in application of tools and technologies to projects. Through my learning from different projects I have been associated with in last sixteen years of work experience, I feel keeping in back of mind the following points may be helpful for managers during conceptualization of projects:-  

1. Recognize the Projects as Change Agents 

While any Project is a Temporary Organization with a definite beginning and a definite end, the outcome of projects are usually long lasting. It is observed that outcome of most of projects are expected to have a profound impact on beneficiary community or are expected to become an integral part of implementing organization. In many cases, projects and programs act as organizational strategy implementation tools and progress of projects give feedback on strategic decisions taken by organizations for business sustainability or business expansion. This means, successful implementation of projects are important for future prospects of organizations and more importantly, in a way, this means that projects (and/or programs) play critical role of effective Change Agents. 

A due considerations must be given to change agent aspect of a project. Not only, must a suitable change management plan be incorporated as a part of project plan, but it should also be ensured that change management plan gets executed to the extent that changes brought about by projects are well adapted for maximization of benefits of projects. 

In this regards, assessment of impact of project in larger perspective may be considered. Indirect impacts of project to society at large and relation of the project outcomes to other projects within different programs must be accounted in the project assessment metrics.
   
2. Harness Learning from the Project

New learning during implementation of a project is critical for trapping the drifts in business environment. Therefore, minute observation of the learning from a project and establishing suitable correlation with information available from other sources could lead to important inputs. Such inputs could be helpful in supporting sensible decision making (to the business strategists, program managers or organizational change managers). At times, these inputs also help in assessment of continuous organizational adaptability for possible challenges expected in future. This holds true for all the different organizations participating in execution of project even though the perspective with which the organizations look at the project may differ. Thus, a Project Designer should keep in mind that apart from fulfillment of objectives of the project, all the learning from the project should get thoroughly processed through the Knowledge Management Framework (of participating organizations) with an intent to enrich organizational understanding of changing business dynamics. 

3. Streamline Efforts made by Executing Partners

In large projects, different project responsibilities are shared with different executing partners. Each executing partner is usually bound to deliver product or services in accordance its obligation defined in contractual agreement. However, exactly who owns the onus to implement the project (Lead Executor) must be very clear to all the stakeholders. And keeping the Lead Executor at the center, the project governance model must be designed for establishing appropriate accountability and control during execution of the project. In the governance model, through suitable provisions, the Lead Executor must be made to be sensible in approach towards business interests of other executing partners. This organizes all the executing partners under a single umbrella and this also  increases mutual trust among the executing partners by reducing mutual frictions (among executing partners) when deviations in time-cost-quality triad is experienced during course of project execution impacting divergent business interests (of executing partners).   

The project should be able to function as an autonomous body and the Lead Executor should be able to exercise powers with authority to take decisions in the best interest of the project (of course, within the framework of project governance model and with suitable justification supported through facts and figures). Similarly, the project execution team should be adequately empowered to get the required resources from different stakeholders as a right. 

In certain cases, when the Lead Executor role is with government department or with an organization with bureaucratic culture, the executing partners of international repute having result oriented approach and commitment to best practices for quality delivery (of goods and services) struggle to work in synchronized manner. Such instances are observed with many e-Governance projects in India (and may be in many other developing countries). Mr. Narayan Murthy, co-founder of Indian Information Technology giant Infosys has once told “I know about Infosys there is not a single project Infosys has done and I believe the same story where the company has not lost money, that’s a reality, when dealing with the governments,”. (in an interview with representative form CNBC-TV18)

Probably, bureaucratic way of project management introduces culture of hierarchical subordination among executing partners and among professionals participating in the project. Hierarchy limits application of creativity in execution required for implementation of multi-disciplinary, multi-dimensional, multi-stakeholder, technology intensive and complex projects having huge sums of money at stake.   

4. Orient Project Team towards Successful Implementation of the Project 

Execution of project is a teamwork. Every member participating in the team must associate with sole intent to make the project successful. It may be noted that chances of success of the project is severely limited without team members establishing personal bonding through a sense of belonging with the project. Project is a temporary organization and professionals usually associate for a short term with the project. For professionals, the project is a means to contribute to the best of their abilities for the success of the project, to enhance their experience and skills by facing new challenges of different dimensions and to do networking with other professionals. 

But, more importantly, each professional assumes that working for the project will eventually contribute to strengthen the long term association with the organization, which has deputed her/him (parent organization) into the project. A fair and transparent mechanism to ensure that performance in the project will surely translate into the professionals’ long term association with her/his parent organization can make a difference.  

Therefore, irrespective of which executing partner, a team member belongs to, a well-defined reward and recognition mechanism linked to contribution in the project must be ensured in concurrence with parent organizations of the professionals. These rewards and recognition must translate to strengthening long term career prospects for each of the team member (may be better income, better stature, better location or better work-life balance). 

5. Ensure Professionals with Required Expertise Run the Project 

Domain experts having significant experience of contributing to similar projects are the best persons to plan, execute, monitor and control projects. It should be understood that application of project management tools and technologies or project management methodologies can be most appropriately done by the people who can really understand the environment and dynamics of work to be executed. Leaders having lack of technical depth fail to make timely and meaningful decisions contributing to success of project. Therefore, ensuring that skillful experts (with domain expertise, know-how on applied technologies, business understanding and project management experience) lead the project with thorough professionalism contributes towards successful project implementation. 



Photograph downloaded from www.us.fotolia.com (https://us.fotolia.com/id/95342356)

/************************/


Friday, November 13, 2015

Some Points to Consider for Writing an RFP (for e-Gov Projects)

(The article is written with respect to RFPs floated for e-Gov (e-Governance) projects by different governments in India; however, some of the points may be generic in nature and may be relevant in general)

The requested proposal in RFP (Request for Proposal) for e-Governance (e-Gov) projects (floated by different governments) are usually turn-key projects intended to improve governance. These projects are generally related to provisioning of delivery of services, automation of internal processes, enhancement of available IT Infrastructure (product or services) or development of MIS (Management Information System intended to enhance decision making). Usually, e-Gov projects are executed under Contractual PPP (Public Private Partnership) on BOOT (Build, Own, Operate and Transfer) model. Mostly, preferred model for selection of vendor through RFP is QCBS (Quality and Cost Based Selection).

Preparation of RFP is very important in tender management process for e-Gov projects. This is so, not only because RFP becomes basis for selection of best possible bidder to do the job (project(s)) but also because whatever is scoped in final RFP (the one released after pre-bid meetings including addendum to the one floated for the first time) usually becomes part of contract (after selection of successful bidder) with either no change or with a minimal changes. Technically this approach is reasonable and this may also be legally appropriate.

However, it is practically difficult to scope a project (with precision in terms of time-budget-quality) at the time of RFP preparation to executable precision. If an attempt is made to accommodate all the practicalities of execution in RFP, probably too much flexibility will need to be incorporated to scope and estimates (of the project) through introducing possible conditions (with corresponding controls) to be applied under future circumstances. This will make RFP complicated for clear understanding by responders and at the same time may induce greater risk of ambiguity for evaluators.

In this regards, it is mention worthy that many RFP experts suggest that when designing government projects, they find difficulty in developing thorough understanding (of the project dynamics) to minutest detail, which is usually required for conceiving large projects. Probably this is so, because of the complexity induced by diversity and volume government projects usually cater to. Things become much more challenging, when it comes to e-Governance projects, which involves fundamental change in way of doing things.

Further, it may be noted that contract is designed to remain static and therefore clauses are purposefully drafted to remain well defined to the best possible precision. But, it turns out, that neither projects (that too, complex projects with big budgets) remain static in nature (during execution) nor can corresponding estimates be expected to remain static throughout the life-cycle of the project. It is noteworthy that quite often Progressive Elaboration, reveals unprecedented circumstances before the project management. To respond to these situations, in the best interest of the project, project management has to resort to scope management. With contractual obligations closely tied to the scope of the project, corresponding contract management also needs to be carried out. Making changes to a contract (in which any government is a party) is very difficult and time taking. Also, vendors show resistance to changes in contract, especially when the changes in contract impact their financials in negative way (reduced contract amount).

Similarly, another related aspect is that contract insists on divided accountability (based on respective scope of contracting agencies – usually successful bidder and the organization, which floats the tender) but to meet the objectives of the project it is important for all the contracting parties to assume shared accountability and put joint efforts.

Thus, putting significant part of project details (taken from RFP) in contract would need flexible contract management to accommodate changing dynamics of any project. Project managers are (professionally) groomed to work strictly in the interest of the project they are undertaking and they are trained to be flexible in decision making (even if, this means taking deviations from contractual obligations). But, organizations (implementing the project) are more comfortable to see progress of project work in interest of contractual obligations (strict adherence to contractual obligations) and have huge resistance to initiate process to change the contract. Even though (as discussed above), these two interests (that of Project Managers and Organizations) seldom align (with expected precision) in practice, all the stakeholders want to see the final objectives of the project met within budget, well in time and with expected quality and most importantly without changing the contract (without taking into account how far the situation on ground has drifted away from what was conceived). This illustrates the dilemma of a project manager on one hand and on the other hand this is considered as one of the possible reasons e-Gov projects do not succeed to expected levels (when operating in usual working environment). Further, in a way, this also throws some light on success of the e-Gov projects, which are related to issues placed at the center of political spectrum in the state. For such projects, the criticality of outcome of the project prompts for quick and flexible decision making in the interest of project with reasonable justifications supporting the decisions. Therefore, in such projects, the project management is more empowered to act in the interest of the project (either at a permissible deviation from strict contractual obligations with suitable justifications in larger interest of the project or by getting contract changed according to needs of project).

In a nutshell, above discussions suggest that drafting an RFP could be one of the critical aspects to consider for success of e-Gov projects. Nevertheless, it is a big challenge to write an RFP that is flexible (with respect to assumptions), accommodative (with respect to changing project dynamics), precise (with respect to outcome), aligned (with respect to scope/objectives) and requires minimal monitoring and control throughout the life cycle of the project (as it is observed that mostly governments do not have human resource with appropriate skills required to enforce strict monitoring and control of technology intensive projects (like e-Governance)). The other challenge during execution of project (in accordance with RFP), is convincing the leadership of contracting parties to show flexibility towards contract management.   

With this discussions on RFP, contract management and project management, I will like to jot down some of the points, I feel are important to consider, when drafting RFP for e-Gov projects:-

1.      Link the Big Six for Clarity and for Coherence but with suitable provisions to accommodate Change Management

Mapping the following six critical aspects (of RFP) with adequate precision articulates the RFP to the prospective bidders with clarity required to strategize the best possible response:-  
Objective ßàScope ßà Deliverable ßà Acceptance ßà Payment ßà Penalty

Objective(s) – Drawing clear objective(s) with precise description of problem(s) is of prime importance. Elaborating expectation(s) and exception(s) from solution(s) helps design of Scope for RFP designer and at the same time helps respondents with design of A & M (approach & methodology). Abstract objectives may be avoided to the best possible extent.
Scope – Scope must be cleanly linked with objective(s) such that any alteration in objective(s) should make it possible to clearly alter scope (accordingly). Scope usually may not be altered in most cases, however a provision for logical scope management may turn out to be helpful.
In government projects, at times, the time gap between conceptualization and execution of project is quite big. Therefore, in some cases, it turns out that when project execution starts, some part of the objectives of the project is already met by some other related project either of the same department or some other department. In similar cases, objective or scope need to undergo changes to avoid duplication of work (and avoid unfruitful expenditure).

Deliverable(s) – Adequate number of deliverables should be clearly defined. Detailed description of features of every deliverable must be listed. Attempt should be made to map each and every deliverable to clause(s) in scope.

Acceptance Criteria for Deliverables – This is a complex aspect. Acceptance Criteria (whether confirming to end user expectations or the use cases or to technical specifications or to agreed service norms or other quality parameters related to product or services rendered) must take into account Cost, Time and Quality triad in some way. Assuming a reasonable approach towards accepting the deliverables with deviations on the above mentioned triad (with suitable justification) is at times found to be in larger interest of project. Charting out a suitable metrics for accommodating different types of deviations with no or with calculated impact on objectives of the project could be helpful.

Payment Terms – Payments are done against deliverables and penalty is imposed on amount to be payed (based on acceptance assessment of deliverables on acceptance criteria). Therefore, payment terms must be synchronized with corresponding deliverables on one hand and with penalty clauses on the other hand. If a vendor could get the payment on the day the deliverables are accepted (after suitable deductions of penalty – if any), this will close the part of project delivered for all parties.
In turn-key projects, a due consideration to capex (capital expenditure) and to opex (operational expenditure) from the point of view of vendor(s) could be considered. Significant part of capex is related to purchase of equipment (hardware). Making upfront payment for such purchases (of equipment) immediately after delivery, testing and installation could make the tender look lucrative for vendor community (resulting in increased interest in the tender). Therefore, where ever possible, higher percentage of payments could be considered to be made at earliest against capex.
Whenever deemed appropriate a suitable consideration to time value of money could be helpful. This could include provision to pay interest to vendor(s) against payment for services, in case of any procedural delay in making payment (to vendor) by the office taking services from vendor(s).   

Penalty Clauses – Penalty are assumed to work as a deterrent for vendor to abide with certain contractual terms of critical importance to the project. The idea of penalty also assumes that the all the possible ways things can go wrong in a project is attributed to avoidable mistakes committed by any vendor. This very assumption does not hold true most of the time. More so, for large projects with either prominent service components or projects dealing with the latest technologies. e-Gov projects usually have both characteristics, they have prominent service components and are technology intensive in nature. In my opinion, whether implemented or exempted, provisions of penalty seldom serves the purpose of being a deterrent or a supplementing factor to effective monitoring and control mechanism. It fails as a deterrent because mostly vendors (through their expertise and experience) are able to make out when do they have chances to fail in penalty clause(s) and therefore, they include penalty as a cost in the financials (financial section of RFP). Imposition of penalty are retrospective in nature and therefore cannot supplement monitoring and control during execution of project. Therefore, very judicious use of penalty should be considered and must be closely synchronized with payment terms for ease of operation.
   
2.      Maintain Flexibility in Estimates and Provisions – Estimates are based on assumptions. It could be helpful to mention the important assumptions with estimates of critical importance for giving implementers some flexibility to get the estimates revised, when the assumed conditions fail to hold true in due course of time. This is true for financial estimates as well as non-financial estimates.

Many times in implementation of e-Governance projects in developing countries, the technical specifications recommended in RFP (like – electronic interface devices (mobile phones, tablets), application servers, hardware equipment) are outdated (or are no more in supply in market) by the time project starts getting executed. Therefore, wherever possible, putting different types of standards (any equipment must comply with) in RFP instead of specification may make negotiation with vendors easier for making changes to proposed equipment.

Similarly, it may be good to have provisions for re-negotiation with vendors. The possible trigger for re-negotiation could be calculated deviations from assumptions critical to the project. Some experts believe that one of the reasons for PPP (Public Private Partnership) Failures in India is not initiating renegotiation on contracted terms pf partnership


3.      Draft a suitable Responsibility Matrix for stakeholders participating in execution – Once tender is awarded to a successful bidder, it (successful bidder) represents the implementing agency (vendor) for the project. But, it should be understood that for an external agency to do the job as critical as implementation of e-Governance project (which involves multi-level and multi-dimension co-ordination) is not possible unless all the stakeholders (internal and external) extend required support to the vendor. Therefore, vendor management team (of the office, which floats tender) must be well aware about the complexities of shared responsibilities (inter-weaving the dynamics of project) and must be adequately empowered to drive different stakeholders in the interest of the project. Leadership of vendor management team should ensure that their office owns the project and the vendor are one of the partners in the project.

A signed off responsibility matrix by the highest authority of the office of vendor management team can be helpful in making different stakeholders (including the vendor) more accountable towards their respective responsibilities towards the project.     

4.      Synchronize with varying Execution Speeds and Procedural Compulsions pertaining to various participating organizations - Extra care must be taken when defining timelines for deliverables (or activities) having dependencies on more than one organization. Mostly, different organizations have different work culture, different approach to projects and more importantly different priorities for a particular project in question. Thus, realistic execution velocity of projects requires accommodative approach for varying execution capabilities of various participating organizations.

5.      Try to make M & A (Methodology and Approach) a test of understanding of the project (by prospective Bidders) – M & A should be the one of the most critical aspect for bidders to show their understanding about the project, their domain expertise and their grip on required tools, technologies and methodologies.

Significant weightage must be given to a bidder for developing an in depth understanding of the environment and circumstances on which the project is going to operate, calculations related to risks and possible mitigation plans, understanding of project dynamics and stakeholder management.

Special attention must be given to maturity of tried and tested methodologies of the bidders and their ability of alter (customize) these methodologies in the context of the project they are bidding for. Similarly, extra effort put by the bidders for suggesting different alternatives or some innovative ways of doing things must be appropriately rewarded through bonus points.

But, all these evaluations must be through objective means (with minimal subjectivity in assessment) to the best possible extent. This may take a lot of time and multiple rounds of discussions with different stakeholders by the tender committee, but the effort may worth taking for truly executing the QCBS model of procurement.

It may be noted that M & A tests differentiation in the products and services of the prospective bidders for best suitability. Unless M & A is able to capture and express these differentiations through suitable variance in technical points given to the bidders, truly capable bidder may not get properly screened through the QCBS approach.   

6.      Choose Professional Skills or Choose Organizational Capabilities – In human resource intensive projects (projects requiring skilled workforce), usually, there are points (towards technical evaluation score) for deployment of suitable professionals. However, in my opinion, RFP writers should be very clear on whether they want to buy Professional Skills to be harnessed by project management team of the organization (which floats the RFP) or they want to buy services of a company for promised value addition as per its brand.

Companies train their employees to utilize the intellectual capital (accumulated by these companies) through internal organizational process to deliver the promised product and services. So, if the project need organizational capabilities (demonstrated through services and products) from vendor, leaving the decision to select profile of resources to be deployed on project on vendors could be a better idea.

7.      Measureable Metric System for Monitoring & Control – Service Level Criteria (or any other Monitoring and Control mechanism) must be well defined and must be easily measured against a sensitive and representative indices. Optimal service level criteria, which make clear business sense in respect to the project, should be chosen.

8.      Simple Pre-Qualification Criteria – Pre-qualification criteria is a yardstick to allow companies to compete for any tender.  This means, though the qualification criteria must be specific and unambiguous, yet they must ensure a fair competition.

Many times relatively small players (may be SMEs (Small and Medium Enterprise) ) with equally good capability (with respect to requirements of the project) do not qualify in Pre-Qualification phase (of tendering process) due to criteria chosen for Pre-Qualification relating to past performances like (say) criteria related to company turnover or past experience of similar work. Therefore, so far as the prevalent practices/guidelines permit, every attempt should be made to accommodate every company capable to perform and willing to participate.
              
9.      Detailed Cost Calculations – The financials section requesting cost from bidders must be a very detailed, unambiguous and easy to understand for the bidders. Taxation for products and services must be cleanly outlined. Special considerations must be taken for components like transportation cost, mobilization cost, logistics cost, cost of office space (work-station) and administrative costs.

Thrust of financials in RFP must be towards value for money rather than bias towards lowest cost. Establishing value for money could be a very difficult task. It is believed that QCBS to some extent helps in ensuring value for money.

Many times some of the bidders, who are very keen to win projects go for aggressive bidding on financials. Such attempts may dilute the considerations for quality in the QCBS. Many experts believe that there should be some provisions to weed out such overtly aggressive bidders. In some of the countries (like UK), there are provisions for Tender Committee to request explanation for abnormally low tenders. And in such cases, if the Tender Committee finds that the evidence supplied does not satisfactorily explain the low price, they have right to reject the bid.
   

Reference:-
http://uk.practicallaw.com/2-386-8761?service=publicsector#a101987 


/********************************/