Technology Assessment Report
Use this skill to write the technology assessment report that a project
study delivers for a technology it may use. The report is generated from the
structured results of neqsim-technology-assessment and
neqsim-technology-fmirr, plus author-written narrative. It checks the inputs
and lists every open point instead of hiding it.
When to Use
- A concept or project study needs a technology assessment report for a new or
step-out technology.
- An assessment and FMIRR exist as data and must become a reviewable Word or
Markdown document.
- A report is updated after new evidence changes ratings (re-run, compare the
issues list, issue a new revision).
Inputs
assessment: a technology_assessment.v1 mapping (required).
fmirr: a technology_fmirr.v1 mapping (recommended whenever any element
needs qualification).
ReportMeta: title, subtitle, document number, revision, author, reviewer,
date, classification, status, project.
narrative: author-written paragraphs per chapter id, appended to the
generated text.
introduction_context: why the project considers this technology.
references: project documents, test reports and standards to add.
Outputs
- A
Report with chapters, tables and an issues list.
to_markdown() / save_markdown(path): Markdown with numbered tables.
save_docx(path): Word document with title block, contents field, header and
footer (classification, status, page numbers), landscape FMIRR chapter and
risk-coloured cells (needs python-docx).
to_dict(): JSON view for downstream tools.
Engineering Method
The report has fixed chapters so that reviewers always find the same content:
- Executive summary (generated from results).
- Introduction (purpose, scope, method, context).
- Technology qualification basis (description, use, environment, functions,
performance expectations, regulatory requirements). Keep this chapter
stable; it is reused in the qualification programme and qualification report.
- Technology description and decomposition.
- Technology maturity: novelty category and TRL per element and for the system.
- Enabling or enhancing technology.
- Step-out from existing experience (design, manufacturing, installation,
operability, fluids, operating conditions, lifetime).
- Benefits and risks.
- Standardisation and multi-implementation.
- FMIRR, first version (landscape).
- Preliminary outline of qualification activities, linked to critical modes.
- Conclusions and recommendations.
- Assumptions, data gaps and open points.
- References.
- Appendix A: definitions (novelty table, TRL scale, consequence and
probability classes).
Authoring workflow:
- Run the assessment and FMIRR; resolve flags and gaps where evidence exists.
- Build the report and read
report.issues.
- Write the narrative where judgement is needed: the justification of each
category and TRL, the reasoning for the role (enabling or enhancing), the
interpretation of step-out, and the recommendation. Cite the evidence by
document id.
- Add project references, set classification and status, build Word output.
- Review figures and tables in the document (Word: update fields so the
contents list fills in), then circulate to the expert panel.
- Re-issue with a new revision when evidence changes ratings.
Python Usage Pattern
from technology_assessment import from_dict as assess
from technology_fmirr import from_dict as rank
from technology_assessment_report import ReportMeta, build_report
assessment = assess(assessment_spec).assess()
fmirr = rank(fmirr_spec).evaluate()
report = build_report(
assessment,
fmirr,
ReportMeta(title="Technology Assessment Report: <technology>", author="<name>",
classification="Internal", status="Draft"),
introduction_context="<why the project considers the technology>",
narrative={"conclusions": ["<author conclusion>"]},
)
report.save_markdown("technology_assessment_report.md")
report.save_docx("technology_assessment_report.docx")
print(report.issues)
examples/build_example_report.py builds the report for the synthetic example.
Validated NeqSim Path
The report presents judgement and evidence; it computes nothing new. Attach
NeqSim study results (process, flow-assurance, mechanical-design, dynamic
simulation) as references and cite them in the narrative and in the FMIRR
re-rating basis.
Escalation
Do not issue the report for decision-making while report.issues contains
open items on novel elements, missing FMIRR coverage, or flags on the ratings.
Have a qualified expert panel review it and record the review.
Validation Checklist
Common Mistakes
| Symptom |
Cause |
Fix |
| Generic report without a position |
Narrative left empty |
Write justification and recommendations |
| Ratings differ between report and workshop |
Report not regenerated |
Rebuild from the current JSON |
| Contents list empty in Word |
Fields not updated |
Update fields in Word before issue |
| FMIRR chapter missing |
fmirr not passed |
Supply the FMIRR result |
| Evidence claims without sources |
Copy from marketing material |
Cite documented, accessible evidence only |
Limitations
- The chapter structure is a general, public structure; company templates,
numbering, gates and approval wording belong in an enterprise overlay.
- English output only; figures and drawings are not generated.
- Word output needs
python-docx; Markdown has no dependency.
References
- DNV-RP-A203, Technology qualification.
- ISO 20815, Production assurance and reliability management.
- ISO 14224, Collection and exchange of reliability and maintenance data for
equipment.
- NeqSim repository: https://github.com/equinor/neqsim
1---2name: neqsim-technology-assessment-report3calculation_basis: "advisory"4version: "0.1.1"5description: "Builds a full technology assessment report (Markdown and Word) for any technology from technology_assessment.v1 and technology_fmirr.v1 results: qualification basis, decomposition, novelty and TRL, step-out, benefits and risks, FMIRR, qualification outline, conclusions, open points. USE WHEN: a project study needs a technology assessment report as a deliverable, or an assessment and FMIRR must be turned into a reviewable document."6last_verified: "2026-10-27"7requires:8 python_packages: ["python-docx (Word output only)"]9 java_packages: []10 env: []11 network: []12metadata:13 source: https://skillmd.com/skills/equinor/neqsim-technology-assessment-report14---1516# Technology Assessment Report1718Use this skill to write the **technology assessment report** that a project19study delivers for a technology it may use. The report is generated from the20structured results of `neqsim-technology-assessment` and21`neqsim-technology-fmirr`, plus author-written narrative. It checks the inputs22and lists every open point instead of hiding it.2324## When to Use2526- A concept or project study needs a technology assessment report for a new or27 step-out technology.28- An assessment and FMIRR exist as data and must become a reviewable Word or29 Markdown document.30- A report is updated after new evidence changes ratings (re-run, compare the31 issues list, issue a new revision).3233## Inputs3435- `assessment`: a `technology_assessment.v1` mapping (required).36- `fmirr`: a `technology_fmirr.v1` mapping (recommended whenever any element37 needs qualification).38- `ReportMeta`: title, subtitle, document number, revision, author, reviewer,39 date, classification, status, project.40- `narrative`: author-written paragraphs per chapter id, appended to the41 generated text.42- `introduction_context`: why the project considers this technology.43- `references`: project documents, test reports and standards to add.4445## Outputs4647- A `Report` with chapters, tables and an `issues` list.48- `to_markdown()` / `save_markdown(path)`: Markdown with numbered tables.49- `save_docx(path)`: Word document with title block, contents field, header and50 footer (classification, status, page numbers), landscape FMIRR chapter and51 risk-coloured cells (needs `python-docx`).52- `to_dict()`: JSON view for downstream tools.5354## Engineering Method5556The report has fixed chapters so that reviewers always find the same content:57581. Executive summary (generated from results).592. Introduction (purpose, scope, method, context).603. Technology qualification basis (description, use, environment, functions,61 performance expectations, regulatory requirements). Keep this chapter62 stable; it is reused in the qualification programme and qualification report.634. Technology description and decomposition.645. Technology maturity: novelty category and TRL per element and for the system.656. Enabling or enhancing technology.667. Step-out from existing experience (design, manufacturing, installation,67 operability, fluids, operating conditions, lifetime).688. Benefits and risks.699. Standardisation and multi-implementation.7010. FMIRR, first version (landscape).7111. Preliminary outline of qualification activities, linked to critical modes.7212. Conclusions and recommendations.7313. Assumptions, data gaps and open points.7414. References.7515. Appendix A: definitions (novelty table, TRL scale, consequence and76 probability classes).7778Authoring workflow:79801. Run the assessment and FMIRR; resolve flags and gaps where evidence exists.812. Build the report and read `report.issues`.823. Write the narrative where judgement is needed: the justification of each83 category and TRL, the reasoning for the role (enabling or enhancing), the84 interpretation of step-out, and the recommendation. Cite the evidence by85 document id.864. Add project references, set classification and status, build Word output.875. Review figures and tables in the document (Word: update fields so the88 contents list fills in), then circulate to the expert panel.896. Re-issue with a new revision when evidence changes ratings.9091## Python Usage Pattern9293```python94from technology_assessment import from_dict as assess95from technology_fmirr import from_dict as rank96from technology_assessment_report import ReportMeta, build_report9798assessment = assess(assessment_spec).assess()99fmirr = rank(fmirr_spec).evaluate()100report = build_report(101 assessment,102 fmirr,103 ReportMeta(title="Technology Assessment Report: <technology>", author="<name>",104 classification="Internal", status="Draft"),105 introduction_context="<why the project considers the technology>",106 narrative={"conclusions": ["<author conclusion>"]},107)108report.save_markdown("technology_assessment_report.md")109report.save_docx("technology_assessment_report.docx")110print(report.issues)111```112113`examples/build_example_report.py` builds the report for the synthetic example.114115## Validated NeqSim Path116117The report presents judgement and evidence; it computes nothing new. Attach118NeqSim study results (process, flow-assurance, mechanical-design, dynamic119simulation) as references and cite them in the narrative and in the FMIRR120re-rating basis.121122## Escalation123124Do not issue the report for decision-making while `report.issues` contains125open items on novel elements, missing FMIRR coverage, or flags on the ratings.126Have a qualified expert panel review it and record the review.127128## Validation Checklist129130- [ ] Assessment and FMIRR are current and refer to the same technology.131- [ ] Every novel element has failure modes in the FMIRR.132- [ ] Narrative justifies each category, TRL and the enabling/enhancing role.133- [ ] Evidence is cited by document id; none is invented.134- [ ] Classification, status, revision and document number are set.135- [ ] Open issues are resolved or accepted explicitly.136- [ ] Word contents field updated; tables and landscape chapter checked.137- [ ] Expert panel review recorded.138139## Common Mistakes140141| Symptom | Cause | Fix |142| --- | --- | --- |143| Generic report without a position | Narrative left empty | Write justification and recommendations |144| Ratings differ between report and workshop | Report not regenerated | Rebuild from the current JSON |145| Contents list empty in Word | Fields not updated | Update fields in Word before issue |146| FMIRR chapter missing | `fmirr` not passed | Supply the FMIRR result |147| Evidence claims without sources | Copy from marketing material | Cite documented, accessible evidence only |148149## Limitations150151- The chapter structure is a general, public structure; company templates,152 numbering, gates and approval wording belong in an enterprise overlay.153- English output only; figures and drawings are not generated.154- Word output needs `python-docx`; Markdown has no dependency.155156## References157158- DNV-RP-A203, *Technology qualification*.159- ISO 20815, *Production assurance and reliability management*.160- ISO 14224, *Collection and exchange of reliability and maintenance data for161 equipment*.162- NeqSim repository: https://github.com/equinor/neqsim