What is SAP Project Management,SAP Project System

What is SAP Project Management,SAP Project System

• SAP PS is a project management tool that provides you with support in all Knowledge areas of the project.
• SAP PS provides structures that you can use to model and organize projects flexibly. You can plan and monitor dates, costs, revenues, budgets, resources, materials, and so on, in these structures using the relevant tools and reports from SAP PS.

Integration

• The Most powerfull from SAP PS is the integration among others main functional with most affected in project.
• The high degree of integration between the Project System (PS) and other R/3 application components means that you can plan, execute, and account for projects as part of your normal commercial procedures.
• This means the Project System has constant access to data in all the departments involved in the project.

An Overview of Project Procedure:
• Project Structuring (Project Builder,Project Planning Board)
• Detailed Planning (Cost,Revenues,Payments,Dates, Materials,Capacities,Resources)
• Execution (Production, Material Procurements,activity allocation,Confirmation,Billing,Periode end closing,Progress analysis)
• Completion (Periode end closing, Archiving,Technical Completion)

Organizational Structures
Structures

• For successful project management you must model all the processes in a project
and be able to display their structure and the sequence of events.
• The Project Systems make this possible at all times by providing basic data, standard structures,and templates which greatly simplify creating and planning projects.
• Before you can run a project in its entirety, you must first describe the project goals precisely and create a structure for the project activities that are to be carried out. A clear project structure is the basis for successful project planning, monitoring, and control.
• Depending on the nature of the project and the emphasis in controlling, structure your project using a work breakdown structure (WBS) or a network. The activities in a network can be linked using relationships to activities in the same network or in another network.

Project Definition
• The project definition is a general description of the project you want to manage.
• You use it to record the ides behind the project. At this point in time you do not need to create a work breakdown structure or activities. Later on, the project definition is the container for all objects that are created within a project, for example for WBS elements, network activities.
• It also contains organizational data that is valid for the whole project such as:
o Controlling Area
o Business Area
o Company Code
o Plant
o Factory Calendar

Work Breakdown Structure
• The work breakdown structure (WBS) is a hierarchical model of the project, providing a view of the phases and functions. It splits the project into manageable parts.
• The work breakdown structure
o Forms the basis for planning, coordinating, and controlling the project
o Shows the work, time, and money spent on a project
o Makes the structure of a project transparent and documents responsibilities
o Forms the basis for both budgeting and the planning and analysis of costs
in project controlling

Network and Activities

• The actual processing of a project is planned using networks.
• Networks describe Networks the sequence in which projects are processed.
• The main elements of networks are activities and relationships.
• Networks form the basis for planning, analyzing, and monitoring time schedules, costs and resources.
• You use activities in networks to plan personnel resources, other capacities, Activities materials, PRTs, and service requirements. You can add detail to your planning by using subnetworks and activity elements.

• For tasks that require capacities (machines or personnel) in your business, create internally processed activities.

• For tasks that are to be processed by outside contractors, use externally processed activities. Such activities form a link to Purchasing. You can refer to a purchasing info record that contains information such as prices and delivery dates for external processing. The system automatically creates a purchase requisition from the data in an externally processed activity.

Milestones
• Milestones are events in a project to which particular importance is attached or which trigger a predefined function.
• In general, they indicate transitions between different phases or departments. You can assign milestones to both WBS elements and activities.
• In the Project System, milestones are used to:
o Trigger predefined functions in network activities
o Determine the percentage of completion (milestone technique in progress
analysis)

• You can use predefined milestone functions in networks to trigger a sequence of steps.
Examples include:
o Releasing activities
o Including standard networks
o Creating networks and subnetworks
o Triggering workflow tasks
Templates
• Although every project is unique, it is often possible to standardize structures and processes, in whole or part, to use them again.
• You can use these templates to keep a record of structures specific to your business and product; this can help reduce work and product management in later projects.
• For example, you only have to create a standard network once and you can copy it many times to create new networks with the same structure.

Simulations
• You use simulation to plan alternatives, that is the classic What-If cases.
• They are created manually, can be changed and deleted.

Project Success is Always Measured in Business Value,

Project Success is Always Measured in Business Value,

‘If you build it, they will come’ But if you build it and it doesn’t provide value, they will soon leave!

We need to focus on the fact that the project is only as successful as the business value it adds to the organization.
 If we’re producing a something, the evaluation factors for “success” are clear. We need to use our project management skills to bring this product to market quicker so we can get it sold to a large portion of the customer base before the competition is able to produce a similar or even better product.
 Without connecting the project to the business need, great product could be a failure from the organization’s return on investment (ROI) point of view.
 Customer satisfaction includes in business need criteria.
Motivating teams and making difficult decisions on the spot become easier when we understand specifically how the completion of this project is intended to benefit the company.

In order for a project to be successful, the project team must:
 Select appropriate processes required to meet the project objectives,
 Use a defined approach that can be adopted to meet requirements,
 Comply with requirements to meet stakeholder needs and expectations, and
 Balance the competing demands of scope, time, cost, quality, resources, and risk to produce the specified product, service, or result.

What is Project?

What is Project?

In PRINCE2 , a project is : A temporary organization that is created for the purpose of delivering one or more business products according to an agreed upon business case

In PMBOK , a project is : A Project is a temporary endeavor undertaken to create unique product, services or result.

Project Characteristic:
 Temporary nature of projects indicates a definite beginning and end.
 The end reached:
• When the project objectives have been achieved
• or when the project is terminated because its objectives will not or cannot met.
• Or when the need of project no longer exist
 The Project is a finite process !, not floating or never ending or regular or periodically or repetitive processes,
 A Operation definition : Permanent endeavor undertaken to create unique product, services or result.
 Temporary Does not mean short duration.
• Projects can be large or small and take a short or long time to complete.

 Unique : Every Project is unique. (Things are not always what they seem.— Phaedrus, Roman writer
and fabulist)
Deliverables Project is always unique, intangible or tangible
 Tangible could be phisically such as created factory, bridge, create software etc
 Intangible such as change culture or Learning Project Management Is could be a Project

 A Project comprises a number of activities that must be completed in some specified order, or sequence.
o To determine the sequence, it is helpful to think in terms of the following inputs and outputs:
 What is needed as input in order to begin working on this activity?
 What activities produce those deliverables as output?
 When you know what your dreams are, you know what your problems are.
o Project is A dream with a deadline
 Want to build new house?
 Want to start a new business?
 Want to new car?
o Each dream with a deadline or an opportunity we want to realize is a project. And that project defines the problems we face. And when we face those problems and solve them, that’s a project, too.
 The project must have goals with precisely described and activities to be carried out must be structured
 Project is Balancing the competing of constrains: Scope, Quality, Schedule, Budget, Resources,Risk
 Projects are managed using project management.
 Projects is cross functional: involve a team of people with different skills working together to introduce a change, often cross from functional dept within organization.

Why Projects Fail?, Kenapa Project Gagal.

Why Projects Fail?

• Integration Management

o Lack of coordination across area
o Lack of progress control

• Scope
o Lack of a clearly defined purpose & Scope
 A project manager should avoid committing to either development schedule or budget before the project has been adequately defined. In most cases, a firm commitment can be given only after the requirements are concluded.
 If the requirements of a project are not met, then adhering to the budget and schedule becomes meaningless.
o Inadequate requirements
o Difficulties in concluding the project
o Changing scope, too often change request
o Scope on contract , significantly different with practical

• Schedule

o Lack of planning, a poor estimation of duration, Fail to update & respond planning.

• Cost
o Insufficient budget
o Budget exceeded
• Quality
o Nonconformance with quality Standard
o Produce product being delivered that do not meet the Product specification , fitness for use, customer’s requirements.
o Values delivered that work differently than expected,
o Not aware with critical to quality

• Human Resources
o Skill & Knowledge
 Inexperienced Project Manager & Project team member
 Skill & competencies Project team member under standard
o Lack Resources
o Frequently of Turnover resources
o Values & Behavior mis-alignment with project’s objectives
o Lack training & development
o Lack Productivity
o Lack Motivation

• Communication
o Lack of communication
o Insuficient measurables & report
 If you cannot measure where you are you cannot demonstrate that you are improving

• Risk
o Cannot manage risk
o Cannot predicts potential problem
o Worst preparation for contingency plans

• Procurement
o Vendor selection
o Vendor readiness & Performance
o Lead time

• Stakeholder
o Behavior & Cultural
o A customer or user will not always provide the correct requirements. It is often the Project Team Member responsibility to ask the right questions in order to collect the necessary information.

Sekilas Microsoft Project server Business intelligence

Microsoft Project server Business intelligence,

Judul nya keren ya :),

Business intelligence seperti yg anda ketahui adalah big data, menemukan emas dlm timbunan data2.

Pernah ke warehouse ?

Yg luas besar berhektar2,
Kontras dgn barang2 besar ribuan dan atau yg kecil ratusan ribu, bgmn cara me manage utk tdk deadstock atau  kita scrap dibuang percuma.

Konsepnya semua data adalh berharga namun bgmn cara mengolah menjadi lbh emas.

Kl term marketing , analisa data, behavor -opinion- user attitude- how they use- compare ,
categorized by segmentasi :needs, user, pattern, buying criteria, lalu create atau enhance product,
Menjadi limpahan revenue derass.

Sama juga diproject,

Didlm portfolio project ada byk project itu mungkin setahun, bgmn bila 5 thn?

Berapa task activities didlmnya?

Berapa resource utilization?
Berapa rata2 task yg paling lama dikerjakan atau yg byk memakai resource.
Brp rata2 waktu yg dibutuhkan utk setiap tahapan projects?

Dr project mandates ke kick off meeting brp rata2 waktu.
Dr bast ke  milestone  AR payment brp waktu.
Apa saja issue atau risk yg sering muncul ?

Perumpamaan seperti menggunakan pivot, anda bisa mengolah data yg bisa berguna utk meningkatkan kualitas dan efisiensi.
Gaji ke 13 dan 14 pegawai negeri belum turun tp harga2 sudah berubah, kondisi cash flow yg terancam akan jadi kontras bila tdk segera dilakukan efisiensi.

Inti dr BI di msp server adlh:

Measurements : day, week, currency dll

Dimensioning: task dlm wbs, wbs dlm project dll.

Attributes: sebagai pendamping utk lbh mendetailkan dimensioning.

Apa yg dihasilkan bisa menjadi bahan top executive, sdh jadi kewajiban kita yg dibawah memberikan panduan data utk arah kebijakan yg lbh tepat real dan cepat.

Reporting tsb juga bisa menjadi lesson learned yg sangat akurat, bukan subjective atau dibuat2. Atau malah kita tdk pernah menggunakan data lesson learned.??

.tenang itu sudah jamak, wkkk.

Msh byk lagi yg blm dibahaas , 🙂