Scribd
Upload
83 views2 pages

Project Specifications Issac Sharp

The document outlines the specifications for a project to design a mobile or semi-mobile method for controlling the power delivery to electric devices remotely. It identifies primary concerns including the need for communication between controlling and controlled devices, choices for the control scheme and its features, ensuring mobility, and implementing solutions securely.

Uploaded by

oddlogic
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
83 views2 pages

Project Specifications Issac Sharp

The document outlines the specifications for a project to design a mobile or semi-mobile method for controlling the power delivery to electric devices remotely. It identifies primary concerns including the need for communication between controlling and controlled devices, choices for the control scheme and its features, ensuring mobility, and implementing solutions securely.

Uploaded by

oddlogic
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Project Specifications

Issac Sharp

The forthcoming designs (to be found in the next three reports) in this project are motivated by a desire to provide a solution to the problem of creating a mobile or semi-mobile method of toggling on and off the power delivery to electric devices and appliances. Many solutions are present already in the market, but few adequately address the problem of allowing mobility while also maintaining flexibility of operation.

Primary Concerns and Unresolved Questions

Communication: there is a need to communicate control signals between the controlling device and the devices that will be switching their power states. There are two main divisions from which we may choose: wired protocols, and wireless protocols. Among these two are a plethora of choices that may be researched for compatibility with the goals of the design.

Choice of control scheme: the controller could be in the form of a mobile device application, such as an Android application, or similar. Other ideas could be used solely or in combination with each other, such as a web interface, or alternatively, a standalone command-line interface The designs may have separate scales of reach: just over a local network, for example, or a publicly visible IP address.

Features: there may be room for varying measures of control and visualization of the state of the system. Control may be limited to ad hoc toggling, or as broad as strong customization, with a chronological job schedule. There is a clear need for some type of way to query scheduled jobs in that case, or display a visualization of some type that represents the past and future of the jobs to be executed. There may be a need for a way to create and store configuration files within the application, such that the configuration could be backed up to disk, or shared with others who are using the system in tandem with one another. If multiple users should need capability to use the system, then there must be some kind of client-to-client communication that would enable the user to know which devices are currently on or off. The level of detail would depend on the rest of the design

Mobility: the level of mobility is related to the choice of control scheme as well as the communication channel. If web/IP is incorporated into the design, then the user could presumably use the device from any Internet-capable device. Alternatively, if the design is for a more personal use, local area networking situation, then web control may not be necessary or desired. The goal here is to have the maximum amount of mobility possible within the scope of the design.

Implementation of the answers to the above: there is a large array of choices among protocols, programming languages, and hardware that could be used to solve this problem. An optimal solution will use as few standards/protocols as necessary to solve this problem, to prevent diminishing returns arising from difficulty of maintaining a multitude of possibly conflicting paradigms within a single design.

Security: a large concern is the security of the system. The design might compromise other features in lieu of preventing device control or monitoring to extend past the intended users of the system.

You might also like