|
Qualified individuals with a perspective on the topic of applications continuity, specifically related to the core areas of telecommunications, email and messaging, and networking are invited to submit articles and manuscripts, article proposals, outlines or other forms of communication that may be made available over the web, to include pre-recorded seminar content for inclusion on the ApplicationContiuity.Org web site. ApplicationContinuity.Org seeks articles with a focus on application continuity as it relates to key communications technologies in the following content categories:
Topics
Style:
ApplicationContinuty.Org publishes written material that has a basic, straightforward style - comparable to business-to-business communication and to popular periodicals that cover the IT industry (e.g., InformationWeek, Network Computing, Network World, etc.). It is the intent of ApplicationContinuity.Org that all materials be accessible in tone, content and readability to the widest possible audience.
Submission Guidelines:
Articles should be written following the guidelines as suggested below. For more information, call +1 408 779 4629 or e-mail your comments and questions to submissions@applicationcontinuity.org.
Article Submission:
If the complete piece of writing is available, please submit with the proposal.
Article Proposal:
Article proposals should include the following:
-
Article Overview
-
Author Information
-
Proposed Length
Article Acceptance Terms
Submissions accepted for publication will be published on ApplicationContinuity.Org.
Submissions should seek to be educational and informative and not act as a strict promotion of a particular product or service. Trade names and examples may be included where necessary to inform the readership.
Submissions that do advocate a particular product or service may be carried by ApplicationContinuity.Org – and clearly marked as to the author.
Sponsored material may also be carried by ApplicationContiuity.Org, again, clearly marked as to its origin.
An article proposal may be accepted after review of the topic, outline and author credentials by ApplicationContinuity.Org.
Articles may be edited with the author’s concurrence before being published.
Deadlines may require very rapid review and approvals by the author. In the event the author is unavailable for review, editorial changes will be incorporated.
Mechanical Submission
Copy should be submitted in Microsoft Word via email as an attachment.
Plain text, in the body of an email message, is also acceptable.
Please do not send HTML files.
If you are sending diagrams or illustrations, send them separately from the text.
If you are submitting an article in the form of a whitepaper, or similar sponsored content, please submit the document in Unlocked Adobe PDF format. The ApplicationContinuity.Org logo and URL will be added to all documents mad available on the site
Length
Between approximately 600 words and 2000 words.
Style
Avoid complex, lengthy sentences. Keep your prose simple and direct. The first paragraph should contain the key points that will be covered in the article. Your opening paragraph should create interest in further reading. Spell out acronyms on first reference, with the abbreviation following in parentheses.
Summarize your main points in a brief conclusion and if possible suggest further resources for additional help.
Include your short author biography, company and contact information (telephone number and email) Please provide a maximum of 50 words.
Graphics
Graphics should be submitted as follows:
-
Electronic submission is preferred and should be TIF or EPS or JPEG with a resolution of 72 dpi at the desired size.
-
The maximum size is 50K, pixel dimensions of 250w, 288h, with a resolution of 72 dpi.
-
For other submissions please contact submissions@applicationcontinuity.org for further instructions.
|
A new study conducted by King Research, and sponsored by Teneros, surveyed 220 IT professionals responsible
for messaging systems in mid-market companies. The goal was to gather data on the activities and products that
IT teams are using to ensure messaging continuity, as well as to investigate key challenges faced by the
individuals responsible for keeping their corporate email up and running. The research suggests that while
most companies are clearly aware of the damage email downtime can do, that knowledge has not yet translated
into increased spending on technology and human resources to prevent downtime, hence, outages are still a
reality.