Galili: Documentation and Training
Knowledge transfer
Technical writers, engineers and consultants who turn the knowledge of the engineering team into technical literature, engineering documentation and training, to the standard set in the contract.
Services
Technical literature and maintenance manuals
User manuals, operation manuals, system and maintenance manuals, and software documentation (API, SDK). For the operator, the technician and the maintainer in the field. The writing is based on a maintenance task analysis, and the manual is built to the standard in the contract. Delivered as PDF, as Word or as an interactive electronic manual.
Engineering documentation and specifications
Production and assembly instructions, parts catalogs, technical illustrations and ILS planning. For the production floor, the supply chain and the engineering department. When required, catalogs and assembly instructions are built in interactive 3D from the CAD data, with RapidAuthor.
Training development and learning materials
SCORM e-learning in 2D and 3D, micro-learning, classroom kits (instructor guide, trainee booklet, tests) and instructor training. The curriculum is derived from the tasks the learner has to perform.
Consulting and building documentation processes
ILS consulting, organizational and regulatory consulting, and building a documentation process in the organization: templates, writing rules, choice of standard and choice of tools.
Standards
Galili produces to every standard supported by one of its three tools.
| Standard | What Galili produces to it | Through which tool |
|---|---|---|
| S1000D | CSDB, data modules, publication module (PM), HTML IETP, PDF, and import from Word | Xignal · RapidAuthor · GALILIX (data module export in development) |
| ATA iSpec 2200 | Aviation maintenance documentation | RapidAuthor · Xignal |
| DITA 1.3 | Structured documentation projects, and DITA-based 3D documentation | GALILIX · RapidAuthor |
| SCORM | E-learning in 2D and 3D | RapidAuthor |
| MIL-STD-40051 | Fault isolation numbering, and rules for checklists | GALILIX |
| MIL-STD-38784 | Style rules for a technical manual, and Word templates in Hebrew and English | GALILIX |
How we work
Five stages, in this order, in every project.
- Consultation. We find out what the system is, who the reader is, and which standard the contract requires.
- Mapping and scope. We build an outline of the document, a list of chapters and topics, and the quote is based on it.
- Writing. The writers work with your engineers and submit a first draft.
- Review and approval. Every draft comes back to you for review. There are usually two rounds before the final draft.
- Delivery and implementation. The document is delivered in the format set in the contract and, when required, with training for the team.
Let us start with a conversation.
Tell us what you have today: a new system with no documentation yet, an old manual that needs updating, or a team that needs training. We will ask a few questions, work out what is really needed, and suggest a way of working that fits you. The conversation commits you to nothing, and we will get back to you ourselves.