The PDBTM database (available at http://pdbtm.enzim.hu), the first comprehensive and up-to-date transmembrane protein selection of the Protein Data Bank, was launched in 2004. The database was created and has been continuously updated by the TMDET algorithm that is able to distinguish between transmembrane and non-transmembrane proteins using their 3D atomic coordinates only. The TMDET algorithm can locate the spatial positions of transmembrane proteins in lipid bilayer as well. During the last 8 years not only the size of the PDBTM database has been steadily growing from ∼400 to 1700 entries but also new structural elements have been identified, in addition to the well-known α-helical bundle and β-barrel structures. Numerous ‘exotic’ transmembrane protein structures have been solved since the first release, which has made it necessary to define these new structural elements, such as membrane loops or interfacial helices in the database. This article reports the new features of the PDBTM database that have been added since its first release, and our current efforts to keep the database up-to-date and easy to use so that it may continue to serve as a fundamental resource for the scientific community.

A contact map is a 2D derivative of the 3D structure of proteins, containing various residue–residue (RR) contacts within the structure. Contact maps can be used for the reconstruction of structure with high accuracy and can be predicted from the amino acid sequence. Therefore understanding the various properties of contact maps is an important step in protein structure prediction. For investigating basic properties of contact formation and contact clusters we set up an integrated system called Contact Map Web Viewer, or CMWeb for short. The server can be used to visualize contact maps, to link contacts and to show them both in 3D structures and in multiple sequence alignments and to calculate various statistics on contacts. Moreover, we have implemented five contact prediction methods in the CMWeb server to visualize the predicted and real RR contacts in one contact map. The results of other RR contact prediction methods can be uploaded as a benchmark test onto the server as well. All of these functionality is behind a web server, thus for using our application only a Java-capable web browser is needed, no further program installation is required. The CMWeb is freely accessible at http://cmweb.enzim.hu.

Workflow management is implemented in manufacturing at many levels. The nature of processes varies at each level, hindering the use of a standard modeling or implementation solution. The creation of a flexible workflow management framework that overarches the heterogeneous business process levels is challenging. Still, one of the promises of the Industry 4.0 initiative is precisely this: to provide easy-to-use models and solutions that enable efficient execution of enterprise targets. By addressing this challenge, this article proposes a workflow execution model that integrates information and control flows of these levels while keeping their hierarchy. The overall model builds on the business process model and notation (BPMN) for modeling at the enterprise level and recipe modeling based on colored Petri net (CPN) at the production level. Models produced with both alternatives are implemented and executed in a framework supported by an enterprise service bus (ESB). Loosely coupled, late-bound system elements are connected through the Arrowhead framework, which is built upon the Service-Oriented Architecture (SOA) concept. To prove its feasibility, this article presents the practical application of the model via an automotive production scenario.Note to Practitioners-The methodology detailed in this article can serve as a basis for experts who are dealing with industrial workflows. Reacting to the requirements of Industry 4.0, i.e., the virtualization, decentralization, modularity, real-time capability, and service orientation, this article provides a concept that can answer all the defined criteria. First, it adopts a new two-level approach to workflow management, which makes the understanding and control of workflows easier, enhancing transparency. Furthermore, it demonstrates how-even completely different-applications and modeling languages can be integrated into a Service-Oriented Architecture (SOA). The presented com-Manuscript

No abstract

No abstract

No abstract

No abstract

No abstract