This page describes a typical process from initial presentations over quotes and contracts to the actual implementation project and roll-out.
|
| Phase | Description |
| 1 | Presentations | Informal meeting or online sessions |
| 2 | Proposal | Concrete quote with fixed prices |
| 3 | Contracts | Negotiations of standard contracts |
| 4 | Implementation project | Actual delivery project |
| 5 | Roll-out | Organisational roll-out |
Typical acquisition and implementation process
We give presentations of Pure onsite or online. An onsite presentation takes 2-3 hours, and it is usually attended by IT-staff, Research Support, Research Management, research representatives, and the library. Online presentations take about 1 hour. Online presentations are for regular product demos, onsite presentations are for broader presentations with discussion of local issues; integration, legacy import, etc.
Presentations forms a basis for the institution to decide if a proposal would be a relevant next step.
A project proposal includes a full description of each activity in the project, a project time schedule, full and detailed costing, and a reserved production time-slot. The production time-slot will remain reserved for 1-2 months or by agreement. Importantly, all costs are fixed.
The proposal includes specifics about customisations, integrations, legacy import, special reporting, local hosting environment variables, user education, etc. We will need certain information in order to write a proposal. We will interview for the necessary details; sometimes via phone conferences or online sessions, sometimes on physical meetings. Also, we might require data samples from integration sources and/or legacy sources. Areas of particular importance such as legacy import and systems integration is discussed and clarified to some extend before the proposal is written in order for it to be precise and in order to allow prices to be fixed.
Obviously, presentations and proposals are free of any charges or other commitments.
If the proposal is accepted, there will be two contracts: One is an Implementation contract, which includes the details from the proposal. The other is a License contract for the purchase of the Pure software itself. Both contracts are standardised international contracts that have been used with other projects in all countries.
The implementation project itself is executed by our Implementation Team. This is a team specialised in handling the particular challenges of implementation projects. Dominated by short-term success criteria and customer considerations, Implementation is a very different discipline compared to Standard Software Development, which is dominated by success criteria such as long-term sustainability and architectural viability.
In chronological order, a typical Pure implementation projects comprises the following phases and activities. Our proposals include detailed descriptions of each of these activities, but please contact us in case of any questions:
| Project activity | Who | Duration | Comment |
| PREPARATION | . | . | . |
| Establishing the hosting environment | Customer | 2 week | A) |
| Remote access to hosting environment | Customer | B) | |
| Remote access to integration sources | Customer | C) | |
| Testing the hosting environment | Atira | 1-2 days | . |
| Delivery of legacy data to Atira | Customer | 1 week | . |
| Start-up workshop | Atira | 1 week | D) |
| Approval of work-shop minutes | Customer |
| |
| . | . | . | . |
| CUSTOMISATION | . | . | . |
| Customisations in Atira environment | Atira | 1-2 weeks | . |
| Test and approval of customisations | Customer | 1-2 weeks | . |
| Configurations in Atira environment | Atira | 1 week | . |
| Test and approval of configurations | Customer | . | |
| Integrations in Atira environment | Atira | 2-4 weeks | . |
| Test and approval of integrations | Customer | 2-4 weeks | . |
| Legacy import in Atira environment | Atira | 1-3 weeks | . |
| Test and approval of legacy import | Customer | 1-2 weeks | . |
| Advanced PurePortal (if included) | Atira | 1-3 weeks | . |
| Test and approval of portal | Customer | 1-2 weeks | . |
| . | . | . | . |
| INSTALLATION | . | . | . |
| Installation in local environment | Jointly | 1-2 weeks | . |
| Installation workshop with IT-staff | . | ||
| Test and approval of local installation | Customer | . | |
| . | . | . | . |
| POST-INSTALLATION ACTIVITIES | . | . | . |
| Reporting workshop | Jointly | 1 week | E) |
| Education of all advanced roles | Jointly | 1-3 weeks | . |
| Education of help-desk staff | Jointly | . | |
| Education of IT-staff | Jointly | . | |
| Education of web-staff (if included) | Jointly | 1 week | . |
| . | . | . | . |
| FINAL TESTS AND APPROVAL | . | . | . |
| Acceptance test | Jointly | 1 week | F) |
| Service level test | Customer | 1 month | G) |
Activities in Pure implementation projects, grouped by phases
A) This will be done based on specifications from Atira, that were provided in the proposal document. The relevant staff is also welcome to contact us before or during setting up the environment.
B) it is recommended that Atira have remote access to the hosting environment for the duration of the project.
C) Ideally, Atira will have remote access to the integration sources. If that is not possible, data dumps, views, or warehouses can also be used.
D) The start-up workshop includes a complete walk-through of the entire system for all participants of the project. The data-model is also introduced, as are areas such as roles/rights, workflows and classifications. All customisations are discussed as well, and any agreements to supplement or specify the proposal are logged in the minutes.
E) The reporting workshop teaches the use of the reporting module. This is placed late in the project in order for it to be based on own data.
F) + G) The acceptance test confirms that all agreed functionality has been delivered. The Service level test renders it probable that everything works with full data loads and many simultaneous users. In addition to this test, Pure solutions come with 12 months of guarantee after project completion for added comfort.
While we are happy to give our help and advise, the roll-out remains largely a management task and is carried out by the institution itself. User-groups are good forums for discussions about roll-out best practises and experiences. Also, recent years have seen much customer-made introduction materials for roll-outs, and many institutions are happy to share such materials as well as their experiences.
Atira A/S
Niels Jernes Vej 10
9220 Aalborg Oest
Denmark
Phone: (+45) 96 35 61 00
VAT no. 26835526
General info: info@atira.dk
PURE support: support@pure.atira.dk
Other support: support@atira.dk
We specialize in customer- and domain-specific solutions for knowledge intensive sectors. Our area is server-side applications and integration in service oriented architectures.
Our development and project management method is SCRUM. We work in a number of European countries.