StatusQuo

This software, allows an Organization to maintain a database of status relatively to its operational objects. To do so, it uses two important concepts: 1. Two forms of accessing, Organizational and Operational, defined as: a. Organizational: Read Only access to all objects owned by teams subordinated in a established Hierarchy, including those owned by itself (New Way); b. Operational: Read and Write access to all objects owned by teams associated to the same Class/Operation (Old Way). 2. Contextualization of the information regarding the activities of an Organization, allowing the attribution of Status accordingly to Classes reflecting such contexts. The previous two concepts allow you the following: 1. Like in a file system, where files/objects may be accessed accordingly to ownership, with Organizational access, it is possible to access a file/object that is owned by a group/team subordinated in the Hierarchy. By other words, reflects the hierarchical organization independently of the direct permissions/associations to those files/objects defined by a given Class; 2. Anything is subject to Status, from devices to tasks with Contextualization it becomes possible to attribute status to classified Objects such as reports, tasks or vehicles, and those status may be defined like concluded, delivered or allocated. This software with the two concepts described, makes it possible to take control of the state of affairs in the Organization on real time without great effort or complications on permissions, simple because it takes advantage of Hierarchical access. It seems to me an extremely useful tool to companies that have too much contracts going on and too little means to audit its activities. The software right now is more a prototype, but I think that already has a lot of potential just as is!