Writing a Good Technical Paper

7/30/2019 Writing a Good Technical Paper

http://slidepdf.com/reader/full/writing-a-good-technical-paper 1/30

suggestions about writing a good paper.

This presentation presumes that your abstractwas accepted by the conference.

Although you do NOT send your paper for

committees can (and do) review the papers.



principles.

The SPE is a premier organization in the oil &gas industry.

We follow its policies and guidelines, unless weare to hold to another organization’s conferenceguidelines when submitting papers to theseother or anizations.



writing a paper.

I will then describe a suggested timeline to helpyou stay on track when writing your paper.

Next, I will provide some suggestions toovercome writers’ block.

I will end with a brief discussion about the

sec ons o a paper.



,to their level of comprehension.

Your selection of the category should help inidentifying your audience.



, ,it’s laboratory/field results, case histories and/orpractical applications of the new technology.



excessive technical jargon, and use appropriateterminology.



provide in your paper.

Do not divulge information that the customermay not really need but that the competitor canuse.

Don’t provide the “recipe” of a productconfiguration, process, or the like.



“ ” .

Some program committees reject any paper

outright containing company names,product/service/trade names.

Some committees are more lenient, particularlythose from smaller, or regional conferences.

If the committee perceives your paper to be a

mar e ng p ece, ey w re ec .

FOG INDEX is next.



“ ” your material will be difficult for a reader tounderstand.

Locate a section of your document that contains ateas wor s o no coun a or an or

“the”).



sentences that contain the words.

This is the average number of words persentence (A).



words of your sample.

This is P.



Index.

To reduce the Fog Index, break long sentencesinto two or more separate sentences.

Now that we have discussed someconsiderations, let’s move along to another

.



time needed to write a paper.

Here is a timeline for the various sub-tasks thatmust be performed and suggested amounts oft me to comp ete eac .



,due to the conference.

You might not be given that amount of time.

-, ,can take time for their company to sign off onthe paper.

Plus, the BHI reviewers need time to give a

oroug rev ew o your paper, as ey m ghave numerous papers to review at one time.



’ outline, make some decisions about the content,and produce a rough draft.

We will discuss some suggestions later on howto overcome wr ter s oc .



and sending it to the customer, if applicable.

You then upload the draft file to the OPS.



— people who reviewed the abstract.

You must maintain oversight of the reviewprocess.

e n orms e ev ewers o e r as v aemail, and provides a link to the document.

Reviewer delays are NOT controlled by the OPS;you must intervene.

Incorporate Reviewer edits, fill out any requiredcopyright/author info forms, and submit thepaper to the conference.

Now let’s talk about “Writer’s Block”.



.

Do not let writer’s block stop you.

Here are some tricks to help you get started.

e ey ea s to wr te somet ng —you canimprove it later.



.

Explain what the paper needs to say to another

person.

said, focusing on the main points rather thanevery word you spoke.

Feedback can help you recognize:

• If your word choice is poor

• If your explanation is unclear

• If your text is missing some information



.

Write down everything that you know, in no

particular order and with no particularformatting.

Write phrases/keywords, not completesentences.

Afterward, organize what you wrote thematically,.

Eventually, convert it into an outline and then adraft.



,choose one section, and write just that section.

When you finish, move on to another section.



,might send you an “Author Kit” on CD or providesa link to the files.

The Kit contains instructions, forms andemp a es.

We have reviewed considerations, timeline and’w .

Now let’s look at the basic parts of a technicalpaper.



SPE conference, many of these items apply toother conference papers.

The title should be concise, attract attention andg g e ma n po n o e paper.

No company names or company abbreviations inthe title.

u , u ,company.

NOTE: State Baker Hughes or Baker HughesIncorporated, NOT Baker Hughes Inc.



submitted, and you may modify it.

The introduction outlines the problem and brieflyexplains the solution.



abstract, only in much more detail.



,might also include these items.



,the overall flow will be similar.



instructions on the formatting of your paper.



before you send it to the conference.



.

Let me give you a summary of some key points I

have mentioned.

Make sure your information benefits theaudience, not the competition.

Avoid commercialism.

.

Follow a timeline.

Writing a Good Technical Paper

Documents

Transcript of Writing a Good Technical Paper