Specific Content. Offerors are required to explain what aspects of the cited contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Xxxxxx having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified.
Specific Content. 6.2.1 The CMS shall graphically depict the project schedule and progress to work package level.
Specific Content. 6.2.1 The specific SS content shall be in accordance with DI-IPSC-81431A, section 4, “Content Requirements”.
Specific Content. 6.2.1 The DD shall consist of the specifications and documentation defined by the TDT and with the format and content as defined by the TDT.
Specific Content. 6.2.1 The software will be developed in an auditable fashion. That is, full version control, as per ISO 9000 and relevant related standards, will be implemented. All versions of the software must be retained in source code format with full documentation of the changes between versions, the reason for these changes and the author or authors responsible for these changes. The source code of the software package will be exhaustively commented. Commonwealth will have access to all versions of the software and all documentation regarding them.
Specific Content. 6.2.1 The Review Package should include information to be reviewed and discussed at the specific review, including: documentation that is necessary to show that the objectives of the review have been satisfied; presentation material; all relevant documents not previously delivered and needed to meet the review objectives; status of action items from previous reviews; status of Target Performance Measures against expectations; and current configuration status along with any identified discrepancies in configuration baselines. DATA ITEM DESCRIPTION 1 DID IDENTIFIER: CTD-06 2 DID NAME: DID-AGENDA 3 TITLE: MEETING AGENDA 4 DESCRIPTION AND INTENDED USE
Specific Content. 5.2.1 The Agenda shall incorporate agenda items and other input requested by the Project Authority and shall include: the purpose or objective of the meeting; the meeting location, date, starting time, and expected duration; a chronological listing of each major discussion topic, including the person responsible to take the lead on the topic; a list of individuals invited to attend the meeting, identifying their appointment and area of responsibility; the identity of the chair person; administrative information associated with the meeting, including, where appropriate, access arrangements and facilities available; a list of documentation to be reviewed at the meeting; and any other information pertinent to the meeting. DATA ITEM DESCRIPTION 1 DID IDENTIFIER: CTD-07 2 DID NAME: DID-MINUTES 3 TITLE: MEETING MINUTES 4 DESCRIPTION AND INTENDED USE
Specific Content. 6.2.1 The SHAR shall include the following: The safety criteria and methodology used to classify and rank hazards, plus any assumptions on which the criteria or methodologies were based or derived including the definition of acceptable risk as specified by the Commonwealth; The results of analyses and tests performed to identify hazards inherent in the system, including: Those hazards that still have a residual risk, and the actions that have been taken to reduce the associated risk to a level contractually specified as acceptable; and Results of tests conducted to validate safety criteria, requirements and analyses; The results of the safety program efforts. Include a list of all significant hazards along with specific safety recommendations or precautions required to ensure safety of personnel, property, or the environment. Categorise the list of hazards as to whether or not they may be expected under normal or abnormal operating conditions; Evidence of all safety assurance activities, including the results of safety assessments performed; Any hazardous materials generated by or used in the system, including: Identification of material type, quantity, and potential hazards; and Safety precautions and procedures necessary during use, packaging, handling, storage, transportation, and disposal (eg, explosive ordnance disposal). Include all explosives hazard classifications; A signed statement that all identified hazards have been eliminated or their associated risks controlled to levels contractually specified as acceptable, and that the system is ready to test or operate or proceed to the next acquisition phase. In addition, the Contractor shall make recommendations applicable to hazards at the interface of his system with the other system(s) as contractually required. DATA ITEM DESCRIPTION 1 DID IDENTIFIER: CTD-15 2 DID NAME: DID-DD 3 TITLE: DESIGN DOCUMENTATION 4 DESCRIPTION AND INTENDED USE
Specific Content. 6.2.1 The Review Package should include information to be reviewed and discussed at the specific review, including:
Specific Content. 5.2.1 The Agenda shall incorporate agenda items and other input requested by the Project Authority and shall include:
