RE: [Phpgroupware-developers] XSLT-version

[Brian Johnson]

I don't use this app since we don't do this type of work but I have looked at
this app in the past

It is VERY slick (ie very good)



sigurdne (address@hidden) wrote:
>
> This is a brief description on the property app - which is the production
> system for maintenance management for Bergen Housing and Urban Renewal (BBB),
> a public housing company comprising 5000 dwellings:
>
> Location - submodule
> A metadatabase keeps track of dynamic configurable location hierarchy - which
> is configurable in both width and depth - that is: one can define as many
> levels as one like - and each level can also have as many attributes as one
> would like.
> The location hierarchy is linked with foreign keys with - and querying a
> certain level generates a query with proper join statements to the top of the
> hierarchy. The sql-query is stored in a cache table for later use.
>
> Entities
> Also a metadatabase (separated from location to) defines entities (as
> components, equipment, reports ..) which links to other entities or locations.
> Entities are organized in class of entitity and entity_category: each
> entity_category is represented by their own table.
> Example: entity_1 is equipment, entity_1_1 is elevator, and entity_1_2 is fire
> alarm system
>
> There is a set of submodules that all is controlled by ACL2 (also: each
> entity_category emerge as its one submodule when defined)
>
> Project - submodule
> A project is a collection of orders/contracts. The project is linked to a
> location or entity (e.g equipment). Projects is separated in orders/contracts
> that could be subject to bidding contest amongst vendors. Each order is linked
> to its parent project and to a vendor - and consists of a series of
> work-descriptions to perform and / or items to deliver. An order can be
> defined as simple as a brief description of simple tasks - or as a detailed
> complex tender document with a full blown deviation auditing system up per
> record in the contract.
> A typical order can be saved as a template for later re-use.
> Orders is sent by email to vendors - which in return sends the invoice (also
> on email)
>
> So far 23000 orders is served by the system.
>
> Deviation / requirement
> Maintenance need that can wait is recorded in the deviation submodule - and
> categorized within six themes by scores within severity, probability and
> consequence.
> These themes (safety, aesthetics, etc) is subject to weighting to produce a
> overall score to help prioritizing among requirements
>
> Electronic invoice handling - submodule
> Invoices is imported and handled by the system (according to users role -
> controlled by ACL2) before exported to accounting system.
> The import filters currently handles cvs ,BBS and XML files (the vendors has
> agreed on a template)
> The export format is defined by a drop-in filter per target system(currently
> two systems is supported).
>
> Vendor agreements
> There is two types of vendor agreements:
> 1) Service agreement - which is actions to perform at locations or equipment
> 2) Pricebook pr type of work or item to deliver.
> All elements in the agreements is subjet to price indexing (with history) over
> the agreement period.
> The agreements supervisor is alerted by a user-configurable alarm (email
> triggered by async) when it is time to evaluate the agreement for termination
> or renewal.
> When calculating an order - one can either choose elements from the prizebook,
> or add custom entries.
>
> Document register/Drawing register - submodule
> Files is stored using vfs - linked to location or entity_category (as
> elevator)
>
> Helpdesk - submodule
> Built from tts - tickets is linked to location or entity. One can start
> (several)projects and (configurabel) entities (as reports) from the ticket -
> with two way links in the project(s) and the entity.
>
> A slightly modified version of ACL2 is implemented in the app property as it
> is not properly implemented i api.
>
> Sigurd
>
>
> >===== Original Message From Kai Hofmann <address@hidden> =====
> >> Please don't break the xslt support - all my work the last
> >> two years is
> >> dependent of this to work.
> >
> >Please identify exactly the modules you have worked on.
> >
> >
> >
> >*********************************************************
> >Wir freuen uns auf Ihren Besuch:
> >     SYSTEMS 2004: probusiness in Halle B3, Stand 345
> >     LinuxWorld 2004: probusiness in Halle 4, Stand B06
> >
> >Besuchen Sie ausserdem unsere Technologietage
> >am 05.10./07.10./21.10.04 in Hannover, Dresden und Berlin
> >*********************************************************
> >
> >
> >
> >
> >_______________________________________________
> >Phpgroupware-developers mailing list
> >address@hidden
> >http://lists.gnu.org/mailman/listinfo/phpgroupware-developers
>
>
>
> _______________________________________________
> Phpgroupware-developers mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/phpgroupware-developers
>
>