XI Implementation project plan

Hi All,
Can somebody help in getting a typical XI implementation project plan, to understand the complexity and risks involved in the implementation
Regards
Anjul

As far as I know there is now such thing as an implementation plan, but there are several steps that you should always carry out when introducing XI.
First of all, know why you wanna use it. See how many interfaces are there in the landscape, what kind of information is exchanged between the different systems, how frequently are messages sent from one system to another, how big are these... If you would like to know details about the size of the hardware involved, you should have a look at service.sap.com/quicksizer, which will give you a first idea about the size of the machine you should run on.
Bear in mind how many system you would like to have, prd,dev,qas etc and how to carry out transports between them.
Don't forget that you should have a backup strategy, an archiving strategy, disaster-recovery strategy and proper authorization concept in mind.
But if you are looking for a special document I cannot help your further.
Regards,
Jaime

Similar Messages

EP6 implementation project plan template needed

I'm looking for a basic template for an EP 6.0 implementation that will create a basic starter portal, only accessing other SAP applications. Does anyone have one they can send me?

Hello,
We follow ASAP Implementation Road map for Portal Implementations. Please find the below link, which gives you information about all the project phases, templates for each phase etc.
https://media.sdn.sap.com/html/submitted_docs/Implementation_Roadmap_EP/Enterprise%20Portal/index.htm
Hope this solves your problem. Don't forget to assign points ... ;-).
Best Regards,
Srinivas.

Study business process requirements in sd implementation project?

how to study business process requirements in sd implementation project?

Hi chandu,
I will suggest you first go through the document given below
SAP Implementation is the whole of processes that defines a complete method to implement SAP software in an organization. The SAP implementation method described in this entry is a generic method and not a specific implementation method as such. It is based on best practices and case studies from various literature sources and presents a collection of processes and products that make up a complete implementation method to allow any organization to plan and execute the implementation of SAP (ERP) software.
Concept Definition
CHANGE MANAGEMENT ***Activities involved in (1) defining and installing new values, attitudes, norms, and behaviors within an organization that support new ways of doing work and overcome resistance to change; (2) building consensus among customers and stakeholders on specific changes designed to better meet their needs; and (3) planning, testing, and implementing all aspects of the transition from one organizational structure or business process to another. (www.gao.gov)
CHANGE MANAGEMENT DOCUMENTATION All documentation that is required and being delivered whilst performing change management, e.g. the functional test cases and all the other documents a new end-user of SAP requires and the various tools and approaches used to manage change by the TSO. (Anderson, 2003)
COST OF OWNERSHIP ANALYSIS Determination of where and when the costs are inquired within the context of the SAP solution stack and ongoing operations. The analysis addresses all internal and external costs, both one-time as well as recurring (Anderson, 2003)
CUTOVER The process of transitioning from one system to a new one (Anderson, 2003)
CUTOVER PLAN All documentation related to planning, preparing and executing cutover, describing how to lock down the system from a technical change management perspective, preparing the TSO for its new role and rolling out the SAP graphical user interface to all future end users. (Anderson, 2003)
DATA CENTER A data center is a facility used for housing a large amount of electronic equipment, typically computers and communications equipment. (www.wikipedia.org)
DATA CENTER REQUIREMENT A requirement for the SAP data center, i.e. a physical requirement like power requirements, a rack requirement, a network infrastructure requirement or a requirement to the network server. (Anderson, 2003)
DISASTER RECOVERY (DR) REQUIREMENT Requirement that focuses on downtime that lasts many hours to days or even weeks (Anderson, 2003)
FUNCTIONAL TEST CASE A set of conditions or variables under which a tester will determine if a certain business process works (www.wikipedia.org)
HIGH AVAILABILITY (HA) REQUIREMENT Requirements that describes the amount of time that the system needs to be available to satisfy the needs of the users. (Anderson, 2003)
INSTALLATION DOCUMENTATION All documentation related to the installation of an end-to-end SAP solution (Anderson, 2003)
OPERATIONS MANUAL The collection of current state system documentation, day-to-day and other regularly scheduled operations tasks, various installation and operations checklists and how-to process documents. (Anderson, 2003)
SAP SAP AG is the name of the biggest European software company. The head office is in Walldorf, Germany. SAP was founded in 1972 as Systemanalyse und Programmentwicklung ("Systems Analysis and Product") by five former IBM employees in Mannheim, Germany. (www.wikipedia.org)
SAP IMPLEMENTATION PROJECT PLAN A comprehensive project plan that contains all products that are delivered whilst performing an SAP implementation project (Anderson, 2003)
SOLUTION STACK Set of software subsystems or components needed to deliver a fully functional solution, e.g. a product or service. (www.wikipedia.org)
SOLUTION STACK PARTNERS LIST A list of all vendors that deliver the products that make up the SAP solution stack (Anderson, 2003)
SOLUTION VISION A vision of the future-state of the SAP solution (Anderson, 2003)
STRESS TEST PLAN A test plan that is focused at determining the stability of a given system or entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results. (www.wikipedia.org)
TEST PLAN A detail of how the test will proceed, who will do the testing, what will be tested, in how much time the test will take place, and to what quality level the test will be performed. (IEEE 829)
TRAINING The acquisition of knowledge, skills, and attitudes as a result of the teaching of vocational or practical skills and knowledge that relates to specific useful skills (www.wikipedia.org)
TRAINING PLAN Consisting of training units, a training plan is the result of hierarchical decompositions of a training goal, tailored according to the learning preferences and prior knowledge of the trainee. A plan is the means by which the trainee satisfies the goal. (www.ece.eps.hw.ac.uk/)
TSO Technical Support Organization. The people that are committed to implementation and management of SAP. (Anderson, 2003)
TSO CHART A chart that depicts the structure of the TSO. (Anderson, 2003)
Activity Sub-Activity Description
Project preparation Craft solution vision Refine and communicate a SOLUTION VISION of the future-state of the SAP solution, to sketch a design that meets both business and financial requirements. The focus should be on the companyu2019s core business and how the SAP solution will better enable that core business to be successful.
Design and initially staff the SAP TSO Design and staff the key positions of the SAP Technical Support Organization (TSO), the organization that is charged with addressing, designing, implementing and supporting the SAP solution.
Sizing and blueprinting Perform cost of ownership analysis Perform a COST OF OWNERSHIP ANALYSIS to determine how to get the best business solution for the least money i.e. to determine where and when the costs are incurred within the context of the SAP solution stack.
Identify high availability and disaster recovery requirements Determine all HIGH AVAILABILITY and DISASTER RECOVERY REQUIREMENTS, to plan what to do with later downtime of the SAP system
Engage SAP solution stack vendors Select the best SAP hardware and software technology partners for all layers and components of the SAP SOLUTION STACK, based on a side-by-side sizing comparison
Staff TSO Staff the bulk of the TSO, i.e. fill the positions that directly support the near-term objectives of the implementation, which are to develop and begin installation/implementation of the SAP data center.
Execute training Train the various members of the SAP TSO, like data center specialists, high availability specialist and network specialists and train the end-users to give all the required SAP knowledge and skills
Setup SAP DATA CENTER Build a new SAP DATA CENTER facility or transform the current data center into a foundation capable of supporting the SAP SOLUTION STACK
Perform installations Install the (My)SAP components and technological foundations like a web application server or enterprise portal.
Round out support for SAP Identify and staff the remaining TSO roles, e.g. roles that relate to help desk work and other such support providing work.
SAP functional development Address Change Management Develop a planned approach to the changes in the organization. The objective is to maximize the collective efforts of all people involved in the change and minimize the risk of failure of implementing the changes related to the SAP implementation.
Address SAP systems and operations management Create a foundation for the SAP systems management and SAP computer operations, by creating a SAP OPERATIONS MANUAL and by evaluating SAP management applications.
Perform functional, integration and regression tests Test the SAP business processes, by executing functional tests to ensure that business processes work, integration tests to ensure that the organizationu2019s business processes work together with other business processes and regression tests to prove that a specific set of data and processes yield consistent and repeatable results.
Final Preparation Perform systems and stress tests Plan, script, execute and monitor SAP STRESS TESTS, to see if the expectations of the end users, defined in service level agreements, will be met.
Prepare for cutover Plan, prepare and execute the CUTOVER, by creating a CUTOVER PLAN that describes all cutover tasks that have to be performed before the actual go-live
Go Live Turn on the SAP system for the end-users
Hope this will help.
Reward Point if helpful.
Thanks,
Raja

Project Plan for EAM analytics implementation.

Hi Experts,
My Boss has asked me to provide him the project plan for this EAM analytics implementation, showing how long will it take for the dashboards to be up with the correct data.
Reason why he is asking this is because initial configuration has been done in BI Apps but prima facie looks like the DATA on dashboards is not correct.
Now he is worried as to how long will it take... and even i am not sure on this as I am new to this..( i m the only one configuring EAM Dashboards - ie only one resource )
Any experiences or helpful advise for this kind of scenario that i can tell my boss or what should be my action plan.
Thanks
Ashish

Any pointers?

Project Plan for ChaRM implementation help

Hi everybody,
I am creating a Project Plan to implement ChaRM in a new project.
This is the first time i am doing that task and i must deliver that plan to a team soon.
So i would like to ask you about comments, idea, missing items on my current plan please
(I voluntarily did not mention Estimated Duration, team to perform, requestor, etc..)
Pre-Check :
- Validate System Component and SP Level
- Request Ids & roles on satellite systems / Build USER IDs & roles created on all satellite
- Verify TMS settings for ChaRm
- RFC Connection creation / RFC TEST
- Activation of cross system Object Locking - CSOL
Project :
- Determin type of project for ChaRm (implementation / Maintenance)
- Create project
- Activate project for ChaRm
- Activate project for task lists
- Id's created in SolMan & satellite
- Establish Business Partners
- Approvals (Change Control process)
- Test creation of Change Request
- Test :Import transports between dev - QA / QA to prod
Thank you in advance
and thx for all the things i understood with all the topics of this forum.

Hi,
Follow RUN SAP Roadmap for Implementing your solutions. Go through [this link.|https://websmp109.sap-ag.de/runsap] This explains Run SAP and how you can plan to implement your SAP solutions (including ChaRM).
Run SAP has 5 phases.
Assessment and Scoping
Define Operations
Setup Operations
Handover into Production
Operations and Optimization
Hope this solves your problem.
Feel free to revert back.
-=-Ragu

Project Plan Implementation

Hi all,
Some body has sent me this URL to see how we plan the project ,but its not opening in my system.
I dont know why, can any one open this and send me the information Please......
Project Plan :
http://help.sap.com/bp_biv270/documentation/BWProjectPlan_EN.mpp
Thanks

Hi,
Check this link.....
http://www.seavusprojectviewer.com/Default.aspx?cid=83666b34-7699-4afb-b23a-eb53fe0353fa&gclid=CM3XzOLEwZQCFQMLewodZBfHGQ
Hope this helps u a lot.........
Assigning points is the way of saying Thanks in SDN
Regards
Ramakrishna Kamurthy

Info on activities involved in various stages in Implementation Project

Hi,
I need some detailed information on activities involved in various stages in a SAP Implementation.
I have seen the earlier threads in the forum on this Topic,but they are very brief.
It will be very helpful for me if someone can provide some detailed document on practically what is done in those stages.
Thanks in advance,
Ashish

Hi,
Based on ASAP methodlogy.
1)Project Preparation
2)Business Blue print preparation
3)Realization
4)Final preparation
5)Post go-live support.
Project Preparation:Phase 1 initiates with a retrieval of information and resources. It is an important
time to assemble the necessary components for the implementation. Some
important milestones that need to be accomplished for phase 1 include
u2022        Obtaining senior-level management/stakeholder support
u2022        identifying clear project objectives
u2022        architect an efficient decision-making process
u2022        creating an environment suitable for change and re-engineering
u2022        building a qualified and capable project team.
Senior level management support:
One of the most important milestones with phase 1 of ASAP is the full agreement
and cooperation of the important company decision-makers - key stake holders
and others. Their backing and support is crucial for a successful implementation.
Clear project objectives:
be concise in defining what your objectives and expectations are for this venture.
Vague or unclear notions of what you hope to obtain with SAP will handicap the
implementation process. Also make sure that your expectations are reasonable
considering your company's resources. It is essential to have clearly defined
ideas, goals and project plans devised before moving forward.
An efficient decision making process:
One obstacle that often stalls implementation is a poorly constructed decision-
making process. Before embarking on this venture, individuals need to be clearly
identified. Decide now who is responsible for different decisions along the way.
From day one, the implementation decision makers and project leaders from
each area must be aware of the onus placed on them to return good decisions
quickly.
Environment suitable for change and re engineering:Your team must be willing to
accept that, along with new SAP software, things are going to change, the
business will change, and information technology enabling the business will
change as well. By implementing SAP, you will essentially redesign your current
practices to model more efficient or predefined best business practices as
espoused by SAP. Resistance to this change will impede the progress of your
implementation.
Business Blue Print Preparation:SAP has defined a business blueprint phase to help extract pertinent information
about your company that is necessary for implementation. These blueprints are in
the form of questionnaires that are designed to probe for information that
uncovers how your company does business. As such, they also serve to
document the implementation. Each business blueprint document essentially
outlines your future business processes and business requirements. The kinds
of questions asked are germane to the particular business function, as seen in
the following sample questions:
1) What information do you capture on a purchase order?
2) What information is required to complete a purchase order?
Accelerated SAP question and answer database:
The question and answer database (QADB) is a simple although aging tool
designed to facilitate the creation and maintenance of your business blueprint.
This database stores the questions and the answers and serves as the heart of
your blue print. Customers are provided with a customer input template for each
application that collects the data. The question and answer format is standard
across applications to facilitate easier use by the project team.
Issues database:
Another tool used in the blueprinting phase is the issues database. This
database stores any open concerns and pending issues that relate to the
implementation. Centrally storing this information assists in gathering and then
managing issues to resolution, so that important matters do not fall through the
cracks. You can then track the issues in database, assign them to team
members, and update the database accordingly.
Realization:With the completion of the business in phase 2, "functional" experts are now ready
to begin configuring SAP. The Realization phase is broken in to two parts.
1) Your SAP consulting team helps you configure your baseline system, called the
baseline configuration.
2) Your implementation project team fine-tunes that system to meet all your
business and process requirements as part of the fine tuning configuration.
The initial configuration completed during the base line configuration is based on
the information that you provided in your blueprint document. The remaining
approximately 20% of your configuration that was not tackled during the baseline
configuration is completed during the fine tuning configuration. Fine tuning usually
deals with the exceptions that are not covered in baseline configuration. This final
bit of tweaking represents the work necessary to fit your special needs.
Configuration Testing:
With the help of your SAP consulting team, you segregate your business
processes into cycles of related business flows. The cycles serve as independent
units that enable you to test specific parts of the business process. You can also
work through configuring the SAP implementation guide (IMG). A tool used to
assist you in configuring your SAP system in a step by step manner.
Knowledge Transfer:
As the configuration phase comes to a close, it becomes necessary for the
Project team to be self-sufficient in their knowledge of the configuration of your
SAP system. Knowledge transfer to the configuration team tasked with system
maintenance (that is, maintenance of the business processes after Go-live)
needs to be completed at this time.
In addition, the end users tasked with actually using the system for day-to-day
business purposes must be trained.
Final Preparation:As phase 3 merges into phase 4, you should find yourselves not only in the midst
of SAP training, but also in the midst of rigorous functional and stress testing.
Phase 4 also concentrates on the fine tuning of your configuration before Go-live
and more importantly, the migration of data from your old system or systems to
SAP.
Workload testing (including peak volume, daily load, and other forms of stress
testing), and integration or functional testing are conducted to ensure the accuracy
of your data and the stability of your SAP system. Because you should have begun
testing back in phase 2, you do not have too far to go until Go-live. Now is an
important time to perform preventative maintenance checks to ensure optimal
performance at your SAP system.
At the conclusion of phase 4, take time to plan and document a Go-live strategy.
Preparation for Go-live means preparing for your end-users questions as they
start actively working on the new SAP system.
Post Go-live Support:The Go-live milestone is itself is easy to achieve; a smooth and uneventful Go-live
is another matter altogether. Preparation is the key, including attention to what-if
scenarios related not only to the individual business processes deployed but also
to the functioning of technology underpinning these business processes and
preparation for ongoing support, including maintenance contracts and
documented processes and procedures are essential.
Regards
Ravi Shankar.

Deliverables in implementation project?

Dear Gurus,
what are the deliverables in implementation project?

Hi,
For quick understanding
Ensuring successful implementation of a project, the Project Scope is a vital and critical component containing with documents of the projectu2019s deliverables with Scope and out of scope. In Project the background need to mention the project definition, Objective, Deliverable, Scope and out of Scope. The scope statement is an agreement between the project team and the project customer by identifying both the project objectives and the major project deliverables (what is possible).
The deliverables part conations:
1. Development of a project plan( you can have methodology or tool to implement) for overarching project
2.Development of project plans for associated project( GAP or Parallel Activities)
3.Development of a communication plan
4.Production of monthly project status reports to document progress
5. Production of monthly report
6.Production of a final report
7.Production of project completion report
8.Project review (Continuous improvement)
For check the links:
http://www.thespot4sap.com/Articles/SAPImplementationRisks_12.asp
http://iris.tennessee.edu/Blueprint/Project%20Charter.doc
Regards,
Biju K

Solution Directory - How to lock a business process for a implement project

We have Solution Directory assigned to a maintenance project and I understand the checkout/checkin process and how it locks the business process in the Solution. What is the best practice when you are starting a new IMPLEMENTATION project that will impact existing business processes that are in the Solution? I know that I can copy from the solution to build the new project, but it doesnu2019t lock the BP from the solution.
I have a new Implementation project, that i want to checkout/pull existing business processes for the Solution Directory.
*How can these Business Processes be "locked" in Solution Directory as they are with a Maintenance project?*

Kelly,
You would use the maintenance project to make daily modifications.
Consider the case of a O2C business scenario. You need to almost make daily configs etc, which get pushed through, such things will go into a maintenance project.
But if you plan to enhance O2C with a CRM front end or include a better planning solution or TPM or something, then you are looking at an implementation project.
Rule of thumb. Short Scale changes : Maintenance Project, Long term/major enhancements : Implementation Projects.
Also In this case to speak about the lock down. Well the Solution Directory kind of takes care of that for you.
I am assuming that you have a solution populated with business processes. So now if you want to enhance it with a new functionality, you would use an implementation project. So when you define the implementation project, and then navigate to Solar01, and try to add business scenarios , ensure that on the Structure tab you select the Solution as the source. This ensures you are copying content from your current, updated, productive solution. Once you do that, the implementation continues on its track, whilst daily support processes are managed with the check-in / check-out functionality of the Solution and the Maintenance Project.
You technically do not need to lock the business processes down, since the Compare and Adjust functionality of a solution will help you identify the deltas between the Solution and the implementation project and you can always make those adjustments post go-live and thus just update the Solution at one shot. Also remember that with SolMan 7.1 the Compare and Adjust functions can be used with Template, Implementation and Solutions in any permutation-combination.
Hope this helps.
Plz let me know if you need any additional information
Cheers!!

Role of a Security Consultant in an SAP implementation Project

Hi All,
What is the role of a Security Consultant in an SAP implementation Project and the stages in which he is involved?

Hello Mohammed,
The role of a Security consultant in any SAP product implementation (not just GRC) is wide enough and it's hard for anyone to sum up on a single forum post. Still I can give you some pointers.
Security consultants come from different backgrounds, some from networking, database administration, infrastructure and even development like me. They contribute enormously to any product implementation from scratch (landscape design) to go-live (and continuous maintenance) so they are active on every phase of the implementation.
Following are some of the activities they may perform (or participate)
-System Landscape Design (work closely with BASIS and DBAs)
-Check Infrastructure feasibility from security perspective (For Portals exposed to internet or extranet work closely with network providers for firewall security, VPS etc.)
-Propose security guidelines, access policies, disaster recovery plan, business continuity roadmap (work closely with information security consultants and internal auditors or risk management teams)
- Implement SAP solution specific Security measures (involves almost every SAP solution) for example: SAP R/3 security, GRC, BW/BI, HR, FI, Portal security etc.
- participate in application integration for example: LDAP, IDM, SAP UME, shared directories etc (User master records security is on high priority).
- Check for any possible backdoor access vulnerabilities (ex: open RFCs, function modules like ping_rfc), and it involves almost all SAP solutions and there are special procedures to analyze such vulnerabilities.
there are many such activities that a security consultant perform on day to day basis. Please do not interprete the above mentioned activities (entirely) as a criteria for any security consultant profile. There are many many possibilities for a security consultants to work from pen testing to SoD violation remediation. That's why I said it's not easy to sum up security.
Always remember, Security and GRC are two sides of a coin they work together. however GRC is more of a combination of policy, regulation, events and involves management participation whereas security is a purely technical practice.
You may also be interested to know what it takes to become a forensic security specialist. Take a quick look at [http://amudee.com/?p=378|http://amudee.com/?p=378]
Best Regards,
Amol Bharti

Need urgent help in listing out checklist from DBA prespective for BI Implementation Project

Hello Guys,
We are in Designing phase Data Modeling of PDW/APS Implementation Project.
I need urgent help in making a checklist from a DBA perspective.
Like what are things ill be needing at a time of implementation/Deployment.
Your expert comments and help will be highly appreciated.
Thank you,
Anish.S
Asandeen

You can get good summary of checklist from this article about
DBA checklist for data warehousing.
Which highlights on below pointers:
New system or old. (I.e. Up-gradation vs starting from scratch)
Complexity of SQL Server architecture
SQL Server storage
Determining SQL Server processing power
SQL Server installation consideration
SQL Server configuration parameter
SQL Server security
SQL Server Database property
SQL Server jobs and automation
Protecting SQL Server data
SQL Server health monitoring and check ups
SQL Server ownership and control
based on my real time experience, I will suggest you to keep an eye on
Load performance (It will be useful when your database(Warehouse) will have huge amount of data)
System availability (Check for Windows update and up time configuration)
Deployment methodology should be planned in advance. Development of packages and respective objects should be done systematically.
Source control mechanism
Disk space and memory usage
You might or might not have full rights on production environment, so be prepared to analyze production environment via Select statements [I guess you got my point]
Proper implementation of Landing , Staging and Mart tables.
Column size (this can drastically decrease your database size)
Usage of indexes (Index are good, but at what cost?)
I hope this will assist you in building your check list.

Change Request Management for Implementation Project

Hello gurus!
I have a problem with execution change request in implementation project.
I have created Implementation project and task list for him."Change request management" is active for this project.
I can create document Change Request, but I can not to create Correction linked with Task plan...
Dmitry.

HI,
Have you verified if your project definition is setup correctly ? Please verify with some of the steps available in the blogs
First steps to work with Change Request Management scenario
/people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
Change Request Management scenario: Usual questions
https://weblogs.sdn.sap.com/cs/junior/view/wlg/15116
Change Request Management scenario: Working examples
/people/dolores.correa/blog/2009/07/23/change-request-management-scenario-working-examples
Hope this helps.
Cheers
Sh

Bulk Import Projects along with Project Plan

Hi,
I am working on a requirement to bulk import Projects into Ms Project Server along with associated Project Plans. I have checked Solution Starter Bulk Create source code. However, the source code doesn't check-in project plans associated with
projects.
It just creates Projects. I am looking for approach and alternatives to implement this requirement. Any help in this regard will be appreciated.

Hi,
From experience you will be able to create Bulk project up to Project details only , for schedule level consider using PSI to Add tasks under the projects.
Regards, Syed Faizan ur Rehman, CBPM®,PRINCE2®, MCTS

SAP IDM 7.0/7.1 Project Plan and Architecture Landscape Diagrams

Need help in identifying whether there is anybody that has a generic project plan along with resources needed in implementing IDM 7.0/7.1. I am also looking for a generic landscape diagram. Any help would be appreciated.

Matt,
Interesting question and one that I think we can answer, but we need a few specifics first (even for a generic)
1. Are you using 7 or 7.1? This is a biggie since there are big differences in implementation.
2. What's your source for Identity data? What are your targets? Even a basic of (Source is HR, targets are ERP, LDAP and badging app)
3. What workflows are you implementing?
4. What is your development approach? Dev / QA / Prod? This can be important too.
For architecture info, take a look at some of the documents available from SAP.
Anyway, a very generic would be:
1.0 Identify requirements
1.1 Sources
1.2 Targets
1.3 Workflows
2.0 Development Environment
2.1 Install Core Components
2.2 Install IdM
2.3 Connector creation
2.3.1 Source (X)
2.3.2 Target A
2.3.3 Target B
2.4 Workflow creation
2.4.1 Notification Tasks
2.4.2 Self Service Tasks
2.5.3 ...
2.6 Unit Testing
3.0 QA
Feel free to contact me if you have further questions

Managing the administration in implementation projects

Hi all,
I have been using the Solution Manager in implementation projects for 2 years now. However, I'm having difficulty on managing the project schedule using the administration tab in transaction solar01 and solar02:
1.     Unlike MS project, for example, you cannot define a connection/ link between the structure elements, which means that if you have to change the start time for a process in the administration tab, i.e., it has no effect on the other processes/ steps' start time, even when you know that there should be an effect.
2.     You cannot put partial person days, for example 1.5 PD or 0.4 PD.
3.     As far as I know, if you export the project structure to a MS Project file, it is not possible to import the changes made in the file back to the Solution Manager.
For that reasons, some customers and project managers prefer to export the project structure to MS Project and manage the project schedule and resources in that separated file.
I would appreciate it if you could give me an advise based on your experience, on how to better manage the times in an implementation project, using the Solution Manager.
Thank you,
Adi

Hi Adi,
I have also been using SolMan since May 2004 (from 3.1 days). Unfortunately, in my view, the functionality of Admin Tab hasn't kept up in pace as with other features of SolMan.
My suggestion is not to use it for active day-to-day tracking for the limitations you have pointed out as also for it not being the best-of-breed to manage Project Plans of a multi-location, multi-stream project.
I have, at best, used Admin Tab for Keywords and Team members - for information sake.
Also, if you use a Template Project -> Implementation Project copy, Admin tab is not included as part of 'Compare and Adjust' functionality - which means that if the same Team Members and Keywords are required on Implementation Project, you cannot get them inherited.
I am sorry that my answer kind of confirms your findings and helplessness as opposed to providing any solution. But, that's my honest sum-up as well.
Regards,
Srini

XI Implementation project plan

Similar Messages

Maybe you are looking for