INTODUCTION

ABSTRACT Pharmaceutical Sales Force Automation (PSFA) is just not a mere user-friendly field force daily report-entry web package. The objective of PSFA is to help the Field Force to spend useful and much needed time and efforts in terms of generating the revenue and help most important support centers like sales admin/Pmt/hr/distribution and logistics to help the field force in-turn, to bring in an overall efficiency and effectiveness for the organization. No doubt, this will also enhance the ability of field force to study, understand and internalize the basics, purpose and results of their work and plan for the future. Daily reports of field forces are captured, stored and processed by the exclusive servers optimized for this application, and reports for analysis are generated. We can also facilitate in terms of customizing the application as per the need of the clients.

SCOPE OF PROJECT PSFA e-vantage is a revolutionary e-reporting package for Pharmaceutical Companies. The product has been designed and developed under the table guidance of professionals from Pharmacy industry, working in various departments like Sales & Marketing, Sales Administration, Distribution & Logistics, HR and Product Team. Thus, it serves as wholesome package, which integrates various departments under one roof, maintaining the smooth communication chain and exchange of information by a mere click of a button. This userfriendly application is hosted on an exclusive server optimized for this application features:

Entries Field Force: Plans, Daily Reports, and Requests etc. Entries Corporate Staffs: Targets, New Launches, News & Events, Input dispatches, Online CME and Quiz etc.

Reports Field Force: Various field related activity reports. Reports Corporate staffs: Various field related activity reports, Reports of entries done at H.O. executives.

On click customer support.

Pharmaceutical Sales Force Automation (PSFA) is just not a mere user-friendly field force daily report-entry web package. The objective of PSFA is to help the Field Force to spend useful and much needed time and efforts in terms of generating the revenue and help most important support centers like sales admin/Pmt/hr/distribution and logistics to help the field force in-turn, to bring in an overall efficiency and effectiveness for the organization. No doubt, this will also enhance the ability of field force to study, understand and internalize the basics, purpose and results of their work and plan for the future. PSFA is an amalgamation of Technical and Field expertise, hence the product designed is absolutely logic driven. Only after thoroughly understanding the functions of each department with respect to the support they extend to make the Field Force function to their fullest efficiency, e-vantage has been developed. Rather than being a mere web entity PSFA strives to provide wholesome solutions to their esteemed clients.

SYSTEM ANALYSIS

STUDY OF CURRENT SYSTEM Medical representatives, also known as medical or pharmaceutical sales representatives, market products for medical supply and pharmaceutical companies. They travel to hospitals, clinics, doctors' office and other health care facilities to distribute information about their company's products and convince health care professionals to use and prescribe their companies' medications and supplies. Medical representatives must make many cold calls to doctors who are not always willing to meet with them. As a result, medical representatives should have several key qualities to establish a successful career. Because medical representatives must make many cold sales calls to doctors' offices and other health care facilities, they should possess a great deal of self-confidence. They must believe that they can convince prospective customers of the quality of their products and demonstrate confidence in the products they sell. Medical representatives must also have enough selfconfidence to deal with the inevitable rejection that comes with failed sales calls.

PROBLEM AND WEAKNESS OF CURRENT SYSTEM First of all the main problem with the current system is that it is quite time consuming sometimes. It has long procedures to obtain the information. It does not provide all information regarding any query at a time. It has time limitation; individual has to apply within the working hours of an organization. In addition, current system does not have good security features regarding the organization.

FUNCTIONAL AND NON-FUNCTIONAL Requirements Specification: Requirements Specification adds further information to the requirements definition: Non- functional Requirements:
Product requirements:

Usability: The interface should use terms and concepts, which are from the experience of the people who will make most of the system. Efficiency: The system must provide easy and fast access without consuming cost. Reliability: User should be surprised by the behavior of the system and it should also provide meaningful feedback when errors occur so that user can recover. Functional Requirements: The only requirement is to automate the whole system as a good source of providing the reliable information to that the user so that he can get the maximum benefit of the services provided by the campus/organization.

FEASIBILITY STUDY The main aim of the feasibility study activity is to determine whether it would be financially and technically feasible to develop a project. The feasibility study activity involves the analysis of the problem and collection of all relevant information relating to the product such as the different data items which would be input to the system, the processing required to be carried out on these data, the output required to be produced by the system as well as the various constraints on the behavior of the system. During feasibility study most of the high-level architectural design decisions are made.
The collected data are analyzed to arrive at the following: An abstracted problem definition, which considers only the important requirements and ignores the rest.

 Formulation of different solutions strategies. Analysis of alternative solutions strategies to compare their benefits and shortcomings. This analysis usually requires making approximate estimates of the resources required, cost of development and development time for each of the options.

Operational Feasibility:
Proposed projects are beneficial only if they are turned into information system that will meet organizations operating requirements. This test of feasibility asks if the system will work when it is developed and installed. Are there any barriers to implementation? A few questions that may be of help to test the operational feasibility of a project are: 1. Is there sufficient support for the project from the management? From users? If the current system is well liked and used to extent that person will not able to see reason for a change, there may be resistance.

Ans: yes there is enough and more support and motivation from the management. The existing system has got series of limitation that has been mentioned in the earlier chapters.
2. Are current methods acceptable to the users? If they are not, users may welcome a change that will bring about a more operational and useful system. Ans: No the current methods are not completely acceptable to the users, which leaded to the requirement of the new enhanced software. 3. Have the users being involved in the planning and development of the project? Ans: yes, the users are completely engrossed in the planning and development of the project, at each stage the users gives the feedback to the developers as per their requirements.

Technical Feasibility: The technical issues usually raised during the feasibility stage of the investigation include these,
Does the necessary technology exist to do what it is suggested (and can be it required)? Are developers aware of these technologies? Are there technical guarantees of accuracy, reliability, is of access security? Can the system be expanded if developed?

Schedule Feasibility: Projects are initiated with a specific deadline. We need to evaluate whether the deadline are mandatory or desirable. Time is one of the critical factors in the development of any system and hence proper scheduling is very essential for the timely completion of a project. Financial and Economic Feasibility: A system that can be developed technically and that will be used if installed must still be a good investment for the organization. Financial benefits must equal or exceed the costs incurred to develop the system. Some of the questions that are generally raised are as follows, Is the organization having the suitable budget to develop the proposed system? How much profit can be earned from the system by the organization? Would it be cost-effective to develop the system or it is worthwhile to remain with current system?

FUNCTIONS OF SYSTEM
4.5.1 Use Case Diagrams:

Fig 4.1: Use case Diagram of Customer

Fig 4.2: Use case Diagram of MR

Fig 4.3: Use case Diagram of Assignee

4.6 DATA MODELING

4.6.1 E-R diagram:

Fig 4.4: E-R diagram

4.6.2 System Activity Activity diagram Conventions used in drawing the Activity Chart here, are given as below:

LOGIN

Yes

No

REGISTER

AS AN ENDUSER

AS AN ADMINISTRATORR

AS AN 3 ASSIGNEE

CHANGE PASSWORD

SUBMIT QUERIES

VIEW ANSWERED QUERIES

Fig 4.5: Activity Diagram for End-users

Fig 4.6: Activity Diagram for Facility-Head

CHANGE

VIEW NEW REQUEST

UPDATE REQUEST

Fig 4.7: Activity Diagram for Assignee

LOGOUT

4.7 FUNCTIONAL AND BEHAVIORAL MODELING

Dataflow Diagrams Data-flow design is concerned with designing a sequence of functional transformations that convert system inputs into the required outputs. The design is represented as data-flow diagrams. These diagrams illustrate how data flows through a system and how the output is derived from the input through a sequence of functional transformations. Data- flow diagrams are a useful and intuitive way of describing a system. They are normally understandable without special training, especially if control information is excluded. They show end-toend processing: that is, the flow of processing from when data enters the system to where it leaves the system can be traced. Conventions used in drawing the Data Flow Diagrams here, are given as below:

Process : Data Store : Entity : Data Flow :

4.7.1: Context Diagram

Fig 4.8: Context Diagram

4.7.2 0th Level DFD:

Admin login

Administrato r

Logi n

Check requests, assign requests to assignee

Informatio n

Reply

Assignee login

Assignee

Login

Request

Answer the requests, update, add, delete For Authorized User the requests.

Informatio n

Reply

Fig 4.9:0th Level DFD for End-user, Facility Head and Assignee

1st Level DFD:

Administrator User Id

Authe ntitcatio n

Password Check Status

Login_detail

View Queries submitte d By the users Assign the task to the assignee s.
Add, Delete Update, Solve queries.

Assignees

task

processedRequest

Fig 4.9: 1st Level DFD

4.8 MAIN MODULES OF NEW SYSTEM

Project work is divided in three modules namely: create request, authenticate request and solve request. In Create request module, request will be created by the students. Authenticate request module, in this module administrator will authenticate the assignees with the queries or requests submitted by the students/user. Solve request module, in this module Assignee will provide students/users with the appropriate solutions to their queries submitted.

4.9

SELECTION OF HARDWARE AND SOFTWARE AND

JUSTIFICATION
Introduction To .Net Platform:

Visual studio .Net is now built on top of the.net framework. This will be significant change from Visual Basic 6.0.The new .Net Framework takes application development to viewing the Internet as your new operating system. Your applications will no longer recognize hardware as a boundary limitation this is an evaluations of the Window DNA Model, this new frame work is built on open internet protocol for a Standardization interoperability between platform and programming language the New .Net framework also allows the creation of new types of applications. Applications will now run using the common Language Runtime (CLR).All .Net applications will use this same runtime environment, which allows your Visual Basic applications to run on equal ground with other languages. The CLR allows Visual basic to provide inheritance and free threading, whose absence created two glaring limitations to visual basic application. Visual basic.Net is object oriented. Every thing is now an object, and every object is inherited from standard base class. Another benefit of CLR is common type system. Which means that all programming Languages share the same types This greatly increases interoperability between Languages. The internet has entered a new phase. First it was used to display static Web Page as time change and the business requirement is increased. At that time the Business soon found that this did not help them significantly. Next, the internet has evolved to dynamic content and allowing electronic commerce. The next step is to move towards complete application running on the internet. Visual Basic.Net also promotes these new web applications. Web services allow objects to be located anywhere on the internet and to be called from any application across the internet ( no more trying to get DCOM configured). Of course, extending applications across the internet will increase security risks. The .Net Framework has many security features built-in to it to protect your applications. ASP.NET is one of the most popular languages for building scalable, Interactive web sites. Several of the highest traffic web sites on the internet employ ASP.NET.Prominent examples include the Home Shopping Network, MSN, and the Microsoft site itself. What is .NET? .NET is a revolutionary new platform, built on open internet protocol and standards with tools and services that meld computing and communication in new ways. The .NET Framework is just part of Microsofts overall .NET platform strategy. The framework is made up of the Common Language Runtime environment, Base Class Library, and higher-level frameworks such as ASP.NET and Windows Forms as shown in Figure 4.10.

Fig 4.10: .NET Framework The common language runtime (CLR) is the foundation that sits on top of the Windows operating system. The base class library is a set of hundreds of classes that are provided as part of the framework to help us build applications that will execute in the CLR. To make building applications even easier Microsoft provides some higher level frameworks like ASP.NET and Windows Forms that utilize and extend the functionality provided by the Base Class Library.ASP.NET greatly simplifies the building of Internet applications by using Web Forms and Web Services. Windows forms provide the ability to develop for the rich environment that the Windows platform provides.

ASP.NET:
ASP.NET is used to create programmable Web pages as part of web form applications. Not only can ASP.Net produce dynamic Web pages, but it can also tailor them to the browser being used by the user. Development in ASP.Net is much easier because it contains a wide range of object-oriented server-side controls ready for use in applications. ASP.Net actually supports four different types of control: HTML Server Controls

These are programmable HTML elements that are exposed to the server. HTML server controls expose an object model that maps very closely to the HTML elements that they render. Web Server controls These controls have more built-in features than HTML server controls. Web server controls include not only form-type controls, such as buttons and text boxes, but also special-purpose controls, such as calendar. Web server controls are more abstract than HTML server controls in their object model does not necessarily reflect HTML syntax. Validation controls These are controls that incorporate logic and that can be attached to an input control to test what the user enters. Some validation controls check for a required field, a specific value or pattern of characters, that a value falls within a specified range, and so on. User controls These are custom controls created as Web form pages. Web forms user controls can be embedded in other Web Forms pages and provide an easy way to create menus, reusable elements, toolbars. Asp.Net also implements an event-driven programming model that is very similar to the Visual FoxPro 7.0 so that custom code be attached to events and executed when the event Fires. Every times a web page(which is an object itself) is called, a series of stages are run through :initializing, processing and disposing of information. One key difference between the event sequence in asp.net and Visual Foxpro 7.0 is that the Page_Init event comes before page Load in Asp.Net. One of the greatest benefit of Asp.net over classic ASP is that Asp.Net reduce the amount of coding needed to write an application. With the introduction of server-side control, it is no longer necessary to write the complex HTML and scripts that were necessary to render the pages on different browser. In addition ASP.Net can automatically keep track of the state between Web Pages, without all the tedious programming necessary in classic Asp.net tests have shown that rendering pages using Asp.net is typically 2-3 times faster than using classic ASP.

ADVANTAGES: Separation of code from the content.Asp.Net allows the developer to separate script code from html. This allows for a clean Separation of code from content and formatting and promotes code reuse.

Executable portion of a Web application compiled so they execute more quickly than interpreted scripts.

 On-the-fly updates of deployed Web application without restarting the server. Access to the .NET Framework, which simplifies many aspects of windows programming. Use of the widely known visual basic programming language, which has been enhanced to fully support object oriented language. Automatic state Management for controls on Web page (called server controls) so that they behave much more like windows controls. The ability to create new customized server controls from existing controls. Built in security through the windows server or through other automatically /authorization methods. Integration with ADO.NET to provide database access and design tools from within Visual Studio.NET. Full supports for Extensible markup language (XML) cascading style sheets (CSS) and other new and establishment web standards. Built in feature for caching frequently requested web pages on the server, localizing content for specific language and culture, and detecting browser capabilities.
Support for compiled languages. While ASP.Net still supports the traditional set of scripting languages, support is also provided for fully compiled language, Instead of using vbscript the developer can use VB.NET and access features such as strong typing and object oriented programming.Asp.Net pages are precompiled to byte code and just in time compiled when first requested. Greater support for different browsers via server side controls and events. Following object oriented design principles, ASP.NET pages make use of server side controls called ASP.NET Web controls. These controls are instantiated on the server, and like regular objects they have associated methods, properties, and events. The advantage of the server side controls is that they render themselves on the client as standard HTML 3.2 (optionally DHTML), depending on the capabilities of the client browser.

SYSTEM DESIGN

5.1

DATA DICTIONARY

Register

Column Name First_name Last_name Gender User_id Password

Data Type
varchar(50) varchar(50) varchar(50)

Constraint Not null Not null

Description First name of user Last name of user

Integer
nvarchar(50)

Primary Key

Unique Data for every user Password

Retype_password nvarchar(50) Email_address Semester Address Mobile_no Dof_days Dof_months Year Username nvarchar(50) numeric(18,0) nvarchar(MAX) numeric(18,0)
nvarchar(50) nvarchar(50) nvarchar(50) nvarchar(50)

Not null

Conform password Email address of user Semester of the user Resident address of the user

Not null Not null Not null Not null

Date of birth Month of birth Year of birth Username for the login

Request

Column Name Request_id Request User_id

Data Type Integer

nvarchar(50)

Constraint Primary Key Not null Not null

Description Unique request number Query send by user Unique data for every user

Integer

Request_cat Time Solution

nvarchar(50)

Request category Actual time of sending request Solution of the query/request

Smalldatetime nvarchar(MAX )

AssigneePswd

Column Name Username Email_address Id Reset

Data Type nvarchar(50) nvarchar(50) Integer nvarchar(50)

Constraint Not null Not null Not null

Description User name User password

AdminLogin

Column Name Username Password User_id

Data Type nvarchar(50) nvarchar(50) Integer

Constraint Not null Not null Primary Key

Description User name User password

Months

Column Name Months

Data Type varchar(50)

Constraint Not null

Description Month

AssigneeLogin

Column Name

Data Type
varchar(50)

Constraint

Description First name of user

First_name Last_name Username Password Confirm_passwo rd Mobile_no Dof_days Dof_months Year Department User_id Email
varchar(50) nvarchar(50) nvarchar(50) nvarchar(50)

Last name of user Not null Not null Username for the login Password Confirm password

numeric(18,0)
nvarchar(50) nvarchar(50) nvarchar(50) varchar(50) Integer Not null

Date of birth Month of birth Year of birth Department name

nvarchar(50)

Email address of user

Category

Column Name Categories

Data Type nvarchar(50)

Constraint Primary key

Description Categories of the

ChangePswd

Column Name Old Password New Password Retype_password

Data Type nvarchar(50) nvarchar(50)

nvarchar(50)

Constraint Not null Not null Not null

Description Old password of user New password of user Conform password

Detail

Column Name User_name User_city User_telephonenumbe r User_email User_semester

Data Type
nvarchar(50) nvarchar(50) numeric(18,0) nvarchar(50) nvarchar(50)

Constraint

Description Name of the user City of the user Telephone number of the user Email id of the user Semester of the user

Feedback

Column Name First_name Last_namae Username comments

Data Type
varchar(50) varchar(50) nvarchar(50) nvarchar(50)

Constraint Not null

Description First name of the user Last name of the user

Not null Not null

Username of the user Comments given by the user

ForgotPswd

Column Name Username Email_address Id Reset

Data Type
nvarchar(50) nvarchar(50) Int nchar(10)

Constraint Not null

Description Username Email address of the user

Primary key Not null

of the user Comments given by the user

Login_Detail

Column Name User_id User_name Password

Data Type nvarchar(50) nvarchar(50)

nvarchar(50)

Constraint

Description User id Name of the user Password of the user

ProcessedRequest

Column Name Processrequest_id Request_id Assignee_id User_id Solution

Data Type Integer Integer Integer Integer nvarchar(MAX )

Constraint Primary Key Not null Not null Not null Not null

Description Unique processed request number Request number Assignee number User id Solution of the query/request

RequestArrivedForAssignee

Column Name Reqassignee_id Request_id User_id Department Assignee_name

Data Type Integer Integer Integer

nvarchar(50) nvarchar(50)

Constraint Primary Key Not null Not null Not null Not null

Description Unique number for the assignee for a particular request assign Request number Unique data for every user Department Name of assignee

5.2

Architectural Design

Following activities are necessary for architectural design process. 1) System Structuring The system is structured into number of principle sub-systems where a sub-system is independent software unit. 2) Control modeling A General model of the control relationships between the parts of the system is established. 3) Modular Decomposition Each identified sub-system is decomposed into modules. The architecture must Decide on the types of modules in their inter connections.

System Architecture
Request and Reply User Interface Information User Fig 5.1: System Architecture TESTING 7.1 TESTING PLAN

Management

Database

Software testing is the critical element of the software quality assurance and represents the ultimate review of specification, design, and code generation. Once the source code has been generated, software must be tested to uncover as many errors as possible before delivery to the users. This chapter describes some of the testing techniques for designing tests that Exercise the internal logic of the software components

Exercise the input and output domains of the program to uncover errors in program function, behavior and performance.

We carried out testing process in four stages as unit testing, module testing, subsystem testing and system testing.

The Testing Process

Unit Testing

Module Testing

Subsyste m Testing

System Testing Fig 7.1: Testing Process The software process activities such as Design, Implementation, and Requirement Engineering were tested. As the design errors are very costly to repair once system has started to operate. Therefore, it is quite obvious to repair them at early stage of the system. So analysis is the most important process of any project.

7.2

TESTING STRATEGY

Requirements Trace ability:

As most interested portion is whether the system is meeting its requirements or not, for that testing should be planned so that all requirements are individually tested. We checked the output of certain combination of inputs, which gives desirable results, or not. Strictly stick to the requirements specifications, gives the path to get desirable results from the system.

Tested Items: Tested items are like sending request to administrator, solving the sent request by the assignee, changing password of assignee and student, sending user feedback, adding new categories, adding new departments etc. Testing Schedule: Testing has been done for each procedure back-to-back so that errors and omissions can be found as early as possible. Once the system has been developed fully testing procedure is followed on other machines, which differs in configuration.

Software Testing involves executing an implementation of the software with test data and examining the outputs of the software and its operational behavior to check that it is performing as required.
7.3 TESTING METHODS:

Different testing techniques are as described below: Statistical Testing:

Statistical Testing is used to test the programs performance and reliability and to check how it works under operational conditions. Tests are designed to reflect the actual user inputs and their frequency.

The stages involved in the static analysis for this system are follows:
Defect Testing: Defect Testing is intended to find inconsistencies between a program and its specification. These inconsistencies are usually due to the program faults or defects. Black-box Testing: In Black-Box Testing or Functional Testing, the output of the module and software, is taken into consideration, i.e. whether the software gives proper output as per the requirements or not. In another words, this testing aim to test a program's behavior against it specification without making any reference to the internal structure of the program or the algorithms used. Therefore the source code is not needed, and so even purchased modules can be tested. The program just gets a certain input and its functionality is examined by observing the output. This can be done in the following way:

 Input Interface Processing Output Interface

The tested program gets certain inputs. Then the program does its job and generates a certain output, which is collected by a second interface. This result is then compared to the expected output, which has been determined before the test. White-box Testing:
White Box testing is used as an important primary testing approach. Here code is inspected to see what it does; tests are designed to exercise the code. Code is tested using code scripts, driver etc that are employed to directly interface with and drive the code.
The tester can analyze the code and use the knowledge about the structure of a component to derive the test data. White box testing methods like control testing, loop testing have been used to make the software of increased reliability. Structural Testing:

Path testing has been exercised i.e. every independent execution path through a component or program has been tested. If every independent path is executed then all Statements in the components must have been executed at least once. The structure of program has also been checked. Integration Testing: After the individual modules were tested out, the integration procedure is done to create a complete system. This integration process involves building the system and testing the resultant system for problems that arise from component interactions. The top-down strategy is applied to validate high-level components of a system before design and implementations have been completed. Because, the development process is started with high-level components and work is done down the component hierarchy. Performance Testing:
Performance testing is designed to test the runtime performance of the system within the context of the system. These tests were performed as module level as well as system level. Individual modules were tested for required performance. Condition Testing: Condition testing is a test case design method that exercises the logical conditions contained in a program module. If the condition is incorrect, or at least one part of the condition is incorrect. It may include

Boolean variable error Array Out Index Out of Bounds error String Index out of Bound error Null Pointer Assignment Input Output Connection Exception Parsing (conversion) errors

Arithmetic expression error

Interface Testing:

Interface testing is integral part of Integration testing. Therefore it is checked for the Interface misuse. Interface misunderstanding

The code to be tested is examined and explicitly lists each call to an external component. In the system, standards tests for GUIs have been performed, which are as follows.
The position and related labels for all controls were checked. All menu functions and sub functions were verified for correctness. Validations for all inputs were done. Each menu functions were tested, whether it invokes the corresponding functionality properly. Pull down controls was verified for proper functionality. Whether the non-editable text control is disabling and it was also verified that it doesnt exceed the maximum allowed length. Whether the system prompts the user with appropriate message as and when invalid information is entered. All required fields arent left blank Object Testing:

Object testing is to test objects as individual components, which are often larger than single functions. Here following activities have taken place.
Testing the individual operations associated with objects Testing individual object classes. Testing clusters of objects Testing the object-oriented system.

It is well said that testing never ends, it just get transferred from programmers to customers. Every time the customer uses the program, a test is being conducted. But developers have tried to test the software exhaustively and completely by using above-mentioned software testing techniques.

7.4 TEST CASES:

By definition, a test case is a set of data that the system will process as a normal input the philosophy behind testing is to find errors. We devised the test cases with this purpose in mind. Test Case 1: Purpose: The purpose of this test case is to find out whether the rendering functionality is working perfectly or not. Required Input: Request of any particular department. Expected Output: The output of the test case was that the required solution is fetched.

Test Case 2:
Purpose: The purpose of this test case is to check whether website is working properly when database is being manipulated by user. Required Input: It must have a website to deal complain along with requests. Expected Output: A Proper working solution along with all facility was found.

LIMITATION AND FUTURE ENHANCEMENT

LIMITATIONS:

Currently we have developed this project only for small scale organization like schools and colleges with limited number of resources and functionality, but with some modifications this project can also prove to be useful to Large-scale organizations with increased functionality. FUTURE ENHANCEMENT:

At present Online Help Desk has been developed in English language but it can be developed in any local language so that the persons using this system can have a greater involvement and ease of understanding the system. The project has been currently developed in ASP.NET with C#, but it can also be developed easily using any other platform as desired by the developer with his choice of the database.

CONCLUSION
Pharmaceutical Sales Force Automation (PSFA) is just not a mere user-friendly field force daily report-entry web package. The objective of PSFA is to help the Field Force to spend useful and much needed time and efforts in terms of generating the revenue and help most important support centers like sales admin/Pmt/hr/distribution and logistics to help the field force in-turn, to bring in an overall efficiency and effectiveness for the organization. No doubt, this will also enhance the ability of field force to study, understand and internalize the basics, purpose and results of their work and plan for the future.