Visual management of sags and incidents gathered in distribution substations for power quality management

Monitor a distribution network implies working with a huge amount of data coining from the different elements that interact in the network. This paper presents a visualization tool that simplifies the task of searching the database for useful information applicable to fault management or preventive maintenance of the network

Mantenimiento preventivo

Análisis y diseño de una aplicación informática que cubre las necesidades del mantenimiento preventivo de una planta de producción.

Sistema per gestionar les incidències d'un servei d'informàtica amb una arquitectura J2EE distribuïda en tres nivells

Tant en la meva etapa d’estudiant com en la meva curta vida laboral, he participat en el desenvolupament de varies aplicacions de gestió, tant d’escriptori com web, que majoritàriament sempre estaven dividides en tres capes però en dos nivells: la base de dades i l’aplicació, que contenia tant la lògica de negoci com la vista. Des de fa temps he tingut la curiositat i la necessitat d’intentar desenvolupar una aplicació de gestió que estigui distribuïda en tres o més nivells, separant el model de dades i la lògica de negoci de la vista. Crec que el treball de fi de carrera és idoni per desenvolupar-la. L’aplicació a desenvolupar anirà destinada a la gestió d’un servei d’informàtica, que s’encarrega de resoldre les incidències, inventariar i realitzar el manteniment preventiu dels equips informàtics d’una o de varies empreses. Es crearà una aplicació que contindrà el model de dades i la lògica de negoci. També es crearan dues aplicacions clients: una aplicació d’escriptori que donarà accés a totes i cadascuna de les funcionalitats del sistema i una aplicació web que oferirà un accés lleuger i des de qualsevol ubicació a les funcionalitats d’explotació del sistema. Per últim, també es crearà una altre aplicació web que s’encarregarà de generar els llistats sol•licitats per les dues aplicacions clients. D’aquesta manera també es centralitzarà la gestió dels llistats de les aplicacions del sistema. Per desenvolupar el sistema, s’utilitzarà la plataforma J2EE de Java, i es comptarà amb l’ajuda de marcs de treball com, per exemple, Oracle ADF o JasperReports. Com a conclusió general, puc assegurar que si es distribueixen les tres capes d’un sistema en tres nivells s’obtenen beneficis en l’administració, en el manteniment, en l’escalabilitat, en la flexibilitat i en la reutilització de les aplicacions. El principal inconvenient és el possible augment de lentitud en les aplicacions clients.

Sistema per gestionar les incidències d'un servei d'informàtica amb una arquitectura J2EE distribuïda en tres nivells

Tant en la meva etapa d’estudiant com en la meva curta vida laboral, he participat en el desenvolupament de varies aplicacions de gestió, tant d’escriptori com web, que majoritàriament sempre estaven dividides en tres capes però en dos nivells: la base de dades i l’aplicació, que contenia tant la lògica de negoci com la vista. Des de fa temps he tingut la curiositat i la necessitat d’intentar desenvolupar una aplicació de gestió que estigui distribuïda en tres o més nivells, separant el model de dades i la lògica de negoci de la vista. Crec que el treball de fi de carrera és idoni per desenvolupar-la. L’aplicació a desenvolupar anirà destinada a la gestió d’un servei d’informàtica, que s’encarrega de resoldre les incidències, inventariar i realitzar el manteniment preventiu dels equips informàtics d’una o de varies empreses. Es crearà una aplicació que contindrà el model de dades i la lògica de negoci. També es crearan dues aplicacions clients: una aplicació d’escriptori que donarà accés a totes i cadascuna de les funcionalitats del sistema i una aplicació web que oferirà un accés lleuger i des de qualsevol ubicació a les funcionalitats d’explotació del sistema. Per últim, també es crearà una altre aplicació web que s’encarregarà de generar els llistats sol•licitats per les dues aplicacions clients. D’aquesta manera també es centralitzarà la gestió dels llistats de les aplicacions del sistema. Per desenvolupar el sistema, s’utilitzarà la plataforma J2EE de Java, i es comptarà amb l’ajuda de marcs de treball com, per exemple, Oracle ADF o JasperReports. Com a conclusió general, puc assegurar que si es distribueixen les tres capes d’un sistema en tres nivells s’obtenen beneficis en l’administració, en el manteniment, en l’escalabilitat, en la flexibilitat i en la reutilització de les aplicacions. El principal inconvenient és el possible augment de lentitud en les aplicacions clients.

Preventive health care and payment systems to providers

Prevention has been a main issue of recent policy orientations in health care. This renews the interest on how different organizational designs and the definition of payment schemes to providers may affect the incentives to provide preventive health care. We present, both the normative and the positive analyses of the change from independent providers to integrated services. We show the evaluation of that change to depend on the particular way payment to providers is done. We focus on the externality resulting from referral decisions from primary to acute care providers. This makes our analysis complementary to most works in the literature allowing to address in a more direct way the issue of preventive health care.

Preventive medicine for epidemic outbreaks and risky behavior through mobile devices and ubiquitous computing

In this work, we have developed the first free software for mobile devices with the Android operating system that can preventively mitigate the number of contagions of sexually transmitted infections (STI), associated with risk behavior. This software runs in two modes. The normal mode allows the user to see the alerts and nearby health centers. The second mode enables the service to work in the background. This software reports the health risks, as well as the location of different test centers.

Intraovarian sperm storage in Helicolenus dactylopterus dactylopterus fertilitzation, crypt formation and maintenance of stored sperm

The females of the bluemouth rockfish, Helicolenus dactylopterus dactylopterus (DelaRoche, 1809), store sperm within their ovaries for periods of up to 10 months. Twenty six females with standard lengths between 152 and 257 mm and six males with standard lengths between 253 and 209 mm were caught storage crypts with stored spermatozoa and to describe their evolution over the year. After internal fertilization and once sperm reaches the ovary, a crypt forms probably by an epithelial inclusion at the base of the lamellae of one or several spermatozoa groups that are floating freely in the interlamellar space of the ovarian lumen. Stored spermatozoa have a large cytoplasm bag surrounding their heads. This bag could serve as a nutritive reservoir during the long storage period. Many desmosonal and tight junctions between the crypt cells ensure tha male sex cells are protected against the female immune system

Probabilistic models to assist maintenance of multiple instruments

The paper discusses maintenance challenges of organisations with a huge number of devices and proposes the use of probabilistic models to assist monitoring and maintenance planning. The proposal assumes connectivity of instruments to report relevant features for monitoring. Also, the existence of enough historical registers with diagnosed breakdowns is required to make probabilistic models reliable and useful for predictive maintenance strategies based on them. Regular Markov models based on estimated failure and repair rates are proposed to calculate the availability of the instruments and Dynamic Bayesian Networks are proposed to model cause-effect relationships to trigger predictive maintenance services based on the influence between observed features and previously documented diagnostics

Income maintenance programs and multidimensional screening

This paper examines properties of optimal poverty assistance programs under different informational environments using an income maintenanceframework. To that end, we make both the income generating ability andthe disutility of labor of individuals unobservable, and compare theresulting benefit schedules with those of programs found in the UnitedStates since Welfare Reform (1996). We find that optimal programs closelyresemble a Negative Income Tax with a Benefit Reduction rate that dependson the distribution of population characteristics. A policy of workfare(unpaid public sector work) is inefficient when disutility of labor isunobservable, but minimum work requirements (for paid work) may be usedin that same environment. The distortions to work incentives and thepresence of minimum work requirements depend on the observability andrelative importance of the population's characteristics.

Maintenance of A/P body regions in planarians by TCEN49, a putative cystine-knot neurotrophin.

In freshwater planarians, the protein TCEN49 has been linked to the regional specification of the central body region, which includes the pharynx.

Effectiveness of psychotropic medications in the maintenance phase of bipolar disorder:a meta-analysis of randomized controlled trials

The purpose of this meta-analysis was to examine the efficacy of maintenance treatments for bipolar disorder. Placebo-controlled or active comparator bipolar maintenance clinical trials of ≥6 months' duration with at least 15 patients/treatment group were identified using Medline, EMBASE, clinicaltrials.gov, and Cochrane databases (1993 to July 2010). The main outcome measure was relative risk for relapse for patients in remission. Twenty trials (5,364 patients) were identified. Overall, lithium and quetiapine were the most studied agents (eight and five trials, respectively). The majority of studies included patients who had previously responded to treatment for an acute episode. All interventions, with the exception of perphenazine+mood stabilizer, showed a relative risk for manic/mixed or depressive relapse below 1.0, although there was variation in the statistical significance of the findings vs. placebo. No monotherapy was associated with a significantly reduced risk for both manic/mixed and depressed relapse. Of the combination treatments, only quetiapine+lithium/divalproex, was associated with a significantly reduced risk vs. comparator (placebo+lithium/valproate) for relapse at both the manic/mixed and depressed poles of bipolar illness. Limitations for the analysis include differences in study durations and definitions of relapse. In conclusion, available maintenance therapies show considerable variation in efficacy. The efficacy of lithium and divalproex has been confirmed, but newer therapies, such as a number of atypical antipsychotics were also shown to be effective in bipolar disorder. Efficacy of all maintenance interventions needs to be balanced against the safety and tolerability profiles of individual agents.

Managing FOSS during development: preventive and curative approaches

Today, most software development teams use free and open source software (FOSS) components, because it increases the speed and the quality of the development. Many open source components are the de facto standard of their category. However, FOSS has licensing restrictions, and corporate organizations usually maintain a list of allowed and forbidden licenses. But how do you enforce this policy? How can you make sure that ALL files in your source depot, either belong to you, or fit your licensing policy? A first, preventive approach is to train and increase the awareness of the development team to these licensing issues. Depending on the size of the team, it may be costly but necessary. However, this does not ensure that a single individual will not commit a forbidden icon or library, and jeopardize the legal status of the whole release... if not the company, since software is becoming more and more a critical asset. Another approach is to verify what is included in the source repository, and check whether it belongs to the open-source world. This can be done on-the-fly, whenever a new file is added into the source depot. It can also be part of the release process, as a verification step before publishing the release. In both cases, there are some tools and databases to automate the detection process. We will present the various options regarding FOSS detection, how this process can be integrated in the "software factory", and how the results can be displayed in a usable and efficient way.

Traducció i adopció a l'Índia: Hindu Adoptions And Maintenance Act, 1956

L’objectiu principal d’aquest treball de fi de grau és fer-se càrrec d’una traducció jurídica amb tot el què això implica: documentar-se a través de fonts fiables, emprar les eines adequades, lliurar-lo dins el termini establert, entre d’altres. En aquest cas, és una traducció de les lleis que regulen les adopcions a l’Índia. A més, en aquest treball també s’explica breument el dret civil a Catalunya i es compara amb el de l’Índia, ja que es basen en idees molt diferents. Aquests tipus de traduccions exigeixen precisió i claredat perquè els conceptes i les estructures sintàctiques acostumen a ser molt complexes. A continuació, hi ha detallat cada pas que s’ha seguit per tal d’assolir l’objectiu principal.

Predictors of psychiatric hospitalization during 6 months of maintenance treatment with olanzapine long-acting injection: post hoc analysis of a randomized, double-blind study.

BACKGROUND: Hospitalization is a costly and distressing event associated with relapse during schizophrenia treatment. No information is available on the predictors of psychiatric hospitalization during maintenance treatment with olanzapine long-acting injection (olanzapine-LAI) or how the risk of hospitalization differs between olanzapine-LAI and oral olanzapine. This study aimed to identify the predictors of psychiatric hospitalization during maintenance treatment with olanzapine-LAI and assessed four parameters: hospitalization prevalence, incidence rate, duration, and the time to first hospitalization. Olanzapine-LAI was also compared with a sub-therapeutic dose of olanzapine-LAI and with oral olanzapine. METHODS: This was a post hoc exploratory analysis of data from a randomized, double-blind study comparing the safety and efficacy of olanzapine-LAI (pooled active depot groups: 405 mg/4 weeks, 300 mg/2 weeks, and 150 mg/2 weeks) with oral olanzapine and sub-therapeutic olanzapine-LAI (45 mg/4 weeks) during 6 months' maintenance treatment of clinically stable schizophrenia outpatients (n=1064). The four psychiatric hospitalization parameters were analyzed for each treatment group. Within the olanzapine-LAI group, patients with and without hospitalization were compared on baseline characteristics. Logistic regression and Cox's proportional hazards models were used to identify the best predictors of hospitalization. Comparisons between the treatment groups employed descriptive statistics, the Kaplan-Meier estimator and Cox's proportional hazards models. RESULTS: Psychiatric hospitalization was best predicted by suicide threats in the 12 months before baseline and by prior hospitalization. Compared with sub-therapeutic olanzapine-LAI, olanzapine-LAI was associated with a significantly lower hospitalization rate (5.2% versus 11.1%, p < 0.01), a lower mean number of hospitalizations (0.1 versus 0.2, p = 0.01), a shorter mean duration of hospitalization (1.5 days versus 2.9 days, p < 0.01), and a similar median time to first hospitalization (35 versus 60 days, p = 0.48). Olanzapine-LAI did not differ significantly from oral olanzapine on the studied hospitalization parameters. CONCLUSIONS: In clinically stable schizophrenia outpatients receiving olanzapine-LAI maintenance treatment, psychiatric hospitalization was best predicted by a history of suicide threats and prior psychiatric hospitalization. Olanzapine-LAI was associated with a significantly lower incidence of psychiatric hospitalization and shorter duration of hospitalization compared with sub-therapeutic olanzapine-LAI. Olanzapine-LAI did not differ significantly from oral olanzapine on hospitalization parameters.

¿Qué entienden los jóvenes universitarios por monogamia y sexo sin penetración, como estrategias preventivas de la transmisión sexual del virus del SIDA? = What university students understand by monogamy and sex without penetration as preventive strategies of sexual transmission of AIDS virus?

Monogamy and sex without penetration are behaviors recommended by the WHO to avoid AIDS virus sexual transmission. Seven hundred and fifty university students from 18 to 25 years (67.7% women) were surveyed and they were asked to give a maximum of three free definitions of the words monogamy and sex without penetration to prevent AIDS virus sexual transmission. Their participation was voluntary and anonymous. Although the majority of the answers was correct, there was a considerable percentage of wrong answers, either for monogamy (3.7% masturbation; 2.1% to have many partners; 0.9% homosexual relations), or for sex without penetration (20.5% oral sex; 1.1% anal coitus; 0.8% coitus without orgasm; 0.4% coitus interruptus). Some definitions or examples differ by gender. The amount of wrongs or incomplete answers put researchers on the alert about insufficient preventive knowledge in a population with a high educational level