Attachment 2 - QASP_ITRP RFI.docx
DOCX document 78 KB Posted
- Solicitation number
- 20154861
About this file
This is a Quality Assurance Surveillance Plan (QASP) for the Department of Homeland Security Customs and Border Protection (CBP) Office of Information & Technology Field Support Directorate Information Technology Refresh Program (ITRP) Support Services contract. The QASP is a government-developed document that establishes systematic quality assurance methods and contractor performance monitoring procedures for a single hybrid fixed-price and time-and-materials contract with one base year and four 12-month option periods. The contract will be administered by a Contracting Officer and a Contracting Officer's Representative (COR), who will oversee compliance with performance metrics and service delivery standards.
The QASP defines performance standards across six primary task areas: Program Management (key personnel onboarding within 5-30 days of award), Storefront Capability (95% system uptime), Hardware Procurement Assistance (99% accurate order entry and data recording), Asset Management (98-99% accuracy in receipt processing and shell record completion within 3 business days), Hardware Preparation for Deployment (95% of devices shipped within 5 business days), and optional End User Device IT Management (image development within 60 days, 100% software patch compliance within 2 business days, 98% infrastructure availability, and one-hour cybersecurity threat remediation). The COR will perform monthly surveillance assessments using automated reports, SAP reporting tools, and inspection methods, evaluating contractor performance across Quality, Schedule, Cost Control, Business Relations, and Management categories using five rating levels ranging from Exceptional to Unsatisfactory. Annual performance assessments will consolidate monthly ratings to determine contract continuation and option exercise eligibility. All surveillance documentation and checklists must be maintained throughout the contract life and forwarded to the Contracting Officer upon contract termination.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment 1 - PWS_ITRP Support Services RFI.docx | DOCX document | |
| Attachment 5 - ITRP RFI Past Performance Reference Template.docx | DOCX document | |
| Attachment 3 - SAMPLE Price Template_ITRP_DRAFT_RFI.xlsx | XLSX spreadsheet | |
| Attachment 4 - Request for Information (RFI) Questions Response Template.xlsx | XLSX spreadsheet |
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
Quality Assurance Surveillance Plan
Quality Assurance Surveillance Plan for Office of Information & Technology Field Support Directorate Information Technology Refresh Program (ITRP) Support Services
1. Purpose
This Quality Assurance Surveillance Plan (QASP) is a government developed and applied document used to ensure that systematic quality assurance methods are used in the administration of this performance-based service contract. The intent is to ensure that the contractor performs in accordance with the performance metrics and the Government receives the quality of services called for in the contract.
The contract requirement is for support services for the Office of Information & Technology (OIT) Field Support Directorate (FSD). The Field Support Directorate serves as the primary customer interface for CBP personnel worldwide. FSD is the operations and maintenance organization responsible for information technology, tactical radio communications, and surveillance systems. FSD provides technology services and service delivery, implements projects, and deploys systems to reduce downtime and maintain operational availability. This requirement is for Information Technology Refresh Program (ITRP) Support Services.
This action will be met by awarding a single hybrid (FFP and T&M) contract with one base year and four (4) 12-month option periods. The contractor’s performance will be monitored by the Contracting Officer’s Representative (COR) and Alternate Contracting Officer’s Representative (ACOR).
A properly executed QASP will assist the Government in achieving the objectives of this procurement.
2. Authority
Authority for issuance of this QASP is provided under Contract Section E – Inspection and Acceptance, which provides for inspections and acceptance of the services and documentation called for in contracts, to be executed by the Contracting Officer or a duly authorized representative.
3. Scope
To fully understand the roles and responsibilities of the parties, it is important to first define the distinction in terminology between Quality Control Plan and QASP. The contractor, and not the Government, is responsible for management and quality control actions necessary to meet the quality standards set forth by the contract.
The QASP on the other hand, is put in place to provide Government surveillance oversight of the contractor’s efforts to assure that they are timely, effective and are delivering the results specified in the contract.
4. Government Resources
The following definitions for Government resources are applicable to this plan:
Contracting Officer - A person duly appointed with the authority to enter into contracts and make related determination and findings on behalf of the Government. Contracting Officers are designated via a written warrant, which sets forth limitations of authority. The CO for this contract will TBD.
Contracting Officer’s Representative (COR) - An individual appointed in writing by the CO to act as their authorized representative to assist in the technical administration of the contract. The COR will be appointed in the resulting contract award. The limitations of authority are contained in a written letter of appointment.
5. Responsibilities
The following Government resources shall have responsibility for the implementation of this QASP:
Contracting Officer – The Contracting Officer ensures performance of all necessary actions for effective contracting, ensures compliance with the terms of the contract and safeguards the interests of the United States in the contractual relationship. It is the Contracting Officer that assures the contractor receives impartial, fair and equitable treatment under the contract. The Contracting Officer is ultimately responsible for the final determination of the adequacy of the contractor’s performance.
Contracting Officer’s Representative (COR) – The COR is responsible for technical administration of the contract and assures proper Government surveillance of the contractor’s performance. The COR is not empowered to make any contractual commitments or to authorize any changes on the Government’s behalf. Any changes that the contractor deems may affect contract price, terms, or conditions shall be referred to the Contracting Officer for action.
6. Methods of QA Surveillance
a. Contractor Performance Assessment – The marketplace for these services is very competitive. As such, the successful offeror has a vested interest in the Government-generated contractor performance assessment ratings under this contract. Additionally, the ratings will be the determinant in exercising an option. For this procurement the Government will address the quality of service, schedule, cost control, business relations, management, and other important areas. As this information may affect future source selections throughout CBP, and the continuation of the contract, the annual Government assessment will be used appropriately as an additional performance oversight and communication tool with the QASP.
b. QASP - The below listed methods of surveillance will be used by the COR in the technical administration of this QASP. In addition to the below instructions, the form to be used for documentation of quality assurance surveillance is the Surveillance Activity Checklist, Enclosure (5).
7. Surveillance Enclosures (1), (2), (3) and (4) set forth performance standards, incentives, definitions and surveillance methods for the contractor and COR while enclosure (5) provides the checklist and means for the COR to document the results of the surveillance. Enclosure (5) will be provided to the Contracting Officer on a monthly basis for inclusion into contract file.
8. Documentation
In addition to providing monthly reports to the Contracting Officer, the COR will maintain a complete Quality Assurance file. The file will contain copies of all reports, evaluations, recommendations, and any actions related to the Government’s performance of the quality assurance function, including the originals of the Quality Assurance Checklists. All such records will be maintained for the life of the contract. The COR shall forward these records to the Contracting Officer at termination or completion of the contract.
9. Enclosures
Enclosure (1) - Performance Standards – Tasks Enclosure (2) - Performance Standards – Data Enclosure (3) - Definitions for Evaluation Areas and Ratings Enclosure (4) - Surveillance Activity Checklist - Monthly Enclosure (5) - Surveillance Activity Checklist - Annually
Source Selection Sensitive Information See FAR 3.104 and 2.101
Source Selection Sensitive Information See FAR 3.104 and 2.101
Enclosure (1)
Performance Standards – Tasks
| Description |
| Performance Standard |
| Acceptable Quality Level (AQL) |
| Surveillance Method |
Task 1:
Program Management Onboard Key Personnel
| Standard is met when contractor has hired/onboarded and / or obtained commitment from proposed key personnel, including submitting BI requests and / or BI transfer requests, within five (5)- days of award. |
| Weekly using Incoming Transition Report |
Task 1:
Program Management Onboarding qualified staff
| Standard is met when the Contractor has obtained commitments from and submitted appropriate BI packages within 30 days of award |
| Weekly using Incoming Transition Report |
| Task 2: Storefront Capability |
| Uptime and accessibility: The percentage of time the Storefront Capability is fully operational, outside of planned outages, allowing users to successfully browse products, add items to a cart, and complete transactions, and all defined tiered access levels are available and responsive |
| The standard is met when the system and access is functional 95% of time. |
| Monthly using Storefront Automated Reports and Relevant Technical Service Desk (TSD) tickets |
Task 4:
Hardware Procurement Assistance
| Order Entry: FSD-managed tech refresh orders are fully and accurately processed and submitted into the CBP storefront, ensuring they are ready for bulk and timely procurement by Government officials, in accordance with validated technology refresh plans |
| Standard is met when 99% of equipment on validated FSD-managed tech refresh plan is accurately entered into the CBP storefront at least three (3)-days prior to planned procurement submission deadline. |
| Monthly using Storefront Automated Reports and FSD Reporting tools |
| Task 4: Hardware Procurement Assistance |
| Post-Procurement Equipment Data: All critical data elements from device procurements awaiting vendor delivery (see task 4.4.) are accurately recorded in designated FSD reporting tools |
| Standard is met when 99% of available critical data elements for each device procurement are: |
1. requested from the equipment vendor within three (3)-business days after order placement is confirmed;
2. accurately and completely recorded in designated FSD reporting tools within two (2)-business days of receipt from equipment vendor Monthly using FSD Reporting tools
| Task 5: Asset Management |
| Order Receipt Processing: Physical deliveries of ordered devices are physically inspected, reconciled against purchase order (PO) and packing slip, and formally entered into SAP within three (3)-business days of physical delivery date |
| Standard is met when >98% of physical deliveries are physically validated (inspected and reconciled against PO / packing slip) and subsequently confirmed as received within SAP within three (3)-business days. |
| Monthly using SAP reporting and Procurement Branch reporting |
| Task 5: Asset Management |
| Shell Record Processing: Initial asset records (shell records) for new devices are completed by accurately populating mandatory data fields within three (3)-days after physical receipt of device |
| Standard is met when >99% of shell records for new devices are completed and accurate in SAP within three (3)-business days of device receipt. |
| Monthly using SAP reporting and Procurement Branch reporting |
| Task 5: Excessing |
| Excess: Devices that have been formally identified for excessing and physically received at the designated excessing facility are fully processed / excessed in accordance with CBP excessing protocols and updated in SAP within 10-business days |
| Standard is met when >98% of devices are excessed within 3 business days of being received for excess. |
| Monthly using SAP reporting |
| Task 6: Hardware Preparation for Deployment |
| Device Deployment: Devices are shipped to designated end users within five (5) business days of shell records completed and accurate in SAP |
| Standard is met when >95% of devices are shipped to the end user within five (5)-business days of shell records completed and accurate in SAP. |
| Monthly using FSD Reporting tools |
| Task 6: Hardware Preparation for Deployment |
| Device InTune-Ready: Verify all required device identifiers for new devices have been securely and accurately enrolled in the designated Microsoft Intune tenant ensuring the device is fully prepared for automated provisioning and imaging via Intune |
| Standard is met when 99% of computers physically received have verification that all available required device identifiers (e.g., MAC addresses) entered accurately into Microsoft tenant rendering them InTune-ready at time of shipping to end user. |
| Monthly using FSD Reporting tools |
| Optional Task 8: End User Device IT Management |
| New Image Development and Deployment: New operating system image and overlays are developed, integrated, tested, CBP-approved, and deployed |
| Standard is met when new operating system image and overlays are developed, integrated, tested, CBP-approved, and deployed within 60-calendar days of the CBP-identified need. |
| Weekly using End User Device IT Management Weekly Status Report and CBP Success/Failure of Image Deployment Report |
| Optional Task 8: End User Device IT Management |
| New Image Compliance: Images are compatible with CBP workstations and CBP applications and in compliance with established CBP policies and standards |
| Standard is met when 100% of the image are compatible with CBP workstations and CBP applications and in compliance with established CBP policies and standards. |
| Weekly using End User Device IT Management Weekly Status Report and Helpdesk Ticket Reporting |
| Optional Task 8: End User Device IT Management |
| Software Packaging and Deployment: Software is packaged and available in the software center |
| Standard is met when software packaging is completed and available in the software center within 10-business days of receiving validated request. |
| Weekly using End User Device IT Management Weekly Status Report and FISMA Compliance Report |
| Optional Task 8: End User Device IT Management |
| Software Patch Compliance: Software is packaged and available in the software center |
| Standard is met when software patches are 100% compliant with vendor-provided OS and application patches within two (2)-business days of patch issuance. Zero-day updates must be applied within 12-hours of notification. |
| Daily using End User Device IT Management Daily Patching Compliance Report and FISMA Compliance Report |
| Optional Task 8: End User Device IT Management |
| Out of Box Experience and Device Enrollment Effectiveness: Devices deployed to end users experience low-friction, zero-touch enrollment |
| Standard is met when 90% of low-friction, zero-touch requests are enrolled without intervention. |
| Weekly using End User Device IT Management Weekly Status Report and FISMA Compliance Report |
| Optional Task 8: End User Device IT Management |
| Cybersecurity: New cyberthreats identified by security operations center are remediated |
| Standard is met when cyber threat remediation is implemented within one (1)-hour, or no more than four (4)-hours, after security operations center notice. |
| Weekly using End User Device IT Management Weekly Status Report and SOC Threat Notice Report |
| Optional Task 8: End User Device IT Management |
| IT Infrastructure: |
CBP’s end user device environment is operation and secure
| Standard is met when CBP’s end user device environment is operational and secure with 98% availability. |
| Weekly using End User Device IT Management Weekly Status Report and CBP End Point Report |
Enclosure (2):
Performance Standards – Data
| Description |
| Standard |
| AQL |
| Surveillance Method/Measure |
| Tech Refresh Operational Protocol1 with Change Management Decision Tracker |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
100% Inspection by COR.
| Recurring program status report |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| Recurring financial status report |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| Program Management Review Briefing Slides |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Background Investigation Packages |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Post-Award Conference (Kick-Off Meeting) Slides |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Post-Award Conference (Kick-Off Meeting) Minutes |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Incoming Transition Plan |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Incoming Transition Report |
| Submission is in accordance with the PWS . |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| Transition-In Lessons Learned Report |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Outgoing Transition Plan |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Outgoing Transition Report |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Storefront Capability Development Plan |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Storefront Capability Requirements Matrix |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Final Pre-Production Solution for Beta Testing, including draft user manual and training guide |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Final Storefront Capability for Formal Roll-Out, including final user manual and training guide |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Intake, distribution, deployment reports related to computer lifecycle management |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Standard use case definitions with associated system specifications and configurations document |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Accurate aging‑technology assessments and prioritized refresh recommendations (including down channeling) |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Report certifying that for all items purchased, all serial numbers are validated, asset shells correct, asset number assignment |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Reports related to device excess process, including time for completion |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| SAP Data Entry Periodic Audit Report |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Device Receipt Instructions for End Users and New Device Start-Up / Deployment Instructions for End Users (unboxing) |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| User-initiated start-up instructions per use case definition document (operational) |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Image Deployment Status Tracker |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Library of SOPs related to Lifecycle Management processes (creation and maintenance) |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Establish Current CBP Computer Use Case Catalog |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Update CBP Computer Use Case Catalog |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Outcomes Metrics Report Framework |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Outcome Metrics Report |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| End User Device IT Management Weekly Status Report |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| End User Device IT Management Daily Patching Compliance Report |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| End User Device IT Management Ad Hoc Report |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
| Library of SOPs related to Imaging / Patching, Device / Software / Capability Testing and Deployment, and Infrastructure Support Practices within CBP |
| Submission is in accordance with the PWS |
| 95% of required deliverable provided on time, are accurate as written, and do not require major rewrite. |
| 100% Inspection by COR. |
Enclosure (3)
DEFINITIONS FOR EVALUAITON AREAS AND RATINGS
All PWS tasks, including PWS sub-tasks, will be assessed focusing on the following:
Quality of Product or Service – Assess the contractor’s effort to transform operational needs and requirements into an integrated solution. Areas of focus may include the planning and management of program tasks, the quality of support provided throughout all phases of contract execution, the integration of program management specialties, management of interfaces, and the management of a totally integrated effort of all program management concerns to meet cost, performance, and schedule objectives. Assess how successfully the contractor meets program quality.
Schedule – Assess the contractor’s adherence to the required delivery schedule by assessing the contractor’s efforts during the assessment period that contribute to or effect the schedule variance. Also address significance of scheduled events (i.e., design reviews), discuss causes, and assess the effectiveness of contractor corrective actions.
Cost Control – Assess the contractor’s effectiveness in forecasting, managing, and controlling contract cost. Is the contractor experiencing cost growth or underrun? If so, discuss the causes and contractor-proposed solutions for the cost overruns. For contracts where task or contract sizing is based upon contractor provided person-hour estimates, the relationship of these estimates to ultimate cost should be assessed. In addition, the extent to which the contractor demonstrates a sense of cost responsibility, through the efficient use of resources in each work effort should be assessed.
Business Relations – Assess the timelines, completeness and quality of problem identification, corrective action plans, proposal submittals, the contractor’s reasonable and cooperative behavior, effective business relations, and customer satisfaction.
Management – Assess the contractor’s success with timely award and management of subcontracts, including whether the contractor met small/small disadvantage and women-owned business participation goals. Discuss the extent to which the contractor discharges its responsibility for integration and coordination of all activity needed to execute the contract; identifies and applies resources required to meet schedule requirements; assigns responsibility for tasks/actions required by contract; communicates appropriate information to affected program elements in a timely manner. Assess the contractor’s risk mitigation plans. If applicable, identify any other management areas that are unique to the contract.
Other areas – Assess additional evaluation areas unique to the contract or that cannot be captured elsewhere.
The evaluation ratings are as follows:
Exceptional – Performance meets contractual requirements and exceeds many to the Government’s benefit. The contractual performance of the task and sub-task being assessed was accomplished with few minor problems for which corrective actions taken by the contractor were highly effective.
Very Good - Performance meets contractual requirements and exceeds some to the Government’s benefit. The contractual performance of the task and sub-task being assessed was accomplished with some minor problems for which corrective actions taken by the contractor were effective.
Satisfactory - Performance meets contractual requirements. The contractual performance of the task and sub-task contain some minor problems for which corrective actions taken by the contractor appear or were satisfactory.
Marginal - Performance does not meet some contractual requirements. The contractual performance of the task and sub-task being assessed reflect a serious problem for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear only marginally effective or were not fully implemented.
Unsatisfactory – Performance does not meet most contractual requirements and recovery is not likely in a timely manner. The contractual performance of the task or sub-task contains a serious problem(s) for which the contractor’s actions appear or were ineffective.
Enclosure (4)
SURVEILLANCE ACTIVITY CHECKLIST – MONTHLY
Monthly Surveillance:
The COR will perform a monthly assessment of Quality, Schedule, Cost Control, Business Relations, Management, and Other Areas as applicable utilizing the contractor performance evaluation rating definitions listed in enclosure (4).
| Description |
| Surveillance Method / Measure |
| Date Completed |
| Quality |
| Schedule |
| Cost Control |
| Business Relations |
| Mgmt |
Other
| Task 1: Program Management |
| See Enclosure 1 |
| Task 2: Storefront Capability |
| See Enclosure 1 |
| Task 4: Hardware Procurement Assistance: |
| See Enclosure 1 |
| Task 5: Asset Management: |
| See Enclosure 1 |
| Task 6: Hardware Prep for Deployment |
| See Enclosure 1 |
| Optional Task 8: End User Device IT Mngmt |
| See Enclosure 1 |
Enclosure (5)
SURVEILLANCE ACTIVITY CHECKLIST - ANNUALLY
Annual Surveillance:
The COR will perform an annual assessment of overall contract performance utilizing the contractor performance evaluation rating definitions listed in enclosure (4) and the monthly summary of ratings.
| Description |
| Surveillance Method/ |
Measure
| Date Planned |
| Date Completed |
| Summary Rating/Results |
| Quality of Service |
| Review of Monthly Ratings. |
| TBD |
| Schedule |
| Review of Monthly Ratings. |
| TBD |
| Cost Control |
| Review of Monthly Ratings |
| TBD |
| Business Relations |
| Review of Monthly Ratings |
| TBD |
| Management |
| Review of Monthly Ratings |
| TBD |
| Other Areas |
| Review of Monthly Ratings |
| TBD |
File details come from the government source that posted it. Updated .