Exhibit A OPTIS Grant Management System Requirements Master.xlsx
XLSX spreadsheet 25 KB Posted
- Attached to
- RFP SAIF Actuary Review
- Solicitation number
- S-16500-00011756
- Issued by
- Marion County, Oregon
About this file
This is an Exhibit A document containing the Grant Management System Requirements Master for the Oregon Department of Transportation (ODOT), outlining comprehensive functional and technical specifications for a Commercial-Off-the-Shelf (COTS) grant management system. The system must support ODOT's dual roles as both a federal grantee and state grantor, encompassing the complete grant lifecycle from funding opportunity identification through closeout. The requirements are organized into 30 major functional groups spanning system-wide capabilities, permissions and workflow management, data access, customization, user interface design, and support services. Key functional areas include advanced querying and reporting with dashboard views, role-based security with single sign-on integration, comprehensive grant tracking at multiple organizational levels, sub-recipient and vendor management, online application processing with customizable forms, and integration with federal systems such as SAM.gov and Grants.gov. The system must also support asset and work management capabilities, resource management including equipment and materials tracking, and financial integration with accounting and ERP systems. The platform must be fully cloud-hosted, accessible via standard web browsers, and permit multi-agency utilization with agency-specific configurations without affecting customization upgrades.
The document emphasizes that all configuration must be performable by agency staff without vendor involvement, and the system must support extensive customization of forms, workflows, reports, dashboards, and security parameters while maintaining compliance with federal grant management requirements including OMB financial reporting and FFR submission capabilities. Vendor support obligations include phone support as part of service level agreements, online manuals and release notes, in-person and online training, and user support forums. The requirements mandate support for electronic signatures, document management integration with platforms such as SharePoint and Google Docs, email notification and scheduling capabilities, and comprehensive audit trail functionality. Critical to sub-award management are capabilities for contract template creation, automated deadline reminders, progress report collection and analysis, payment integration with configurable approval workflows, and performance measurement against established goals, with the system designed to accommodate multiple spending and grant periods including single-year, multi-year, and state fiscal year reporting structures.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| SAIF Actuary Review RFP S-16500-00011756~2.pdf | ||
| RFPAttE Cost Proposal~3.xlsx | XLSX spreadsheet | |
| RFPAttD~3.docx | DOCX document | |
| Amendment 1 RFPAttE Cost Proposal.xlsx | XLSX spreadsheet | |
| RFPAttG~3.docx | DOCX document | |
| RFPAttB~3.docx | DOCX document | |
| RFPAttA Sample Contract for Actuary Review Services~1.docx | DOCX document | |
| RFPAttC~3.docx | DOCX document | |
| RFP s-16500-00011756 Amendment 1.pdf | ||
| RFPs-16500-00011756 Amendment 2.pdf | ||
| Intent_to_Award_SAIF_Actuary_Review 6-23-25.pdf |
Show all 11
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| Requirement Group | ID | Requirement Detail | |
| General System-Wide Requirements | |||
| System Querying and Reporting | 1.1 | Casual users can easily run queries and retrieve reports independently with minimal training. | |
| 1.2 | Ability to search or filter to find a particular set of grants based on various important fields such as status, federal award number, and funding agency. | ||
| 1.3 | Ability to make common updates to standard reports—for example, to change the columns displayed, or the grouping—to meet slightly different needs. | ||
| 1.4 | Ability to view favorite reports, actions, or queries without searching/navigating a large result set. | ||
| 1.5 | Ability for users to name and save newly created reports. | ||
| 1.6 | Supports user creation of ad hoc reports within the system including any field displayed to users, custom data columns, sorting, grouping, logos, and headers. | ||
| 1.7 | Virtually all system data—including data entered into online applications, review forms, and sub-recipient progress reports—can be included in reports. | ||
| 1.8 | Allows drill down on reports. | ||
| 1.9 | Ability to search within attached documents. | ||
| 1.10 | System contains industry-standard reporting templates. | ||
| 1.11 | Reports can be set to automatically run and send to individuals or groups. | ||
| 1.12 | Report support visual graphic representations—e.g., charts or graphs. | ||
| 1.13 | Provides pre-defined “dashboard” views that summarize the grants currently relevant to each individual user. | ||
| 1.14 | Provide a department wide sub-recipient/vendor repository that contains grant funding history. | ||
| 1.15 | Ability for the agency, sub-recipients and/or vendors to print a final report. | ||
| 1.16 | Ability to define a standard visual dashboard of the grant lifecycle milestones and alerts that can be customized by agency. | ||
| 1.17 | Ability to report, sort, and query on any field. | ||
| 1.18 | Reports must be able to support graphics such as attachments, graphs, charts, logos, and watermarks. | ||
| 1.19 | Provides a user-friendly report writer that does not require vendor or technical assistance. | ||
| 1.20 | Reports must be able to be printed our exported into various file formats such as .pdf, .csv, .doc, .xls, etc. | ||
| Permissions and Workflow | 2.1 | Ability to grant individuals access to granularly view, edit, or delete data for a wide variety of system functions. | |
| 2.2 | Ability to provide a role-specific internal interface for each role in the system. | ||
| 2.3 | Records most data updates, along with the data and the user who made the update, in an audit log. | ||
| 2.4 | Provides “dashboard” views that only display information that the user has permissions to access. | ||
| 2.5 | Provides users a “task list” when they sign onto the system. | ||
| 2.6 | Ability to assign tasks, such as reviews, to other users. | ||
| 2.7 | Ability to provide a focused, roles-based view for management via dashboards and role definitions. | ||
| 2.8 | Assigns tasks to users based on security permissions. | ||
| 2.9 | System provides role-based data security, task lists, and email reminders. | ||
| 2.10 | Supports single sign-on capability with AD & LDAP. | ||
| 2.11 | Supports the ability to integrate with electronic signature systems. | ||
| 2.12 | Provide workflow capabilities and dashboard tracking for key activities within the federal grant lifecycle. | ||
| 2.13 | Ability for administrators to view, sort and organize submissions. | ||
| 2.14 | Supports electronic approvals. | ||
| 2.15 | Ability to delegate authority to another user to approve or take other actions on a workflow item or task. | ||
| 2.16 | Ability to inactivate any user in the system. | ||
| Data Access | 3.1 | Allows export of all data visible to users into another file format, such as .xls or .csv. | |
| 3.2 | Allows a programmer to create custom data flows to an external system. | ||
| 3.3 | Ability to import grants current and historical data from various formats including spreadsheets and databases. | ||
| 3.4 | Data is secure and encrypted at rest and when data travels to and from the database via network connections using Advanced Encryption Standard (AES) (up to 256-bit keys), Triple Data Encryption Standard (DES), and RC4 encryption. | ||
| Overall Customization | 4.1 | Ability to customize online forms including file uploads, drop down lists, checkboxes, and text fields. | |
| 4.2 | System includes character and word counts for application questions, and an administrator can set and adjust character limit for any field. | ||
| 4.3 | System includes in-system editable help text for customizable fields created. | ||
| 4.4 | Allows customized dropdown values for fields. | ||
| 4.5 | Allows custom fields throughout the system. | ||
| 4.6 | Allows custom “internal tracking” fields for staff use only. | ||
| 4.7 | Allows customization of the information requested in online forms. | ||
| 4.8 | Fields may be marked as required. | ||
| 4.9 | Labels and field order are fully customizable. | ||
| 4.10 | Vendor permits customized systems to remain on the upgrade path, and ensures that enhancements don’t affect customizations. | ||
| 4.11 | Ability to define custom language sets for public-facing forms. | ||
| 4.12 | All configuration can be performed by the staff without involvement from the vendor. | ||
| Ease of Use | 5.1 | User interface is polished, organized, and intuitive. | |
| 5.2 | Navigation and action items are labeled intuitively. | ||
| 5.3 | On the core interface pages, the user can easily find the actions they would most likely take. | ||
| 5.4 | System groups information and actions an expert user is likely to need. | ||
| Support and Training | 6.1 | Vendor provides phone support included in as part of the SLA. | |
| 6.2 | Manuals and release notes are available online. | ||
| 6.3 | Vendor provides in person and online training. | ||
| 6.4 | User support forums or discussion groups are available. | ||
| Installation and Maintenance | 7.1 | System is fully hosted and cloud-based accessible from any major web browser. | |
| 7.2 | Ability to export all system data into CSV and PDF format. | ||
| 7.3 | System must be a Commerical-Off-the-Shelf (COTS) solution. | ||
| 7.4 | Ability to support multiple agencies utilizing the same instance of the system. | ||
| 7.5 | Ability to have agency specific configurations within the same instance of the system including workflows, reports, dashboards, forms, and security. | ||
| Letters/ | |||
| Documents | 8.1 | Ability to create custom forms for printing including the ability to choose which fields to include, as well as customizing fonts, colors, and logos. | |
| 8.2 | Ability to create letter templates in Microsoft Word that include mail-merged information about grants and organizations, and lets you customize their fonts, colors, and logos. | ||
| 8.3 | Electronic signatures on letters and other documents supported with an integration. | ||
| 8.4 | All letters and documents can be exported out of the system to Word, Excel, or PDF. | ||
| Emails | 9.1 | Supports spell checking within the system. | |
| 9.2 | Ability to create email to individuals and groups based on templates that include both standard text and “mail-merge” type inserted data. | ||
| 9.3 | Allows file attachments to emails sent to individuals and groups. | ||
| 9.4 | Ability to set up event-triggered emails. | ||
| 9.5 | Ability to set up and send scheduled reminder emails to applicants and sub-recipients. | ||
| Integration | 10.1 | Supports integration with enterprise systems including financial and ERP systems. | |
| 10.2 | Integrates with SAM.gov and Grants.gov. | ||
| 10.3 | Ability to integrate with a Document Storage client file server such as SharePoint, Google Docs, or other document storage application. | ||
| 10.4 | Ability to integrate with federal agencies grant management systems, payment systems and reporting systems /websites. | ||
| Collaboration | 11.1 | Ability to collaborate across multiple teams using social media tools. | |
| 11.2 | Ability to upload documents (Word, Excel, PDF) to support the grant management lifecycle. | ||
| 11.3 | Supports creating, assigning, and tracking tasks. | ||
| 11.4 | Supports calendar sharing and scheduling. | ||
| 11.5 | Provides a dashboard with messages, tasks, workflow items, and other pre-defined performance measures. | ||
| ODOT as a Grantee | |||
| Registration | 12.1 | New user registration. | |
| 12.2 | Department user and organizational profile creation and maintenance. | ||
| 12.3 | Ability to allow multiple users to register to work on a single application. | ||
| Funding Opportunity | 13.1 | Ability to provide a searchable repository to identify grant opportunities by keyword. | |
| 13.2 | View multiple Funding Opportunity Announcements (FOAs) and recent updates. | ||
| 13.3 | Search across grant announcements from external services such as Grants.gov and foundations. | ||
| 13.4 | Review/rate FOAs and collaborate on pursuit decision making and next steps. | ||
| 13.5 | Ability to schedule automated application due date reminder email notifications. | ||
| 13.6 | Internal FOA review and formal approval process prior to opportunity pursuit. | ||
| 13.7 | Track all historic opportunity data such as past funding information, grant performance measures, prior vendors, attachments, success rate with the federal agency for a specific program, etc. | ||
| Applications | 14.1 | Complete, review, approve, and store applications directly in the system. | |
| 14.2 | Ability to create, store, and update budget spreadsheets that meet the level of detail required for federal grant submissions. | ||
| 14.3 | Ability to attach artifacts e.g., Word, PDF, Excel, etc. to grant application. | ||
| 14.4 | Define multi-level workflow for the application to support the review and approval processes. | ||
| 14.5 | Maintain historic application repository including version control. | ||
| 14.6 | Display all federal grants that are in the application process across all the department. | ||
| Award Management | 15.1 | Ability to manage and report on grants at the multiple levels including department, project, grant, and sub-award. | |
| 15.2 | Ability to support the federal grants spending and project periods including: |
• Single year spending and grant period
• Multi-year spending and grant period
• Multiple spending periods within a grant period
• State fiscal year reporting
| 15.3 | Ability to interface with accounting systems to track expenses, collections, and payments. | |
| 15.4 | Ability to identify match for a grant and determine if match requirements are met including third party match. | |
| 15.4 | Ability to track indirect cost and determine if appropriate amount is being reimbursed. | |
| 15.6 | Ability to manage grant award amendments. | |
| 15.7 | Ability to track tasks and milestones for a grant. | |
| 15.8 | Ability to monitor grant spending against budget. | |
| 15.9 | Upload all documents required for the grant set-up as they are received including award letters, amendments, internal documents, etc. | |
| 15.10 | Grant management system sub-recipients and vendors are alerted to provide interim or final reports and then submit the reports via the system. | |
| 15.11 | Ability to generate federal OMB financial reports (e.g. FFR, FFATA). | |
| 15.12 | Ability to create an audit trail of actions taken on a grant. | |
| 15.13 | Ability to track vendor contracts including deliverables, terms, progress, and payments. | |
| 15.14 | Ability to support creating and maintaining grant project schedules including key grant dates as well as project dates (site visits, reporting dates, etc.). | |
| 15.15 | Ability to interface with federal system to initiate a draw down or funds reimbursement. | |
| 15.16 | Ability to track draw downs. | |
| 15.17 | Ability to produce federal reports to request reimbursement (e.g. SF-270). | |
| 15.18 | Ability to create custom forms to request payments. | |
| 15.19 | Ability to update the Approved Budget in response to an approved budget re-direction request. | |
| 15.20 | Ability to provide managers list of key grant dates across all the grants under their management. | |
| 15.21 | Ability to revise the grant application budget to an approved budget in response to creating a grant award. | |
| 15.22 | Ability to update the Approved Budget in response to an approved budget re-direction request. | |
| Post-Award Reports | 16.1 | Create federal financial and performance reports. |
| 16.2 | Aggregate and finalize reports to the federal government. | |
| 16.3 | Manage program level budgets and programmatic impact. | |
| Close Out | 17.1 | Create grant close out documents including final financial and performance reports per task-based checklist with workflow capability and notifications. |
| 17.2 | Measure performance and financial outcomes. | |
| ODOT as a Grantor | ||
| Applicant Registration | 18.1 | System registration follows standard best practices—applicants enter email address and password and are sent a confirmation email. |
| 18.2 | System checks the email address of each new registrant to make sure it doesn’t already exist in the system and prompts the registrant if there is a match. | |
| 18.4 | System creates a profile for each sub-recipient based on registration information and other information desired by the department. | |
| 18.5 | Ability for sub-recipients to maintain profile information online. | |
| 18.6 | Supports multiple logins for sub-recipients on a single application—for example, allows separate people to complete financial sections and proposal sections. | |
| 18.7 | Sub-recipient organization profile can be automatically populated with information from the IRS by entering the EIN number. | |
| 18.8 | Both applicant and grantmaker can quickly and easily reset lost credentials via self-service tools. | |
| Internal Tracking | 19.1 | All information for each grant is linked together through its entire lifecycle from the federal award to the sub-awards and vendor contracts. |
| 19.2 | Ability to retrieve grant information and status. | |
| 19.3 | Track by categories, such as geographic, population-based budget, or project codes, and by percentage or dollar allocations. | |
| 19.4 | Split grants across different categories/codes. | |
| 19.5 | Define custom categorization codes for tracking and reporting. | |
| 19.6 | Ability to update basic grant information like project names or codes throughout the process. | |
| 19.7 | Attach files to grant records, including Word documents, Excel spreadsheets, and PDFs. | |
| 19.8 | Paper applications can be easily entered into the system and attached to existing users. | |
| 19.9 | System uploads attached documents to the server and stores a link to that uploaded file in the database. | |
| 19.10 | Batch data updates of defined coding and other fields is supported. | |
| 19.11 | Ability to see related records and data across records. | |
| 19.12 | Ability to report on all changes made by a sub-recipient over a specified timeframe. | |
| Online Applications | 20.1 | Ability to create new online applications file uploads, dropdown boxes, checkboxes, and text fields, without additional charges from the vendor. |
| 20.2 | Ability to create different online forms to support each grant program. | |
| 20.3 | Ability to format applications—for example, use rich text, create groups of questions, and create multiple pages. | |
| 20.4 | Grant application forms can "branch"—for example, to show a different set of questions based on specific criteria. | |
| 20.5 | System allows both individuals and organizations to apply for grants from the same grant program. | |
| 20.6 | System does not allow more than one application from an entity for an award. | |
| 20.7 | Receive grant applications and proposals in electronic format. | |
| 20.8 | Eligibility quizzes can "branch" (stored and reused) to multiple applications. | |
| 20.9 | Supports multiple application stages, including eligibility quizzes. | |
| 20.10 | Applicants can save partially completed applications and return to them later. | |
| 20.11 | Ability for the sub-recipient or applicant to transfer their account and history to a new staff contact. | |
| 20.12 | Applicants can view their status online. | |
| 20.13 | Applicants can easily view or print applications at any stage in the process. | |
| 20.14 | Applicant can create a preview packet of their grant which includes either copies of all uploaded documents or links to them. | |
| 20.15 | Offers a full virus scan feature to prevent malicious files from being uploaded onto the application. | |
| 20.16 | Allows for applicants or sub-recipients to manage all grant information for all of their funders in the system. | |
| 20.17 | Provide a workflow with checkpoints to ensure that all documents are provided. | |
| 20.18 | Provide templates and forms to sub-recipients and vendors to control responses and material submitted. | |
| Application Review | 22.1 | Provides history of a relationship with prospective sub-recipients such as past communications, applications completed, applications declined or awarded across the department. |
| 22.2 | Supports checklist functionality to define what information or documents are required from prospective sub-recipients. | |
| 22.3 | Ability for reviewers to print grant summaries or full grant information. | |
| 22.4 | Provides an interface to allow reviewers to view, review, and score grant applications. | |
| 22.5 | Allows reviewers to view uploaded documents associated with the application. | |
| 22.6 | Ability for users to define automatic workflows to support grants review process. | |
| 22.7 | Ability for multiple reviewers to evaluate and score an application on a number of different factors and add comments. | |
| 22.8 | Supports different information or scoring schemes for different programs. | |
| 22.9 | Provides numeric review scores with ability and report summary statistics. | |
| 22.10 | Ability to choose whether to allow reviewers to see each other’s comments and scores. | |
| 22.11 | Ability to choose whether to allow applicants to see the reviewers' comments. | |
| 22.12 | Ability for agency staff to view applications and reviewer comments. | |
| 22.13 | Ability to notify applicant the status of the applications - approved or denied. | |
| 22.14 | Ability to notify applicant and grants management staff when reviews are completed, either via email or internal message, or both. | |
| Client Relationship | 23.1 | Allows multiple individuals on online forms with ability to track contact status. |
| 23.2 | Tracks organizations separately from individual grants to allow you to see a history of all grants to an organization. | |
| 23.3 | Ability to send email to any contact recorded in an application form. | |
| 23.4 | Ability to associate multiple contacts with an organization and define their relationships. | |
| 23.5 | Ability to log outside communications, such as phone calls and emails, with a particular contact at a grantee organization. | |
| 23.6 | Ability to store a record of all system-generated letters and emails for each grant. | |
| 23.7 | Ability to capture emails from an external email system. | |
| 23.8 | System allows you to automatically export system contacts. | |
| 23.9 | Ability to create a risk assessment template for sub-recipients containing various fields of varying field types for data collection. | |
| 23.10 | Ability to capture risk assessment for sub-recipients at the time of application and periodically thereafter, and provide a monitoring plan that is visible to the department. | |
| 23.11 | Allows scheduling, tracking, and documenting of sub-recipient monitoring activities (e.g. desk reviews, onsite visits, training, etc.) with workflow and e-mail notifications. | |
| 23.12 | Ability to track findings, issues, and concerns from a desk review. | |
| 23.13 | Allow sub-recipients to submit resolutions/responses to desk review action items online. | |
| Sub-award Management | 24.1 | Ability to create a contract template with standard language. |
| 24.2 | Ability to create and maintain standard language for individual contract terms and conditions. | |
| 24.3 | Ability to generate a contract using the template and selecting specific pre-defined terms and conditions relevant to the grant. | |
| 24.4 | Workflow to route contract for review and approval. | |
| 24.5 | Ability to associate documents as part of an award package for distribution or download/printing. | |
| 24.6 | Ability to track where grant funding is disbursed by zip code. | |
| 24.7 | Ability to define a default set of grant requirements and customize them for individual sub-awards. | |
| 24.8 | Ability to “branch” (store and reuse) data collection based on grant type. | |
| 24.9 | Sub-recipients can view grant requirement deadlines online. | |
| 24.10 | Ability to report on performance measures against goals using submitted progress reports. | |
| 24.11 | Ability to view which requirements sub-recipients have met and which they have not. | |
| 24.12 | Automatically email sub-recipients to remind them about upcoming deadlines using email templates. | |
| 24.13 | Track the receipt of progress reports and approval by internal staff. | |
| 24.14 | Store progress report information submitted by sub-recipients to allow summarization across many sub-recipients. | |
| 24.15 | Submit progress report information through online data fields. | |
| 24.16 | Ability to create custom online progress report forms specific to the grant. | |
| 24.17 | Ability to configure a template of performance measures to collect data based on grant program. | |
| 24.18 | Allows staff to define performance goals by program and for individual grants, and automatically measures progress toward those goals using submitted progress reports. | |
| Payments | 25.1 | Ability to integrate with the accounting system for payments. |
| 25.2 | Ability to generate a custom form request for accounting. | |
| 25.3 | Ability to view payments that are due based on a schedule and whether the sub-recipient has met the associated prerequisite requirements. | |
| 25.4 | Supports an automated payment approval process with configurable workflow steps. | |
| 25.5 | Allows for payments to be made contingent or conditional upon a specified grant or payment requirement. | |
| 25.6 | Allows configuration of audit/security controls to ensure that only certain staff can change payment information. | |
| 25.7 | System provides the ability to include notes on payments. | |
| Budgeting | 26.1 | Create budgets by grant year (project period and budget period), state fiscal year, and the total amount awarded. |
| 26.2 | Track budgets against spending by grant year (project period and budget period), state fiscal year, and the total amount awarded. | |
| 26.3 | Allow budgets to be summarized by defined categories or programs. | |
| 26.4 | Allows use previous years’ budgets as a base with ability to and adjust them for current year. | |
| 26.5 | Split grants across more than one program for budgeting and payment-tracking purposes. | |
| 26.6 | Ability to set up multi-year budgets. | |
| 26.7 | Ability to revise the contract budget per approved re-direction request | |
| 26.8 | Ability to create a process for requesting budget re-direction, with configurable review and approval hierarchy. | |
| ODOT and Asset Management | ||
| Asset Management | 27.1 | Ability to move assets from one location to another |
| 27.2 | Ability to set up Preventative Maintenance plans for any asset. Plans must be able to be created based on time, condition or a combination of both. | |
| 27.3 | Configurable performance curves must be available for every asset in an easy to use graphical interface. | |
| 27.4 | Standard and configurable inspection capability for every asset with weighted condition categories can be utilized. | |
| 27.5 | Each asset should have the capability to view historic work, broken down by completed, in-progress or planned work status. | |
| 27.6 | Work activities must be able to be configured for any type of asset. | |
| 27.7 | Every asset type can have their own configurable attributes that can be tracked. | |
| 27.8 | Ability to see a roll up cost of every work activity performed against an asset. | |
| 27.9 | Ability to view an estimated overall condition index (OCI) for every asset that automatically calculates. | |
| 27.10 | Every asset should allow for various attachment file formats to be associated to asset record. | |
| 27.11 | Ability to create configured, non-standard assets with little or no vendor assistance. | |
| 27.12 | Ability for assets to be linked to other assets (sign to a support for example) | |
| Work Management | 28.1 | Ability to create work on assets and non-assets. |
| 28.2 | Ability to create non-asset work without a location being required. | |
| 28.3 | Ability to group multiple tasks together for cost and progress-level tracking. | |
| 28.4 | Ability to assign a priority to work. | |
| 28.5 | Intuitive work creation wizard that steps the user through the process. | |
| 28.6 | Ability to assign work to an individual or multiple laborers and or crews. | |
| 28.7 | Email notifications when new work has been assigned to a laborer. | |
| 28.8 | Ability to reassign work from one laborer to another based on permissions. | |
| 28.9 | Ability to receive email notification upon work completion or cancelation. | |
| 28.10 | Ability to manage work tasks and work orders. | |
| 28.11 | Ability to create work orders with multiple tasks associated to it and roll up cost capability. | |
| 29.12 | System must have capability to manually or automatically calculate estimated activity costs. These costs should be easily comparable to actual costs. | |
| Resource Management | 30.1 | Equipment/vehicles can be tracked in time or distance (miles, kilometers) for usage. |
| 30.2 | Preventative maintenance plans can be created for equipment based on time, condition or a combination of both. | |
| 30.3 | Vehicle Replacement Ratings (VRR) can be associated to vehicles to assist in determining when vehicle is nearing the end of useful life. | |
| 30.4 | Labor, Equipment and Materials can be associated to any work activity with costing information automatically calculated. | |
| 30.5 | Materials can be inventoried and quantity automatically deducted from inventory when consumed. | |
| 30.6 | Ability to establish inventory consumption methodology in either LIFO, FIFO, Most Expensive or Least Expensive first. | |
| 30.7 | Ability to establish re-order point and amount to re-order with email notifications when threshold is met. | |
| 30.8 | Labor, Equipment and Materials should be available via pick lists when entering against a work activity. | |
| 30.9 | System must support the ability to multiple laborers, equipment and materials to multiple work records at the same time. | |
| 30.10 | System must support the use of multiple warehouse locations, including mobile warehouses. | |
| 30.11 | System must support the ability to transfer materials from one location to another. | |
| 30.12 | System must have the ability to order materials and restock to inventory when they arrive. |
_x000D_&1#&"Calibri"&10&K000000 Level 3 - Restricted
File details come from the government source that posted it. Updated .