2e2.Common_Plg_Opn_Oorja app _ Project OJAS

• OORJA APP


  App for BSNL officers to verify the Electricity Bills issued by State electricity Boards/Discoms to BSNL Offices, Exchange Building, BTS site etc.

  
• OORJA APP


  • Auto Bill Validation & Payment System
  • Payment process is automated and needs minimum manual intervention unless any discrepancy in bill is noticed or in case due to lack of data, validation is not feasible
  • Acquisition of data from DISCOMs is automated and populated in Oorja on regular basis
  • Bills raised by DISCOM are captured on daily basis by bill aggregator and provided to Oorja Application (By ITPC) through FTP server
  • Oorja application validates each bill based on automated validation algorithms

  
• Auto Bill Validation & Payment System

  1. Bill fetch from Vendor

  2. Auto Bill Validation

  3. Bill approval

  4. ERP Integration for Liability Generation

  5. Pay Priority

  6. Payment through CSC/Payment Aggregator

  
• Bill fetch from Vendor

  Fetch bills from Discom Web Portal & convert PDF into xls format
• Sanity Bill Validation (SBV)

  • Check for Meter faulty through OMR & CMR
  • Check for Consumed Units – 0 & Avg. Billing cases
  • Check for Number of Units Consumed + OMR = CMR
  • Check for Meter Continuity by tallying OMR of the Present Month with CMR of the Previous Month
  • Exceptions in any one of the above checks will be treated as failed in Sanity Bill Validation
  • Sanity Failed Invoices will not be validated for next DBV & OBV validations due to lack of info
  • Sanity Bill Validation success Invoices will be sent for Discom & Oorja Bill Validations
  • Sanity Bill Validation failed Bills will be identified as starting letter "S" in the "Bill Id"
• Discom Bill Validation (DBV)

  • Bills will be Validated based on historical data i.e. Average of last 6 months Consumed Units & Current Amount Pay and calculate Relative Percentage Variation w.r.t. Present month Consumed Units & Current Amount Pay
  • If Invoice having any one of the above Relative Percentage Variation < -30% or > 10% will be treated as Discom Bill Validation failed
  • If both the Relative Percentage Variations within -30 to +10% treated as Discom Bill Validation (DBV) is Success
  • Irrespective of the Discom Bill Validation failed/Success, all the Discom Bill Validation Invoices will be sent for Oorja Bill Validation
  • Discom Bill Validation failed/Success Bills will be identified as starting letter 'D' in the "Bill Id"

  
• Oorja Bill Validation (OBV)

  • Oorja Bill Validation is just like normal bill tariff validation in Oorja App with auto filling of all Permanent (A), Dynamic (B) and Calculated(C) parameters and calculates the Percentage Variation
  • If all the Dynamic Parameters are available in the Bill Data provided by Bill Fetch Vendor & Bill Category configured in the Oorja then those Invoices will be taken for Oorja Bill Validation
  • If Percentage Variation of Oorja Calculated Gross Amount w.r.t. Discom Gross Amount is < +/-5% treated as OBV Success. If it is exceeds +/-5% then these bills will be treated as OBV failed
  • If the Invoices having both OBV & DBV success then these cases will be sent directly to DGM (F) for financial approval then sent to Circle Nodal for final approval
  • If Invoices having any one of the Validation – DBV or OBV fails then these cases will be sent to Site In-charge for his approval with remarks
  • A docket will be generated against the bill when any one of the SBV/DBV/OBV Validation fails
  • All the Oorja Bill Validation (failed/Success) Bills will be Identified as starting letter 'U' in the "Bill Id"
  • If all 3 validations are success then those bills will be identified as starting letter 'A' in the Bill Id

  
• Bill approval


  1. Site Inch. / DGM (F)/ Circle Nodal approve bills based on thresholds

  2. Site in-charge approves bills with exceptions

  3. Bills directly received from system are approved by DGM (F) through bulk approval

  4. Circle Nodal @ L1 approves all the bills approved by Site In-charge and DGM (F) through bulk approval

  5. All the approved bills are progressed to ERP for generation of liability

  
• ERP Integration for Liability Generation


  1. Liability will be generated for the bills through ERP Meter Master & Vendor Master

  2. Circle designated AO runs a T-Code in ERP-SAP to generate a liability document no. against each Invoice

  3. If prime data – BA, CAN, Meter No, Cost Center No., Vendor Code and Partner Bank type are tallied for the received invoice, a liability document number will be generated and updated back to Oorja

  4. Any mismatch on above will lead to ERP failure – IF/LF bills will be pushed back to L1 for resolution

  
• Pay Priority


  1. All the liability generated bills will be pushed back to Circle Nodal @L2

  2. CN has to a send requisition to CSC for fund allocation against liability

  3. Pay Priority Module designed based on the priority algorithm with the predefined Payment categories – Gold/Silver/Bronze/Z. and Allocated fund

  4. Based on fund allocation, Circle Nodal @ L2 has to run the Pay Priority Module to generate a prioritized list of Invoices and initiate a Payment Request through CSC/Payment Aggregator
• Payment through CSC/Payment Aggregator

  1. There are two modes of Payment of EB Bills – CSC and Payment Aggregator (SBI – under development)

  2. Invoices which are having Virtual Bank Account Numbers against each CAN, has to use the CSC mode of Payment

  3. Invoice which is not having Virtual Bank Account numbers has to select the Payment Aggregator mode of Payment

  4. In case of CSC, acknowledgement will be updated back to Oorja

  5. In case of PA – acknowledgement will be updated to ERP through Oorja
• Unprocessed Bills – Role of Circle Wkg. Node
• Role of Site In-charge (SI)
• Validation & Alert Check list for Site In-charge before approving the Payment
• Role of DGM (F)
• Discom bill approval process

  1. Site In-charge approves invoice by submitting reasons and remarks under "Bill Approval" tab

  2. Site In-charge can select "Not to Pay" option and submit with remarks if they don't want to pay the bill

  3. Unapproved/Rejected bills moved to "Unapproved/Rejected Bills" tab

  
• Role of DGM (F)

  • Verify final approved amount, tax components etc. derived from bill is correct
  • Approve entire invoice by pressing "Bulk Approve" button
  • Can send invoice back to Site In-charge if any discrepancies

  
• Role of Circle Nodal @ L1 Stage

  1. Approve all invoices by pressing "Bulk Approve" button

  2. Can send invoice back to DGM (F)/Site In-charge if any discrepancies

  3. All approved invoices sent to ERP for liability generation

  4. Invoices with final approved amount as '0' sent directly to 'Bills Paid' block
• Invoice Failure (IF)


  Mismatch in CAN/MeterNo/VAN/PBT/Cost Center numbers with ERP MM
• Liability Failed (LF)


  Invoice returned after generation of liability due to any issue
• Multiple Invoice (MI)


  Discom issues more than one invoice against a site within 15 days
• Resolving IF/LF invoices


  1. Re-submit after resolving mismatches or other issues

  2. Monitor dockets and ensure all pending dockets closed before next billing cycle
• Invoice Failure Remarks and Reasons

  • No Cost Centre found
  • GST No or PAN not available
  • Vendor Code not defined
  • Invoice already posted by document number
• IF cases resolved by ITPC

  1. FI/CO interface: Balance in transaction

  2. IGST/CGST Amount Does not match

  3. Amount is Negative

  4. Incorrect Invoice Number

  5. Key data missing
• Liability Failure (LF) handling


  1. Circle can cancel already generated liability for unpaid invoices

  2. LF invoices can be cancelled permanently or resent to ERP for liability regeneration
• ERP Parameters


  • Meter Rent, SGST, CGST, IGST, UTGST and TCS amount captured from invoice
  • Non Taxable Electrical Charges = Current Amount - (Meter Rent + Taxes)
  • Invoice Amount = Current Amount + Meter Rent + Taxes + Surcharge + TCS
  • Adj. Debit & Adj. Credit = Arrears (+/-)
  • TDS calculated by ERP
  • Net Payable to Vendor = Gross Amount - TDS
  • Liability generated for Net Payable to Vendor amount only
• Role of Circle Nodal @ L2 Stage

  1. Approve invoices through "Bulk Approve" button in "Pending Bills at Circle Nodal (L2)" tab

  2. Manage Pay Priority through "Generate Pay Priority" button

  3. Initiate Payment Request through "Payment through CSC"/"Payment through Payment Aggregator" buttons
• Work Flow (WF)


  • Shows milestones of invoice like approval by Site In-charge, DGM (F), Circle Nodal (L1), ERP read, Liability Document Number posted, Payment Request initiated, Payment done

  
• Project OJAS is an initiative by BSNL to save energy and focus on renewable sources
• Roadmap of Project OJAS


  • Implementation of in-house software for analyzing and scheduling electricity bills
  • Analysis of existing tariff and exploring single window payment
  • Review of demand and taking corrective action
  • Closure of DG sets and providing mobile DG sets
  • Power plant optimization
  • Non-provision of BTS at un-electrified sites and closure of non-electrified BTSs
  • Implementation of Turbo Ventilator for BTS cooling
  • Closure/removal of air conditioners for non-entitled officers
  • Provisioning of renewable energy resources on RESCO model
  • Online monitoring of parameters at corporate level
• Methodology of Project OJAS


  • Saving in energy cost by optimizing use of electricity
  • Smart use of appliance
  • Temperature setting
  • Auto timer
  • Non parallel operation of transformer
  • Non starting of DG immediately
  • TOD optimisation
  • Using more energy efficient equipment
  • Getting advantage of tariff by HT to LT
  • Changing the tariff slab
  • Minimizing the contract demand
  • Betterment of power factor
  • Conversion of commercial to industrial tariff
  • Electricity bill validation and rectification
  • Alternate energy source like solar, wind, hybrid