Documenting GSO projects

Documenting GSO projects

Record specifications, engineering decisions and operational results in a documented file

The implemented project is the place of communication between idea, calculation, equipment and real experience of use. A detailed introduction of a project shows the reader why a type of fountain was chosen, what limitations there were, what solutions were implemented and what the result was in operation.

For the municipality, information related to maintenance, consumption and quality of people's presence is important. The consultant pays attention to the logic of the design and how to coordinate the disciplines. The manager of the shopping center also wants to know how the fountain is coordinated with the architecture, activity of the complex and the operation plan.

The project introduction file should provide the answer to these needs in a specific structure. The final image is the beginning of the introduction; The technical specifications, the execution narrative and the documentary result complete it.

This chapter presents a suggested format for introducing GSO projects. The words inside the brackets are the place to insert real information and should be completed from the documents of the same project.

41–1. The purpose of introducing the project in a reference book

Introducing the project in this book has four tasks:

1. Showing the application of technical topics in real conditions; 2. Explaining the relationship between the client's needs and the implemented solution; 3. transfer of design, construction and operation experiences; 4. Providing comparable information for future projects.

To achieve this goal, each case must answer five questions:

• In what place and for what need was the project formed?

• What type of fountain and what specifications were chosen?

• What was the role of GSO and other project agents?

• How was the most important technical or executive issue resolved?

• With what evidence is the result of implementation and exploitation recorded?

In the example of introducing the Al Liwan project by OASE, sections such as the challenge, design idea, project implementation, result and project certificate are separated. This method is a useful example for organizing the project narrative. Introducing the Al Liwan project on the OASE website ^[280]

41–2. Choosing the right projects for the book

It is better to choose projects based on diversity of experience. Size or visual impact is not the only selection criterion.

A small fountain with a suitable solution for maintenance access may be more educational for the reader than a large project with only the final image available.

In the projects section of the GSO website, there are categories such as musical, rhythmic, dry, floating, classical, and German. This category can be the starting point for selecting samples; Then the projects are selected based on the quality of the documents and transferable experience. GSO urban fountain projects ^[281]

It is better for the final collection to include both flagship projects and conventional projects whose conditions are repeatable for many municipalities and employers.

41–3. Project ID and the role of executive agents

The first part of every introduction is a short and accurate birth certificate.

Determining the role of the company is important. Supply of equipment, system design, complete implementation and reconstruction of a part of a fountain are different services and should be registered with their exact title.

If the GSO has done only part of the project, that part should be introduced. For example:

"The scope of GSO's services in this project included [providing nozzles and lighting, building a panel and setting up a control system]."

In the Crystal Fountains project collection, the projects are presented as examples of cooperation and are categorized according to uses such as urban, commercial, historical and garden. This approach is useful for simultaneously recording the type of project and the role of agents. Crystal Fountains Project Collection ^[282]

41–4. Description of the location, the client's needs and the purpose of the design

After the birth certificate, it should be clarified why the fountain was built in that place.

This part should be short, but it should say three things:

The initial state of the place: the existing use, the movement of people, the quality of the public space, architectural elements and the limitations of the place.

Employer's need: creating a gathering point, night show, renovating a dilapidated space, completing the commercial area or returning the existing fountain to operation.

Design response: choice of form, type of establishment, display scale and relationship with the environment.

Sample text structure:

"The project site is located at [location] and had [documented site status] prior to implementation." The client set [primary requirement] as the project objective. Accordingly, a [type] fountain with [short description] arrangement was chosen to coordinate with [surrounding traffic, architecture, or activity].”

In this part, a difference should be made between the project goal and the realized result. "Increasing visitor retention" can be a design goal; Its realization requires post-operational evaluation.

Place Image 41–1 — Introducing Place

Choose a wide picture of the project that shows the fountain, buildings or surrounding space and the path of people's presence at the same time.

*Suggested subtitle: "Waterfall [project name] in relation to [significant feature of surrounding environment]; [city, year of image registration]"*

41–5. Record dimensions and technical specifications

The technical table should be extracted as much as possible from the construction plan, list of installed equipment and delivery documents.

The number of nozzles and the number of independent groups are not the same. Several nozzles may work with a common pump and steering wheel. Therefore, these two numbers should be recorded separately.

In multi-outlet nozzles, it should also be specified whether the number means "nozzle set" or "water outlets". Without this explanation, comparing projects becomes misleading.

The height of the launch must also have a base. Design height, maximum recorded in test and typical display height may vary. If the number is obtained from the measurement, the test conditions and measurement reference should be mentioned.

41–6. Separation of pump power, electric power and energy consumption

In the introduction of projects, the term "fountain power" is often used without definition. To avoid ambiguity, the three types of information should be recorded separately.

Nominal power of the pump motor

The power recorded on the plate must be reported by its nature. The output mechanical power of the engine should not be considered the input power of the system without conversion or measurement.

Electrical input power

This number can be related to a single device, a set of devices or the entire input of the fountain. It should be clear whether it includes lighting, filtration, sound and auxiliary equipment.

Energy consumption

Energy is related to the time period and is reported in kilowatt hours; Such as consumption of a show or daily consumption in a specific program.

To express the daily consumption, it is not enough to write "Electricity consumption: [number]". The more precise wording is:

"The energy consumption recorded in the [interval], with the execution of the [program] and the total [hours] of work, was equal to [number of] kilowatt-hours. This value includes [included circuits]."

If measurement data is not available, the calculated number should be published as an estimate.

41–7. Introducing the control system, light and display

This section should explain how technical capabilities have been translated into visible experience.

For control, the main information is:

• The method of controlling pumps and nozzles;

• Number of independent groups;

• protocols actually used;

• Operating modes;

• The reaction of the system to conditions such as lack of water or wind;

• Operator facilities to select or change the program.

Mentioning the name of a protocol alone does not explain the full capability of the system. For example, the presence of DMX does not indicate how many independent bands there are or whether the show is timed to the music.

In the introduction of lighting, the relationship between light and water form, points of view and architecture should be explained. The number of lights, color, radiation angle and installation location are complementary information to this narrative.

For a musical fountain, specify whether the show is preset or uses some other method to communicate with the music. The duration of programs and editing facilities should also be included if there is a document.

Figure 2-41 — Arrangement of water and light

Prepare a simple project plan. The groups of nozzles and lighting are marked with limited colors and numbers. Beside the plan, a photo of the same arrangement at the time of operation should be placed.

*Suggested subtitle: "Equipment grouping association with display form in project [name]."*

41–8. Duration and important points of the schedule

The duration of the project should be reported with a clear start and end.

These intervals may vary:

Some activities are done at the same time; Therefore, the total period of design, production and installation is not necessarily equal to the calendar period of the project.

If there is a stoppage due to site unavailability, plan change or access restriction, it should be separated from active work time. This explanation helps the reader interpret the project duration in real terms.

Recommended format:

“The equipment was installed within [number of] business days. The calendar interval was from [date] to [date] and included [description of stoppage or parallel activity, if any].”

41–9. Registration of challenges and technical solutions

The educational value of the case is formed in this section. The challenge must be specific, relevant to the project and explainable.

Statements such as "the project was very complex" do not provide enough information. It is better to write the issue, its effect and the decision taken separately.

Example of a template that can be completed:

“Due to the [specified limitation], the implementation of the [initial solution] faced a [technical effect] problem. After considering the [options], the [final decision] solution was chosen. This decision was implemented by executing [the details] and the result was checked through [testing or observing the document]."

The issue of the challenge can be depth limitation, level difference, maintenance access, wind, water quality, equipment noise, limited execution time or coordination with the existing structure.

It is not necessary to write a large number of challenges for each project. One or two issues that are explained in sufficient detail are more valuable.

Figure 41–3 inset — Solution details

A workshop photo and a section or schematic of the discussed details should be placed together. Identify which component has solved the problem with a simple notation.

*Suggested Caption: "Details of [solution name] to address limitation [topic] in project [name]."*

41–10. The result of implementation and exploitation experience

The result of the project should be checked at several levels.

Delivery result: Has the system been delivered with the agreed specifications and have the defined tests been performed?

Operating result: In what schedule did the fountain work, what maintenance needs did it have, and what modifications were made after it was put into use?

Spatial and social outcome: What change in the way the place is used has been observed or measured?

Economic or tourism outcome: Is there data on visits, time spent, events or business activity?

A crowded place in a photo alone does not prove increased traffic or economic success. Change in business activity may also be influenced by other factors such as collection openings, promotions or events.

If the evaluation is not done, the correct statement is:

"Little data on [the index] was available at the time of this filing."

41–11. Registering the consent of the employer and users

Consent must be reported along with its subject, source and time.

The employer's satisfaction with the execution of the contract, the user's satisfaction with the ease of maintenance and the visitor's satisfaction with the space experience are not a single indicator.

For qualitative comments, record this information:

• Speaker's name and title, if publishable;

• Comment date;

• Subject of assessment;

• Registration source;

• Exact text or a summary that is explicitly introduced as a summary.

The advertising sentence should not be written in quotation marks and in the name of the employer, unless the same sentence is actually registered by him.

If a survey was conducted, the number of valid responses, the method of selecting the respondents, the date and the scoring scale should be mentioned. The satisfaction percentage of a sample should not be generalized to all users without explanation.

Suggested report format:

“In the assessment conducted on [date], a [number] of valid responses about [item] was recorded. The result based on the [description] scale was equal to [result]. This assessment is related to [group and scope]."

41–12. Pictures before, during and after the performance

The collection of images should show the way the project was formed.

For before and after comparison, the viewing angle and frame range should be as close as possible. The change of season, time of day, or the presence of a special event should also be considered in the interpretation of images.

The caption of each photo should include the name of the project, location, stage, date and visible subject.

Subtitle example:

“Project [name], [city]; Installing collectors of the display circuit before the final covering of the pond, [month and year]."

A generated image or 3D reconstruction can be used to illustrate a detail, but must be labeled as a "concept image," "schematic reconstruction," or "design model." To document the actual execution, archival images of the same project are the basis.

Figure 41-4 — Execution process

Three or four frames of the same size before, during and after the performance should be placed in a row or two facing pages. The chronological order and brief explanation of each step should be clear.

41–13. Template ready to introduce any project

The following format is recommended for completing the project file.

Project title

[Official Project Name] [City and Location] — [Fountain Type] — [Completion Year]

Short introduction

“The fountain [name] was implemented at [location] with the aim of [primary need]. The selected solution includes [short description of form and function]. The scope of GSO's services in this project has been [actual services]."

birth certificate

Technical specifications

The need and limitation of the place

[A paragraph about the client's request and conditions affecting the design.]

The main challenge

[Description of the specific problem and its effect on the project]

Technical and executive solution

[The decision taken, the reason for the choice and the implementation method.]

Test and delivery

[Related tests, date of delivery and recorded result.]

The result of exploitation

[Review period, performance status, consumption or other documented results.]

Employer or user feedback

[Recorded comment with source and date; if any.]

Transferable experience

[An obvious tip that is useful for similar projects.]

Pictures

[main view]

Figure note from the source manuscript

Previous image

Figure note from the source manuscript

Image during execution

[Technical details] [Final view day or night]

Basic documents

[ID of the construction plan, list of equipment, minutes of the test meeting, operation report and ID of the pictures.]

41–14. Additional information for different types of fountains

The common format should be maintained, but each type of fountain requires some specific data.

In the renovation project, before and after pictures and specifications should be related to the same scope and comparable conditions. A reduction in consumption is only properly reported when the change in work schedule and quality of service is also explained.

41–15. Suggested arrangement of project pages

For most projects, four pages can provide a good balance between images and information. This number is a proposal and changes with the importance and documents of the project.

For a shorter project, the same structure should be summarized in two pages. In a more complex project, an additional page is better devoted to details or results.

A link or QR code can also direct the reader to the page of the same project and the actual video of the show. The digital content must have the project name and date and remain consistent with the printed version information.

41–16. Preparing and controlling the file before printing

It is better to collect information from the time of design and implementation. It is more difficult to reconstruct the case after the work is done, especially for hidden facilities and workshop decisions.

Incomplete information should not be replaced with zero. Three situations must be distinguished from each other:

• Does not exist: that equipment or feature is not installed in the project.

• Not measured: the target index has not been measured.

• Verified information not available: There is insufficient evidence to enter a value.

Before printing, the name of the project, the role of agents, technical specifications, dates and images should be matched with the basic documents. If the system is upgraded in later periods, it will be determined which stage the file belongs to.

Each file should convey a clear experience to the reader at the end; For example, the effect of positioning modification on maintenance access, the effect of changing grouping on display, or the role of documentation in reducing troubleshooting time. This experience turns the project into a usable part of the knowledge of fountain design and implementation.