Company, branch, and department arrive ready. A single site skips the choice; the record takes the branch location.
Going Live
Same Portal, Two Setups
Release 6.0.0. In the cloud the data sits on onerisistemi.com servers. On a company server it stays with the organization.
- Product line
- Fast go-live
- Data on-premise
- Update management
Cloud
Cloud Service
Several organizations use the same product. Each organization’s records, people, and settings stay apart. Your IT team does not host the application server.
This public site stays on the main address. The organization portal has its own address. Central administration opens the organization, grants record areas, and watches them.
- Server onerisistemi.com servers. The organization does not run a server.
- How Many Organizations More than one. Records do not mix.
- Public Site Stays open on the main address.
- Organization Address Short name plus domain. Form: short-name.domain
- Second Path The short name opens the organization’s own address. Staff sign in there.
- Areas That Arrive Suggestion and ISG arrive on. Kaizen and success stories arrive off; they enter the menu when opened.
- Account Central administration opens the organization.
- Care Expired sessions, old logs, and activity older than 90 days are removed on a schedule.
- 01 One Organization The root address goes straight to that organization’s sign-in.
- 02 Several Organizations The root address opens organization choice. Each organization opens under its own short name.
- 03 Package Taken areas are installed. An area you did not take has no record, menu, task, or notice.
- 04 Guide Administrator steps are written down. Sample organization accounts are not part of this install.
- 05 Mail and Brand Language, color, and email templates are organization settings. The typeface is one.
- 06 Cleanup Scheduled care also runs on the company server. The same job can be run from the administration desk.
Data Stays With You
Company Server
The software is installed on the organization’s server. The package contains only the record areas you take. The root address is the sign-in screen. These public pages are not on that install.
The administrator guide arrives in writing with the install. Passwords, keys, and server paths are not printed on screen. No package is downloaded from outside; the release is planned with the organization.
Side by Side
Same Work, Different Place
The screen does not change. The rows below are what the setup itself changes.
| Topic | Cloud Service | Company Server |
|---|---|---|
| Data Location | onerisistemi.com servers. Organizations stay apart. | The organization’s server. |
| Home Page | This public site. | Sign-in. These public pages are absent. |
| Organizations | More than one. | One or more. |
| Address | Short name with the domain. | The company’s own address. |
| Record Areas | Record areas are ready. The organization opens or keeps them off. | Only taken areas are in the package. |
| Suggestion and ISG | Arrive on. | Arrive on when they are in the package. |
| Kaizen and Success Story | Arrive off, and can be opened. | If they are in the package, they arrive off and can be opened. |
| Review | The same published order. | The same published order. |
| Updates | The release is applied on onerisistemi.com. | Planned with the organization. No package download. |
| Guide | Central administration. | Written steps that arrive with the install. |
Catalog
What Is Ready at Opening
Setup does not open an empty shell. Organization, record areas, a published order, and point rules arrive ready; the organization fills its own names and people.
Arrives on. Default sharing is public; the organization can keep it internal.
Arrives on. Near miss sits inside this area; it is not a separate menu row. Default visibility is internal.
Arrives off. When opened it enters the menu, the record, and notices.
Arrives off. When opened, default sharing is public.
Seven stops arrive published. A step can be closed and renamed to the procedure. A record already in motion keeps the old order.
Each step has accept, revision, or reject. The reject reason comes from a list; revision returns the same record to the author.
The point rule is written in administration. It posts to the author’s balance on submission and on approval.
The days on a step are an organization setting. A record past its day is marked in the list.
Color and language belong to the organization. Submission and revision letters use the organization template.
Capabilities
System Features
The record, the review, the notice, the reward, and the report live in one portal.
Suggestion, kaizen, near miss, and success story open from the same door. A draft has no number; once sent, the file receives a number, a unit, and an author.
Each step writes acceptance, revision, or rejection. The reason stays on the file, and the record lands on the next owner’s list.
Approved work is routed to the implementation owner. At close, the work done and the actual result are written on the same record.
The author is reminded of a similar record and a missing field. The reviewer sees a repeated topic before opening the file.
Task, decision, and revision notices follow the role. A step that does not concern the person does not open on their list.
Comments, questions, and noted handoffs stay on the record. Chat and the notice flow do not scatter; the reason sits in the file history.
The point rule is set by step and module. Approval and closing points land on the balance; the rule changes from administration.
The catalog shows the point price and the quantity left. Opening a request holds the points; rejection refunds them.
An open record on the same topic is shown while a new file is opened. The reviewer separates the repeat and links it to the existing file.
A closed file stays in the archive with its number, module, and result. The lesson learned is read from the success story.
How long a step has been waiting is read from the list. A task past its time rises on the owner’s queue.
Photos and documents stay attached to the record. Review does not scatter into email attachments; the file opens from the same record.
The menu follows the role and the open areas. Who sees a record and who writes the decision is read from one table.
Each organization’s records are kept apart. An unauthorized user does not see another organization’s file.
Screens are used with a keyboard and a reader. Focus, color, and target size follow the same order on the work screen.
Comments, questions, and stars stay on the file. The average is read on the record page; the discussion runs until close.
Filter by number, module, status, unit, and the person waiting. The record is not hunted by file name or in the inbox.
Status, module, and participation are read on a chart. The period list, close time, and point total come from the same report.
Steps, decision forms, roles, the catalog, and mail wording change without code. An existing record is not broken by that change.
Who changed what, and when, stays on the record history. The decision, the points, and a setting change are read from the same trail.
The organization announcement lands on the panel. The person who can publish manages the text. An announcement does not replace the record.
Limits
What We Do Not Do
No Automatic Updates
The install does not take a new version on its own. In the cloud we apply the update. On a company server the update is planned with you.
Passwords and Addresses Stay Private
Sign-in details and server addresses are not shown on this site or on administration screens. Setup guidance is sent in writing.
Demo Does Not Touch Your Data
The public demo is only for this site. Sample accounts and sample records are not copied into your own install.
Questions
Setup Questions
Where does the data sit?
In the cloud, records are kept on onerisistemi.com servers and organizations stay apart. On a company server, the data sits on the organization’s own server. The portal screens match.
Does a company server include this public site?
No. The root address goes to sign-in. One organization opens that sign-in directly. Several organizations open a choice first.
What is the short name for?
It builds the organization address. In the cloud the short name joins the domain. Staff sign in at that address.
What happens to a closed record area?
It stays out of the menu, tasks, and notices. A record cannot be opened. Kaizen and success stories arrive this way. Suggestion and ISG arrive on.
Who applies updates?
In the cloud the update is applied on onerisistemi.com. On a company server it is planned with the organization, on the internal network. The install does not download a package from outside.
Can the review order change later?
A new publication is pinned to new records. A record already in motion keeps its old publication. A step can be turned off.
How do several companies sit?
Under one roof, several companies, each with branches and departments. A person’s membership ties them to a company, branch, and department.
What does a pilot opening mean?
A limited group opens records and walks the steps first. When order, access, and mail settle, the rest of the organization is added.
Going Live
Which One Suits You?
Share IT policy, data location, and launch timeline; we will confirm the fit.