Skip to content

Categories:

Enterprise risk evaluation and continuous mitigation using the fuzzy-multiattribute decision making'A conceptual

J. Indian Inst. Sci., Nov.'Dec. 2006, 86, 625'638

© Indian Institute of Science.

*Author for correspondence. System Integration, CMC Limited, Fourth Floor, 28, Camac Street, Kolkata

700 016, India.

Enterprise risk evaluation and continuous mitigation using

the fuzzy-multiattribute decision making'A conceptual

approach

NIRAJ KUMAR* AND K. R. SRIVATHSAN

Indian Institute of Information Technology and Management-Kerala, Park Center, Techno Park Campus,

Thiruvananthapuram 695 581, Kerala, India.

email: nirajkumariitkgp@gmail.com

Received on December 8, 2005; Revised on September 26, 2006, and October 17, 2006.

Abstract

Software development processes generally follow easily identifiable stages and become increasingly more challenging.

They differ from traditional manufacturing project stages in various ways, which make them very risky

and uncertain. Traditional software risk management practices are more focused on qualitative judgment and experiences;

however, with exponential growth in number and size, software companies require effective scientific

methodology for risk management. The main objective of this study is to increase the effectiveness of risk detection

and mitigation practices in the software development process. Another objective is to analyze these practices,

identify the areas for improvement, and develop a mechanism for their quantification. We also aim to identify the

processes, which cause problems and suggest strategy to eliminate or reduce the harmful effect of these processes

in minimum possible cost and time. Analytical hierarchy process and fuzzy set theory are suggested as effective

tools to achieve this objective.

Keywords: Risk management, AHP, fuzzy set theory, software engineering, CMM.

1. Introduction

Software development processes generally follow easily identifiable stages like project

planning, requirement definition, design, development, testing, integration, installation, acceptance

and support. However, they differ from traditional manufacturing project stages in

various ways. Firstly, we need to give time and cost estimates to the customers in advance

without actually knowing its exact nature, which make software projects very risky and uncertain.

Secondly, to judge the requirements in diverse domain areas with almost the same

set of manpower requires a lot of flexibility on the part of employees and management.

Then fast rate of changes in technologies, customer requirements, possibility of unexpected

number of employees leaving the organization make the task even more complicated. Integrating

the complete solution, implementing it in successful ways, and making the end-user

understand the software and changes in the traditional processes are all part of the software

development life cycle. More and more global companies are outsourcing their software

development projects to offshore software development destinations like India which are

626 NIRAJ KUMAR AND K. R. SRIVATHSAN

throwing new challenges in terms of requirements specifications, cultural differences, effective

communication, security of valuable information, more rigorous legal, governance and

compliance standards.

Because of challenges posed by software development risks many approaches have been

proposed to improve the development process. These approaches include various computeraided

software engineering (CASE) tools, enterprise project management tools, conceptual

tools like various quality, coding, process standards, models, and frameworks, and various

software engineering models like traditional waterfall and spiral model.

In some cases, modeling and design tools are widely used and include Rational Rose [1,

2], versioning control tools like CVS, various testing and bug-tracking tools like Bugzilla,

integrated development environment and automatic code generation tools like Visual Studio,

Jcreator, Dreamweaver and others. Requirements development and management have

always been critical in the implementation of software systems. Some automated tools are

also available to support requirements management. The use of these tools not only provides

support in the definition and tracing of requirements, but also opens the door to effective

use of metrics in characterizing and assessing testing. Metrics are important because of

the benefits associated with early detection and correction of problems with requirements

[3].

Enterprise project management tools are found to provide a wide range of functions.

Among these are scheduling, resource allocation, and cost estimating, budgeting, and collaborating.

It is important to note that these tools emphasize project performance relative to

resource consumption within a given set of time constraints (i.e. progress and dates). Some

of the popular enterprise project management tools include Welcome product suite, Microsoft

project 2002, Primavera P3e suite. While interest and investment in CASE and project

management tools are rising steadily, actual experiences with tools have exhibited more

ambiguity. There has been no systematic examination or formulation of the organizational

changes surrounding CASE tools [4]. The major challenge is to develop quality software in

a reliable and repeatable manner while improving productivity [5].

On the conceptual front all these challenges gradually led to development of capability

maturity model (CMM) and concept of 'Balanced Scorecard'. The concept of 'Balanced

Scorecard' [6] developed in the early 1990s by Kaplan and Norton represented an advance

in the field of measuring enterprise performance, providing a framework for companies to

evaluate both financial and 'non-financial', or 'extra-financial' measures such as quality,

customer and employee satisfaction. This framework was widely used for enterprise-level

planning, control and monitoring by software companies. However, it suffers from limitations

of over reliance on expert judgments for decision making.

CMM [7] was developed in the early 1990s by Carnegie Mellon's Software Engineering

Institute (SEI). Since then many versions of this model appeared and are widely accepted as

most rigorous and best standard by software industry throughout the world. What led to instant

success of this model is its ability to focus not only on external processes but also

provide a framework for continuous improvements of internal processes in the company.

ENTERPRISE RISK EVALUATION AND CONTINUOUS MITIGATION 627

Table I

Key process areas of CMM levels [7]

CMM Level 2 KPAs CMM Level 3 KPAs CMM Level 4 KPAs CMM Level 5 KPAs

Requirements management Requirement development,

Technical solution,

product integration

Quantitative process

management

Defect prevention

Software project planning Verification, validation Software quality

management

Technology change

management

Software project monitoring

and control

Organization process

definition and focus

X Process change

management

Supplier agreement

management

Integrated software

management

X Continous improvement

and optimization

Measurement and analysis Organizational training,

integrated project

management

X X

Software configuration

management

Risk management,

integrated teaming

X X

Process and product quality

assurance

Integrated supplier

management, decision

analysis and resolution,

integrated supplier management,

integrated teaming

X X

The CMM establishes an yardstick against which it is possible to judge, in a repeatable

way, the maturity of an organization’s software process and compare it to the state of the

practice of the industry. The CMM can also be used by an organization to plan improvements

to its software development processes.

However, implementing the CMM framework is a very challenging problem for three

fundamental reasons. First is the issue of recognizing all input/output parameters in real

time, which influence various key process areas. Second, methodologies for quantification,

optimization, and continuous improvement of these processes are vague. Third is the issue

of synchronization of these processes with overall organizational objectives, profitability,

efficiency, and growth.

Our primary focus in this study is to develop a model to analyze risk management (CMM

level 3), quality management (CMM level 4), quantification of processes (CMM level 4),

and defect prevention, continuous improvement and optimization (CMM level 5). Then

based on analysis we also suggest improvement into various processes, which should be

cost effective and suited for particular organization culture.

Software development process analysis is an important first step towards making the

process more efficient and profitable. However, analysis is difficult not only due to its

complex nature because of large number of subsystems involved and dynamic interaction

and influence of one over another, but also because it is difficult to quantify their contribution

and influence on the software development process as a whole. For example, technical

expertise of manpower and quality of software developed are two important factors affect628

NIRAJ KUMAR AND K. R. SRIVATHSAN

ing any software company. However, technical expertise in itself can play an important role

in the quality of software delivered, at the same time it may also lead to cost and time overrun,

which may have negative consequences for the project. Similarly, the quality of software

also depends upon the processes adopted for quality control and on the amount of time

and funds available for the project. Also, the resources of an enterprise are limited so not all

sources of risk can be immediately eliminated and priorities need to be established. Studying

the various processes of a software development life cycle and measuring their impact

in quantitative terms is one of the important objectives of this study. Again identification of

key sources of risk and the ability to measure the level of its harmfulness on the system as a

whole is another important objective of this study. In this paper, various risk sources for a

software enterprise have been identified and a new approach based on analytical hierarchy

process [8] and fuzzy set theory [9'11] has been suggested as effective tool for enterprise

risk evaluation and continuous mitigation.

2. Literature review

Many researchers have tackled problems related to software development processes, practices

and tools, multicriteria and multiattribute decision-making, risk management and

fuzzy set theory.

Wiegers [12] points out unstated expectations as major source of software project failure

which can lead to erroneous assumptions, unfulfilled dependencies, unexpected risks and

disappointed customers. He emphasizes the importance of documenting the requirements

thoroughly, precisely and without ambiguity. Mall [13] gives an overview of software engineering

practices and covers almost every aspect of software engineering in brief.

Ming and Smidts [14] deal with ranking of software engineering measures based on expert

opinion. Over reliance on expert opinion is a major limitation of this study. These theories,

methodologies and tools need to be subjected to rigorous test of practices to live up to

their perceived expectations and promises.

Many methodologies are available [9, 10] in the literature for multicriteria and multiattribute

decision-making including data envelopment analysis [15], analytical hierarchy

process [16], multiattribute utility theory [17], and Bayesian analysis and outranking methods

[19]. The AHP, designed to solve complex problems of multiple criteria involving both

qualitative and quantitative parameters, was proposed by Saaty in early 1970s. The application

of AHP is based on four basic principles, namely, decomposition, prioritization, synthesis

and consistency. Among others, Rong et al. [20], Hafeez et al. [21], and Kumar et al.

[22] have demonstrated the effectiveness of AHP to solve real-life industrial problems.

Kumar and colleagues [23'25] have tackled the problem of enterprise-level planning and

control with multiple criteria which include parameters like capacity, productivity, profitability,

environment and safety involving a number of decision-making units (DMUs).

The acceptance of term risk is universal and it penetrates every discipline of the society.

Each discipline visualizes risk in its own understanding. The concept of risk management

varies from macro to micro level. Several authors have highlighted the objectives of establishing

risk assessment and mitigation process [26, 27]. However, due to the dynamic nature

of interaction between various risk sources understanding of their relationship is

ENTERPRISE RISK EVALUATION AND CONTINUOUS MITIGATION 629

imprecise which can be equated with fuzziness. Further, they require far more detailed description

than is usually available for analysis. Application of the fuzzy set theory is an effective

tool to handle these kinds of real-life situations.

The theory of fuzzy set proposed by Zadeh [11] provides a strict mathematical framework

in which vague conceptual phenomena can be precisely and rigorously studied. It has

led to a paradigm shift in the way problems are solved in various disciplines. It can also be

considered as a modeling language well suited for situations in which fuzzy relations, criteria

and phenomena exist.

3. Risk management?A must for every software enterprise

Most software development projects fail to deliver acceptable systems on time and within

budget. Many studies were conducted to study software project failure rate at global level

including the Conference Board Survey 2001. Their key findings suggest that 40% of software

projects failed to achieve their business case within one year of going live and project

costs were found to be on average 25% over budget from the original estimates. Traditionally,

user requirements, inadequate user documentation, excessive schedule pressure,

low quality, low user satisfaction, cost overruns were considered some of the major risk

sources for software projects. However, increasing concern over security, legal problems,

rising cost of software development, and HR-related problems necessitates that these factors

should also be taken into account in risk management [4, 7, 18].

Much of the failure could be avoided by managers proactively planning for dealing with

risk factors rather than waiting for problems to occur and then trying to react. Usually, this

reaction is too little and too late, because by the time the problem is fully recognized, the

schedule has already slipped, a considerable investment has been made, and the product

quality has suffered due to introduction of errors or workaround. Risk management is an

important tool to provide insight into potential problem areas and to identify, address, and

eliminate them before they derail the project. Software risk management is important because

it helps avoid disasters, rework, and overkill, but more importantly because it stimulates

win'win situations [3]. A typical risk assessment and mitigation system may follow

the following cycle (Fig. 1):

Typical internal and external factors causing risk in the software industry include the following:

(i) Improper planning: Uncertain requirement, unprecedented efforts?estimates unavailable,

infeasible design, unavailable technology, unrealistic schedule estimates or allocation,

lack of flexibility in planning process.

(ii) Inventory-related problems: Uncertain or inadequate subcontractor capability, uncertain

or inadequate vendor capability, poor quality of software/hardware supplied, excessive

inventory level.

(iii) HR-related problems: Inadequate staffing and skills, lack of match between employee

skill sets and project requirements, improper and rigid hiring policy, inconsistency in employee

perception level, improper method of employee performance evaluation, conflict between

employee and top management, short-term goal and local optimization, preference to

self interest over organization interest, improper training program.

630 NIRAJ KUMAR AND K. R. SRIVATHSAN

Sources of external and

internal risk in an enterprise

Risk identification Risk analysis and

prioritization Risk mitigation

New risk sources

Mitigated and

redundant risk

sources

FIG. 1. A typical risk assessment and mitigation system.

(iv) Customer-related problems: Risk from product rejection by the customer, risk from

change in customer requirements, risk from project not delivered on time, risk from improper

understanding of customer requirements, risk of losing other opportunities due to

lack of customer satisfaction.

(v) Security-related problems: Risk from lack of technology for security handling, reactive

approach of security in place of proactive approach, misapplication of scarce security

resources, ineffective security goal setting, measurement, and achievement, misalignment

between security goals and organizational drivers, risk due to theft or loss of valuable information

due to security-related problems, risk from high cost of security management.

(vi) Quality-related problems: Poor product performance, lack of additional features, poor

reliability of the product, nonconformance with specifications, lack of durability of product,

lack of serviceability, lack of aesthetics, perceived quality of the product, lack of security

features, lack of customer focus, faulty tool and techniques used for quality measurement,

ease of training by the end-user, ability to integrate with legacy system of the customer,

methodology of software engineering measures (bugs per line of code, code defect density,

design defect density, failure rate, function point analysis, man hours per major defect detected,

mean time to failure, requirement compliance, requirements specification change request,

requirement traceability).

(vii) Communication-related problems: Risk due to delay in decision-making process,

risk due to delay in information transfer, risk due to distortion of information, risk due to

lack of proper communication between customer and team members.

(viii) Miscellaneous problems: Risk from fast technological change, risk from political

uncertainty and government policy change, risk from lack of R&D effort and culture in the

organization, ineffective utilization of available resources, financial risk, risk from recession

from world economy, risk due to lack of overall system optimization, risk from foreign

ENTERPRISE RISK EVALUATION AND CONTINUOUS MITIGATION 631

exchange fluctuations, risk from increasing software development cost, risk from litigation

expense.

All the factors listed above are important sources of risk in the software industry. It is

also important to understand that some of these sources are critical and their impact is profound

across various processes of software development. Proper evaluation of all these factors

and identification of key risk sources and subsequently their reduction or elimination

with minimum cost and resources is necessary to make system more efficient and profitable

and to gain competitive advantage in the market.

4. Proposed methodology

Methodology to be adopted for this study is four fold?first to identify the major risk factors,

then able to quantify most of them, prioritize the factors based on their potential for

causing risk to the organization and finally developing a general-purpose risk management

software. These four stages can be summarized as

Identification of the various sources of risk in the organization

Quantification of these sources and estimation of their effect on the software development

system as a whole.

Prioritization of these sources according to their effect and importance in causing harm

to the organization. Then, suggesting means to their elimination or reduction according

to practical feasibility and requirement of the management.

Development of a general-purpose software, which by giving suitable input, will be

able to quantify and prioritise various risk sources. Also, it will be able to give estimates

about how much elimination of any particular risk source expected to benefit the management

and how much cost it is likely to incur.

The proposed methodology can be implemented as follows:

4.1. Identification and quantification of key risk sources

The constraints of time and cost make it impossible to eliminate all forms of risk in any enterprise,

so an effective way to eliminate key sources of risk and continuous improvement

of risk control process is required. Identifying and quantifying the key sources of risk that

should be eliminated is an important first step towards achieving this. Figure 2 displays

various potential risk sources identified and classified for a typical software enterprise.

Then harmfulness of each type of risk on the system as a whole is proposed to be determined.

Some factors like risk from project rejection by customers, risk due to theft or loss of

valuable information, risk from high cost of security management, risk from excessive inventory

level, financial risk, risk from currency fluctuations, risk from increasing software

development cost are relatively easy to quantify and estimate in monetary terms and their

harmfulness on the system as a whole can be determined. For example, consider risk due to

security-related problems. The cost of security-related problems on a software enterprise

are a function of fixed and variable costs. Fixed costs include those costs that are independ632

NIRAJ KUMAR AND K. R. SRIVATHSAN

Uncertain requirement, unprecedented efforts

Risk due to improper Infeasible design, unavailable technology

planning Unrealistic schedule estimates or allocation

Lack of flexibility in planning process

Risk from lack of technology for security handling

Risk due to Reactive approach of security

security- Misapplication of scarce security resources

related problems Ineffective security goal setting

Mismatch between security and organizational goal

Risk due to loss/theft of information

Risk due to additional expenditure on security management

Risk due to Risk due to delay in information transfer

communication- Risk due to delay in decision-making process

related problems Risk due to distortion of information

Risk from increasing litigation cost

Risk from fast technological change

Risk in Risk from increasing software development cost

S/W Risk from currency fluctuations

development Miscellaneous Risk from lack of R&D effort

problems Ineffective utilization of available resources

Poor product performance, lack of additional features

Nonconformance with the specifications

Risk due to Poor reliability and durability of the product

quality-related Lack of serviceability, lack of aesthetics

problems Perceived quality and lack of customer focus

Software engineering measures

Inadequate staffing and skills

Risk due to Improper and rigid hiring policy

HR-related Conflict between employees and top management

problems Mismatch between skill sets and project requirements

Inconsistency in employee perception level

Risk from product rejection by the customer

Risk due to customer- Risk from change in customer requirements

related problems Risk of losing opportunities due to customer dissatisfaction

Excessive inventory level

Risk due to inventory- Uncertain or inadequate subcontractor capability

related problems Uncertain or inadequate vendor capability

Poor quality of software/hardware supplied

FIG. 2. Risk identification and breakdown structure for software development process.

ent of the software developed like cost of maintaining firewalls, gateways, etc. These costs

can result in increased capital and operating costs for software enterprise. Variable costs are

those that vary directly with the software developed. Methodology that examines the cost

impact of security-related problems can be based on crude estimates of the order of magnitude

of fixed and variable costs. For this, reliability analysis of failure due to securityrelated

problems is done and hazard function is determined.

Then cost model of security-related problems on software system can be given as:

Td [ ( )]

GRPC FC VC MTTR

MTBF

= × + ×

ENTERPRISE RISK EVALUATION AND CONTINUOUS MITIGATION 633

where,

GPRC: Security-related problem costs;

Td: Designed scheduled operating life;

MTBF: Mean time between failures;

FC: Fixed cost for a single security-related failure;

VC: Variable costs for a single security-related failure per man days of down time;

MTTR: Mean time to repair the subsystem and bring it to its designed capacity.

Similar reliability models for other kinds of failure can be developed and their impact in

the monetary term can be calculated.

Some other factors like lack of flexibility in planning process, risk from project not delivered

on time, traditional software engineering measures, efforts estimate, various quality

and reliability metrics, project schedule estimates have a number of empirical and analytical

models which can be correlated with monetary gain or loss. Other factors are harder to

quantify and innovative and focused research is required to quantify them in monetary term

or judge their impact on the system as a whole. Expert judgment can be used as alternative

option if no other suitable quantification model is feasible. Our literature review revealed

that any of the present-day software engineering or quantification model is far below the

level of challenges posed by the requirement of such a system.

Not all sources of risk are key sources. By key sources is meant the sources of most

harmful types of risk that arise within software development process and those that are

likely to cause other forms of risk and waste, that is those that are strongly correlated with

the generation of other forms of risk and waste and whose elimination will suppress the

generation of the strongly correlated forms of risk and waste. The risk due to different

sources dynamically interacts with each other, but poor quality of information and vague

benchmarks make it difficult to determine the degree of correlation. Hence, the various

sources of risk are not easily evaluated and summarized into key risk sources. Understanding

of the relations between the forms of risk is thus imprecise, which can be equated with

fuzziness. To a great extent, software development process evaluation problem is a fuzzy

unstructured decision problem.

To analyze the fuzzy relations among various risk types and identify the key sources of

risk, the AHP and fuzzy set theory are proposed as effective tools. The proposed method

consists of three steps: evaluating, clustering and ranking. First, a risk evaluation index system

is established through the AHP to systematically measure the harmfulness of each risk

source to determine which are most harmful. Here, attempts are being made to quantify the

important source of risk and where quantification is not possible based on expert judgement

decision is taken.

4.2. Clustering

After evaluation of software development process and identification of the various forms of

risk and its degree of harmfulness, fuzzy clustering is used to cluster more harmful forms of

risk on the basis of their fuzzy correlation and categorize the various risk sources into key

634 NIRAJ KUMAR AND K. R. SRIVATHSAN

risk sources (Fig. 3). Expert grading method is used to estimate the correlation between objects.

The correlation between two risk sources is (0, 1). The bigger the number, the

stronger the correlation is. After generating tolerance matrix and transforming it into fuzzy

equivalence matrix, more harmful sources of risk that are strongly correlated can be clustered

into a single risk source. This stage is likely to bring down the number of unmanageable

risk sources into manageable few.

4.3. Ranking

The priorities by which key forms of risk should be eliminated are ranked based on the following

important principles:

Overall optimization of the software development process

Consistency with the software enterprise development strategy

Consistency with corporate technology level

Consistency with skill set of the employees and management

Its cost on the software company and time period required for improvement (shorter the

better)

Best quality product development and customer satisfaction

Efficient use of various inputs going into software development process.

In the ranking process, first the primary elimination measure for each key risk source is

determined. By evaluating these measures with regard to enterprise conditions, the key risk

source to be eliminated can be decided and this will correspond to the most appropriate

measures for the enterprise optimization process. Fuzzy comprehensive evaluation can be

used for this purpose.

Based on the analysis results important risk sources are analyzed closely and improvement

measure is proposed to be selected after which the benefits in terms of efficiency and

profitability of software development process can be determined.

As seen from the flow diagram of Fig. 3, if the previous three stages are followed and

appropriate elimination plan is implemented in focused manner, harmfulness from this

particular key risk source is likely to be eliminated or considerably reduced. It should be

monitored on a continous basis and all steps are repeated to find the next potential key risk

sources. All these steps are repeated till risk factors from all key sources are eliminated or

considerably reduced. In due course, many of the above-mentioned risk sources are likely to

be nonexistent or irrelevent, while many new ones can arise and should be included in the

model, which may be different for a particualar enterprise.

4.4. Development of computer software for risk evaluation and quantification

User-friendly computer software can be developed, which can quantify, cluster and rank the

various sources of risk by giving suitable input. Accordingly, management will be able to

generate useful information for elimination of risk sources and their effect on the software

development process.

ENTERPRISE RISK EVALUATION AND CONTINUOUS MITIGATION 635

Choosing the

most harmful forms

of risk sources

Identifying and classifying all forms of risk in software process

Evaluating the harmfulness of each type of risk

Clustering to identify the key sources of risk (Fuzzy clustering)

Dynamic

recycling for

total risk

Determining the primary elimination measure for each key risk source elimination

Ranking the key risk sources (Fuzzy comprehensive evaluation)

Identifying the eliminated object'the most harmful key risk source

Making systematic plan to eliminate this key risk source

Yes

No

FIG. 3. Flow diagram of software risk-evaluation system [modified from [8]].

5. Model validation and tool development

Validation and implementation of the model to the scale, which is required for this kind of

research, is yet to be fully realized. However, preliminary attempt of its validation based on

information collected from a middle-level consultant of a fast-growing CMM-level 5 company

has been done. This company is situated at Technopark, Thiruvananthapuram, and it

relies on audits, reviews and testing for risk and quality management. However, no specific

information regarding quantification of quality and customer satisfaction level has been

provided.

Based on information, which is related with breakdown structure for software enterprise

in Fig. 2, data was collected in April 2005, which identifies two most important risk sources

636 NIRAJ KUMAR AND K. R. SRIVATHSAN

Table II

Two most important risk sources as identified by model validation

Category Two most important risk sources

Improper planning �� Uncertain requirements

�� Estimates unavailable

Customer-related problems �� Risk from change in customer requirements

�� Product rejection by the customer

Security-related problems �� Reactive approach of security

�� Risk due to loss of valuable information

Quality-related problems �� Nonconformance with specifications

�� Poor product performance

Miscellaneous problems �� Ineffective utilization of available resources

�� Risk from lack of R&D culture

Overall �� Customer-related problems

�� Miscellaneous problems

in each category (Table II). However, these results are not conclusive, as the authors did not

verify practices and processes of the company.

A web-based system for risk evaluation, quantification and multicriteria decision-making

using Java-based technologies (JSP/Servlets), Mysql database and Apache tomcat application

server were already started (see Fig. 4 for screenshot of one such interface) and plan to

make it available in public domain after its completion.

6. Conclusion

Enterprise risk management is one of the most important strategic business tools to manage

effectively a variety of risks to gain competitive advantage and add value to the firm. This

FIG. 4. Web-based interface for enterprise risk evaluation.

ENTERPRISE RISK EVALUATION AND CONTINUOUS MITIGATION 637

study has identified the various external and internal risk sources in a software enterprise.

Authors have proposed a scientific model based on AHP and fuzzy set theory to prioritize

various risk sources and developed a framework for their continuous elimination by adopting

enterprise-specific strategy. The paper also emphasizes the dynamic interactions between

these factors and their suggested importance, quantification to judge the impact on

software enterprise as a whole. This model is highly flexible and customizable according to

specific enterprise need. Fuzzy clustering is proposed to cluster risk factors, which are

closely correlated to each other and are likely to have common source of problems to enable

their effective mitigation. However, quantifying (preferably in monetary terms) various risk

sources and improvements required for their effective mitigation can be some of the potential

directions in which this work can be extended.

Based on preliminary attempt of model validation with a CMM level-5 company it can be

said that uncertain requirements, change in requirements, reactive approach of security,

nonconformance with specifications and ineffective utilization of available resources are

some of the major risk sources for this enterprise. Software enterprises can apply this new

approach in their project and enterprise risk management to improve efficiency, performance,

profitability and to meet rising enterprise management challenges.

Acknowledgements

The authors would like to acknowledge Prof. Ashis Bhattacherjee, Department of Mining

Engineering, Indian Institute of Technology, Kharagpur, and anonymous reviewers for their

invaluable suggestions and encouragement. Thanks are also due to Mr K. Sreenivasa Rao,

Assistant Editor, Journal of the Indian Institute of Science, Bangalore for his efforts and

suggestions for improvements in the manuscript and in the presentation of the paper. They

also would like to thank Mr Amrendra Kumar, Department of Mining Engineering, Indian

Institute of Technology, Kharagpur, and Dr Abhiram Verma, Department of Mining Engineering,

B. E. College, Sibpur, West Bengal, for their help in the presentation of this paper.

References

1. Object Management Group, http://www.omg.org/gettingstarted/what is uml.htm

2. Rational Software Corporation, http://www.ibm.com/developerworks/rational/library/253.html

3. Rosenberg Linda, Hammer Theodore, and Gallo Albert, Continuous risk management at NASA, Applied

Software Measurement/Software Management Conf., San Jose, California (1999).

4. Orlikowaski Wanda, CASE tools as organizational change: Investigating incremental and radical changes in

systems development, MIS Q., 17, 309'340 (1993).

5. Menendez Jose, The software factory: Integrating case technologies to improve productivity, Report LEAN,

Center for Technology, Policy, and Industrial Development, Massachusetts Institute of Technology, p. 84

(1996).

6. The Balance score card, http://www.balancedscorecard.org/

7. Software Engineering Institute, www.sei.cmu.edu/sei-home.html.

8. T. L. Saaty, The analytical hierarchy process, McGraw-Hill (1980).

9. L. A. Zadeh, Fuzzy sets, Inf. Control, 8, 338'353 (1965).

10. H. J. Zimmermann, Fuzzy set theory and its applications, Kluwer, pp. 241'260 (1991).

638 NIRAJ KUMAR AND K. R. SRIVATHSAN

11. S. Osman Mohammed, Omar M. Saad and Ali A. Yahia, A fuzzy interactive approach to generate a finite set

of efficient solutions for multi-objective programming problems with their degree of efficiency, J. Fuzzy

Math., 8, 745'752 (2000).

12. Karl Weigers, See you in court, Process Impact, p. 6 (2003).

13. Rajib Mall, Fundamentals of software engineering, Prentice-Hall of India (1999).

14. Li Ming, and Carol S. Smidts, A ranking of software engineering measures based on expert opinion, IEEE

Trans. Software Engng, 29, 811'824 (2003).

15. A. Charnes, W. W. Cooper, and E. Rhodes, Measuring efficiency of decision making units, Eur. J. Op. Res.,

2, 429'444 (1978).

16. Z. Sinuany-Stern, A. Mchrez, and Y. Hadad, An AHP/DEA methodology for ranking decision making units,

Int. Trans. Op. Res., 7, 109'124 (2000).

17. R. L. Keeney, and H. Raffia, Decisions with multiple objectives: Preferences and value tradeoffs, Wiley

(1976).

18. Thomas Bayes, An essay towards solving a problem in the doctrine of chances, Phil. Trans. R. Soc., 53,

370'418 (1763).

19. B. Roy, How outranking relation helps multiple criteria decision making, in Multiple criteria decision making

(J. L. Cochrane and M. Eeny, eds), University of South Carolina Press, Columbia, SC, USA, pp. 179'

201 (1973).

20. C. Rong, K. Takahashi, and J. Wang, Enterprise waste evaluation using the analytic hierarchy process and

fuzzy set theory, Int. J. Prod. Plann. Control, 14, 90'103 (2003).

21. K. Hafeez, Y. Zhang, and Malak Naila, Determining key capabilities of a firm using analytical hierarchy

process, Int. J. Prod. Econ., 76, 39'51 (2002).

22. N. Kumar, A. Bhattacherjee, D. Chakravarty, and D. Sarkar, Efficiency measurement of mines using DEA

and AHP, TAMSEM, Int. Conf. on Technology Management for Sustainable Exploitation of Minerals and

Natural Resources, Indian Institute of Technology, Kharagpur, India, February 5'7, 2004 (2004).

23. Niraj Kumar, Assessment of performance appraisal for mines using data envelopment analysis and fuzzy set

theory'A case study from coal mining, M.Tech. Thesis, Department of Mining Engineering, Indian Institute

of Technology, Kharagpur, India (2002).

24. N. Kumar, A. Bhattacherjee, and D. Sarkar, Performance appraisal of coal mines using data envelopment

analysis and fuzzy set theory, Mintech, 23, 18'25 (2002).

25. Debasish Sarkar, Ashis Bhattacherjee, and Niraj Kumar, Performance evaluation of underground coal mines:

A case study, 19th World Mining Congress, New Delhi, pp. 917'928 (2003).

26. Jootar Jay, A risk dynamic model of complex system development, Ph.D. Thesis, Massachusetts Institute of

Technology, p. 204 (2002).

27. V. Carr, and J. H. M. Tar, A fuzzy approach to construction project risk assessment and analysis: construction

project risk management system, Adv. Software Engng, 32, 847'857 (2001).

Posted in Software.

No comments



My recently published paper in IISc journal

Please click on the link to read my recent published work
http://journal.library.iisc.ernet.in/vol200606/paper5/625.PDF

Posted in Software.

No comments



Enterprise risk evaluation and continuous mitigation using the Fuzzy-Multi-attribute decision making ' A conceptual approach

Enterprise risk evaluation and continuous mitigation using the Fuzzy-Multi-attribute decision making ' A conceptual approach

                                        BY
                                 Niraj Kumar    

                               IT Engg (T), System Integration
                               Kolkata ' 700016.

                                West Bengal, India

                 E-mail: nirajkumariitkgp@gmail.com

              Contact No:

© 2006 Niraj Kumar. All rights reserved            

                                  Abstract

 Software development processes generally follows easily identifiable stages and become increasingly more challenging.  It differs from traditional manufacturing project stages in various ways which makes them very risky and uncertain. Traditional software risk management practices are more focused towards qualitative judgment and experiences; however with exponential growth in the size of the software companies and complexity of projects require effective scientific methodology for risk management.  The main objective of this study is to increase the effectiveness of risk detection and mitigation practices in the software development process.  Another objective is to analyze these practices, identify the areas for improvements, and develop a mechanism for their quantification.  We also aim to identify the processes which are causing most of the problems and suggest strategy to eliminate or reduce the harmful effect of these processes in minimum possible cost and time. Analytical Hierarchy Process and Fuzzy set theory were suggested as effective tool to achieve this objective.

Key words: Risk Management, AHP, Fuzzy Set Theory, Software Engineering, CMM.

 

 1. Introduction

Software development processes generally follows easily identifiable stages like project planning, requirements definition, design, development, testing, integration, installation, acceptance and support.  However it differs from traditional manufacturing project stages in various ways. Firstly, we need to give time and cost estimates to the customers in advance without actually knowing its exact nature, which make software projects very risky and uncertain. Secondly, to judge the requirements in diverse domain areas with almost same set of manpower requires lot of flexibility on the part of employees and management. Then fast rate of changes in technologies, customer requirements, possibility of unexpected number of employees leaving the organization make our task even more complicated.  Integrating the complete solution, implementing it in successful ways, and making understand the end user about the software and  changes in the traditional processes are all part of the software development life cycle.  More and more global companies are outsourcing their software development projects to offshore software development destinations like India which are throwing new challenges in terms of requirements specifications, cultural differences, effective communications, security of valuable information, more rigorous legal, and governance and compliance standards.

 

Due to challenges posed by software development risks many approaches has been proposed to improve the development process. These approaches include various Computer aided Software Engineering (CASE)  tools, Enterprise project management tools,  Conceptual tools like various quality, coding,  process standards, models, and frameworks, and various software engineering models like traditional waterfall and spiral model.

Some of the case tools currently widely used include modeling and design tools like Rational Rose [19, 20], versioning control tools like CVS, various testing and bug tracking tools like Bugzilla, Integrated development environment and automatic code generation tools like Visual Studio, Jcreator, Dream weaver and others. Requirements development and management have always been critical in the implementation of software systems.  Some automated tools were also available to support requirements management. The use of these tools not only provides support in the definition and tracing of requirements, but it also opens the door to effective use of metrics in characterizing and assessing testing. Metrics are important because of the benefits associated with early detection and correction of problems with requirements [21].

Enterprise Project Management Tools were found to provide a wide range of functions. Among these functions are scheduling, resource allocation, and cost estimating, budgeting, and collaborating. Because enterprise project management tools are usually built on centralized data repositories, their operation enables the synchronization of these functions at multiple sites. They also allow enterprise-wide views of all the projects in an organization as well as access to anyone involved in setting up, maintaining, updating or browsing to come in contact with the project information needed to make informed decisions. These tools assist in disseminating and sharing project knowledge that relates to resource skills, project-related policy documents, templates, threaded discussions,  time and expense reports. It is important to note that enterprise project management tools emphasize project performance relative to resource consumption within a given set of time constraints (i.e., progress and dates). Some of the popular enterprise project management tools include the Welcome product suite, Microsoft project 2002,  Primavera P3e suite. These tools provide functionality such as enterprise project scheduling and resource management, Cost and Earned Value Management Software, and platform independent project collaboration, project stat using, and project portal functionality. While interest and investment in CASE and Project Management tools are rising steadily, actual experiences with tools have exhibited more ambiguity.  There has been no systematic examination or formulation of the organizational changes surrounding CASE tools [17].  The major challenge is to develop quality software in a reliable and repeatable manner while improving productivity [16].     

On the conceptual front all these challenges gradually led to development of Capability Maturity Model and concept of "Balanced Scorecard". The concepts of "Balanced Scorecard" [23] developed in the early 1990’s by Drs. Robert Kaplan (Harvard Business School) and David Norton represented an advance in the field of measuring enterprise performance, providing a framework for companies to evaluate both financial and "non-financial," or "extra-financial" measures such as quality, customer and employee satisfaction. This framework was widely used for enterprise level planning, control and monitoring by software companies.  However this framework suffers from limitations of over reliance on expert judgments for decision making.

The Capability Maturity Model (CMM) [3] was developed in early 1990's by Carnegie Mellon Software Engineering Institute. Since then many versions of this model came and were widely accepted as most rigorous and best standard by software industry throughout the world. What leads to instance success of this model is its ability to focus not only on external processes but also provide a framework for continuous improvements of internal processes in the company.  The CMM establishes a yardstick against which it is possible to judge, in a repeatable way, the maturity of an organization’s software process and compare it to the state of the practice of the industry. The CMM can also be used by an organization to plan improvements to its software development processes.

                                                      Five levels of CMM [3]

Key Process Areas of CMM Levels [3]

CMM Level 2 KPAs

CMM Level 3 KPAs

CMM Level 4 KPAs

CMM Level 5 KPAs

Requirements Management

Requirement development, Technical Solution, Product Integration

Quantitative Process Management

Defect Prevention

Software Project Planning

Verification, Validation

Software Quality Management

Technology Change Management

Software Project monitoring and control

Organization process definition and focus

X

Process Change Management

Supplier agreement management

Integrated Software Management

X

 Continous Improvement & Optimization

Measurement and Analysis

Organizational Training, integrated project management

X

X

Software Configuration Management

Risk Management, Integrated teaming

X

X

Process and product quality assurance

Integrated supplier management, Decision analysis and resolution, Integrated supplier management, Integrated teaming

X

X

However implementing the CMM framework is very challenging problem for three fundamental reasons. First is the issue of recognizing all input/output parameters in real time which influence various key process areas. Second, methodologies for quantification, optimization, and continuous improvements of these processes are vague. Third is the issue of synchronization of these processes with overall organizational objectives, profitability, efficiency, and growth. 

 Our primary focus in this study is to develop a model for analyze risk management (CMM level 3), quality management (CMM level 4), Quantification of processes (CMM level 4), defect prevention, continuous improvement and optimization (CMM level 5). Then based on analysis we also suggest improvement into various processes, which should be cost effective and suited for particular organization culture.

Software development process analysis is an important first step towards making the process more efficient and profitable. However,  analysis is difficult not only due to its complex nature because of large number of subsystems involved and dynamic interaction and influence of one over another, but also because it is difficult to quantify their contribution and influence on the software development process  as a whole. For example, technical expertise of manpower and quality of software developed are two important factors affecting any software company. However, technical expertise in itself can play an important role in the quality of software delivered, at the same time it may also lead to cost and time overrun, which may have negative consequences for the project. Similarly, quality of software also depends upon what the processes adopted for quality control and how much time and cost available for the project.  Also, the resources of an enterprise are limited so not all sources of risk can be immediately eliminated and priorities need to be established. Studying the various processes of a software development life cycle and measuring their impact in quantitative terms is one of the important objectives of this study.  Again identification of key sources of risk and the ability to measure the level of its harmfulness on the system as a whole is another important objective of this study.  In this paper various risk sources for a software enterprise were identified and a new approach based on Analytical Hierarchy Process [1,11,12]  and Fuzzy set  theory [1, 13, 14, 15]  were suggested as effective tool for enterprise risk evaluation and continuous mitigation. 

4.  Proposed Methodology

Methodology to be adopted for this study is four fold ' first to identify the major risk factors, then able to quantify most of them , to prioritize the factors based on their potential for causing risk to the organization and finally developing a general purpose risk management software. These four stages can be summarize as 

·                 Identification of the various sources of risk in the organization

·                 Quantification of these sources and estimation of their effect on the software development system as a whole.

·                 Prioritization of these sources according to their affect and importance in causing harm to the   organization. Then, suggesting means to their elimination or reduction according to practical feasibility and requirement of the management.  

·                 Development of a general purpose software, which by giving suitable input, able to quantify and priorities various risk sources.  Also, it will able to give estimates about how much elimination of any particular risk source expected  to benefit the management and how much cost it is likely to incur.    

6. Summary and Conclusion

Enterprise risk management is one of the most important strategic business tools to more effectively manage a variety of risks to gain competitive advantage and add value to the firm.   This study has identified the various external and internal risk sources in a software enterprise. We proposed a scientific model based on AHP and Fuzzy set theory to prioritize various risk sources and   developed a framework for their continuous elimination by adopting enterprise specific strategy. We also emphasize the dynamic interactions between these factors and suggested importance of quantification of these factors to judge their impact on the software enterprise as a whole.  Our model is highly flexible and customizable according to specific enterprise need. Then using fuzzy clustering we propose to cluster risk factors which are closely correlated with each other and likely to have common source of problems to enable their effective mitigation.  However to develop a  model to quantify various risk sources in monetary terms and how much improvements is required for effective mitigation  can be some of potential  future directions in which this work can be extended.

Based on  preliminary attempt of model validation with a CMM level 5 company revealed that   uncertain requirements, change in requirements, reactive approach of security, non conformance with the specification and ineffective utilization of available resources are some of the major risk sources for this enterprise.  It can be inferred that software enterprise can apply this new approach in their project and enterprise risk management to improve their efficiency, performance, profitability and to meet rising enterprise management challenges.      

Posted in Software.

No comments



MEASURING EFFICIENCY OF MINES THROUGH DATA ENVELOPMENT

1

MEASURING EFFICIENCY OF MINES THROUGH DATA ENVELOPMENT

ANALYSIS AND ANALYTICAL HIERARCHY PROCESS

Niraj Kumar*, Ashis Bhattacherjee**, Debashis Chakravarty***

and Debashis Sarkar****

ABSTRACT

Measuring efficiency of mines involves a multi-criteria decision making problem. Mines

can be ranked based on number of parameters like productivity, profitability,

environmental record and safety performance. However, ranking based upon individual

input and output parameters is often conflicting in nature. There are various methods by

which a composite score of various input and output parameters can be obtained to rank

mining units. The Analytic Hierarchy Process (AHP) and Data Envelopment Analysis

(DEA) are two most popular methods among them. However both of them suffer from

limitations. In AHP as the number of decision making units increases it becomes difficult

to rank, while in DEA all efficient units get equal score of 1, which makes it impossible

to rank among them. This paper presents a two-stage model for fully ranking mining

units based upon multiple input and output parameters.

In first stage, the DEA is used to get efficiency scores of various mining units. In second

stage, the AHP is applied to differentiate among mines, which have the same efficiency

score based upon the DEA method. This helps in further ranking for each mining units.

The application of this combined approach is demonstrated through a case study example

of a group of opencast coal mines. It is inferred that the approach can be used by the

mine management in ranking of a group of mines.

* IT Engg (T), System Integration, Kolkata, India 

E-mail: nirajkumariitkgp@gmail.com, Contact No: (Mobile).

** Professor and Head, Department of Mining Engineering, IIT, Kharagpur

*** Assisstant Professor , Department of Mining Engineering, IIT, Kharagpur

**** Deputy CME, Coal India Limited, 10, Netaji Subash Road, Kolkata-1.

2

INTRODUCTION

Coal mining is a capital-intensive industry. Over the last two decades, the industry has

been progressively mechanized. The size and cost of equipment, used in both

underground mines as well as in opencast mines, have become larger with passage of

time [2, 3, 4]. More capital-intensive production technique would increase the partial

productivity index of labour use while labor itself remains passive. Thus, although

productivity measures in OMS have shown steady increase, it cannot be fully attributed

to improvement in actual productivity of labour [9].

Opencast mining in India has received greater emphasis owing to its lower gestation

period, concentrated high rate of extraction, safety, high recovery and comparatively

higher potential of the technique for improved results. However the factor capital

accumulation instead of efficiency has become the prime driving force for growth in

production. Moreover, acute underutilization of the machineries and environmental

degradation are some of the major challenges, which need urgent attention [8].

In the Indian coal mining industry, a little attempt has been made for development of any

rational framework for ranking of mines based upon multiple criteria, which is very

important for management planning and control [11]. A coal mine uses several

incommensurables inputs and produces output, which makes it difficult to rank different

coal mines. Increasing concern over safety and environmental issues necessitates that

these factors should also be taken into account in ranking of the mines.

In this paper, the DEA method is applied for measuring the relative efficiency of mines

based on empirical data from previous operations of the mines [1, 2, 3, 5, 6, 9, 10, 12,

14]. However, the DEA does not provide full ranking, it merely provides classification

into two groups: efficient and inefficient. It does not rank the mines and all efficient

mines are classified as equally good [6]. As a result, the AHP method [6, 7, 13] is applied

to rank the mines. This approach enables all the mines to be ranked separately.

3

This paper combines the two most widely used multi-criteria decision making methods-

DEA and AHP- to rank the mines by taking into account the factors namely productivity,

profitability, environment and safety. The results of this new approach are demonstrated

through a case study example from a group of opencast coal mines.

METHODOLOGY

The DEA model to assess the relative efficiency of DMUs was first proposed by Charnes,

Cooper and Rhodes in 1978 [14]. The DEA deals with classifying mines into two

categories, efficient and inefficient, based on two sets of multiple criteria: multiple inputs

contributing negatively to the overall evaluation and multiple outputs contributing

positively to the overall evaluation. Since in DEA, a decision making unit has freedom to

receive the most favorable weights to achieve the objective, the efficiency score < 1

means that unit is inefficient as there is another unit that has received a higher value for

the same weights. The values of the weights differ from unit to unit and this flexibility in

the choice of weights characterizes the DEA model. This variability of weights is the

strength of the DEA, as the DEA is a methodology directed to frontiers rather than central

tendencies. The DEA model applicable to mining industry was discussed in detail by

Bhattacherjee et al [5] and Niraj et al [2, 1].

The various input parameters included in the analysis were: Capacity (In Lakhs Tones per

year), Man shifts (In Lakhs per year) and Cost Per Tones (In Rs./Te). The output

parameters included were:

(a) Productivity (in OMS), which is calculated based upon the following formulae:

OMS for O/C = (Ap + 1.4 Aobr) / {AMS(1+ 1.4 Sr)}

Where, Ap = Production of coal in opencast mines in tonnes

Aobr = Quantity of overburden in cubic meter

AMS = Annual Man-shift

Sr = Average OBR in cubic meter / Te of coal raised i.e. stripping ratio.

(b) Financial Operating Efficiency Index (FOEI), which is equal to

[Operational profit/loss]/ [Operating cost],

4

(c) Environmental Efficiency Index (EEI), which is equal to the ratio of difference of

initial and final environmental impact matrix score and initial environment

matrix score. These scores were computed based on factors such as air, water,

dust and their psychological impact on human beings of the locality.

(d) Safety Efficiency Index (SEI), which is the inverse of moving average of last five

years of the parameter severity frequency index. The severity frequency index is

the product of the severity and frequency rate.

As the DEA does not provide full ranking, the AHP method was applied to differential

between various mining units having same efficiency score from DEA model.

The Analytic Hierarchy process (AHP) is proposed by Saaty in early1970's [13]. The

application of the AHP is based on four basic principles namely decomposition,

prioritization, synthesis and consistency. In decomposition, a complex decision problem

is decomposed into a hierarchy with each level consisting of a few manageable elements,

while prioritization involves pairwise comparisons of various elements based on experts

judgments. Synthesis requires priorities to be pulled together through the principle of

hierarchy composition to provide the overall assessment of the available alternatives.

Finally, to guard against decision-makers making careless errors or exaggerated

judgments during the process of pairwise comparisons, consistency of judgments should

be measured. A consistency ratio of 0.1 is considered as the acceptable upper limit.

The AHP is designed to solve complex problems involving multiple criteria, organized in

a hierarchical structure. The hierarchy of the case study problem is shown in Figure 1.

At the top level, the criteria are evaluated and at the lower levels, the alternatives are

evaluated by each criterion. In Figure 1, M1, M2, M3, M4, M5, M6 are mines whose

ranking needs to be made based upon six criteria namely capacity, cost/te, productivity,

FOEI, EEI and SEI. The decision makers provide judgments about the relative

importance of each criterion on the scale of absolute values of 1-9 and then specify a

preference on each criterion for each decision alternatives. The output of AHP is a

prioritized ranking indicating the overall preference for each of the decision alternatives

[13].

5

Ranking of the mining units

Capacity Cost/Te Productivity FOEI EEI SEI

M1 M2 M3 M4 M5 M6

Figure 1: The hierarchy of the problem

In this study, as the quantitative values for each of the parameters for the mines are

known, so on the basis of that by considering prevailing industry standard, pairwise

comparison matrix was generated.

CASE STUDY

The analysis was carried out using the data from 20 opencast coal mines of Coal India

Limited [4]. The data were collected in the same time frame during the period 1999-2000.

The data were normalized to ensure adequate accuracy in the analysis. Twenty linear

programming problems of the DEA model were solved using the QSB software. The

results obtained are presented in Table 1. From Table 1, it is revealed that the mines M2,

M3, M5, M8, M9 and M14 are efficient with efficiency score of 1, while the remaining

mines are inefficient with efficiency score of less than one.

Table 1 also shows the reference set (peer group). The reference sets of a relatively

inefficient mine are those mines, which have relative efficiency of one with respect to the

optimal weights of the inefficient mine. These mines are considered to have similar

operating conditions as the concerned inefficient mine. For example, the mines M5 and

M9 are in the reference set for the mine M1. This reference set is helpful in constructing a

6

mine virtually efficient corresponding to the efficient mines. The shadow prices,

presented in Table 1, provide some more insight to the process of identifying

inefficiencies in the mines [3]. For example, the mine M1 has an efficiency score of 0.36

with the mine M5 and M9 being in reference set and shadow values of 0.22 and 0.79.

This means that a hypothetical mine M1 can be constructed as a combination of the

efficient inputs of the mines M5 and M9 in the proportion of their shadow values. It

could be stated that efficient inputs corresponding to the mine M5 is a combination of the

efficient inputs of the mines M5 and M9 for the given level of outputs.

The DEA solution revealed that six mining units namely M2, M3, M5, M8, M9 and M14

have efficiency score of 1, which makes it difficult to perform the absolute ranking of the

mines. For absolute ranking of the mines, the AHP method was applied. The judgment

matrix for the mines based on productivity was prepared, which is presented in Table 2.

we can see from Table 2 that the value of judgment is 5 for mine M2 in comparison to

M3 (See row 1- column 2). This means that mine M2 is "strongly preferred" than mine

M3 in terms of productivity, that is, productivity figure for mine M2 is sufficiently higher

than mine M3. Similarly, the judgment matrix was prepared based on all other criterion

like capacity, cost/te, FOEI, EEI and SEI. The judgment matrix for all criteria in terms of

importance of each for contributing towards the overall goal of ranking the mines were

generated based upon expert opinion [4] and is presented in Table 3. For example, in

Table 3, value of judgment matrix for cost/te is 2 in comparison to productivity (see row

2 - column 3). This means that the factor cost/te is "equally to moderately" preferred over

productivity in degree of importance towards their contribution in performance

evaluation of opencast coal mines. Based on judgment matrix, priority vectors for all six

mining units were computed and are presented in

Table 4.

After AHP analysis the mines M2, M14, M9, M8, M3 and M5 were ranked in the

decreasing order (from 1 to 6) with overall priority of 0.2656, 0.1861, 0.1640, 0.1603,

0.1286 and 0.1248 respectively (Table 4). Consistency of the judgments are also

calculated and consistency ratio value for all the judgments are much below than

7

specified upper limit of 0.1. Full ranking of all the 20 opencast mining units are shown in

Table 5.

Summary

In this paper, a two-stage model for fully ranking a group of mines based upon multiple

input and output parameters is presented. The application of the DEA and AHP clearly

generated the ranking of the mines considered in this study. Specifically, the study

revealed that out of the twenty mines studied, the overall performance of Mine 2 is the

best with rank 1.

While DEA is used to identify efficient and inefficient mines, the AHP is applied to

differentiate between mines having same efficiency score obtained from DEA model.

This combined approach not only helps to overcome the limitations of both the methods,

but also enables the full ranking of all the mines. It can be inferred that the mine

management can apply this new approach for ranking of their various mining units. This

enables mine management in various kinds of decision-making including resource

allocation, planning and control.

REFERENCES

. 1. Kumar Niraj, "Assessment of Performance Appraisal for Mines using Data

Envelopment Analysis and Fuzzy set theory- A Case Study from Coal Mining",

M.Tech. Thesis, Department of Mining Engineering, I.I.T. Kharagpur, 2002, 85pp.

2. Kumar N., Bhattacherjee A. and Sarkar D., " Performance appraisal of coal mines

using Data Envelopment Analysis and Fuzzy Set Theory", Mintech, 2002, Volume

23, No. 5, pp. 18-25.

3 . Sarkar Debasish, Bhattacherjee Ashis and Kumar Niraj, "Performance Evaluation

of Underground Coal Mines: A Case Study", 19th World Mining Congress,

1-5 November, 2003, New Delhi, PP. 917-928.

4. Sarkar D., "Development of Methodology For Improving The Performance of

Different Work Units ' A Case Study From Large Public Sector Mining Company

",Ph.D. Thesis, Department of Industrial Engineering and Management,

8

I.S.M. Dhanbad, 2000, 160 pp.

5. Bhattacherjee A., Kumar P. and Sarkar D., January 1999, "Application of Data

Envelopment Analysis for Performance Apprisal", Proceedings of Platinum

Jubilee Symposium on Productivity Improvement in Indian Mining Industry,

Department of Mining Engineering, Institute of Technology, BHU, 1999,

pp. 50-54.

6. Sinuany-stern Z., Mchrez A. and Hadad Y., "An AHP/DEA methodology for

ranking decision making units", International Transactions in Operational

Research, volume-7, 2000, pp. 109-124.

7. Hafeez K., Zhang Y. and Malak Naila, "Determining Key Capabilities of a firm

using analytical hierarchy process", International Journal of Production

Economics, Volume-76, 2002, PP. 39-51.

8. Kulshreshtha M. and Parikh J. , " A study of productivity in the Indian coal

sector", Energy Policy, Volume- 29, 2001, pp. 701-713.

9. Kulshreshtha M. and Parikh J., " Study of efficiency and productivity growth in

opencast and underground coal mining in India: a DEA analysis", Energy

Economics, Volume ' 24, 2002, PP. 439-453.

10. Ghose R., Sinha B.K., Krishna K.C., Sengupta J.K., "A Study on Application of

Data Envelopment Analysis in Coal India Limited", Consultancy Project Report,

Indian Institute of Management, Calcutta, 1998, 163 pp.

11. Mukherjee K. and Bera A., " Application of goal programming in project

selection decision ' A case study from the Indian Coal mining industry",

European journal of Operational Research, Volume- 82, 1995, PP. 18-25.

12. Thompson R., Dharmapala P. and Thrall R., " Linked-cone DEA profit ratios and

technical efficiency with application to Illinois coal mines", Int. j. Production

Economics, volume- 39, 1995, PP. 99-115.

13. Saaty T.L., "The Analytical Hierarchy Process", McGraw-Hill, 1980.

14. Charnes A., Cooper W.W. and Rhodes E. (CCR), "Measuring Efficiency of

Decision making units," European Journal of Operation Research, 1978, Vol.2,

pp. 429 ' 444.

9

TABLE 1: Efficiency scores, reference sets and shadow values obtained by DEA

model runs for the case study mines

Unit

Code

Efficiency

Score

Peer Group Shadow values

M1 0.36 5, 9 0.22, 0.79

M2 1.00 2 1.00

M3 1.00 3 1.00

M4 0.62 3, 5, 9, 14 0.27, 0.09, 0.23, 0.24

M5 1.00 5 1.00

M6 0.68 2, 5, 14 0.43, 0.17, 0.46

M7 0.46 5, 8, 9 0.25, 0.57, 0.18

M8 1.00 8 1.00

M9 1.00 9 1.00

M10 0.36 5, 9 0.06, 0.87

M11 0.60 5, 9 0.37, 1.01

M12 0.87 2 1.01

M13 0.39 5, 8, 9 0.21, 0.06, 0.70

M14 1.00 14 1.00

M15 0.56 2, 9 0.64, 0.51

M16 0.71 2, 9 0.24, 0.73

M17 0.48 3, 5, 9, 14 0.17, 0.38, 0.40, 0.08

M18 0.83 3, 5, 9, 14 0.17, 0.38, 0.21, 0.35

M19 0.33 3, 5, 14 0.01, 0.57, 0.39

M20 0.65 2, 9 0.49, 0.48

10

Table 2: Judgment matrix for Productivity

Productivity M2 M3 M5 M8 M9 M14

M2 1 5 ½ ¼ ½ 1/3

M3 1/5 1 1/5 1/7 1/5 1/7

M5 2 5 1 1/5 1/3 1/5

M8 5 7 4 1 4 3

M9 3 6 2 ¼ 1 1/3

M14 3 7 5 1/3 3 1

(In the pairwise comparison matrix, the value in the row i and column j is the measure of

preference of the mining units in row i when compared to the mining units in column j)

Table 3: Pairwise comparison to set priorities for all criteria

Capacity Cost/te Productivity FOEI EEI SEI

Capacity 1 1/3 1/3 2 5 5

Cost/Te 3 1 2 3 7 7

Productivity 3 ½ 1 3 7 7

FOEI ½ 1/3 1/3 1 5 5

EEI 1/5 1/7 1/7 1/5 1 2

SEI 1/5 1/7 1/7 1/5 ½ 1

Table 4: Priority vectors obtained for six mining units

Capacity Cost/Te Productivity FOEI EEI SEI Overall

Priority

M2 0.2732 0.4222 0.0845 0.2465 0.1502 0.2511 0.2656

M3 0.0550 0.1537 0.0296 0.3573 0.0321 0.1590 0.1286

M5 0.3774 0.0620 0.0915 0.0984 0.0617 0.0547 0.1248

M8 0.0550 0.0620 0.3990 0.0807 0.1224 0.0304 0.1603

M9 0.0550 0.1950 0.1423 0.2152 0.3539 0.0679 0.1640

M14 0.1842 0.1046 0.2525 0.1595 0.2791 0.4364 0.1861

Priority

vectors

0.1575 0.3589 0.2827 0.1288 0.0424 0.0362

11

Table 5: Ranking of mining units based on DEA and AHP methods

Ranking 1 2 3 4 5 6 7 8 9 10

Mining

Units

M2 M14 M9 M8 M3 M5 M12 M18 M16 M6

Ranking 11 12 13 14 15 16 17 18 19 20

Mining

Units

M20 M4 M11 M15 M17 M7 M13 M1 M10 M19

Posted in Technical.

No comments



S.I.M.P.L.E. (SWIFT Information Management Product for Leadership

Array

Posted in Software.

No comments



Developing Next Generation Dynamic Web Services for Scientific Portals

Developing Next Generation Dynamic Web Services for Scientific Portals

By

Niraj Kumar

Software Developer
 Kolkata ' 700026.

West Bengal, India

E-mail: nirajkumariitkgp@gmail.com

Contact No: (Mobile).

© 2005 Niraj Kumar. All rights reserved.

Objective:

The main objective of this whitepaper is to develop a framework for next

generation web services for scientific portal . Integrating various databases and web

resources of specific domain available on the WWW and bring these

heterogeneous sources of data into common platform or in the form required by

the user. Developing a domain specific wrapper (CHEMWRAP) for extracting

useful information from HTML web pages and hidden Web and converting these

into directly usable form. Next stage is to develop fully automatic, dynamic and

generic web based service for portal which can based on user specific query,

able to crawl the Web, give the most relevant data from multiple sources and

convert these data into user specific requirement. Our goal is to simplify access

to chemistry data by providing a single access point to a large number of

sources.

Introduction:

The Web can be considered as world's biggest data source and just textual data

amounts to at least hundreds of terabytes. The growth rate of Web is even more

dramatic with its size doubling every two years. However, the content of the Web

changes very fast and many of the past links and resources become dead while

many more newer one getting added every day. Aside from these newly created

pages, the existing pages are continuously updated. For example, in a study at

Stanford University of over half a million pages over 4 months, it was found that

about 23%

of pages changed daily. In the .com domain 40% of the pages changed daily,

and the half-life of pages is about 10 days (in 10 days half of the pages are gone,

i.e., their URLs are no longer valid) [Arasu et. al.].

Apart from this, a tremendous amount of content on the Web is dynamic. According to

an estimate close to 80% of the content of the Web is dynamically generated and that this

number is continuously increasing. This dynamism takes a number of different form like

temporal dynamism (time sensitive dynamic content), Client-based dynamism

(Customized web pages), Input dynamism ( Pages whose content depends on the input

received from the user) etc and further complicate the integration of web resources

[Raghavan et.al.]. However, little of these dynamic content is currently being crawled and

indexes by even most popular search engine and they usually index only static web pages

by following hyperlinks, ignoring search forms and pages that require authorization or

prior registration.

Crawling the hidden Web is a very challenging problem for two fundamental reasons.

First is the issue of scale: a recent study estimates that the size of the content available

through such searchable online databases is about 400 to 500 times larger than the size

of the "static Web". Second, access to these databases is provided only through restricted

search interfaces, intended for use by humans. However, the domain specific scientific

portals needs to crawl and integrate these hidden Web databases to provide task specific

requirements of a particular user and application.

Most of the modern science and technological advancement were driven by

latest development in sciences and Information Technology and particularly web

based system is going to play very important role. With technical development of

applied sciences currently facing many limitations and ever increasing

complexities of problems, increasing use of computer to solve problems is only

natural. Today, Scientific and research portals domain covers wide areas from

physical, organic, inorganic to biochemistry, molecular modeling, biology, drug

design, Geosciences, Applied engineering, and many more. The scientific

community is globally distributed with culture of sharing and rapid dissemination

of information. Each separate area of science generates its own data and

information sources.

A large amount of scientific data is distributed over the Internet (for example: The

Cambridge Crystallographic Data Center, NIST, The Protein Data Bank .

Typically, these information is accessible only through custom web based query

interfaces. Each of these sources and databases have different structures,

contents, query languages and retrieved data in different format. Furthermore,

they are prone to having their interfaces and formats updated without warning

[Buttler et. al.]. To facilitate scientist, students and industrial users, a large

number of specialist interrogation, modeling, and software analysis tools are

available (for example: GAMESS, Gaussian, GAP, Ghemical, COLUMBUS,

COSMO-RS etc).

When scientific resource users require information from multiple sources, they

must pose the appropriate queries at each source individually then explicitly

integrate the result. This solution may be acceptable for a small number of

sources, but it quickly becomes an overwhelming burden for users as the number

of sources grow [Buttler et. al.]. Currently there are thousands of scientific

resources and databases, making it infeasible to manually gather required and

relevant data from these sources. Our proposed system aims to provide a user

interface where they can enter their query, then it should be able to perform the

following query formulation and execution tasks :

(a) identify sources and their locations both static as well as dynamic

(b) identify the content/function of sources and its type

(c) Clustering Web pages based on their structure and attributes

(d) Developing a generic wrapper CHEMWRAP which able to filter required

information from HTML pages as well as hidden databases from heterogeneous sources

(e) transform data in user required format

(f) merge results from different sources

(g) Optimize the whole system to give most efficient, secure and low cost solution

Challenges in developing future generation Web services can be broadly classified into

integration of number of interrelated problems like developing a system which in real

time able to identify the most relevant static and dynamic sources (This is essentially a

problem of developing a advanced search engine and crawling technologies with high

precision and recall ratio) , addressing the problem of heterogeneous of these resources

i.e. developing some Multi-database system (This is problem of portability and platform

independences from data sources to hardware and software used). Then extracting only

relevant information from these sources (i.e. developing the wrapper(s)/filter(s)

methodology and technology which includes larger problems of semantics of Web) and

finally developing customized user interfaces and integration of all software, networking

and hardware sub-systems. From last 30 years a number of efforts are being made in all

these areas separately and in last 10 years more focused attempts of integration of these

techniques and methodologies were taken. However, my literature review revealed that

any of present day system is far below the level of challenges posed by requirement of

such a system. Now, before going into methodology of our approach, I would like to

give a brief overview of attempts already made in this direction particularly with

reference to providing future generation Web services from heterogeneous sources.

Overview of Related work

Many researchers have tackled problems related to information extraction and integration

from the Web. These go from developing toolkits to add in building wrappers manually

and wrapper induction to the extraction of relational data from large collections of web

documents or extraction of symbolic knowledge. Some of wrapper construction

methods are manual, while others are semiautomatic and automatic. However manually

coding of wrappers become entirely impossible in current scenarios. Methodologies

employed to develop wrappers vary widely from finding pattern in HTML pages using

tree structure to finite state based approach to fuzzy set, artificial intelligence, and neural

networks based learning and training approach. Some of the well known research groups

and products in these areas are: ANDES, WysiWyg Web Wrapper Factory (W4F),

Ariadne, Garlic, TSIMMIS, XWRAP, Mostrare Project, STALKER, TAMBIS,

SoftMealy, FASTUS, HLRT Wrappers, Jedi etc.

XWRAP [Liu et. al.]: XWRAP is a semi-automatic XML-enabled wrapper construction

system for Web sources. The architecture of XWRAP consists of four components:

Syntactical structure normalization, Information extraction, Code generation, Program

Testing and packaging. XWRAP was developed in Java. By XML-enabling, it means that

the wrapper programs generated by XWRAP can transform an HTML document into an

XML document and deliver the extracted data content in XML format with a DTD.

STALKER [Muslea et. al.]: STALKER, developed in University of Southern California,

is a wrapper induction algorithm that generates extraction rules for semi-structured Web

based information sources using landmark automata. Based on just a few training

examples STALKER learns extraction rules for documents with multiple level of

embedding.

FASTUS [Hobbs et. al.]: FASTUS is a five stage system for extracting information

from natural language text. It works essentially as a cascaded, non-deterministic

finite-state automaton.

Decomposition of language processing enables the system to do exactly the

right amount of domain-independent syntax, so that domain-dependent semantic

and pragmatic processing can be applied to the right larger-scale structures.

Some of the blind experiments have demonstrated that it is very efficient.

WisiWyg Web Wrapper factory [Sahuguet et. al.]: W4F, developed at Penn Database

Research Group, is a toolkit that allows the fast generation of Web wrappers. Wrapper

generation consists of retrieval of an HTML page via GET or POST methods, followed

by construction of HTML parse tree according to the HTML hierarchy. Information can

then be extracted declaratively using a set of rules applied on the parse tree. A nested

string list (NSL) data structure is used as the datatype to represent extracted information

internally.

InfoSleuth [Bayardo et. al.]: The InfoSleuth project at MCC exploit and synthesize

new technologies into a unified system that retrieves and processes information

in an ever changing network of information resources. This is scalable and

portable and accomplished through the use of collaborative agents, and it uses

Java as a common wrapper agent.

TAMBIS [Baker et. al.]: The TAMBIS project at University of Manchester, UK, is

a three layer madiator/wrapper architecture which aims to provide transparent

access to various disparate biological databases and analysis tools. The use of

knowledge base and wrapped resources removes the need for user to know

which are the appropriate resources and how to access them. It greatly reduces

time taken to analyze their data. TAMBIS aims to use CORBA wrapped services.

Garlic: Developed at IBM Almaden Research Center, Garlic is a middleware

system that provides an integrated view of heterogeneous legacy data without

changing how or where data is stored. It provides a unified schema and common

interface for new applications without disturbing existing applications. This relies

on wrappers that encapsulate the underlying data and mediate between data

source and middleware.

Other projects which specifically aims at diverse and heterogeneous databases

are SINGAPORE, TSIMMIS, DISCO etc.

Problems related with crawling hidden Web and developing search engine were

addressed by Raghvan et. al., Brin et. al. among others.

METHODOLOGY

Methodology to be adopted for this study is to develop a web crawler specific to

scientific areas which able to crawl on the Web for available database resources. For

start we do not propose to crawl all the Web resources but try to stick to four or five

sources. But as most of the databases available are hidden and they have their own

data retrieval mechanism and user interfaces, we need to develop a crawler taking

into account all these factors. Then based on these sources we try to cluster

information into one based on their structural similarity. As each of these databases

have their own format but closely related one as each of them have data about

molecular structure of chemical compounds, so We propose a generic wrapper

CHEMWRAP which able to filter required information from HTML pages covert

them into a common format (say XML) and extract the required information and

convert them into format supported by some scientific software program. We will

develop whole our system in Java, XML, COM/CORBA and other Java based Web

technologies.

Decomposition of Web Information extraction task: The Wrapper generation

process is so complex that it is not possible to consider the construction process

occurring in a one single step. For this reason we have partition the CHEMWRAP

construction process into six phases (Figure 2). The interaction and information

exchange between any two of the phases needs to be performed . After the

preprocessing of sources, information extraction is started. The main task of the

information extraction component is to explore and specify the structure of the

retrieved document (page object) in a declarative extraction rule language. For an

HTML document, the information extraction phase takes as input a parse tree

generated by the syntactical normalizer. It first interacts with the user to identify the

semantic tokens (a group of syntactic tokens that logically belong together) and the

important hierarchical structure. Then it annotates the tree nodes with semantic tokens

in comma-delimited format and nesting hierarchy in context-free grammar. More

concretely, the information extraction process involves three steps; each step

generates a set of extractions rules to be used by the code generation phase to

generate wrapper program code.

Step 1: Identifying region of interest on the Page

Step 2: Identifying Semantics token of interest on the page

Step 3: Determining the nesting hierarchy for the content presentation of the page

Proposed System Architecture (Figure 1)

Scientific Portal

Client 1 Client 2 Client 3

HTTP

request

Cambridge databank NIST Databank Protein databank

Wrapper

Wrapper

wrapper

CHEMWRAP

Extracted Data

Data Integrator

XML form Data

Some Scientific software Format

Data

Result calculation by scientific

software

Decomposition of Web Information Extraction Task (Figure 2)

(CHEMWRAP Architecture)

HTTP Query Building

Enter asset of URL (s)

Fetching and Repairing Source document

Clustering Pages of Same Structure if

needed

Required Source Document

Generating a Parse Tree

Information Extraction

XML-enabled Wrapper Code Generator

Code Testing and Integration With

ChemCraft

Wrapper Code

Extraction rule

References

Raghavan Sriram, Grecia 'Molina Hector, "Crawling the Hidden Web", Computer

Science Department, Stanford University, Stanford, USA, 2000, PP-25.

Buttler David, Critchlow Terence, "Using meta-data to automatically wrap

bioinformatics sources", Information and Software Technology, No-44, 2002, PP 237-

239.

Baker Patricia G. et al ,"TAMBIS ' Transparent access to Multiple Bioinformatics

Information Sources", School of Biological Sciences, University of Manchester, UK

Arasu Arvind, Cho Junghoo et. al., "Searching the Web", Computer Science

Department, Stanford University, 2000, PP-42

Habegger Benjamin, Quafafou Mohamad, "Multi-pattern wrappers for relation

extraction from the Web", IRIN, University of Nantes, France, 2003,PP-5.

Myllymaki Jussi, "Effective Web data extraction with standard XML technologies",

Computer Networks, No ' 39, 2002, PP 635-644.

Liu Ling, Pu Calton, Han Wei, "XWRAP: An XML-enabled Wrapper Construction

System for Web Information Sources", Georgia Institute of Technology, Atlanta, PP-11.

Muslea Ion, Minton Steve, Knoblock Craige, "STALKER: Learning extraction rules for

semistructured webbased information sources", IMSC, University of South California,

USA, PP-8.

Hobbs Jerry R., Applet Douglas et.al., "FASTUS:A Cascaded Finite-State Transducer

for Extracting Information from Natural-Language Text", Artificial Intelligence Center,

SRI International, California, 1997, PP-25.

A. Sahuguet, F. Azavant. W4F, 1998. http://db.cis.upenn.edu/W4F.

Bayardo R. J., Bohrer W. et. al., "InfoSleuth: Agent-Based Semantic Integration of Information in Open

and Dynamic Environments", Microelectronics and Computer Technology Corporation, Austin, Texas,

1997, PP-12

Roth Mary Tork, Schwarz Peter, "A Wrapper Architecture for Legacy Data Sources", IBM Almaden

Research Center

Brin Sergey, Page Lawrence, "The Anatomy of a Large-Scale Hypertextual Web Search Engine",

Computer Science Department, Stanford University, PP ' 26.

Brin Sergey, "Extracting Patterns and Relations from the World wide Web", Computer Science

Department, Stanford University, PP ' 12.

Liu Ling, Pu Calton, Han Wei, "An XML-enabled data extraction toolkit for web

sources", Information Systems, No ' 26, 2001, PP ' 563-583

Habegger Benjamin, Quafafou Mohamad, "Web Services for Information Extraction

from the Web", Proceedings of the IEEE International Conference on Web Services, 2004, PP ' 8.

CHEMW

RAP

Posted in Software.

1 comment



Competitive advantage through need based segmentation and value addition in Iron ore industry


 
              Competitive advantage through need based segmentation

and value addition in the iron ore industr
       
                By

 

Niraj Kumar

 

Software Developer, Kolkata ' 700026.

West Bengal, India

E-mail: nirajkumariitkgp@gmail.com

 

Contact No:  (Mobile).

© 2003 Niraj Kumar. All right reserved.

Project Summary: India is an important player in iron ore and steel market globally. It is

expected that iron ore prices will fall over the long term while demand continues to rise.

Also the iron ore industry has been facing the challenge of deteriorating mining

conditions. These include ever-deepening mines, growing waste-to-ore ratios, longer

hauling distances and the depletion of high-grade ores. Between 1998 and 2002, the

weighted average cost of non-agglomerated ore globally was fell by 24% (on FOB basis),

while pellets cost dropped by 9% (Iron ore 2003, AME's Report). The Indian iron ore

industry needs to respond to these issues with reducing costs, increasing output, process

re-engineering, product quality improvement and better customer relations. Also,

The iron ore market is not one single market. It consists of several submarkets of which

the market for fines, the market for lump ore and the market for pellets are the most

important. Fines, sold in the market are usually sintered at the steel mill, while lump ore

and pellets can be fed directly into the blast furnace. Pellets are usually produced by the

iron ore producer at the mine site.

To gain competitive advantage, it is imperative that customized service should be

provided to the customer according to their need. For this identification of customer

needs and need 'based segmentation is required. This is one of the objectives of this

study. After segmentation and identification of needs, company needs to develop its

mining, processing and service strategy accordingly. A typical iron ore company

undergoes one or more of the following processes:

(1) Stripping Overburden

(2) Drilling and Blasting

(3) Loading of iron ore and waste, usually on trucks

(4) Haulage to crusher for primary crushing and sizing

(5) Further haulage or processing through stages of crushing, screening and in some

cases according to customer need, washing, to produce lump and natural fine ore

products

(6) If necessary, beneficiation by crushing and separation of iron through magnetic

floatation or other methods

(7) If necessary, pelletization by mixing ground ore with a binder and indurating in a

grate or furnace

(8) Road or rail transport to a blendery or storage stockpile at the point of shipping or

directly to the customer in case of domestic market.

Apart from these partial lists, there are many activities which any

organization goes through in their day to day functioning. If we consider from

production planning to overburden removal to final product delivery to the customer

as one process, then this whole process goes through a number of sub processes.

These sub processes can be classified as value adding processes, Essential processes

and non value adding processes. Target of this study is the identify non value adding

processes and improve upon existing value adding and essential processes. This way

we can suggest the mine management to eliminate the non value adding processes

and increase the value adding processes according to the need of every particular

segment of customer. This helps in lot of cost reduction and quality improvement and

gives better value to the customer. This help the iron ore company to retain their

existing customer base as well as increase customer base by giving better value to

customer and thus greater customer satisfaction.

In short we can say that purpose of this

study is two fold. First is identifying the need of iron ore customer and accordingly

segmenting them and then streamlining the current company processes to fulfill their

need with better value and thus gain competitive advantage over their customer.

 

METHODOLOGY: The purpose of this study is to identify the attributes of iron ore

which are important for customer point of view, identifying the group of buyers that

possess similar characteristics and analyzing the iron ore company performance relative

to these. Then on the basis of firm present and potential capabilities, suggesting the best

course of action and improvement in present processes which help to satisfy need of

particular segments of customer and thus give better value to the customer to gain

competitive advantage over their competitor. The work can be divided into three stages.

 

STAGE I: Identifying the need of the customer and segmenting them on the basis of

similar characteristics. Literature review revealed that industrial customer buying

behavior is very complex and often not a single person but a group of persons like

initiators, users, influencers, deciders, approvers, buyers, gatekeepers etc influence the

buying decision of a firm. There are many characteristics of iron ore which affects its

performance in blast furnace and quality of steel made like reducibility, size and size

distribution, Strength, Softening range, Swelling and volume change, iron content,

moisture content, gangue contents etc. Again cost, quality and technical specifications of

the product is the most important criteria influencing the buying behavior of the

customer. Our primary task is to identify the characteristics of iron ore which are major

concern for the consumer. For this purpose Qualitative data collection from customer

through Questionnaire is the best Option.

After this we need to identify the importance of the various characteristics of the

iron ore with customer point of view and the perception of the customer about the

performance of the company in fulfilling these characteristics. Literature suggests there

are two widely used method for this, one is qualitative method, also called laddering

(which is the most widely practiced presently) and other is quantitative approach (like

Association pattern technique). While both of these approaches has its suitably and

limitations according to situations, in industrial setting it is often desirable to make the

conclusion on the basis of both, to considerably reduce the chances of error.

Qualitative data collection: For these in-depth interviews with the customers of the

company required. Interview should be conducted in such a manner, which allows the

customer to tell the story from their own prospective. The qualitative data so collected

should be interpreted correctly and analyzed using analysis of variance (ANOVA).

However this method has its limitations. It is time consuming and needs to be carried out

by trained interviewers. It is an expensive data collection technique. Moreover, it places a

serious burden on respondents and quality of data may be affected by respondent fatigue

and boredom. So some quantitative oriented technique to find the customer response is

also proposed to apply.

Association pattern technique (APT) is one such quantitative technique.

APT is inspired by Gutman (1982). APT method uses fixed format for questionnaire.

This implies that free-response format in the laddering required the respondents to recall

the concepts from memory, whereas the fixed-format of APT is associated with

recognition of these concepts that are presented to the customer. This may lead to

differences as recall and recognition are quite different processes. The total number of

recognized concepts typically exceeds the total number of recalled concepts. This may

suggest that total number of attributes is greater in APT than in laddering. In contrast to

laddering attributes in APT are provided by the Researcher. In APT an Attribute-

Consequence matrix (AC matrix) and a consequences- Value matrix (CV matrix) are

distinguished. It is assumed that attribute of the product and its consequences are directly

related and consequences and value are directly related with each other. However AC and

CV are independent to each other. Also analysis of the data with APT is simple due to the

standardization of the concepts used. It will very interesting to check convergent validity

between Laddering and APT Technique. After analyzing the data by using some

statistical technique, we able to separate the customer with common preferences and

segment them and on the basis of this segmentation the company can make their strategy

according to particular segment of customer.

 

STAGE II: In this stage firm performance and importance attribute identified by

customer is analyzed using Performance-importance analysis. There are various

approaches of majoring performance of a Organization like gap analysis, performance

ratios, comparative scales etc. In gap analysis performance of the firm on each attribute is

compared with the performance of the best competitor in the market and accordingly

positive and negative gap obtained were analyzed. Positive gap means firm has superior

performance on these account and it is core competence of the firm. Negative gap means

that firm need to improve upon these attributes to remain competitive. Similarly is the

approach in case of performance ration. Here in case of subtracting the attributes we are

dividing this. However with this kind of performance analysis it is difficult to identify the

deficiencies which industry as a whole is going through. In comparative scales, instead of

performance comparing with its competitor, it is compared with some standard scale.

Depending upon the purpose the standard may be anything from more than mean (say

more than 5 on a scale of 10) to top box performance score like 9 out of 10. However

fixing the standard of performance on the basis of individual firm goal is the most logical

approach and in this study we try to measure the performance of the firm on the basis of

the firm goal. After doing performance-importance matrix analysis, we able to identify

the strong as well as weak link in the processes of firm. If the importance as well as

performance is high on any attributes that means firm is doing fine on these attributes and

these are core competence of the firm to get competitive advantage in the market. If

importance score are high, while performance score are low, it means these are the weak

area of the firm and the firm needed to immediately address these in order to get

competitive advantage. If importance is low, while performance is high, this means that

unnecessarily firm using their scare resources on these and some of these resources needs

to be diverted on high importance and low performance area. If importance is low and

also performance is low, then these issues may be not issues of immediate concern.

 

STAGE III: In this stage the detailed flow chart of all the processes from start to the

point of delivery to the customer is needed to be made. For a typical iron ore company

these processes may start from exploration stage to development and planning and may

cover combination of the following

(9) Stripping Overburden

(10) Drilling and Blasting

(11) Loading of iron ore and waste, usually on trucks

(12) Haulage to crusher for primary crushing and sizing

(13) Further haulage or processing through stages of crushing, screening and in

some cases according to customer need, washing, to produce lump and natural

fine ore products

(14) If necessary, beneficiation by crushing and separation of iron through

magnetic floatation or other methods

(15) If necessary, pelletization by mixing ground ore with a binder and

indurating in a grate or furnace

(16) Road or rail transport to a blendery or storage stockpile at the point of

shipping or directly to the customer in case of domestic market.

However apart from these there

are many other activities go into running of any Organization. Here, we need to find out

value adding, essential and non value adding processes. We can suggest to eliminate or

minimize the non value adding processes from the whole processes. Also essential

process need to be reduce to minimum as these are non value adding processes. After

getting the result from stage II, We need to concentrate on those value adding processes

which are critical for customer point of view. We intended to improve upon these value

adding processes by suggesting some improved method or practice. However our

approach is to concentrate more on mining processes (& not on concentrating or pelleting

processes as these are domain of metallurgy engineers) and on transportation of the iron

ore product from stockyard of the company to the customer (It is observed that

transportation cost is usually very high on its share on the total cost may be upto 50% for

international market to upto 30% for domestic market, However rarely less than 10%).

 

How to analyze processes?

 

A process is any part of an organization that takes input and

transforms them into outputs that, it is hoped, are of great value to the organization than

the original inputs. The processes can produce product as an output or services can be

product of a processes. A good way to analyze a process is with a diagram showing the

basic elements of process- typically task , flows and storage area. Processes may be

single stage or multistage. In case of multistage processes buffering may be required in

order to prevent starvation of some processes. Process selection is also a very important

parameter to gain competitive advantage i.e. whether to go for job shop or mass scale

production. Iron ore industry usually follow make to stock philosophy. A make to stock

process can be controlled based on actual or anticipated amount of customer demand. A

target stocking level is set and process is periodically activated to maintain that target

stocking level. Processes may be pacing or non pacing type. Pacing means processes

which needed to complete in a specified time frame, while there is no such standard time

is necessary than it is called non pacing process. In the processes where large number of

work force is employed than by work measurement and with proper job design and

improving the working environmental usually lead to improved value addition in the

processes.

After this measuring the performance of each processes is very important task

to increase the value addition. There are many traditional way of measuring performance

like partial or overall productivity, efficiency analysis or by identifying the Operation

time, throughput time , run time etc of the processes. We need to remember here that

time is money in competitive environment and by reducing time of any processes we are

adding value to that process. Also better value can be added to processes by following

one or more of the following activities:

(1) By performing activities in parallel

(2) By changing the sequence of activities

(3) By reducing interruptions in the processes

(4) By integrating more processes into single processes etc.

Proper facility layout also makes

processes efficient and thus add value to the product. By suggesting better transportation

system or better stock management method, we can significantly add value to the

processes. Finally, through better service to the customer, we can significantly add to the

value of the process. Now days service is considered to be most important value addition

activity and with very less additional cost. By suggesting better means of service we can

significantly add to the value of the processes. Then, on the basis of above analysis, the

improved flow chart of all processes needs to be drawn. With this project work we hope

to significantly improve the competitiveness of Indian iron ore company and able to give

better value to the customer which may result in greater customer satisfaction.

 

Posted in Technical.

No comments



Ranking of Indian Coals using Image Analysis Technique

Ranking of Indian Coals using Image Analysis Technique

By

Niraj Kumar

Software Developer

 Kolkata ' 700026.

West Bengal, India

E-mail: nirajkumariitkgp@gmail.com

Contact No: (Mobile).

© 2003 Niraj Kumar. All rights reserved.

Abstract

In this paper, an attempt has been made to rank Indian coal using Image analysis

technique. Coal apart from C (carbon) contains number of other constituent like

hydrogen, nitrogen, sulphur, oxygen etc. Classifying coal scientifically is of tremendous

importance in techno-economic applications particularly for the purpose of

grading/pricing, for quality grouping , for reserve estimation and for industrial use. In this

study, image analysis coupled with Energy Dispersive Spectrometry (EDS) analysis on a

Scanning Electron Microscope (SEM) is proposed to apply for ranking of Indian coal as

well as for estimating degree of coal liberation for metallurgical purpose.

Screened size fractions of coal were mounted on polished thin sections and later on

analyzed by a SEM coupled with EDS. This is important for discrimination of various

constituent of coal, particularly when two constituent have similar average atomic

numbers, such as carbon and nitrogen. Two images per field were collected '

backscattered electrons image and a multi-element X-ray dot mapping images. The

results were utilized for ranking of coals as well as for liberation analysis of various

coals.

Introduction

Coal quantification and liberation degree evaluations are a major issue for ranking of coal

as well as its characterization for mineral dressing for customer required quality delivery.

These analyses can be performed manually by optical microscopy (OM) or a Scanning

Electron Microscope (SEM) in a very tiresome and exhaustive routine. Image analysis

coupled with an OM or a SEM can perform these analyses resulting in more reliable and

rapid outcomes.

Since phase differentiation by OM coupled to an image analysis is not a usual

and easy task, a digital SEM image is frequently used to solve more complex

mineralogical associations. Special care must be taken regarding sample preparation

and beam control . Atomic number contrast from backscattered electrons (BSE)

signal are primarily used for phase discrimination; however, when phases with a very

similar average atomic number are present, X-ray information is the only possible tool

that could be used to differentiate them.

This work presents an off-line image analysis routine applied to the

characterization of Indian coal. However, the BSE image not able to clearly identify between

phases having similar atomic numbers like C and N. These phases could only be properly

segmented by coupling additional information related to their chemical composition

using X-ray data. Multi-element X-ray dot-mapping images acquired by an energy

dispersive spectrometry (EDS) were considered for this purpose.

Methodology

The study samples consisted of coal sample particles from four closely screened

fraction sizes mounted on polished thin sections. Special care needs to be taken regarding the

sample preparation to avoid the physical touch of particles as well as regarding the

polishing surface quality.

BSE and X-ray dot images need to obtained by a S440, Leo, coupled with an Isis-

300 EDS System, Oxford. X-ray dot-mapping images also needed to be acquired by S440;

each selected element was represented by a binary plane and by a specific gray level value.

Both images, presenting 1024 by 768 pixels resolution, needed to be processed off-line by

Quantimet Qwin-Pro software, Leica, an image analysis system which operates under the

same SEM PC hardware. Important stages involved in the study are:

Stage 1: In order to determine all constituent of coal, qualitative mineralogical work

is needed to be first performed coupling X-ray diffraction data with a detailed SEM-EDS

observation. This helps us in identifying various constituent of coal like C, H, O, N, P, S etc.

Stage 2: The second step comprised the acquisition of BSE and X-ray dot-mapping

images. Since the acquisition time for the dot images were relatively high, off-line

image processing was chosen to assure a better SEM electron beam stability during the

total acquisition period, which corresponds to almost 200 minutes for 30 fields per

sample. Incident probe current, brightness and contrast levels were set to allow the

acquisition of BSE and X-ray images with a good quality for further processing.

Because particle density per field is one of the major factors that directly affect

the total processing time, an ideal compromise is required to optimize the acquisition

time. The SEM magnification was adjusted for an average of 40 to 50 particles per

field, a situation in which some particles may touch other particles. For this reason, the

basic step in image processing is to individualize these touching particles.

Stage 3: A relatively complex subroutine should be applied to

discriminate the touching particles. Firstly, the detected image was eroded

and then skeleton and prune operations were applied in order to separate the

particles so they would not touch each other. Finally applying outline followed by

close and open operations to the particles may result in the dark lines of potential

touching areas. These lines should be subtracted from detected image by

logical operation, resulting in the final binary image of particles to be measured.

An image analysis routine should be developed in order to discriminate the various constitute

of coal and, later on, to perform modal and mineral liberation analysis. Detection,

identification and segmentation of the phases are the most complex issues, and the

routine should process a gray scale image plus external inputs as the X-ray dot image.

Gray level threshold from the BSE image can allow discriminating up to 6 binary

planes. Further, The acquired multi-element X-ray dot-mapping image needs to be submitted

to a gray level threshold that was intended to discriminate various constituent of coal.

Stage 4: At the end of the segmentation procedure each mineral phase was represented

by a binary image plane. Modal or quantitative phase analysis could be then performed

considering the area fraction measurements for the different binary planes (mineral

phase). The results of all fields should be accumulated in a file and, later on,

normalized to 100% regarding the volume percentage. The weight percentages are calculated

considering the mineral densities and their volume fractions.

This way, we able to find the various

constituent of coal and their composition and able to rank the various Indian coal on the basis

of quality and composition. Also, we able to do liberation analysis which helps to determine

suitable method for its beneficiation.

Posted in Technical.

No comments



Composition of Grid-enabled Web Services

Composition of Grid-enabled Web Services for

Integration and Sharing of Distributed Resources

through Web based Interfaces

By

Niraj Kumar

Software Developer

 Kolkata ' 700026.

West Bengal, India

E-mail: nirajkumariitkgp@gmail.com

Contact No: (Mobile).

© 2006 Niraj Kumar. All right reserved.

ABSTRACT

Traditional computer architecture and integration mechanism are more biased towards

tightly coupled client-server architecture and centralized databases. However with

phenomenal growth in web technologies and emergence of Web as world biggest

database has pushed human and organizations ability to utilize these resources effectively

to limits. Computer scientists, researchers and organizations throughout the world trying

to develop mechanism to make effective utilization of these distributed and

heterogeneous resources to gain competitive advantage in market. In this study, we

propose to develop a grid-enabled web services through web based interfaces, which may

considerably enhance our ability to share distributed and heterogeneous resources and

services among the institutions and organizations throughout the world.

Key Words: XML, SOAP, UDDI, WSDL, Web Services, Grid Computing, Java.

THE PROBLEM

To fulfill challenges posed by competitive world there is need to develop a system, which

can Integrate various distributed databases and web resources on the WWW and bring

these heterogeneous sources of data into common platform or in the form required by the

user. Also there is need to provide mechanism to allow sharing of resources and services

among various Organization / Institutions. Clients through portal interfaces should be

able to get required information on real time basis by seamlessly integrating various

resources/services spread across WWW and various Organization/ institutions and hiding

its implementation details from the user. Required system should be highly flexible and

scalable and services should be added and deleted at any time without affecting the

2

performance of the system. This required that Client and Servers must be independent of

each other.

Introduction

The organizations/ institutions of todays need to share and integrate various resources and

services to provide task specific requirements of a particular users and applications.

However, this is very challenging task because each of these resources and services have

different structures, contents, query languages and retrieved data in different format and

supported by different underlying hardware and network support. Furthermore, they are

prone to having their interfaces and formats updated without warning. Due to increasing

complexities of problems any user specific task typically requires to interact with

number of resources and services distributed over geographically distant locations and

under the control of different agencies. Many of them have security concerns and want to

share only limited resources with others. They also need flexibility in adding or deleting

resources and our proposed system should able to run even if some resources and services

will be no longer available for use or new resources and services get added to the system.

This requires that machines must be able to communicate with one another without much

human intervention.

Our current web applications follow the traditional client-server model of software

architecture and they are closely interrelated with one other, inflexible and tightly

coupled. This makes whole system dysfunctional if any changes is done in client or

server architecture independently. Also, our traditional database and information

integration systems (like Enterprise Resource Planning) are biased towards centralized

system where various resources of the organization are integrated using centralized

databases and mostly with proprietary software. This is contrary to the spirit of the Web

- a loose, open confederation of resources held together by simple protocols. So, to

address these problems many distributed environment technologies and standards like

DCOM, CORBA, RMI etc were came up during late 1990's. However, in reality these

are not suitable for the Internet, and introduce a degree of dependency and/or platform

issues. They are not able to completely eliminate need to write client application without

having to know anything about the architecture of participating distributed objects. In the

meantime advances in Servlet and Java Server Page (JSP) technologies and emergence of

standard like J2EE and .Net from Sun Microsystems and Microsoft respectively made

possible development of fast and relatively secure Web based application within the

realm of reality.

This set the stage for XML based Web services, which is an exciting new technology

standard that enables communication between heterogeneous computer systems. Web

services emerged as standard only in last 3 years. At its core, the technology is simply

XML moving from one computer to another in a form that each computer can reliably

process. It is a significant improvement to traditional systems integrations and it has

significant implication for any organization. Web services facilitates the ability to expand

computer to computer communication. They are developed supporting three primary

3

internet standards - Simple object access protocol (SOAP), Web Services Description

Language (WSDL), and Universal Description, Discovery, and Integration (UDDI)

directory. Currently these standard were supported by all major software technology

vendors and approved by the W3C. Grid based computer applications can be considered

as next level in this chain of events, which make possible even heavy duty task solvable

by using diversified and heterogeneous resources and services.

In this case study, we propose to develop a XML-based Web services and Grid based

solution using various Java based technologies, which can facilitate transfer and sharing

of various resources across the Organizations/ Institutions of the world through Web

based interfaces on the portal. We also want to make it possible to share and transfer not

only light weight resources and services, but also heavy weight resources and services.

Our aim is to develop a full fledged independent software product and methodology,

which can be directly usable to any portals which needs to share and integrate resources

over the Internet or among the enterprises and their partners and can be marketable as an

independent product in its own right.

GRID COMPUTING AND WEB SERVICES FOR THE

FUTURE

Imagine a scenario where just with an interface anybody will be able to run any program

without downloading any softwares or all barriers of platforms, databases and

networks vanishes . Grid computing system of the future should able to provide solution

to these problems. It is also expected that autonomic computing and smart network

technologies should emerge which should automatically able to detect changes in the

systems and accordingly able to take appropriate action. It is likely to provide user

friendly interfaces for remote job monitoring and show the status of the result computed

at each nodes in real time. More and more web based interfaces is likely to be added for

all activities related with grid computing. The primary reasons for these are because grid

systems require dynamic discovery and composition of services in heterogeneous

environments necessitates mechanisms for registering and discovering interface

definitions and endpoint implementation descriptions and for dynamically generating

proxies based on (potentially multiple) bindings for specific interfaces. WSDL supports

this requirement by providing a standard mechanism for defining interface definitions

separately from their embodiment within a particular binding (transport protocol and data

encoding format). Second, already numerous tools and support for WSDL processors

that can generate language bindings for a variety of languages and platforms. Third,

using http protocol for communication allows to communicate with any system sitting

behind firewalls as usually firewalls don't likely to block this port. Fourth, because any

computational intensive tasks require to interact with more than one computers at

geographically distributed locations, databases etc which requires algorithms for defining

work flows. Web Services Flow Language (WSFL) and MS XLANG, which is an XML

language to describe workflow processes among distributed and heterogeneous

environment offers excellent potential for this purpose.

4

The web services framework is likely to integrated with the grid computing system of the future

and already attempts in this direction is being made, however it is yet to matured to stage where

web services potential can be harnessed for grid computing fully. As grid computing has

started to leverage Web services to define standard interfaces for business services and

institutional needs. The grid is likely to provide virtual integrated environment to people

from different organizations and locations to work together to solve a specific problems.

This is a typical dynamic resource sharing and information exchange. The grid

computing platform is likely to allow resource discovery, resource sharing, and

collaboration in a distributed environment in more user friendly ways.

Future generation Grid enabled Web services should be able to accomplice the following

tasks:

The ability to more efficiently use computing power. Jobs can be sent to the node

that has the least amount of load.

Complex jobs can be broken up and run on multiple nodes in parallel, providing a

significant performance increase. This kind of structure is known as a

computational grid.

Large amounts of data can be stored in a structure that spreads over many

systems, yet still be accessed as if they were part of a single node. This structure,

similar to a federated database, is known as a data grid.

The ability to run different parts of an application on systems with different

characteristics. However, any grid system requires that user specific to their

requirements and problems

should submit the appropriate input files and define the problems algorithm in suitable

languages. This requires considerable domain expertise in the problem areas as well as

understanding of the processes involved in grid systems to able to efficiently use it.

Using SOAP for Communication in Grid environment

We need to develop a mechanism to send and receive communication to remote services

and resources in grid environment. Web services expose objects method via SOAP.

Following steps needed to be followed:

The client application builds a SOAP message, which is an XML document capable

of performing the desired request/response operation.

The client sends the SOAP message to a JSP page on a Web server listening SOAP

requests.

The SOAP server parses the SOAP package and invokes the appropriate method

and object in its domain, passing in the parameters included in the SOAP document

The request object performs the indicated function and returns data to the SOAP

server which packages the response in a SOAP envelope. The server wraps the SOAP

enveloped response object, such as servlet , which is send back to the requesting

machine.

5

The client receives the object, stripps off the SOAP envelope and send the response

document to the program originally requesting it, completing the request/response

cycle.

Managing Work Flow in Grid

Once the resources are discovered, Work flow in grid can be established using Web

Services Flow Language (WSFL) and MS XLANG, which is an XML language to

describe workflow processes and spawn them. WSFL specifies how a Web Service is

interfaced with another. With it, we can determine whether the Web Services should be

treated as an activity in one workflow or as a series of activities. While WSFL

complements WSDL (Web Services Definition Language) and is transition-based,

XLANG is an extension of WSDL and block-structured based. WSFL supports two

model types: flow and global models. The flow model describes business processes that a

collection of Web Services needs to achieve. The global model describes how Web

Services interact with one another. XLANG, on the other hand, allows orchestration of

Web Services into business processes and composite Web Services. WSFL is strong on

model presentation while XLANG does well with the long-running interaction of Web

Services. Web Services and resources can be declared as private or public.

Monitoring Remote Jobs in Grid environment

In a complex system like the grid, monitoring is essential for understanding its operation,

debugging, failure detection and for performance optimization. The monitoring system

must be able to provide information about the current state of various grid entities, such

as grid resources and running jobs, as well as to provide notifications when certain events

(e.g. system failures, performance problems) occur. Monitoring jobs require

interoperation between the monitoring system and other grid services. The running

application consists of processes running on hosts constituting the grid resource.

Processes are identified locally by the operating system by process identifiers

(PIDs). The local resource management system (LRMS) controls jobs running on hosts

belonging to a grid resource. It allocates hosts to jobs, starts and stops jobs on user

request and possibly restarts jobs in case of an error. It may also checkpoint and migrate

jobs between hosts of the resource which can be considered as a special case of job

startup. The LRMS identifies the job it manages by a local job identifier (LJID). To

monitor a job the monitoring system has to know the relation between LJIDs and PIDs.

There are various ways to accomplice this task and each grid system implements this in

different ways. The future generation grid systems should provide job submission, job

monitoring, job status and job output through web based interfaces to make it accessible

to common man.

6

System Architecture, Design and Modeling

Our architecture focuses on providing virtual integrated environment among

organizations/institutions through web based interfaces, which are easy to use, flexible

and secure. It provides mechanism to share large number of resources like video

lectures on real time and on demand, scientific databases, query to partner institutions,

lecture notes etc though our primary focus is on providing computation resources for

computation intensive scientific and engineering tasks. Our architecture aims to provide

support for platform independent and heterogeneous resources.

In the beginning our focus is on providing support for Java, C++/C and Fortan languages.

For scripting we intends to provide support for PERL, Shell Script, Dos Script. As far as

operating system is concerned we intend to provide support for windows and Unix based

platforms. To make this possible our architecture is XML based and intend to combine

web services concepts with grid computing concepts. Our architecture is based on

autonomic computing concepts and also intended to integrate intelligent network

technology concepts like Jini Technology with grid computing to make it possible for us

to able to dynamically sense changes in network environment and system should able to

take appropriate action automatically. Our architecture is capable of taking into

consideration any number of systems and services added/removed from the system in

real time. Besides it is capable of displaying status of jobs, output of the jobs at each

nodes in real time.

The job is submitted by the client to the web portal through a graphical user interface

(GUI). The web portal delegates the management of jobs to schedulers. A scheduler

divides a job into smaller tasks (in the case of an independent job, a task refers to the

subset of parameters that can be executed independently) and sends the tasks to the

resources for execution. Ease of use is achieved by encapsulating the system with an easy

and a well defined interface. The execution service provided by the resources is wrapped

inside a web service interface, hence it can be consumed easily by any user. The

scheduler encapsulates the complexity of the job scheduling into a web service interface.

This approach of using web service interface allows easy client side implementation. The

web portal provides GUIs for job submission and management, hence allowing the client

to submit and monitor jobs easily. The parameter file can contain a range or a list of input

values. The scheduler parses the parameter file and splits the input values so it can

distribute the job to many resource machines with different range or list of input values,

which is a subset of the submitted input values.

The status of the each subparts of the job submitted to each nodes is displayed through

web based interface at real time. It is also proposed to display the status about

performance of each nodes with respect to particular job to the respective clients through

web based interface. It will also display the available memory at each nodes, current load

at each nodes, average CPU performance of each nodes. After computation is complete

the final result is generated and displayed in real time basis through web based interface

and automatically an event is generated to send output to the clients through email or to

the computer directory of the client.

7

Simplified view of integrating two organizations resources for Grid

Communication Protocols(like HTTP/ HTTPS etc)

Information flow

Between two institutions

(XML over HTTP/

XML over FTP/

XML over HTTPS)

Data Data

CyberSWIFT Partner Organizations

Web Server and

Application Server

Database Server

Web Server and

Application Server

Database Server

WWW

Web Portal

Other resources

(Computers, Video

Lectures, Files etc

Other resources

(Computers, Video

Lectures, Files etc)

8

Grid enabled Web service Dataflow Diagram

Result

Find the Appropriate Nodes

Transfer the Data

Submit the Jobs

Collect the result

Web Portal

Client 1 Client 2 Client 3

HTTP

request

Authenticate with the

Server

Connect to the Server

Transfer the File

(XML over FTP)

Close the Connection

Integrate the result

9

Proposed Design Methodology

Design methodology to be adopted for this study is in stages. Each stages can be

considered as separate software modules. Primary challenges when designing Grid-based

Web services are to look beyond the traditional Client- Server paradigm, where client is

tightly coupled with server. Here we have to design client completely independent of

server, so that even if some changes take place in the server side (In this case which is not

in our control as many services can be withdrawn, while many new services can be added

without our knowledge). Then on server side, this system must able to give choices to the

other partner institutions regarding type of services and resources they want to share and

at any point of time able to withdrawn as well as add new services/resources. So this

kind of system design should be based on following design principles:

Clients and server applications should be independent from one another

Applications should be built by discrete components coordinating serverbased

modules.

Services and resources should be discovered by querying directories.

Services should be transient

Services should support extension and able to degrade when no longer

needed.

A mechanism to describe the Services (Example: WSDL implementation)

A mechanism to communicate with services (Ex: SOAP implementation)

A mechanism to submit the services and resources in registry (Implementation

of UDDI)

A mechanism to discover available services and resources (Implementation of

UDDI)

A mechanism to break the complex jobs into simple jobs to be submitted to

available and least loaded nodes. Depending upon the changes in the load of any

nodes it should capable of automatically redistribute the jobs to least loaded

nodes.

A mechanism to display the status of jobs submitted at each nodes in real time

with related statistics about memory status, CPU performances and uses and

changes in them at real time. It should also display the output displayed by each

nodes.

A mechanism to send back result to the client (Using SOAP)

Keeping into consideration these guidelines the system design stages should be

following:

STAGE I:

In this stage we propose to design user interfaces keeping into view that clients should

able to minimize the number of pages needed to be viewed and this should be

independent from the available services and resources.

STAGE II:

10

In this stage we have developed elementary and small grid computing systems for

elementary computations. We have evaluated various available grid computing systems

like Globus, Unicore, Candore, JCGrid, Jgrid, Optimal Grid etc. We also propose to test

all these grid systems by running sample jobs among number of windows and Unix based

environment. Idea is just to make a suitable decision about which of these grid based

systems are based suitable for our purpose. Here we need to take into account computing

facilities available or likely to be available in the future for this purpose, Which kinds of

operating systems all these runs, technological level of people involved in this process

and their commitment, type of network facilities available and security, firewalls and

other administrative decisions about how to allow access to our facilities to the clients as

well as partner institutions. Also we need to take into consideration all these

environments of our partner institutions and general state of affairs and understanding

about grid based system in the country, its current and future potential, and requirements

for such a system .

In this stage we also propose to develop web based interfaces for this kind of system for

job submission, job monitoring, output condition monitoring, output displayed specific

for the grid system we plan to adopt considering our suitability and capabilities. Once this

interface come up user should start the server and submit their jobs . Similar interfaces

will be provided to the partner institutions with the difference that no public interfaces

should be provided but only to transfer their resources to IIITMK or to submit the

services/resources to the registry.

STAGE III:

In this stage we implement the logic of web interface implementation using web services

concepts and suitable grid system. We also customize that system according to our

requirements and feasibility. We also combine computing power of various PCs in

windows and Unix platforms available. Make it fully operational and providing facilities

for remote jobs and status monitoring. Provide single web interface to submit any

computational intensive jobs. We also provide support for various available languages

and scripts as well as integrate the whole system with partner institutions and industry.

We also implement autonomic grid computing concepts and intelligent network concepts

with suitable technologies to see that our system should able to withstand the requirement

of future generation grid systems. We also optimize our whole system to get best possible

throughput and CPU utilization of available nodes for the purpose in geographically

distributed locations. We also aim to enhance our capabilities to apply web services

concepts for grid computing purpose. We also train people and students about these

technologies and systems and considerably enhance our abilities to use this system with

maturity.

STAGE IV:

In this stage we develop web based interfaces for many other grid computing systems as

well as continuously improve and upgrade our system as newer technologies for these

11

will be developed. In this stage we also try to make grid computing technologies

available to common man which requires very less technical knowledge of computers.

As future systems are likely to develop monitors of different kinds and capabilities in

terms of memory requirements, CPU capabilities, we aim to provide grid facilities

through all those devices. We also look into possibilities of developing cutting edge

technology and products in these areas as well as developing some algorithms for

defining work flows, job monitoring etc in the distributed environment. We also try to

look into developing the possibility of system where any body without downloading

softwares can able to use these softwares by sending appropriate program to them.

Summary and Conclusion

In this study, we have presented a framework for sharing distributed and heterogeneous

resources and services among the organizations/institutions. We have also presented

various modules of our framework. We have overviewed some current grid system

available and their usefulness through sample case studies taking into account strength

and weakness of the organizations. We have implemented sample SOAP, AXIS and Jini

based web services and made it available through our web based interfaces. We have

empathizes the importance of combining autonomic, intelligent networks, and web

services concepts with current grid computing systems to make it more effective,

efficient and reachable to the common man.

In summary, a simple grid computing system combining the power of Web Services,

autonomic computing, and intelligent network concepts with capabilities of combining

the computing power of twenty ' thirty computers of different platforms through web

based interfaces, which may be geographically distributed and hiding the complexities

of the implementations from its user, is recommended as grid computing system for the

future.

Challenges and Potential Research Directions

In this section we try to point out potential challenges and future research directions of

this study in stages.

As discussed in the assumptions, publicizing grid-enabled web services through web

based interfaces may raise security concerns. For example, if they are open to anyone and

everyone, the hackers and malicious users can overload the system by submitting dummy

jobs. We may think of providing these facilities through HTTPS or to develop different

level of security mechanism for such a system.

12

Developing browser plug-ins specifically for grid computing purpose is another

interesting areas which requires our attention.

Web services concepts has made significant advancement in last few years, however its

focus so far is only towards providing light weight services. However, we can think of

providing services of the kind where we don't need to download and install any software

to use it, but by requesting with appropriate input files anybody should be able to use it.

We can think of developing some these kind of services in future.

Developing pricing mechanism for making available these kind of services is another

important potential area, which can be explored.

Developing domain specific tools for using these kind of grid system in optimal way for

example drug design, earth sciences, bio-informatics etc are another potential area which

required further exploration.

REFERENCES

(1) IBM Developer Works

http://www-128.ibm.com/developerworks/webservices

(2) IBM OptimalGrid

http://www.alphaworks.ibm.com/tech/optimalgrid

(3) IBM TSpaces

http://www.almaden.ibm.com/cs/TSpaces

(4) JCGrid Website

http://jcgrid.sourceforge.net/

(5) PovRay Website

http://www.povray.org/

(6) Foster Ian, "What is Grid? A Three Point Checklist", Argonne National Laboratory &

University of Chicago, 2002, PP: 1- 4 .

(7) Foster Ian, Kesselman Carl, Nick J., Tuecke, "The Physiology of the Grid - An Open

Grid Services Architecture for Distributed Systems Integration ", OGSA draft documents,

Version: 6/22/2002, PP: 1-31.

(8) Balaton Zoltan, Gombas Gabor, "Resource and Job Monitoring in the Grid", MTA

SZTAKI Computer and Automation Research Institute 2003, PP: 1-8.

13

(9) Tantra J. W., Thu M. M., Heng F. C., "A Framework for secure execution of java

jobs in grid computing", Executive Summary, 2004, PP: 1-7.

(10)Jgrid Website

http://pds.irt.vein.hu/jgrid_index.html]

(11) Jini Network Technology Website

www.gini.org

(12) Sun MicroSystem Web Services

http://java.sun.com/webservices

(13) Apache Website

http://apache.org

(14) Globus Grid Computing Site

http://www.globus.org/

(15) Unicore Grid Computing Site

www.unicore.org

(16) Gridbus, Australia Site

www.gridbus.org

(17) MIT Thesis Web Site

http://theses.mit.edu/

(18) MIT Open Course Site

http://ocw.mit.edu

(19) Java World Site

www.javaworld.com

(20) Apache Tomcat Site

http://tomcat.apache.org

(21) Apache Axis Site

http://ws.apache.org/axis/

(22) Apache Soap Site

http://ws.apache.org/soap/

(23) VideoLAN Project site

http://www.videolan.org/

(24) Streaming Media World Site

http://streamingmediaworld.com

14

(25) OpenSSH Website

http://www.openssh.com/

(26) Marty Hall CoreServlet Site

www.coreservlets.com

(27)W3 School Website

http://www.w3schools.com

(28) IIT Kharagpur E-library Site

http://www.library.iitkgp.ernet.in/

(29) IIT Kanpur Online Thesis Site

http://www.iitk.ac.in/

(30)Computational Chemistry portal, IIITMK

http://comchem.in

(31) W3 consortium Site

http://www.w3.org/

(32) Professional XML, Wrox Press, 2000, PP: 797-835.

(33)Microsoft Website

http://www.microsoft.com/

(34) Kumar Niraj, Srivathsan K. R., "Enterprise risk evaluation and continuous

mitigation using the Fuzzy-Multi-attribute decision making ' A conceptual approach",

Under review by IISc Journal, 2005, pp-1-25.

(35) Kumar N., Bhattacherjee A. and Sarkar D., " Performance appraisal of coal mines

using Data Envelopment Analysis and Fuzzy Set Theory", Mintech, 2002, Volume 23,

No. 5, pp. 18-25.

(36) Kumar N., Bhattacherjee A., Chakravarty D. and Sarkar D., “Efficiency

measurement of mines using DEA and AHP”, TAMSEM, I.I.T. Kharagpur, February,

2004.

(37) Biomer Website

http://www.es.embnet.org/Services/MolBio/B/

(38)Reddy J. N, “An Introduction to Finite Element Method”, McGRAW-HILL

International Editions, 1993.

(39) Condore Grid Computing Site

http://www.cs.wisc.edu/condor

15

Posted in Software.

No comments



ERP IN MINING INDUSTRY ' AN INDIAN MINING PROSPECTIVE


 


By


Niraj Kumar


Sr Software Engineer,
 Bangalore , India


E-mail: nirajkumariitkgp@gmail.com


Contact No: (Mobile).


' 2002 Niraj Kumar. All right reserved.


ABSTRACT: Though concept of ERP is about one decade old and industries like


electronics , chemical, steel manufacturing, cement etc are fastly  implementing concept


of ERP ,still mining industry is far behind. This paper is an attempt of conceptual


implementation of ERP in mining industry.


Key words: MINING, ERP, MRP, ENTERPRISE, INVENTORY MANAGEMENT,


SALES & DISTRIBUTION.


28


2


Background - Human history is marked by measure changes for betterment of existing


facility, and making existing facility more efficient in every period. However attempt in


this direction has increased manifold in last few decades and particularly after the


invention of computers. Consequently, the first business activities to be computerized


were inventory control and purchasing. The need for software specifically designed for


manufacturing operations led to the development of MRP in the early 1970s and


subsequently to MRP II (manufacturing resource planning). But these systems failed,


which gave rise to the development of MES (Manufacturing execution  systems). Then


came demand forecasting and DRP (distribution requirements planning), Which paved


the way for supply chain management. ERP encompasses both MES and supply chain


management capabilities to use new technological opportunities brought forth by the


internet.


Introduction: In this age of global technology, global trade and nature of


competition are changing at faster rate than ever. Fast and accurate information is the key


for success. In this scenario, companies have to protect their profits and remain


competitive in a crowded market and with sophisticated customers. Like any other


industry, mining industry can't afford to far behind to these changes and ERP is a tool by


which chances of success increased considerably in these conditions.


To fully understand ERP and its implementation in mining industry, We need to


 answer certain question like what is ERP, what is need of ERP in mining industry ,what


are benefits of ERP implementation and many more. So in next few section we try to


answer these questions one by one.


What is ERP?


ERP is acronym for enterprise resource planning. An enterprise is a group of


people with common objective of making profits. But traditional mining industry is


divided into a number of sections like Surveying, Production Planning, Production,


Material requirement, Sales and Distribution, Finance ,Humane Resource Development,


Machinery Maintenance etc which has very limited interaction with each other and in


many cases isolated with each other. So very limited data are available about a particular


department to other departments and top management. As a result, Instead of taking


organization towards a common goal, the various departments end up pulling it in


different directions. Sometimes objectives of different departments are conflicting. For


example, Sales department forecast higher demand for coal .To meet this demand


production department require new machinery, but Financial department wants to reduce


purchasing cost. These may lead to disruption of normal  functioning of the organization.


But in ERP system , Data related with all the departments of the company are


stored in a central database, so that each department can access it and exactly able to


know what others are doing in no time. Why they are doing it and what are required to


move the company towards a common goal. The ERP system helps to accomplish this


task by integrating the information systems, enabling smooth and seamless flow of


information across departmental barriers, automating business process and function and


thus helping the organization to work and move forward as a single entity. Thus ERP


system able to improve efficiency of an enterprise drastically.


What is need of ERP in mining industry?


To apply any new technology or concept in any industry, We must first identify if


there is really a need for that and we can’t adopt a new thing only because others are


 doing the same. Important point which identify needs of mining industry presently are


' In this age of liberalization for survival, there is urgent need in mining industry to


operational excellence responding to the demand of customers for faster services


and lower cost compared to the competitors.


' There is need to customer intimacy leading to a closer relationship to the customers


and integrate the customers into the company’s core process.


' To ensure high quality or quality of mineral which is required by the customer.


' In many cases, high grade ore are depleting and so we have to move towards lower


grade minerals ,whose economic mining is possible only by improved technology and


increasing operational efficiency.


' Most of mining companies in our country are running  into loss due to lack of


transparent and efficient management. so there is urgent need for increased


transparency at every level of the industry.


' As gestation period is comparatively high in mining industry, there is urgent need in


reduction of these by increasing efficiency at all stages of (like exploration,


development etc). of mining.


' Able to adopt new technology of mining in efficient way like telemining (which is


the use of current state. of art technology, including u/g communications,


Positioning, process engg., monitoring and control systems to operate mining


equipment and systems) ,computerized truck dispatch system, navigation systems


(which supply information accurate to, the millimeter on the size, shape and location


for all underground working) ,which can be used with a CAD like system showing


the mine’s workings in real time.


' Able to use different mining software for exploration, reserve estimation, mine


planning, feasibility studies, operations and control and simulation work.


' To harness the potential benefits of information technology and internet.


What are benefits of ERP implementation in mining industry?


ERP implementation in mining industry has both direct and indirect benefits. Direct


benefits are reduction in lead time ,greater transparency and fast data transfer,on time


shipment, reduction in cycle time, increased worker efficiency etc to name a few. While


some indirect benefits in terms of better customer goodwill ,helps in increasing customer


base.


Requirements of ERP implementation and problems in fulfilling these requirements


w.r. to mining industry


' For successful ERP implementation support from all its users from lower level to


higher level is necessary. There is human nature to resist changes and chances of


elimination of jobs is also high. All these are big problems to deal with in developing


 countries like ours.


In Indian mining industry, at lower level there is illiteracy and also tendency to


obstruct changes at higher level due to many factors. These are the measure obstructs in


ERP implementation.


' Existing technology of mining, nature of business being done and hardware, software


and data base management systems infrastructure in the company is largely going to


influence the ERP implementation. However, most of the mines or mining


organization has very little infrastructure ,so it also creates problem in ERP


implementation.


' A team of experts is required who can understand the problem of mining industry as


well as pros and cons of ERP, but at present our country is lacking in this area.


 ' There must be willingness in high level of company and also people in management


must be motivator for successful ERP implementation. Excellent training facilities


and skills are required.


' High cost of ERP implementation. so it is always required to do a cost - benefit


analysis, before actually going in for ERP implementation. Important cost involved


are:


*High training cost of worker’s and other employees.


*Cost in data conversion i.e. cost involved in converting data from traditional


system to ERP system.


*High testing cost.


*Other high cost in increasing infrastructure for ERP and using latest technology in


every operation.


Important Components of ERP system in mining industry:


Important components of ERP system in mining industry can be Finance


deptement, Surveying departement, Production planning, Production, Material


management, Sales and Distribution etc. Most significant thing  about these modules are


information transfer is fully automated and beyond departmental barrier is possible in no


time. To understand it in better way let us take a very elementary example. Suppose a


small coal company receives a purchase order. In the non - ERP environment the order


entry clerk will enter the order details such as quantity of coal, quality of coal, address of


delivery etc. These order details are then passed on to the finished good coal storage


department, Where the in charge of the department checked if coal of required quantity


and quality are available or not. If coal are available, then distribution department load it


in trucks and send it to the customer. The accounts department of the company is also


notified, where bill will be prepared and sent to the customer. If coal is not in stock, then


through production planning department it will pass on to the production department


with time schedule for production and production department after checking with


materials management department if all materials such as explosives, drilling machines


etc are available and accordingly action is taken. Some machines may be not in working


condition and production might get delayed and help of machinery maintenance


department is required. Information transfer may take a week or even more.


However in an ERP system, these same activities will happen differently. As


soon as, the order entry clerk enters the order of coal into the system, the system


checks the inventory records and finds out whether coal are available or if the coal are


available, procedures are triggered automatically that will inform people in the sales and


distribution department and finance department. The information will contain the details


of coal to be shipped, the most economic route to the customer and so on. Also, the


system will trigger procedures in the financial modules so that bills are sent to the


customer. The information is transformed electronically through electronic data transfer


(EDT) and the payment are received electronically through electronic funds transfer


(EFT). If coal are not available, the production - planning module makes a production


schedule. Which is made available to the production, materials management and


machinery maintenance modules. So that everybody is prepared to start production as


per the production schedule. The materials requirement planning is done and any


material that is not in stock is ordered. The supplier is informed and associated processes


happen electronically. The machine maintenance gets the lists of machine required and


ensures that all of them are available. Thus, the production of 14 the coal goes on without


any hitches. An order entered into the ERP system by order entry clerk, triggers a whole


lot of procedures and automatically performs a host of functions. All these processes


take only a few minutes to complete.


After the order is received with a very short period of time, the coal are on their


way to the customer. If coal are not readily available, the customer is informed about it


and is given a delivery schedule. Other than the order entry clerk and people in the


distribution, production and maintenance departments, all the other tasks are done by the


system and that too automatically. In a Non - ERP environment, these tasks could take


days or even weeks to complete. since the ERP system stores all the data in a central


database and since the database is updated by all the modules on a real time basis, the


information available in the database is up - to - the minute. This integration of the


different business function and automation of the business processes and availability


 (which is accurate and current) is what makes the ERP system capable of producing


dramatic improvements in productivity and profitability. Now take a look at various


components of ERP in mining industry briefly.


Finance Management Departement: As soon as the initial indication of minable ore is


found work of Financial module starts.From economic evaluation of the project to cost


benefit analysis to exploration, development and exploitation at every stage financial


module plays an active role. It links to all departments of organization from Material


requirement to production planning ,production and Sales and Distribution to HR and R


& D section. This module is also responsible for cost benefit analysis of each activity


within the organization and also all cash inflow and outflow is done via this departement.


Financial module of a mining enterprise should capable of dealing with special conditions


that exists in mining industry like its Exhaustibility, Remote location, need for heavy


investment in infrastructural facilities, Pollution control measures, Quality constraints,


Price fluctuation and particular country tax regime like royalty, dead rent taxation,


custom duty, corporate taxes etc as applicable to the mining industry.


Production planning and production. Department


Production is key to any mining industry. All other activities evolved around this.


The key concept in operations management is transformation, the conversion of


resources into minerals. Managing of production units starts with planning the total


production system. The planning process for mining operations is very complex and so


incorporating all information is not an easy task in any ERP module. In ideal ERP system


we prefer our production unit to be make to order rather than make - to- stock. However


even after using the latest technology of wining coal it is not possible to follow make - to


order philosophy.


A typical mine production planning module in close interaction with


surveying department and data available from exploration, development etc should able


to do geostatistical analysis so that to estimate the quality, quantity with higher accuracy.


 It should also responsible for design of workings, equipment selection and able to give


exact time schedule for production.


A typical mine production planning module has following subsystems:


' Geostatistical analysis of available data


' Working design of mine production


' Selection of equipments for production


' Ventilation planning in case of U/G mine


' Production scheduling


' Plan transportation system inside the mine


' Inform maintenance department about maintenance of machineries


' Inform material management department about requirement of materials.


' Give update information to quality control department about expected quality of


coal.


After getting production schedule from production planning department


production department starts working. This module should able to ensure that all


provisions of Act, regulation etc are followed strictly and safety should given top priority.


Its important work should be


' Remove overburden in case of open cast mine


' Win coal


' Monitor wining coal , Monitor O/B Removal


' Assists in optimum inventory


' Responsible for adequent ventilation ,roof support in case of U/G mine


' Responsible for drainage of water from mine


' Responsible for power supply to the mine


' Give information about exact quality and quantity of coal supplied to sales and


distribution department.


' Estimation of life of various equipment and machineries.


' Responsible for transportation of minerals from mine to storage


Human Resource Management Department


Even today in our country mining industry is largely a manpower


driven industry as many units of mining industry like development ,drilling etc lack


proper advancement. Also there is large scale illiteracy at lower level and largely labour


force in our mining industry is in grip wine, tobacco and worst of all heavy loan taken by


them from private money lenders. Also safety ,health and proper understanding of mine


plans and Act, Rules, Byelaws and Regulations are necessary for efficient functioning of


mining industry. All these factors placed a heavy burden on HR management department


in mining industry. So HR module of ERP is capable of dealing with all these problems.


Apart from that HR management is responsible for new recruitments, Training of existing


as well as new manpower ,small health care provisions for its  employees, maintain the


profile of each members of the organization so that management is able to choose best


among them for any specific work. It should also responsible for spreading safety related


propaganda among workers and arranged meeting, outings, foreign trips etc for the


organization. It must also study behavior of the manpower against any specific cause and


able to record absentees, work schedule etc of any particular employee.


Machinery Maintenance Department


Machineries are heart of any mining industry. Any mining industry can’t achieve


excellence with unreliable equipment. In ERP system our target is to obtain quick


response production and elimination of wasteful production practices. In these


circumstances, machine breakdown and idle time for repair are not acceptable.


Any mining industry has a number of heavy and small machineries like Shovel, Dumper,


Loader, SDL, pump for water drainage ,Winding engine, Various types of fan for


ventilation, ome crushing and grinding plant in case of Metal mines, Gate end box etc.


Successful performance of all these machineries under mining condition is vital for


profitable mining. Operations of machinery maintenance department can be classified in


four measure categories:


' Maintaining a database about machineries with name of supplier, date of supply,


guarantee/warranty period, price, type, efficiency, case history of the equipment.


Maintaining the case history helps in future decision making about machinery,


deciding about maintenance schedule etc.


' Reliability study of all machineries under specific condition and based on that


suggesting a maintenance schedule , precaution required during operation,


maintenance required and active life time of equipment estimation and suggesting


means to improve reliability of a particular machinery or system.


' This department should also help the management in selection of machineries under


given condition by some scientific or engineering method like partial ranking method


or multiple attributes decision making system etc.


' Regular supervision of machineries, planning maintenance schedule and doing


maintenance work within the stipulated period ,so that chances of machinery failure


during production hour is minimal or negligible.


Materials management Department: Wide range of materials are required for


mining ,from components of different machineries to explosives, support system to any


other materials required for proper functioning of any organization. Materials


management department has various constraints like availability of space , EOQ etc and


within these constraints our target is to minimize cycle time and overall cost. Also for


each it should calculate economic order quantity and accordingly order should be placed .


Quality Management : It is unfortunate part of mining industry that we have no control


over quality of minerals. However, the quality of ores may be different at different


mines or sections in the same mine and by proper mixing the minerals, we can improve


the quality or supply the mineral of desired quality. Also quality department can ensure


the washing or processing of minerals if required and improve the quality of mineral


supply and take advantage over its competitor. The quality management priorities shift


from production planning to production and sales and distribution as well as listening to


 complain of customers about quality of minerals.


Quality management department of a mining enterprise should have following


components:


' Planning the production and after production activities in such a way so as t6o deliver


best possible quality to customer


' Inspection of the quality of minerals at various stages after the production and before


the delivery


' Controlling the quality and suggesting some washing etc if required


Sales and Distribution:


With today’s bossiness environment characterized by growing competition,


shrinking cycle times and accelerating pace of technological innovation, it is no longer


enough for any mining company to have good mineral quality and enough quantity, but


focus should now on core competencies and closer partnerships over the whole supply


chain. Customers want higher quality of mineral and shrinking lead time. To cope with


this ,mining companies should make a sales and distribution  model, which is customer


centric. In mining industry mostly contract handling is the standard practice. Contract is


nothing but agreement with customer. So this require that company must retain the


current customer base at the same time try to expand the existing customer base by closer


interaction with customers like mail campaign. It may led to success or failure. In case of


success , customer do enquiry about the minerals etc and finally orders from cont6ract is


obtained and delivery is scheduled. So sales and distribution component of an ERP


system should have following ingredients:


' Sales and distribution should have a database with information about total reserves,


quality of minerals, production rate, Detailed information about customers, materials


required by company and its supplier. With detailed information about how much


quantity ,quality of mineral is send to which customer with their cost, date and time


of delivery, so that all these information are available on time to decision makers of


the company.


' Making an efficient inventory planning, maintaining mineral stock on the basis of


reliable forecast and projecting delivery schedule.


' Transportation and shipping-Choosing and maintaining most efficient and economic


route to customer as well as ensuring proper supply of material to the company and


assigning these by using efficient assignment and scheduling algorithms.


Finally combining all these to obtain result closer to J.I.T. philosophy and to


minimize overall cost. Now take a look on the logical view of sales and distribution


system in a modern mine enterprise.


Apart from all these while practical implementation of


ERP in mining industry cost benefit analysis , project planning and its implementation in


phased manner ,end user training and always adaptability with new technology is


required.


Conclusion - Based on the above discussions following conclusions can be drawn:


' ERP system can help mining company increase its market reach with faster rate ,


improved production and distribution ,processed and more personalized interaction


with customer.


' This enables the mining company to have its executive times becoming available for


better and more productive causes, elimination of unproductive works, improved


decision making due to availability of timely and appropriate information.


' In Indian mining industry due to lack of understanding by mine managers that


benefits of any computerization project can be derived only after successful


implementation of the system. So to take benefits of ERP system, managers need to


shade off conventional management style, co-oporate for changes at corporate ,


operational lend during implementation. Otherwise chances of ERP Implementations


are very dim.


' For getting better results of ERP Implementation, mining industry needs


technological advancement in development, exploitation etc. So mining production


 unit should move towards automation.


' With increasing base of internet and expected increase in E- commerce, it is


expected that except in production, all other units of mining industry going to adopt


ERP system in near future.


REFERENCES:


1 Leon Alexis , 2000,’ERP Demystified’, TMH Publishing company Limited, new


Delhi.


2 Garg V.K. and Venkitakrishnan N.K.,1999,’Enterprise Resource Planning -


concepts and Practice ,’ Prentice hall India Private Limited, New Delhi.


3 Sarkar chinmoy, ‘ New Paradign healing for mining Enterprises,’ Management of


mining Machineery, MG MI -99,page -301-315


4 Sarkar Chinmoy,’ Managing transformation @ 2000 - A mining Perspective,’


page - 143-154, mining and marketing of minerals MGMI, MIMM’ 2000


5 ‘INDIA and IT. Application,’ coal international - mining & quarry world, Jan/


Feb 2000,


6 ‘Mine Management and control systems of the 21st century,’ 14 Coal international -


mining & quarry world, May/ June - 2000, Page - 8-9.


7 ‘Computerised truck Despatch ,’ By P.Raj, R. Trived and R.Nath, Coal


international mining & quarry world, May - June - 2000 Page -97-100.


8 Shuey A. Cott, ‘ Mining Technology for the 21st century,’ E & mj Journal, April -


1999, page -18-24.


9 ‘Minerals Terrier - the world’s first computerised minerals Estate Management


system,’ coal international journal, jan.1999, page -14.


10 M. wassell, ‘ Extrapolating seams and fault modelling using mining software, ‘


Coal international journal, Jan .1999, Page-5.

Posted in Technical.

No comments