Information and Knowledge Management using ArcGIS ModelBuilder

Bartosz Wachnik
User’s requirement specification and relative functional specification as well as design
specification should be determined by one system.
The constructed system has to correspond with design specification.
Documents and relative tests placed in the right corner of the letter “V” must test all the specified
system parameters.
All the documents and requirements presented in the documents have to comply with legal
regulation for Good Production Practice.
In order to efficiently implement an ERP system in the “Life&Science” branch, the project has to be
realised on the basis of specifically designed methodics that comply with validation requirements. A
modified system life cycle “V” that adapts to specific ERP system requirements is most broadly used.
Table 2 presents and characterises stages of system life cycle according to the “V” model with
references to parallel ERP system implementation project tasks. Presented methodics enable to
complete prospective validation. An important step in system validation is creating a detailed
validation plan for an ERP system that is going to be implemented. This plan has to comply with the
Main Validation Plan in a “Life&Science” enterprise.
Table 1: ERP system implementation methodics in a „Life&Science” branch enterprise
Tasks in an ERP
implementation project
Defining ERP system
implementation contract
details i.e. implementation
range and implementation
budget
Signing an ERP system
implementation
agreement in a
„Life&Science” branch
enterprise.
Opening meeting, the socalled
Implementation
Planning Session
Training key users in
range of ERP system
functionalities.
Steps according
to the V model
User
Requirements
Specification
(URS).
User
Requirements
Specification
(URS).
(URS – User
Requirements
Specification).
Functional analysis (URS – User
Requirements
Specification).
Comments
Detailed identification of an ERP system implementation
range vs. system’s validation range Defining a business
process master list that is critical in reference to ERP
system validation. Identifying detailed number and range
of processes implemented and then validated in ERP
system will enable us to precisely define implementation
budget and validation budget.
Signing an agreement can take place after a thorough
analysis of a selected ERP system and implementation
partner. It is important to conduct an audit of the
implementation partner. According to the GAMP 4.0
manual it is crucial in case of ERP class systems.
Meeting of the whole project group on the implementation
partner side and client’s side aimed at discussing and
defining:
A detailed project realisation schedule
Notions that will be used in project’s realisation
Project’s organisational structure
Detailed implementation methodics
Project and quality management procedures
Project documentation
Training key users within the range of ERP system
functionalities. Training must be completed with
documentation containing detailed range of trainings,
knowledge transfer methods and training’s organisation.
Key users acquainted with the basics of ERP system
functioning will realise project tasks included in functional
analysis more efficiently.
The basis of launching a validation cycle possesses a
detailed specification of user’s requirements, the so-called
URS that contained detailed requirements for every
process included in the business process master list. In
the first stage „Life&Science” branch specialists create a
preliminary URS version. In the second stage, following
selection of the ERP system supplier, the team should
create a final URS version. Developed and approved
URS is a key computer system’s specification and should
be included in an annex to an ERP system
implementation contract. On the basis of URS, within
functional analysis realisation, we should develop:
ERP Functional Specification
ERP System Design Specification
496