PCS offers a dedicated development team to integrate Primavera products to other applications, such as accounting and ERP systems. Our team consists of qualified, experienced Primavera consultants and programmers from PCS and Primavera Australia. This provides our customers with national support but a local focus.
Major Integration Projects
Recent projects include:
 |
SAP and P3e |
 |
P3e and Maximo |
 |
Expedition and in-house financial systems |
Integration Products
Primavera has a range of products designed specifically for the integration of Primavera products with external systems. They are:
 |
P3e Link |
 |
Primavera SDK |
 |
Expedition TGIF |
 |
Expedition SDK |
 |
Expedition Link |
 |
Ra |
The Integration Process
The integration process consists of six phases:

Phase 1 - Feasibility
The Feasibility phase consists of the following sub-phases:

Sub Phase 1.1 Requirements Definition
The client and PCS will discuss the general requirements of the proposed system as well as present environmental, equipment and staffing issues.
Sub Phase 1.2 Solution Definition
PCS will develop and define a solution to meet the general requirements outlined in 1.1 above. This will include a brief schedule of proposed development activities. There may be more than one solution defined.
Sub Phase 1.3 Client Approval
The client and PCS will discuss the solution(s) prepared in 1.2 above. PCS will explain the reasoning behind any proposed solutions and this gives the client the opportunity to check that the project meets the general requirements and that the project is feasible.
Phase 2 - Specification
The Specification phase consists of the following sub-phases:

Sub Phase 2.1 Technical Specification
PCS will develop a detailed technical specification for the project. This will define the responsibilities of both the client and PCS, project timeframe and cost, hardware, software, programming and training requirements.
Sub Phase 2.2 Proto Typing
A prototype system will be developed defining system architecture and user interfaces.
Sub Phase 2.3 Client Approval
The client and PCS will discuss in detail both the Technical Specification and proposed Prototype. The client is encouraged to study the proposal carefully and discuss the proposal within their organization before any further work is to be done.
Phase 3 - Development
The Development phase consists of the following sub-phases:

Sub Phase 3.1 Programming
PCS will develop any required interfaces or stand-alone programs. The coding for these programs will be written in the programming language specified in the Technical Specification.
Sub Phase 3.2 Technical Support Documentation
Technical documentation for all programming, hardware and software specifications will be provided. This will allow for any future maintenance or upgrading to be done with minimal downtime.
Sub Phase 3.3 End User Documentation
A user guide will be provided for end users showing what screens will be available and a basic outline of how the system works.
Phase 4 - Testing
The Testing phase consists of the following sub-phases:

Sub Phase 4.1 Unit Testing
Each individual module of the project will be tested, allowing for all possible errors.
Sub Phase 4.2 Functional Testing
All modules will be combined to form the entire system, which will then be tested as a whole.
Sub Phase 4.3 QA Testing
The system will be tested in its proposed environment using actual data provided by the client.
Sub Phase 4.4 User Acceptance
Once PCS has established that the system is working correctly, the client will have an opportunity to fully test the system to prove that it meets the requirements of the Technical Specification.
Phase 5 - Installation
The Installation phase consists of the following sub-phases:

Sub Phase 5.1 Rollout
The system will be installed by PCS working alongside a client representative, usually a member of the IT department. Depending on the system, the installation may be phased (one module/section at a time), parallel (the client uses both old and new systems for a period of time) or a full cutover (old system stopped and new system started on same day).
Sub Phase 5.2 Data Migration
All live data will be backed up before being loaded into the new system. At this point, data integrity checks will be done to ensure that no data corruption has occurred.
Sub Phase 5.3 User Training
A user training program will be developed for the client. This training may be carried out by PCS for all client staff or, if the client prefers, training of key personnel only who will then train other users within their organization.
Sub Phase 5.4 Project Sign-off
Once the client and PCS are satisfied that all of the requirements of the Technical Specification have been met, along with any variations, the project will be signed off as being complete.
Phase 6 - Benefits Realisation
PCS will continue to work with the client to ensure that their system operates as required and that the expected benefits are being realised. These benefits may not be evident for several weeks or months, however PCS will continue to work with the client and provide assistance where necessary.
[ go to top ]
|