J.1_Attachment_01_A001.xlsx
XLSX spreadsheet 167 KB Posted
- Solicitation number
- 1331L519R13OS0005
About this file
This is a solicitation amendment for a business applications solution. The amendment incorporates changes to Sections C, H, and L of solicitation 1331L519R13OS0005. The solicitation is seeking proposals for a commercial off-the-shelf business applications solution to replace legacy systems currently used by the Department of Commerce Office of the Secretary. Offerors must submit proposals by the revised due date of April 15, 2019. The period of performance is one base year with four one-year options. The place of performance is Washington, DC. The NAICS code is 541511. Small businesses are encouraged to respond.
J.1_Attachment_01_A001
View the file
Other files
Show all 32
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
Data_ConsolidatedReq
| DOC Requirement Information | |||||||||
| Line # | Scope Area | Name | Description | Group | Sub-Group | Req. Source | Identified Software Solution | Method for Meeting Requirement | |
| 1 | Acquisitions | Acquisition Planning | The system must have the ability to capture, track and report on advanced acquisition plans (and capture unique plan number) based on bureau requirements. | Acquisitions | Advanced Acquisition Planning | DOC | |||
| 2 | Acquisitions | Forecasting | The system shall provide planning data so Contract Specialist workloads can be forecasted and estimated. | Acquisitions | Advanced Acquisition Planning | DOC | |||
| 3 | Acquisitions | Planning Metrics | The system shall enable the calculation of planning metrics, on a predefined basis, to compare estimated acquisitions to actual acquisition submissions. | Acquisitions | Advanced Acquisition Planning | DOC | |||
| 4 | Acquisitions | Acquisition Planning Document Routing | The system shall provide the capability to route documents to the pre-established routing lists. | Acquisitions | Advanced Acquisition Planning | DOC | |||
| 5 | Acquisitions | Acquisition Planning Attachments | The system shall provide the capability to support attachments with various file extensions (related to "Whitelist" functionality.) | Acquisitions | Advanced Acquisition Planning | DOC | |||
| 6 | Acquisitions | Requisitioning | The system must capture customer requirements in an automated system. | Acquisitions | Requisition Management | DOC | |||
| 7 | Acquisitions | Requisition Document Routing | The system shall provide the capability to route documents to the pre-established routing lists. | Acquisitions | Requisition Management | DOC | |||
| 8 | Acquisitions | Requisition Attachments | The system shall provide the capability to support attachments with various file extensions (related to "Whitelist" functionality.) | Acquisitions | Requisition Management | DOC | |||
| 9 | Acquisitions | Requisition Data - Accounting String Validation | The system shall provide the capability to validate accounting strings against the financial system real-time | Acquisitions | Requisition Management | DOC | |||
| 10 | Acquisitions | Requisition Line Item Designations | The system shall provide the capability to allow the following designations for a line in the Acquisition system such as: Subject to Availability of Funds (SAF), Option Year (OLI) and Government Furnished Property (GFP). | Acquisitions | Requisition Management | DOC | |||
| 11 | Acquisitions | Requisition Commitment | The system shall provide the capability to ensure that required financial data from requisitions is sent to the financial system in real time (e.g. Initial commitment, modifications to initial commitment and cancellation of the commitment shall be fully integrated with the financial system). | Acquisitions | Requisition Management | DOC | |||
| 12 | Acquisitions | Requisition Data - Integration Validation | The system shall provide the capability for the Acquisition system to allow a way for a user to ascertain that the integrated commitment transaction was successful (approval message) or that there was an error in processing (error messages and/or access to error logs, etc.). | Acquisitions | Requisition Management | DOC | |||
| 13 | Acquisitions | Requisition Data - Acquisition System as System of Record | The system shall provide the capability for the Acquisition system to be the system of record for Acquisition documents. Creation/Modification of such documents must not be allowed directly in the financial system outside of addressing rare data corruption issues. Such data corrections, if absolutely necessary, must be performed by personnel with specified authority to carry out the needed actions in the financial system. | Acquisitions | Requisition Management | DOC | |||
| 14 | Acquisitions | Requisition Vendor Search | The system shall provide the capability to search Acquisition vendors at a minimum by DUNS or NAME or SAMMI | Acquisitions | Requisition Management | DOC | |||
| 15 | Acquisitions | Requisition Funding | The system shall provide the capability for the Acquisition system to allow upward/downward/cancel modifications to the requisition document. | Acquisitions | Requisition Management | DOC | |||
| 16 | Acquisitions | COTR/COR Assignment | The system must allow the user to choose the COTR/COR that will be assigned to the resultant award. Authority levels (i.e. COR I, II, III) need to be captured and warnings issued if the Authority level and Award Amount are not accurate. | Acquisitions | Requisition Management | DOC | |||
| 17 | Acquisitions | Requisition Data - Funds Check | The system shall provide the capability to check funds against the financial system real time | Acquisitions | Requisition Management | DOC | |||
| 18 | Acquisitions | Requisition Data - Independent Validation | The system shall provide the capability to ensure that data validations for both acquisition and financial data occur at the earliest possible point of entry. | Acquisitions | Requisition Management | DOC | |||
| 19 | Acquisitions | Requisition Data - Acquisition/Financial System Data Reconciliation | The system shall provide the capability for the Acquisition and Financial personnel to be provided with a mechanism to reconcile data and validate the data integrity between the two systems. | Acquisitions | Requisition Management | DOC | |||
| 20 | Acquisitions | Election of One or More Vendors on Requisition | The system shall provide the capability for the Acquisition system to allow election of one or more vendors on a Acquisition request. | Acquisitions | Requisition Management | DOC | |||
| 21 | Acquisitions | Solicitation Management | The system shall provide the capability to process all solicitation types specified in the FAR including, but not limited to the following: Solicitation (IFB, RFP, RFQ). | Acquisitions | Pre-Solicitation/Solicitation | DOC | |||
| 22 | Acquisitions | Solicitation Document Routing | The system shall provide the capability to route documents to the pre-established routing lists. | Acquisitions | Pre-Solicitation/Solicitation | DOC | |||
| 23 | Acquisitions | Solicitation Data - Independent Validation | The system shall provide the capability to ensure that data validations for acquisition data occur at the earliest possible point of entry. | Acquisitions | Pre-Solicitation/Solicitation | DOC | |||
| 24 | Acquisitions | Solicitation Line Items | The system shall allow the Acquisition Office to consolidate line items and track the funding source back to the original line item. | Acquisitions | Pre-Solicitation/Solicitation | DOC | |||
| 25 | Acquisitions | Solicitation Consolidation | The system must allow multiple requisitions to be combined during the solicitation process | Acquisitions | Pre-Solicitation/Solicitation | DOC | |||
| 26 | Acquisitions | Solicitation Multiple Solicitations | The system must allow the Acquisition Office to generate multiple solicitations from one or more requisitions | Acquisitions | Pre-Solicitation/Solicitation | DOC | |||
| 27 | Acquisitions | Solicitation Vendor Search | The system shall provide the capability to search Acquisition vendors at a minimum by DUNS or NAME or SAMMI | Acquisitions | Pre-Solicitation/Solicitation | DOC | |||
| 28 | Acquisitions | Solicitation Detailed Status | The system must track "true status" of acquisition document with dates. | Acquisitions | Pre-Solicitation/Solicitation | DOC | |||
| 29 | Acquisitions | Solicitation FBO Format | The system must have the ability to export to Government wide point of entry. | Acquisitions | Pre-Solicitation/Solicitation | DOC | |||
| 30 | Acquisitions | Solicitation Attachments | The system shall provide the capability to support attachments with various file extensions (related to "Whitelist" functionality.) | Acquisitions | Pre-Solicitation/Solicitation | DOC | |||
| 31 | Acquisitions | Award Management | The system shall provide the capability to process all award types specified in the FAR including, but not limited to the following contract types: Awards (Contracts, PO, DO/TO, BPA, IDIQ, Interagency Agreements etc.) through award closeout. | Acquisitions | Award Management | DOC | |||
| 32 | Acquisitions | Award Document Routing | The system shall provide the capability to route documents to the pre-established routing lists. | Acquisitions | Award Management | DOC | |||
| 33 | Acquisitions | Award Workload Management | The system shall provide the ability to manage individual and group workloads; including document reassignment. | Acquisitions | Award Management | DOC | |||
| 34 | Acquisitions | Award Workload Tracking | The system shall provide workload tracking and generate metric and status data for acquisition personnel, managers, customers and stakeholders. | Acquisitions | Award Management | DOC | |||
| 35 | Acquisitions | Group Workload Management Reports | The system must have the ability to produce management reports that provide data on group workload levels and individuals within each group. | Acquisitions | Award Management | DOC | |||
| 36 | Acquisitions | Individual Workload Management Reports | The system must have the ability to produce management reports for individual workload levels and capacity | Acquisitions | Award Management | DOC | |||
| 37 | Acquisitions | Award Attachments | The system shall provide the capability to support attachments with various file extensions (related to "Whitelist" functionality.) Provide ability for users across the agency to view attachments (i.e. Accounts payable staff) | Acquisitions | Award Management | DOC | |||
| 38 | Acquisitions | Award - Accounting String Validation | The system shall provide the capability to validate accounting string against the financial system real-time | Acquisitions | Award Management | DOC | |||
| 39 | Acquisitions | Award - Funds Check | The system shall provide the capability to check funds against the financial system real time | Acquisitions | Award Management | DOC | |||
| 40 | Acquisitions | Award Multiple Awards | The system must allow the Acquisition Office to generate multiple awards from one or more requisitions | Acquisitions | Pre-Solicitation/Solicitation | DOC | |||
| 41 | Acquisitions | Award Line Item Designation Types | The system shall provide the capability to allow the following designations for a line in the Acquisition system such as: Subject to Availability of Funds (SAF), Option Year (OLI) and Government Furnished Property (GFP). | Acquisitions | Award Management | DOC | |||
| 42 | Acquisitions | Award Consolidation | The system must allow multiple requisitions to be combined during the award process but not lose the source document identification (for document chaining) | Acquisitions | Award Management | DOC | |||
| 43 | Acquisitions | Award Line Items | The system shall allow the Acquisition Office flexibility in structuring line items (consolidating, splitting, rearranging, reallocating, etc.) and maintain the ability to track the funding source back to the original line item. Keep the source document identification (for document chaining). | Acquisitions | Pre-Solicitation/Solicitation | DOC | |||
| 44 | Acquisitions | Award Funding Sent Real Time to Financial System | The system shall provide the capability to ensure that required financial data from awards is sent to the financial system in real time (e.g. Initial award shall be fully integrated with the financial system). | Acquisitions | Award Management | DOC | |||
| 45 | Acquisitions | Award Amounts Not Greater than PR | The system shall provide the capability for the Acquisition system not to allow award amount to exceed the amounts on the associated Purchase Request (PR) unless provided by DoC policy on tolerance levels. | Acquisitions | Award Management | DOC | |||
| 46 | Acquisitions | Award FBO Format | The system must have the ability to export to Government wide point of entry. | Acquisitions | Award Management | DOC | |||
| 47 | Acquisitions | Award - Confirm Integration | The system shall provide the capability for the Acquisition system to allow a way for a user to ascertain that the integrated obligation transaction was successful (approval message) or that there was an error in processing (error messages and/or access to error logs, etc.). | Acquisitions | Award Management | DOC | |||
| 48 | Acquisitions | Award - Acquisition Data Entry Validation | The system shall provide the capability to ensure that data validations for both acquisition and financial data occur at the earliest possible point of entry. | Acquisitions | Award Management | DOC | |||
| 49 | Acquisitions | Acquisition System - System of Record | The system shall provide the capability for the Acquisition system to be the system of record for Acquisition documents. Creation or modification of such documents must not be allowed directly in the financial system outside of addressing rare data corruption issues. Such data corrections, if absolutely necessary, must be performed by personnel with specified authority to carry out the needed actions in the financial system. | Acquisitions | Award Management | DOC | |||
| 50 | Acquisitions | Award Printing | The system shall provide the capability to preview the printed copy of an award document and allow for formatting of the structure (not content) and to have the ability to save all changes for future use. | Acquisitions | Award Management | DOC | |||
| 51 | Acquisitions | Award Modifications | The system shall provide the capability for the Acquisition system to allow modifications to be created in any order, however, enforce obligation to occur sequentially. | Acquisitions | Award Management | DOC | |||
| 52 | Acquisitions | CO/OO Awards | The system shall provide the capability for a Contracting Officer or Ordering Officer to make an award only within their threshold. | Acquisitions | Award Management | DOC | |||
| 53 | Acquisitions | Correct Award without Re-Routing | The system shall provide the capability for the Final Approver of a particular award document to be able to reopen the document, correct the issue (if pertinent information is available to him/her) and reapprove without having to go through a route process. | Acquisitions | Award Management | DOC | |||
| 54 | Acquisitions | Acquisition/Financial System Data Reconciliation | The system shall provide the capability for the Acquisition and Financial personnel to be provided with a mechanism to reconcile data and validate the data integrity between the two systems. | Acquisitions | Award Management | DOC | |||
| 55 | Acquisitions | Award Min/Max | The system shall provide the capability (if needed) to enforce Min/Max limits defined on the contract or BPA setup document | Acquisitions | Award Management | DOC | |||
| 56 | Acquisitions | Award Payment | The system shall allow an award to be created that will be paid via purchase card. | Acquisitions | Award Management | DOC | |||
| 57 | Acquisitions | Award Vendor Information - SAM/CCR | The system shall provide the capability to capture vendor information for all awards from SAM/Entity Management. | Acquisitions | Award Management | DOC | |||
| 58 | Acquisitions | Award Vendor Information - Not SAM/CCR | The system shall provide the capability to capture vendor information for all awards from vendors not required to be in SAM/Entity Management. | Acquisitions | Award Management | DOC | |||
| 59 | Acquisitions | Award - Vendor Search | The system shall provide the capability to search Acquisition vendors at a minimum by DUNS or NAME or SAMMI | Acquisitions | Award Management | DOC | |||
| 60 | Acquisitions | Vendor Data SAMS Validation | The system shall provide the capability to validate vendor data against the SAM/Entity Management database and the applicable Do Not Pay lists | Acquisitions | Award Management | DOC | |||
| 61 | Acquisitions | Award COTR/COR | The system shall capture the designated COTR/COR(s) and their authority levels. | Acquisitions | Award Management | DOC | |||
| 62 | Acquisitions | Award Payment Ceiling | The system shall capture contract payment ceilings at the contract and/or contract line item levels, as appropriate. | Acquisitions | Award Management | DOC | |||
| 63 | Acquisitions | Award FPDS-NG | The system shall export contract action information to FPDS-NG/Contract Data | Acquisitions | Award Management | DOC | |||
| 64 | Acquisitions | Generate Conformed Contract | The system shall have the ability to generate a conformed copy of the contract that incorporates any and all changes to the terms and conditions into a single document. | Acquisitions | Award Management | DOC | |||
| 65 | Acquisitions | Award Line Item Designations | The system shall capture contract line/sub-line items that are not separately priced. | Acquisitions | Award Management | DOC | |||
| 66 | Acquisitions | Award Clauses | The system shall generate final award terms and conditions, including customized clause text and fill-ins in award format (contract, task/delivery order, etc.) | Acquisitions | Award Management | DOC | |||
| 67 | Acquisitions | Generate Award Documents | The system shall assemble and generate the proposed final award documents for signature and route to the approving official. | Acquisitions | Award Management | DOC | |||
| 68 | Acquisitions | Award Multiple Offers | The system shall associate multiple offers with a solicitation and all resulting awards. | Acquisitions | Award Management | DOC | |||
| 69 | Acquisitions | Award Line Item Management | The system shall capture contract line item information to include list of documents, exhibits, fill-ins and other attachments at the line item level. | Acquisitions | Award Management | DOC | |||
| 70 | Acquisitions | Award Clause Management | The system shall notify users when updates to clauses have occurred. | Acquisitions | Award Management | DOC | |||
| 71 | Acquisitions | Award Obligation Data | The system shall export contract action obligation data to the financial system. | Acquisitions | Award Management | DOC | |||
| 72 | Acquisitions | Award Bilateral Contract | The system must route bilateral contract actions to the contractor for signature. | Acquisitions | Award Management | DOC | |||
| 73 | Acquisitions | Award Prevent Award Before Milestones are Met | The system must present a warning until all prescribed notifications/milestones are identified as complete, based on agency configured business rules. | Acquisitions | Award Management | DOC | |||
| 74 | Acquisitions | Assign/Reassign Buyer | The system shall provide the capability for the Acquisition System to assign and reassign the buyer after the document is released. | Acquisitions | Award Management | DOC | |||
| 75 | Acquisitions | Award Export to Property System | The system shall capture and export to the fixed asset system, the following information related to GFP disposed of at a minimum: Contract Number, Serial Number, Method of Disposition and Date of Disposition | Acquisitions | Award Management | DOC | |||
| 76 | Acquisitions | Award Period of Performance | The system must provide Period of Performance to the financial system | Acquisitions | Award Management | DOC | |||
| 77 | Acquisitions | Award Place of Performance | The system must provide Place of Performance information to the financial system | Acquisitions | Award Management | DOC | |||
| 78 | Acquisitions | Award Small Business | The system must provide award specific business size information to the financial system | Acquisitions | Award Management | DOC | |||
| 79 | Acquisitions | Award Open requisitions | The system must provide an option to close requisitions that are closed in the Financial System during the fiscal year close-out process | Acquisitions | Award Management | DOC | |||
| 80 | Acquisitions | Award Year End Processing | The system must be capable of allowing acquisition actions to be processed until 11:59pm on 9/30. | Acquisitions | Award Management | DOC | |||
| 81 | Acquisitions | Post Award Management | The system must allow the Acquisition user to create all types of modifications allowed by the FAR. | Acquisitions | Post Award Management | DOC | |||
| 82 | Acquisitions | Post Award Document Routing | The system shall provide the capability to route documents to the pre-established routing lists. | Acquisitions | Post Award Management | DOC | |||
| 83 | Acquisitions | Novations/Name Changes | The system shall allow for Novations/Name Changes | Acquisitions | Post Award Management | DOC | |||
| 84 | Acquisitions | Post Award Attachments | The system shall provide the capability to support attachments with various file extensions (related to "Whitelist" functionality.) | Acquisitions | Post Award Management | DOC | |||
| 85 | Acquisitions | Post Award Line Items | The system shall allow the Acquisition Office to consolidate and reallocate line items and track the funding source back to the original line item. | Acquisitions | Post Award Management | DOC | |||
| 86 | Acquisitions | Post Award Consolidation | The system must allow multiple requisitions to be combined during the modification process | Acquisitions | Post Award Management | DOC | |||
| 87 | Acquisitions | Post Award Modifications Integrated to Financial System | The system shall provide the capability for the Acquisition system to fully integrate modifications to the lines previously designated as SAF, OLI, or GFP to the financial system (as long as it effects budget, i.e., it is intended to create a commitment/award). | Acquisitions | Post Award Management | DOC | |||
| 88 | Acquisitions | Award Funding Modifications Sent Real Time to Financial System | The system shall provide the capability to ensure that required financial data from modifications is sent to the financial system in real time (e.g. Modifications shall be fully integrated with the financial system). | Acquisitions | Post Award Management | DOC | |||
| 89 | Acquisitions | Post Award - Validate Integration | The system shall provide the capability for the Acquisition system to allow a way for a user to ascertain that the integrated commitment transaction was successful (approval message) or that there was an error in processing (error messages and/or access to error logs, etc.). | Acquisitions | Post Award Management | DOC | |||
| 90 | Acquisitions | Post Award Administrative Modifications | The system shall provide the capability for the Acquisition system to allow administrative (non-financial) modifications to the document without requiring a PR. | Acquisitions | Post Award Management | DOC | |||
| 91 | Acquisitions | Post Award Issuing Office change | The system shall allow a change to the issuing office | Acquisitions | Post Award Management | DOC | |||
| 92 | Acquisitions | Post Award - Independent Validation | The system shall provide the capability for the Acquisition system to ensure internal Acquisition data-entry validation independent of the validations specific to the financial system/integration. | Acquisitions | Post Award Management | DOC | |||
| 93 | Acquisitions | Post Award - Acquisition System as System of Record | Creation/Modification of data must not be allowed directly in the financial system outside of addressing rare data corruption issues. Such data corrections, if absolutely necessary, must be performed by personnel with specified authority to carry out the needed actions in the financial system | Acquisitions | Post Award Management | DOC | |||
| 94 | Acquisitions | Award TAS Disbursement | The system must provide linkage to the financial system such that once the TAS disbursement period has completed, that all open acquisition documents with that TAS funding have an automatically generated draft modification for deobligation waiting for CO approval. The financial system and acquisition system must be in sync. | Acquisitions | Award Management | DOC | |||
| 95 | Acquisitions | Incremental Funding | The system shall provide the capability for the Acquisition system to add incremental funding | Acquisitions | Post Award Management | DOC | |||
| 96 | Acquisitions | Post Award - Vendor Search | The system shall provide the capability to search Acquisition vendors at a minimum by DUNS or NAME or SAMMI | Acquisitions | Post Award Management | DOC | |||
| 97 | Acquisitions | Obligation Data to Financial System | The system shall provide contract action obligation data to the financial system. | Acquisitions | Post Award Management | DOC | |||
| 98 | Acquisitions | Post Award Line Item Designations | The system shall capture contract line/sub-line items that are not separately priced. | Acquisitions | Post Award Management | DOC | |||
| 99 | Acquisitions | Contract Action Modifications | The system must allow for contract action modifications - specifically, the system must allow for the modification of data elements, clauses and related documents. | Acquisitions | Post Award Management | DOC | |||
| 100 | Acquisitions | Post Award Exercise Contract Actions | The system must allow for contract modifications to exercise contract options, including those that are not funded and those that do not require funding, such as indefinite delivery contracts. | Acquisitions | Post Award Management | DOC | |||
| 101 | Acquisitions | Post Award Update Period of Performance | The system must allow for contract modifications to update the period of performance end date on contract upon exercising contract option or modifying the schedule. This period of performance must be included in data sent to the financial system. | Acquisitions | Post Award Management | DOC | |||
| 102 | Acquisitions | Post Award Obligation Data Related to Modifications | The system must export obligation data to the financial system upon modifying the dollar amount of the contract or upon exercising a contract option. | Acquisitions | Post Award Management | DOC | |||
| 103 | Acquisitions | Post Award Check for Available Funds | The system must check for available funds. | Acquisitions | Post Award Management | DOC | |||
| 104 | Acquisitions | Post Award Update Value of Contract | The system must update the value of a contract (or delivery order, task order, etc.) upon processing dollar amount modifications to contracts or exercising options. | Acquisitions | Post Award Management | DOC | |||
| 105 | Acquisitions | Contract Modification Information Export | The system must export contract modification information to FPDS-NG/Contract Data. | Acquisitions | Post Award Management | DOC | |||
| 106 | Acquisitions | Contract Action Information Export | The system shall export contract action information to FPDS-NG/Contract Data. | Acquisitions | Post Award Management | DOC | |||
| 107 | Acquisitions | Closeout Management | The system must support automated closeout management functionality. | Acquisitions | Closeout Management | DOC | |||
| 108 | Acquisitions | Closeout Attachments | The system shall provide the capability to support attachments with various file extensions (related to "Whitelist" functionality.) | Acquisitions | Closeout Management | DOC | |||
| 109 | Acquisitions | Closeout Due Dates | The system shall maintain assign due dates to contract closeout items. | Acquisitions | Closeout Management | DOC | |||
| 110 | Acquisitions | Post Award Receipt | The system shall provide the capability for the COTR/Task Manager to validate that services and/or supplies were received. - this process happens at the time of the invoice approval. | Acquisitions | Post Award Management | DOC | |||
| 111 | Acquisitions | Closeout UDO balance | The system will check the financial system for zero dollar undelivered order balance as part of eligibility process | Acquisitions | Closeout Management | DOC | |||
| 112 | Acquisitions | Closeout Reopen Awards | The system shall allow authorized users to reopen closed contracts, if necessary. | Acquisitions | Closeout Management | DOC | |||
| 113 | Acquisitions | REMOVED | REMOVED | Acquisitions | Closeout Management | DOC | |||
| 114 | Acquisitions | Archive Documents | The system must archive documents that have passed the contract retention period. | Acquisitions | Closeout Management | DOC | |||
| 115 | Acquisitions | Unarchive Documents | The system shall allow the agency to unarchive documents as needed. | Acquisitions | Closeout Management | DOC | |||
| 116 | Acquisitions | System Configuration | The system must have the capability to set system and user permissions based on agency requirements. | Acquisitions | System Configuration | DOC | |||
| 117 | Acquisitions | Documents | The system shall serve as a document repository for all contracts/orders and have the ability to electronically route documents. | Acquisitions | System Configuration | DOC | |||
| 118 | Acquisitions | Sequential Document Numbering | The system shall provide the capability to configure sequential document numbering system. | Acquisitions | System Configuration | DOC | |||
| 119 | Acquisitions | System Configuration - Workload | The system shall provide the capability for the Acquisition System to assign and reassign the buyer after the document is released. | Acquisitions | System Configuration | DOC | |||
| 120 | Acquisitions | Ordering Officer User Type | The system shall provide the capability to establish an Ordering Officer user type (e.g. Blanket Purchase Agreements (BPA)). | Acquisitions | System Configuration | DOC | |||
| 121 | Acquisitions | Vendor Table Shared with Financial System | The system must support a single shared vendor table with the financial system | Acquisitions | System Configuration | DOC | |||
| 122 | Acquisitions | Restrict Vendor File Access | The system shall provide the capability to restrict access to the vendor files to only designated users. | Acquisitions | System Configuration | DOC | |||
| 123 | Acquisitions | Mask SPII Data | The system shall provide the masking capability to ensure SPII data elements (i.e. TIN) are protected. | Acquisitions | System Configuration | DOC | |||
| 124 | Acquisitions | System Configuration - Vendor | The system shall provide the capability to enter a vendor entry within one business day. | Acquisitions | System Configuration | DOC | |||
| 125 | Acquisitions | System Configuration - Vendor | The system shall provide the capability to enter a vendor update within one business day. | Acquisitions | System Configuration | DOC | |||
| 126 | Acquisitions | System Configuration - Notifications | The system shall provide the capability to automatically send reminders/notifications for renewals, options, closeouts, etc., to users via defined user email and Acquisition System Inbox. | Acquisitions | System Configuration | DOC | |||
| 127 | Acquisitions | ORCA Database Access | The system shall provide the capability to automatically have access to the SAM-Entity Management database. | Acquisitions | System Configuration | DOC | |||
| 128 | Acquisitions | Website Access | The system shall provide the capability to access various websites from within Acquisition System. | Acquisitions | System Configuration | DOC | |||
| 129 | Acquisitions | System Configuration - Templates | The system shall provide the ability for the system/site administrator to create various templates to minimize user processing error (closeout template, milestone templates, clause templates, etc.) | Acquisitions | System Configuration | DOC | |||
| 130 | Acquisitions | System Configuration - PALT | The system shall provide the capability for Agency to define, track and report progress of a specific Acquisition action through the Acquisition System Milestone Plan module. PALTs are defined by Agency. | Acquisitions | System Configuration | DOC | |||
| 131 | Acquisitions | Multiple Tiers of Users | The system shall provide the capability for multiple tiers of users defined by the Acquisition system functions; such as Buyers, Contracting Officers, Requisitioners, Read Only Access, COTR/IAO. | Acquisitions | System Configuration | DOC | |||
| 132 | Acquisitions | User Access Restrictions | The system shall provide the capability to restrict access to selected features, forms, and fields within forms as regulated by the Systems/Site Administrator. | Acquisitions | System Configuration | DOC | |||
| 133 | Acquisitions | System Configuration - Data Repository | The system shall have the capability to provide a centralized electronic data repository with ability to store all documents related to a particular acquisition in one file location. | Acquisitions | System Configuration | DOC | |||
| 134 | Acquisitions | System Configuration - Audit Trail | The system shall provide the capability to capture electronic audit trails from PR initiation through closeout; | Acquisitions | System Configuration | DOC | |||
| 135 | Acquisitions | System Configuration - Digital Signature | The system shall provide the capability to support digital and electronic signatures | Acquisitions | System Configuration | DOC | |||
| 136 | Acquisitions | FAR-based Clauses | The system shall provide the capability to be FAR-based; FAR clauses must be updated when the FAR or CAR is updated within 24 hours. | Acquisitions | System Configuration | DOC | |||
| 137 | Acquisitions | Agency Specific Statements and Clauses | The system shall provide the capability to process, retrieve and load non-FAR (agency specific) statements and clauses into Acquisition document. | Acquisitions | System Configuration | DOC | |||
| 138 | Acquisitions | Agency Specific Document Library | The system shall provide the capability to maintain an agency specific document Library | Acquisitions | System Configuration | DOC | |||
| 139 | Acquisitions | System Configuration - Connectivity | The system shall provide the capability for Agency to get thru the firewall to the Acquisition System | Acquisitions | System Configuration | DOC | |||
| 140 | Acquisitions | System Configuration - Printing | The system shall provide the capability to print on demand to standard commercial printers in standard print formats | Acquisitions | System Configuration | DOC | |||
| 141 | Acquisitions | System Configuration - User Manuals | The system shall provide the capability to provide on-line help plus electronic downloadable user manuals. | Acquisitions | System Configuration | DOC | |||
| 142 | Acquisitions | Help Desk Staffing | The system shall provide the capability to ensure Acquisition Help Desk Support during Agency business hours, including Regional Offices. This includes extended hours during the 4th quarter of the fiscal year | Acquisitions | System Configuration | DOC | |||
| 143 | Acquisitions | Help Desk Notifications | The system shall provide the capability to notify the requestor on any help desk action that the request is processed and provide a status. | Acquisitions | System Configuration | DOC | |||
| 144 | Acquisitions | System Configuration - Instances | The system shall provide the capability to have a Acquisition System "sandbox" instance for new user training and/or users to be able to "test-drive" new Acquisition System instances after upgrades. | Acquisitions | System Configuration | DOC | |||
| 145 | Acquisitions | System Configuration - Users | The system shall provide the capability to enter a new user entry within one business day. | Acquisitions | System Configuration | DOC | |||
| 146 | Acquisitions | System Configuration - Document Conversion | The system shall support the conversion of acquisition documents from the DOC legacy Acquisition system to the new system using an automated mechanism | Acquisitions | System Configuration | DOC | |||
| 147 | Acquisitions | System Configuration - Users | The system shall provide the capability to enter user entry update within one business day. | Acquisitions | System Configuration | DOC | |||
| 148 | Acquisitions | System Configuration - Bidirectional integration | Allow information from financial system (such as payments, credit memos, etc.) to be shown in Acquisition system for staff to view | Acquisitions | System Configuration | DOC | |||
| 149 | Acquisitions | System Configuration - Cross Servicing | A CO must have the ability to provide cross servicing actions. Must be able to see into the cross-serviced bureau's data as required. | Acquisitions | System Configuration | DOC | |||
| 150 | Acquisitions | System Configuration - Recurring obligations | System must provide a capability to create and process obligations that recur periodically. | Acquisitions | System Configuration | DOC | |||
| 151 | Acquisitions | System Configuration - Copy functionality | System must provide basic copy functionality for actions | Acquisitions | System Configuration | DOC | |||
| 152 | Acquisitions | System Configuration - Basic Reports | System must provide basic reports such as workload management, metrics, etc. | Acquisitions | System Configuration | DOC | |||
| 153 | Acquisitions | System Configuration - IAA | System must be able to process and track Interagency Assisted Agreements | Acquisitions | System Configuration | DOC | |||
| 154 | Acquisitions | Award Line Items | The system must allow the Acquisition Office to take a line item and split it into multiple line (staying within agency set tolerance) and retaining the document chaining from the original line item. | Acquisitions | Award Management | DOC | |||
| 155 | Acquisitions | System Configuration - Track CO warrant dates | The system needs to provide the ability to track warrant expiration dates for CO. The system will enforce denial of access to the system if the warrant has lapsed. | Acquisitions | System Configuration | DOC | |||
| 156 | Acquisitions | Prevent Awards - Expired SAM Vendors | The system shall prevent awards to vendors whose SAM registration has expired or capture FAR exception clause. | Acquisitions | Award Management | DOC | |||
| 157 | Acquisitions | Prevent Awards - Do No Pay Lists | The system shall prevent awards to vendors who are excluded parties or on Do Not Pay lists. | Acquisitions | Award Management | DOC | |||
| 158 | Acquisitions | Award Electronic Notification | The system must distribute contracts/orders to vendors electronically. | Acquisitions | Award Management | DOC | |||
| 159 | Acquisitions | Award Indicate Complete | The system must identify a contract award action as complete and flag it ready for distribution. | Acquisitions | Award Management | DOC | |||
| 160 | Acquisitions | Award Protest Status | The system must capture data on the status of protests. | Acquisitions | Award Management | DOC | |||
| 161 | Acquisitions | COTR/COR Expiration Dates | The system shall capture COR expiration dates and not allow assignment if expired. | Acquisitions | Award Management | DOC | |||
| 162 | Acquisitions | Post Award - Acquisition/Financial System Reconciliation | The system shall provide the capability for the Acquisition and Financial personnel to be provided with a mechanism to reconcile data and validate the data integrity between the two systems. | Acquisitions | Post Award Management | DOC | |||
| 163 | Acquisitions | Post Award Reversal of Receipt | The system shall provide the option to have receiving tickets that have been entered in Acquisitions system and have been interfaced to the financial system may be reversed in the financial system. This information must be provided to the acquisition system (integration is bi-directional). | Acquisitions | Post Award Management | DOC | |||
| 164 | Acquisitions | Post Award E-Invoicing | The system must provide a linkage of the E-Invoicing solution with both the financial and acquisition system. | Acquisitions | Post Award Management | DOC | |||
| 165 | Acquisitions | Closeout Management | The system shall provide the capability to route documents to the pre-established routing lists. | Acquisitions | Closeout Management | DOC | |||
| 166 | Acquisitions | Closeout Eligibility | The system shall provide the option to notify users and identify contract(s) eligible for closeout based on the period of performance end date, delivery or payment status. | Acquisitions | Closeout Management | DOC | |||
| 167 | Acquisitions | Closeout Retention Period | The system shall assign a retention period based on FAR requirements to all documents in a contract file eligible for closeout. | Acquisitions | Closeout Management | DOC | |||
| 168 | Acquisitions | Closeout Retention Period Modifications | The system shall allow for the modification of retention periods on documents in the contract file. | Acquisitions | Closeout Management | DOC | |||
| 169 | Acquisitions | Closeout Checklist | The system must maintain an agency-defined contract closeout checklist. | Acquisitions | Closeout Management | DOC | |||
| 170 | Acquisitions | Closeout Assignments | The system must assign user responsibility to contract closeout items. | Acquisitions | Closeout Management | DOC | |||
| 171 | Acquisitions | Closeout Assignment Notifications | The system must notify responsible parties of assignment of closeout items and due dates. | Acquisitions | Closeout Management | DOC | |||
| 172 | Acquisitions | Closeout Status | The system must capture status of contract closeout items. | Acquisitions | Closeout Management | DOC | |||
| 173 | Acquisitions | Late Completion of Closeout | The system must generate follow-up notices to assignees when contract closeout items are not completed on time. | Acquisitions | Closeout Management | DOC | |||
| 174 | Acquisitions | Closeout Retention/Withholding Amount Period Passed | The system must identify contract documents that have passed the contract retention/withholding amount period. | Acquisitions | Closeout Management | DOC | |||
| 175 | Acquisitions | Closeout Store Summary Data on Contracts | The system must store summary data from closed contract files as defined by agency business rules. | Acquisitions | Closeout Management | DOC | |||
| 176 | Acquisitions | Contract dollar amount/length | The system shall allow for 100 billion dollar value with 25 year length and over 1000 amendments | Acquisitions | Award Management | DOC | |||
| 177 | Acquisitions | FPDS Non-Reporting | The System shall allow for selective FPDS reporting on a contract by contract basis for both the procurement writing system and the finance system | Acquisitions | Award Management | DOC | |||
| 178 | Acquisitions | Reporting Requirements | The system shall be capable of producing reports that mimic FPDS reporting without actually reporting to FPDS | Acquisitions | Award Management | DOC | |||
| 179 | Acquisitions | Link PR Solicitation and Award together | The system shall link the Requisition, Purchase Request, Solicitation and Award Line Items to keep the source document identification (for document chaining). | Acquisitions | Award Management | DOC | |||
| 180 | Acquisitions | NOAA | The system shall check data integrity and funds availability prior to recording the obligation. | ||||||
| The system shall check data integrity prior to finalizing data within SAM/FPDS | Acquisitions | Award Management | DOC | ||||||
| 181 | Acquisitions | NOAA | The system shall provide the capability to search vendor records for a specific product, supply or service, NAICS and FSC. | Acquisitions | Award Management | DOC | |||
| 182 | Acquisitions | ES-A | The system shall provide the capability to link all awards to transactions within the financial system whether or not awards were entered through the acquisition system (non-interfaced awards). | Acquisitions | Award Management | DOC | |||
| 183 | Acquisitions | ES-A | The system shall allow multiple bureau funding on a single award. | Acquisitions | Award Management | DOC | |||
| 184 | Acquisitions | FirstNet | The system shall be able to upload document (regardless of type and size) into the Clause Section of the contract without impacting system performance when printing. | Acquisitions | Requisition Management, Pre-Solicitation and Award Management | DOC | |||
| 185 | Acquisitions | COTR/COR Appointment Letter | The system shall generate a COTR/COR appointment letter and provide notification to the designated COTR/COR. | Acquisitions | Award Management | DOC | |||
| 186 | Acquisitions | COTR/COR Expiration Dates | The system shall capture COTR/COR expiration dates and enforce denial of access for those who have expired certifications | Acquisitions | Award Management | DOC | |||
| 187 | Acquisitions | Award Congressional Notification | The system shall provide the capability (if desired) to generate a notification documents for Congress 30 days prior to the award of a multi-year contract greater than FAR-specific (FAR 17.108) or agency-assigned threshold. | Acquisitions | Award Management | DOC | |||
| 188 | Acquisitions | Award TO/DO | The system shall generate task orders and delivery orders incorporating clauses, terms and conditions in the contract. | Acquisitions | Award Management | DOC | |||
| 189 | Acquisitions | Prevent Awards - Expired CCR Vendors | The system shall warn of awards to vendors whose SAM/Entity Management registration has expired or capture FAR exception clause. | Acquisitions | Award Management | DOC | |||
| 190 | Acquisitions | Award Notify Unsuccessful Offerors | The system shall provide the option to notify all unsuccessful offerors that the offer has not been accepted. | Acquisitions | Award Management | DOC | |||
| 191 | Acquisitions | Award Notify Selected Awardee | The system shall provide the option to notify the selected awardee that offer has been accepted. | Acquisitions | Award Management | DOC | |||
| 192 | Acquisitions | Award Distribute Final Award Document (Duplicate of 129, 97?) | The system shall provide the option to distribute the final award document and associated notifications to the user-defined distribution list based on notification rules. | Acquisitions | Award Management | DOC | |||
| 193 | Acquisitions | Award Electronic Notification | The system must distribute contracts/orders to vendors electronically. | Acquisitions | Award Management | DOC | |||
| 194 | Acquisitions | Prevent Awards - Do Not Pay List | The system shall prevent awards to vendors who are excluded parties or on Dot Not Pay list. | Acquisitions | Award Management | DOC | |||
| 195 | Acquisitions | Award Protest Document | The system must consolidate protest documentation into a protest case file. | Acquisitions | Award Management | DOC | |||
| 196 | Acquisitions | Award Multiple Funds Cites | The system must generate specific instructions to the payment office for dealing with contracts/orders which have multiple funds citations. | Acquisitions | Award Management | DOC | |||
| 197 | Acquisitions | Post Award Receipt | The system shall provide the capability for the COTR/Task Manager to validate that services and/or supplies were received. | Acquisitions | Post Award Management | DOC | |||
| 198 | Acquisitions | Administrative Modifications | The system shall provide the capability for the Acquisition system to allow administrative modifications to the document that moves the same funding from one contract line to a different contract line using the same accounting codes without the need for a PR. | Acquisitions | Post Award Management | DOC | |||
| 199 | Acquisitions | Post Award Contract holdbacks | Include Contract Holdbacks and/or withholdings in obligation data export to the financial system | Acquisitions | Post Award Management | DOC | |||
| 200 | Acquisitions | Post Award Document Distribution (Duplicate 80, 97?) | The system shall distribute the final award document and associated notifications to the user-defined distribution list based on notification rules. | Acquisitions | Post Award Management | DOC | |||
| 201 | Acquisitions | Closeout Management | The system support automated closeout management functionality. | Acquisitions | Closeout Management | DOC | |||
| 202 | Acquisitions | Closeout Generate Checklist | The system must generate a checklist of contract-specific closeout items including due dates and responsible parties. | Acquisitions | Closeout Management | DOC | |||
| 203 | Acquisitions | Closeout Checklist Signatures | The system must capture checklist signatures. | Acquisitions | Closeout Management | DOC | |||
| 204 | Acquisitions | Closeout Status of Closeouts | The system must notify the contracting officer of status of closeout items upon expiration of period of performance. | Acquisitions | Closeout Management | DOC | |||
| 205 | Acquisitions | Closeout Release of Retention/Withholding Amounts | The system must export notice of release of retention/withholding amounts to the Financial System. | Acquisitions | Closeout Management | DOC | |||
| 206 | Core Finance | Spending plans | Capture spending plans for any funded organization level or other accounting classification. | Core Financials | Budgetary Resource Management | OFFM - FMA-02 | |||
| 207 | Core Finance | Plan periods | Capture financial operating and spending plans by month, quarter, year and continuing resolution periods. | Core Financials | Budgetary Resource Management | OFFM - FMA-03 | |||
| 208 | Core Finance | Plan measurements | Generate plan results based on multiple measures including fixed dollar amounts, unit costs, cost allocations, labor hours, full-time equivalents (FTEs) or positions/appointments. | Core Financials | Budgetary Resource Management | OFFM - FMA-05 | |||
| 209 | Core Finance | Plan versions | Maintain current and multiple historical versions of plans. | Core Financials | Budgetary Resource Management | OFFM - FMA-06 | |||
| 210 | Core Finance | Compare plans | Compare multiple versions of plans. | Core Financials | Budgetary Resource Management | OFFM - FMA-07 | |||
| 211 | Core Finance | Future plans | Maintain financial operating and spending plans for future periods (i.e., future fiscal years, future reporting periods in current fiscal year). | Core Financials | Budgetary Resource Management | OFFM - FMA-08 | |||
| 212 | Core Finance | Merging Plans | Ability to merge existing plan to new one (i.e. continuing resolution to full year plan) | Core Financials | Budgetary Resource Management | DOC | |||
| 213 | Core Finance | Plan activation | Activate future period plans based on a specified plan start date or on-demand. | Core Financials | Budgetary Resource Management | OFFM - FMA-09 | |||
| 214 | Core Finance | Planned to actual | Compare planned spending to actual spending. | Core Financials | Budgetary Resource Management | OFFM - FMA-10 | |||
| 215 | Core Finance | Budget information | Classify budget projections using accounting classification elements (e.g., Apportionment categories, Authority type, Program-Project-Activity, etc.). | Core Financials | Budgetary Resource Management | OFFM - FMB-01 | |||
| 216 | Core Finance | Import budget formulation data | Import budget formulation data (e.g., Presidential/OMB pass backs, congressional markup documents, and internal agency decisions). | Core Financials | Budgetary Resource Management | OFFM - FMB-02 | |||
| 217 | Core Finance | Create plan from imported budget formulation data | Create plan from imported budget formulation data. | Core Financials | Budgetary Resource Management | DOC | |||
| 218 | Core Finance | Calculate prior year budget data | Calculate prior year budgets, actual spending amounts and variances at multiple levels including as low as object class or project level. | Core Financials | Budgetary Resource Management | OFFM - FMB-03 | |||
| 219 | Core Finance | Export prior year budget data | Export prior year budgets, actual spending and variances at the line item level in an excel, ASCII text delimited, or XML file format. | Core Financials | Budgetary Resource Management | OFFM - FMB-04 | |||
| 220 | Core Finance | Projected activity | Generate projected future period obligations, income, and expenditures at any level of the organizational structure based on prior year actual activity using agency-defined projection rates. | Core Financials | Budgetary Resource Management | OFFM - FMB-05 | |||
| 221 | Core Finance | Define projection rates | Define projection rates (e.g., 90%, 100%, 110%) by budget object class for use in budget formulation and execution. | Core Financials | Budgetary Resource Management | OFFM - FMB-06 | |||
| 222 | Core Finance | Apply projection rates | Calculate budget amounts for all, selected groups, or individual budget line items based on agency-defined projection rates. | Core Financials | Budgetary Resource Management | OFFM - FMB-07 | |||
| 223 | Core Finance | What if analysis | Generate multiple budgets based on alternative agency-specified accounting structures, funding levels, and spending criteria. | Core Financials | Budgetary Resource Management | OFFM - FMB-08 | |||
| 224 | Core Finance | Reporting indicator | Provide a mechanism to identify specific reporting projects (i.e. NSF, SBIR, or ARRA) across accounting classification elements | Core Financials | Budgetary Resource Management | DOC | |||
| 225 | Core Finance | Payroll forecasts | Generate payroll forecasts (i.e., anticipated compensation and benefits) at the object class and individual employee level. | Core Financials | Budgetary Resource Management | OFFM - FMB-09 | |||
| 226 | Core Finance | Modified payroll forecasts | Generate modified payroll forecasts. | Core Financials | Budgetary Resource Management | OFFM - FMB-10 | |||
| 227 | Core Finance | Projected overhead | Generate overhead projections using agency defined overhead rates. | Core Financials | Budgetary Resource Management | OFFM - FMB-11 | |||
| 228 | Core Finance | Import budget information | Import budget formulation data submitted in Excel, ASCII text delimited, or XML format. | Core Financials | Budgetary Resource Management | OFFM - FMB-12 |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .