DETAILS OF BIDDER. Bidders are to complete the following section in full Where the bidder consists of a Joint Venture Consortium, the nominated lead party details shall be submitted. Name of Bidder Contact Person for this bid Postal address Domicillium Address Telephone No Facsimile No Email Address SIGNATURE …………………………………………………… DATE…………………… NAME OF BIDDER ………………………………POSITION …………………………….. MBD 3 FORM D: PRICING SCHEDULE & REQUIREMENTS (To be completed by the Bidder) PRICING SCHEDULE – NON-FIRM PRICES (PURCHASES) Name of Bidder: …………………………………………………….. Bid Number: ………….……………………………………………… Closing Time: ………….……………………………………………… Closing Date: …………………………………………………………. OFFER TO BE VALID FOR 120 DAYS FROM THE CLOSING DATE OF BID. Price(s) must include cost of supply, delivery, off-loading. Prices must be exclusive of VAT. It must be noted that the estimated quantities provided in the Pricing Schedule are purely for evaluation purposes only and does not provide any indication of the required quantities of product/s for the duration of the contract by the JRA and does not provide any guarantee to the contractor whatsoever in terms of quantities required. PRICING SCHEDULE & REQUIREMENTS. (To be completed by the Bidder). Price(s) must include cost of supply, delivery, off-loading (direct and indirectly) related costs. SCHEDULE OF RATES PRICING SCHEDULE – NON-FIRM PRICES NOTE: PRICES SUBJECT TO RISE AND FALL AND ESCALATION FOR OTHER APPLICABLE FACTORS. Price(s) must include cost of supply, delivery, off-loading and removal where applicable (indirect and direct costs). Prices must be exclusive of VAT, on the pricing schedule *NB It must be noted that the estimated quantities provided in the Pricing Schedule are purely for evaluation purposes only and does not provide any indication of the required quantities of products for the duration of the contract by the JRA and does not provide any guarantee to the contractor whatsoever in terms of quantities required. Rates shall remain firm for the first twelve months, where after escalation will be negotiable in line with CPI. The items listed below are not limited to, the JRA reserves the right to request quotations for Concrete Product items which are not listed in the pricing schedule from the awarded bidder / bidders in the related category or sub- category or from all bidders. JOHANNESBURG ROADS AGENCY (SOC) LTD CONTRACT NO:20-153 APPOINTMENT OF A SUPPLIER FOR THE SUPPLY, DELIVERY, OFFLOAD AND STACKING OF CONCRETE PRODUCTS TO JOHANNESBURG RO...

Related to DETAILS OF BIDDER

Data Requirements ‌ • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.
HUB Subcontracting Plan The Owner has adopted Exhibit H, Policy on Utilization of Historically Underutilized Business ("Policy"), which is incorporated herein by reference. Contractor, as a provision of the Agreement must comply with the requirements of the Policy and adhere to the HUB Subcontracting Plan submitted with Contractor's Proposal and attached as Exhibit I. No changes to the HUB Subcontracting Plan can be made by the Contractor without the prior written approval of the Owner in accordance with the Policy.
Quality Control Procedures The Seller shall have an internal quality control program that verifies, on a regular basis, the existence and accuracy of the legal documents, credit documents, property appraisals, and underwriting decisions. The program shall include evaluating and monitoring the overall quality of the Seller's loan production and the servicing activities of the Seller. The program is to ensure that the Mortgage Loans are originated and serviced in accordance with Accepted Servicing Standards and the Underwriting Guidelines; guard against dishonest, fraudulent, or negligent acts; and guard against errors and omissions by officers, employees, or other authorized persons.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Price Adjustments for OGS Centralized Contracts Periodic price adjustments will occur no more than twice per year on a schedule to be established solely by OGS. Pricing offered shall be fixed for the first twelve (12) months of the Contract term. Such price increases will only apply to the OGS Centralized Contracts and shall not be applied retroactively to Authorized User Agreements or any Mini-bids already submitted to an Authorized User. Price Decreases Price decreases may be made at any time. Additionally, some price decreases shall be calculated in accordance with Appendix B, section 17, Pricing.
Solicitations for Subcontracts, Including Procurement of Materials and Equipment In all solicitation, either by competitive bidding or negotiation, made by the Contractor for work to be performed under a subcontract, including procurement of materials or leases of equipment, each potential Subcontractor or supplier shall be notified by the Contractor of the Contractor’s obligations under this Agreement and the Regulations relative to non-discrimination on the grounds of race, color, or national origin.
Change of Control; Assignment and Subcontracting Except as set forth in this Section 7.5, neither party may assign any of its rights and obligations under this Agreement without the prior written approval of the other party, which approval will not be unreasonably withheld. For purposes of this Section 7.5, a direct or indirect change of control of Registry Operator or any subcontracting arrangement that relates to any Critical Function (as identified in Section 6 of Specification 10) for the TLD (a “Material Subcontracting Arrangement”) shall be deemed an assignment.
Compliance Policies and Procedures To assist the Fund in complying with Rule 38a-1 of the 1940 Act, BBH&Co. represents that it has adopted written policies and procedures reasonably designed to prevent violation of the federal securities laws in fulfilling its obligations under the Agreement and that it has in place a compliance program to monitor its compliance with those policies and procedures. BBH&Co will upon request provide the Fund with information about our compliance program as mutually agreed.
For Company bidder(s The E-bidder’s need to key in their company details for online registration and upload a certified true copy of The Company’s Memorandum And Articles Of Association (M&A), Forms 44, 24 and 49, Board Of Director Resolution (or its equivalent forms under the Companies Act 2016) and authorize bidding letter than upload to ESZAM AUCTIONEER SDN BHD website.
Assignment and Subcontracting City and Consultant recognize and agree that this Agreement contemplates personal performance by Consultant and is based upon a determination of Consultant’s unique personal competence, experience, and specialized personal knowledge. Moreover, a substantial inducement to City for entering into this Agreement was and is the professional reputation and competence of Consultant. Consultant may not assign this Agreement or any interest therein without the prior written approval of the City. Consultant shall not subcontract any portion of the performance contemplated and provided for herein, other than to the subcontractors listed in the Consultant’s proposal, without prior written approval of the City.

DETAILS OF BIDDER Sample Clauses

Filter & Search

Related Clauses

Related to DETAILS OF BIDDER