RRB12R004 FMIS Attachment 1 Requirements
330 KB Posted
- Attached to
- Financial Management Integrated System (FMIS) Federal contract opportunity
- Solicitation number
- RRB12R004
- Issued by
- Railroad Retirement Board
About this file
RRB12R004 Attachment 1 FMIS Requirements document
Text of this file
Instructions
| RRB System Requirements: Instructions |
| Please complete the RRB System Requirements using the instructions below. Submit the completed requirement responses in the same format in which you received them. Do not add or delete columns or requirements. |
It is assumed that the service provider complies with all Financial Systems Integration Office (FSIO) mandatory requirements. The requirements matrices are therefore an extract of FSIO value added requirements that RRB prioritized as mandatory, modified FSIO mandatory requirements, and RRB specific requirements. RRB specific additions in FSIO requirements are bolded.
| The following legend describes the types of requirements in the matrices. Offerors shall not complete requirements for optional services they do not intend to provide. | ||
| Requirement Type | Description | Mandatory or Optional |
| CM | Cost Management | Mandatory |
| DC | Debt Collection | Optional |
| FA | Fixed Assets | Optional |
| FB | Fund Balance with Treasury | Mandatory |
| FM | Funds Management incl Budget Formulation | Mandatory |
| GL | General Ledger | Mandatory |
| IN | Inventory | Optional |
| PM | Payment Management | Mandatory |
| PO | Purchasing | Mandatory |
| RB | Reimbursable Management | Mandatory |
| RM | Receivable Management | Mandatory |
| RP | Reporting Management | Mandatory |
| SM | System Management | Mandatory |
| TL | Technical Capability | Mandatory |
| TR | Travel | Optional |
| TS | Security Control | Mandatory |
| XF | Cross Functional | Mandatory |
| The following table provides guidelines for columns that require vendor responses: | ||
| Column | Column Heading | Description |
| G | Vendor Response: Solution Meets Requirement (Y, P, or N) | Indicate whether or not the proposed solution meets (Y), partially meets (P) or does not meet (N) the requirement. |
RRB mandatory requirements indicate functionality the system must provide. RRB value added requirements indicate functionality the system should provide.
| H | Vendor Comments | Mandatory Requirements- If the proposed solution does not meet a mandatory requirement, the offeror must specify how the gaps will be addressed. If the proposed solution partially meets a mandatory requirement, the offeror shall specify what is and is not satisfied by the solution and the gap-closing activities for the unsatisfied portions. Keep in mind that costs applicable to gap-closing activities shall be included in the pricing section of the Business Proposal. Additionally, indicate if the requirement will be satisfied in a future version, which version and the projected release date. |
| Value Added Requirements- The RRB does not require gap-closing activities for value added requirements. If the solution partially meets or does not meet a value added requirement, and the requirement will not be satisfied in a future version, the offeror shall enter ‘N/A.’ If the requirement will be satisfied in a future version, indicate what version and the projected release date. Keep in mind that there shall be no gap-closing activity costs for value added requirements in the pricing section of the Business Proposal. | ||
| The following legend provides a description of the rest of the columns: | ||
| Column | Column Heading | Description |
| A | RRB ID Number | Provides a unique identifier for each requirement (ID numbers may not be in consecutive order as this is an extract of all requirements). |
| B | Requirement | Provides the wording of the requirement. |
| C | Source | Identifies the original source of the requirement and the source of modifications, if any. |
| D | Original Source ID Number | Provides the unique identifier of requirements obtained from other sources, such as FSIO core requirements. |
| E | Priority | Provides the RRB priority designation for requirements as mandatory or value added. RRB mandatory requirements indicate functionality the system must provide. RRB value added requirements indicate functionality the system should provide. |
&L&10U.S. Railroad Retirement Board FMIS Attachment 1&R&10&P of &N
CM
RRB ID Number Requirement Source Original Source ID Number Priority Vendor Response:
Solution Meets Requirement
| (Y, P, or N) | Vendor Comments | ||||
| RRB-CM-13 | The system must have automated functionality to accumulate non labor costs by organization and budget object code. | RRB | N/A | Mandatory | |
| RRB-CM-14 | The system must have functionality to capture U.S. SGL attributes on cost distribution entries needed to prepare the Statement of Net Cost at the program level. | RRB | N/A | Mandatory | |
| RRB-CM-15 | The system must provide automated functionality that provides non effort cost to the RRB cost accounting system. | RRB | N/A | Mandatory |
&L&10U.S. Railroad Retirement Board FMIS Attachment 1&R&10&P of &N
DC
RRB ID Number Requirement Source Original Source ID Number Priority Vendor Response:
Solution Meets Requirement
| (Y, P, or N) | Vendor Comments | ||||
| RRB-DC-01 | The system must provide the capability to establish and maintain non-Federal customer information to support receivable management and debt collection processes though batch and online manual input. | FSIO - 2009 Core Requirements with RRB Modifications | RMA-01 | Mandatory | |
| RRB-DC-02 | The system must provide automated functionality that maintains a history of changes made to customer and debt information to support internal control and receivable management processes. | FSIO - 2009 Core Requirements with RRB Modifications | RMA-04 | Mandatory | |
| RRB-DC-03 | The system must provide the capability to capture data on receivable documents to support billing and debt management processes including the following: |
• Baseline receivable date (used to age receivable and determine the delinquency date)
• Description of goods/services or other basis for debt
• Item type to be billed
• Agency defined receivable codes identifying source, type, cause, category, collection and referral status
• Dates of performance
• Customer Information
• Source system
• Source system document number
• Billing terms
RRB debt collection does not currently use the following:
• Treasury defined receivable type
• Reimbursable agreement number
| • Shipping information. | FSIO - 2009 Core Requirements with RRB Modifications | RMB-04 | Mandatory | ||
| RRB-DC-04 | The system must provide the capability to customize the text and data elements to be displayed on system-generated bills, by customer type, agency-defined receivable source type, Treasury-defined receivable type or billing method and to repeat the information in a tear away section of the bill. For example, a bill for a benefit overpayment would need to contain different supporting text than a bill to railroad for an overpayment under section 12(o) 2(f) of the Railroad Unemployment Insurance Act. | FSIO - 2009 Core Requirements with RRB Modifications | RMB-11 | Mandatory | |
| RRB-DC-05 | The system must provide the capability to reschedule existing receivables to be paid under installment plans of various frequencies. | FSIO - 2009 Core Requirements with RRB Modifications | RMB-21 | Mandatory | |
| RRB-DC-06 | The system must provide the capability to maintain Treasury-defined receivable types used for distinguishing between various receivables reported on the TROR. | FSIO - 2009 Core Requirements with RRB Modifications | RMB-29 | Mandatory | |
| RRB-DC-07 | The system must provide automated functionality that calculates and records the allowance for loss on uncollectible accounts receivable based on agency-defined criteria. The RRB’s current practice for calculating this allowance is to determine percentages of debt written-off on closed accounts by age and category and then to apply the derived percentages to open receivables of the same age and category. | FSIO - 2009 Core Requirements with RRB Modifications | RMC-17 | Mandatory | |
| RRB-DC-08 | The system must provide automated functionality that records a refund when collections for a particular collection credit exceeds the outstanding balance of the receivable. | FSIO - 2009 Core Requirements with RRB Modifications | RMD-10 | Mandatory | |
| RRB-DC-09 | The system must provide the capability to generate bills to non-reimbursable customers based on receivables recorded. Include the following information on the bills: |
• Customer name
• Customer address
• Customer contact name
• Agency contact name, office, address and telephone number
• Date due
| • Agency-defined debt Identification Number. | FSIO - 2006 Core Requirements with RRB Modifications | RMB-06 | Mandatory | ||
| RRB-DC-10 | The system should provide the capability to include advances and prior collections received on bills. | FSIO - 2006 Core Requirements | RMB-13 | Mandatory | |
| RRB-DC-11 | The system must provide the capability to distinguish receivables between administration and benefit accounts based on an agency assigned ratio or direct dollar input, while retaining the ability to identify the receivable as a whole. | RRB | RRB-RM-51 | Mandatory | |
| RRB-DC-12 | The system must provide the capability to distinguish collections between administration and benefit accounts based on an agency assigned ratio or direct dollar input, while retaining the ability to identify the collection as a whole. | RRB | RRB-RM-52 | Mandatory | |
| RRB-DC-13 | The system must provide the automated capability to identify an attempt to input duplicate debt records, and provide an immediate warning message to the user about the duplication. | RRB | N/A | Mandatory | |
| RRB-DC-14 | The system must provide the automated capability to establish and maintain debts based on high level debt types which identify the originating trust fund account. RRB debts originate from multiple trust fund debts which must be tracked separately; RRA, RUIA, SSA, Medicare, Commercial and Employee. | RRB | N/A | Mandatory | |
| RRB-DC-15 | The system must provide the automated capability to establish and maintain debts with multiple lines within each record; assessing interest, penalty and other charges on specified lines within the debt. | RRB | N/A | Mandatory | |
| RRB-DC-16 | The system must provide the automated functionality to store and maintain agency specific customer information and debt identifiers, and provide for online cross-reference to stored TIN's, SSN's and RRB claim numbers. | RRB | N/A | Mandatory | |
| RRB-DC-17 | The system must provide the automated capability to interface with legacy DB2 VSAM databases and applications. Specifically, the system must receive and update its database from a nightly RRB generated batch file of debts/accounts receivable, collections records and adjustments, and the system must provide a nightly file of open, uncollectible and written-off debts to RRBs legacy databases and applications. | RRB | N/A | Mandatory | |
| RRB-DC-18 | The system must provide the capability to establish and maintain agency-defined receivable codes which identify the source, type, cause, category, collection and referral status so such agency-defined codes can be captured in debt management, collection and performance reporting. | RRB | N/A | Mandatory | |
| RRB-DC-19 | The system must provide the automated functionality to reprint bills. | RRB | N/A | Mandatory | |
| RRB-DC-20 | The system must provide the automated capability to reopen closed or written-off debts based on reversal of cash or write-off transactions through manual or batch transactions. | RRB | N/A | Mandatory | |
| RRB-DC-21 | The system must provide the automated capability to receive and process collections in batch from RRB and external sources. | RRB | N/A | Mandatory | |
| RRB-DC-22 | The system must have the automated capability to categorize and track debts using agency defined tracking codes which indicate the age, collection and referral status of the debt. For example, debts referred to the Treasury's cross servicing program for enforced collection will need to be assigned to a different category or tracking code from debts being collected through Treasury's reclamation process. | RRB | N/A | Mandatory | |
| RRB-DC-23 | The system must have the automated capability to generate a file of delinquent debts meeting certain agency defined criteria for batch referral to Treasury's cross servicing program, RRB's Office of the Inspector or other external collection programs. | RRB | N/A | Mandatory | |
| RRB-DC-24 | The system must have the automated capability to allow agency management control over specified collection decisions and policy enforcement based on pre-defined criteria such as, debt amount, status, resolution request, etc. | RRB | N/A | Mandatory | |
| RRB-DC-25 | The system must have the automated capability and functionality to provide online summary and detail of daily deposits by deposit number, date and type. | RRB | N/A | Mandatory | |
| RRB-DC-26 | The system must have the automated capability and functionality to generate online reports based on agency defined codes (e.g., source, type, cause, category, collection and referral status). | RRB | N/A | Mandatory | |
| RRB-DC-27 | The system must have the automated capability for agency manual online input of customer service contact notes associated with individual open or closed debts. | RRB | N/A | Mandatory | |
| RRB-DC-28 | The system must have the automated capability to prioritize and assign debts to individual agency users based on agency defined criteria (e.g., source, type, cause, category, collection and referral status, aging, amount and collection status). | RRB | N/A | Mandatory | |
| RRB-DC-29 | The system must have the automated capability to change the collection due date on individual debts manually or automatically based on agency defined criteria. For example, RRB moves the collection due date when a customer requests due process rights, enters an installment plan or RRB manually re-bills. | RRB | N/A | Mandatory | |
| RRB-DC-30 | The system must have the capability to automatically monitor collections by user and debt type. | RRB | N/A | Mandatory | |
| RRB-DC-31 | The system must have the automated capability to allow a debt to be assigned to multiple collection paths simultaneously. A referral location code will define what collection stream the debt is assigned to. | RRB | N/A | Mandatory | |
| RRB-DC-32 | The system must provide for multi-user processing and built-in role based security to support multiple collection and recovery responsibilities within the agency. | RRB | N/A | Mandatory | |
| RRB-DC-33 | The system must have a complete running history and permanent audit trail of all collection, charges, adjustments, billing, assignments, etc. activity on individual debts. | RRB | N/A | Mandatory | |
| RRB-DC-34 | The system must provide the automated capability for agency defined account inventory (including online number, dollar amount of debts and collections for all collection streams) and performance reporting. | RRB | N/A | Mandatory | |
| RRB-DC-35 | The system must provide the automated functionality to input, online or via batch processing, and track the due process stage of an individual debt. Under RRA and RUIA debtors are afforded the right to review, reconsideration, waiver consideration and appeal of agency decisions. Collection efforts may not continue, in most cases, while due process decisions are pending. | RRB | N/A | Mandatory | |
| RRB-DC-36 | The system must have the automated capability to provide agency staff with on screen customer service scripts. The customer service screen shall have summarized customer and account data such as the status of a debt, collection stream, and due process. | RRB | N/A | Mandatory |
&L&10U.S. Railroad Retirement Board FMIS Attachment 1&R&10&P of &N
FA
RRB ID Number Requirement Source Original Source ID Number Priority Vendor Response:
Solution Meets Requirement
| (Y, P, or N) | Vendor Comments | ||||
| RRB-FA-07 | The system should have automated functionality to interface electronically with GSA’s Worldwide Inventory. | FSIO - Property Mgmt System Req - Acquiring / Receiving Property | N/A | Value-Added | |
| RRB-FA-08 | The system should have automated functionality to capture warranty/guarantee information, including terms and period of coverage. | FSIO - Property Mgmt System Req - Acquiring / Receiving Property | N/A | Value-Added | |
| RRB-FA-34 | The system must be able to capture the acquisition cost of individual items acquired through bulk purchase, when required by agency policy. | FSIO - Property Mgmt System Req - Managing and Accounting for Property - Changes in Asset Value | N/A | Mandatory | |
| RRB-FA-35 | The system must be able to capture the cost of capitalizable improvements separate from the original cost, the estimated change in asset’s life as a result of the improvement, and the date of improvement. | FSIO - Property Mgmt System Req - Managing and Accounting for Property - Changes in Asset Value | N/A | Mandatory | |
| RRB-FA-36 | The system must be able to separately calculate depreciation on capital improvements. | FSIO - Property Mgmt System Req - Managing and Accounting for Property - Depreciation of Capitalized Assets | N/A | Mandatory | |
| RRB-FA-38 | The system must have the ability to identify and track assets that will be capitalized or become accountable property from requisition to purchase order to receiving ticket to invoice and to recording the asset as capitalized or becomes accountable property. | RRB | N/A | Mandatory | |
| RRB-FA-39 | The system must have the ability to provide reports to perform an inventory of capitalized and/or accountable assets. | RRB | N/A | Mandatory |
&L&10U.S. Railroad Retirement Board FMIS Attachment 1&R&10&P of &N
FB
RRB ID Number Requirement Source Original Source ID Number Priority Vendor Response:
Solution Meets Requirement
| (Y, P, or N) | Vendor Comments | ||||
| RRB-FB-21 | The system should provide the automated capability to integrate with the RRB's Program Accounts Receivable (PAR) System for IPAC splits related to TRACS Reclamations (CROS's), Debt Management Services (DMS), and IPAC TRACS (OZ) for SF 224 purposes. | RRB | N/A | Mandatory | |
| RRB-FB-22 | The system should provide the capability to capture interfund transfers performed by Programs. | RRB | N/A | Value Added |
&L&10U.S. Railroad Retirement Board FMIS Attachment 1&R&10&P of &N
FM
RRB ID Number Requirement Source Original Source ID Number Priority Vendor Response:
Solution Meets Requirement
| (Y, P, or N) | Vendor Comments | ||||
| RRB-FM-31 | The system must provide automated functionality that monitors the availability of funds at each level of the accounting classification structure at which funds are controlled, and, when attempting to process a spending document that exceeds the budget authority available, provides a notification to the user that includes the accounting classification structure element values of the funds that were exceeded. The system must automatically prevent creation of a spending document that exceeds the budget authority available. | FSIO - 2009 Core Requirements with RRB modifications | FME-01 | Mandatory | |
| RRB-FM-39 | The system must provide the automated capability to monitor the use of funds against legal (statutory) and administrative (agency-imposed) limitations (e.g., object class limitations) and, the system must automatically prevent creation of a spending document that exceeds the allotment available. | FSIO - 2009 Core Requirements with RRB modifications | FME-14 | Mandatory | |
| RRB-FM-47 | The system must provide the automated capability to validate that the CCR/SAM vendor information to be stored on an obligating document (i.e., inherited from a referenced commitment) matches the vendor information in the vendor file, prior to posting the obligation. | FSIO - 2009 Core Requirements with RRB modifications | FME-23 | Mandatory | |
| RRB-FM-58 | The system must provide the capability to drill down to the item level. It must calculate prior year budgets, actual spending amounts and variances at the line item level. | FSIO - 2006 Core Requirements with RRB modifications | FMB-03 | Mandatory | |
| RRB-FM-60 | The system must provide the capability to export prior year budgets, actual spending and variances at the line item level in an excel or ASCII text delimited file format. | FSIO - 2006 Core Requirements | FMB-04 | Mandatory | |
| RRB-FM-61 | The system must provide the capability to generate budget information for multiple budget cycles (e.g. monthly, quarterly, semi-annual, and yearly). | FSIO - 2006 Core Requirements | FMB-15 | Mandatory | |
| RRB-FM-62 | The system must provide the capability to associate budget formulation line items to the agency’s stated goals and objectives required by GPRA. | FSIO - 2006 Core Requirements | FMB-16 | Mandatory | |
| RRB-FM-63 | The system must provide the capability to generate budget formulation information for all categories on which legally binding budgetary decisions are made (e.g., appropriation limitations). | FSIO - 2006 Core Requirements | FMB-17 | Mandatory | |
| RRB-FM-64 | The system must provide the capability to generate allotment and sub-allotment information with sufficient detail to support funds control. | FSIO - 2006 Core Requirements | FMD-09 | Mandatory | |
| RRB-FM-65 | The system must provide the capability to distribute system-generated allotment and sub-allotment information electronically to subordinate organizations. | FSIO - 2006 Core Requirements | FMD-10 | Mandatory | |
| RRB-FM-66 | The system must provide the capability to capture requests for reprogramming of funds or additional funds outside the formal budget process. | FSIO - 2006 Core Requirements | FMD-11 | Mandatory | |
| RRB-FM-67 | The system must provide the capability to capture submitted, reviewed and approved status information on re-programming requests. | FSIO - 2006 Core Requirements | FMD-12 | Mandatory | |
| RRB-FM-68 | The system must provide the capability to record allotment changes based upon approval of reprogramming requests. | FSIO - 2006 Core Requirements with RRB modifications | FMD-13 | Mandatory | |
| RRB-FM-69 | The system must provide the capability to notify the agency when funds availability by TAFS or internal fund code reaches a pre-defined percent of the original total funding amount. | FSIO - 2006 Core Requirements | FMF-10 | Mandatory | |
| RRB-FM-70 | The system must provide budget formulation capabilities that are integrated with the core financial system, so that final budgets can be posted to the GL and update funds control using an automated process. | RRB | N/A | Mandatory | |
| RRB-FM-71 | The system must provide budget formulation capabilities that allow Program/Office users to develop budgets and transmit to the Budget Office. | RRB | N/A | Mandatory | |
| RRB-FM-72 | The system must provide budget formulation capabilities that allow the Budget Office to review, update, and approve budget submissions received from Program/Office users. | RRB | N/A | Mandatory | |
| RRB-FM-73 | The system must provide budget formulation capabilities that allow the Budget Office to maintain multiple versions of the budget (current year & future year) with version history and ability to track changes and notate comments. | RRB | N/A | Mandatory | |
| RRB-FM-74 | The system must provide budget formulation capabilities that allow the Budget Office to consolidate budget submissions received from Program/Office users and view and report on the budget at summary levels. | RRB | N/A | Mandatory | |
| RRB-FM-75 | The system must provide the Budget Office with budget approval workflow (systemic, with ability to attach supporting documentation) for current year budget and for developing budget submissions for future years. | RRB | N/A | Mandatory | |
| RRB-FM-77 | The system must provide the capability to have separation of duties between budget users who create and budget users who approve documents and entries. The same budget user should have the ability to both create and approve documents, but should never be able to create and approve the same document. | RRB | N/A | Mandatory | |
| RRB-FM-80 | The system must have the capability to process reprogramming documents in real time or near real time. | RRB | N/A | Mandatory | |
| RRB-FM-81 | The system must provide automated functionality to log changes made at any organizational or accounting level in order to provide an audit trail. | RRB | N/A | Mandatory | |
| RRB-FM-83 | The system must provide automated functionality to alert the Budget Office when a budgeted level becomes negative (e.g., in the case of an accounting override for payment of interest). | RRB | N/A | Mandatory | |
| RRB-FM-84 | The system must provide automated functionality to prevent the creation of a spending document that exceeds an allotment or sub-allotment. The system must allow for agency specified exceptions within threshold limits (e.g., an accounting override for payment of interest). | RRB | N/A | Value Added | |
| RRB-FM-85 | The system must provide the ability for staff without invoice/voucher entry capabilities to obligate funds for fixed special accounts and infrequent low value services (e.g., building maintenance and rent, utilities, postage, communications, government-government InterAgency Agreements) | RRB | N/A | Mandatory | |
| RRB-FM-111 | The system should provide budget formulation capabilities that allow the Budget Office to create a file to be uploaded to the OMB MAX system. | RRB | N/A | Value Added | |
| RRB-FM-112 | The system should provide the capability to calculate continuing resolution amounts. | RRB | N/A | Value Added | |
| RRB-FM-113 | The system should have the capability for core system users to open a "ticket" should a budget related issue arise, and automatically route to a budget user for review. | RRB | N/A | Value Added | |
| RRB-FM-114 | The system should allow for standardization and automatic population of data into Congressional Justification documents. | RRB | N/A | Value Added |
&L&10U.S. Railroad Retirement Board FMIS Attachment 1&R&10&P of &N
GL
RRB ID Number Requirement Source Original Source ID Number Priority Vendor Response:
Solution Meets Requirement
| (Y, P, or N) | Vendor Comments | ||||
| RRB-GL-42 | The system must deliver a capability to make mass changes to tables rolled forward to a subsequent fiscal year. | FSIO - 2006 Core Requirements | GLF-12 | Mandatory | |
| RRB-GL-44 | The system must be able to have inbound interface with a HRLOB payroll provider, such as GSA. The interface shall exchange data such as employee data, fund, organization code, budget fiscal year, budget object class, hours worked, payroll amounts, and transit benefit amounts. | RRB | N/A | Mandatory | |
| RRB-GL-45 | The system must be able to have inbound and outbound interfaces with a travel vendor identified in the GSA E2 travel Master Contract (e.g., Carlson Wagonlit Travel). The interfaces shall exchange data such as travel orders and travel vouchers for employee travel. At minimum, the interface must be able to pass employee vendor number, order number, voucher number, travel line item detail (e.g., air, hotel, per diem, ground transportation), travel accounting line item detail (e.g., fund, budget fiscal year, organization, budget object class), and amounts. | RRB | N/A | Mandatory | |
| RRB-GL-46 | The system must provide the functionality to perform accounting transactions for change of station transactions with the Bureau of the Public Debt (Accept data from IPAC or FMS report 224). | RRB | N/A | Mandatory | |
| RRB-GL-49 | The system must be able to produce cash statements that provide Monthly & YTD collections and disbursements data by transaction type (e.g., receipts - payroll taxes, interest; disbursements - benefits paid, salaries and expenses) to be used by the agency's actuaries. | RRB | N/A | Mandatory | |
| RRB-GL-50 | The system must have functionality so that transactions posted in to the general ledger should have an audit trail to allow a user to identify the related detail transactions in the other systems. | RRB | N/A | Mandatory | |
| RRB-GL-51 | The system must have functionality to select which funds are included in the account balances. | RRB | N/A | Mandatory | |
| RRB-GL-52 | The system must provide the automated capability to review and correct accounting string elements (e.g., cost center and budget object code) before the transaction is submitted for processing. | RRB | N/A | Mandatory | |
| RRB-GL-53 | The system must provide automated financial reports, balance sheet, statement of net costs, statement of changes in net position and budgetary statements. | RRB | N/A | Mandatory | |
| RRB-GL-54 | The system must have the capability to accept program benefit payment data in a designated format to automatically post the required accounting entries to the system general ledger. | RRB | N/A | Mandatory | |
| RRB-GL-55 | The system must have the capability to accept Program Accounts Receivable (PAR) data in a designated format to automatically post the required accounting entries to the system general ledger. | RRB | N/A | Mandatory | |
| RRB-GL-56 | The system should be able to produce cash statements that provide daily collections and disbursements data by transaction type (e.g., receipts - payroll taxes, interest; disbursements - benefits paid, salaries and expenses) to be used by the agency's actuaries. | RRB | N/A | Value Added | |
| RRB-GL-57 | The system should provide Budget with an effective date field for apportionment input. | RRB | N/A | Value Added | |
| RRB-GL-58 | The system should have the capability to show which SF-132 lines are affected and which accounts are debited and credited. | RRB | N/A | Value Added | |
| RRB-GL-59 | The system should provide automatic notices of insufficient allotments to Budget officials. | RRB | N/A | Value Added | |
| RRB-GL-60 | The system should provide bulk files for FACTS II and GTAS (Government Wide Treasury Account Symbol Adjusted Trial Balance). | RRB | N/A | Mandatory | |
| RRB-GL-61 | The system should provide the ability to view ledgers on-line. | RRB | N/A | Value Added |
&L&10U.S. Railroad Retirement Board FMIS Attachment 1&R&10&P of &N
IN
RRB ID Number Requirement Source Original Source ID Number Priority Vendor Response:
Solution Meets Requirement
| (Y, P, or N) | Vendor Comments | ||||
| RRB-IN-01 | The system must provide automated functionality to record beginning balances (on-hand), acquisitions (on order), withdrawals (dispositions/releases), and calculate ending balances (available on-hand) expressed in dollar values and physical units. | FSIO - Inventory System Requirements with RRB modifications | N/A | Mandatory | |
| RRB-IN-03 | The system must provide automated functionality such as a Physical Inventory Adjustment Document (IA) to record changes to value of Inventory, Supply Amounts and Materials due to changes in condition or other impacting circumstances. | FSIO - Inventory System Requirements with RRB modifications | N/A | Mandatory | |
| RRB-IN-05 | The system must provide automated functionality to identify the type of transaction affecting the item; e.g., initial acquisition, inventory adjustment, over-the counter transactions, pick and issue documents, stock issue confirmation documents, location, change in location, and disposal. | FSIO - Inventory System Requirements with RRB modifications | N/A | Mandatory | |
| RRB-IN-08 | The system must provide automated functionality to provide a field for a Unique Item Identifier (UID). A UID is a unique, unambiguous string of alpha numeric characters that enable the identification of a specific item or form from any other like or unlike it in compliance with ISOs 15434 and 15418.2. | FSIO - Inventory System Requirements with RRB modifications | N/A | Mandatory | |
| RRB-IN-19 | The system must provide automated functionality such as a Physical Inventory Adjustment Document (IA) with the proper reason for adjustment code to record reduction in the dollar value and quantity of inventory items destroyed, lost, or pilfered. | FSIO - Inventory System Requirements with RRB modifications | N/A | Mandatory |
&L&10U.S. Railroad Retirement Board FMIS Attachment 1&R&10&P of &N
PM
RRB ID Number Requirement Source Original Source ID Number Priority Vendor Response:
Solution Meets Requirement
| (Y, P, or N) | Vendor Comments | ||||
| RRB-PM-01 | The system must provide the capability to establish and maintain CCR/SAM and non-CCR/SAM information about non-federal payees (vendors) to support payment request and disbursement processes. | FSIO - 2009 Core Requirements with RRB modifications | PMA-01 | Mandatory | |
| RRB-PM-04 | The system must provide the automated capability to import payee data from the CCR/SAM system no less frequently than daily. | FSIO - 2009 Core Requirements with RRB modifications | PMA-04 | Mandatory | |
| RRB-PM-05 | The system must provide automated functionality that prevents the manual updating of CCR/SAM-originated data in the payee information file. | FSIO - 2009 Core Requirements with RRB modifications | PMA-06 | Mandatory | |
| RRB-PM-08 | The system must provide the automated capability to associate each combination of the DUNS and DUNS+4 numbers with one and only one bank account for each CCR/SAM vendor. | FSIO - 2009 Core Requirements with RRB modifications | PMA-09 | Mandatory | |
| RRB-PM-13 | The system must provide the automated functionality to prevent new obligations and payments to payees with expired CCR/SAM registrations. | FSIO - 2009 Core Requirements with RRB modifications | PMA-17 | Mandatory | |
| RRB-PM-32 | The system must provide the automated functionality to validate, prior to recording, payment requests from registered CCR/SAM vendors for the following CCR/SAM vendor information: |
• Vendor status is active.
• Vendor name on payment request or referenced obligation is the same as CCR/SAM company name (legal, DBA, or division).
• DUNS+4 number on referenced obligation is the same as DUNS+4 number on vendor file.
| Hold payment requests that fail these validations from further processing. | FSIO - 2009 Core Requirements with RRB modifications | PMC-06 | Mandatory |
| RRB-PM-33 | The system must provide the automated functionality to validate, at the time of preliminary payment scheduling, payments to registered CCR/SAM vendors for the following CCR/SAM vendor information: |
• Vendor status is active.
• Vendor name on payment is the same as CCR/SAM company name (legal, DBA, or division) on vendor file.
• DUNS+4 number on referenced obligation is the same as DUNS+4 number on vendor file.
| Hold payment requests that fail these validations from further processing. | FSIO - 2009 Core Requirements with RRB modifications | PMC-07 | Mandatory | ||
| RRB-PM-85 | The system must have the capability to export data to fit the Treasury's Payment Application Modernization (PAM) standard format when making disbursements or reporting on disbursements. This is to include TAS/BETC information. Functionality must exist based on Treasury implementation schedule and cutover dates. | Treasury 1/14/11 Memo "Upcoming FMS Systems Changes and Timelines" | N/A | Mandatory | |
| RRB-PM-86 | The system must provide automated functionality to cancel an obligation resulting from ordering medical exams and consultations. | RRB | N/A | Mandatory | |
| RRB-PM-87 | The system must provide automated functionality to cancel medical exam or medical consult payments. | RRB | N/A | Mandatory | |
| RRB-PM-88 | The system must provide the capability to handle medical exam and consulting opinion functionality as described in the SOW and Exhibit 1 (obligate, receive and automatically generate payment upon receipt). Includes the ability to create a daily file for vendor download. | RRB | N/A | Mandatory | |
| RRB-PM-89 | The system must provide an interface from the travel system to obligate, process payments and cancel obligations. | RRB | N/A | Mandatory | |
| RRB-PM-95 | The system should provide the ability to interface/download files from the purchase card vendor (e.g., Citibank) for payment. | RRB | N/A | Value Added | |
| RRB-PM-96 | The system must provide the ability to make payments for purchase card invoices (Citibank), referencing the related obligation(s). | RRB | N/A | Value Added | |
| RRB-PM-97 | The system must provide the capability to add vendor data for payees that may not be registered in the CCR/SAM. | RRB | N/A | Mandatory | |
| RRB-PM-98 | The system must provide the ability to obligate funds for fixed special accounts. | RRB | N/A | Mandatory | |
| RRB-PM-99 | The system must have the capability to do split disbursements (e.g., credit card and employee payments for travel). | RRB | N/A | Mandatory | |
| RRB-PM-102 | The system should provide the ability to use automated workflow to forward Citibank purchase card invoices to authorizing officials for approval. | RRB | N/A | Value Added | |
| RRB-PM-104 | The system should provide automated functionality that updates employee vendor records on a recurring basis. | RRB | N/A | Value Added |
&L&10U.S. Railroad Retirement Board FMIS Attachment 1&R&10&P of &N
PO
RRB ID Number Requirement Source Original Source ID Number Priority Vendor Response:
Solution Meets Requirement
| (Y, P, or N) | Vendor Comments | |
| RRB-PO-11 | The system must have automated capability to query agency procurement history for recent vendor procurement actions. Parameters are NSN/Part Number, NAICS, FSC, PSC, or UNSPSC, and date item entered. Store results for use during evaluation, negotiation, and selection phase. Display the following information regarding previous purchases: |
• Vendor name
• Vendor ID number
• Vendor POC name
• Vendor POC telephone
• Vendor POC e-mail
• DUNS number/BPN number
• Vendor TIN code
• CAGE code/NCAGE code
• Name of ordering office previously acquiring item
• Contract or order number
• Date item acquired
• Quantity
• Unit price
• Competitive or sole source
| • Number of offerors for the previous procurement and how many were small businesses | FSIO - Acquisition System Requirements - 2008 - Acquisition Planning with RRB modifications | APB-02 | Mandatory |
| RRB-PO-12 | The system must have automated capability to query registered CCR/SAM vendors. Parameters include NAICS and Item number/NSN/Part Number code. Results to be stored include: |
• Vendor name
• Vendor POC name
• Vendor POC telephone
• Vendor POC e-mail
• DUNS number/BPN number
• Vendor TIN code
• CAGE code/NCAGE code
• NAICS
• FSC /PSC
| • Small Business Size & category | FSIO - Acquisition System Requirements - 2008 - Acquisition Planning with RRB modifications | APB-03 | Mandatory | ||
| RRB-PO-18 | The system must have automated capability to capture the evaluation Justification and Approval (J&A) memo on plans where competition extent code is other than full and open competition. Required for acquisitions over $25,000, with exceptions per FAR part 6. | FSIO - Acquisition System Requirements - 2008 - Acquisition Planning with RRB modifications | APC-03 | Mandatory | |
| RRB-PO-23 | The system must have automated capability to generate a report of acquisition plans by any one or a combination of the following parameters: |
• Description
• Dollar amount
• Accounting classification elements of fund cite
• Requestor’s name
• Requestor’s organization code
• CO
• CS
• Vendor Name
| • Socioeconomic category set-aside | FSIO - Acquisition System Requirements - 2008 - Acquisition Planning with RRB modifications | APC-08 | Mandatory | ||
| RRB-PO-44 | The system must provide automated functionality to detect and prevent duplication of selected clauses included in Section H in other sections of the solicitation. | FSIO - Acquisition System Requirements - 2008 - Synopsis & Solicitation Function with RRB modifications | ISB-10 | Mandatory | |
| RRB-PO-49 | The system must provide automated functionality to detect and prevent duplication of selected FAR clauses included in Section L, in other sections of the solicitation. | FSIO - Acquisition System Requirements - 2008 - Synopsis & Solicitation Function with RRB modifications | ISB-15 | Mandatory | |
| RRB-PO-51 | The system must provide automated functionality to identify those Section J attachments that are sensitive in nature to facilitate restricting their access through FedTeDS or other access means. | FSIO - Acquisition System Requirements - 2008 - Synopsis & Solicitation Function with RRB modifications | ISB-17 | Mandatory | |
| RRB-PO-68 | The system must provide automated functionality to query the WDOL, if applicable, to capture the most current wage determination for that locality for that work and/or create a CBA wage determination on WDOL. Include the WD as an attachment or refer to it in the solicitation. | FSIO - Acquisition System Requirements - 2008 - Synopsis & Solicitation Function with RRB modifications | ISB-34 | Mandatory | |
| RRB-PO-71 | The system must provide automated functionality to validate that the offeror/bidder CCR/SAM registration status is active. If expired, notify vendor. | FSIO - Acquisition System Requirements - 2008 - Screening & Evaluation Function with RRB modifications | SEA-02 | Mandatory | |
| RRB-PO-77 | The system must provide automated functionality to capture the receipt of bids/proposals. Include the following information: |
• Vendor name
• Vendor ID number
• DUNS number/BPN number
• Vendor TIN code
• CAGE code/NCAGE code
• Receipt date
• Receipt time
• Type (e.g., solicited, modification, alternate, unsolicited, final)
• Bidding round
• Any exceptions taken to terms and conditions
| • Expiration date of offer | FSIO - Acquisition System Requirements - 2008 - Synopsis & Solicitation Function with RRB modifications | SEB-01 | Mandatory | ||
| RRB-PO-80 | The system must provide automated functionality to notify bidders/offerors of bids/proposals rejected due to receipt after closing date/time. System must allow for manual override by user (CS). | FSIO - Acquisition System Requirements - 2008 - Screening & Evaluation Function with RRB modifications | SEB-04 | Mandatory | |
| RRB-PO-90 | The system must provide automated functionality to capture pricing information. Calculate line item and total bid price for each bidder. Identify the apparent low bidder. The abstract of bid offers should include the independent government cost estimate. | FSIO - Acquisition System Requirements - 2008 - Screening & Evaluation Function with RRB modifications | SEB-14 | Mandatory | |
| RRB-PO-118 | The system must provide automated functionality to: |
• Capture award terms and conditions, including customized clause text and fill-ins.
• Generate final award terms and conditions, including customized clause text and fill-ins in award format (contract, task/delivery order, work order, blanket purchase agreements)
• Generate the proposed award documents. Notify approving official.
• Associate multiple offers with solicitation and all resulting awards. Capture selection criteria and grading (ranking) information of each associated requirement.
• Capture contract line item information to include list of documents, exhibits, fill-ins, and other attachments at the line item level.
• Identify modifications or updates to clauses.
| • Generate a list of attachments and exhibits for procurement instruments and award actions. Capture attachments and exhibits | FSIO - Acquisition System Requirements - 2008 - Award Function with RRB modifications | AWA -01 to -07 | Mandatory |
| RRB-PO-119 | The system must have automated functionality to: |
• Generate a configurable procurement action checklist.
• Associate award line items with solicitation line items. Support the association of single/multiple award lines to single/multiple solicitation line item. (Split/multiple awards)
• Associate multiple award line items to a single solicitation line item. (Split/multiple awards)
• Capture delivery/performance dates. When delivery/performance dates are dependent on other scheduled items, calculate the delivery/performance date based on task completion information (i.e., when project plan is due five (5) days after award, use award date to determine project plan delivery/performance date).
• Capture liquidation rate and basis for contract financing payments, where applicable.
• Prevent awards to vendors whose CCR/SAM registration is expired or capture FAR exception clause. Allow for contract exception.
• Prevent awards to excluded parties.
| • Prevent document designated unapproved/internal from being distributed to vendors (such as marking “DRAFT” on every page of an unsigned award for review by the requisitioner). | FSIO - Acquisition System Requirements - 2008 - Award Function with RRB modifications | AWA -10 to 16 | Mandatory |
| RRB-PO-129 | The system must have automated capability to generate and export the obligation document and include the following information: |
• Award date
• Source system ID
• Source system -generated document number
• Reference document number
• Reimbursable agreement number (when applicable)
• Source document numbers (e.g., contract number and associated delivery/task order number (if applicable); BPA number and associated call number; purchase order number; modification number)
• Obligation type (e.g., contract, delivery/task order, purchase order)
• Prompt Pay indicator and type
• Payment terms (e.g., discount terms)
• Fast Pay indicator
• Matching terms (2-way, 3-way, 4-way)
• Vendor ID number
• Vendor name
• DUNS number/BPN number
• DUNS+4 number
• Vendor TIN code
• CAGE code/NCAGE code
• Contracting Officer’s name
• Contracting Officer’s telephone number
• Contracting Officer’s e-mail address
• Amounts increased/decreased
• Contract financing indicator
• Contract financing rate (if applicable)
• Liquidation rate Contracting Specialist/Administrator's Name, email address & telephone number
| information: | FSIO - Acquisition System Requirements - 2008 - Award Function with RRB modifications | AWC-08 | Mandatory |
| RRB-PO-130 | The system must have automated capability to generate and export the obligation document and include the following information: |
• DUNS number/BPN number
• DUNS+4 number
• Vendor TIN code
• CAGE code/NCAGE code
• Contracting Officer’s name
• Contracting Specialist/Administrator's Name, email address & telephone number
• Contracting Officer’s representative name, telephone number & e-mail address
• Amounts increased/decreased
• Contract financing indicator
• Contract financing rate (if applicable)
| • Liquidation rate | FSIO - Acquisition System Requirements - 2008 - Award Function with RRB modifications | AWC-08 con't | Mandatory | ||
| RRB-PO-133 | The system must have automated functionality to generate notification of Congress 30 days prior to the award of a multi-year contract greater than FAR-specific (FAR 17.108) or agency-assigned threshold. System notification must be routed through a review chain. | FSIO - Acquisition System Requirements - 2008 - Award Function with RRB modifications | AWC-11 | Mandatory | |
| RRB-PO-135 | The system must have automated functionality to distribute contracts/orders to vendors electronically via EDI or Internet. System should provide user with notice that the contract/order was sent and also provide a read receipt as requested. | FSIO - Acquisition System Requirements - 2008 - Award Function with RRB modifications | AWC-13 | Mandatory | |
| RRB-PO-141 | The system must have automated functionality to route bilateral contract action to contractor for signature. System must allow for electronic signatures | FSIO - Acquisition System Requirements - 2008 - Award Function with RRB modifications | AWC-19 | Mandatory | |
| RRB-PO-147 | The system must have automated functionality to prevent awards to vendors whose CCR/SAM registration is expired or capture FAR exception clause. Allow for contract exception.. | FSIO - Acquisition System Requirements - 2008 - Award Function with RRB modifications | AWC-25 | Mandatory | |
| RRB-PO-152 | The system must have automated functionality to maintain agency-defined lists of contract administration functions based on: |
• Contract type
• Vendor type
• Dollar value of contract
| • Period of Performance/ Options to be Exercised | FSIO - Acquisition System Requirements - 2008 - Contract Administration Function with RRB modifications | CAA-01 | Mandatory |
| RRB-PO-159 | The system must have automatic functionality to capture contract terms and conditions, including but not limited to the following: The system must have automatic functional to capture contract terms and conditions, including but not limited to the following: |
• Payment terms
• Prompt pay indicator and type
• Fast pay indicator
• Liquidation rate indicator
• Liquidation rate
• Progress payment rate
• Discount terms
• Matching terms (e.g., 2-way, 3-way, 4-way)
• DUNS number/BPN number
• DUNS+4 number
• Vendor TIN code
• CAGE code/NCAGE code
• Noncommercial Item Purchase Financing
• Commercial Item Purchase Financing
• Loan Guarantees for Defense Production
• Advance Payment for Noncommercial Items
• Progress Payments Based on Cost
| • Performance Based Payments | FSIO - Acquisition System Requirements - 2008 - Contract Administration Function with RRB modifications | CAA-08 | Mandatory |
| RRB-PO-175 | The system must have automatic functionality to capture bond and surety information including: |
• Contract number
• Vendor ID number
• DUNS number/BPN number
• Vendor TIN code
• CAGE code/NCAGE code
• Bond type
• Bond number
| • Expiration date | FSIO - Acquisition System Requirements - 2008 - Contract Administration Function with RRB modifications | CAB-17 | Mandatory |
| RRB-PO-176 | The system must have automatic functionality to capture expiration dates of certificates of insurance. Notify contracting officer and contract administrator prior to expiration, include: |
• Contract number
• Vendor ID number
• DUNS number/BPN number
• Vendor TIN code
• CAGE code/NCAGE code
• Expiration date, and
| • Type of insurance | FSIO - Acquisition System Requirements - 2008 - Contract Administration Function with RRB modifications | CAB-18 | Mandatory | ||
| RRB-PO-177 | The system must have automatic functionality to notify contracting officer and contract administrator when a bond expires. | FSIO - Acquisition System Requirements - 2008 - Contract Administration Function with RRB modifications | CAB-19 | Mandatory | |
| RRB-PO-181 | The system must have automatic functionality to capture and export to the Asset Management (AM) system, the following information related to government-furnished property (GFP) that the contractor acquires: |
• Contract number
• Date of acquisition
• Purchase price
• Serial number
• Description
| • Classification (agency-defined) | FSIO - Acquisition System Requirements - 2008 - Contract Administration Function with RRB modifications | CAB-23 | Mandatory |
| RRB-PO-189 | The system must have automatic functionality to capture contract post award dispute information to include but is not limited to: |
• Disputer (vendor ID number) ID
• Vendor TIN code
• CAGE code/NCAGE code
• Disputer Name
• Contract Number
• Dispute Date
• Dispute Text
| • Dispute related clause(s) | FSIO - Acquisition System Requirements - 2008 - Contract Administration Function with RRB modifications | CAB-31 | Mandatory | ||
| RRB-PO-193 | The system must have automatic functionality to integrate the contract writing system so it provides the final performance evaluations for each contract period to the government-wide performance repository. | FSIO - Acquisition System Requirements - 2008 - Contract Administration Function with RRB modifications | CAB-36 | Mandatory | |
| RRB-PO-197 | The system must have automatic functionality to export obligation data to Core financial system upon modifying the dollar amount of contract or upon exercising a contract option in real time or near real time. | FSIO - Acquisition System Requirements - 2008 - Contract Administration Function with RRB modifications | CAC-04 | Mandatory |
This is the start of the file's text. The full file is on GovTribe.
Other files for this federal contract opportunity
Show all 18
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
File details come from the government source that posted it. Updated .