Writing a Plant Operating Manual
Moderators: Alexander Halser, Tim Green
-
- Posts: 4
- Joined: Sat Apr 28, 2018 12:23 pm
Writing a Plant Operating Manual
Hi,
I have to write a manual for a Water Treatment Plant.
The manual will basically be a huge collection of pdfs, for example instrument data sheets, PLC manuals, motor manuals, equipment manuals, etc.
I will barely have to write anything.
Since the client will also require a pdf version of the whole manual, I was wondering how Help&Manual behaves with "nested" pdfs.
I would need, under the main pdf, subsections that could actually explode to the detail manual of each instrument, equipment, etc.
Is this software able to do that?
I couldn't find anything in the help section about it.
Thanks
I have to write a manual for a Water Treatment Plant.
The manual will basically be a huge collection of pdfs, for example instrument data sheets, PLC manuals, motor manuals, equipment manuals, etc.
I will barely have to write anything.
Since the client will also require a pdf version of the whole manual, I was wondering how Help&Manual behaves with "nested" pdfs.
I would need, under the main pdf, subsections that could actually explode to the detail manual of each instrument, equipment, etc.
Is this software able to do that?
I couldn't find anything in the help section about it.
Thanks
- Tim Green
- Site Admin
- Posts: 23184
- Joined: Mon Jun 24, 2002 9:11 am
- Location: Bruehl, Germany
- Contact:
Re: Writing a Plant Operating Manual
Hi Riccardo,
Sorry, but Help+Manual doesn't handle PDFs like this directly. You can use the modular projects feature to create a modular project as you describe with a master project, in which you insert your individual sub-projects in the TOC. However, if you publish that as a PDF you will get one very large PDF, in which all the projects are merged together. See here for information on modular projects:
https://helpandmanual.com/help/index.ht ... odular.htm
The real question here is why you want to do this with PDF, which is generally not a good format for any kind of interactive access. It is also the worst possible format for online access, because before your users could read any single topic they would need to download the entire PDF for the related project, since each PDF is essentially a single long page. If you create a modular project as described above and publish it as WebHelp for viewing in a web browser it is very much superior to PDF. When users view it online their browser only needs to load the pages they are actually reading, and WebHelp is ideally suited for the kind of linked, non-linear viewing that is typical when reading documentation.
Despite having some interactive features, PDF is only really suitable for two things: Providing a printable version, because it has much better printing capabilities than any other format; and for texts that people are going to read in a linear fashion from beginning to end.
Sorry, but Help+Manual doesn't handle PDFs like this directly. You can use the modular projects feature to create a modular project as you describe with a master project, in which you insert your individual sub-projects in the TOC. However, if you publish that as a PDF you will get one very large PDF, in which all the projects are merged together. See here for information on modular projects:
https://helpandmanual.com/help/index.ht ... odular.htm
The real question here is why you want to do this with PDF, which is generally not a good format for any kind of interactive access. It is also the worst possible format for online access, because before your users could read any single topic they would need to download the entire PDF for the related project, since each PDF is essentially a single long page. If you create a modular project as described above and publish it as WebHelp for viewing in a web browser it is very much superior to PDF. When users view it online their browser only needs to load the pages they are actually reading, and WebHelp is ideally suited for the kind of linked, non-linear viewing that is typical when reading documentation.
Despite having some interactive features, PDF is only really suitable for two things: Providing a printable version, because it has much better printing capabilities than any other format; and for texts that people are going to read in a linear fashion from beginning to end.
Regards,
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
- Martin Wynne
- Posts: 2656
- Joined: Mon May 12, 2003 3:21 pm
- Location: West of the Severn, UK
Re: Writing a Plant Operating Manual
Hi Riccardo,Riccardo Schiavone wrote:The manual will basically be a huge collection of pdfs
How many is a "huge collection"?
Most desktop publishing programs and some PDF readers will open a PDF and export each page as an image. You could then include them in an H&M topic as a sequence of images, and publish the whole thing as Webhelp and/or as a single PDF.
For data sheets and technical manuals, if you select 8-bit PNG format it is very likely that the image files will be quite small, possibly smaller in total than the original PDF. Here for example this page is only 64KB, exported from PagePlus DTP:
But it does mean processing each input PDF file. If the collection is large, you could maybe automate the process with a script or macro.
You would get the option to add some additional text and/or links above/below/between the page images, which wouldn't be possible if a PDF was simply nested in the topic.
cheers,
Martin.
You do not have the required permissions to view the files attached to this post.
-
- Posts: 4
- Joined: Sat Apr 28, 2018 12:23 pm
Re: Writing a Plant Operating Manual
The manual in pdf is a requirement of the customer.
I am fully aware that they will basically never use the pdf, but I cannot avoid it.
I cannot convert pdfs into png.
Some equipments have 500-600 pages pdf manuals.
In total, I am looking at something like 5000+ pages of manuals.
I don't have a problem with having one single huge pdf.
As long as all the single pdfs are printed and the header is common and it is professionally looking.
Thanks
Regards
I am fully aware that they will basically never use the pdf, but I cannot avoid it.
I cannot convert pdfs into png.
Some equipments have 500-600 pages pdf manuals.
In total, I am looking at something like 5000+ pages of manuals.
I don't have a problem with having one single huge pdf.
As long as all the single pdfs are printed and the header is common and it is professionally looking.
Thanks
Regards
-
- Posts: 206
- Joined: Thu Jul 13, 2017 2:57 pm
Re: Writing a Plant Operating Manual
To convert a PDF to png images:Riccardo Schiavone wrote:I cannot convert pdfs into png. Some equipments have 500-600 pages pdf manuals.
- Open document in Acrobat Pro DC
- Navigate Tools > Export PDF
- Select Image : PNG
- Click Export
- Accept or amend the proposed folder
All the pages will be exported as <filename>_Page_<nnn>.png
- Tim Green
- Site Admin
- Posts: 23184
- Joined: Mon Jun 24, 2002 9:11 am
- Location: Bruehl, Germany
- Contact:
Re: Writing a Plant Operating Manual
Hi Riccardo,
See this chapter in the help for full details:
https://helpandmanual.com/help/index.ht ... odular.htm
If you're ever going to publish other output formats, it's very important to avoid topic ID conflicts between your sub-projects:
https://helpandmanual.com/help/index.ht ... ar_ids.htm
I would recommend setting up a dummy system with a master and a couple of demo sub-projects and your own customized PDF template to show your client to get approval and feedback before going all-in on it.
Then your best solution is to use modular projects. You create a separate project for what would normally be each individual sub-PDF. That gives you much more flexibility than having them in one huge PDF. Then you create a master project for publishing and insert references to the individual projects in the table of contents. Those projects remain independent; you are just inserting references in the TOC. When you publish, however, they are treated as part of the main project, effectively becoming "chapters" in that project.I don't have a problem with having one single huge pdf.
As long as all the single pdfs are printed and the header is common and it is professionally looking.
See this chapter in the help for full details:
https://helpandmanual.com/help/index.ht ... odular.htm
If you're ever going to publish other output formats, it's very important to avoid topic ID conflicts between your sub-projects:
https://helpandmanual.com/help/index.ht ... ar_ids.htm
I would recommend setting up a dummy system with a master and a couple of demo sub-projects and your own customized PDF template to show your client to get approval and feedback before going all-in on it.
Regards,
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
Re: Writing a Plant Operating Manual
I've been using this for a few weeks now:
https://www.reaconverter.com/
It can batch convert pdf's to whatever format you desire. It can also crop, resize and all sorts.
To convert a pdf takes about a minute per 100 pages.
You could then just drop all the images into a topic in one go.
https://www.reaconverter.com/
It can batch convert pdf's to whatever format you desire. It can also crop, resize and all sorts.
To convert a pdf takes about a minute per 100 pages.
You could then just drop all the images into a topic in one go.
Re: Writing a Plant Operating Manual
Sounds useful, but that website doesn't say who owns the product, there's no address or phone, the domain has WhoIs privacy, and it was registered in Russia. I wouldn't want to install that, let alone use it for anything at all sensitive.Ga Bowen wrote: ↑Mon Jun 29, 2020 7:25 pm I've been using this for a few weeks now: https://www.reaconverter.com/
-
- Posts: 2
- Joined: Tue Apr 09, 2024 2:45 pm
Re: Writing a Plant Operating Manual
Here is my way:
1. write your manuals in Word. save as .doc or .docx
2. convert those docs to PDF with something like this: https://oneconvert.com/pdf-converter/word-to-pdf
It's all free
1. write your manuals in Word. save as .doc or .docx
2. convert those docs to PDF with something like this: https://oneconvert.com/pdf-converter/word-to-pdf
It's all free