RFP ANNEX F
EELV PROGRAM CONTRACT DATA REQUIREMENTS LIST (CDRL)
158
THIS ANNEX, INCLUDING THE COVER, CONSISTS OF 52 PAGES
ANNEX F, CDRLS F04701-95-R-0009 (159)
CONTRACT DATA REQUIREMENTS LIST (CDRL) INSTRUCTIONS 1. SCOPE: These instructions supplement the Contract Data Requirements List (CDRL). All delivery instructions are specified on DD Forms 1423-1. 2. GENERAL: The CDRL is a list of data requirements authorized for this specific procurement and made a part of this contract. The contractual method is to use DD Forms 1423-1, CDRL, which specify the data required to be delivered to the Government. The Data Item Descriptions (DIDs) listed on the DD Forms 1423-1 were selected from DoD 5010.12-L, Acquisition Management Systems and Data Requirement Control List (AMSDL). Non-AMSDL DIDs are attached after the corresponding DD Form 1423-1. 3. DATA ITEM DESCRIPTION (DID)/DID TAILORING: The DID is a specification for the preparation of data. DID tailoring (Block 16) is made to either relax preparation instructions or to tailor the DID to be in consonance with the Government List of Objectives (GLO). 4. SUPPLEMENTAL DATA DELIVERY INSTRUCTIONS: a. Due dates: Due dates for delivery of data are to be construed as "On Dock" dates at destination. b. Late delivery: Delivery of data is considered late if it does not arrive at its destination by 1530 hours on the date specified in Block 12, 13 or 16 of the CDRL. If the data delivery is post marked three days before the due date, and because of U.S. Postal Service handling, is not received by the EELV Data Management Office (DMO) on the due date, the CDRL delivery requirements are still met. Use of U.S. Postal Service "Express Mail" or overnight courier/delivery service is not encouraged. c. Letter of transmittal (Block 7): Each data submittal shall be accompanied by a paper copy letter of transmittal (LT). Note the letter of transmittal format instructions for electronic delivery in paragraph 4e. Letters of transmittal shall contain the following information: (1) Contract Number and, if applicable, Integrated Task and Management Plan (ITAMP) task assignment number (2) CDRL sequence number together with DID number (i.e., A001/OT-95-34151) (3) Exact title, and subtitle if appropriate, of the document being transmitted (4) Document date, number, and revision information (if applicable) (5) Whether the document is a preliminary draft, draft, or final submittal (6) For periodic reports: The report period the document covers
160
(7) Information disclosing the total contractual distribution being made per Block 14 or 16 of the DD Form 1423-1. d. The Contractor is not authorized to provide copies of any data to any outside agency other than those listed in Block 14 or 16 of the DD Form 1423-1 without specific approval of the Procuring Contracting Officer (PCO). e. It is the intent of the EELV Program Office to accept digital delivery of specified CDRLs. For those CDRLs that are specified for electronic delivery, the data shall be submitted as an uploaded file to the Contractor‟s designated file library on the EELV Electronic Bulletin Board (EBB), per the instructions outlined in the EELV EBB User‟s Guide. The name of the specific library will be designated by the EELV DMO at contract award. The file description summary for the uploaded file on the EBB will contain the letter of transmittal information outlined in paragraph 4c. All drawings shall be submitted as paper copies and shall be delivered with the paper submittal of the associated CDRL. The Integrated Master Schedule shall be delivered as paper copies with a 3.5” High Density diskette that contains the file. This diskette shall be properly labeled with contract number, CDRL number, title, subtitle (if applicable), date, and classification. All deliveries, via the EBB and the paper copies, must be received by the due date to ensure that the CDRL requirements are met. Note that data delivered in electronic format must print out acceptably at the AF destination without any additional work for contract compliance. To facilitate ease of transfer and use, the following document formats shall be delivered in the software application/version indicated: Written Material Spreadsheets Vugraphs (presentation material) MS Word Version 6.0 MS Excel Version 5.0 MS Power Point Version 4.0
5. COMMUNICATIONS: Any correspondence related to requests for data delivery deviations and/or amendments, additions or deletions to the DD Forms 1423-1 shall be addressed to the EELV DMO and the PCO. Verbal requests to change a CDRL will not be honored; a written request is required in each case. 6. DATA ACCESSION LIST (DAL): Requests from the PCO for data ordered from the Data Accession List (with the application of DID: DI-A-3027A) shall be provided at no increase in contract price. Requests for quantities greater than two (2) each per document shall be honored upon receipt of PCO direction and with Contractor concurrence that such requests can be filled at no increase in contract price. Transmittal of any such data so ordered shall include information copies to the EELV DMO.
ANNEX F, CDRLS F04701-95-R-0009 (161)
7. CODES USED IN THE DD FORM 1423-1: The directions for submittal of data is indicated in Blocks 7, 8, 9, 10, 11, 12, 13, or 16 of the DD Form 1423-1. Usually, the direction is in the form of a code. The abbreviations/codes are extracted from DoD 5010.12-M. Block 14 for data items: A006, A009-A011, A015-A018, and A020 have specific numbers of copies for draft and regular submittal. Draft submittals are the initial and incremental drafts submitted according to the tailoring in BLK 16. Regular submittals are the final draft submittal and if necessary the updated final submittal reflecting any changes from the tailored Preliminary Design Review as described in BLK 16. 8. DISTRIBUTION STATEMENT MARKING: Block 9 of all documents shall be marked with Distribution Statement “C”, for the reason of Administrative or Operational Use, unless the Contractor determines the appropriate Distribution Statement to be assigned to the document is something other than “C”. Either way, the Contractor is ultimately responsible for correctly marking the data using Air Force Instruction (AFI) 61-204 as reference. Justification for marking data with Distribution Statements other than “C” shall be pre-coordinated with the EELV DMO prior to contract document submittal in accordance with DD Form 1423-1 requirements. The date of the distribution statement shall be the effective date of the contract. All technical documents shall also be marked with the destruction notice in AFI 61-204, paragraph 2.3. 9. EXPORT CONTROL STATEMENTS: All newly created technical documents must be reviewed to determine if they contain information subject to export control or technical data subject to withholding under DoD Directive 5230.25 as implemented by AFI 61-204. All data controlled by the International Traffic-in-Arms Regulations (ITAR), Department of Commerce requires dissemination control. All technical documents subject to export-control laws must be marked with the notice in AFI 61-204, paragraph 2.1, in addition to distribution statements and other required notices. 10. ADDRESSES: CDRLs shall be delivered to the following addresses by the due date: Electronic Bulletin Board 3.5” HD diskettes Drawings Paper Copies (310) 363-1623 for low speed modem (310) 363-3296 for high speed modem EELV DMO 2435 Vela Way, Suite 1613 LAAFB, CA 90245-5500
162
M onths after C ontract A w ard 1 CDRL # CA
L ife C y cle C o st S o ft. A rch . D esig n D esc. D ata A ccessio n L ist C o n feren ce A g en d a P resen tatio n M aterial In terface C o n tro l S p ec D ev S p ec (B S p ec) CFSR S y st. A n aly ses R p t L o g istics T rad e S tu d y M issio n C L C C T rad e A S p ec S y st. D es. D escrip tio n S R S (B S p ec) IR S (B S p ec) M etrics S tatu s R p t M an u factu rin g P lan D em o n stratio n R p t M o d elin g R p t E n v iro n . A n aly sis R ep o rt S p ecs an d S td s R p t O p s T ech n ical R p t IM S
2
3
4 TSRR
5
6
7
8
9
10
11
12 TPDR x
13
14
15
EOC x*
A 001 A 002 A 003 A 004 A 005 A 006 A 007 A 008 A 009 A 009 A 009 A 010 A 011 A 012 A 013 A 014 A 015 A 016 A 017 A 018 A 019 A 020 A 021 x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x
x x
x
x* x* x x x*
x* x* x* x* x x x* x* x* x* x* x x x x*
0
* As per the instructions in BLK 16 of the DD Forms 1423-1, a final submission shall be made if changes result from the tailored PDR. NOTE: If the delivery dates between the DD Forms 1423-1 and the delivery matrix differ, the DD Forms 1423-1 take precedence.
ANNEX F, CDRLS F04701-95-R-0009 (163)
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Form Approved OMB No. 0704-0188
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A001 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: OT TDP_______ TM_______ OTHER F. CONTRACTOR N/A 3. SUBTITLE OT
E. CONTRACT/PR.NO F04701-95-R-0009
LIFE CYCLE COST ESTIMATE DOCUMENT 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 C 11. AS OF DATE 13. DATE OF SUBSEQUENT SUBMISSION EELV DMO* 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) OT-95-34151 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
2
BLK 12: Submit at the tailored Preliminary Design Review * Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
Annex F, CDRLs
F04701-95-R-0009 (1)
15. TOTAL
2
G. PREPARED BY MAJ Delane Aguilar 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_1_Pages
J. DATE
Annex F, CDRLs
F04701-95-R-0009 (2)
2
DATA ITEM DESCRIPTION
Form Approved OMB NO. 0704-0188
Public reporting burden for collection of this information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden to Washington Headquarters Services, Directorate of Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington , DC 20503.
1. TITLE
2. IDENTIFICATION NUMBER
LIFE CYCLE COST ESTIMATE
3. DESCRIPTION/PURPOSE
OT-95-34151
3.1 The Life Cycle Cost Estimate (LCCE) is a prediction of the total life cycle cost of a system. The LCCE is the cost to the Government for acquisition and ownership. It includes the cost of development, acquisition, operation, support, and disposal. 3.2 LCCE provides essential data to the Government when considering acquisition versus
Annex F, CDRLs
F04701-95-R-0009 (3)
operating and support costs, comparing competing prototypes, or comparing current versus new systems.
4. APPROVAL DATE
-(YYMMDD)
94-11-23
5. OFFICE OF PRIMARY RESPONSIBILITY
6a. DTIC APPLICABLE
6b. GIDEP APPLICABLE
F/SMC-XR
7. APPLICATION/INTERRELATIONSHIP
7.1 This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement for this data included in the contract. 7.2 The DID is for one-time use on the solicitation number: F04701-95-R-0009.
8. APPROVAL LIMITATION Limited to solicitation F04701-95-R-0009 9a. APPLICABLE FORMS 9b. AMSC NUMBER
10. PREPARATION INSTRUCTIONS
10.1 Reference: Contractor format acceptable. 10.2 Costs shall be based on the requirements of the National Mission Model (NMM) identified by the Government, and/or operational support requirements, design and test requirements, and other technical data as delineated by the Offeror‟s concept. The costs shall be displayed by Government fiscal years and include overhead, general and administrative expense, and estimated fee or profit. 10.3 LCCE 10.3.1 Executive Summary. (Ten pages maximum) The Executive Summary is a separate, stand alone document, and shall contain: 10.3.1.1 Total Estimate/Purpose. - No more than one page that discusses how this estimate was prepared. - Bottom line total value of the estimate at the 70th percentile confidence level in Then-Year (TY) dollars. - Estimate totals in TY dollars shall be displayed for each Work Break Down Structure (WBS) level element. - Risk totals in TY dollars shall be displayed for each WBS level 2 element. 10.3.1.2 Estimate Summary and Time Phasing. - Top level estimate summary (i.e., by major segment: vehicle, ground, facilities, etc.) and acquisition life cycle modules/phases (i.e., Low Cost Concept Validation (LCCV), Pre-Engineering and Manufacturing Development (Pre-EMD), EMD, Production, Operations and Support (O&S), etc.). - Point Estimate (i.e., the sum of initial estimates from cost models/methodologies, prior to any dollars added for risk), ranges, and 70th percentile confidence level estimate. - Phased by Government fiscal year in constant Fiscal Year 1995 (FY95) and TY dollars. (Continued)
Annex F, CDRLs
F04701-95-R-0009 (4)
4
11. DISTRIBUTION STATEMENT
DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.
DD Form 1664, APR 89
135/123
Previous editions are obsolete
Annex F, CDRLs
F04701-95-R-0009 (5)
10.3.1.3 Issues/Content. - Discuss at WBS level 2 or lower levels as appropriate. - Brief program/estimate content discussion. - Include discussion of program schedule. - Major factors bearing on estimate. - Cost drivers (i.e., high cost elements of estimate, risk drivers, etc.). - Business base considerations. - Trade analyses. - Key ground rules and assumptions. - Sensitivities. 10.3.1.4 Programmatic Alternatives. - Solutions to issues addressed in 10.3.1.3 above. - Sensitivity Analyses/Excursions (e.g., impacts due to changes in major cost drivers and risk drivers, or assumptions). 10.3.2 Detailed Documentation. The narrative portion of the LCCE is limited to 100 pages; however, the number of pages of spreadsheets displaying the LCCE is unlimited. 10.3.2.1 The LCCE shall be presented at the 70th percentile confidence level. The cost-risk analysis supporting the development of this 70th percentile confidence level shall utilize valid techniques and acceptable approaches to distribution range development and summarization, and will be performed by acquisition module/phase. This cost-risk analysis shall contain narratives explaining all methodologies used to determine risk magnitudes of identified risk areas, quantification of these risk magnitudes into cost impacts, and spreadsheets or other formats containing calculations, algorithms, etc., that fully support an understanding of the performance of the cost-risk analyses. The cost-risk analysis shall include, but is not limited to, the following areas of risk: Design and Engineering, Technology (including the use of foreign technology, components, and non-domestically manufactured products), Cost Estimating, Manufacturing, Schedule, Supportability, Integration, and Threat. (The Air Force Risk Analysis Handbook may be helpful in conducting an acceptable risk analysis.) Cost drivers (e.g., high cost and high risk elements) and LCCE sensitivities (e.g., impacts resulting from changes in major cost drivers, risk drivers, or assumptions) shall be identified and explained. Cost risk quantification shall be performed and applied at the cost estimating level. 10.3.2.2 The cost estimating methodologies derived and utilized in the development of the LCCE shall be clearly documented to allow assessment of the reasonableness and completeness of costs presented in the LCCE. 10.3.2.3 The Offeror shall provide a cost track to explain the differences between the 50th percentile confidence level LCCE (submitted with proposal for LCCV module) and the 70th percentile confidence level LCCE. 10.3.2.4 The Offeror shall develop a LCCE in accordance with the following cost estimating guidelines, general ground rules, and assumptions:
Annex F, CDRLs
6
F04701-95-R-0009 (6)
- The implications of the provided System Performance Document (SPD) NMM shall be addressed in the LCCE, to include the Offeror‟s commercial market projections. - LCCE shall be shown by acquisition life cycle module/phase. - LCCE shall extend through FY 2020. - Most current OSD approved inflation indices shall be used. - LCCE shall be provided at the point estimate level (i.e., the sum of initial estimates from cost models/methodologies, prior to any dollars added for risk) and the 70th percentile confidence level. - LCCE detail shall be shown at the level each WBS element was estimated. - LCCE shall be structured as reflected in WBS Dictionary submitted in the Offeror‟s proposal. - LCCE shall be developed and shown by Government fiscal years in constant FY95 and TY dollars. 10.3.2.5 The LCCE documentation will include a detailed discussion of the methodologies employed for each WBS element at which the LCCE was estimated. It shall be prepared in concert with the following requirements and be limited to 100 pages: 10.3.2.5.1 Discussion of all levels of the WBS shall contain: - WBS element definitions. - acquisition life cycle phase identifications. - cost phasing approach. - a detailed explanation of estimating approach/methodology. - an explanation of risk assessment/analysis. - an identification of sources of data. 10.3.2.5.2 Estimating approaches shall be presented at the WBS level at which the LCCE was developed. "Roll-up" is an acceptable description of methodology if the estimate was developed at a lower WBS level. If an estimating methodology is identical for all lower level elements, methodology need only be described once at the next highest WBS level. 10.3.2.5.3 Key ground rules and assumptions, business base assumptions, and trade analyses, shall be clearly documented.
Annex F, CDRLs
F04701-95-R-0009 (7)
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Form Approved OMB No. 0704-0188
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A002 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: OT TDP_______ TM_______ OTHER OT F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
SOFTWARE ARCHITECTURAL DESIGN DESCRIPTION 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES C 11. AS OF DATE 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 Final Draft
4. AUTHORITY (Data Acquisition Document No.) OT-95-34152 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
EELV DMO*
2
BLK 12: Submit the final draft 30 CD prior to the tailored Preliminary Design Review BLK 13: Any changes to the final draft as a result of the tailored Preliminary Design Review shall be reflected in an updated draft submitted 14 CD prior to the end of contract (EOC). * Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
Annex F, CDRLs
F04701-95-R-0009 (8)
8
15. TOTAL
2
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 MAR 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_1_Pages
J. DATE
Annex F, CDRLs
F04701-95-R-0009 (9)
DATA ITEM DESCRIPTION
Form Approved OMB NO. 0704-0188
Public reporting burden for collection of this information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden to Washington Headquarters Services, Directorate of Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington , DC 20503.
1. TITLE
2. IDENTIFICATION NUMBER OT-95-34152
SOFTWARE ARCHITECTURAL DESIGN DESCRIPTION (SADD)
3. DESCRIPTION/PURPOSE
3.1 The Software Architectural Design Description (SADD) describes the design of the EELV software. It includes the overall design decisions and the architectural design for the EELV Computer Software Configuration Items (CSCIs), databases, and software interfaces. 3.2 The SADD is used as the basis for performing the detailed design of the software. It
Annex F, CDRLs
F04701-95-R-0009 (10)
10
provides the acquirer visibility into the software architectural design and provides information needed for software support.
4. APPROVAL DATE
(YYMMDD)
950221
5. OFFICE OF PRIMARY RESPONSIBILITY
6a. DTIC APPLICABLE
6b. GIDEP APPLICABLE
SMC/XRV
7. APPLICATION/INTERRELATIONSHIP
7.1 This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by specific and discrete task requirements as delineated in the contract. 7.2 This DID is used to define and record the architectural design of the EELV software. 7.3 The information requested in sections 3 through 7 of this DID is to be prepared to the level of detail appropriate for the EELV tailored Preliminary Design Review event according to the Contractor‟s software and database design methodologies, as described in the Contractor‟s Integrated Task and Management Plan (ITAMP). 7.4 The data requested by this DID may be delivered in Contractor format rather than in the format specified herein. 7.5 If any of the data requested in sections 3 through 7 of this DID is provided in referenced documents that are not other EELV CDRL items, those referenced documents must be provided to the Government with the SADD CDRL. 7.6 This DID is for one-time use on solicitation F04701-95-R-0009.
8. APPROVAL LIMITATION Limited to solicitation F04701-95-R-0009 9a. APPLICABLE FORMS 9b. AMSC NUMBER
10. PREPARATION INSTRUCTIONS
10.1 General instructions. a. Automated techniques. Use of automated techniques is encouraged. The term "document" in this DID means a collection of data regardless of its medium.
b. Alternate presentation styles. Diagrams, tables, matrices, and other presentation styles are acceptable substitutes for text when data required by this DID can be made more readable using these styles. (Continued)
11. DISTRIBUTION STATEMENT
DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.
DD Form 1664, APR 89
Previous editions are obsolete
Annex F, CDRLs
F04701-95-R-0009 (11)
135/123
Annex F, CDRLs
F04701-95-R-0009 (12)
12
10. PREPARATION INSTRUCTIONS -- 10.1 General Instructions (continued) c. Title page or identifier. The document shall include a title page containing, as applicable: document number; volume number; version/revision indicator; security markings or other restrictions on the handling of the document; date; document title; name, abbreviation, and any other identifier for the system, subsystem, or item to which the document applies; contract number; CDRL item number; organization for which the document has been prepared; name and address of the preparing organization; and distribution statement. For data in a database or other alternative form, this information shall be included on external and internal labels or by equivalent identification methods. d. Table of contents. The document shall contain a table of contents providing the number, title, and page number of each titled paragraph, figure, table, and appendix. For data in a database or other alternative form, this information shall consist of an internal or external table of contents containing pointers to, or instructions for accessing, each paragraph, figure, table, and appendix or their equivalents. e. Page numbering/labeling. Each page shall contain a unique page number and display the document number, including version, volume, and date, as applicable. For data in a database or other alternative form, files, screens, or other entities shall be assigned names or numbers in such a way that desired data can be indexed and accessed. f. Response to tailoring instructions. If a paragraph is tailored out of this DID (format tailoring only), the resulting document shall contain the corresponding paragraph number and title, followed by "This paragraph has been tailored out." For data in a database or other alternative form, this representation need occur only in the table of contents or equivalent.
g. Multiple paragraphs and subparagraphs. Any section, paragraph, or subparagraph in this DID may be written as multiple paragraphs or subparagraphs to enhance readability. h. Standard data descriptions. If a data description required by this DID has been published in a standard data element dictionary specified in the contract, reference to an entry in that dictionary is preferred over including the description itself. i. Substitution of existing documents. Commercial or other existing documents may be substituted for all or part of the document if they contain the required data.
10.2 Content requirements. Content requirements begin on the following page. The numbers shown designate the paragraph numbers to be used in the document. Each such number is understood to have the prefix "10.2" within this DID. For example, the paragraph numbered 1.1 is understood to be paragraph 10.2.1.1 within this DID. 1. Scope. This section shall be divided into the following paragraphs.
Annex F, CDRLs
F04701-95-R-0009 (13)
1.1 Identification. This paragraph shall contain a full identification of the system and the software to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s). 1.2 System overview. This paragraph shall briefly state the purpose of the system and the software to which this document applies. It shall describe the general nature of the system and software; summarize the history of system development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, and support agencies; identify current and planned operating sites; and list other relevant documents. 1.3 Document overview. This paragraph shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use. 2. Referenced documents. This section shall list the number, title, revision, and date of all documents referenced in this document. This section shall also identify the source for all documents not available through normal Government stocking activities. 3. CSCI-wide design decisions. This section shall be divided into the following paragraphs to present CSCI-wide design decisions for each EELV CSCI. 3.X (EELV CSCI name and project-unique identifier). This paragraph shall present the CSCI-wide design decisions for this CSCI. This paragraph (and subparagraphs as needed) shall describe decisions about the CSCI‟s behavioral design (how it will behave, from a user's point of view, in meeting its requirements, ignoring internal implementation) and other decisions affecting the selection and design of the software units that make up the CSCI. If all such decisions are explicit in the CSCI requirements or are deferred to the design of the CSCI's software units, this paragraph shall so state. Design decisions that respond to requirements designated critical, such as those for safety, security, or privacy, shall be placed in separate subparagraphs. If a design decision depends upon system states or modes, this dependency shall be indicated. Design conventions needed to understand the design shall be presented or referenced. Examples of CSCI-wide design decisions are the following: a. Design decisions regarding inputs the CSCI will accept and outputs it will produce, including interfaces with other systems, HWCIs, CSCIs, and users. Information contained in other sections of this document or in other interface documents may be referenced. Design decisions on CSCI behavior in response to each input or condition, including actions the CSCI will perform, response times and other performance characteristics, description of physical systems modeled, selected equations/algorithms/rules, and handling of unallowed inputs or conditions. Design decisions on how databases/data files will appear to the user. Information contained in other sections of this document may be referenced.
Annex F, CDRLs
b.
c.
14
F04701-95-R-0009 (14)
d. e.
Selected approach to meeting safety, security, and privacy requirements. Other CSCI-wide design decisions made in response to requirements, such as selected approach to providing required flexibility, reliability, availability, and maintainability.
4. CSCI architectural design. This section shall be divided into the following paragraphs to describe the CSCI architectural design for each EELV CSCI. 4.X (EELV CSCI name and project-unique identifier). This paragraph shall describe the architectural design for this CSCI. If part or all of the design depends upon system states or modes, this dependency shall be indicated. If design information falls into more than one subparagraph, it may be presented once and referenced from the other subparagraphs. Design conventions needed to understand the design shall be presented or referenced. 4.X.1 a. CSCI components. This paragraph shall: Identify the software units that make up the CSCI. Each software unit shall be assigned a project-unique identifier. Note: A software unit is an element in the design of a CSCI; for example, a major subdivision of a CSCI, a component of that subdivision, a class, object, module, function, routine, or database. Software units may occur at different levels of a hierarchy and may consist of other software units. Software units in the design may or may not have a one-to-one relationship with the code and data entities (routines, procedures, databases, data files, etc.) that implement them or with the computer files containing those entities. A database may be treated as a CSCI or as a software unit. This SADD may refer to software units by any name(s) consistent with the design methodology being used. b. Show the static (such as "consists of") relationship(s) of the software units. Multiple relationships may be presented, depending on the selected software design methodology (for example, in an object-oriented design, this paragraph may present the class and object structures as well as the module and process architectures of the CSCI). State the purpose of each software unit and identify the CSCI-wide design decisions allocated to it. Identify each software unit's development status/type (such as new development, existing design or software to be reused as is, existing design or software to be reengineered, software to be developed for reuse, software planned for Build N, etc.). For existing design or software, the description shall provide identifying information, such as name, version, documentation references, library, etc.
c.
d.
Annex F, CDRLs
F04701-95-R-0009 (15)
e.
Describe the CSCI's (and as applicable, each software unit's) planned utilization of computer hardware resources (such as processor capacity, memory capacity, input/output device capacity, auxiliary storage capacity, and communications/network equipment capacity). The description shall cover all computer hardware resources included in resource utilization requirements for the CSCI and in system-level resource allocations affecting the CSCI. If all utilization data for a given computer hardware resource are presented in a single location in this SADD, this paragraph may reference that source. Included for each computer hardware resource shall be: 1) 2) The CSCI requirements or system-level resource allocations being satisfied The assumptions and conditions on which the utilization data are based (for example, typical usage, worst-case usage, assumption of certain events) Any special considerations affecting the utilization (such as use of virtual memory, overlays, or multiprocessors or the impacts of operating system overhead, library software, or other implementation overhead) The units of measure used (such as percentage of processor capacity, cycles per second, bytes of memory, kilobytes per second) The level(s) at which the estimates or measures will be made (such as software unit, CSCI, or executable program)
3)
4)
5)
4.X.2 Concept of execution. This paragraph shall describe the concept of execution among the software units. It shall include diagrams and descriptions showing the dynamic relationship of the software units, that is, how they will interact during CSCI operation, including, as applicable, flow of execution control, data flow, dynamically controlled sequencing, state transition diagrams, timing diagrams, priorities among units, handling of interrupts, timing/sequencing relationships, exception handling, concurrent execution, dynamic allocation/deallocation, dynamic creation/deletion of objects, processes, tasks, and other aspects of dynamic behavior. 5. Interface design. This section shall be divided into the following paragraphs and subparagraphs to describe the interface characteristics of the EELV software units. It shall include both interfaces among the software units within a single EELV CSCI and interfaces between a software unit in an EELV CSCI and an entity external to that CSCI (such as an external system, a user, an EELV hardware configuration item (HWCI), or a software unit in another EELV CSCI). Information contained in other sections of this document or in other interface documents may be referenced. 5.1 Interface identification and diagrams. This paragraph shall state the name and project-unique identifier assigned to each interface and shall identify the interfacing entities (software units, systems, configuration items, users, etc.) by name, number, version, and documentation references, as applicable. The identification shall state which entities have fixed
Annex F, CDRLs
16
F04701-95-R-0009 (16)
interface characteristics (and therefore impose interface requirements on interfacing entities) and which are being developed or modified (thus having interface requirements imposed on them). One or more interface diagrams shall be provided, as appropriate, to depict the interfaces. 5.x (EELV interface name and project-unique identifier). This paragraph (beginning with 5.2) shall identify an interface by name and project-unique identifier, shall briefly identify the interfacing entities, and shall be divided into subparagraphs as needed to describe the interface characteristics of one or both of the interfacing entities. If a given interfacing entity is not covered by this SADD (for example, an external system) but its interface characteristics need to be mentioned to describe interfacing entities that are covered by this SADD, these characteristics shall be stated as assumptions or as "When [the entity not covered] does this, [the entity that is covered] will ...." This paragraph may reference other documents (such as data dictionaries, standards for protocols, standards for user interfaces, or other interface documentation) in place of stating the information here. The design description shall include the following, as applicable, presented in any order suited to the information to be provided, and shall note any differences in these characteristics from the point of view of the interfacing entities (such as different expectations about the size, frequency, or other characteristics of data elements): a. b. Priority assigned to the interface by the interfacing entity(ies) Type of interface (such as real-time data transfer, storage-and-retrieval of data, etc.) to be implemented Characteristics of individual data elements that the interfacing entity(ies) will provide, store, send, access, receive, etc., such as: 1) Names/identifiers a) Project-unique identifier b) Non-technical (natural-language) name c) DoD standard data element name d) Technical name (e.g., variable or field name in code or database) e) Abbreviation or synonymous names Data type (alphanumeric, integer, etc.) Size and format (such as length and punctuation of a character string) Units of measurement (such as meters, dollars, nanoseconds) Range or enumeration of possible values (such as 0-99) Accuracy (how correct) and precision (number of significant digits) Priority, timing, frequency, volume, sequencing, and other constraints, such as whether the data element may be updated and whether business rules apply Security and privacy constraints Sources (setting/sending entities) and recipients (using/receiving entities)
c.
2) 3) 4) 5) 6) 7) 8) 9)
Annex F, CDRLs
F04701-95-R-0009 (17)
d.
Characteristics of data element assemblies (records, messages, files, arrays, displays, reports, etc.) that the interfacing entity(ies) will provide, store, send, access, receive, etc., such as: 1) Names/identifiers a) Project-unique identifier b) Non-technical (natural language) name c) Technical name (e.g., record or data structure name in code or database) d) Abbreviations or synonymous names Data elements in the assembly and their structure (number, order, grouping) Medium (such as disk) and structure of data elements/assemblies on the medium Visual and auditory characteristics of displays and other outputs (such as colors, layouts, fonts, icons and other display elements, beeps, lights) Relationships among assemblies, such as sorting/access characteristics Priority, timing, frequency, volume, sequencing, and other constraints, such as whether the assembly may be updated and whether business rules apply Security and privacy constraints Sources (setting/sending entities) and recipients (using/receiving entities)
2) 3) 4) 5) 6) 7) 8) e.
Characteristics of communication methods that the interfacing entity(ies) will use for the interface, such as: 1) 2) 3) 4) 5) 6) 7) 8) Project-unique identifier(s) Communication links/bands/frequencies/media and their characteristics Message formatting Flow control (such as sequence numbering and buffer allocation) Data transfer rate, whether periodic/aperiodic, and interval between transfers Routing, addressing, and naming conventions Transmission services, including priority and grade Safety/security/privacy considerations, such as encryption, user authentication, compartmentalization, and auditing
f.
Characteristics of protocols that the interfacing entity(ies) will use for the interface, such as: 1) 2) 3) 4) 5) 6) Project-unique identifier(s) Priority/layer of the protocol Packeting, including fragmentation and reassembly, routing, and addressing Legality checks, error control, and recovery procedures Synchronization, including connection establishment, maintenance, termination Status, identification, and any other reporting features
g.
Other characteristics, such as physical compatibility of the interfacing entity(ies) (dimensions, tolerances, loads, voltages, plug compatibility, etc.)
Annex F, CDRLs
18
F04701-95-R-0009 (18)
6. Database-wide design decisions. This section shall be divided into the following paragraphs for each EELV database to present database-wide design decisions. A database is defined to be any collection of related data stored in one or more computerized files in a manner that can be accessed by users or computer programs via a database management system. A database management system (DBMS) is an integrated set of computer software that provides the capabilities needed to establish the database, modify it, make data available from it, and maintain its integrity. Note that the definition of a DBMS does not require those software capabilities to be provided by a commercial DBMS package; the capabilities may be provided by EELV custom software contained in one or more CSCIs described in sections 3 and 4 of this SADD. Note also that the storage media of the computerized files that comprise the database are not limited to external storage devices but may also include in-memory storage, such as global common or shared memory areas. Note also that the definition of a database makes no implications concerning the structure of the data stored in the computerized files or of the computerized files themselves; thus, for example, the data in a database may be stored in various types of data structures in memory, in sequentially accessed flat files on external media, in various types of randomly accessed files on external media, or in tables whose structure and access methods are determined by a commercial DBMS. 6.X (EELV database name and project-unique identifier). This paragraph (and subparagraphs as needed) shall present the database-wide design decisions for the EELV database, that is, decisions about the database's behavioral design (how it will behave, from a user's point of view, in meeting its requirements, ignoring internal implementation) and other decisions affecting further design of the database. If all such decisions are explicit in the system or CSCI requirements, this section shall so state. Design decisions that respond to requirements designated critical, such as those for safety, security, or privacy, shall be placed in separate subparagraphs. If a design decision depends upon system states or modes, this dependency shall be indicated. If some or all of the design decisions are described in the documentation of a commercial DBMS or elsewhere in this SADD, they may be referenced from this section. Design conventions needed to understand the design shall be presented or referenced. Examples of database-wide design decisions are the following: a. Design decisions regarding queries or other inputs the database will accept and outputs (displays, reports, messages, responses, etc.) it will produce, including interfaces with other systems, HWCIs, CSCIs, and users. Information contained in other sections of this document or in other interface documents may be referenced. Design decisions on database behavior in response to each input or query, including actions, response times and other performance characteristics, selected equations/algorithms/rules, disposition, and handling of unallowed inputs Design decisions on how databases/data files will appear to the user
b.
c.
Annex F, CDRLs
F04701-95-R-0009 (19)
d.
Design decisions on the database management system to be used (including name, version/release) and the type of flexibility to be built into the database for adapting to changing requirements Design decisions on the levels and types of availability, security, privacy, and continuity of operations to be offered by the database Design decisions on database distribution (such as client/server), master database file updates and maintenance, including maintaining consistency, establishing/reestablishing and maintaining synchronization, enforcing integrity and business rules Design decisions on backup and restoration including data and process distribution strategies, permissible actions during backup and restoration, and special considerations for new or non-standard technologies such as video and sound Design decisions on repacking, sorting, indexing, synchronization, and consistency including automated disk management and space reclamation considerations, optimizing strategies and considerations, storage and size considerations, and population of the database and capture of legacy data
e.
f.
g.
h.
7. Database design. This section shall be divided into the following paragraphs to describe the design of each EELV database. 7.X (EELV database name and project-unique identifier). This paragraph shall be divided into the following subparagraphs to describe the design of the database. The number of levels of design and the names of those levels shall be based on the design methodology used. Examples of database design levels include conceptual, internal, logical, and physical. If part or all of the design depends upon system states or modes, this dependency shall be indicated. Design conventions needed to understand the design shall be presented or referenced. Note: This DID uses the term "data element assembly" to mean any entity, relation, schema, field, table, array, etc., that has structure (number/order/grouping of data elements) at a given design level (e.g., conceptual, internal, logical, physical) and the term "data element" to mean any relation, attribute, field, cell, data element, etc. that does not have structure at that level.
7.x.y (Name of database design level). This paragraph shall identify a database design level and shall describe the data elements and data element assemblies of the database in the terminology of the selected design method. The information shall include the following, as applicable, presented in any order suited to the information to be provided: a. Characteristics of individual data elements in the database design, such as: 1) Names/identifiers a) Project-unique identifier
Annex F, CDRLs
20
F04701-95-R-0009 (20)
2) 3) 4) 5) 6) 7) 8) 9) b.
b) Non-technical (natural-language) name c) DoD standard data element name d) Technical name (e.g., field name in the database) e) Abbreviation or synonymous names Data type (alphanumeric, integer, etc.) Size and format (such as length and punctuation of a character string) Units of measurement (such as meters, dollars, nanoseconds) Range or enumeration of possible values (such as 0-99) Accuracy (how correct) and precision (number of significant digits) Priority, timing, frequency, volume, sequencing, and other constraints, such as whether the data element may be updated and whether business rules apply Security and privacy constraints Sources (setting/sending entities) and recipients (using/receiving entities)
Characteristics of data element assemblies (records, messages, files, arrays, displays, reports, etc.) in the database design, such as: 1) Names/identifiers a) Project-unique identifier b) Non-technical (natural language) name c) Technical name (e.g., record or data structure name in code or database) d) Abbreviations or synonymous names Data elements in the assembly and their structure (number, order, grouping) Medium (such as disk) and structure of data elements/assemblies on the medium Visual and auditory characteristics of displays and other outputs (such as colors, layouts, fonts, icons and other display elements, beeps, lights) Relationships among assemblies, such as sorting/access characteristics Priority, timing, frequency, volume, sequencing, and other constraints, such as whether the assembly may be updated and whether business rules apply Security and privacy constraints Sources (setting/sending entities) and recipients (using/receiving entities)
2) 3) 4) 5) 6) 7) 8)
8. Requirements traceability. This section shall contain: a. Traceability from each software unit (identified in section 4 of this SADD) to the CSCI requirements allocated to it Traceability from each CSCI requirement to the software units (identified in section 4 of this SADD) to which it is allocated Traceability from each interface (identified in section 5 of this SADD) to the system, CSCI, and/or interface requirements addressed by the interface design
Annex F, CDRLs
b.
c.
F04701-95-R-0009 (21)
d.
Traceability from each system, CSCI, and/or interface requirement that affects an interface (identified in section 5 of this SADD) to the interface that addresses it Traceability from each database (identified in sections 6 and 7 in this SADD) to the system and/or CSCI requirements it addresses Traceability from each system and/or CSCI requirement that has been allocated to a database (identified in sections 6 and 7 in this SADD) to the database that addresses it
e.
f.
9. Notes. This section shall contain any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of any terms and definitions needed to understand this document. A. Appendixes. Appendixes may be used to provide information published separately for convenience in document maintenance (e.g., charts, classified data). As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided. Appendixes may be bound as separate documents for ease in handling. Appendixes shall be lettered alphabetically (A, B, etc.).
Annex F, CDRLs
22
F04701-95-R-0009 (22)
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Form Approved OMB No. 0704-0188
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A003 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: A TDP_______ TM_______ OTHER A F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
DATA ACCESSION/INTERNAL DATA 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY BI-MO C 11. AS OF DATE 12. DATE OF FIRST SUBMISSION BLK 16 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO* 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-A-3027A 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
2
BLK 4: Para 10.1, change last sentence to read “Request for internal data shall be by PCO letter.” Para 10.2, Delete second sentence and add, “documents shall be by functional area (i.e., Logistics, Quality Assurance, etc.) in alphabetical order. “Contractor format is acceptable.” Para 10.2.1a, after “RR” include “GPLR = Government Purpose License Rights.” BLK 9: The distribution statement only applies to the data that is ordered from the Data Accession/Internal Data list, and not to the Data Accession/Internal Data List. BLK 12: Initial submittal shall be 30 CD after contract award BLK 13: Bi-monthly on the 10th day of the month Note: This data item is also applicable to SMC FAR 5352.235-9000, enabling clause for General Systems Engineering and Integration (GSE&I) and SMC FAR 5352.235-9001, Enabling Clause for Technical Review. Note: Data Accession List shall include subcontractor‟s listings. * Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
Annex F, CDRLs
F04701-95-R-0009 (23)
15. TOTAL
2
G. PREPARED BY LT Jason Wilson 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_1_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A004 2. TITLE OF DATA ITEM CONFERENCE AGENDA
B. EXHIBIT A
C. CATEGORY: ADMIN TDP_______ TM_______ OTHER ADMIN F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.) DI-ADMIN-81249A 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS C 9. DIST STATEMENT REQUIRED
5. CONTRACT REFERENCE
6. REQUIRING OFFICE EELV
10. FREQUENCY ASREQ 11. AS OF DATE
12. DATE OF FIRST SUBMISSION BLK 16 13. DATE OF SUBSEQUENT SUBMISSION BLK 16
14. DISTRIBUTION b. COPIES Draft Final
EELV DMO*
2
BLK 4: Para 10.2J: This information shall be provided on an as requested basis. BLKS 12 & 13: Submit thirty 30 CD prior to major program reviews.
Annex F, CDRLs
F04701-95-R-0009 (24)
24
* Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
15. TOTAL
2
G. PREPARED BY CAPT Suzanne O‟Reilly 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_1_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002
B. EXHIBIT A
C. CATEGORY: ADMIN TDP_______ TM_______ OTHER ADMIN
Annex F, CDRLs
F04701-95-R-0009 (25)
D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A005 2. TITLE OF DATA ITEM PRESENTATION MATERIAL
E. CONTRACT/PR.NO F04701-95-R-0009
F. CONTRACTOR
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.) DI-ADMIN-81373 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS C 9. DIST STATEMENT REQUIRED
5. CONTRACT REFERENCE
6. REQUIRING OFFICE EELV
10. FREQUENCY ASREQ 11. AS OF DATE
12. DATE OF FIRST SUBMISSION BLK 16 13. DATE OF SUBSEQUENT SUBMISSION BLK 16
14. DISTRIBUTION b. COPIES Draft Final
EELV DMO*
2
BLKS 12 & 13: Copies shall be available at the major program reviews for all attendees. One copy shall be delivered within seven (7) working days after each major review. *Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy.
Annex F, CDRLs
F04701-95-R-0009 (26)
26
15. TOTAL
2
G. PREPARED BY CAPT Suzanne O‟Reilly 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_1_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A006 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: CMAN TDP_______ TM_______ OTHER CMAN F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
SYSTEM/SEGMENT INTERFACE CONTROL SPECIFICATION 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 C 11. AS OF DATE 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO* 2 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-CMAN-81314 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
2
BLK 4: Para 10.1, Use DID content as reference. Para 10.3, delete in its entirety and change to read: “This specification shall address the following: 1.0 Scope 2.0 Applicable Documents 3.0 Interface Requirements 4.0 Quality Assurance Provisions 5.0 Notes Contractor format is acceptable.” BLK 12: A draft shall be submitted 30 CD prior to the tailored System Requirements Review. BLK 13: An update to the draft shall be submitted 90 CD after the tailored System
Annex F, CDRLs
F04701-95-R-0009 (27)
Requirements Review. The final draft shall be submitted 30 CD prior to the tailored Preliminary Design Review. Any changes as a result of the tailored Preliminary Design Review, shall be reflected in an updated draft submitted 14 CD prior to the EOC. * Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy.
15. TOTAL
2
2
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_1_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A007 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: E TDP_______ TM_______ OTHER E F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
CONFIGURATION ITEM DEVELOPMENT SPECIFICATION 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY Annex F, CDRLs 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION
4. AUTHORITY (Data Acquisition Document No.) DI-E-3102 7. DD 250 REQ 9. DIST STATEMENT
F04701-95-R-0009 (28)
28
REQUIRED LT 8. APP CODE N/A 16. REMARKS C 11. AS OF DATE BLK 16 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO* b. COPIES Draft Final
2
BLK 4: Para 7.0: Change to read: “The development specification(s) establishes the performance requirements which the configuration item(s) must satisfy upon completion of the development phase. A development specification is required for each configuration item allocated from the system specification which established the functional baseline or from a higher level configuration item or for a non-system CI.” Para 9.0: Delete references listed Para 10.1: Change to read: “The Contractor shall prepare a development specification for each configuration item.” Para 10.2: Change to read: “Contractor format is acceptable. Specifications shall contain six numbered sections, and appendices as required, titled and numbered as shown below: 1.0 Scope 2.0 Applicable Documents 3.0 System Requirements 4.0 Quality Assurance Provisions 5.0 Preparation for Delivery 6.0 Notes” BLK 12 and 13: Submit the draft 30 CD prior to the tailored Preliminary Design Review. Any changes as a result of the tailored Preliminary Design Review, shall be reflected in an updated draft submitted 14 CD prior to the EOC. *Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
15. TOTAL
2
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_1_Pages Form Approved
J. DATE
Annex F, CDRLs
F04701-95-R-0009 (29)
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
OMB No. 0704-0188
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A008 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: F TDP_______ TM_______ OTHER F F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
CONTRACT FUNDS STATUS REPORT 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY QRTLY C 11. AS OF DATE BLK 16 12. DATE OF FIRST SUBMISSION BLK 16 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO* 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-F-6004B 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
2
BLK 4: Para 7.1 In second sentence delete (as defined in DAR 3-404.2) Para 7.4.2 In first sentence delete references to DAR 7-203.4 and DAR 7-104.35 Para 7.4.3 Delete last two sentences Para 9.0 Delete all references Para 10.3.1 Delete second sentence BLK 12: Date of 1st Submission shall be no later than the 22nd day following the end of the first Government fiscal quarter following contract award BLK 13: Not later than the 22nd day after the end of each of the following Government fiscal quarters a. Report by CLIN, appropriation and fiscal year. b. CFSR data shall be reconciled to the Government‟s fiscal year (FY) end at 30 September if the Contractor‟s FY does not coincide with the Government‟s. c. Report shall contain forecast by month for the next six months, by quarter for the remaining fiscal year, and by year for the remaining fiscal years. * Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
Annex F, CDRLs
F04701-95-R-0009 (30)
30
15. TOTAL
2
G. PREPARED BY MAJ Delane Aguilar 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_1_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A009 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: ILSS TDP_______ TM_______ OTHER ILSS F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE SYSTEM ANALYSIS REPORT 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES Draft Final
SYSTEM DESIGN TRADE STUDY REPORT 5. CONTRACT REFERENCE
4. AUTHORITY (Data Acquisition Document No.) DI-ILSS-81021 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS C 9. DIST STATEMENT REQUIRED
11. AS OF DATE
13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO* 2
2
BLK 4: Para 7.1: Change to read: “This DID contains the format and preparation instructions for the System/Design Trade Study Report.” Para 7.4: Change to read: ...“the contractual Integrated Task and Management Plan
Annex F, CDRLs
F04701-95-R-0009 (31)
(ITAMP).” Para 10.2.4: Add after the first sentence: “The design selection shall consider the sensitivity parameters on significant characteristics as listed in 10.2.2.” BLK 12: The logistics trade study to analyze GLO objective 1.1b) and the Mission C life cycle cost trade study to analyze GLO objective 1.1i) shall be submitted at the tailored System Requirements Review. A draft of all the other trades shall be submitted 90 CD after the tailored System Requirements Review. BLK 13: An update to the logistics trade study and Mission C life cycle cost trade study shall be submitted 60 CD after the first submittal and the final version shall be submitted 60 CD after the update is submitted. The final draft of all the other trades shall be submitted 30 CD prior to the tailored Preliminary Design Review. Any changes as a result of the tailored Preliminary Design Review shall be reflected in an updated draft submitted 14 CD prior to EOC. *Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
15. TOTAL
2
2
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_1_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002
B. EXHIBIT A
C. CATEGORY: IPSC TDP_______ TM_______ OTHER IPSC
Annex F, CDRLs
F04701-95-R-0009 (32)
32
D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A010 2. TITLE OF DATA ITEM
E. CONTRACT/PR.NO F04701-95-R-0009
F. CONTRACTOR
3. SUBTITLE
SYSTEM/SUBSYSTEM SPECIFICATION 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 C 11. AS OF DATE 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO* 2 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-IPSC-81431 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
2
BLK 4: Para 10.2.3.3: Replace the second sentence with “The paragraph may reference one or more system-level Interface Requirements Specifications (IRSs) or other system-level interface requirements documents, such as Interface Control Specifications (ICSs), containing these requirements. Any reference system-level interface requirements documents must be delivered with the completed SSS and contain the information described in 3.3.1 through 3.3x below.” Para 10.2.3.4: Replace the first sentence with “The paragraph shall specify the requirements, if any, imposed on interfaces internal to the system, including both subsystem-to-subsystem interface and interfaces between components within subsystems.” Replace the second sentence with “If all internal interfaces are left to the design or to requirement specifications for system components and/or interfaces, this fact shall be so stated.” Para 10.2.3.5 Replace this paragraph with the following: 3.11 System quality factors. This paragraph shall be divided into the following subparagraphs which specify the applicable requirements pertaining to system quality factors. 3.11.1 Reliability: This paragraph shall specify reliability requirements in quantitative terms and shall define the conditions under which the reliability requirements are to be met. This paragraph may include a reliability apportionment model to support apportionment of reliability values assigned to system capabilities for their share in achieving required system reliability.
Annex F, CDRLs
F04701-95-R-0009 (33)
15. TOTAL
2
2
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_5_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A010 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: IPSC TDP_______ TM_______ OTHER IPSC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
SYSTEM/SUBSYSTEM SPECIFICATION 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 C 11. AS OF DATE 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-IPSC-81431 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
3.11.2 Maintainability: This paragraph shall specify quantitative maintainability requirements for the system. The requirements shall apply to maintenance in the planned maintenance and support environments, which shall include at least the organizational environment and the depot environment, and shall be stated in quantitative terms. Examples are: a. Mean and maximum down time, reaction time, turnaround time, mean and maximum times to repair, mean time between maintenance actions; b. Maximum effort required to locate and remedy an error; c. Maintenance man-hours per specific maintenance action, operational ready rate, maintenance hours per operating hour, frequency of preventive maintenance; d. Number of people, skills levels, and support equipment; and e. Maintenance cost per operating hour. 3.11.3 Availability. This paragraph shall specify the degree to which the system shall be in an operable and committable state at the start of the mission(s), where the mission(s) is/are called
Annex F, CDRLs
F04701-95-R-0009 (34)
34
for at an unknown (random) point in time. 3.11.4 Failure/recovery/restoral/degraded operations requirements. This paragraph shall identify possible failures of the system, the consequences of such failures in terms of the system, the consequences of such failures in terms of system performance, and alternative courses of action to be provided to satisfy system requirements. For example, these may include back-up/redundant provisions, fallback on other systems, retention/restoration priorities in the event of degraded operation, restart/recovery provisions, and other measures such as pre-establishment of alternate sites and capability of communications re-routing. 3.11.5 Additional quality factors. This paragraph shall specify any other system quality requirements not defined in the above paragraphs, for example, integrity, efficiency, correctness, flexibility (the ability to be easily modify software for a new environment), reusability (the ability to be used in multiple applications), testability (the ability to be easily and thoroughly tested), and usability (the ability to be easily learned and used.)
15. TOTAL
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_2_of_5_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A010 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: IPSC TDP_______ TM_______ OTHER IPSC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
SYSTEM/SUBSYSTEM SPECIFICATION 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY Annex F, CDRLs 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION
4. AUTHORITY (Data Acquisition Document No.) DI-IPSC-81431 7. DD 250 REQ 9. DIST STATEMENT
F04701-95-R-0009 (35)
REQUIRED LT 8. APP CODE N/A 16. REMARKS C 11. AS OF DATE BLK 16 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 b. COPIES Draft Final
Para 10.2.3.12: Replace item (c) with “Physical characteristics of the system (such as weight limits, dimensional limits, color protective coating), interchangeability of parts; ability to be transported from one location to another, and identification of all system elements that, due to operational or functional considerations, will be unsuitable for normal transportation methods; ability to be carried or set up by one, or a given number, of persons.” Replace item (f) with “Flexibility and expandability that must be provided to support areas of growth or changes in technology, threat, or mission, and identification of system elements that require spare capacity to support flexibility and expansion.” Para 10.2.4: Replace items (a) through (e) with the following: a. Demonstration: Demonstration is the verification method used to verify requirements by exercising or operating the system or a part of the system in which instrumentation or special test equipment is not required beyond that inherently provided in the system being verified. In the demonstration method, sufficient data for requirements verification can be obtained by observing functional operation of the system or a part of the system. When this verification method generates data that is recorded by inherent instrumentation, inherent test equipment or operational procedures, any analysis that must be performed using the data collected during the demonstration is analysis methods of verification described below. b. Test: Test is the verification method used to verify requirements by exercising or operating the system or a part of the system using instrumentation (hardware and/or software) or special test equipment that is not an integral part of the system being verified. The test method by its nature generates data, which is recorded by the instrumentation, test equipment, or procedures. Analysis or review is performed on the data derived from the testing. This analysis, as described here, is an integral part of this method and should not be confused with the analysis method of verification described below.
15. TOTAL
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_3_of_5_Pages
J. DATE
Annex F, CDRLs
F04701-95-R-0009 (36)
36
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Form Approved OMB No. 0704-0188
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A010 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: IPSC TDP_______ TM_______ OTHER IPSC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
SYSTEM/SUBSYSTEM SPECIFICATION 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 C 11. AS OF DATE 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-IPSC-81431 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
c. Analysis: Analysis is the verification method used to verify requirements by determining qualitative and quantitative properties and performance by studying and examining engineering drawings, software, and hardware flow diagrams, software and hardware specifications, and other software and hardware documentation (e.g., COTS vendor documentation), or by performing modeling, simulation, and/or calculations and analyzing the results. Analysis techniques include interpretation or interpolation/extrapolation of analytical or empirical data under defined conditions or reasoning to show compliance with requirements. Similarity analysis is used in lieu of the test or demonstration methods when it can be shown that an item is similar to or identical in design to another item that has been previously certified to equivalent or more stringent criteria. d. Inspection: Inspection is the verification method used to verify characteristics by inspecting engineering documentation produced during product development/modification (including both hardware and software documentation) or by inspection of the product itself to verify conformance with specified requirements. Inspection is generally nondestructive and consists of visual inspections or simple measurements without the use of precision measurement equipment. Verification by inspection will include assessment of similarities of subsequent elements to the first item generated based on a common design. e. Special qualification methods: Special qualification methods include techniques that do not belong to the methods defined in (a) through (d) above, for example, formal proofs. Para 10.2.5: Replace this paragraph with the following: For systems-level specifications, this paragraph shall contain:
Annex F, CDRLs
F04701-95-R-0009 (37)
a. Traceability from each system requirement in this specification (the SSS) to the requirements(s) in the System Performance Document (SPD) that it addresses. (Alternatively, this may be provided by annotating each requirement in section 3.) b. Traceability from each requirement in the SPD to the requirement(s) in the SSS that address it. All SPD requirements shall be accounted for. Those that trace to system requirements contained in interface requirements documents shall reference one or more requirements contained in those documents.
15. TOTAL
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_4_of_5_Pages
J. DATE
Annex F, CDRLs
F04701-95-R-0009 (38)
38
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Form Approved OMB No. 0704-0188
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A010 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: IPSC TDP_______ TM_______ OTHER IPSC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
SYSTEM/SUBSYSTEM SPECIFICATION 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 C 11. AS OF DATE 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-IPSC-81431 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
For subsystem-level specifications, this paragraph shall contain: a. Traceability from each subsystem-level requirement in this specification to the system-level requirements(s) it addresses. (Alternatively, this may be provided by annotating each requirement in section 3.) Note: Each level of system refinement may result in requirements not directly traceable to higher level requirements. For example, a system architectural design that creates two subsystems may result in requirements about how the subsystem may result in these interfaces are not covered in system requirements. Such requirement may be traced to a general requirement or to the system design decisions that resulted in their generation. b. Traceability from each system requirement that has been allocated to the subsystem requirements that address it. All system requirements allocated to the subsystem requirements contained in interface requirements documents shall reference one or more requirements contained in those documents. BLK 12: A draft shall be submitted 30 CD prior to the tailored System Requirements Review. BLK: 13: An update to the draft shall be submitted 90 CD after the tailored System Requirements Review. The final draft shall be submitted 30 CD prior to the tailored Preliminary Design Review. Any changes as a result of the tailored Preliminary Design Review shall be reflected in an updated draft submitted 14 CD prior to EOC. * Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
Annex F, CDRLs
F04701-95-R-0009 (39)
15. TOTAL
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_5_of_5_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A011 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: IPSC TDP_______ TM_______ OTHER IPSC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
SYSTEM/SUBSYSTEM DESIGN DESCRIPTION 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 C 11. AS OF DATE 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO* 2 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-IPSC-81432 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
2
BLK 4: Para 10.2.3.a: In first sentence, delete parenthetical reference to 4.3.x. Change second sentence to read: “If part or all of this information is given in Interface Design Descriptions (IDDs) or
Annex F, CDRLs
F04701-95-R-0009 (40)
40
Interface Control Specifications (ICSs), they may be referenced.” Para 10.2.3.c: In first sentence, delete parenthetical reference to 4.3.x. Para 10.2.4.1.e: Delete second sentence and all subparagraphs (10.2.4.1.e(1) through 10.2.4.1.e(6)). Para 10.2.4.1.g (Added): Add paragraph 10.2.4.1.g as follows: “Describe physical and functional systems/subsystem configuration characteristics in terms of form, fit, and function. Include developmental design drawings, schematics, and data summaries as necessary. Configuration characteristics or design decisions derived from trade studies, analyses, or risk mitigation demonstrations may be referenced to the appropriate CDRL item. Para 10.2.4.3.1: Change second sentence to read: “If part or all of this information is contained in Interface Design Descriptions (IDDs), Interface Control Specifications (ICSs), or elsewhere, they may be referenced.” Para 10.2.4.3.x: Delete entire paragraph and all subparagraphs (10.2.4.3.x.(a) through 10.2.4.3.x.(g)). BLK 12: A draft shall be submitted 90 CD after the tailored System Requirements Review. BLK 13: The final draft shall be submitted 30 CD prior to the tailored Preliminary Design Review. Any changes as a result of the tailored Preliminary Design Review shall be reflected in an updated draft submitted 14 CD prior to the EOC. * Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy per submittal
15. TOTAL
2
2
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_1_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002
B. EXHIBIT A
C. CATEGORY: IPSC TDP_______ TM_______ OTHER IPSC
Annex F, CDRLs
F04701-95-R-0009 (41)
D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A012 2. TITLE OF DATA ITEM
E. CONTRACT/PR.NO F04701-95-R-0009
F. CONTRACTOR
3. SUBTITLE
SOFTWARE REQUIREMENTS SPECIFICATION 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 C 11. AS OF DATE 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO* 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-IPSC-81433 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
2
BLK 4: Para 10.2.3: Replace the second sentence with “CSCI requirements are software requirements generated to satisfy the higher level (e.g., system-level and, if applicable, subsystem-level) requirements allocated to this CSCI.” Para 10.2.3.2.x: After fourth sentence add: “Equations that are required to be implemented shall be specified with mathematical symbols defined. Each requirement shall be stated in such a way that an objective test can be defined for it. Design-level information shall not be included in the SRS but shall be included in the SADD. Data in each Para 3.2.x shall identify those CSCI capabilities that either generate or receive CSCI external interface data, with each interface identified by its project-unique identifier.” Para 10.2.3.3: Delete the first sentence. Replace the second sentence with “This paragraph shall reference the Interface Requirements Specification(s) (IRS(s)) and/or interface requirements applicable to this CSCI. The information specified in 3.3.1 and 3.3.x below shall be included in the IRS(s)/ICS(s). Para 10.2.3.11: Replace the second sentence with the following: “Examples include quantitative requirements regarding reliability, maintainability, availability, flexibility, portability, reusability, testability, usability, and other attributes, as applicable.” Para 10.2.4: Replace items (a) through (e) with the following:
Annex F, CDRLs
F04701-95-R-0009 (42)
42
15. TOTAL
2
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 MAR 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_3_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A012 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: IPSC TDP_______ TM_______ OTHER IPSC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
SOFTWARE REQUIREMENTS SPECIFICATION 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 C 11. AS OF DATE 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-IPSC-81433 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
a. Demonstration: Demonstration is the verification method used to verify requirements by exercising or operating the system or a part of the system in which instrumentation or special test equipment is not required beyond that inherently provided in the system being verified. In the demonstration method, sufficient data for requirements verification can be obtained by observing functional operation of the system or a part of the system. When this verification method generates data that is recorded by inherent instrumentation, inherent test equipment or operational procedures, any analysis that must be performed using the data collected during the demonstration is analysis methods of verification described below. b. Test: Test is the verification method used to verify requirements by exercising or operating the system or a part of the system using instrumentation (hardware and/or software) or special test equipment that is not an integral part of the system being verified. The test method by its nature generates data, which is recorded by the instrumentation, test equipment, or procedures. Analysis or review is performed on the data derived from the testing. This analysis, as described here, is an integral part of this method and should not be confused with the analysis method of
Annex F, CDRLs
F04701-95-R-0009 (43)
verification described below. c. Analysis: Analysis is the verification method used to verify requirements by determining qualitative and quantitative properties and performance by studying and examining engineering drawings, software, and hardware flow diagrams, software and hardware specifications, and other software and hardware documentation (e.g., COTS vendor documentation), or by performing modeling, simulation, and/or calculations and analyzing the results. Analysis techniques include interpretation or interpolation/extrapolation of analytical or empirical data under defined conditions or reasoning to show compliance with requirements. Similarity analysis is used in lieu of the test or demonstration methods when it can be shown that an item is similar to or identical in design to another item that has been previously certified to equivalent or more stringent criteria.
15. TOTAL
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_2_of_3_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A012 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: IPSC TDP_______ TM_______ OTHER IPSC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
SOFTWARE REQUIREMENTS SPECIFICATION 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION
4. AUTHORITY (Data Acquisition Document No.) DI-IPSC-81433 7. DD 250 REQ 9. DIST STATEMENT REQUIRED
Annex F, CDRLs
F04701-95-R-0009 (44)
44
LT 8. APP CODE N/A 16. REMARKS C 11. AS OF DATE
BLK 16 13. DATE OF SUBSEQUENT SUBMISSION BLK 16
b. COPIES Draft Final
d. Inspection: Inspection is the verification method used to verify characteristics by inspecting engineering documentation produced during product development/modification (including both hardware and software documentation) or by inspection of the product itself to verify conformance with specified requirements. Inspection is generally nondestructive and consists of visual inspections or simple measurements without the use of precision measurement equipment. Verification by inspection will include assessment of similarities of subsequent elements to the first item generated based on a common design. e. Special qualification methods: Special qualification methods include techniques that do not belong to the methods defined in (a) through (d) above, for example, formal proofs. Para 10.5: In the first sentence in both items (a) and (b), replace “or subsystem” with “and subsystem.” In item (b) replace the last sentence with “Those that trace to CSCI-level requirements contained in IRSs shall reference requirements in those IRSs.” BLK 12 and 13: The draft shall be submitted 30 CD prior to the tailored Preliminary Design Review. Any changes as a result of the tailored Preliminary Design Review shall be reflected in an updated draft submitted 14 CD prior to the EOC. *Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy.
15. TOTAL
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_3_of_3_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST
Annex F, CDRLs
F04701-95-R-0009 (45)
(1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A013 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: IPSC TDP_______ TM_______ OTHER IPSC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
INTERFACE REQUIREMENTS SPECIFICATION 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 C 11. AS OF DATE 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO* 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-IPSC-81434 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
2
BLK 4: Para 10.2.4: Replace items (a) through (e) with the following: a. Demonstration: Demonstration is the verification method used to verify requirements by exercising or operating the system or a part of the system in which instrumentation or special test equipment is not required beyond that inherently provided in the system being verified. In the demonstration method, sufficient data for requirements verification can be obtained by observing functional operation of the system or a part of the system. When this verification method generates data that is recorded by inherent instrumentation, inherent test equipment or operational procedures, any analysis that must be performed using the data collected during the demonstration is an integral part of this method and should not be confused with the analysis methods of verification described below. b. Test: Test is the verification method used to verify requirements by exercising or operating the system or a part of the system being verified. The test method by its nature generates data, which is recorded by the instrumentation, test equipment, or procedures. Analysis or review is performed on the data derived from the testing. This analysis, as described here, is an integral part of this method and should not be confused with the analysis method of verification described below. c. Analysis: Analysis is the verification method used to verify requirements by determining qualitative and quantitative properties and performance by studying and examining engineering drawings, software, and hardware flow diagrams, software and hardware specifications, and other software and hardware documentation (e.g., COTS vendor documentation ), or by performing modeling, simulation, and/or calculations and analyzing the results. Analysis techniques include interpretation or interpolation/extrapolation of analytical or empirical data under defined conditions or reasoning to show compliance with requirements. Similarity analysis is used in lieu of the test or demonstration methods when it can be shown that an item is similar to or
Annex F, CDRLs
F04701-95-R-0009 (46)
46
identical in design to another item that has been previously certified to equivalent or more stringent criteria.
15. TOTAL
2
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_3_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A013 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: IPSC TDP_______ TM_______ OTHER IPSC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
INTERFACE REQUIREMENTS SPECIFICATION 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 C 11. AS OF DATE 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-IPSC-81434 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
d. Inspection: Inspection is the verification method used to verify characteristics by inspecting engineering documentation produced during product development/modification (including both hardware and software documentation) or by inspection of the product itself to verify conformance with specified requirements. Inspection is generally nondestructive and consist of visual inspections or simple measurements without the use of precision measurement equipment. Verification by inspection will include assessment of similarities of subsequent elements to the
Annex F, CDRLs
F04701-95-R-0009 (47)
first item generated based on a common design. e. Special qualification methods: Special qualification methods include techniques that do not belong to the methods defined in (a) through (d) above, for example, formal proofs. Para 10.2.5: Delete the first sentence. Replace second sentence with “For each interfacing entity covered by this IRS, this paragraph shall contain:”. Replace items (a) and (b) with the following: a. Traceability from requirements in the IRS to higher level requirements: Traceability from each requirement imposed on the entity in this specification (the IRS) to the higher level requirement(s) that it addresses (e.g., for CI-level IRS, those requirements documented in the SSSs and higher level IRSs and /or ICSs). (Alternatively, this may be provided by annotating each requirement in section 3) b. Traceability from higher level requirements to requirements in the IRS: Traceability from each higher level requirement that has been allocated to the interfacing entity and that affects an interface covered in this specification (the IRS) to the requirements in this specification that addresses it. (Higher level requirements include, for example, those in the SSS and higher level IRSs and/or ICSs.)
15. TOTAL
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_2_of_3_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION
B. EXHIBIT A
C. CATEGORY: IPSC TDP_______ TM_______ OTHER IPSC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
Annex F, CDRLs
F04701-95-R-0009 (48)
48
1. DATA ITEM NO. A013
2. TITLE OF DATA ITEM INTERFACE REQUIREMENTS SPECIFICATION 5. CONTRACT REFERENCE
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.) DI-IPSC-81434 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS C 9. DIST STATEMENT REQUIRED
6. REQUIRING OFFICE EELV
10. FREQUENCY
12. DATE OF FIRST SUBMISSION BLK 16
14. DISTRIBUTION b. COPIES Draft Final
11. AS OF DATE
13. DATE OF SUBSEQUENT SUBMISSION BLK 16
c. Traceability from interface requirements in the IRS to requirements at the same level for the interfacing entities addressed by the IRS (i.e., requirements for the interfacing systems, subsystems, CSCIs or HWCI): Traceability from each requirement imposed on the interfacing entity in this specification (the IRS) to the associated requirement(s) documented in the entity‟s requirements specification (e.g., if the entity is a CSCI, the requirement is documented in the CSCI‟s Software Requirements Specification (SRS); if it is a system/subsystem, the requirement is documented in the applicable SSS). BLK 12 and 13: The draft shall be submitted 30 CD prior to the tailored Preliminary Design Review. Any changes as a result of the tailored Preliminary Design Review shall be reflected in an updated draft submitted 14 CD prior to EOC. *Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
Annex F, CDRLs
F04701-95-R-0009 (49)
15. TOTAL
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_3_of_3_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A014 2. TITLE OF DATA ITEM STATUS REPORT
B. EXHIBIT A
C. CATEGORY: MGMT TDP_______ TM_______ OTHER MGMT F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE METRICS STATUS REPORT 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-MGMT-80368 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS C 9. DIST STATEMENT REQUIRED
11. AS OF DATE
13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO*
2
BLK 4: Paragraph 10.2.2.1h: Change to read: “Provide metrics information, as described in the ITAMP, to measure the following attributes: size, effort, rework, schedule, and quality. Software quality metrics shall include the following: Requirements Progress: Specification Completeness Developmental Progress: Design Document Completeness, Design Completeness Staffing: Actual vs. Planned Level/Turnover Rate for: Major Software Function, CSCI, and Skill Level Developmental Resource Utilization: CPU, RAM, DISK, ROM, I/O Channel, Workstation Design Complexity: Structure, Information Flow, Data Structures Target Resource Utilization: CPU, RAM, DISK, I/O Channel Volatility: Requirements, Design Traceability: Between Requirements, Between Requirements and Design Defect Density: Requirements, Design Problem Reports/Action Items/Issues Provide the following system level metrics information as described in the ITAMP: Requirements Progress: Specification Completeness
Annex F, CDRLs
F04701-95-R-0009 (50)
50
Development Progress: Design Document Completeness, Design Completeness Volatility: Requirements, Design Traceability: Between Requirements, Between Requirements and Design Problem Reports/Action Items/Issues” For each of these metrics, provide: - Data covering the current reporting period in graphic and tabular form, as described in the ITAMP. Where appropriate, show 12 months of history and 6 months of projections. Revised plans may be added to the graphs, but previous plans, including the original plan, shall not be removed. - Metrics primitive data for the current reporting period on IBM PC DOS-compatible floppy disks accompanied by format or other descriptive information needed to read these disks. - Explanations and interpretations or reported metric data, including deviations from expected or projected values.
15. TOTAL
2
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_2_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A014 2. TITLE OF DATA ITEM STATUS REPORT
B. EXHIBIT A
C. CATEGORY: MGMT TDP_______ TM_______ OTHER MGMT F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE METRICS STATUS REPORT 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY QRTLY 12. DATE OF FIRST SUBMISSION BLK 16 13. DATE OF SUBSEQUENT SUBMISSION 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-MGMT-80368 7. DD 250 REQ LT 8. APP CODE C 9. DIST STATEMENT REQUIRED
11. AS OF DATE
Annex F, CDRLs
F04701-95-R-0009 (51)
N/A 16. REMARKS
BLK 16
Paragraph 10.2.2.1: Add item “j” with the following text: “Where appropriate, show 12 months of history and 6 months of projections. Revised plans may be added to the graphs, but previous plans, including the original plan, shall not be removed.” Delete paragraphs 10.2.2.3 through 10.2.2.5 BLK 12: Initial submission shall be at the tailored System Requirements Review. BLK 13: Quarterly by the 10th day of the month with the final submittal on the 10th day of the final month of the contract. *Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy.
15. TOTAL
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_2_of_2_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington
Annex F, CDRLs
F04701-95-R-0009 (52)
52
Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A015 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: MISC TDP_______ TM_______ OTHER MISC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
MANUFACTURING PLAN 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 C 11. AS OF DATE 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO* 2 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-MISC-80074 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
2
BLK 4: Para 7.1: Delete second sentence Para 7.2: Change second sentence to read: “Tailoring may be to the „A‟ level of application for the LCCV.” Delete third sentence. Para 10.2: Delete the following sections and section references: 10.2.2.2, 10.2.3.7.2, 10.2.6. Para 10.2.1.2: Add as the second sentence: “Identify members of the manufacturing management team which are involved in the design Integrated Product Teams.” Para 10.2.1.3: Replace paragraph to read: “The section shall include operating procedures for integrating manufacturing into the design.” Para 10.2.2.3: Delete second sentence. Para 10.2.2.4: Change first sentence to read: “This section shall include a summary of manufacturing risks.” Para 10.2.2.4: Delete second sentence. Para 10.2.3.1: Change second sentence to read: “They will include procedure for performing producibility analyses to include capability analyses, identification of groups ...” Para 10.2.3.2: Add: g. Capability analyses (Cpk) Para 10.2.3.4: Change f. to read: “Show how during production, Contractor will provide periodic...” Para 10.2.3.6: Delete fourth sentence. Para 10.2.3.7: Delete the words “weapon system” Para 10.2.3.7.1: Change to read: “Critical Forms, Parts, and Materials. This element identifies all critical forms, parts, and materials used, or planned to be used, in the system, and shall list them on the “Critical Form, Part and Material List” format shown in figure 1. The “Critical Form, Part, and Material List” is supported with documentation of efforts the Contractor and/or subcontractors and vendors have taken to eliminate or mitigate risks due to foreign dependence, materials shortages, and limited surge capacity.” Para 10.2.4: Change first sentence to read: “Explain how results of analyses performed during manufacturing surveillance will be used in the format used by the Contractor.”
Annex F, CDRLs
F04701-95-R-0009 (53)
Delete Table 1.
15. TOTAL
2
2
G. PREPARED BY LT Mary Jo Neenan 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_2_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A015 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: MISC TDP_______ TM_______ OTHER MISC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE
MANUFACTURING PLAN 5. CONTRACT REFERENCE 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 C 11. AS OF DATE 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES Draft Final
4. AUTHORITY (Data Acquisition Document No.) DI-MISC-80074 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS 9. DIST STATEMENT REQUIRED
Delete Table 1 BLK 12: A draft shall be submitted 90 CD after the tailored System Requirements Review. BLK 13: The final draft shall be submitted 30 CD prior to the tailored Preliminary Design Review. Any changes as a result of the tailored Preliminary Design Review shall be reflected in an updated draft submitted 14 CD prior to EOC. * Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
Annex F, CDRLs
F04701-95-R-0009 (54)
54
15. TOTAL
2
2
G. PREPARED BY LT Mary Jo Neenan 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_2_of_2_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A016 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: MISC TDP_______ TM_______ OTHER MISC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE DEMONSTRATION REPORTS 6. REQUIRING OFFICE
TECHNICAL REPORT - STUDY SERVICES 5. CONTRACT REFERENCE Annex F, CDRLs
4. AUTHORITY (Data Acquisition Document
F04701-95-R-0009 (55)
No.) DI-MISC-80508 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS C 11. AS OF DATE 9. DIST STATEMENT REQUIRED 10. FREQUENCY
EELV 12. DATE OF FIRST SUBMISSION BLK 16 13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO* 2 14. DISTRIBUTION b. COPIES Draft Final
2
BLK 4: Paragraph 10.1, delete in its entirety and change to read “Contractor format is acceptable.” Paragraph 10.2(c) delete in its entirety and change to read: “The report shall include sections discussing: 1. Identification of risk factors 2. Assessment of the risks 3. Demonstrations conducted 4. Demonstrations results and impact of risk mitigation” BLK 12: Submit a draft 90 CD after the tailored System Requirements Review. BLK 13: Submit the final draft 30 CD prior to the tailored Preliminary Design Review. Any changes as a result of the tailored Preliminary Design Review shall be reflected an updated draft submitted 14 CD prior to the EOC. *Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
15. TOTAL
2
2
G. PREPARED BY
H. DATE
I. APPROVED BY
J. DATE
Annex F, CDRLs
F04701-95-R-0009 (56)
56
CAPT Heather Knight 17. PRICE GROUP
17 Mar 95 18. ESTIMATED TOTAL PRICE Page_1_of_1_Pages Form Approved OMB No. 0704-0188
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A017 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: MISC TDP_______ TM_______ OTHER MISC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE MODELING REPORT 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES Draft Final
TECHNICAL REPORT - STUDY SERVICES 5. CONTRACT REFERENCE
4. AUTHORITY (Data Acquisition Document No.) DI-MISC-80508 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS C 9. DIST STATEMENT REQUIRED
11. AS OF DATE
13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO* 2
2
BLK 4: Para 10.1 Contractor format acceptable Para 10.2 (c)(2) Change to read: “Summary - A brief summary of the modeling efforts employed and the results obtained from them.” Para 10.2 (d) Change to read: Section II - a complete and detailed description of the modeling effort which led to the conclusions stated in Section 1 above. This includes procedures followed, development processes, capabilities and limitations of each model, and all assumptions necessary to fully understand the scope or limitations of the analysis. Rationale for significant variances from historical data or estimating relationships shall be included. The detail of this section shall be sufficient to permit full understanding of the techniques, algorithms, and data bases incorporated in each model.” BLK 12: Submit at the tailored System Requirements Review. BLK 13: Submit 30 CD prior to the tailored Preliminary Design Review event. Any changes as a result of the tailored Preliminary Design Review shall be reflected in an updated draft submitted 14 CD prior to the EOC. *Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
Annex F, CDRLs
F04701-95-R-0009 (57)
15. TOTAL
2
2
G. PREPARED BY CAPT Heather Knight 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_1_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A018 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: MISC TDP_______ TM_______ OTHER MISC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE ENVIRONMENTAL ANALYSIS REPORT 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES Draft Final
TECHNICAL REPORT - STUDY SERVICES 5. CONTRACT REFERENCE
4. AUTHORITY (Data Acquisition Document No.) DI-IPSC-80508 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS C 9. DIST STATEMENT REQUIRED
11. AS OF DATE
13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO* 2
2
BLK 4:
Annex F, CDRLs
F04701-95-R-0009 (58)
58
Para 10.3: Change to read: “A report of all technical work accomplished and information gained pertaining to EELV environmental analysis will be prepared. The environmental analysis report will identify possible environmental impacts of the proposed system concept. This report will contain an overview of the proposed concept, including viable alternatives that may reduce environmental impact. It will also contain a description of all environmental impacts. It will also contain a description of all environments affected by the system and possible impacts at these locations. Any anticipated permits, regulatory reviews, and waivers required for developmental operation of the proposed system will be identified. Finally, the report will include measures which might be taken to minimize or mitigate the environmental impacts of the proposed system. The recommended outline for this report is as follows: I. Overview of Proposed Actions and Alternatives a. Purpose of and Need for the System b. Proposed Locations c. Description of Proposed System to include: New Construction; Utilization of Existing Facilities; Description of Materials Used in System (Toxic Chemicals, Hazardous Materials, Ozone Depleting Substances, and Wastes) d. Description of Alternatives to the Proposed System II. Description of Environment and Environmental Impacts a. Potential Regions of Impact: Natural -- to include: topography; geology and soils; lower atmosphere; upper atmosphere; surface water ground water; biological resources and wetlands; and aesthetics. b. Potential Regions of Impacts: Man-made -- to include: cultural resources and native populations; socioeconomic; farmland; and population
15. TOTAL
2
2
G. PREPARED BY LT Jeff Ward 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_3_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
B. EXHIBIT
C. CATEGORY: MISC
Annex F, CDRLs
F04701-95-R-0009 (59)
0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A018 2. TITLE OF DATA ITEM
A
TDP_______
TM_______ OTHER MISC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-0009
3. SUBTITLE ENVIRONMENTAL ANALYSIS REPORT 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES Draft Final
TECHNICAL REPORT - STUDY SERVICES 5. CONTRACT REFERENCE
4. AUTHORITY (Data Acquisition Document No.) DI-MISC-80508 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS C 9. DIST STATEMENT REQUIRED
11. AS OF DATE
13. DATE OF SUBSEQUENT SUBMISSION BLK 16
c. Potential Environmental Impacts (Short Term and Cumulative) to include: air quality; ozone depletion; global climate; water quality and quantity; electromagnetic radiation; hazardous materials and management; noise; sonic booms; erosion; soil contamination; and pollution prevention (substitute processes/chemicals) III. Possible Regulatory Reviews, Permits, and Waivers Required to include: air quality; air conformity; ozone depleting chemicals; EPA-17 substances; water quality; hazardous waste; coastal zone management; threatened and endangered species; cultural resources; excavation; and marine mammals. IV. Possible Mitigation Measures to include: air quality; upper atmosphere; hydrology and water quality; geology and soils; biota; threatened or endangered species; population; socioeconomic; hazardous wastes; safety; and cultural resources (historic preservation, archaeological significance). As a separate annex (Annex A: Hazardous Materials Management Report), include a Hazardous Materials Management Report documenting efforts to eliminate or reduce the use of hazardous materials in the EELV system, system components, and support items being acquired. Include report contents and formats described by paragraph 4.4, 4.4.1, 4.4.2, and 5.3 of National Aerospace Standard (NAS) 411. Delete report contents described by paragraph 4.4.3 of NAS 411 and add the following: Paragraph 4.4.3.1 - Identify the pounds and processes (i.e., cleaning, degreasing, hand wiping, etc.) required by applicable technical data of the EPA-17 Hazardous Materials for each calendar quarter projected throughout the system life cycle.
Annex F, CDRLs
F04701-95-R-0009 (60)
60
15. TOTAL
G. PREPARED BY LT Jeff Ward 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_2_of_3_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A018 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: MISC TDP_______ TM_______ OTHER MISC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE ENVIRONMENTAL ANALYSIS REPORT 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES Draft Final
TECHNICAL REPORT - STUDY SERVICES 5. CONTRACT REFERENCE
4. AUTHORITY (Data Acquisition Document No.) DI-MISC-80508 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS C 9. DIST STATEMENT REQUIRED
11. AS OF DATE
13. DATE OF SUBSEQUENT SUBMISSION BLK 16
Paragraph 4.4.3.2 - Identify the percent reduction in total pounds of EPA - 17 Hazardous Materials used and the percent reduction in the number of processes in which EPA-17 materials are used for each calendar quarter projected throughout the system life cycle based on projected usage baseline at contract award. Paragraph 4.4.3.3 - Identify the Class II ODSs and EPCRA Section 313 chemicals by names and stock numbers and applicable technical data which requires the use of these hazardous materials. For system concepts using solid rocket motors, prepare a separate annex (Annex B: Clean Burning Propulsion System Alternatives) describing potential alternatives (clean burning solid propellants, hybrid propellants, all-liquid propulsion) that could be implemented as P4I efforts to reduce ozone depletion. Describe the development, test, production, and operations and support activities, costs, risks, and environmental impacts associated with each alternative. Include cost
Annex F, CDRLs
F04701-95-R-0009 (61)
and schedule impacts on baseline program to minimize downstream retrofit.” BLK 12: Submit an initial draft 90 CD after the tailored System Requirements Review. BLK 13: Submit 30 CD prior to the tailored Preliminary Design Review. Any changes as a result of the tailored Preliminary Design Review shall be reflected in an updated draft submitted 14 CD prior to the EOC. *Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
15. TOTAL
G. PREPARED BY LT Jeff Ward 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_3_of_3_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A019 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: MISC TDP_______ TM_______ OTHER MISC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE SPECIFICATIONS AND STANDARDS ANALYSIS REPORT 6. REQUIRING OFFICE EELV
TECHNICAL REPORT - STUDY/SERVICES 5. CONTRACT REFERENCE
4. AUTHORITY (Data Acquisition Document No.) DI-MISC-80508
Annex F, CDRLs
F04701-95-R-0009 (62)
62
7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS
9. DIST STATEMENT REQUIRED
10. FREQUENCY
12. DATE OF FIRST SUBMISSION BLK 16
14. DISTRIBUTION b. COPIES Draft Final
C
11. AS OF DATE
13. DATE OF SUBSEQUENT SUBMISSION EELV DMO*
2
BLK 4: Para 10.1: Change to read “Contractor format is acceptable. The report shall contain 4 numbered sections, and appendixes as required, titled and numbered as shown below: 1.0 Introduction 2.0 Proposed Commercial, Industry, Corporate, and Government Compliance Documents for Pre-EMD and EMD 3.0 Summary of the Benefits/Risks of Approach 4.0 Detailed Analysis and Documentation Supporting Approach BLK 12: Submit 180 CD after contract award *Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
15. TOTAL
2
G. PREPARED BY Lt Jason Wilson 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_1_Pages
J. DATE
Annex F, CDRLs
F04701-95-R-0009 (63)
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Form Approved OMB No. 0704-0188
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A020 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: MISC TDP_______ TM_______ OTHER MISC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE OPERATIONS TECHNICAL REPORT 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES Draft Final
SCIENTIFIC AND TECHNICAL REPORTS 5. CONTRACT REFERENCE
4. AUTHORITY (Data Acquisition Document No.) DI-MISC-80711 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS C 9. DIST STATEMENT REQUIRED
11. AS OF DATE
13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO* 2
2
BLK 4: Para 10.3: Change to read: “A report of all technical work accomplished and information gained pertaining to EELV operating functions and supporting resource requirements will be prepared. An overall system description, abbreviated launch vehicle descriptions, and integrated test plan summaries will be included and cross-referenced to the appropriate CDRL item. Operations and support functions will be defined in terms of task descriptions, functional flow, and timeliness. Variations in processing times, resource utilization rates, and system responsiveness will be addressed. Supporting resource requirements to be defined and/or addressed by cross-reference to appropriate CDRL items include all Government funded production, test, and operational facilities; ground command, control, communications and mission equipment; development test equipment, production tooling, support equipment and software; and flight support operations and services. The report will also include time phased acquisition networks, schedules, and funding profiles depicting planning, design, long-lead procurement, facility construction, support equipment design and production, support equipment installation, software development and production, training, acceptance tests, ground system test, integrated systems tests, pathfinder operations (if applicable) and site activation. Transition requirements, concepts, schedules, and constraints will be fully described. This includes the plan for transitioning a) any existing payloads (scheduled to use EELV in the National Mission Model) to EELV and b) to standard payload interfaces. Mitigation measures required to minimize impacts to existing space launch vehicle operations during transition periods will be identified. BLK 12: Initial submittal shall be 90 CD after the tailored System Requirements Review. BLK 13: The final draft shall be submitted 30 CD prior to the tailored Preliminary Design
Annex F, CDRLs
F04701-95-R-0009 (64)
64
Review. Any changes as a result of the tailored Preliminary Design Review shall be reflected in an updated draft submitted 14 CD prior to the EOC. * Distribution shall be one file transferred via the EELV Electronic Bulletin Board (EBB) and one paper copy
15. TOTAL
2
2
G. PREPARED BY Michael Ross 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_1_Pages Form Approved OMB No. 0704-0188
J. DATE
CONTRACT DATA REQUIREMENTS LIST (1 Data Item)
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to DoD, Washington Headquarters Services, Directorate for InformationOperations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. 0002 D. SYSTEM/ITEM EELV LOW COST CONCEPT VALIDATION 1. DATA ITEM NO. A021 2. TITLE OF DATA ITEM
B. EXHIBIT A
C. CATEGORY: IPSC TDP_______ TM_______ OTHER IPSC F. CONTRACTOR
E. CONTRACT/PR.NO F04701-95-R-0009
3. SUBTITLE INTEGRATED MASTER SCHEDULE (IMS) 6. REQUIRING OFFICE EELV 10. FREQUENCY 12. DATE OF FIRST SUBMISSION BLK 16 14. DISTRIBUTION b. COPIES Draft Final
MASTER INTEGRATED PROGRAM SCHEDULE (MIPS) 5. CONTRACT REFERENCE
4. AUTHORITY (Data Acquisition Document No.) DI-MISC-81183 7. DD 250 REQ LT 8. APP CODE N/A 16. REMARKS C 9. DIST STATEMENT REQUIRED
11. AS OF DATE
13. DATE OF SUBSEQUENT SUBMISSION BLK 16 EELV DMO*
11
BLK 4: Para 10.2: Delete first sentence and replace with “The IMS shall contain an integrated network based schedule, traceable to the Low Cost Concept Validation (LCCV) module ITAMP and WBS. It shall include program milestones and definitions, logical network based schedules, summary, intermediate, and detailed schedules, and periodic analysis of progress to date.”
Annex F, CDRLs
F04701-95-R-0009 (65)
Para 10.2.6: Delete second sentence and 10.2.6a through 10.2.6o. Para 10.3: Change the first sentence to read: “The LCCV Module IMS shall display all of the proposed events and significant accomplishments from contract award to the end of the LCCV module. The Total EELV Program Roadmap, submitted with the LCCV proposal, shall be resubmitted only if LCCV performance is projected to change future program module activities. Para 10.4: In the first sentence, delete “(e.g., duration, TS, ES, EF, LS, LF, etc.).” BLKS 12 & 13: The LCCV IMS submitted with the proposal shall be the baseline IMS. Submit by 1st of each month. * Distribution shall be 10 paper copies and one 3.5” High Density diskette per submittal
15. TOTAL
11
G. PREPARED BY CAPT Suzanne O‟Reilly 17. PRICE GROUP
H. DATE 17 Mar 95 18. ESTIMATED TOTAL PRICE
I. APPROVED BY Page_1_of_1_Pages
J. DATE
Annex F, CDRLs
F04701-95-R-0009 (66)
66
1