Related Change Request (Cr) #: 3303 Related Cr Release Date: June 18, 2004 Related C: Fill & Download for Free

It depends on the project.Fixed price is recommended when:The scope is clearly defined and the outcome is 100% known.The materials are complete and well-understood by the development team.The timeline is realistic.The budget matches the scope and the timeline.It’s predictable, transparent and easy to manage. You get the requirements, client gets the price. Easy peasy.On the other hand, it doesn’t give much flexibility, it has a bad impact on communication and it doesn’t build any relation. It is possible that you will waste much time convincing your client that “it’s not a bug, it’s a feature”, while he tries to convince you that “it’s a part of the scope”. Limited contact with the client and pre-defined scope may make the team disconnected from the product in a business sense.Also, while developing a product this way, sticking strictly to the scope, the chances of building a useless product are higher. Project development isn’t a map where everything’s in place and all directions are known, it’s an ongoing process where you have to be responsive to changes. But there is no flexibility in responding to those when we work in a fixed price model. If you come to a realization that you need an additional feature, the scope will change. You will then need to go through formal Change Request (CR) process, which ends up with signing an appendix to the original agreement.Does it mean that we should rather go for time & material contract?Well… Not always.T&M contract allows both parties to work in an agile way. That’s because we can react to changes and learn with each iteration. When the development is divided into sprints, at the end of which a functioning feature is delivered, there is room for adjustments. Every iteration is an opportunity to test whether the development is going in the right direction. Agile way of working creates a transparent relationship between the client and the vendor, thus making it a partnership. The team is more involved in the process of developing the product and connected with it on a business level.Sounds good? Ok, there is one problem. Some clients don’t want to work with T&M contract. First, it requires trust. If they don’t trust you, they may be afraid that it will be in your interest to burn maximum hours. There’s also a potential risk of running out of money along the way of developing the product.Here is a good article comparing pros and cons of both types of contract: Fixed Price vs Time & Material. What type of contract should I choose?The solution may be to make a mix of both. You can start with fixed price for the proof of concept, and then go for T&M with the further development.In our experience at Neoteric, we’ve found that starting small with a fixed price and later migrating to time and material is often the best model. During the first stages of development, fixed price will work in most cases (unless you’re dealing with highly R&D project), so you can see how the cooperation is going, the process will be predictable and transparent. Later on, as the complexity of your product unfolds, you will need more flexibility, dynamic work scope, and better timing. And that’s when T&M steps in.

Please find below some roles of Informatica admin which you can mention in ur resume :1.To understand the business needs and deploy changes in production environment for the optimal solutions in data warehousing domain2.Debug the sessions by utilizing the logs of the sessions.3.Deployment /Migrations of Repository folders and objects from Development to Test and from test to Production environment4.Performing code refresh activity from a higher environment to lower environments.5.Interact with UNIX and Database Administrators to create and maintain each Power Center instance.6.Independently perform complex troubleshooting, root-cause analysis, solution development.7.Create and manage users, groups and folders. Ensure appropriate privileges are assigned to the different users.8.Interact with end users to resolve issues with Informatica Power Center.9.Coordinate with Informatica support for patches and bug fixes.10.As per Change requests (CR) migration of objects in all phases (DEV, QA and PRD) of project and trained developers to maintain system when in production.11.Managing nodes, Domains, Repository services and Integration services.12.Creation and backup, restore for Informatica Repositories...13.Worked with UNIX / DB2 DBA team related to OS and Database related issues.14.Monitoring the Jobs and sever space availability and CPU Process.15.Developed, Modified and Tested UNIX Shell scripts and necessary Test Plans to ensure the successful execution of the data loading process.16.Co-ordination with project team on application related issues and performance issues.17.Recommend and implementation of automation for known and recurring activities/issues.18.Monitoring the Workflows using Workflow monitor.19.Running of Workflows based on Requests received from Project teams.20.Ensure stability in support services, by identifying root cause of the issues in infrastructure with the help of engineering and other teams within Pfizer/ vendor support teams.21.Preparing standard operating Procedures for related Informatica issues.22.Preparing weekly and monthly progress report.23.Help new Informatica projects get started.24.Informatica installations25.Unix to Linux migration26.Upgradation

There are no any terms in SAP BW support projects like BR and DR.Here are some in context to the same:CR - Change requestCD - Change directoryIA - Impact analysis (A document known as as Impact Analysis document needs to be provided before making any change to the existing flow, which shows the possible impacts on the already existing development work).Most of the companies does use SAP Solution Manager (Solman) and there are some protocols to use it. A ticket from the client’s side will be raised and will be assigned to a particular developer by the reporting manager, a developer in turn will get a notification in the form of a support message in the Solman and in the mail as well notifying about the requirement. After this, a developer will select BIcharm as the project (there are different projects you need to choose one for BW and other for any functional change or any other module) in the support phase in order to make any changes in any of the report or else in any flow.After then a CR will be created, then a developer will change the ticket’s status as “in process” and will create an IA (Impact analysis document) as well. And then after certain approvals, he/she will make changes as per the client’s requirement, which then be tested and reconciled along with the one who has requested the change. After getting satisfied with the work done by the developer, the manager will close the ticket with the consent of the requester.So, now continue to the topic, probably you may find BR and DR terms in a SAP FI related project, in form of voucher codes as:BR - Bank receipt voucherCR - Cash receipt voucher.Cheers!! :)R A J A T