NemisFs how to implement?

Shoot first, ask questions later. NemisFs requires only a few days of preparation after which NewFrontiers or a business partner will do the installation of the standard model with selected modules.

The standard installation is obviously not an exact fit however has proven to be an excellent starting point for any BI project. Because the NemisFs has been designed for people to use they can rapidly start playing with the data and in an iterative process change the application to fit their needs.

This method is much more effective than the process of lengthy and costly interviews, specification writing and company specific development.

Quick Results

Fast results enable business users to deliver fast feedback. From this feedback the QuickStart can in most cases be quickly added to and extended, such that within a few weeks the business users can have a production reporting application tailored to their specific needs, based on their feedback, derived from real-world data.

Development Cycles

Starting with a NemisFs project does not mean that after the implementation there will be no more change. In fact we expect needs and requirements to evolve and we call them cycles. In most cases a NemisFs based project goes through 3 cycles until the formal "go-live".

Cycle one (1) -- Pilot, "try and proof". In this phase the focus is on the "technology", i.e. can NemisFs deal with multiple sources; can the application easily change and grow; how flexible are ad-hoc querying capabilities; do the deliverables fit with the high level business requirements.

Cycle two (2) -- Validate, "check and understand". In this phase the focus is on the actual usage of the "technology", i.e. make sure that the business users validate the reports which should include their first round of feedback.

Cycle three (3) -- Implementation, "fit for production use". In this phase the detailed reports are reviewed, data and analysis errors are corrected and the users sign off the end-to-end design.