EPIC_Requirements_Matrix_V1_0.xls
XLS spreadsheet 240 KB Posted
- Attached to
- EPIC System
- Solicitation number
- GPO09252013
- Issued by
-
Government Publishing Office
About this file
Attachment No. 2 EPIC Requirement Matrix
View the file
Other files
| File | Type | Posted |
|---|---|---|
| EPIC_ConOps_v1_1.pdf |
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
Requirements
| Req # | Requirement Feature | Req Text | Clarification | Can this requirement be met with COTS? (Y/N) | If so, which product? | If not, can this requirement be met through software extensions? | |
| (Y/N) | Additional Comments | ||||||
| AA-0001 | Agency Authorization (AA) | Ability for external customers to manage Federal agency account information through a group (e.g., agency locator code, contact point). | |||||
| AA-0002 | Agency Authorization (AA) | Ability for external customers to manage Federal agency billing information through a group (e.g., BACs, who is authorized to obligate funds, limitation amounts for contract vehicles, line of accounting). | |||||
| AA-0003 | Agency Authorization (AA) | Ability for external customers to register for a Deposit Account as a funding source. | |||||
| AA-0004 | Agency Authorization (AA) | Ability for external customers to register for an IPAC account as a funding source. | |||||
| AA-0005 | Agency Authorization (AA) | Ability for external customers to register for a credit card account as a funding source. | |||||
| AA-0006 | Agency Authorization (AA) | Provide the ability for GPO to manage the registration request process (e.g. authorizations to obligate funds, funding source approvals). | |||||
| AA-0007 | Agency Authorization (AA) | Ability for GPO to manually assign a BAC. | |||||
| AA-0008 | Agency Authorization (AA) | Ability for the system to automatically assign a BAC. | |||||
| AA-0009 | Agency Authorization (AA) | Ability for the system to associate the funding source with a BAC. | |||||
| AA-0010 | Agency Authorization (AA) | Ability for the system to associate the specific billing information (e.g. line of accounting) with a BAC. | |||||
| AA-0011 | Agency Authorization (AA) | Provide the ability to associate a BAC with a system account or system group. | |||||
| AA-0012 | Agency Authorization (AA) | Provide the ability to link BACs with a credit card. | |||||
| AA-0013 | Agency Authorization (AA) | Ability to notify users that a credit card expiration date is near or past due. | |||||
| AA-0014 | Agency Authorization (AA) | Provide the ability to assign not to exceed limits with a funding source (e.g. credit card limit, deposit account limit). | |||||
| AA-0015 | Agency Authorization (AA) | Ability to associate submitted orders with a system account or system group including all account information (personal, group, and financial information). | |||||
| AA-0016 | Agency Authorization (AA) | Provide the ability to manage the agency authorization process through workflow rules. | |||||
| AA-0017 | Agency Authorization (AA) | Provide the ability to send agency authorization related notifications and alerts to users based upon workflow rules. | |||||
| AA-0018 | Agency Authorization (AA) | Provide the ability for GPO to manage the registration request process. | |||||
| AA-0019 | Agency Authorization (AA) | Ability for external users to request a BAC. | |||||
| AA-0020 | Agency Authorization (AA) | Ability for external customers to request that a deposit account be replenished. | |||||
| A-0001 | Award (A) | Provide the ability to centralize all bid or quote data for an order. | |||||
| A-0002 | Award (A) | Provide the ability to search or sort bid or quote data. | |||||
| A-0003 | Award (A) | Provide the ability to automatically create abstracts based upon bid or quote data. | |||||
| A-0004 | Award (A) | Provide GPO users with appropriate vendor information in order to determine award (e.g., quality capabilities, equipment lists). | |||||
| A-0005 | Award (A) | Provide GPO users with appropriate vendor compliance information in order to determine award (e.g., quality history, compliance, correspondence history, order history, pre-award survey). | |||||
| A-0006 | Award (A) | Provide the ability for GPO users to provide notes within the order related to award or certification. | |||||
| A-0007 | Award (A) | Provide the ability for users to certify orders and award an order to a contractor(s). | |||||
| A-0008 | Award (A) | Provide the ability to highlight bid, quote, or specification information that is missing from required fields in the solicitation. | |||||
| A-0009 | Award (A) | Provide the capability to review and confirm prices with customers to confirm that obligated funds are available. | |||||
| A-0010 | Award (A) | Provide the capability to review and confirm prices with vendors. | |||||
| A-0011 | Award (A) | Provide the capability for vendors to confirm that their bid or quote complies with all specifications. | |||||
| A-0012 | Award (A) | Provide the ability to facilitate communication between GPO and vendors on bid or quote information to ensure compliance to specifications. | |||||
| A-0013 | Award (A) | Allow GPO to define the basis for the determination of the award (e.g. low price, highest quantity for a fixed price). | |||||
| A-0014 | Award (A) | Provide the ability to apply the costs of travel to an order as a basis of award. | |||||
| A-0015 | Award (A) | Provide the capability to link award documentation to an order(s). | |||||
| A-0016 | Award (A) | Allow GPO users to manage award documentation format and information. | |||||
| A-0017 | Award (A) | Generate and output all award documentation for orders. | |||||
| A-0018 | Award (A) | Provide the ability to post award results publicly. | |||||
| A-0019 | Award (A) | Provide the ability to notify the contractor(s) and customers of award. | |||||
| A-0020 | Award (A) | Provide the ability for contractors and customers to access order information, including award documentation. | |||||
| A-0021 | Award (A) | Provide the ability to include and associate award information and other documentation (e.g. non-responsive letters, award letter) in the order. | |||||
| A-0022 | Award (A) | Provide the ability to generate and notify vendors of documentation (e.g. non-responsive letters) for orders that they have not been awarded. | |||||
| A-0023 | Award (A) | Provide the ability to support the pre and post award conference process. | |||||
| A-0024 | Award (A) | Provide the ability to notify contractors that a Print Order has been placed against a term contract that they have been awarded. | |||||
| A-0025 | Award (A) | Provide the ability for users to denote how or why award determination was made (e.g. lowest cost, best value). | |||||
| A-0026 | Award (A) | Provide the ability for customers to review SPA quotes and make award. | |||||
| A-0027 | Award (A) | Provide the ability to automatically generate a Work Order number and assign it to a SPA order. | |||||
| A-0028 | Award (A) | Provide the ability to notify a customer that a credit card limit may be exceeded after an order’s award amount determined. | |||||
| A-0029 | Award (A) | Provide the ability to manage the award through workflow rules. | |||||
| A-0030 | Award (A) | Provide the ability to send award related notifications and alerts to users based upon workflow rules. | |||||
| A-0031 | Award (A) | Provide the ability to check a deposit account for available funds. | |||||
| CT-0001 | Compliance and Tracking (CT) | The system shall have the capability to track orders. | |||||
| CT-0002 | Compliance and Tracking (CT) | The system shall have the capability to track orders by divisions. | |||||
| CT-0003 | Compliance and Tracking (CT) | The system shall have the capability to track orders by sections. | |||||
| CT-0004 | Compliance and Tracking (CT) | The system shall have the capability to track orders by operations. | |||||
| CT-0005 | Compliance and Tracking (CT) | The system shall have the capability to track when a order is received. | This refers to when a order is received by date and time at any point in the production process. | ||||
| CT-0006 | Compliance and Tracking (CT) | The system shall have the capability to track when a order is completed. | This refers to when a order is completed by date and time at any point in the production process. | ||||
| CT-0007 | Compliance and Tracking (CT) | The system shall have the capability to track orders that are partially complete. | E.g., partial shipments | ||||
| CT-0008 | Compliance and Tracking (CT) | The system shall allow an authorized user to input tracking information. | |||||
| CT-0009 | Compliance and Tracking (CT) | The system shall allow an authorized user to input additional tracking information by section. | This could be accomplished through a comments field. | ||||
| CT-0010 | Compliance and Tracking (CT) | The system shall allow an authorized user to input additional tracking information by division. | |||||
| CT-0011 | Compliance and Tracking (CT) | The system shall allow an authorized user to input additional tracking information by operation. | |||||
| CT-0012 | Compliance and Tracking (CT) | The system shall record the user who inputs tracking information. | |||||
| CT-0013 | Compliance and Tracking (CT) | The system shall timestamp when a user has input tracking information. | |||||
| CT-0014 | Compliance and Tracking (CT) | The system shall allow authorized users to manage tracking information. | |||||
| CT-0015 | Compliance and Tracking (CT) | The system shall allow authorized users to denote the status of a order. | Examples of order status include ok to print, out on proof, order on hold, etc. | ||||
| CT-0016 | Compliance and Tracking (CT) | The system shall have the capability to track orders by items. | |||||
| CT-0017 | Compliance and Tracking (CT) | The system shall have the capability to associate tracking information with a workflow. | |||||
| CT-0018 | Compliance and Tracking (CT) | The system shall have the capability for users to inquire on the tracking information for a order. | |||||
| CT-0019 | Compliance and Tracking (CT) | The system shall have the capability for users to input quality control information for a order. | |||||
| CT-0020 | Compliance and Tracking (CT) | The system shall have the capability to notify authorized users if a order is falling behind schedule. | The time that specifies if a order is behind schedule is TBS. | ||||
| CT-0021 | Compliance and Tracking (CT) | The system shall have the capability to alert authorized users if a order is falling behind schedule. | The time that specifies if a order is behind schedule is TBS. | ||||
| CT-0022 | Compliance and Tracking (CT) | The system shall have the capability to track order status using a order identifier(s). | |||||
| CT-0023 | Compliance and Tracking (CT) | The system shall have the capability for an authorized user to inform the system that an order activity has been completed. | |||||
| CT-0024 | Compliance and Tracking (CT) | The system shall allow authorized users to add status information about order activities. | This could be accomplished through a comments field. | ||||
| CT-0025 | Compliance and Tracking (CT) | The system shall allow authorized users to modify status information about order activities. | |||||
| CT-0026 | Compliance and Tracking (CT) | The system shall have the capability to notify users of order tracking status. | |||||
| CT-0027 | Compliance and Tracking (CT) | The system shall provide the capability to automatically request order status information from users. | |||||
| CT-0028 | Compliance and Tracking (CT) | The system shall have the capability for authorized users to enter shipping and delivery tracking information. | This would include the shipping company, tracking numbers, etc. | ||||
| CT-0029 | Compliance and Tracking (CT) | The system shall have the capability to provide shipping notification to authorized users. | |||||
| CT-0030 | Compliance and Tracking (CT) | The system shall have the capability to provide delivery notification to authorized users. | |||||
| CT-0031 | Compliance and Tracking (CT) | Provide a central repository of all compliance information. | |||||
| CT-0032 | Compliance and Tracking (CT) | Provide the ability to link compliance information with an order. | |||||
| CT-0033 | Compliance and Tracking (CT) | Provide the ability to link compliance with a vendor or contractor. | |||||
| CT-0034 | Compliance and Tracking (CT) | Provide the ability to associate vendor and contractor information with compliance information. | |||||
| CT-0035 | Compliance and Tracking (CT) | Provide the ability to electronically send contractor letters (e.g. delinquent orders, disputed orders). | |||||
| CT-0036 | Compliance and Tracking (CT) | Provide the ability for users to enter tracking information for an order. | |||||
| CT-0037 | Compliance and Tracking (CT) | Provide the ability to link tracking information with an order. | |||||
| CT-0038 | Compliance and Tracking (CT) | Provide the ability to track revisions (e.g., Author's Alterations, Printer's Errors) made by users. | |||||
| CT-0039 | Compliance and Tracking (CT) | Provide the ability to track proof activities. | |||||
| CT-0040 | Compliance and Tracking (CT) | Provide the ability for GPO to manage the complexity of tracking information (e.g. simple tracking information for certain contract types and more complex tracking information for other contract types). | |||||
| CT-0041 | Compliance and Tracking (CT) | Provide the ability for contractor to verify in BPI that quantity shipped matches the specifications. | |||||
| CT-0042 | Compliance and Tracking (CT) | Provide the ability to validate a proof of delivery against a delivery due date. | |||||
| CT-0043 | Compliance and Tracking (CT) | Provide the ability for users to enter information about orders that have encountered delays. | |||||
| CT-0044 | Compliance and Tracking (CT) | Provide the ability to automatically receive tracking information from other systems. | This includes UPS, FedEx, DHL, other delivery systems. | ||||
| CT-0045 | Compliance and Tracking (CT) | Provide the ability to automatically notify users when due dates are past due. | |||||
| CT-0046 | Compliance and Tracking (CT) | Provide the ability to manage the compliance and tracking process through workflow rules. | |||||
| CT-0047 | Compliance and Tracking (CT) | Provide the ability to send compliance and tracking related notifications and alerts to users based upon workflow rules. | |||||
| CA-0001 | Contract Administration (CA) | The system shall have the capability for users to enter BPI that includes tracking information about a order. | |||||
| CA-0002 | Contract Administration (CA) | The system shall provide the capability to store BPI that includes tracking information about a order. | |||||
| CA-0003 | Contract Administration (CA) | The system shall provide the capability for users to edit BPI that includes tracking information about a order. | |||||
| CA-0004 | Contract Administration (CA) | Provide the ability to manage the quality complaint process. | |||||
| CA-0005 | Contract Administration (CA) | Provide the ability to associate quality complaints with an order. | |||||
| CA-0006 | Contract Administration (CA) | Provide the ability for GPO to record information related to a quality compliant. | |||||
| CA-0007 | Contract Administration (CA) | Provide the ability to associate quality complaints with compliance information. | |||||
| CA-0008 | Contract Administration (CA) | Provide the ability to manage the modification process regardless of the contract vehicle. | |||||
| CA-0009 | Contract Administration (CA) | Provide the ability to create and issue modifications. | |||||
| CA-0010 | Contract Administration (CA) | Provide the ability to associate modifications with an order. | |||||
| CA-0011 | Contract Administration (CA) | Provide the ability for users to record information related to a modification. | |||||
| CA-0012 | Contract Administration (CA) | Provide the ability to track modification information (e.g. who issued a modification, who responded, who approved). | |||||
| CA-0013 | Contract Administration (CA) | Provide the ability to create and manage a modification template. | |||||
| CA-0014 | Contract Administration (CA) | Provide a repository for modification language. | |||||
| CA-0015 | Contract Administration (CA) | Provide the ability to input standard modification language into a modification. | |||||
| CA-0016 | Contract Administration (CA) | Provide the ability to search modification language. | |||||
| CA-0017 | Contract Administration (CA) | Provide the ability to generate contract administration letters. | |||||
| CA-0018 | Contract Administration (CA) | Provide the ability to pre-populate data with order BPI where applicable on contract administration letters. | |||||
| CA-0019 | Contract Administration (CA) | Provide the ability for users to request contract changes. | |||||
| CA-0020 | Contract Administration (CA) | Provide the ability for users to approve contract changes. | |||||
| CA-0021 | Contract Administration (CA) | Provide the ability to manage communications between GPO, contractors, and customers. | |||||
| CA-0022 | Contract Administration (CA) | Provide the ability to manage the contract administration process through workflow rules. | |||||
| CA-0023 | Contract Administration (CA) | Provide the ability to send contract administration related notifications and alerts to users based upon workflow rules. | |||||
| CA-0024 | Contract Administration (CA) | Provide the ability to associate all components of an order and create an electronic contract file. | |||||
| CA-0025 | Contract Administration (CA) | Provide the capability to manage a standard language repository. | |||||
| CA-0026 | Contract Administration (CA) | Provide the capability to insert language from the standard language repository | |||||
| CE-0001 | Contract Establishment (CE) | Provide a central repository for all GPO contracts (e.g. term contracts, SPA, GPO Express, 951-M). | |||||
| CE-0002 | Contract Establishment (CE) | Provide the ability to search all contracts based upon BPI. | |||||
| CE-0003 | Contract Establishment (CE) | Ability to associate a contract with a customer(s) or contractor(s). | |||||
| CE-0004 | Contract Establishment (CE) | Provide the ability to associate all orders placed against a contract. | |||||
| CE-0005 | Contract Establishment (CE) | Provide the ability to generate basis of award information to show how many times a line item on a term contract was used. | |||||
| CE-0006 | Contract Establishment (CE) | Provide the ability for GPO to create and manage all contracts. | |||||
| CE-0007 | Contract Establishment (CE) | Ability for customers to request a new term contract. | |||||
| CE-0008 | Contract Establishment (CE) | Provide the ability to manage the contract renewal process. | |||||
| CE-0009 | Contract Establishment (CE) | Provide the ability to generate contract letters (e.g. Contract Renewal Letters, Option Year Review Letters). | |||||
| CE-0010 | Contract Establishment (CE) | Provide the ability for users to add notes specific to a contract (e.g. complaints, possible revisions to a contract). | |||||
| CE-0011 | Contract Establishment (CE) | Ability for customers to place orders against an existing term contract. | |||||
| CE-0012 | Contract Establishment (CE) | Ability for customers to register for the SPA. | |||||
| CE-0013 | Contract Establishment (CE) | Provide a vendor repository of all SPA vendors. | |||||
| CE-0014 | Contract Establishment (CE) | Ability for customers to register for the GPO Express program. | |||||
| CE-0015 | Contract Establishment (CE) | Provide the capability to notify customers of contract instructions upon registration or creation. | |||||
| CE-0016 | Contract Establishment (CE) | Ability to monitor trends in order BPI (either all orders or orders specifically for a particular customer) to recommend if a new term contract could be written. | |||||
| CE-0017 | Contract Establishment (CE) | Provide the ability to manage the contract establishment process through workflow rules. | |||||
| CE-0018 | Contract Establishment (CE) | Provide the ability to alert users that a contract may be used based upon BPI (e.g. BPI matches a contract directly; BPI matches a majority of a contract specifications). | |||||
| CE-0019 | Contract Establishment (CE) | Provide the ability to send contract establishment related notifications and alerts to users based upon workflow rules. | |||||
| CE-0020 | Contract Establishment (CE) | Provide the ability to associate a contract with a particular GPO office. | |||||
| CVM-0001 | Contractor and Vendor Management (CVM) | A central repository for all vendor and contractor information. | |||||
| CVM-0002 | Contractor and Vendor Management (CVM) | Provide the ability for vendors to register with GPO (e.g. equipment capabilities, financial data, and other information). | |||||
| CVM-0003 | Contractor and Vendor Management (CVM) | Ability for vendors to electronically submit their registration information. | |||||
| CVM-0004 | Contractor and Vendor Management (CVM) | Provide the ability for vendors to attach financial data with their registration (e.g. W9 form). | |||||
| CVM-0005 | Contractor and Vendor Management (CVM) | Provide interfaces with mandatory fields to ensure GPO receives required information for registration processing. | |||||
| CVM-0006 | Contractor and Vendor Management (CVM) | Provide the ability for users to manage vendor or contractor information. | |||||
| CVM-0007 | Contractor and Vendor Management (CVM) | Provide the ability to execute searches and sort the contractor and vendor repository. | |||||
| CVM-0008 | Contractor and Vendor Management (CVM) | Provide the ability for GPO to manage the contractor and vendor registration process. | |||||
| CVM-0009 | Contractor and Vendor Management (CVM) | Ability for GPO to manually assign a Contractor Code or other contractor identifier. | |||||
| CVM-0010 | Contractor and Vendor Management (CVM) | Ability for the system to automatically assign a Contractor Code or other contractor identifier. | |||||
| CVM-0011 | Contractor and Vendor Management (CVM) | Ability for the system to associate a Contractors Code Contractor Code or other contractor identifier with a contractor or vendor account. | |||||
| CVM-0012 | Contractor and Vendor Management (CVM) | Provide a vendor repository of all SPA vendors. | |||||
| CVM-0013 | Contractor and Vendor Management (CVM) | Allow users to search the SPA vendor repository based upon defined parameters (e.g. capabilities, locations). | |||||
| CVM-0014 | Contractor and Vendor Management (CVM) | Ability to link a contractor with their compliance, bid/quote, quality, award history. | |||||
| CVM-0015 | Contractor and Vendor Management (CVM) | Provide the ability to associate a vendor or contractor’s account with their history (e.g. all orders a contractor has been awarded, all bids or quotes a vendor has submitted, associate vendors with contract vehicles they are certified to perform work on, compliance report). | |||||
| CVM-0016 | Contractor and Vendor Management (CVM) | Provide the ability to notify a vendor of their contractor code or contractor identifier. | |||||
| CVM-0017 | Contractor and Vendor Management (CVM) | Provide the ability for GPO to assign a vendor a quality level. | |||||
| CVM-0018 | Contractor and Vendor Management (CVM) | Provide the ability for vendors to request a new quality level. | |||||
| CVM-0019 | Contractor and Vendor Management (CVM) | Provide the ability to notify GPO that a vendor’s quality level has not been evaluated within a specific timeframe (e.g. once every four years). | |||||
| CVM-0020 | Contractor and Vendor Management (CVM) | Provide the ability to notify and instruct vendors on how to conduct business with GPO (e.g. how to get a different quality rating, how to bill GPO). | |||||
| CVM-0021 | Contractor and Vendor Management (CVM) | Provide the ability for GPO to manage contractor and vendor letters and correspondence information. | |||||
| CVM-0022 | Contractor and Vendor Management (CVM) | Provide the ability to manage the contractor and vendor management process through workflow rules. | |||||
| CVM-0023 | Contractor and Vendor Management (CVM) | Provide the ability to send contractor and vendor management related notifications and alerts to users based upon workflow rules. | |||||
| CVM-0024 | Contractor and Vendor Management (CVM) | Provide the ability for SPA vendors to search the SPA repository to view authorized SPA customers, users, spending amounts, and other information. | |||||
| D-0001 | Delivery (D) | Expose delivery data to external users. | |||||
| D-0002 | Delivery (D) | Provide the ability for contractors to upload proof of delivery information (e.g. delivery receipts). | |||||
| D-0003 | Delivery (D) | Provide the ability for users to denote and verify that GFM has been received or returned before payment. | |||||
| D-0004 | Delivery (D) | Ability for contractors to denote that quality samples (blue label copies and QARCS) were randomly selected. | |||||
| D-0005 | Delivery (D) | Ability for users to denote notes about the delivery process. | |||||
| D-0006 | Delivery (D) | Provide the ability to manage the delivery process through workflow rules. | |||||
| D-0007 | Delivery (D) | Provide the ability to send delivery related notifications and alerts to users based upon workflow rules. | |||||
| DLM-0001 | Distribution List Management (DLM) | The system shal provide the capability for GPO and customers to manage distribution list information. | |||||
| DLM-0002 | Distribution List Management (DLM) | The system shall provide the ability for users to include distribution information and attach distribution lists. | |||||
| ESB-0001 | Enterprise Service Bus (ESB) | The system shall provide the capability to interoperate with services or applications deployed in different hardware and software platforms, using industry-accepted standards. | |||||
| ESB-0002 | Enterprise Service Bus (ESB) | The system shall have the capability to utilize GPO's Enterprise Service Bus. | |||||
| ESB-0003 | Enterprise Service Bus (ESB) | The system shall provide the capability to integrate newly developed (or acquired) services or applications (e.g. FDsys, Oracle Financials) using industry standard protocols. | This is considered as a placeholder to identify and integrate newly developed systems or applications as they are identified. | ||||
| ESB-0004 | Enterprise Service Bus (ESB) | The system shall provide the capability to integrate existing (or legacy) services or applications. | |||||
| EST-0001 | Estimating (EST) | The system shall estimate costs for GPO products and services for orders based upon BPI. | |||||
| EST-0002 | Estimating (EST) | The system shall have the capability to allow authorized users to input an estimate for a order. | This is an estimate that is in addition to a system generated estimate. | ||||
| EST-0003 | Estimating (EST) | The system shall have the capability to allow authorized users to override a system generated estimate. | This is for a particular line(s) item within an estimate. | ||||
| EST-0004 | Estimating (EST) | The system shall have the capability for an authorized user to enter an estimate approval/disapproval. | |||||
| EST-0005 | Estimating (EST) | The system shall have the capability to estimate shipping costs based upon BPI. | |||||
| EST-0006 | Estimating (EST) | The system shall allow users to retrieve estimates for previous orders. | |||||
| EST-0007 | Estimating (EST) | The system shall save order estimates. | |||||
| EST-0008 | Estimating (EST) | The system shall store order estimates. | |||||
| EST-0009 | Estimating (EST) | The system shall have the capability to perform estimating scenarios. | For example, generating estimates for a order on different kinds of stock. | ||||
| EST-0010 | Estimating (EST) | The system shall have the capability to save versions of estimates. | |||||
| EST-0011 | Estimating (EST) | The system shall have the capability to determine select order materials needed for the order based upon BPI. | For example, based upon an estimate you will need 40 pounds of paper. | ||||
| EST-0012 | Estimating (EST) | The system shall have the capability to associate a estimate with a order. | |||||
| EST-0013 | Estimating (EST) | The system shall have the capability to allow authorized users to manually adjust estimates. | |||||
| EST-0014 | Estimating (EST) | The system shall have the capability for users to manually enter surcharges. | This is will be used after the system has generated an estimate. | ||||
| EST-0015 | Estimating (EST) | The system shall have the capability for users to manually enter discounts. | This is will be used after the system has generated an estimate. | ||||
| EST-0016 | Estimating (EST) | The system shall have the capability for users to manually enter additional charges. | This could be used for rush orders or items not included in the scale of price rates. | ||||
| EST-0017 | Estimating (EST) | The system shall have the capability to automatically generate estimates based upon a product type. | For example, Congressional Hearings are charged at the current page rate. | ||||
| EST-0018 | Estimating (EST) | The system shall have the capability to automatically adjust surcharges based upon a product type. | |||||
| EST-0019 | Estimating (EST) | The system shall have the capability to automatically discount a order based upon a product type. | |||||
| EST-0020 | Estimating (EST) | The system shall have the capability to denote an estimate as informal. | |||||
| EST-0021 | Estimating (EST) | The system shall have the capability to denote an estimate as firm. | |||||
| EST-0022 | Estimating (EST) | The system shall have the capability to generate estimates by running rate 'per thousand' pieces. | This estimate would not include make-ready costs. It would be for running costs only and is known as the rider rate. | ||||
| EST-0023 | Estimating (EST) | The system shall have the capability to breakdown a order estimate by rider cost only. | Note: Riders do not include make-ready costs. | ||||
| EST-0024 | Estimating (EST) | The system shall have the capability to breakdown a order estimate by make-ready costs only. | |||||
| EST-0025 | Estimating (EST) | The system shall have the capability to generate estimates for items within a order. | |||||
| EST-0026 | Estimating (EST) | The system shall have the capability to save estimates if they are not complete. | For example, if the paper price is not known. | ||||
| EST-0027 | Estimating (EST) | The system shall have the capability to search estimates based upon BPI. | All fields within estimate data fields must be searchable. | ||||
| EST-0028 | Estimating (EST) | The system shall have the capability to estimate the total paper (by total weight) used for a order. | |||||
| EST-0029 | Estimating (EST) | The system shall have the capability to determine the size of mailing cartons based upon the BPI. | |||||
| EST-0030 | Estimating (EST) | The system shall have the capability for users to re-estimate orders that have been sent back in the workflow. | |||||
| EST-0031 | Estimating (EST) | The system shall have the capability to determine the total number of mailing cartons required based upon BPI. | |||||
| EST-0032 | Estimating (EST) | Ability to generate cost estimates based upon specific contract based prices (pricing of a particular contract including term contracts or SPA). | |||||
| EST-0033 | Estimating (EST) | Ability to generate cost estimates based upon general market price data including GPO historical prices, previous order costs, and GPO schedule of prices. | |||||
| EST-0034 | Estimating (EST) | Provide the ability to manage all cost estimate source data (e.g. change GPO schedule of prices, term contract economic price adjustments). | |||||
| EST-0035 | Estimating (EST) | Provide the ability to automatically estimate travel costs (e.g. for inspection services, production monitoring). | |||||
| EST-0036 | Estimating (EST) | Provide the ability to generate an estimate for a rider (the last product produced on a print run). | |||||
| EST-0037 | Estimating (EST) | Provide the ability to breakdown estimates into specific GPO defined categories (e.g. production, materials, shipping, human resources, other). | |||||
| EST-0038 | Estimating (EST) | Provide the ability for users to access previous quotes for SPA orders with similar BPI. | |||||
| EST-0039 | Estimating (EST) | Provide the ability to manage the estimating process through workflow rules. | |||||
| EST-0040 | Estimating (EST) | Provide the ability to send estimating related notifications and alerts to users based upon workflow rules. | |||||
| IB-0001 | Invoicing and Billing (IB) | Provide a central invoice submission and management system. | |||||
| IB-0002 | Invoicing and Billing (IB) | Provide the ability to have a standard invoice submission form for contractors. | |||||
| IB-0003 | Invoicing and Billing (IB) | Provide the ability to expose select billing data (e.g. if an invoice has been received, has GPO billed the customer, view billing information such as credit card receipts or GPO Form 400) from financial systems to GPO users and customers. | |||||
| IB-0004 | Invoicing and Billing (IB) | Provide the ability to expose select invoicing data (e.g. has GPO received the invoice and proof of delivery, has GPO processed the invoice, has GPO paid the contractor, view payment information about the order) from financial systems to users. | |||||
| IB-0005 | Invoicing and Billing (IB) | Provide the ability to link additional charges, including modifications, to an order. | |||||
| IB-0006 | Invoicing and Billing (IB) | Provide the ability to access all financial information related to riders (e.g. ability to separate order costs from rider costs). | |||||
| IB-0007 | Invoicing and Billing (IB) | Provide the ability to process and charge credit card orders. | |||||
| IB-0008 | Invoicing and Billing (IB) | Provide the ability to notify a user that they have outstanding orders with credit card purchases that are about to expire. | |||||
| IB-0009 | Invoicing and Billing (IB) | The ability to compare the invoiced amount with the award cost (e.g. contract schedule of prices). | |||||
| IB-0010 | Invoicing and Billing (IB) | Provide the ability for users to denote when an order is ready to be billed to a customer. | For example, Customer Services specialists should be able to trigger Finance to bill an agency for an order after they have confirmed that the price and all modifications have been entered (and before a contractor has sent an invoice). | ||||
| IB-0011 | Invoicing and Billing (IB) | Provide the ability for users to denote when an order’s invoice has been received from a contractor. | |||||
| IB-0012 | Invoicing and Billing (IB) | Provide the ability for users to denote when an order’s invoice has been paid to a contractor. | |||||
| IB-0013 | Invoicing and Billing (IB) | The system shall access agency billing contact information. | Provide GPO personnel with the ability to see agency financial contact information. Could be handled by EPIC or by GBIS. | ||||
| IB-0014 | Invoicing and Billing (IB) | Provide the ability to manage the invoice and billing process through workflow rules. | |||||
| IB-0015 | Invoicing and Billing (IB) | Provide the ability to send invoice and billing related notifications and alerts to users based upon workflow rules. | |||||
| OCS-0001 | Order and Content Submission (OCS) | The system shall allow simultaneous access to orders by multiple authorized users. | For example, this would allow two authorized users to access the order simultaneously. However, the user who accesses the order first can edit the order while the second user to access the order can only view. | ||||
| OCS-0002 | Order and Content Submission (OCS) | The system shall allow authorized users to assign orders to other users. | |||||
| OCS-0003 | Order and Content Submission (OCS) | The system shall provide the capability to notify a user that a order assignment has been completed. | |||||
| OCS-0004 | Order and Content Submission (OCS) | The system shall provide the capability to create common phrases used in specifications. | |||||
| OCS-0005 | Order and Content Submission (OCS) | The system shall provide the capability to enter common phrases used in specifications into orders. | |||||
| OCS-0006 | Order and Content Submission (OCS) | The system shall provide the capability to save common phrases used in specifications into orders. | |||||
| OCS-0007 | Order and Content Submission (OCS) | The system shall have the capability to notify customers that their order has been received. | |||||
| OCS-0008 | Order and Content Submission (OCS) | The system shall provide a means to add notes to each order. | Notes are meant to be captured during order processing while miscellaneous information about a order is captured at the order entry stage. | ||||
| OCS-0009 | Order and Content Submission (OCS) | The system shall provide a user interface for order entry. | |||||
| OCS-0010 | Order and Content Submission (OCS) | The system shall have the capability to track revisions to BPI for a order. | |||||
| OCS-0011 | Order and Content Submission (OCS) | The system shall create a new order version when BPI has been changed. | |||||
| OCS-0012 | Order and Content Submission (OCS) | The system shall timestamp a order version when it has been changed. | |||||
| OCS-0013 | Order and Content Submission (OCS) | The system shall provide the capability for users to enter BPI data for specific fields contained on the GPO jackets (red, black, brown, blue, supplemental). | Assumption: GPO is not getting rid of jackets. If getting rid of jackets, this requirement needs to change. | ||||
| OCS-0014 | Order and Content Submission (OCS) | The system shall provide the capability to store BPI data for specific fields contained on the GPO jackets (red, black, brown, blue, supplemental). | Assumption: GPO is not getting rid of jackets. If getting rid of jackets, this requirement needs to change. | ||||
| OCS-0015 | Order and Content Submission (OCS) | The system shall provide the capability for users to edit BPI data for specific fields contained on the GPO jackets (red, black, brown, blue, supplemental). | Assumption: GPO is not getting rid of jackets. If getting rid of jackets, this requirement needs to change. | ||||
| OCS-0016 | Order and Content Submission (OCS) | The system shall provide the capability for users to enter BPI data specific fields contained on the Standard Form 1. | The specific fields for the Standard Form 1 are available at: http://www.gpo.gov/forms/pdfs/sf1.pdf | ||||
| OCS-0017 | Order and Content Submission (OCS) | The system shall provide the capability to store BPI data specific fields contained on the Standard Form 1. | The specific fields for the Standard Form 1 are available at: http://www.gpo.gov/forms/pdfs/sf1.pdf | ||||
| OCS-0018 | Order and Content Submission (OCS) | The system shall provide the capability for users to edit BPI data specific fields contained on the Standard Form 1. | The specific fields for the Standard Form 1 are available at: http://www.gpo.gov/forms/pdfs/sf1.pdf | ||||
| OCS-0019 | Order and Content Submission (OCS) | The system shall provide the capability for users to enter BPI data specific fields contained on the GPO Form 2511. | The specific fields for the GPO Form 2511 are available at: http://www.gpo.gov/forms/pdfs/2511.pdf | ||||
| OCS-0020 | Order and Content Submission (OCS) | The system shall provide the capability to store BPI data specific fields contained on the GPO Form 2511. | The specific fields for the GPO Form 2511 are available at: http://www.gpo.gov/forms/pdfs/2511.pdf | ||||
| OCS-0021 | Order and Content Submission (OCS) | The system shall provide the capability for users to edit BPI data specific fields contained on the GPO Form 2511. | The specific fields for the GPO Form 2511 are available at: http://www.gpo.gov/forms/pdfs/2511.pdf | ||||
| OCS-0022 | Order and Content Submission (OCS) | The system shall provide the capability to store BPI data specific fields contained on GPO specifications. | Specification information can include elements such as paper, ink, size, general, product, proof, binding, quantity, and prepress data. | ||||
| OCS-0023 | Order and Content Submission (OCS) | The system shall provide the capability for users to enter BPI data specific fields contained on GPO specifications. | Specification information can include elements such as paper, ink, size, general, product, proof, binding, quantity, and prepress data. | ||||
| OCS-0024 | Order and Content Submission (OCS) | The system shall provide the capability for users to edit BPI data specific fields contained on GPO specifications. | Specification information can include elements such as paper, ink, size, general, product, proof, binding, quantity, and prepress data. | ||||
| OCS-0025 | Order and Content Submission (OCS) | The system shall have the capability for users to enter BPI that includes general information about a order. | General information can include elements such as title, agency, and quality level. | ||||
| OCS-0026 | Order and Content Submission (OCS) | The system shall store BPI that includes general information about a order. | General information can include elements such as title, agency, and quality level. | ||||
| OCS-0027 | Order and Content Submission (OCS) | The system shall provide the capability for users to edit BPI that includes general information about a order. | General information can include elements such as title, agency, and quality level. | ||||
| OCS-0028 | Order and Content Submission (OCS) | The system shall have the capability for users to enter BPI that includes billing information about a order. | Billing information can include elements such as Requisition Number and Billing Address Code. | ||||
| OCS-0029 | Order and Content Submission (OCS) | The system shall provide the capability to store BPI that includes billing information about a order. | Billing information can include elements such as Requisition Number and Billing Address Code. | ||||
| OCS-0030 | Order and Content Submission (OCS) | The system shall have the capability for users to edit BPI that includes billing information about a order. | Billing information can include elements such as Requisition Number and Billing Address Code. | ||||
| OCS-0031 | Order and Content Submission (OCS) | The system shall have the capability for users to enter BPI that includes estimating information about a order. | Estimating information can include elements such as Not to exceed, agency estimate, GPO estimate, surcharge, line of accounting, and discounts. | ||||
| OCS-0032 | Order and Content Submission (OCS) | The system shall provide the capability to store BPI that includes estimating information about a order. | Estimating information can include elements such as Not to exceed, agency estimate, GPO estimate, surcharge, line of accounting, and discounts. | ||||
| OCS-0033 | Order and Content Submission (OCS) | The system shall provide the capability for users to edit BPI that includes estimating information about a order. | Estimating information can include elements such as Not to exceed, agency estimate, GPO estimate, surcharge, line of accounting, and discounts. | ||||
| OCS-0034 | Order and Content Submission (OCS) | The system shall provide the capability for users to enter BPI that includes shipping and delivery specifications about a order. | This includes quantities, due dates, partial deliveries. This is for single or multiple addresses. | ||||
| OCS-0035 | Order and Content Submission (OCS) | The system shall provide the capability to store BPI that includes shipping and delivery specifications about a order. | This includes quantities, due dates, partial deliveries. This is for single or multiple addresses. | ||||
| OCS-0036 | Order and Content Submission (OCS) | The system shall provide the capability for users to edit BPI that includes shipping and delivery specifications about a order. | This includes quantities, due dates, partial deliveries. This is for single or multiple addresses. | ||||
| OCS-0037 | Order and Content Submission (OCS) | The system shall provide the capability for users to enter BPI that includes product specifications about a order. | |||||
| OCS-0038 | Order and Content Submission (OCS) | The system shall provide the capability to store BPI that includes product specifications about a order. | |||||
| OCS-0039 | Order and Content Submission (OCS) | The system shall provide the capability to edit BPI that includes product specifications about a order. | |||||
| OCS-0040 | Order and Content Submission (OCS) | The system shall provide the capability for users to enter BPI that includes prepress specifications about a order. | |||||
| OCS-0041 | Order and Content Submission (OCS) | The system shall provide the capability to store BPI that includes prepress specifications about a order. | |||||
| OCS-0042 | Order and Content Submission (OCS) | The system shall provide the capability for users to edit BPI that includes prepress specifications about a order. | |||||
| OCS-0043 | Order and Content Submission (OCS) | The system shall provide the capability for users to enter BPI that includes press specifications about a order. | |||||
| OCS-0044 | Order and Content Submission (OCS) | The system shall provide the capability to store BPI that includes press specifications about a order. | |||||
| OCS-0045 | Order and Content Submission (OCS) | The system shall provide the capability for users to edit BPI that includes press specifications about a order. | |||||
| OCS-0046 | Order and Content Submission (OCS) | The system shall provide the capability for users to enter BPI that includes bindery specifications about a order. | |||||
| OCS-0047 | Order and Content Submission (OCS) | The system shall provide the capability to store BPI that includes bindery specifications about a order. | |||||
| OCS-0048 | Order and Content Submission (OCS) | The system shall provide the capability for users to edit BPI that includes bindery specifications about a order. | |||||
| OCS-0049 | Order and Content Submission (OCS) | The system shall provide the capability for users to enter BPI that includes proof information about a order. | |||||
| OCS-0050 | Order and Content Submission (OCS) | The system shall provide the capability to store BPI that includes proof information about a order. | |||||
| OCS-0051 | Order and Content Submission (OCS) | The system shall provide the capability for users to edit BPI that includes proof information about a order. | |||||
| OCS-0052 | Order and Content Submission (OCS) | The system shall provide the capability for users to enter BPI that includes miscellaneous information about a order. | Miscellaneous information can include specification remarks specific to a particular area. Notes are meant to be captured during order processing while miscellaneous information about a order is captured at the order entry stage. | ||||
| OCS-0053 | Order and Content Submission (OCS) | The system shall provide the capability to store BPI that includes miscellaneous information about a order. | Miscellaneous information can include specification remarks specific to a particular area. Notes are meant to be captured during order processing while miscellaneous information about a order is captured at the order entry stage. | ||||
| OCS-0054 | Order and Content Submission (OCS) | The system shall provide the capability for users to edit BPI that includes miscellaneous information about a order. | Miscellaneous information can include specification remarks specific to a particular area. Notes are meant to be captured during order processing while miscellaneous information about a order is captured at the order entry stage. | ||||
| OCS-0055 | Order and Content Submission (OCS) | The system shall provide the capability for users to enter BPI that includes purchase order information about a order. | This requirement is meant to capture purchase order data that is generated by legacy systems (e.g. Oracle Inventory). It is not an interface to Oracle to exchange purchase order data, but rather provide the ability for users to enter in BPI data specific to purchase orders. | ||||
| OCS-0056 | Order and Content Submission (OCS) | The system shall provide the capability to store BPI that includes purchase order information about a order. | This requirement is meant to capture purchase order data that is generated by legacy systems (e.g. Oracle Inventory). It is not an interface to Oracle to exchange purchase order data, but rather provide the ability for users to enter in BPI data specific to purchase orders. | ||||
| OCS-0057 | Order and Content Submission (OCS) | The system shall provide the capability for users to edit BPI that includes purchase order information about a order. | This requirement is meant to capture purchase order data that is generated by legacy systems (e.g. Oracle Inventory). It is not an interface to Oracle to exchange purchase order data, but rather provide the ability for users to enter in BPI data specific to purchase orders. | ||||
| OCS-0058 | Order and Content Submission (OCS) | The system shall provide the capability for authorized users to manage business process information. | |||||
| OCS-0059 | Order and Content Submission (OCS) | The system shall have the capability for the system to denote mandatory BPI elements. | |||||
| OCS-0060 | Order and Content Submission (OCS) | The system shall have the capability to automatically save orders. | As it is being written. | ||||
| OCS-0061 | Order and Content Submission (OCS) | The system shall have the capability to store order information at any point in the order entry process. | Note: Mandatory elements do not have to be filled in order to be saved. | ||||
| OCS-0062 | Order and Content Submission (OCS) | The system shall have the capability to save orders. | |||||
| OCS-0063 | Order and Content Submission (OCS) | The system shall have the capability to save all BPI associated with a order. | |||||
| OCS-0064 | Order and Content Submission (OCS) | The system shall alert a user if mandatory elements are not entered. | Until the mandatory elements are entered, the order cannot proceed to the next step in the workflow. | ||||
| OCS-0065 | Order and Content Submission (OCS) | The system shall have the capability to retrieve an order. | For example, the retrieval could be accomplished by searching by a order identifier. | ||||
| OCS-0066 | Order and Content Submission (OCS) | The system shall have the capability to copy an order. | This is the copying of select BPI elements (elements TBS) of a order. It would be used to copy single orders to a template. | ||||
| OCS-0067 | Order and Content Submission (OCS) | The system shall have the capability to copy portions of a order. | This is the copying of select BPI elements (elements TBS) of a order. | ||||
| OCS-0068 | Order and Content Submission (OCS) | The system shall allow authorized users to enter BPI at any point in a workflow. | There are certain frields that shouldn't be able to enter/edit after certain events. Solicitation, Award, Bid Opening Date/Time, Etc. | ||||
| OCS-0069 | Order and Content Submission (OCS) | The system shall be capable of relating a order with multiple items. | Multiple items is different from strapping. Multiple items are on a single order. Strapping is multiple orders linked together. | ||||
| OCS-0070 | Order and Content Submission (OCS) | The system shall provide the capability for authorized users to cancel a order. | |||||
| OCS-0071 | Order and Content Submission (OCS) | The system shall provide the capability for authorized users to delete a order. | |||||
| OCS-0072 | Order and Content Submission (OCS) | The system shall be able to create order templates. | |||||
| OCS-0073 | Order and Content Submission (OCS) | The system shall be able to manage order templates. | |||||
| OCS-0074 | Order and Content Submission (OCS) | The system shall be able to create a new order from a order template. | |||||
| OCS-0075 | Order and Content Submission (OCS) | The system shall be capable of managing orders that are produced both in-house and procured. | This capability is for portions of orders that would be sub-contracted out. The system must be able to link the in-house order (black jacket) with the procured order (red jacket). | ||||
| OCS-0076 | Order and Content Submission (OCS) | The system shall allow users to enter BPI about portions of orders that have been procured. | This capability is for portions of orders that would be sub-contracted out. The system must be able to link the in-house order (black jacket) with the procured order (red jacket). | ||||
| OCS-0077 | Order and Content Submission (OCS) | The system shall be capable of displaying delivery information. | |||||
| OCS-0078 | Order and Content Submission (OCS) | The system shall have the capability to alert an authorized user that a new order has been created. |
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 .