In addition to EN 301 549 requirements, this application could also generate language to be included in the Statement of Work (SoW) and the evaluation criteria (mandatory and rated).
Desired functionality:
Admins can create and edit solicitation language "snippets", and attributes related to the procurement, not the product itself, e.g. "Is it COTS or custom development"
Admins can create and edit the mappings between the attributes and those snippets
Users can select procurement-specific attributes and have these mapped to relevant snippets (Step 1)
Users can fine-tune the selection of these snippets (Step 2)
Users can download the generated contract language separately from the EN 301 549 requirements (Step 3)
Note that the language generated by the application would be considered a starting point for technical authorities, to be fine-tuned to the product or agency. To keep things simple, I suggest the snippets be static rather than dynamically generated (e.g. inserting the name of the product or agency into a sentence).
In addition to EN 301 549 requirements, this application could also generate language to be included in the Statement of Work (SoW) and the evaluation criteria (mandatory and rated).
Desired functionality:
Note that the language generated by the application would be considered a starting point for technical authorities, to be fine-tuned to the product or agency. To keep things simple, I suggest the snippets be static rather than dynamically generated (e.g. inserting the name of the product or agency into a sentence).