The problems in the current system we have addressed and provide the solution in Blockchain.As we all know that the current and existing system has centralized database. The drawback of existing Vehicle Management lifecycle system are as follows:1. Consumer trust is lacking2. Verification by data provider is not available.3. No scope for real-time updaters.4. Centralized and hence can be changed for commercial purpose.5. Subjected to fraud from bank, insurance and leasing companies.6. Weeks time for Updating of vehicle details to RTOBenefits of Proposed solution: Integration among different organizations (ex. RTO, Insurance, Bank, Manufacturer, Dealer) will really benefit at each organization to improve their sales and services due to excellent transparency and speed process.Operational cost will be reduced 5% on each peer and organization.Transparency is maintained among all systems.Fault tolerance across the systems.Customer trust is built through the proposed system as he can find the information related to his vehicle at one place rather approaching different cross organizations.Resellers can trust the vehicle as the original parts of the vehicle are traceable.How it works:Integrating blockchain solves the problem of asymmetrical information in the used vehicle market by creating a Decentralized, immutable, transparent, secure, and reliable vehicle life-cycle repository.Create a block with different levels of access and information protection. Data security level should correspond to the needs of government agencies.All the records from data providers is hashed and added into Blockchain.The data itself is stored in service providers databases but its hash in the Blockchain.The validity of the information provided can be checked by the hash code.Create an infrastructure and provide direct access to the database for each market participant.Roles and Responsibilities-Network setup for Hyperledger Fabric.-Understanding of Functional architecture of Vehicle lifecycle management and Implemented in technically.-Developed POC and Whitepaper.-Implemented Channel creation, channel join conditions, Governance rule and Endorsement policy design as part of the development.-API development and UI connectivity.Site address: vehicle.html

Project Description:

The problems in the current system we have addressed and provide the solution in Blockchain.

As we all know that the current and existing system has centralized database. The drawback of existing Vehicle Management lifecycle system are as follows:

1. Consumer trust is lacking
2. Verification by data provider is not available.
3. No scope for real-time updaters.
4. Centralized and hence can be changed for commercial purpose.
5. Subjected to fraud from bank, insurance and leasing companies.
6. Weeks’ time for Updating of vehicle details to RTO

Benefits of Proposed solution: Integration among different organizations (ex. RTO, Insurance, Bank, Manufacturer, Dealer) will really benefit at each organization to improve their sales and services due to excellent transparency and speed process.

• Operational cost will be reduced 5% on each peer and organization.
• Transparency is maintained among all systems.
• Fault tolerance across the systems.
• Customer trust is built through the proposed system as he can find the information related to his vehicle at one place rather approaching different cross organizations.
• Resellers can trust the vehicle as the original parts of the vehicle are traceable.

How it works:

Integrating blockchain solves the problem of asymmetrical information in the used vehicle market by creating a Decentralized, immutable, transparent, secure, and reliable vehicle life-cycle repository.

Create a block with different levels of access and information protection. Data security level should correspond to the needs of government agencies.

All the records from data providers is hashed and added into Blockchain.

The data itself is stored in service provider’s databases but its hash in the Blockchain.

The validity of the information provided can be checked by the hash code.

Create an infrastructure and provide direct access to the database for each market participant.

Roles and Responsibilities

-Network setup for Hyperledger Fabric.

-Understanding of Functional architecture of Vehicle lifecycle management and

Implemented in technically.

-Developed POC and Whitepaper.

-Implemented Channel creation, channel join conditions, Governance rule and

Endorsement policy design as part of the development.

-API development and UI connectivity.

Site address: vehicle.html

Project Description:

ICO for crowdfunding was done for the business Helloworld video sharing platform.

It is similar to youtube but with this app by registering itself users can avail 10 tokens. For watching the video and good comments.

User attention is the most valuable resource on the Helloworld video platform, and it is rewarded! Any registered user who has watched a video, will get from 25% to 95% of the funds allocated by advertisers.

Creators who upload their video content on the platform, receive 65% of the funds spent by advertisers, and 90% of the funds received as payment from users who watch their premium content.

Helloworld provides advertisers with accurate statistics for each ad view. All data is

recorded on the blockchain and can be checked by both advertisers and third party

auditors. The payments for user’s attention are made directly, without intermediaries and is completely transparent. Advertising costs are 20% lower than on centralized video platforms.

Advertisers may upload on the platform their advertising video that promotes an event, a website, a product or a service, by indicating in the settings a cost-per-view and by targeting based on audience country, city, gender, age and interests.

The video will only be shown to those users who are in the selected targeting group. A reward, specified by an advertiser in the settings, will be added automatically to users’ wallets for each unique viewing of the video.

Advertisers may add their banner or a short promotional video for up to 30 seconds to appear in the videos that are listed as free to view by their uploaders. It is possible to choose targeting based on audience country, city, gender, age and interests. Both the author of the video where the ad is displayed, and the user who watches the video, will automatically receive a reward specified by the advertiser for each unique ad view. The author receives 65% of a costper-view, and the user receives 25%.

Advertisers may add a video that promotes a specific product or a service, to the marketplace, along with a text description, technical characteristics and price.

Users can buy the product or the service advertised in the video, by clicking the “Buy” button and paying HWVSP tokens directly from their wallets to the wallet of the advertiser.

Video creators can upload their video and specify the price on a per-view basis.

Video creators can create a paid channel, for which users pay a daily, weekly, monthly or yearly subscription fee.

Video creators can upload their video and specify them as free to watch.

Video creators can upload their video and specify that users can watch the video for free, and that the video is adfree.

How it works:

Users can watch free videos without ads with the option to support content creators by donating some HWVSP tokens if they

liked the video.

Users can watch free videos with ads embedded in them and automatically receive in their wallets 25% of the cost-per-view

specified by the advertiser.

Users can watch promotional videos uploaded by advertisers and automatically receive in their wallets 90% of the cost-per-view specified by an advertiser.

Users can watch premium content on a pay-per-view basis, or pay a subscription fee for a daily, weekly, monthly or yearly access.

Users can buy the goods and services, advertised in the videos and pay sellers with HWVSP tokens directly from their wallet.

Blockchain and tokens are necessary to achieve full transparency of payments, anonymity, and for reaching the full decentralization of the video platform, both in terms of video storage, and mutual settlements between users.

All mutual settlements between advertisers, content creators, users, sellers and buyers are carried out by HWVSP tokens: this will directly boost demand for HWVSP tokens.

Roles and Responsibilities

-Designed architecture for ICO for crowdfunding.

-coding was done for ICO with all phases (Airdrop, Early bird offer…etc)

-Developed first web page for raising funds from ICO model and second webpage has been developed for video sharing.

-Preparation of whitepaper.

Site address: helloworldvsp.com, helloworldvsp.in

Project Description:

GrainCorp was founded in 1916, and was originally part of the NSW Government’s Department of Agriculture.

Since then, GrainCorp has been instrumental in leading the development of the bulk grain handling system in Australia. Our first bulk grain elevator was built at Peak Hill, NSW, in 1918, and Australia’s first bulk grain export terminal was located in Sydney and was commissioned in 1922.

In 1992 GrainCorp became one of the first Government organisations in Australia to be privatised, and in 1996 was the first Australian bulk handler to trade grain in the Australian domestic market.

GrainCorp was listed on the Australian Stock Exchange in 1998, and acquired Victoria-based Vic grain in 2000, and 60% of Allied Mills in a joint venture with Cargill Australia in 2002. It acquired Queensland-based Grainco in 2003 and made its biggest acquisition, its international malt business, in 2009.

Grain corp have the business units like Storage & Logistics, and Ports Network, Malt (One of the largest malt in the world) and Allied Mills.

Individual's role on the project

· Worked on developments and Enhancements.

· First level support for loading issues.

· Handling production support issues (high and low priority issues).

· Working on Major RFCs (Broadcasting reports,), Publishing Bex Reports in

Portal.

· Worked on Performance optimization on cube.

· Worked on Performance tuning on the Bex Report using APD concept.

. Supported Basis from BI side to configure portal with admin roles (RFC creation from source to portal, security roles assignment..etc.)

Project description:

BP is one of the world's largest energy companies, providing its customers with fuel for transportation, energy for heat and light, retail services and petrochemicals products for everyday items.

A single, dedicated SAP platform across all of the Lubricants SPU businesses and functions in Europe will be implemented, to simplify the technical landscape and drive adoption of standard and simplified business processes. The result will be to reduce 31 applications down to 1.

Initially the project was developed in SAP R/3 4.7 and SAP BW 3.5 environment, Later on they it was decided to upgrade it to 7.0 for individual countries, This project involves the End-To-End Implementation of SAP R/3 ECC 6.0, 4.7 incorporating modules. This project will also deliver custom solutions to the client after a detailed functional and technical analysis. Regression testing, User documentation and post go-live production support will also form an important part of this project.

This client is having multiple vendor for IT development, ACE (Own developers), TCS, Accenture and IBM. They have used the multiple technologies like Mainframes, Informatica, SMT tool, Tivoli, SAP, .net, VB, and Oracle DB..etc for their business development.

BP was using the modules in SAP ABAP, SD, MM, CRM, SRM and apart from these modules also using BI for staging of the data and reporting.

The Data flows from R/3 and couple of legacy systems to BW and APO (Vice versa), The planned data (SNP, DP) from APO to BW and by using Informatics server the data will reach SMT tool for their own analysis of reporting.

SAP Application Platform for Project Stack and Production Stack, Any new releases will be built in project stack and then cutover into Production.

The initial solution was delivered and used by Belgium, Netherlands and Luxemburg. Later the development was happened to Rashya, Benelux

At first, NIKE will be implemented in Belgium and the Netherlands (BeNeLux), followed by the UK & Ireland, Germany/ Austria/ Switzerland. Scandinavia, France, Eastern Europe, Poland, Greece, Turkey, Italy will follow.

The current project which I am handling is NIKE, Which is a European wide SAP implementation across three main process areas including Customer Facing, Supply Chain and Finance. These process areas span core businesses of Auto Europe and AIME (Air, Industrial, Marine and Energy) supported by Supply Chain and Finance functions.

Release 1 went live in Apr 2010

Role and Responsibilities: Worked as BI Consultant.

• Individual handling of the tickets for Rashya (European) project.
• Daily monitoring and maintenance of the process chains.
• Maintenance of the transactions ST22, SM21 and SM58 ..etc, Fixing issues.
• Handling the tickets, planning for reload activities.
• Working with Transports.
• Working with special characters especially during transactional loads.
• Complete maintenance of BW server.
• Involved in Regression Testing.
• Exclusively worked on Finance BW (PCA, GL) transition project and played a key person role. Received couple of appreciation mails from client and BP management team.

Project description:

Ace Hardware Corporation is a hardware cooperative based in Oak Brook, Illinois, United States. Ace Hardware was founded in 1924 by Richard Hesse, E. Gunnard Lindquist, Frank Burke and Oscar Fisher in Chicago, Illinois.

ACE Hardware is the retailer for the stores like grocery stores, hardware stores and pharmacies.

They have their own employees nearly 1lakh, they have the products related to lawn &garden, outdooring living, paint, Home goods, Tools, Hardware, plumbing, heating and cooling, Electrical appliances and Products related to Automotive (like Booster cables, lubricants, car leaning suppliences...etc.)

This client is having multiple vendor for IT development, ACE (Own developers), Cognizant and IBM.They have used the multiple technologies like Mainframes, Webfocus, SAP, .net, VB, Oracle DB..etc for their business development.

ACE is using the modules in SAP ABAP, SD, MM, CRM and apart from these modules also using BI for staging of the data.

The landscape of the systems in this project is D-Q-P, The extraction of the data happens from different legacy systems to BI, From BI (till DSO level), From DSO level the data will be sent out to Teradata for the reporting, As the client is using the Web focus reporting tool for reporting we have not developed much Bex queries except the standard queries like query statistics and Data load statistics, apart from these we have the queries like Total pricing cost reports, Total sales report daily, and Total purchase reports daily.

Individually handled the client from BI side, and supported the release and solved the issues during the release(Phase4).

Role and Responsibilities: Worked as BI Consultant. (worked at client location for 2 months and offshore till December 2010.)

• Individual handling of the client from BI side for any kind of issues.
• Daily monitoring of the process chains
• Maintenance of the process chains.
• Adhoc process chains creation.
• Handled the master data enhancements in R/3
• Handled enhancements in BI.
• Worked with transports.
• Fixing the issues proactively.
• BW Data load scheduling, monitoring and troubleshooting data extraction / load problems, checked data consistency and modified the data in PSA before loading it to the data targets, compressed and rollup the data in data targets.
• Process chain monitoring, Solving the issues raised as tickets.
• Interacting with the client during the weekly scheduled meetings.
• Maintaining Reconciliation’s to verify the data in SAP R/3 and SAP BW are same or not after the data loads.
• Interfacing with the users for clarifying queries regarding tickets posted by him.
• BW Data load scheduling, monitoring and troubleshooting data extraction / load problems, checked data consistency and modified the data in PSA before loading it to the data targets, compressed and rollup the data in data targets.
• Worked extensively on LO Cockpit extractions loaded the data from R/3 to BW and used Initialization with delta update and full update methods.
• Setup the Statistical Setup for the LO-Cockpit and used the V3 Update for Delta Management.
• Solved the issues for the Billing document conditions at retail business level.
• Worked with Transports.
• Worked with special characters.

Project description:

The Ericsson Company is world largest communication towers manufacturing, sales and distribution unit. This project has come a long way. Flagged off with a 24 FTE count pilot project Ericsson now boasts a projected 600 plus FTE spread over 250 applications, And about 53,000 employees. Ericsson Head Quarters is in Stockholm, Sweden. The Ericsson Tower Tube is an innovative construction that houses base stations and antennas, fully encapsulating them in an aesthetic, energy-efficient and environmentally friendly tower. It employs cutting-edge design and building materials, and can be built in a variety of shapes and sizes, with customized finishes that make it a natural fit for any landscape. Ericsson has redefined the telecommunications landscape with its cutting-edge Tower Tube. The breakthrough design employs innovative architecture and construction techniques that improve energy efficiency and reduce operator costs, while offering an aesthetically pleasing design.

Ericsson is a world-leading provider of telecommunications equipment and related services to mobile and fixed network operators globally. Ericsson is one of the few companies worldwide that can offer end-to-end solutions for all major mobile communication standards.

Role and Responsibilities: Worked as BI Consultant.

• Transport BEX-requests D-Q-R-P when requested by query developers (Super Users).
• Schedule and monitor periodic data loads from SAP R/3 to BW. Data extraction from R/3, Creating Info Packages.
• Inform super users when reported data is incorrect/not up-to-date and provide instructions what actions to take.
• Involved in escalating high-prioritized tickets regarding extractions and load failures.
• Extensively worked in Data Extraction and Data Staging using LO-Cockpit and used the V3 Update for Delta Management.
• Analyzed and corrected production problems as they occur in the SAP BW system.
• Interfacing with the users for clarifying queries regarding tickets posted by him.
• Maintaining Work History for all the tickets until it is closed down
• Maintaining Reconciliation’s to verify the data in SAP R/3 and SAP BW are same or not after the data loads.
• Scheduling the packages and DTPs.
• Handling Tickets and make the project corrections with design documents.
• Process chain monitoring, Solving the issues raised as tickets.
• Interacting with the client during the weekly scheduled meetings.
• Involved in solving the tickets related to entire supply area. Mainly solved the issues related to Inventory, Sales and purchase related areas.
• Maintaining Work History for all the tickets until it is closed down.
• BW Data load scheduling, monitoring and troubleshooting data extraction / load problems, checked data consistency and modified the data in PSA before loading it to the data targets, compressed and rollup the data in data targets.
• Maintenance of BIA server.

Role and Responsibilities: Worked as MDM Consultant.

• Monitoring MDM application
• Repositories includes customer, vendor, Material
• Worked on Data manager, Import Manager, Console, and Syndicator.
• Maintaining qualified tables with the updated data.
• Importing of data into MDM.
• Validation of the data.
• Data masking.
• Maintenance of Lookup tables.
• Worked on Matching strategies.
• Mass file uploads using Import maps.
• Worked on validations in Data manger.
• Merging and data unmerging functionality. Finding the merging information of non-winning records.
• Handled various issues in Production including high priority tickets such as syndication failures from MDM to ECC and importing failures from ECC to MDM, Investigated Inbound and Outbound IDOCs in ECC related to the syndication and importing failures.
• Active participation in supporting new repository Material master data.