Database of modular designs all of which are compatible with the OpenStructures Grid and the Design Principles.
Listing designers, partners and funds that have contributed to and supported OpenStructures.
Events, activities and projects based on OpenStructures
OpenStructures is a design methodology for open modular design (also see ‘About’).
OS_Studio is the design studio that facilitates the use of the OpenStructures design methodology (also see ‘Team’).
Because we want to develop a networked alternative on how to create, exchange, manage and redistribute value.
Because modularity is one of the basic principles of sustainable design
Because we believe in collaboration rather than competition.
Unlike most existing modular systems, the OS model doesn’t follow the classical top-down approach in which one person designs a complete (modular) system for everybody, but rather favors a system where everybody designs a small part of one shared system.
The Platform aims at establishing a balance between openness, fairness and economic viability. Parts are open and accessible enough to allow innovation based on existing designs, yet closed enough in order to protect their creative value. Revenue is redistributed between the community and the platform in order to remunerate the work of contributors on the one hand and to maintain the services of the website on the other.
The OS model will offer a more flexible environment to the end user, allowing his built environment to adapt (grow, shrink or update) more easily.
If we shift from project to process, each design object becomes a prototype, an update, a new version. If we see our society as ‘under construction’, rather than ‘accomplished’, we will free up space for progress.
Every evolutionary process started with only a few blocs to build from, frequently resulting in rather primitive designs. But with every cross-pollination more pieces were created, and with every piece more complexity was added to the overall system, finally sophisticated constructions and creations emerged.
Since the OS system is conceived as an evolutionary model, it doesn’t consider its designs to be static end results, but rather sees them as updates of existing versions, phases within a broader cycle. Apart from that, the OS model wants to introduce variety within man-made modularity, welcoming different signatures to the design of its individual parts.
Modularity is a dimensional restriction by definition, but it also offers new opportunities because of the shared dimensional framework it proposes. And within this restriction, variation is endless.
The OpenStructures project doesn’t impose its grid system, it proposes it. It invites people to experiment with it and hopes to learn from their outcomes. The OS model doesn't aim at convincing everybody but hopes to unite a tightly knit network of likeminded enthusiasts.
Because it syncs up nicely with already existing standards and it’s easy to use.
Because developing a(n ecosystem) is more complex than developing a product.
Because you don’t buy a consumer product but rather an assembly of parts that can be infinitely adapted, reconfigured and re-used.
Because it’ll stimulate you to rethink, play and improvise rather than simply consume.
What would you do with a LEGO car if you don’t need it anymore?
A part is a modular piece, based on the OS Grid and the Design Principles, that cannot be further disassembled without breaking it.
An application is a functional assembly of two or more Parts (such as f.i. an object) that contains at least one registered OS part.
An original is the first appearance of a Design, stated by submission parameters (submitted by a Contributor on a given date).
A derivative is a variation on an Original / an edited version of an original in which the 3D file of the derivative is (slightly) different than the 3D file of the original.
An edition is a specific reproduction of a design; one design can have multiple editions, and each might have a different price tag though they all share the same 3D file.
The institutions and organisations that have actively supported the project (with whom we’ve been interacting) through workshops, exhibitions commissions, debates, conferences etc. until now.
Yes, you can!
You can either submit work in 'My Profile' once registered or email pictures to info@openstructures.net. Please give us some time to review your submission and get back to you.
All design submissions need to be verified prior to uploading in order ensure that all published content (product photography, fabrication files etc. ) is coherent and technically sound.
Because the designer chose to share his / her design for free.
Because the designer chose to do so.
50% of the revenue go to the designer, the other 50% goes to the OS platform.
Because the designer decided to do so (or not)
Because it’s the only way to truly build things together, to create a database of parts that is fully accessible to everybody at all times
Because we want to leave this choice up to the designer.
When submitting an App with an OS open 1.0 license, you offer your design to use, enjoy or even copy - for anybody everywhere.
When submitting an App and choosing an OS_non-commercial 1.0 license, you still offer your design to use, enjoy or even copy - to everybody, but for personal use only. However you indicate that it is Not OK to commercialise it, without prior agreement with you.
or
Because you support the idea that people out there could copy your design and enjoy its use it in their everyday but you’re less comfortable with the idea that a (big) manufacturer would make profits with your design.
Because some are (unique) archive copies and/or haven’t been produced in large numbers (yet).
Only of designs that are licensed under OS_open 1.0
No. Only the designer of the part is allowed to do so.
Yes, please contact us if you are interested in distributing.
Yes
No, you would need to submit your edited Part first either via this formula or by emailing to submit@openstructures.net in order for it to be verified by us prior of being published as a derivative.
No, because Parts are always licensed and published as fully open (OS open 1.0).
Only if the designer licensed his / her application as Partly Open (OS non-commercial 1.0) and if the purpose of reproduction is commercial.
The sales price of an Application is the sum of the production price of the application + a royalty for the designer (only if licensed as OS_non-commercial) + a sales-channel fee for the use of the OS webshop.
OS parts can be recognized on sight by their typical assembly point patterns and / or dimensions. Apart from that the designer can then decide to feature the OS trademark and ID number onto the design. This will allow other users to look up additional part information by searching for the ID number on the OS platform.
The Part and/or App ID allows
For example,
in P.137.2:
Not all registered designs get published, mainly because their submission is incomplete, incorrect or files are missing.
No, in order for an object to be OS compatible it needs to contain at least one OS compatible part.
The designer allows other Users to use their Design free of charge regardless of the purposes for use. Under the fully open licensing option, both Personal Use Purposes and purposes that surpass Personal Use (e.g. purely commercial use of your Application) are freely allowed under the following terms:
As a rule all OS parts that are published on the OS platform are open (in order to allow others to easily use and build further on them). Wether or not a published OS App is open is decided by the designer of this app.
The designer decided that the entity using and/or reproducing his / her OS_Application for purposes that surpass Personal Use (e.g. commercial use of your OS_Application) is bound to the payment of licensing fees as described in our Terms of contribution and commercial use.
In all cases:
