Steering projects. Integrating systems.
We take on project management and project leadership for your technical project and keep schedule, costs, quality and risks transparently in view. Together with specialist partners engaged for each project, we deliver and integrate technical operational infrastructure for your mission system.
We agree the scope of services, partner contributions and test and acceptance criteria with you for each project.
Project status
Illustrative example
Degree of completion
58%plan 62%
Actual costs
61%of budget
Forecast total cost
98%of budget
Decision gates
- Project approved
- Requirements defined
- System designed
- Units realised
- System integrated
- Acceptance declared
Upcoming dates
- Design review, subsystem B
- Steering committee with project status report
- Decision gate: system integrated
- Project approvedcompleted
- Requirements definedcompleted
- System designedcompleted, with conditions
- Units realisedin progress, 2 weeks behind, recoverable
- System integratedplanned in 6 weeks
- Delivery completedplanned in 14 weeks
- Acceptance declaredplanned in 18 weeks
Work packages
18 / 31completed
Critical path
Integration test, subsystem B
- Plan
- Actual
- today
Upcoming dates
- Design review, subsystem B
- Steering committee with project status report
- Start of integration testing
- Decision gate: system integrated
Planned and actual costs per quarter
- Planned costs
- Actual costs
Planned costs to date
58%of budget
Actual costs to date
61%of budget
Variance
+3%above plan
Forecast total cost
98%of budget
Plan/actual cost comparison as a percentage of budget, complemented by earned value analysis of progress.
Reviews and tests completed
42 / 48planned
Requirements covered by test cases
91 %
Findings by criticality
- 0critical
- 2high
- 7medium
- 11low
Test reports: 38 passed, 4 with conditions. Quality assessment from the QA report.
- highInterface to the mission system not yet finalAction: coordination meeting with the specialist supplier scheduled
- mediumLead time of a key componentAction: alternative source qualified
- lowTest bench availabilityAction: time slot firmly reserved
9 active risks, 4 closed. Extract from the risk register.
Change requests
- 14received
- 12assessed
- 10decided
- 8implemented
Open problem reports
3
Results changed again
2
Problem and change statistics from the change status list.
Specifications
System design
Test specifications
Verification evidence
- completed
- submitted
- in progress
Status of project results according to the V-Modell XT product state model.
Schedule adherence over recent reporting periods
Defects per review
0.5trend falling
Change effort per document
low
Metrics evaluation as the basis for objective project control.
Available today
Project management and project leadership
We support your project from initiation through execution to completion. The goal is for technical systems to be available on time, cost-effectively and ready for operation, and to stay that way. For us, project success comes from effective communication, proven methodology and the appropriate use of resources.
- The right delivery strategyWe tailor the approach to your project, based on classic project management, the V-Modell XT (German standard development process model) or your own processes, and apply exactly the disciplines your project needs.
- Clear roles, shared understandingTogether with you, we define the necessary roles and resources and create a common understanding of the approach among everyone involved.
- Communication and controlWe connect customer, users and specialist partners and manage schedules, quality, changes and configuration through to completion.
What you gain
- 01Better communication
- 02Relieved resources
- 03Early identification of project risks
- 04Targeted control of quality and verification
- 05Costs and changes under control
Services across the entire life cycle
We get involved early and stay with you into operation.
We contribute where the course for a solution is set, and we stay involved until the system is operating reliably.
01Analysis phase
Supporting the analysis
We help requirement owners and project teams to understand the capability gap technically and to grasp the problem behind the requirement.
- Capture the conditionsOperating environment, operation and logistics of the user
- Evaluate solution pathsCommercially available options by performance, time, cost and risk
- Help shape conceptsContributions to logistics, deployment, training and operating concepts
02Implementation phase
Implementation, integration and verification
Together with our specialist partners, we deliver and integrate the solution and support the testing, from the specification of work to handover to the user.
- SpecifyTurn requirements into testable specifications
- Deliver and integrateBring together infrastructure, mission equipment and carrier
- Verify and hand overTests, acceptance and complete documentation
03In-service phase
Operation, sustainment and further development
We support operation, maintenance and further development to the agreed extent, for example through documentation, spare parts concepts and obsolescence management. Responsibilities and services over the service life are defined by contract.
- Logistic supportSpare parts, documentation and training
- Support maintenanceRepair and obsolescence management
- Develop furtherExchange modules, add mission equipment
Our approach
Join at the right point in your project.
We can join a project in different phases: during analysis, when requirements and solution paths are being clarified; during implementation, when a system is developed, integrated and tested; or during the in-service phase, when an existing system is to be adapted or extended. Where and to what extent we contribute is agreed with you. We run development and integration projects according to a structured, staged approach. For Bundeswehr (German Armed Forces) projects, it is embedded in the PBN (Projektbezogene Bedarfsdeckung und Nutzung, the Bundeswehr’s project-based procurement and in-service process) with its analysis, implementation and in-service phases.
Not every project starts from zero. We rely on our modular toolkit concept and, depending on the requirements, join the process exactly where it makes sense.
PBN phase (project-based procurement and in-service use)
Analysis phase · From tasking the FFFmLV (capability gap and functional requirement with proposed solution) to the selection decision
- Tasking the FFFmLV and setting up the IPT (integrated project team)The BAAINBw (Federal Office of Bundeswehr Equipment, Information Technology and In-Service Support) sets up an integrated project team and appoints the ProjLtr (project manager). The PlgABw (Bundeswehr Office for Defence Planning) or KdoCIR/ZDigBw (Cyber and Information Domain Service Command / Bundeswehr Digitalisation Centre and Capability Development for the Cyber and Information Domain) appoints the stvLtrIPT (deputy head of the IPT).
- Project categorisation and project manualThe ProjLtr (project manager) initiates the classification into project categories A to D and prepares the PHB (project manual), taking the project elements into account.
- Prioritised requirements catalogue (PFK)Based on operational scenarios, the IPT summarises the capability-defining requirements. Countersignature within five working days, requirements controlling from the outset.
- Evaluation of possible solutionsAnalysis of the options by performance, time, cost and risk, taking the entire life cycle into account.
- FFFmLV as an economic efficiency analysisInitial situation and capability gap, PFK, demand forecast, options, budget requirements, risk assessment and recommended decision. Time frame of no more than six months.
- Selection decision (AWE)Category A by the GenInsp (Chief of Defence of the Bundeswehr), B by AbtLtg Plg or CIT (Planning or Cyber/Information Technology Directorate of the Federal Ministry of Defence), C and D by the PlgABw or KdoCIR. The document that establishes the requirement and budget for implementation.
Milestone or decision
Simplified procedure for requirements up to EUR 500,000: compact WU (economic efficiency analysis) instead of the FFFmLV, no PFK, classification in category D.
PBN phase (project-based procurement and in-service use)
Implementation phase · From the AWE (selection decision) to the handover of the last unit
- Statements of work (LB)The IPT (integrated project team) details the functional requirements of the PFK (prioritised requirements catalogue) along a system structure. Countersignature before the BAAINBw (Federal Office of Bundeswehr Equipment, Information Technology and In-Service Support) approaches the market.
- Award and contractsThe contracting authority decides on the award procedure and reviews framework agreements and options. From EUR 25 million, submission to the parliamentary budget committee.
- Supporting service deliveryThe ProjLtr (project manager) monitors the contractually agreed performance and manages the contributions required from the authority.
- Integrated verificationContractor’s proof of performance, verification of performance values and operational testing, as early as possible and coordinated with each other.
- Acceptance and readiness for takeoverAcceptance by the customer after successful proof of performance, declaration of readiness for takeover after successful operational testing.
- Approval for use (GeNu)Confirms safe use, performance in line with the AWE, achieved operational readiness and suitability for the intended purpose.
Milestone or decision
Concluded with a target/actual comparison including impact and efficiency review. In this phase, we deliver our services as the contractor along the V.
PBN phase (project-based procurement and in-service use)
In-service phase · From the handover of the first unit to the disposal of the last
- Continuous and in parallel
- In-service managementThe ProjLtr (project manager) plans and manages measures to maintain and restore operational readiness, accompanied by performance reviews.
- Materiel responsibility for operational readiness (MatVwtgEinsRf)Rests with the PräsBAAINBw (President of the Federal Office of Bundeswehr Equipment, Information Technology and In-Service Support) and includes supply readiness.
- Operating and supply responsibility (BtrbVersVwtg)Maintaining operational capability and readiness through the OrgBer (organisational areas of the Bundeswehr), including training and keeping skills current.
- As required
- Product change and product improvementChanges according to VG 95031 (German defence equipment standard “Change of products”), for example due to obsolescence or weaknesses. Capability growth via an AAWE (adjustment of the selection decision) or a new PBN project.
- Capability retention, regeneration and supplementary procurementExtended service life, follow-on and replacement procurement and expansion of the inventory.
- Completion
- Disposal and final reviewDisposal and recycling of the units, final performance review over the entire period under consideration.
Milestone or decision
The in-service phase begins with the first unit handed over and therefore overlaps with the implementation phase.
Decision point
Project approved · products to be submitted
- Project proposalJustifies need, objectives, feasibility and economic efficiency. Customer side.
- Tender assessmentReviews a tender and prepares the bid decision. Contractor side.
- Project orderDefines objective, scope, budget and responsibility as binding. The project starts with its signature.
- Information security checklistCaptures information security requirements early and is maintained throughout the project.
Initial: created exactly onceUpdated or new at each stage
Depending on the project set-up, either the project proposal or the tender assessment is prepared.
Decision point
Project set up · products to be submitted
- Project manualDefines organisation, roles, approach and tailoring of the project.
- Project planSchedules, work packages and resources. Updated at every subsequent decision point.
- Quality assurance manualDefines quality objectives, test procedures and responsibilities.
- Product libraryCentral, versioned repository of all project products under configuration management.
- Information security management systemAdopted from the organisation and applied in the project.
- Project status report, quality assurance report and project progress decisionCreated here for the first time and updated at every further decision point.
Initial: created exactly onceUpdated or new at each stage
Decision point
Tender · offer · contract award · products to be submitted
- TenderThe customer’s specification of work. Kept by the contractor as the initial input product.
- Tender concept and criteria catalogueThe customer’s award strategy and evaluation criteria.
- OfferThe contractor’s technical and commercial response.
- Offer evaluationEvaluation of the offers against the criteria catalogue.
- ContractBinding basis for the cooperation. Kept by the contractor as the initial product.
- Contract amendmentsRecord changes and are added as required.
- Acceptance specificationDefines how acceptance will later be tested.
Also updated at every point: project plan, project status report, quality assurance report, project progress decision.
Initial: created exactly onceUpdated or new at each stage
Summarises the decision points at the interface between customer and contractor.
Decision point
1 · Clarify requirements · products to be submitted
- Requirements specificationThe customer’s functional and technical requirements for the solution.
- Requirements assessmentEvaluates and prioritises the requirements.
- Protection requirements assessmentDetermines the protection needs of information and functions.
- Requirements for IT operations, data protection and information securityFramework conditions that are extended in the following design stages.
Also updated at every point: project plan, project status report, quality assurance report, project progress decision.
Initial: created exactly onceUpdated or new at each stage
Decision point
2 · Design the overall solution · products to be submitted
- Functional specification (overall system design)The contractor’s response to the requirements specification with the design of the overall solution.
- Security conceptInformation security measures. Refined at every stage.
- Functional safety analysisAssesses hazards and the required safety functions.
- Extended requirements for IT operations, data protection and information securityDetail the requirements derived from the requirements specification.
- Test specificationsDefine how the overall system and system elements are tested.
Also updated at every point: project plan, project status report, quality assurance report, project progress decision.
Initial: created exactly onceUpdated or new at each stage
Decision point
3 · Define the technical architecture · products to be submitted
- System architectureDecomposition into segments and units with their interfaces.
- System specificationRequirements for the system and its elements.
- System implementation, integration and test conceptSequence and environment for build, integration and testing.
- External unit specificationRequirements for purchased or customer-furnished units.
- Logistic support specificationRequirements for maintenance, spare parts, training and transport.
- Security concept, functional safety analysis and system element test specificationUpdated at system level.
Also updated at every point: project plan, project status report, quality assurance report, project progress decision.
Initial: created exactly onceUpdated or new at each stage
Decision point
4 · Design assemblies · products to be submitted
- Hardware architecture and hardware specificationInternal structure and requirements of the hardware units.
- Software architecture and software specificationInternal structure and requirements of the software units.
- Hardware and software implementation, integration and test conceptPlan build and testing at unit level.
- Specifications of external hardware and software modulesRequirements for purchased or customer-furnished modules.
- Logistic support conceptDetails maintenance, spare parts supply and training.
- Security concept, functional safety analysis and system element test specificationUpdated at assembly level.
Also updated at every point: project plan, project status report, quality assurance report, project progress decision.
Initial: created exactly onceUpdated or new at each stage
Decision point
5 · Build and test assemblies · products to be submitted
- Hardware units, components and modulesManufactured or procured hardware.
- Software units, components and modulesImplemented software.
- External hardware and software modulesPurchased or customer-furnished modules.
- System element test reportDocuments the testing of every assembly.
Also updated at every point: project plan, project status report, quality assurance report, project progress decision.
Initial: created exactly onceUpdated or new at each stage
Decision point
6 · Integrate and test the system · products to be submitted
- System and segmentsIntegrated equipment at every level.
- External unitsIntegrated purchased or customer-furnished units.
- System element test reportResults of the integration tests.
- Logistic support documentationManuals, maintenance and training documents.
Also updated at every point: project plan, project status report, quality assurance report, project progress decision.
Initial: created exactly onceUpdated or new at each stage
Decision point
7 · Delivery to the customer · products to be submitted
- DeliveryPackage of system, documentation and verification evidence.
- Test reportEvidence of the overall system test before delivery.
- Proof of accessibilityWhere required in the project.
Also updated at every point: project plan, project status report, quality assurance report, project progress decision.
Initial: created exactly onceUpdated or new at each stage
Decision point
8 · Acceptance by the customer · products to be submitted
- Acceptance reportResult of the acceptance test at the customer.
- Declaration of acceptanceFormal acceptance of the delivery by the customer.
- Operational release declarationReleases the system for operation.
Also updated at every point: project plan, project status report, quality assurance report, project progress decision.
Initial: created exactly onceUpdated or new at each stage
Decision point
Project completed · products to be submitted
- Project completion reportReview of the project with lessons learned for follow-on projects.
- Project progress decisionFormal completion of the project.
Initial: created exactly onceUpdated or new at each stage
Project support services
We take on these disciplines throughout the entire project.
AreaManagementProject and quality management8 disciplines
- Initiation and organisationSet up the project, define roles and organisation.
- Planning and controlPlan, control and continuously compare target and actual status.
- Risk managementIdentify, assess and avert risks early.
- Problem and change managementCapture, assess and decide on problems and changes in a structured way.
- Configuration managementVersion, store and secure results traceably.
- Quality assurancePlan quality and check it at every decision point.
- Measurement and analysisDefine metrics and evaluate them for project controlling.
- ReportingInform everyone involved in a targeted and timely manner.
AreaDevelopmentHardware and software9 disciplines
- System elementsBreak the system down into segments, units and components.
- System analysisExamine and document the operating environment and overall system.
- System designPrepare the overall system design, the functional specification.
- System specificationDescribe the requirements and functionality of the system elements.
- Logistic elementsPrepare documentation for operation, maintenance and repair.
- User organisation and operationInvolve the user and prepare for operation.
- Logistics conceptShape logistic support from the outset (Integrated Logistic Support, ILS).
- Information security and data protectionImplement information security and data protection requirements.
- Functional safetyVerify and ensure the operational safety of the system.
AreaContract and acceptanceFrom tender to handover3 disciplines
- Tendering and contractsTender and contract from the customer’s perspective.
- Offers and contractsOffer and contract from the contractor’s perspective.
- Delivery and acceptanceHandover of the delivery item with test report and declaration of acceptance.
The diagram shows 4 + 8 decision points (quality gates): the four project milestones at the top and steps 1 to 8. At each decision point, the defined documents and products must be available before the project moves on to the next section. The drop-down at each point shows which ones they are.
Management
We plan and control the project, keep risks, changes and configuration under control and assure quality at every decision point.
Development
We structure the system, specify hardware and software, integrate the building blocks and demonstrate that everything meets the requirements.
Contract and acceptance
We support tender, offer and contract on both sides and ensure a tested, properly documented handover.