On-Pre­mi­ses Data Keeping

Keep Your Data on Your Own Busi­ness Premises

On-Pre­mi­ses Data Kee­ping on Your Own Servers

You can main­tain the PLANTA soft­ware, inclu­ding the agi­le PLANTA pul­se com­po­nent on your own ser­vers on your busi­ness pre­mi­ses. For com­pa­nies in stron­gly regu­la­ted sec­tors with par­ti­cu­lar­ly high data pri­va­cy requi­re­ments, the on-pre­mi­ses ope­ra­ti­on pres­ents a good solu­ti­on. One of the gre­at advan­ta­ges of this type of data kee­ping as com­pared to SaaS is the high level of data secu­ri­ty. Becau­se if you store data local­ly, pro­tec­ted by your own fire­wall, you keep full con­trol over your data and their secu­ri­ty. Con­se­quent­ly, your sen­si­ti­ve data is not com­mu­ni­ca­ted out­side your company.

  • Your data remains with you
  • Bene­fit of licen­se purcha­se: afforda­ble licen­se models available
  • You deci­de whe­ther you want to update or not

In terms of soft­ware licen­sing, PLANTA offers dif­fe­rent licen­se models.

The PLANTA soft­ware is available as a 3‑tier / cli­ent-ser­ver-sys­tem or as a web-based appli­ca­ti­on. The cli­ent-ser­ver archi­tec­tu­re of the soft­ware kept on-pre­mi­ses with its pro­cess based approach offers you a par­ti­cu­lar­ly high degree of sta­bi­li­ty and lower resour­ce rivalry.

Is on-pre­mi­ses for you?

Read our blog artic­le to learn more about the advan­ta­ges and dis­ad­van­ta­ges of on-pre­mi­ses com­pared to SaaS

Tech­ni­cal Spe­ci­fi­ca­ti­ons and Architecture 

Cli­ent Server

The PLANTA soft­ware uses a Java based, pro­cess-based 64bit archi­tec­tu­re as cli­ent-ser­ver-sys­tem. It comes as a 3‑tier appli­ca­ti­on and con­sists of the fol­lo­wing components:

  • PLANTA pro­ject Server
  • PLANTA pro­ject Client
  • Data­ba­se

PLANTA pro­ject can be used on a vast varie­ty of plat­forms (ope­ra­ting sys­tems) and data­ba­se sys­tems and is func­tion­al­ly iden­ti­cal on all of them. The com­mu­ni­ca­ti­on bet­ween cli­ent and ser­ver is done via the TCP/IP pro­to­col.

Advan­ta­ges of the Cli­ent-Ser­ver Architecture:

The advan­ta­ges of the PLANTA ser­ver archi­tec­tu­re with its pro­cess-based approach are its high sta­bi­li­ty and lower resour­ce rival­ry.

Inter­faces and Integrations

Various inter­faces to ERP sys­tems, hybrid sys­tems, as well as indi­vi­du­al inter­faces can be con­fi­gu­red via the uni­ver­sal inter­face PLANTA link (e.g. Out­look Calen­dar, Goog­le Calen­dar, Micro­soft Pro­ject, SAP-RFC Calls, SAP Net­Wea­ver, web ser­vices, Python Api, Jira). Dif­fe­rent for­mats can be used for authen­ti­ca­ti­on and manage­ment of user mas­ter data, e.g. Ping­Fe­de­ra­te, Azu­re Acti­ve Direc­to­ry (LDPA), Ope­nID Con­nect, SAML, Ker­be­ros, OAuth. For the import and export of Micro­soft Pro­ject data you can use PLANTA MSP link. 

Export For­mats: .txt, .csv, .mpx, .xml, .html, Ado­be Acrobat

planta link integrations

Sys­tem Requirements/Required Storage

Fur­ther infor­ma­ti­on on sys­tem requi­re­ments and plat­forms for instal­la­ting and updating the PLANTA soft­ware, plea­se click here.

You have fur­ther ques­ti­ons con­cer­ning the PLANTA software?

Con­sul­tancy Appointments

Book your appoint­ment for con­sul­tancy here