ContractWritingFed_V1.xlsx
XLSX spreadsheet 19 KB Posted
- Attached to
- CONTRACT WRITING SOFTWARE
- Solicitation number
- 63NLRB19RCWS
- Issued by
-
National Labor Relations Board
About this file
Characteristics
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| 1 | Acquisition/eSourcing |
| 2 | System must provide comprehensive acquisition support for all FAR-based a documents , clauses and templates, with auto merge of contract or solicitation field data |
| 3 | Must adhere to all applicable Agency and Federal rules, provisions, regulations, and laws |
| 4 | Able to support all steps in the procurement process from creation of Procurement Requests through contract closeout. With task related email alerts, escalation and monitoring |
| 5 | System must provide workflow for the routing, review, and approval of acquisition documents and procurement requests. Logic relating to workflow must be configurable. |
| 6 | Should have configurable email notification process to inform users or an external party, of actions within an agency defined amount of time |
| 7 | Should have the ability to have unlimited configurable fields. |
| 8 | Should have the ability to mark procurements and contracts as secured for National Defense |
| 9 | Ability to generate Procurement Requests and route them in the system |
| 10 | The system must provide the ability to upload external files and associate them with system generated documents (awards, procurement requests, etc.). And provide full text document searching |
| 11 | The system must have the ability to create FAR - compliant solicitations. |
| 12 | The system shall prevent or warn the end user of duplication of clauses in multiple contract or solicitation sections. |
| 13 | System must have a online portal access to collect bid documents, pricing, and question and answers from interested vendors/respondents |
| 14 | Track Unlimited notes with audit trail tracking |
| 15 | |
| 16 | Vendor Management |
| 17 | Track large number of vendor fields with configurable fields |
| 18 | Track and insert sub-grids and tables on vendor records |
| 19 | The system must provide the ability to upload external files and associate them with vendor records |
| 20 | Provide pre and post contract rating and score cards |
| 21 | Integrate with external vendor management system |
| 22 | Produce documents such as award letters, cancel letters, etc with mergable fields on templates |
| 23 | |
| 24 | Contracts |
| 25 | The system must support "hybrid" contracts where Contract Line Items are a mix of Fixed Price, Labor Hour, Cost Plus Fixed Fee, Time and Material, etc. |
| 26 | Provide configurable checklists for the contract file content by contract type. |
| 27 | The system must provide the ability to upload external files and associate them with system generated documents (awards, procurement requests, etc.). And provide full text document searching |
| 28 | The system must provide the ability to upload external files and associate them with system generated documents (awards, procurement requests, etc.). And provide full text document searching |
| 29 | Documents should be able to be locked or have a check in/out feature |
| 30 | Track period of performance at the contract level |
| 31 | Provides Contract Clause intelligence evaluates contract/procurement fields and inserts required FAR Clause |
| 32 | Ability to modify required clauses within the contract terms and conditions. |
| 33 | Ability to add and edit specific clauses rules for the purposes of contract clause generation. |
| 34 | Track line item based pricing/costing with qty, rate, unit of measure, description, account code, with sorting and grouping |
| 35 | Track Unlimited notes with audit trail tracking |
| 36 | The system shall identify Contracting Officers , POCs and other related employees for solicitations and contract and shall be configurable. |
| 37 | Accommodate entering existing contracts that were awarded on paper or historic data into the new system so that they may be managed electronically. System must accommodate the conformed view of the pre-existing contract. |
| 38 | The system shall ensure when a contract is modified that the most recent vendor record is incorporated into the modification. |
| 39 | System shall include a task calendar with day, week, monthly and searchable views |
| 40 | System shall include grouping by organization/department/division, type, project, contract owner |
| 41 | System shall include secured, electronic collaboration with external parties for contract negotiation and collaboration |
| 42 | Templates must support mergable fields and rules based text |
| 43 | |
| 44 | Workflow |
| 45 | System shall have tasks that can perform workflow , kick off new steps, and update and/or close out the contract |
| 46 | The system shall have the ability to define custom Milestone Tasks steps that can map back to system fields. |
| 47 | The system shall have the ability to create steps independent or dependent of one another. |
| 48 | The system shall have the option to define processing time (notify days a head) settings for each milestone for contracts managed by a specific division or team. |
| 49 | The system shall allow the ability to track milestones to existing solicitation, vendor, contract records |
| 50 | The system shall allow the ability to report on any and all end-user data via reports |
| 51 | Ability to automatically notify designated user via electronic mail prior to the expiration of an option year based on line item period of performance. |
| 52 | The system shall be able to provide notifications to the contracting employees based on configurable rules |
| 53 | System shall include the assignment of deadlines and owners to all deliverables and tasks |
| 54 | System shall include the option for sending alerts when a step has not been performed. |
| 55 | System shall provide the flexibility for reassignment of contracts between and within user organizations. |
| 56 | System should provide the ability to generate one-time, recurring, and group tasks events |
| 57 | |
| 58 | Purchase Orders |
| 59 | System must accommodate the use of one Purchase Order/Request to fund multiple contracts, and multiple PRs to fund one contract. |
| 60 | The system must provide the ability to upload external files and associate them with system generated documents (awards, procurement requests, etc.). And provide full text document searching |
| 61 | Track spend management to monitoring PO allocation versus contract funding limits |
| 62 | Ability to track delivery orders against IDIQ contracts and ensure that guaranteed minimum order requirements are met. |
| 63 | System shall include budget and fiscal year tracking, funding source, limits of funding, at both the PO Level and Line Item level. |
| 64 | Must allow for a user to identify multiple shipping locations for a line item. |
| 65 | The system must be able to electronically post a pre-solicitation notice to FBO |
| 66 | Quantity, unit price, unit of measure, and extended price, discount, notes shall be recorded at the line item level. |
| 67 | |
| 68 | Reports |
| 69 | Ability to track workload by contract specialist/officer. |
| 70 | All data elements shall be available for reporting performed with ad hoc reporting software. |
| 71 | All data elements shall be available for queries within the system. |
| 72 | Must provide standard reports that allow end users to view information regarding their contracts and work volume. Include functionality that allows administrators to configure standard reports. |
| 73 | The system shall provide a selection of reports to allow users to gather information on number and types of actions processed and the time required to perform actions. |
| 74 | Shall generate output reports, query results, and data files, using multiple formats as specified. Such formats can include online display, printed report, Portable Document Format (PDF), Microsoft (MS) Word, Excel. |
| 75 | Shall generate output reports, query results, and data files, using multiple formats as specified. Such formats can include extensible Markup Language (XML), American Standard Code for Information Interchange (ASCII) or delimited text file. |
| 76 | Draft Request for Quotation Contract Writing System and Support Services |
| 77 | System shall include a full report designer which allows end-users to develop reports that can be saved and re-run |
| 78 | The system shall include a report builder that provides data grouping, totals, sub totals, calculated columns, export to PDF, MS Word, Excel, CSV, HTML, and XML |
| 79 | System should include Ad-hoc reporting capability. |
| 80 | |
| 81 | Interoperability/Usability |
| 82 | Must be web based without onsite hosting |
| 83 | System shall have dashboards to provide personalized views by user |
| 84 | The system must be able to receive vendor information that is relevant to contract awards from a secure download from the System for Award management (SAM). System must be designed at a minimum to accommodate a daily vendor update that incorporates adds, changes, and deletes; and a monthly update that is a full update from SAM. Daily update process must take no longer than four hours. Monthly update process must take no longer than 8 hours. Alternatively, a real-time interface from the Contract Management System to SAM is acceptable. The real time interface shall import the most recent contract vendor record into the contract award document prior to finalizing. |
| 85 | The system must be able to electronically post a pre-solicitation notice to FBO in addition to transfering data to FPDS via interfacing |
| 86 | The System must run on mobile devices such as tablets. |
| 87 | The system shall be capable of interfacing to the financial system - Oracle Federal Financials |
| 88 | Ability to track workload by contract specialist/officer. |
| 89 | The system must generate electronic versions of standard forms and should use other electronic substitutes for paper documents whenever practicable |
| 90 | |
| 91 | Signatures |
| 92 | Ability to support unilateral digital signature. |
| 93 | Ability to support bilateral digital signature. |
| 94 | Ability to support electronic document approvals with configurable approval processing |
| 95 | |
| 96 | Security |
| 97 | Ability for single sign on should the department implement single sign on. |
| 98 | Ability to restrict access for users by document, branch, division, component. |
| 99 | The system shall enforce limitations on the user’s ability to perform actions based on the user’s documented authority in his user account (e.g. warrant limits). |
| 100 | Ability to ensure segregation of duties. The system shall be able to segregate role-based capabilities and limit access to these functions to individuals with appropriate authority. Duties such as authority to issue contracts, order goods and services, receive goods and services; certify availability of funds shall be able to be assigned to different individuals to minimize the risk of misuse to the greatest extent possible. |
| 101 | Access to functional and technical capabilities shall be controlled by role-based authorities granted during system configuration. |
| 102 | The system shall provide at least X configurable data fields that can be set up through the application front end for the purpose of capturing additional information relating to requisition, solicitation, and award documents. |
| 103 | Ability to identify who made any file content changes in the end-to-end process. |
| 104 | Multiple user security profiles must be created to control the access to all of the proposed system's features and functions by different groups of users |
| 105 | |
| 106 | System Configuration |
| 107 | The system shall allow for detailed information about personnel (name, phone number, email, etc.) to be added to standard drop-down lists (such as COR, requester, etc.) without requiring a named user account. |
| 108 | Data traceability - system must establish an audit trail for requisitions, solicitations, and award documents. The audit trail must record the calendar date and time that a document status or phase changed and the user name that made the change. If another system is responsible for the change in document status, the system must be identified in the audit information. The system identifier and transaction identifier shall be captured. |
| 109 | The system shall not impose limitations on the number or type of vendors, contract types, custom fields, sub tables, documents, sections, or workflow rules |
| 110 | Ability to promptly switch configuration settings & business rules |
| 111 | Ability to configure the system quickly along certain pre-defined parameters, fields, sub-grids /tables, and user regional settings |
| 112 | Ability to change configuration settings as business processes change through a system Administration-type user interface. |
| 113 | Designed to allow for future growth and enhancement through system scalability (e.g., software, hardware) and scalable solution to provide ability to expand to accommodate growing user population and storage requirements for electronic records. |
| 114 | Shall deliver the capability to integrate with an agency operated e-mail system. This capability Shall include the ability to distribute application-generated email messages. |
| 115 | The system shall provide the capability for the user to initiate an email that includes contracts, forms, or documents from within the system to the external email. |
| 116 | Provide function for bulk import and upload of records |
Sheet2
Sheet3
Sheet4
| Access to working documents (contract and includeing documentation) shall be restricted during the contract negotiation phase. Upon full execution of the contract, the fully executed contract can be accessed with a lower level of security/restriction. |
| Expiring insurance certificates or bonding requirements |
| System must capture unlimited contract information and be searchable data fields. |
| System shall include a full report designer which allows end-users to develop reports that can be saved and re-run |
| System shall include a task calendar with day, week, monthly and searchable views |
| System shall include grouping by organization/department/division, type, project, contract owner |
| System shall include secured, electronic collaboration with external parties for contract negotiation and collaboration |
| System shall include the assignment of deadlines and owners to all deliverables and tasks |
| System shall include the option for sending alerts when a step has not been performed. |
| System shall provide the flexibility for reassignment of contracts between and within user organizations. |
| System should include Ad-hoc reporting capability. |
| System should include the delegation of signature authority when the primary signator/delegate is not available. |
| System should provide the ability to generate one-time, recurring, and group tasks events |
| Templates must support mergable fields and rules based text |
| The system shall include a report builder that provides data grouping, totals, sub totals, calculated columns, export to PDF, MS Word, Excel, CSV, HTML, and XML |
File details come from the government source that posted it.