1 | 2010 Case planning and Statement of Work (SOW) 15/9/10 - Revision 6 - RHJ.

Slides:



Advertisements
Similar presentations
ITIL 1 Oklahoma Office of State Finance Information Services Division Instructions: Service Catalog Request.
Advertisements

PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.
1 PROJECT MANAGEMENT ROLE OF KEY PERSONNEL Bernd Madauss International Space University Strasbourg February, 2011
JobTracker™ A Job Tracking System for Architects & Engineers Produced by LA Solutions.
SPS Quality Healthcheck: Supporting Customer Excellence.
Project Management Shuffle Directions: take the definitions from the following cards and write a song using the tune from “Cupid Shuffle”
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Chapter 3 Project Initiation
NEES Project Management Workshop June 16 June 18 1 Segment 2.
EGEE NA3 Planning Prof. Malcolm Atkinson Director John Murison Training Manager CERN 13 th November 2003.
T /5115 Software Development Project I/II Project Planning Jari Vanhanen Ohjelmistoliiketoiminnan ja –tuotannon laboratorio Software Business and.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
CS 545 Software Systems Design Project Presentation Format Lecture Created by Dan Benson Computer Science Lectures © D. Benson, 2002.
The Proposal. Project Proposals Genesis of Proposals: They can result for formal requests (e.g. Request For Proposal, RFP) They can be unsolicited (e.g.
Alessandro Canossa – Michael Schmidt – Course code: MSU U Game Development – A crash course Spring.
Chapter 3 Project Initiation. The stages of a project  Project concept  Project proposal request  Project proposal  Project green light  Project.
The BIM Project Execution Planning Procedure
A SOUND INVESTMENT IN SUCCESSFUL VR OUTCOMES FINANCIAL MANAGEMENT FINANCIAL MANAGEMENT.
Safety Project Request received by TDOT Safety Project Request sent to RSAR Coordinator Safety Planning Office completes Letter of Findings for internal.
The Software Development Life Cycle: An Overview
Vs Xora Professional Services - INTERNAL. Definition of Xora Professional Services o Types of Services Provided How to Request Xora Professional.
CC20O7N - Software Engineering 1 CC2007N Software Engineering 1 Requirements Engineering Practices with Techniques.
Typical Software Documents with an emphasis on writing proposals.
Contractors & contracts
1 Lecture 3.9: RFP, SOW and CDRL (SEF Ch 19) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Requirements Analysis
SoITSSpecifications of IT systems? 1 Specifications of IT systems checking and validating Jens Bennedsen and Peter Gorm Larsen
1 Lecture 3.1: Project Planning: Work Breakdown Structure (WBS) [SEF Ch 9] Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
COSC 4303 Software Engineering GROUP PROJECT Introduction and Initial Planning Fall 2012.
1 Lecture 5.2a: SEF Ch 8 SE Outputs Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
COSC 4303 Software Engineering GROUP PROJECT Introduction and Initial Planning Fall 2010.
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
Dr. Tom WayCSC Software Requirements CSC 4700 Software Engineering Lecture 2 Based on Sommerville, Chapter 6.
Requirements for Federal Aid Project Contracts Kenneth Spear, Contracts & Estimates Engineer.
CPSC 372 John D. McGregor Module 2 Session 1 More on requirements and the Investment Decision.
Uriel Corporation One Westbrook Corporate Center Suite 300 Westchester, IL USA (708) Call to arrange fax.
IT 499 Bachelor Capstone Week 4. Adgenda Administrative Review UNIT Four UNIT Five Project UNIT Six Preview Project Status Summary.
COSC 4303 Software Engineering Introduction and Initial Planning of Group Projects Fall 2007.
Dr. John MacCarthy UMBC CMSC 615 Fall, 2006
Alpha Contracting Sole Source Negotiations between Government and Industry (13 CFR (c)(2))
0 Electronic Subcontracting Reporting System (eSRS) Department of Defense Government Training Submitting a SSR – Commercial Plan.
0 Electronic Subcontracting Reporting System (eSRS) Department of Defense Government Training Submitting a SSR – Individual Plan.
1. 2 Workflows: Create a Distribution List in ORPIN  Click on My Documents in the menu bar.  Click on Distribution List Maintenance.  Click the “Add.
1 | 2010 Case planning and Statement of Work (SOW)
Requirements Analysis
The following training presentation is for all 1Prospect subcontract employees and is taken upon joining a contract or task order to which 1Prospect is.
What is Contracts? When two or more persons have common intention communicated to each other to create same topic & done the agreement that is called.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Collaborating for Quality Quality Assurance (QA) & Quality Control (QC) in the Accelerator Project (ACCSYS) Matthew Conlon ACCSYS QA/QC
CDR for the ESS Linac Magnets for LWUs (pulsed quadrupoles and DC correctors) Closeout May 4, 2016 J.G. Weisend II, Chairman CDR.
Get Results: SOWS and Evaluation Models Presented by Kevin Greene (SAO) and Scott Smith (DES)
Collaborating for Quality through the Project Quality Plan Matthew Conlon ESS ACCSYS QA/QC Quality Learning & Planning.
Project Management PTM721S
PROJECT COMMUNICATION PROCEDURE AND DOCUMENT MANAGEMENT
The following training presentation is for all subcontract employees and is taken upon joining a contract or task order to which we are the Prime vendor.
Procurement Management
Software Subcontractor
Ch 11 - Procurement Management Learning Objectives
Venture Name – Company Mission
Leading Indicators and Dashboarding for Advanced Work Packaging
LPTA – The impact of LPTA is not fruitful to the Government or to Industry. We have seen multiple times where the lowest price won, but could not be executed,
Requirements Analysis
Lockheed Martin Canada’s SMB Mentoring Program
PRELIMINARY DESIGN REVIEW
Addie N. Olsen, Lynge C. Christiansen, Steffen J
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Business Acquisition An Introduction into Processes and Tools
CEN/WS XBRL PT kick-off meeting
Presentation transcript:

1 | 2010 Case planning and Statement of Work (SOW) 15/9/10 - Revision 6 - RHJ

Congratulations. You have won the contract! The customer need his product a.s.a.p. So, get started now!

Case work flow 3 | 2010 Terma case SOW U.C. Req. Terma case SOW U.C. Req. Systematic case SOW U.C. Req. Systematic case SOW U.C. Req. Systematic case SOW U.C. Req. Systematic case SOW U.C. Req. Terma case SOW U.C. Req. Terma case SOW U.C. Req. Company A Company B Company C Company D Company E Company F Company G Company H SOW – Statement of Work MSR – Milestone review Del. Doc = deliverable documentations U.C. Req. = Use Case Requirements Contract to prime MSR Del. Doc. MSR Del. Doc. MSR Del. Doc. MSR Del. Doc. Contract to prime MSR Del. Doc. MSR Del. Doc. MSR Del. Doc. MSR Del. Doc. Contract to prime Contract to subcontractor MSR Del. Doc. MSR Del. Doc. Contract to subcontractor MRS Del. Doc. MRS Del. Doc. MRS Del. Doc. MRS Del. Doc. MRS Del. Doc. MRS Del. Doc.

Contractors and sub-contractors Company A Prime contractor to Terma case Subcontractor to Company B Company B Prime contractor to Systematic case Subcontractor to Company C Company C Prime contractor to Terma case Subcontractor to Company D Company D Prime contractor to Systematic case Subcontractor to Company H Company E Prime contractor to Systematic case Subcontractor to Company A Company F Prime contractor to Terma case Subcontractor to Company E Company G Prime contractor to Systematic case Subcontractor to Company F Company H Prime contractor to Terma case Subcontractor to Company G 4 | 2010

Case input: Customer requirements Terma -Statement of Work -Use Case Requirements (U.C. Req.) Systematic -Statement of Work -Use Case Requirements (U.C. Req.) 5 | 2010

Timeline for case work 6 | 2010 Contract win 3/ / / /

Responsibilities (1 of 2) Prime-contractor’s MSR with the end-customer and the QA consultant: All documents for the MSR shall be delivered to the customer no less that 72 hours in advance Delivery information: Terma: Systematic: QA consultant: All documents shall be in PDF format All documents shall be revision controlled The MSR shall be conducted at an agreed time on the dates specified by the end-customer It is the prime-contractor’s responsibility that the MSR time is not conflicting with other MSR’s 7 | 2010

Responsibilities (2 of 2) Subcontractor’s MSR with the prime-contractor: The MSR shall be conducted outside class lectures The requirements for the documentation is the same as for the prime-contractor’s MSR with the end-customer. Minutes of Meeting (MoM) from the MSR shall be sent to the end- customer and the QA consultant by the prime contractor no less that 48 hours after the MSR meeting MoM shall be in PDF format containing a max. of 1000 words. 8 | 2010

Required documentation for review meetings ReviewDelivery documentationComments SRR MA: Project planSchedule with all MSR w/ stakeholders) MA: System Requirement SpecificationRequirements analysis based on U.C. Req. OP: List of all subsystems and subcontractors Based on preliminary design sketches CDR MA: Detailed Design DescriptionThe system is designed with all subsystems including subcontractor’s design(s) design documentation MA: ICDAll interfaces described (SW/HW) MA: Verification MatrixVerification method for all requirements MA = Mandatory delivery OP = Optional delivery

Systems Engineering teams in companies A-H Company A Amos Hoste Anders Petersen Søren Aa. Mikkelsen Nikki Ashton Jeremi V. Kiruparajan Lasse H. Rasmussen Nikolaj Tørring Company B Ba Thy Thu Søren Dalsgaard Ulrikkeholm Allan Nielsen Zoi Kostopoulou Rony Aywan Teddy Holm Roskvist Jesper Jakobsen Company C Brian V.Danielsen Kristoffer L. Jakobsen Frederik Ø.Laulund Anders Bo Nielsen Maria Soler Climent Lasse V. Hansen Michael Owsinski Company D José Antonio Esparza Isasa Adam Enø Jensen Martin S. Madsen Martin G. Olsen Rene G. Stenner Lars W. Jochumsen Company E Anders Torndahl Christian Jensen David N.R. Marmoy Michael N. Pedersen Peter H. Mikkelsen Company F Hardy Rusbjerg Kaj Norman Kenneth Pihl Lars Munch Michael B. Mogensen Anders H. Poder Company G Klaus Kolle Morten O. Jakobsen Frank Andersen Bodil Bruun Jørgen V. Hansen Said Shah Alizadeh Company H Anders Bloch Jesper Bærentzen Erik Eskjær Øbakke Jens Klinting Ole Lysgaard Torben T. Dissing 10 | 2010 Main contact person is underlined

Questions and support issues Planned consultation (17/9 at 10-12) An optional consultation is planned at IHA. Location to be announced on CampusNet. Companies shall send only one representative. Questions sent no later that 48 hours before the consultation will be given highest priority. Questions must be prioritized due to time constraints. Contact information for QA consultant Rune Jacobsen IHA, Office 407b Phone: | 2010