CWS Initial

Actief sinds: 2017 Nov 20

Bass is een schoonmaakbedrijf en al meer dan 50 jaar een succesvol familiebedrijf. Het bedrijf bestaat al sinds 1962. Het succes danken we aan onze aanpak: maatwerk, efficiency, mensgericht ondernemen, klantgericht werken en vanzelfsprekend kwaliteit leveren. test speicher

bedrijfsinformatie

Leverancier :

CWS Initial

E-mail :

bass1@facilitydeal.nl

Telefoonnummer :

0402820090

Factuuradres :

Lichtstraat 3,
5611 BJ Eindhoven
Let op, het correspondentie adres is niet altijd gelijk aan het retouradres. Stuur een e-mail naar info@facilitydeal.nl voor een goedkeuring en het juiste adres voor het terugsturen van uw product.

BTW nr :

806650096B01

Bestellingen

Wil je meer informatie over jouw bestelling? Controleer de status van uw bestelling in uw account. Kijk bij de help klant voor meer informatie.

algemene voorwaarden


Remark: This kind of information don´t have to change often. Only 1 person should be responsible for it. Same information can only be adjusted or delete but the admin can add new ones. If it is necessary it isn´t a lot of work for them to add the functionality.

A service items are made up of components.

Most component classes related to the services are found in app/Lib/ItemOption/Class

 

For example cleaning service has 3 components, they are Cleaning space, Timing, Workprogram.

From these 3 components interaction a service price is calculated.

 

The initial data for these components data are added by the admin. They are stored in database tables relatively named after each components. For example:

 

item_option_cleaning_spaces

item_option_cleaning_timings

item_option_cleaning_workprograms

 

These also have model classes at app/Model/

 

These components view files are at app/View/Themed/FrontEnd/Elements/ItemOption/

and at app/View/Themed/Admin/Elements/ItemOption/ . They also have subfolder with the component names cleaning_space, cleaning_timing etc.. and all components have these form elements in them and have similar naming conventions.

option_buyer_form.ctp (used for buyer inputs)

option_detail.ctp (show details of options)

option_vendor_form.ctp (used for vendor inputs)

The main file for service is app/Model/AttributeSet.php where all the services are defined. It is where a service type is defined and its components are assigned. This model class also holds all the formula to be used for calculation of the service price per month. One formula deals with service calculator where a Sql snippet is used to calculate the price, this is used to find prices for the services that match condition all at once, and can be also sorted. The other formula is with components to find prices for each individual service items, one at a time. Both these formulae should result in the same calculated price for the same inputs.

There are 3 types of inputs for components, one from Admin, one from suppliers, one from buyers. Some may not require all 3 types. These inputs will be used to calculate the service price. The admin settings are stored in the component related models, whereas the supplier inputs are are stored at these 3 tables, with EAV (Entity Attribute Value) type storage, so every suppliers input are stored there.

 

item_options

item_option_choices

item_option_settings

The basic idea of calculating a service price is:

Join all these related tables fields with those inputs, (admin, suppliers) and also use the buyer input in a formula to calculate the price. The difficult part is for a service is, a sql formula must be devised that must join these tables multiple times. The individual service item calculation is relatively easier.

The components are a subclass of ItemOptionAbstract class. These classes are collected in a ItemOptionCollection class. This collection class in essential in manipulating these components as a group/collection.

You can find the different kind of services in the admin.

https://lh4.googleusercontent.com/zd_fHFr1XXjVrF_oHE1YwlNzo4A4dlH-NTHPHQf0VYzO0bBNTaNGmU34xAvTLSrrHt0z0U6e4z7OVAMjrlncmZWaFGeBRFtIK5Lc2CTdOduHFtjeDCgpoV6JU6n8d32PO4Pa498DzOLoR0gOPA

1.     processes

 

We visualize our main processes in flowcharts to give the admin and other employees  a better feeling how the platform is build and works (see google drive; flowcharts).

One example for a visualized process is the supplier registration process.