1998 Oct |
Integrate Internet solutions into your energy management network Abstract: Presented by Johan Sarkinen at Intelec '98 in San Francisco, California, 1998-10-08. From http://intl.ieeexplore.ieee.org/xpl/abs_free.jsp?arNumber=793610 This paper appears in: Telecommunications
Energy Conference, 1998. INTELEC. Twentieth International |
2001 Aug |
Framework for Energy Management Abstract: CONTRIBUTION: T1E1.5/2001-020 (1E150200) www.T1.org.| Presented by Johan Sarkinen at T1E1 meeting in Ottawa, Canada, 2001-08-24. |
2001 Nov |
Draft Standard for Energy Monitoring, Machine-Machine Interaction Abstract: CONTRIBUTION: T1E1.5/2001-028 (1E150280) www.T1.org. Presented by Johan Sarkinen at T1E1 meeting in Greensboro, North Carolina, 2001-11-08. |
2004 Sep |
Introduction to
DC Power A layman's introduction to 24V and -48V power systems with what it's all about. PDF, white paper, v2.0, Sep 2004 |
2005 Sep |
Decentralized Power, Need for Smarter Products, Total Cost of Ownership, and Security Abstract: More equipment (due to decentralization); more mixing of different technologies such as 2G-3G wireless, cable, DSL, Wi-Fi and WiMAX; tougher competition; and shorter economic life makes calculations like Total Cost of Ownership (TCO) and Return on Investment (ROI) even more important. Solutions for lowering TCO include simplified and automatic business processes – lean operations, use of technologies such as standardized element management and controller area networking, Radio Frequency Identification (RFID), Global Positioning System (GPS), wireless sensors and mesh networks, and zero configuration networking – intelligent infrastructure. Various alternative technologies – e.g. Bluetooth vs. ZigBee, proprietary vs. standards (SNMP and XML) have their strengths and weaknesses and require evaluation. XML for instance, has great advantages but due to space inefficiencies this technology is not yet suitable for embedded applications (e.g. power controllers). Inefficiency issues are addressed by new proposals like SOAP Message Transmission Optimization Mechanism (MTOM) and XML-binary Optimized Packaging (XOP). Along with decentralization, more automatic functionality and with progressively more wireless technologies, there is also an increased need for, and focus on, security. Wireless networks are great due to ease of deployment and use, but also pose security challenges because they are easier to breach, including unnoticed entry. Accordingly, security in authentication, data integrity, data confidentiality, and access control needs to be addressed in designing power controllers and power components. Presented by Johan Sarkinen at Intelec '05 in Berlin, Germany, 2005-09-22. http://intl.ieeexplore.ieee.org/xpl/abs_free.jsp?arNumber=4134320 |
2007 Oct |
An Open Source(d) Controller Abstract - The open source software movement has been going on for a few decades now. Today, an increasing number of open source solutions enter the market and become valid alternatives to proprietary and closed solutions. Examples include operating systems like Linux and OpenSolaris, back-end solutions (e.g. LAMP - Linux, Apache web server, MySQL database, and Perl/PHP/Python programming languages – are among the most well-known and widely used open source software on the Internet), office applications (e.g. Firefox web browser, Thunderbird email, GIMP graphics, OpenOffice office suite), and complete enterprise systems like Compiere (ERP and CRM) and Mambo content management system (CMS). In addition, a variety of devices increasingly include open source (e.g. cellular phones, network equipment like routers, and Asterisk – a complete IP PBX). The open source culture is about much more than software and includes open source hardware, views on intellectual properties rights, completely changes how products are developed and owned, and how business models are developed. To decide if open source is something for you, a good understanding of what open source really means is necessary. This includes legal aspects (different licenses), availability of support with (hopefully a thriving) user community and commercial for-pay support options, and security. Intellectual properties rights, and the vast number of many types of open source licenses (e.g. GNU General Public License (GPL) and BSD License), is one of the more complex areas when using open source. What can and not can be done, what must be done, and so on, vary between licenses. One effort to bring some order in all this is the Open Source Definition (OSD) from Open Source Initiative (OSI) which lists ten conditions that must be met for an OSI Certified open source license. Today, many companies have already been forced to either remove or release as open source code borrowed by developers without properly complying with licenses. Such “dirty code” is increasingly easy to detect via compliance tools used by companies doing this as business. (Not to mention whistle-blowing employees tipping of property owners.) Searching for dirty code is also increasingly part of due diligence in mergers and acquisitions and can add costly delays and lawsuits. The perceived low cost is often a reason for considering open source solutions but the total costs of development (TCD) – including for example licenses, tools, labor, and support – must be considered from initial design, to maintenance, all through the end of life of the product. This paper reviews critical aspects for going open source, including software and hardware, use of commercial off-the-shelf (COTS) alternatives, system design going from a monolithic, single-binary, firmware to a layered design with operating system, middleware, and user applications.Presented by Johan Sarkinen at Intelec 2007 in Rome, Italy (Thu 2007-10-04, 08:30) http://intl.ieeexplore.ieee.org/xpl/abs_free.jsp?arNumber=4448885 This paper appears in: Telecommunications Energy Conference, 2007. INTELEC 2007. 29th International |