signal infrastructure best practice

This signal infrastructure best practice list - is preliminary and is not published by openpolitics.ca itself. See the intranet best practice, extranet best practice? and telework best practice? list for variants specific to where the user works. See the greening of government operations, greening of corporate operations? and greening of nonprofit operations? pages for pages directly relevant to sector of operation. Finally, see civic best practice, office best practice? and wiki best practice for other practices relevant to building a healthy signal infrastructure?.

  • terms
    • refer to performance per watt as indicator of "cool computing" - do not permit abusive terms like "green computing" or the use of the term:ecosystem? to mean anything other than natural capital
    • avoid terms like "computing" or "data processing" when any implication of actions that take place beyond a motherboard? are involved - avoid also "communications" or "information technology" or (worst)"technology" to mean too general or too specific a range of devices.
    • forbid terms like "hydro" to mean electric power, which is rarely generated by hydroelectric? means but usually a much dirtier method - encourage use of exact descriptive terms, e.g. NS Power? sends a coal bill? or smog bill? while Ontario Hydro? sends a plutonium bill? - that being the waste product that is generated by their CANDU? operations.
    • Prefer the term signal infrastructure for the broadest uses and for subsets rely on the infra trade? terminology, e.g. boot?, bay?, box?.
    • Train users in all infra term?s and consider rationed support for those that refuse to learn or state problems in operational terms. This is a team best practice?.
  • support
    • respect: "Genuine Green Systems" "must assume that the user's time is important, as they are using it to do something that, if done by someone else, would waste more material resources to create the same well-being/happiness and do more damage to the environment. Accordingly a high degree of support must be provided" including at least:
    • Standard boot image? providing "basic protections against malware?: virus, worm, spyware, and even spam if email is a provided/supported service"
    • "Advice and instructions on the installation and configuration of new hardware/software" or ideally complete boot image? builds and restores provided and updated and (if possible) managed centrally.
    • "Recommendations on the most current drivers for the customer's hardware" or their provision in the boot image?s.
    • "Fixing problems related to system and applications error messages" assuming that such messages use the correct diagnostic? terms.
    • "Remote diagnostics of malfunctions with computer hardware components" ideally with the ability to talk a user through any need to swap box?es for their spare.
    • "Fixing problems related to malfunctions of Microsoft Windows?Operating Systems family? components and software applications, if this is offered
and there is no Linux? option" as there should be. The easiest way to fix is to swap boot?s by remote or remotely managed protocols.
    • "Performance optimization, recommendations on upgrades/updates, system failure, functional disorder of the basic components both hardware and software." Again ideally remotely run using infra term?s
    • "troubleshoot Local Area Network? and Dial-Up Networking?configuration and connectivity." Do not require users to know anything about the IP protocol? or other net trade? issues. (Some volt trade?, wire trade? and web trade? terms will be required, however).
    • "Provide fixes for DLL and other Windows errors, if this is the only OS supported, and the software clashes are within the parameters of the ordinary use of the system", else require them to swap boot?s to one that can be more easily supported, and re-install all well behaved software.
    • "Provide updates for device driver problems and conflicts" again preferably by requiring them to swap boot?s to a known starting state.
    • "Provide updates for BIOS? related issues" using methods that do not affect the rest of the boot image - as a BIOS is a box? level issue.
    • insist that users learn to observe and state their problems in infra term?s or else pay a penalty or charge or rationed support token.
  • protocol
    • prefer home automation? tools that can readily be deployed in both home and office settings, but which rely on the industrial-strength BACnet protocols
    • encourage standard office protocol?s that conserve enegy? by checklisting instructions to:
      • turn down heat
      • close heat-containing curtains at night
      • turn off lights
      • turn off electronic devices
      • turn off all phone equipment except the answering machine?s
    • ensure that support for customer relationship?s, regular reports, meetings and other protocols and systems permit the use of worn devices where feasible, so that no additional transport to and from office spaces is required, and so that pandemics and other disaster?s that render persons or office spaces useless or inaccessible do not prevent routine operations. A study of these problems has indicated that over 50% of businesses that suffer a major disaster of this nature do not recover.
  • power/waste
    • monitor energy? use judiciously and visibly - preferably with visible meter?s plugged into a wall
    • consider an electricity challenge? to reward using less electricity
    • use of rechargeable battery technology, not fuel cell?s, at this time, except in very large stationary fuel cell? applications.
    • never use any disposable battery? - even in fire alarm?s - recharged batteries are reliable if fire alarm turn?s are performed on schedule with the shift to and from Daylight Savings Time?
    • keep solar charger?s on hand for each type of battery used
    • prefer lead-acid? batteries because of a well-developed infrastructure of recycling these; use nickel-cadmium? and lithium-ion?, rechargeable alkaline? and aluminum-air? only where a proper means of disposal exists
    • in high reliability applications prepare to move to aluminum-air?-based fuel cell? that use aluminum ion fuel? and generate compact aluminum oxide? waste which can be reprocessed in a closed fuel cycle?. Despite toxicity of aluminum oxide, this may be the only known technology acceptable for zero e-waste hardware.
    • Compare performance of rechargeable battery technology to fuel cell?s using the watt-hours per litre metric: find the litres of fuel used on the power grid? that generate the electric power used in recharging, then adjust for the relative ecological damage done by that, relative to that used in the fuel cell - typically methanol fuel? or pumped hydrogen?. Details:
    • Normalize the relative working lifespan of each cell type to adjust for a short lived device that generates more e-waste? versus a long-lived one that generates less, but potentially more toxic waste. Also for the labour and compatibility risk of swapping batteries. For instance, a 4-year lifespan on a poorly standardized battery type should compare unfavourably to a 3-year lifespan on a well-standardized one since the odds of having to replace the device using the battery is higher. Over 12 years, the relative cost, risk and waste of disposing of 3 of the 4-year versus 4 of the 3-year types must be compared.
  • redundant? systems
    • no single point of failure? for any work process whatsoever
    • at least one backup boot? and box? per office, meaning a minimum of two even in a SOHO? environment
    • at least two backups of any user data?, and three of mission-critical data?, with user privacy? precautions to prevent these from falling into the hands of likely data abusers.
  • accounting
    • total quality management? approach focused on protocol and service? to be preferred to those focused only on work product or labour efficiency - see throughput accounting.

The green systems and green bay specifications apply and extend the above.

Show php error messages