RPS2014. Production Management Software for industrial SME's

RPS2014(Vision)

Statement of DirectionUpdated: January 2014

Enero 2014. RPS2014 Statement of direction

Ibermática, S.A. RPS Development TeamJanuary 2014

The information contained in this document is placed at the disposal of RPS distributors for the solepurpose of providing information on the strategic lines followed in RPS software evolution and to reporton any new functions and changes incorporated into the 2014 and subsequent versions of RPS,developed according to the criteria of IBERMÁTICA, S.A. as the owner and holder of the software. Theuse of the contents of this document for any other purpose is forbidden.

The contents of this document and the implementation or incorporation of functions in RPS softwareproposed or identified herein are not binding on IBERMÁTICA, S.A.. We reserve the right to modify,change or adapt the contents in any way. Nor do we guarantee the accuracy or completeness of theinformation contained herein, as modifications may have been made subsequent to its dissemination.

In no case may the contents of this document or the information hereby made available to RPSdistributors be interpreted as a binding commitment on the part of IBERMÁTICA, S.A.. Nor may it beused by authorised distributors of RPS to make any guarantee, offer or otherwise commitIBERMÁTICA, S.A. and/or the RPS software to third parties.

All rights are reserved. IBERMÁTICA, S.A. Is the owner of RPS and of the documentation associatedtherewith, including the contents of this document.


Introduction

RPS must consolidate its futurewhile remaining true to its originsas a specialised, high-performance ERP solution for industrial companies”


General points. DriversIntroduction

User-friendliness

A solution with a functional concept anda user interface designed to be familiarand easy to accept and learn.

Industry-oriented functions

A high-capacity tool that providesspecialist support for industrialcompanies in planning, managementand analysis.

Fast implementation

A product that can be deployedextremely quickly and updated easilyto keep the initial investment aliveover time.

High configurability

An app that is functionally powerfulbut can be parameterised andmodulated to meet the needs of eachcustomer.

4The driving ideasThat resulted in the creation of RPS and continue to mark out its future


General points. Strategy lines for RPS 2014Introduction

High-performance engineering

Going further into one of our distinguishing features, with a more functional, more native, more universal integration between the world of engineering in CAD/PDM/PLM and ERP.

Business strategy modelling

Designing new tools to enable our clients to draw up graphic models of their businesses, arrange the implementation of their underlying processes and assess their performance in an environment of continuous improvement.

CRM

Creating a new CRM module for a sales environment, designed to supplement the current functions for quotes and potential customers.

Document management

Reinforcing our document management capabilities by means of categorisation, versioning, security and semantic search functions.

Strategy linesFor RPS2014, the new version on which we are currently working …

Big Data

Integrating the data generated by the ERP and that generated in the business world into RPS and providing clients with the solutions required to interpret it.

HTML5. Multiplatform interface

Trying out a new interface that enables users to interact with RPS using any device, anywhere.

6The


Business strategy modellingStrategy lines for RPS2014

ReflectionWith the advent of RPS2014 business strategy modelling isset to become the backbone of all RPS projects: from thepre-sales process up to implementation, from initial design tomaintenance over time. The extensive use of templates indrawing up high-level business models and their KPIs, low-level process orchestration, continuous improvement andassessment and the integration of all the stakeholders in thevalue chain (clients, suppliers & employees) make up thefundamental core for the development of the RPS of thefuture.

…in RPS2014…

We multiply the capabilities of our current workflow moduleby incorporating the following functions:

• Business strategy: definition & recording bymanagement areas of your strategy plan, your goals,your indicators and your initiatives.

• Catalogue of processes: process hierarchies, definition& design (versions, stakeholders, tasks, applications),indicators, analysis of problems/consequences andsolutions.

• Process improvements: definition of areas forimprovement, improvement actions and follow-up.

• Queries & follow-ups: process maturity, RASCI matrix.• Upgrades from RPS2013: Subprocesses, Workflow

Designer 4.5, Incident management.

Business strategy modellingDesigning a business, orchestrating its running & assessing its performance

… and what next? 2015/16/…

In the future we plan to make the app even easier and morefully integrated. We intend to draw up templates per types ofbusiness, to define KPIs based on standard and to cater forintegration with standard tools in the definition andmanagement of processes.


ReflectionIntegrating ERP and the world of engineering continues to bea major strategy line for development in RPS2014. RPSneeds to develop a new connector that is more closelyintegrated with ERP, where the functions are developed withnative RPS Development Tools. Integration with CADsystems needs to be more universal so that two-waycommunication is possible via web services with productssuch as Solidworks, but also with Autocad and SolidEdge.Integration with RPS needs to go deeper and include theinitialisation of RPS workflows from engineering anddocument management.

…in RPS2014…

The following functions are to be included:

• Universal integration with any CAD software via thedevelopment of add-ins.

• A configurable data mapping system for the twoenvironments.

• Consolidation & extension of integration features:articles, structures, allocation of times to projects &production tasks, allocation of materials. Quality controlguidelines, graphics, meta-data set displays.

• Integration of the RPS document manager with PDM.

High-performance engineeringMore native, more universal & deeper integration between engineering and ERP


We plan to go into more depth as regards the integration ofother engineering solutions with RPS functions & modules,by e.g. assessing the possibilities of integration betweentechnical manual creation & maintenance systems with ourRPS industrial maintenance & technical assistance module.

High-performance engineeringStrategy lines RPS2014


ReflectionWithout forgetting who the intended clients of RPS are, andwithout neglecting any of our original driving ideas, we wantRPS to reflect the new techniques and solutions knowngenerically as “Big Data”. By extending the capabilities of oursolutions in the field of BI, we plan to tackle two newobjectives in RPS2014: extracting & structuring internal RPSinformation and data from other “social” sources andinterpreting the correlations and the information generated bymassive data analysis and data mining with a view toproviding our clients with a faster, easier way of reachingconclusions concerning the future prospects of theirbusinesses.

…in RPS2014…

We are working on the following for RPS2014:

• Data mining and behaviour pattern interpretation tables for sales, purchases, production and industrial maintenance.

• Definition of study areas for each module on which the study of correlations can be based.

• Definition of the algorithm to be used and its links with pre-defined data capture.

• Definition of an interpretation panel using desktop panels, on which we aim to define the graphics and the source of the data to be used.

Big DataExtracting data, assessing patterns and drawing conclusions


We plan to compile our experience in social business in RPSby integrating information from social networks into the BigData module. We will seek to work out how to identify who iswho in these external data sources so that they can be linkedto the transactional data generated in RPS.

Big DataStrategy lines RPS2014


ReflectionWe want our customers to spend their time making decisionsabout their data and documents, not looking for them. Wewant RPS to be not just a transactional repository but also adocument container. We want RPS to enable users tocategorise and index documents which are both internal andexternal to the app, but above all we want RPS to allowsemantic searches in its document repository that returncontextualised, guided results weighted in line with what theuser actually wants. Our intention is that the semantic searchengine should enable users to categorise and shareknowledge much better in the fields of industrialmaintenance, production, technical assistance, etc.

…in RPS 2014…

We further explore functions such as:

• Structuring & visual categorisation of folders &documents

• Corporate group repository accessible from membercompanies.

• Extended security: Roles, permits.• Location & versioning of documents.• Integration with RPS Workflow.• Add-in for Outlook. Storage & indexing of e-mail.

Document managementBetter organising, categorising & indexing so time is not wasted on searching


We plan to go further, incorporating artificial intelligencetechniques for automatic document categorisation, thusenabling our clients to save time in the indexing andcategorisation stages too.

Document managementStrategy lines RPS2014


ReflectionWe want to complete the functions of RPS in the fields ofquoting and sales opportunity follow-ups with thedevelopment of a new CRM sales module. This module is tointegrate the options already available in earlier versionssuch as RPS Workflow associated with quote management,Mobility, etc. Our aim is to help our clients to produce betterquotes, better follow ups of opportunities generated, etc. Andin short to generate more business.

…in RPS 2014…

In CRM we are working on the following areas:

• Entry channels• Types of activity. Sorting of types of activity.• Reasons for closure. Reasons for success or failure.• Potential clients.• Competitors.• Sales methods.• Opportunities.• Activities.• Quotes.• Task agendas per user.• Add-in for Outlook.

CRMCompleting the functions for better knowledge of the market


As with the rest of RPS, we plan to work on mobile versionsof these tasks and applications. The idea is for part of thetasks in workflow, potential clients, activities, etc., to bemanageable from any device at any time.

CRMStrategy lines RPS2014


ReflectionThe Cloud, Windows 8, Smartphones, Tablets and a greatmany other new technologies, user interfaces and devicesare now available to our ERP clients. Regardless of whattechnology they use, we believe that as industrial companiesthey will benefit greatly from the potential for interacting withERP from multiple devices and locations. With RPS we alsoplan to invest in this line of development, and are working toassess various alternative technologies, mainly Windowsand HTML5.

…in RPS 2014…We are now developing a pilot on HTML5 as a model fortrying out the new waves in technology on these RPSfunctions:

• Administration: Roles, users.• Workflow: Outstanding task manager.• Storage: Articles, inventory queries & locations.• BI.• Quality: Supplier assessment, Nonconformities.• Production: Data capture & attribution of production

times.• Purchasing: Suppliers, quotes & orders.• Maintenance: Agenda, maintenance orders, incidents.• Planning.• Projects: Agenda, attributions.• Sales & CRM: Quotes, potential clients, rates.

HTML5. Multi-platform interfaceInteracting from any device, anywhere.


The rapid spread of new devices continues to surprise us all,and it is not easy to make long-term provisions. What iscertain is that in the years (or perhaps months or even days)to come we will need to be alert to what changes andstrategies are best suited to the needs of our type ofcustomer.

HTML5. Multiplatform interfaceStrategy lines RPS2014


Timeline RPS2014

June – December 2013 January – February 2014 September 2013 -June 2014

June 2014

Reflection on:•Strategy lines for development•Review of new technologies•Prototyping•Feedback on actual implementations of version RPS2013

ReflectionReflection ConcretionConcretion ReleaseReleaseDecision-making

Decision-making

Sharing & decision-making:•Road-map publication•Convening & deployment of Technical Committee•Decision on what functions to include in and exclude from the final version

Activities concerned with: • Development of prototypes• Development of applications &

modules• Quality control• In-house pilot testing• External pilot testing

Final launch:• Final announcement of

availability• Commercial launch• Technical launch, training for

partners• Availability to clients


Take Part

Send us your comments at:[email protected]

Rate this content andhelp us to improveWe hope you are as thrilled as we are with the build of the new version of RPS. Nowis your chance to read about it, assess it, think about it and send us your comments

Thank you!

RPS2014. Production Management Software for industrial SME's

Technology

owner of rps

rps projects

creation of rps

rps software evolution

strategy lines

disposal of rps distributors

subsequent versions

authorised distributors