Project Summary

Prototyping the Omata One in this early instance was a way to work through some of the ideas in hardware. I had a fairly clear idea of the functional requirements, but needed to work through them in a grounded way rather than just drawing boxes and arrow on sheets of paper. I'd descxribe this as a macro board representing the major subsystems tha twould need to be implemented. It gave me something to point at and say, "This is what I mean by the Omata One", and could feed directly into the engineering specifications. It was a way to work through the engineering requirements and get a better sense of the overall system. (This all from the perspective of engineering dept.; of course there are the brand aspects and such, but first you need a thing that does what it says it does — later you can make sure the character of it as a brand is right and consistent. But, if the thing doesn't work, then the brand is irrelevant.)

Project Semantic Tags
ENGINEERINGHARDWAREPATENTPROTOTYPING