Inactive

The scope of the work is to procure a COTS product solution that is customized for authors that have little to no experience with writing XML language The contractor shall provide COTS software soluti... The scope of the work is to procure a COTS product solution that is customized for authors that have little to no experience with writing XML language The contractor shall provide COTS software solution for authoring in XML with licenses for up to 1,000 users to create and maintain tax instructions and publications. This software will assist in authoring tax instructions and publications in XML format to be used as source files in the creation of Portable Document Format (PDF), Hypertext Markup Language (HTML), Docbook XML, and ePub that meets the following features: Compatible with existing IRS DTD Requires minimal retraining < 2 hours Is a web-based solution that can be hosted on site with the ability to be hosted in a cloud environment. Customizable to add customized features and interaction with 3rd party tools, such as Link Author, Adobe AEM Assist, OneDrive, or SharePoint online. A configurable WYSIWYG display that able to closely resemble the PDF using a single column format. Such that when author the user has a very good understanding of how the composed file will look. Standardized linking to the Code of Federal Regulations (CFR), Internal Revenue Code (IRC), Internal Revenue Bulletin (IRB), and Revenue Procedures and Revenue Rulings. Ability to link to specific locations within the XML file. Ability to add anchors within XML file to link to the specific location. Customizable Metadata. Who the owner business unit(s) is, user business unit(s) and author(s). Also need to identify if there is Official Use Only (OUO) within the document, the catalog number, and if active or obsolete. When the software starts up, checking for the values of the respective part title and chapter title of the file in a centralized XML file stored on a web server and update the value within the user’s file. If no value is present on the server, inform the user of such. When user completes the part n.o attribute on the tag, pulling the respective part title from a centralized XML file stored on a web server. If no value is present on the server, inform the user of such. When user completes the chap no attribute on the tag, pulling the respective chapter title from a centralized XML file stored on a web server. If no value is present on the server, inform the user of such. Locking and tags from end user editing. Only the authoring software can alter the content of the tags. Context Rules always on. If there are rules, we need all XML files to follow, why would we allow someone to ever complete actions/edits outside of the rules? Providing the ability to turn off the display of software features that our users will never use. Plain language error messages for explaining context errors in completeness check Plain language text for all menu items, warnings, tooltips and settings within the software Ability to insert tables. Locate controls for features all together--i.e Table editing is in one menu not 4 menus/views. Tables must have a header row. This row is read before all the body rows. This is required for 508 compliance (visually impaired employees who use screen readers). Tables to have a summary (508 compliance). Ability to edit table widths. Currently we have 3 inch, 4.5in, 6.625in and 8.5in. Portrait or landscape tables. Table templates. Can save a table as a template and then insert it anywhere in the IRM. Default table templates already created. Such as if/then table and if/and/then tables. Templates named with plain-language, not abbreviations. For tables: Ability to edit lines between columns, rows and outside border. Ability to copy/paste tables from other sources/software. (Ex. Excel, Word, HTML, PDF). Ability to insert graphics. Graphics must have descriptors, such as paragraphs, lists, etc. This is required for 508 compliance. Ability to view graphics within XML file. A check to resolve any errors. Currently it is called Check Completeness. Such as, if an element or tag has no content within it (empty tag). Ability to find/replace text and tags. Ability to cut/copy/paste text and tags. Ability to copy directly from Microsoft Word and other kinds editing programs. EG, a bullet list from .docx to .xml is recognized and tagged as a bullet list. Ability to select the entire tag(s) and the content within it. Ability to track changes. Accept/reject one change at a time or accept/reject all at once. Ability to view tracked changes, original document, or new document without tracked changes highlighted. Display who made the change at exactly what time. Show disposition of all changes (accept / reject, defer, description, ID, date, time stamp). Ability to create a compare file. This would compare two different versions open, two different saved files, or compare from the last saved version of the same document. Ability to merge a document from a compare. Ability to bold, italicize, underline and, use quotes for text. Ability to add a Note, Exception, Reminder, Example, and Caution indented within a paragraph. Ability to insert comments. Ability to add bookmarks. Ability to add quickmarks and collapse/expand elements. Insert Symbols. Page setup - modify headers/footers and margins. Print to Adobe PDF. Ability to View tags or no tags. Tool to resolve double-spacing. Tool to verify cross-references within XML document. Ability to add a “link” to an email address (and it opens Outlook when you click on it). To keep the structure of our IRMs. Part – Chapter – Section – Subsection (it nests 5 subsections deep). Display the titles of the part, chapter, section, and all the subsections. Ability to add paragraphs. Ability to add lists. Step list, alpha list and bullet list. balanced selections for text highlighting ability to remove irrelevant tags from being options ability to update SELECT boxes (such as current IRS business units) units without a software update. Date input with optional calendar tool. Providing a feature that allows the user to delete all tags from the file in a single click. Allowing users to open a sample file prepopulated with data for training purposes provided by IRS- “Sample IRM”, “Sample Obsolete IRM”, “Sample CCDM”, “Sample Obsolete CCDM” Ensuring the text of all s follows the format Month DD, YYYY, whether it be the actual month, day, and year, or the text “Month DD, YYYY” Ensuring the text of all s follows the format (MM-DD-YYYY), whether it be the actual month, day, and year, or the text “(MM-DD-YYYY)” Displaying generated text in a different color than user-entered text Providing a “symbol key” that shows a symbol (character), its name, and its definition Providing a “tag key” that shows a tag name, its definition, and example of its use, and the tag’s attributes and respective definitions Adjustment of text font independent of tag size Allow symbols typed from qwerty keyboard instead of Insert symbol function. Allow tags for EFOIA and other new privacy designations in addition to restrict/norestrict for OUO. The solution shall capture and track text changes directly in the file along with reason, reference, user ID, date and time stamp. (38,39,50, 85,86) The solution shall embed technical authorities (TA’s) and reasons for change. Reflects current gallery solution through use of “U” notes The solution shall cite references to technical authorities with corresponding links. Currently Arbortext highlights TA tags but doesn’t give a list. The solution shall generate a list of technical authority tags. The solution shall have visual editing features to hide tags for a clean paragraph review with the option to turn on or off throughout the editing process. Stopped here 3/18/2022 Need to write “accept / reject from compare (merge)” The solution shall allow accepted changes to be integrated automatically into the main document. The solution shall be able to display a print preview. The solution shall have the ability to create tables within tables (example: keeping text right justified and the column header centered). The solution shall allow for a table or picture to be depicted across either one, two, or three columns (To be able to span tables across columns) The solution shall be able to provide a copy and pasting feature that retains the proper characters. (such as when coping content from Microsoft Word or web browsers) The solution shall support authoring documents in two and three column formats. The solution shall provide commonly used word processing / publishing features (Critical) To include: • Grammar Check • • Spelling Check • Completeness Check (parser) Thesaurus The solution shall perform comparison to identify differences between similar content in more than one product. The solution shall provide index generation. Allow elements to be selected (words and phrases) for indexing. If automated, then must be a default way to override. The solution shall identify automatically when elements need to show in the table of contents and provide a way to override. The solution shall have the ability to identify other tax products containing similar language / topics as the product is being modified and be able to pull commonly used text from a central storage. Reusable content The solution shall handle Unicode format or multi-byte character sets to support multiple languages. The solution shall support right to left languages. The solution shall provide easily retrievable catalogue of templates, tables and standard language. The solution shall integrate with existing publication processes and tools. (Guarantee the integrity of the file so as not to disrupt downstream processing) The solution shall provide constant, continuous, real-time XML validation during the authoring and editing process. Describe whether during the process, when saving the document or upon completion of document. The solution shall provide desktop and network print functionality. (system requirement) The solution shall adhere to Section 508 compliance. The Contractor shall support the configuration, implementation, and integration of the COTS solution with the IRS infrastructure. The number of technical integration interfaces supported during the period of performance may vary based on the use cases requested by the COTS solution.