Standards and Practices (Player corporation)

Corporation Details

We do things by the book.
Name	Standards and Practices
Ticker	[IEEE]
CEO	Zedrik Cayne
Founded	May 9, 2009
Status	Active
Headquarters	Undisclosed
Website	[None None]

Overview

Standards and Practices, the basis upon which all well formed corporations and alliances are based upon.

The repository of all knowledge of what 'good looks like' has finally been concentrated in a series of documents and put under the stewardship of the IEEE for the benefit of the entire New Eden pod pilot community.

Periodic spot checks by designated agents may be performed at any time, and if possible demonstrations of why the incorrect practices are bad may be administered at the discretion of the agent.

Verbal warnings, even going as far as 'smacktalk' broadcast to a local system's populace may be administered as well at an agent's discretion. (Please see document #762.258.255 for the proper standards and practices involved in the warning procedures, as well as the parameters for the demonstrations available to the agents of the IEEE)

All standards and practices documents are available from any agent for a nominal fee, plus delivery, shipping and handling charges. Hard copies are also available upon request but they involve an extra handling fee.

Publically Available Documents

We here at Standards and Practices have decided that a few of the most often used and quoted documents should appear here as a service to the pod pilot community.

Standards and Practices Document Id #762.258.255

Overview

Accepted standards and practices for the application of verbal warnings to pod pilots for the transgression of any documented standards or practices enforcable by any agent of the IEEE.

Verbiage

There are four levels of standard verbiage that should be used when applying verbal warnings across public channels.

1. Polite
2. Firm
3. Derision
4. Smack

Polite

This level of verbiage is rarely used. Mostly comprised of friendly warnings across public channels of violation of published standards.

Firm

The : most commonly used form of verbiage, usually associated with an initial demonstration as to why the particular violation of published standards and practices is indeed a bad idea. Normally rather curt, including a reference to the IEEE document id.

Derision

Should a target of correction offer resistance, claims of non-violation of published standards, violence, or a bad attitude, derision should be employed as a stronger method of correction. Comments should remain relatively polite and no personal attacks should be employed. Derisive comments should be kept to the violation of standards and practices with repeated quotes from the relative documentation to back up the agent's words and actions.

Smack

At an agent's discretion, personal attacks against particular members of the offending corporation or alliance. Especially if personal violence has been offered towards the agent. Please remember to keep comments as humorous as possible for the entertainment of the masses while the correction is underway.

Typical Progression

Typical progression between verbiage levels are usually as follows for first time offenders.

1. Polite -> Firm -> Derision
2. Firm -> Derision

For repeat offenders, you may wish to start at a more advanced level as per the following progressions.

1. Derision -> Smack
2. Smack

Once : the verbiage level goes up to Smack, it will be difficult to regress to a lighter level, but it can be done with persistence.

Document Id #223.646.377

Overview

Accepted standards and practices for the practice of the mining profession.

Practices

• Using un-secured temporary storage while mining is prohibited. The practice is commonly referred to as 'jet can mining' and while convenient, is inherently dangerous. The presence of high security 'can flippers' and other thieves can result in the loss of your hard work along with the possibility of the destruction of your ship, and very rarely your pod.
• Using mining barges and exhumers in space where the security is above 0.7 is bad for the environment. Resource depletion in empire space is a great problem as witnessed by the over mining and destruction of all high security ice fields. Henceforth all mining barges should only mine in 0.7 security space or lower to avoid over-mining these precious scarce resources.
• Mining in low security space without locking the system down is even more dangerous than mining with an un-secured container in high-sec and should be avoided at all costs. The presence of pirates in low security space can often result in the destruction of ship and pod.
• Mining in deadspace should be avoided as the asteroids there fall under temporary phenomena which provide a significant amount of mass and gravitational matter is provided by these phenomena. The exact mechanic by which the objects appear and disapaer are unknown at this point but it is known that removing the temporary mass and refining into more 'permanent' mass has been known to add mass to the universe in an unbalanced way. This could result in the spontaneous reduction of mass in nearby spaces including ship destruction.
• Mining while at war should not be done at all. Most serious mining vessels are slow on the helm and easily caught by warp scramblers. And while certain exhumers can produce very strong tanks, they are usually no match for a properly fit PVP vessel. (Exceptions made for a PVP fit Hulk of course, but flying such a toy during a serious war is probably just asking for it to be dead)

Document Id #467.732.8466

Overview

Accepted standards and practices for the temporary deputization of field agents.

Practices

Agents of IEEE are vastly outnumbered when the scope of their authority is taken into consideration. As such the emergency deputization act, doc id: 467.732.8466 was put into place to allow senior IEEE agents to field deputize normal citizens in times of great stress to assist with the inspection and enforcement of IEEE standards.

• Deputization is compulsory, not voluntary. Fate rarely chooses us at a time of convenience.
• Deputized personnel and/or corporations will be given 24 hour notice in writing and/or person of their drafted status. They will have their area of operations assigned to them at this time.
• Deputized personnel are expected to familiarize themselves with all IEEE Standards.
• Deputized personnel will perform routine and thorough inspections of their area of operations. They will intercede with all infractions as though an IEEE agent. All instances of infractions will be noted in detail and sent via eveMail to IEEE command.
• Failure to comply will result in enforcement of Document Id XXX.XXX.XX (please note that this document remains classified at this time).