27.06.2013 Views

Information and Knowledge Management using ArcGIS ModelBuilder

Information and Knowledge Management using ArcGIS ModelBuilder

Information and Knowledge Management using ArcGIS ModelBuilder

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Bartosz Wachnik<br />

Table 1: Criteria of ERP selection <strong>and</strong> implementation partner selection<br />

Criteria of ERP systems selection Criteria of implementation partner selection<br />

1. Ensuring required specialized functionalities enabling<br />

servicing of business process that will be subjected to<br />

validation, e.g.<br />

• Possibility of completing pick-up process <strong>and</strong><br />

warehouse release process <strong>using</strong> the First Expire<br />

First Out method.<br />

• Warehouse management system has to ensure<br />

the so-called “traceability”: the possibility to fully<br />

monitor the history of raw materials, materials,<br />

wares <strong>and</strong> products from the moment of entry to<br />

the warehouse, through production cycle to<br />

product to product release including information<br />

on who subsequently received the product. This<br />

functionality is crucial when it is necessary to<br />

identify raw materials that are used as ingredients<br />

of a drug that has to be withdrawn from the<br />

market. In this case the traceability functionality<br />

enables us to associate a required batch of<br />

contaminated drugs with raw materials batches<br />

that have been used in the drugs production.<br />

• Managing the batch of product status in a quality<br />

control context. A System on the basis of defined<br />

statuses, should manage the raw materials’ <strong>and</strong><br />

half-finished products’ flow within warehouse<br />

structure.<br />

• Managing access right <strong>and</strong> possibility to monitor<br />

modifications of specific records in ERP system<br />

database.<br />

2. Architecture enabling ERP system integration with<br />

other IT systems of industrial automation e.g.<br />

scales. This type of interface responsible for<br />

integration should be validable if required.<br />

3. The possibility of validating an ERP system within<br />

a defined range.<br />

4. The possibility of further ERP system<br />

developments in accordance with validation<br />

allowing low cost system maintenance, the socalled<br />

TCO (Total Cost of Ownership)<br />

User Requirments<br />

Specification URS<br />

Functional<br />

Specification FS<br />

Design<br />

Specification DS<br />

Computer system design<br />

1. Competence of implementation partner in terms of<br />

implemented functionalities complying with validation<br />

requirements.<br />

2. An implementation partner must have access to a<br />

group of consultants who have knowledge <strong>and</strong><br />

documented experience in completing similar ERP<br />

implementation projects.<br />

3. Organisational structure of project should ensure<br />

knowledge transfer concerning an ERP system’s<br />

functionality from an implementation enterprise to<br />

key system users.<br />

4. A partner should complete an implementation project<br />

in accordance with ERP system implementation<br />

methodics concerning validation conditioning both<br />

prospective <strong>and</strong> retrospective. Methodics should<br />

includes e.g.<br />

• Dividing the whole implementation process into<br />

task that should be precisely defined.<br />

• Full documentation that has to be completed<br />

during project’s implementation, e.g. tests script<br />

used in acceptance testing.<br />

• Verification procedures concerning user<br />

requirements specification completion.<br />

• Adjusting procedures <strong>and</strong> approval procedures<br />

for functional specification <strong>and</strong> user<br />

requirement specification.<br />

• Procedures for creating <strong>and</strong> testing parameters<br />

setting.<br />

• Procedures for creating <strong>and</strong> reviewing source<br />

code in case of programming.<br />

• Procedures for testing software <strong>and</strong> its<br />

documentary evidence.<br />

• Reporting procedures concerning error <strong>and</strong><br />

discordance elimination in created software.<br />

• Software version control procedures.<br />

• Procedures concerning enhancing functional<br />

changes during project implementation.<br />

Process<br />

Qualification PQ<br />

Operational<br />

Qualification OQ<br />

Installation<br />

Qualification IQ<br />

Figure 2: Life cycle of the “V” computer system in reference to its validation according to the GAMP<br />

manual (Hojdyś K. 2004)<br />

The system under-construction <strong>and</strong> then operation moves across the “V” line starting from the top left<br />

corner to the top right corner of the line. We need to underline to underline that this is a st<strong>and</strong>ard IT<br />

system life cycle <strong>and</strong> it has to be adapted to the ERP class IT system requirements. Important general<br />

rules (Hojdyś K. 2004) of practical “V” model usage are:<br />

Documents in the left <strong>and</strong> right corners of the letter “V” have to be mutually coherent.<br />

495

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!