VBMS Scoring TEMPLATE- STANDARD.xlsx
XLSX spreadsheet 41 KB Posted
- Attached to
- Veterans Benefit Mngmnt System DVA
- Solicitation number
- 27-448DOIT-APP44-B-53273
- Issued by
- Illinois
About this file
This is a scoring template document used by the Illinois Department of Innovation and Technology on behalf of the Department of Veterans Affairs for evaluating proposals related to the Veterans Benefit Management System (VBMS). The template establishes a standardized evaluation framework for assessing vendor responses to this solicitation. The document provides the scoring methodology and criteria that will be applied during the proposal evaluation process to determine which bidder will be selected for award of the contract. The template outlines the specific evaluation categories, point allocations, and scoring ranges that evaluators must use when reviewing submitted proposals.
The scoring template serves as the administrative tool to ensure consistency and objectivity in the evaluation of all bidder submissions. This standardized approach allows the Department of Innovation and Technology and Department of Veterans Affairs to fairly compare competing proposals against the same criteria and point values, facilitating the selection of the vendor best qualified to deliver the Veterans Benefit Management System. The template does not contain specific pricing information, contract terms, or other substantive solicitation details, but rather functions as the evaluation instrument to be applied once proposals are received from interested vendors.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| VBMS Master Evaluation Roll Up.xlsx | XLSX spreadsheet | |
| Exhibit 2- 4WVGR.pdf | ||
| Attachment C- Minimum Service Level Agreement ~1.xlsx | XLSX spreadsheet | |
| Attachment B- Experience~1.docx | DOCX document | |
| Vendor Disclosure formerly Forms A~1.docx | DOCX document | |
| Exhibit 3- Reports.pdf | ||
| Attachment D- State of Illinois Standard Security Requirements~1.pdf | ||
| C2D vendor-guidance~1.pdf | ||
| B-53273 VBMS RFP Final.docx | DOCX document | |
| C2D vendor-answer-sheet~1.pdf | ||
| B-53273 BEP Utilization Plan v.26.1.pdf | ||
| IPG Active Vendor Disclosure formerly Forms B~1.docx | DOCX document | |
| Information and Techology Offer to the State~1.pdf | ||
| Exhibit 1- 3WVGR.pdf | ||
| Attachment A- DoIT Cloud Hosting Appendix~2.pdf |
Show all 15
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
Worksheet Information
STATE OF ILLINOIS
Worksheet Information
| Tabs in this Worksheet | |
| Worksheet Information | This tab includes the information about the contents of this worksheet. |
| Mandatory Requirements with Evidence | Contains Requirments that a offeror must meet. This section requires the offeor to show they can meet this criteria. Comments should be added to show the vendor has me this need or has not met it. |
| Desirable Criteria Tab | Contains Desirable Criteria the Department has identified and their related data. Offerors shall notify the Department of Desirable Criteria Offeror believes should have been included and may add Functional Criteria at the bottom of the next tab as needed to completely document the functionality of Offeror's proposed Solution. The Department encourages innovation, this is one method for Offerors to highlight their proposed Solution's innovation. |
| Columns in the Mandatory With Evidence Tab | |
| Criteria ID | Assigned # to track the Criteria. |
| Description | This is a description of the Criteria. |
| Met? | Yes or No drop down to indicate if the offeror meets the criteria. |
| Evaluator Comments | Any notes or comments for the evaluator to justify applied Evaluator Rating and Score. |
| Columns in the Desirable Criteria Tab | |
| Criteria ID # | Assigned # to track the Criteria. |
| Criteria Description | This is a description of the Criteria. |
| Quality Rating | Evaluator's quality assessment rating chosen from a drop down value. Values are from No Value (0%) to Excellent - Above and Beyond (100%) sourced from the Point Breakdown Tab. |
| Evaluator Score | Calculated score for the evaluator's self assessment (Quality Rating) |
| Evaluator Comments | Any notes or comments for the evaluator to justify applied Evaluator Rating and Score. |
DCFS PO19-164 CCWIS Attachment D Functional Criteria Page &P of &N
Mandatories W Evidence
| ID# | Mandatory Requirement with Evidence | Met? | Comments |
| F.2.1 | Offeror, or Offeror’s team, must have experience hosting and providing maintenance and support of the proposed Solution for at least two (2) government customers. | ||
| F.2.2 | Offeror Project Manager must have at least two (2) years’ experience leading the implementation of systems similar to the proposed Solution. | ||
| F.2.3 | Offeror Solution must be capable of interfacing with the State of Illinois’ identity and access management solution, Okta, via the Security Assertion Markup Language (SAML) or OpenID Connect (OIDC) open standards. | ||
| F.2.4 | Offer shall submit a Statement of work with their proposal. This SOW may be negotiated with the awarded vendor. |
Desirable Criteria
| DESIRABLE CRITERIA | EVALUTION | ||||
| Criteria ID# | Criteria Description | Max Score | Quality | ||
| Rating | Evaluator Score | Evaluator's Comments - must justify applied Evaluator Rating and Score. | |||
| F.3.1 | Executive summary of proposed services including approach, methodology, staffing, work plan, milestones, and offeror contact information. | 2 | 2.00 | ||
| F.3.2 | F.3.2 | Summary of required offeror experience, including two relevant past projects and narrative on relevance, issues, lessons learned, readiness, and regulatory familiarity. | 2 | 2.00 | ||
| F.3.3 | F.3.3 | Summary of subcontractor experience requirements, including two relevant examples, narrative details, restrictions on subcontractor changes, and quality expectations. | 2 | 2.00 | ||
| F.3.4 | F.3.4 | System supports full integration with VA systems, including VBMS, VA APIs, claim status retrieval, and resubmission with submission history. | 21 | 21.00 | ||
| F.3.5 | F.3.5 | System supports uploading and submitting VA forms and documents, additional submissions, and storing historical submissions. | 21 | 21.00 | ||
| F.3.6 | F.3.6 | System manages digital documents with metadata linking, previewing, missing‑document alerts, and completeness validation. | 9 | 9.00 | ||
| F.3.7 | F.3.7 | System supports form auto‑population, schema compliance, validation rules, required‑field enforcement, and veteran master records. | 9 | 9.00 | ||
| F.3.8 | F.3.8 | System ensures accuracy and visibility in claim lifecycle with real‑time status, history tracking, required evidence display, and missing‑data warnings. | 10 | 10.00 | ||
| F.3.9 | F.3.9 | Full digital claims processing: multiple claim types, creation through appeals, document versioning, letters, and workflow support. | 9 | 9.00 | ||
| F.3.10 | F.3.10 | User account and hierarchy management including supervisor assignment, effective‑date tracking, and organizational structure setup. | 10 | 10.00 | ||
| F.3.11 | F.3.11 | Support for team creation and management, including team types, assignments, and performance visibility. | 9 | 9.00 | ||
| F.3.12 | F.3.12 | User identity options including aliases/short codes with audit history and display across workflows. | 8 | 8.00 | ||
| F.3.13 | F.3.13 | User lifecycle management including creation, updates, deactivation, permissions tracking, and full audit history. | 10 | 10.00 | ||
| F.3.14 | F.3.14 | End‑to‑end client case lifecycle including intake, screening, claims, appeals, issue tracking, and performance indicators. | 10 | 10.00 | ||
| F.3.15 | F.3.15 | Structured workflow routing including task assignment, queues, notifications, workload balancing, next steps, and audit logging. | 10 | 10.00 | ||
| F.3.16 | F.3.16 | Notes and communication management including timestamped notes, client/claim separation, interaction history, and spell‑check. | 10 | 10.00 | ||
| F.3.17 | F.3.17 | Alerts and reminders including recurring reminders, deadline warnings, role‑specific alerts, escalation, and overdue‑task detection. | 10 | 10.00 | ||
| F.3.18 | F.3.18 | Calendar and event tracking including linking reminders to calendars, tracking hearings/meetings, and permission‑based visibility. | 10 | 10.00 | ||
| F.3.19 | F.3.19 | Notification capabilities including task and claim alerts, VA contact alerts, submission notifications, and multi‑channel delivery. | 10 | 10.00 | ||
| F.3.20 | F.3.20 | Claim decision and rating tracking including issues, combined rating history, awards, adjustments, and linkage to outcomes. | 10 | 10.00 | ||
| F.3.21 | F.3.21 | Eligibility and presumptive‑condition support using service history, presumptive logic, and cross‑referencing eligibility rules. | 10 | 10.00 | ||
| F.3.22 | F.3.22 | Financial data management including income calculations, financial info storage, payment history, and export options. | 5 | 5.00 | ||
| F.3.23 | F.3.23 | Specialized case types and state‑program integration including adaptive housing, property tax, and prerequisite checks. | 7 | 7.00 | ||
| F.3.24 | F.3.24 | Letter generation and communication management including templates, electronic/printed delivery, newsletters, and versioning. | 10 | 10.00 | ||
| F.3.25 | F.3.25 | Data accuracy and correction features including error correction with audit trails, date/value warnings, master records, and validation rules. | 10 | 10.00 | ||
| F.3.26 | F.3.26 | Document upload and storage with support for multiple formats, bulk scanning, metadata routing, and previewing. | 10 | 10.00 | ||
| F.3.27 | F.3.27 | Document versioning including timestamps, edit history, restoration of prior versions, and version control for forms and templates. | 10 | 10.00 | ||
| F.3.28 | F.3.28 | VA forms support including auto‑population, up‑to‑date library, field validation, record requests, and data migration to new forms. | 17 | 17.00 | ||
| F.3.29 | F.3.29 | Template and letter management including creation, updates, imports, storage, and versioning. | 10 | 10.00 | ||
| F.3.30 | F.3.30 | Structured form configuration including required‑field indicators, inline help, and customizable cheat sheets. | 7 | 7.00 | ||
| F.3.31 | F.3.31 | Documentation readiness including missing‑document alerts, documentation requirements display, validation errors, and signature workflows. | 10 | 10.00 | ||
| F.3.32 | F.3.32 | Scanned‑image management with secure storage, metadata, audit history, and export options. | 10 | 10.00 | ||
| F.3.33 | F.3.33 | Comprehensive search including multiple identifiers, claim attributes, classifications, full client view, and dependent searches. | 10 | 10.00 | ||
| F.3.34 | F.3.34 | Advanced reporting including predefined reports, supervisor/field reporting, program reporting, and multi‑level metrics. | 10 | 10.00 | ||
| F.3.35 | F.3.35 | Ad hoc reporting including custom queries, export formats, scheduling, and replication/processing requirements. | 7 | 7.00 | ||
| F.3.36 | F.3.36 | Structured data import/export including CSV/XML/JSON imports, validation, permissions, and tracked activity logs. | 10 | 10.00 | ||
| F.3.37 | F.3.37 | Export/download security with role‑based controls, restricted downloads, audit logs, and printable summaries. | 10 | 10.00 | ||
| F.3.38 | F.3.38 | Long‑term data management and archiving including workflows, version history, and data dictionary maintenance. | 10 | 10.00 | ||
| F.3.39 | F.3.39 | Task management including creation, assignment, to‑do lists, reassignments, filtering, and exporting task lists. | 7 | 7.00 | ||
| F.3.40 | F.3.40 | Full accessibility compliance including screen readers, keyboard navigation, high contrast, ARIA support, and WCAG 2.1 AA compliance. | 10 | 10.00 | ||
| F.3.41 | F.3.41 | Multilingual support including compatibility with Weglot, translation coverage, UI exposure, formatting preservation, and scalability. | 7 | 7.00 | ||
| F.3.42 | F.3.42 | Cloud‑based SaaS hosting with FedRAMP Moderate compliance, scalability, performance, unified UI, safeguards, and multi‑monitor support. | 10 | 10.00 | ||
| F.3.43 | F.3.43 | Delivery of required software components including utilities, tools, version control, licensing documentation, and virtual environment support. | 10 | 10.00 | ||
| F.3.44 | F.3.44 | Complete module integration with real‑time synchronization, consistency enforcement, and safe concurrent updates. | 10 | 10.00 | ||
| F.3.45 | F.3.45 | System stability, disaster recovery, and continuity including multiple environments, DR plans, backups, and auditable recovery logs. | 10 | 10.00 | ||
| F.3.46 | F.3.46 | Update and maintainability framework including automatic updates, preservation of customizations, compatibility support, and change‑management documentation. | 10 | 10.00 | ||
| F.3.47 | F.3.47 | Security compliance with NIST, VA standards, encryption, and protections for PII/PHI/CJIS data. | 10 | 10.00 | ||
| F.3.48 | F.3.48 | Authentication and identity management including Login.gov/ID.me, OKTA integration, MFA, and partner authentication. | 10 | 10.00 | ||
| F.3.49 | F.3.49 | Role‑based access control including permission definitions, multi‑role support, temporary delegation, IDVA‑specific access, and access‑matrix workflows. | 10 | 10.00 | ||
| F.3.50 | F.3.50 | Access control for IDVA and partners including full access for IDVA users, restrictions for others, and role‑based partner access. | 9 | 9.00 | ||
| F.3.51 | F.3.51 | User lifecycle and access change management including creation, updates, deactivation, and audit tracking. | 10 | 10.00 | ||
| F.3.52 | F.3.52 | Comprehensive audit logging including login events, CRUD actions, retention controls, exports, and full before/after history. | 10 | 10.00 | ||
| F.3.53 | F.3.54 | Compliance with Illinois cybersecurity standards including CIS benchmarks, state policies, OWASP, and secure handling of integrations. | 10 | 10.00 | ||
| F.3.54 | F.3.55 | Secure API framework with real‑time/scheduled exchange, security controls, encryption, and documented specifications. | 7 | 7.00 | ||
| F.3.55 | F.3.57 | Secure cross‑agency integration with data isolation, cybersecurity compliance, monitoring, and documentation. | 9 | 9.00 | ||
| F.3.56 | F.3.59 | Comprehensive training including onsite/remote/online training, full system coverage, advance scheduling, and training materials. | 9 | 9.00 | ||
| F.3.57 | F.3.60 | Ongoing technical support including hotline support, response times, coverage scope, and no‑cost updates. | 9 | 9.00 | ||
| F.3.58 | F.3.61 | Maintenance tracking including issue logs, severity tracking, prioritization, and sharing logs with contract managers. | 10 | 10.00 | ||
| F.3.59 | F.3.62 | Comprehensive auditing including auditing all record types, logging changes, role‑based visibility, and export of logs. | 10 | 10.00 | ||
| F.3.60 | F.3.63 | Configurable audit trails including field‑level tracking, metadata, automatic tracking, and retention‑policy alignment. | 10 | 10.00 | ||
| F.3.61 | F.3.64 | System‑wide activity monitoring including event tracking, dashboards, program integrity reporting, and compliance oversight. | 10 | 10.00 | ||
| F.3.62 | F.3.65 | Transparency in claim lifecycle including full history, responsible party identification, ownership transfers, and long‑term audit storage. | 10 | 10.00 | ||
| F.3.63 | F.3.66 | Data migration planning including full inventory, cleansing steps, mapping specifications, and validation documentation. | 10 | 10.00 | ||
| F.3.64 | F.3.67 | Structured ETL methodology including secure extraction, transformation rules, controlled loading, and contingency/rollback options. | 10 | 10.00 | ||
| F.3.65 | F.3.68 | Data‑migration validation including record/field verification, completeness checks, functional validation, and reconciliation reporting. | 10 | 10.00 | ||
| F.3.66 | F.3.69 | Backup and recovery including frequent backups, integrity verification, granular restoration, and continuity procedures. | 10 | 10.00 | ||
| F.3.67 | F.3.70 | Mobile access via web interface including full functionality, claim updates, document upload, performance consistency, and responsive layout. | 7 | 7.00 | ||
| F.3.68 | F.3.71 | Optional native mobile apps including offline capability, secure camera use, and state‑compliant authentication. | 2 | 2.00 | ||
| F.3.69 | F.3.72 | Mobile security including encryption, session timeouts, remote wipe, MFA, and IAM integration. | 7 | 7.00 | ||
| F.3.70 | F.3.73 | Mobile accessibility including assistive tools, zoom/text scaling, full usability, and consistent experience. | 7 | 7.00 | ||
| F.3.71 | F.3.74 | Mobile document capture including direct camera upload, optimization, metadata tagging, and audit trails. | 2 | 2.00 | ||
| F.3.72 | F.3.75 | Software development and quality standards including Agile/PMBOK, testing phases, ISO certification, and issue‑notification policies. | 10 | 10.00 | ||
| F.3.73 | F.3.76 | Scalable technical architecture including version compatibility, virtual environments, DR support, and integrated modules. | 10 | 10.00 | ||
| F.3.74 | F.3.77 | Secure infrastructure operations including SOC/ISO frameworks, datacenter security, and encryption‑key/incident‑response documentation. | 10 | 10.00 | ||
| F.3.75 | F.3.78 | Application‑level security including multi‑level controls, OWASP coding standards, and validation enforcement. | 10 | 10.00 | ||
| F.3.76 | F.3.79 | Customization and configuration including user‑defined fields, no‑code configurations, preserved customizations, and versioned entities. | 7 | 7.00 | ||
| F.3.77 | F.3.80 | Operational stability including reliable performance, consistent response times, update handling, and complete database documentation. | 10 | 10.00 | ||
| F.3.78 | Veteran Self‑Service Portal The system must provide a secure, modern online portal that allows Veterans to authenticate through approved identity‑verification services (e.g., Login.gov, ID.me), complete online intake forms, and submit demographic, service, and dependent data. All portal‑submitted information must flow directly into the internal IDVA claims management workflows. The portal must ensure secure access, encryption, and full audit tracking for every Veteran‑submitted action. | 18 | 18.00 | ||
| F.3.79 | Guided Electronic Claim Submission | ||||
| The system must enable Veterans to initiate and complete claims through structured, guided workflows. It should identify required forms, documents, and eligibility criteria automatically, support VA‑compliant electronic signatures or attestations, and route both completed and in‑progress claims into internal IDVA workflows for review. | 10 | 10.00 | |||
| F.3.80 | Customer‑Facing Document Upload | ||||
| The system must support secure document upload from desktop and mobile devices, including photos and evidence. Uploaded files must be automatically classified and associated with the correct claim or issue. Veterans must receive confirmations of receipt, and all uploads must be encrypted, securely handled, and labeled with appropriate metadata. | 10 | 10.00 | |||
| F.3.81 | The portal must provide Veterans with real‑time visibility into their claim status, including current phase, outstanding requirements, and next steps. Veterans should also see historical claim activity, submissions, updates, and communications. Alerts should display missing information or upcoming deadlines, with data synchronized in real time with internal workflows. | 10 | 10.00 | ||
| F.3.82 | The portal must allow Veterans to request, book, and modify appointments online, with access to confirmations, reminders, and instructions. The system must synchronize appointments with staff calendars and support multiple appointment types, including in‑person, virtual, and phone meetings. | 10 | 10.00 | ||
| F.3.83 | Access to Letters & Communications | ||||
| Veterans must be able to view and download official letters and notifications generated by the claims management system. The system should support opt‑in/opt‑out for electronic delivery, maintain a historical communications library, and ensure all documents meet security and privacy standards. | 10 | 10.00 | |||
| F.3.84 | Accessibility & Multilingual Support | ||||
| The portal must comply with WCAG 2.1 Level AA and support full accessibility, including screen readers, high‑contrast modes, keyboard navigation, and text scaling. It must also support the State’s Weglot translation widget and maintain consistent formatting and functionality across all translated conten | 9 | 9.00 | |||
| F.3.85 | Secure Portal‑to‑System Interaction | ||||
| The system must ensure that public‑facing portal components are properly segregated from internal systems, using secure APIs for communication. All portal transactions must be logged and auditable, and strict role‑based access controls must be enforced to ensure Veterans can view only their own data. | 9 | 9.00 | |||
| 800.00 | 0.00 | 800.00 | |||
| 800.00 |
Demonstrations
| DESIRABLE CRITERIA | EVALUTION | |||
| Criteria ID# | Criteria Description | Max Score | Quality | |
| Rating | Evaluator Score | Evaluator's Comments - must justify applied Evaluator Rating and Score. | ||
| F.5.1 | Demonstrate how a new Veteran is entered into the system during intake. In your response, show: |
• Real time entry of demographics, service history, dependents, and identifiers
• Field validation for required and optional information
| • Auto population of this data into a claim or form | 20 | 20.00 | |
| F.5.2 | F.5.2 Demonstrate how a new claim is created and screened for eligibility. In your response, show: |
• How users initiate a claim for a Veteran
• How the system identifies required documents and eligibility factors
| • How the system warns users about missing or incomplete items | 20 | 20.00 | |
| F.5.3 | F.5.3 Demonstrate how claims and supporting documents are submitted electronically. In your response, show: |
• Upload of multiple document types and assignment to the correct claim
• Pre submission validation and error messaging
• The electronic submission process using VA approved interfaces
| 20 | 20.00 | |
| F.5.4 | F.5.4 Demonstrate how issues within a claim are tracked and updated. In your response, show: |
• How issues are added, categorized, or modified
• How status changes are displayed
| • How staff add notes, tasks, or reminders tied to an issue | 20 | 20.00 | |
| F.5.5 | F.5.5 Demonstrate how rating decisions and benefit changes are displayed in the system. In your response, show: |
• Where granted, denied, or deferred decisions appear
• How combined rating changes are tracked over time
| • How award amounts and retro calculations are presented to the user | 20 | 20.00 | |
| F.5.6 | F.5.6 Demonstrate how appeals are initiated and managed. In your response, show: |
• How the system creates and tracks NODs, HLRs, supplemental claims, and Board appeals
• How the system displays hearing dates, deadlines, or pending items
| • How appeal related evidence and correspondence are stored | 20 | 20.00 | |
| F.5.7 | F.5.7 Demonstrate how long term benefits and ongoing Veteran status updates are managed. In your response, show: |
• How payment history, adjustments, or offsets are displayed
• How users update dependents or personal information
| • How required annual or recurring reviews are tracked | 20 | 20.00 | |
| F.5.8 | F.5.8 Demonstrate how fiduciary or competency information is recorded and used. In your response, show: |
• How fiduciary contact details are entered and linked to a case
• How competency status is updated and where it affects workflows
| • How the system alerts staff to required follow up actions | 20 | 20.00 | |
| F.5.9 | F.5.9 Demonstrate how death information is processed and linked to survivor benefits. In your response, show: |
• How death is recorded and verified
• How the system identifies potentially eligible survivor benefits
• How DIC claims, burial benefits, and related applications are created
| 20 | 20.00 | |
| F.5.10 | F.5.10 Demonstrate how the Veteran’s complete record is preserved for final disposition. In your response, show: |
• Full historical view of claims, issues, awards, and document versions
• How data can be archived or exported according to policy
• How long term retention rules are applied to the Veteran’s record 20 20.00
Point Breakdown Description Percentage
| Does not meet criteria | 0.00% |
| Extrememly Poor | 14.00% |
| Poor | 25.00% |
| Slightly better than Poor | 34.00% |
| Below Average | 43.00% |
| Average | 50.00% |
| Slightly Better than Average | 57.00% |
| Better than Average | 66.00% |
| Good | 75.00% |
| Very Good | 84.00% |
| Excellent | 92.00% |
| Exceeds all expecatations | 100.00% |
Score Value Definitions Evaluation Sheet - Score Value Definition
| Point Value to Assign | Evaluation | Description |
| 0% of Maximum Points Possible (MPP) | No value | The vendor's proposal has responded to the requirement, but has not established the capability to perform the requirement |
| 14% to 34% of MPP | Poor | The vendor's proposal has responded to the requirement, but the proposal presents no convincing capability to meet the requirement or the capability is only marginally described. Further differentiation can be shown as follows: |
| 14% Just barely above no value | ||
| 25% Poor | ||
| 34% Response falls short of average but is slightly better than other items scored as poor | ||
| 43% to 57% of MPP | Average | The vendor's proposal has an adequate capability to perform and meet this requirement or the detail provided to describe its approach is only sufficient to consider it average. Further differentiation can be shown as follows: |
| 43% Just barely above average, but better than poor | ||
| 50% Average | ||
| 57% Slightly better than average, but not good | ||
| 66% to 84% of MPP | Good | The vendor's proposal has provided additional information to establish performance qualifications, which meet and exceed the requirements of the RFP. Further differentiation can be shown as follows: |
| 66% Better than average, based on some additional information in the proposal or reference checks | ||
| 75% Good | ||
| 84% Very good, but falls short of excellent | ||
| 92% to 100% of MPP | Excellent | The vendor's proposal has provided an efficient, detailed approach to meeting and exceeding requirements or references and/or their proposal appears to be practical, reliable, stable, sophisticated, and implementable. The proposal has provided a clear and detailed approach that demonstrated superior capability considering all factors such as efficiency, feasibility, stability, and quality. |
| 92% Excellent-Better than good, based on qualities listed above. |
| 100% Above and beyond all expectations |
File details come from the government source that posted it. Updated .