Loren Data's SAM Daily™

FBO DAILY ISSUE OF SEPTEMBER 17, 2003 FBO #0659
SOLICITATION NOTICE

A -- MODELING AND SIMULATIOM SERVICES

Notice Date

9/15/2003
 

Notice Type

Solicitation Notice
 

Contracting Office

US Army Aviation and Missile Command DAAH01, ATTN: AMSAM-AC, Building 5303, Martin Road, Redstone Arsenal, AL 35898-5280
 

ZIP Code

35898-5280
 

Solicitation Number

DAAH0103PR076
 

Response Due

9/24/2003
 

Archive Date

11/23/2003
 

Point of Contact

NATALYNN WEDDLE, (256) 876-1351
 

E-Mail Address

Email your questions to US Army Aviation and Missile Command DAAH01
(NATALYNN.WEDDLE@REDSTONE.ARMY.MIL)
 

Small Business Set-Aside

N/A
 

Description

NA This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are b eing requested and a written solicitation will not be issued. **** See Numbered Note 22: This action is Sole Sourced to Lanner Group, Inc 11000 Richmond Ave Suite 680 Houston, Tx 77042 STATEMENT OF WORK MODELING AND SIMULATION SERVICES 1.0 INTRODUCTION: Faced with the challenge of reduced military budgets, increasing weapon system complexity, and the need to produce affordable weapon systems in a more timely manner, it is clear that the Government must implement the next generation of engineering tools w hich provide insight into the producibility, manufacturability and cost of producing and maintaining weapon systems. The U.S. Army Aviation and Missile Command AMCOM, Research Development and Engineering Center, Production Engineering Division PED has the mission to insure that producibility and manufacturability with consideration of cost issues are addressed. Hence, t he implementation of advanced engineering analysis systems which utilize artificial intelligence techniques to address weapon systems life cycle issues is critical to fulfilling this mission and is the focus of this modeling and simulation effort. 2.0 OBJECTIVE: The objective of this task is to build models of the UH-60 M Utility Helicopter remanufacturing process utilizing WITNESS and/or SIMBA software which makes use of artificial intelligence techniques that are proprietary to the Lanner Group. 3.0 WORKSITE: The Primary locations for performance of this task is at the Lanner Group facilities . Additional work may be performed as needed at the Redstone Arsenal building 5400. Temporary duty at other locations for the purpose of knowledge engineering and data a cquisition will be conducted when necessary to fulfill the SOW requirements. 4.0 REQUIREMENTS: 4.1 The Lanner Group shall complete and develop models, simulations and user interfaces or Front ?????? Ends to make data changes easier for the user to update. The number of models to be built will depend upon the critical path as determined by each suc cessive model that is built. However, for estimating purposes a figure of 156.8 hours per model to include necessary travel and miscellaneous expenses can be used and a total of 5 models completed during the SOW period of performance of 12 months. This ef fort will require functional expertise in data analysis, statistics and production simulation. The contractor shall only accept guidance and direction from the Production Engineering Division of the U.S. Army Aviation and Missile Command in keeping within the confines of this scope of work. 4.2 Software construction shall proceed through the normal phases of requirements definition, design, implementation, testing, and delivery. Special attention shall be given to the modularity, extensibility, and robustness of the system. The contractor s hall also allow for various platforms and means of access. 4.3 Periodic review and assessments will be scheduled at key points in this plan and be a cooperative effort between the Government and the contractor. Contractor frequent interaction with experts and anticipated users will be vital to the credibility and functionality of this project and to ensure that the Army receives anticipated benefit from this work. 5.0 DELIVERABLES: 5.1 The contractor shall prepare and submit a performance and cost report every 60 days IAW DI-FNCL-80912. 5.2 The contractor shall prepare a final technical report summarizing efforts performed under this task IAW DI-ADMN-80447. 5.3 The contractor shall deliver software source codes for th e system modeled and document the use of such software IAW DI-MCCR-80019. 5.4 The contractor shall conduct an end of project review and demonstration of the system to the AMCOM representatives. DATA ITEM DESCRIPTION Performance and Cost Report 1. TITLE: Performance and Cost Report 2. IDENTIFICATION NUMBER: DI-FNCL-80912 3. DESCRIPTION/PURPOSE: 3.1. The Performance and Cost Report provides current status and projected requirements of funds, man-hours, and work completion. 3.2. The report is used for evaluation of contractor progress. 4. APPROVAL DATE: 891006 5. OFFICE OF PRIMARY RESPONSIBILITY OPR: A/MICOM 6a. DTIC APPLICABLE: Not Applicable 6b. GIDEP APPLICABLE: Not Applicable 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 as delineated in the contract. 7.2. This DID supersedes DI-F-1208A. 8. APPROVAL LIMITATION: Not Applicable 9a. APPLICABLE FORMS: Not Applicable 9b. AMSC NUMBER: A4845 10. PREPARATION INSTRUCTIONS: 10.1. Format. The Performance and Cost Report format shall be contractor selected. Unless effective presentation would be degraded, the initially used format arrangement shall be used for all subsequent submissions. 10.2. Content. The Performance and Cost Report shall contain the following: 10.2.1. Man-Hours. Total man-hours expended by technical categories or program tasks, cumulative total man-hours to date, and percentages of total man-hours spent to date. State whether or not remaining hours are sufficient to complete the task. 10.2.2. Funds. Total funds expended, by task, for the month; cumulative total funds spent to date; and percentage of total contract funds spent to date. State whether or not remaining funds are sufficient to complete the task. 10.2.3. Work completion. Percentage of work completed, by tasks during the month, and cumulative percentage of total contract work completed to date. 11. DISTRIBUTION STATEMENT: DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited. DATA ITEM DESCRIPTION Form Approved OMB No. 0704-0188 1. TITLE SOFTWARE USER'S MANUAL 1. IDENTIFICATION NUMBER DI-MCCR-80019A 3. DESCRIPTION, PURPOSE 3.1 The Software User's Manual SUM provides user personnel with instructions sufficient to execute one or more related Computer Software Configuration Items CSCIs.. 3.2 The SUM provides the steps for executing the software, the expected output, and the measures to be taken if error messages appear. continued on page 2 4. APPROVAL DATE YYMMDD 880229 5. OFFICE OF PRIMARY RESPONSIBILITY OPR E C 6a. DTIC APPLICABLE 6b. GIDEP APPLICABLE 7. APPLICATION/INTERRELATIONSHIP 7.1 This Data Item Description DID contains the format and content preparation instructions for data generated under the work tasks described by paragraph 4.6.4 of DOD-STD-2167A. 7.2 The Contract Data Requirements List should specify whether this document is to be prepared and delivered on bound 8-1/2 by 11 inch bond paper or electronic media. If electronic media is selected, the precise format must be specified. continued on page 2 8. APPROVAL LIMITATION 9a. APPLICABLE FORMS 9b. AMSC NUMBER N4336 10. PREPARATION INSTRUCTIONS 10.1 Content and format instructions. Production of this manual using automated techniques is encouraged. Specific content and format instructions for this manual are identified below. a. Response to tailoring instructions. In the event that a paragraph or subparagraph has been tailored out, a statement to that effect shall be added directly following the heading of each such sub paragraph. If a paragraph and all of its subparagraphs are tailored out, only the highest level paragraph heading need be included. b. Use of alternate presentation styles. Charts, tables, matrices, or other presentation styles are acceptable when t he information required by the paragraphs and subparagraphs of this DID can be made more readable. c. Page numbering. Each page prior to Section 1 shall be numbered in lower-case Roman numerals beginning with page ii for the Table of Contents. Each page starting from Section 1 to the beginning of the appendixes shall be consecutively numbered in Arabic numerals. If the document is divided into volumes, each such volume shall restart the page numbering sequence. continued on page 2 11. DISTRIBUTION STATEMENT DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited 3. DESCRIPTION/PURPOSE continued 3.3 The information required by this DID is directd to the functional user of the CSCIs, as opposed to the operator of the computer system. If this distinction does not exist, the user will need to refer to both the Computer Syste Operator's Manual and the SUM to operate the computer system and to use the CSCIs. 7. APPLICATION/INTERRELATIONSHIP continued 7.3 This DID supersedes DI-MCCR-80019 dated 4 June 1985. 10. PREPARATION INSTRUCTIONS continued d. Document control numbers. For hard copy formats, this document may be printed on one or both sides of each page single-sided/double-sided. All printed pages shall contain the document control number and the date of the document centered at the top of th e page. Document control numbers shall include revision and volume identification as applicable. e. Multiple subparagraphs. All paragraphs and subparagraphs starting with the phrase This subparagraph shall... may be written as multiple subparagraphs to enhance readability. These subparagraphs shall be numbered sequentially. f. Document structure. This manual shall consist of the following: 1 Cover 2 Title page 3 Table of contents 4 Scope 5 Referenced documents 6 Execution procedures 7 Error messages 8 Notes 9 Appendixes. 10. PREPARATION INSTRUCTIONS continued 10.1.1 Title page. The title page shall contain the information identified below in the indicated format: Document control number and date: Volume x of y if multi-volume Rev. indicator: date of Rev. SOFTWARE USER'S MANUAL FOR THE SYSTEM NAME CONTRACT NO. contract number CDRL SEQUENCE NO. CDRL number Prepared for: Contracting Agency Name, department code Prepared by: contractor name and address 10.1.2 Table of contents. This document shall contain a table of contents listing the title and page number of each titled paragraph and subparagraph. The table of contents shall then list the title and page number of each figure, table, and appendix, in t hat order. 10.1.3 Scope. This section shall be numbered 1 and shall be divided into the following paragraphs. 10.1.3.1 Identification. This paragraph shall be numbered 1.1 and shall contain the approved identification numbers, version number, release number, titles, and abbreviations, if applicable, of the CSCIsand the system to which this SUM applies. 10.1.3.2 System overview. This paragraph shall be numbered 1.2 and shall briefly state the purpose of the system and the CSCIs to which this SUM applies. 10.1.3.3 Document overview. This paragraph shall be numbered 1.3 and shall summarize the purpose and contents of this manual. 10.1.4 Referenced documents. This section shall be numbered 2 and shall list by document number and title all documents referenced in this manual. This section shall also identify the source for all documents not available through normal Government stockin g activities. 10.1.5 Execution procedures. This section shall be numbered 3 and shall present the information and instructions necessary for user interaction with the CSCIs in order to carry out the operation of the software. This subparagraph shall describe the step-by -step procedures for executing the software and shall identify the options available to the user. Reference may be made to an operator's manual for the computer system operating procedures (e.g., Computer System Operator's M anual CSOM, DI-MCCR-80018. The procedures shall include the following information as applicable: a. Initialization. Describe the initialization procedures necessary to execute the software. Identify any initialization options available to the user. b. User inputs. Describe the user inputs to the software. c. System inputs. Describe the system inputs to the software that may occur while the software is in use and that may affect the software' interface with the user (e.g., inputs from a remote sensor). Include format, frequency, allowable range, and units of measure, as applicable. d. Termination. Describe how to terminate software operation and how the user can determine whether normal termination has occurred. e. Restart. Describe the procedures for restarting the software. f. Outputs. Describe expected utputs of the software, including error messages. 10.1.6 Error messages This section shall be numbered 4 and shall identify all error messages output by the software, the meaning of each error message, and the action to be taken when each message appears. 10.1.7 Notes. This section shall be numbered 5 and shall contain any general information that aids in understanding this document, i.e., background information, glossary. This section shall include an alphabetical listing of all acronyms, abbreviations, an d their meanings as used in this document. 10.1.8 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 wou ld normally have been provided. Appendixes may be bound as separate documents for ease in handling. Appendixes shall be lettered alphabetically A, B, etc., and the paragraphs within each appendix be numbered as multiples of 10 e.g., Appendix A, paragraph 1 0, 10.1, 10.2, 20, 20.1, 20.1, etc. Pages within each appendix shall be numbered alpha-numerically as follows: Appendix A pages shall be numbered A-1, A-2, A-3, etc. Appendix B pages shall be numbered B-1, B-2, B-3, etc.
 

Place of Performance

Address: US Army Aviation and Missile Command DAAH01 ATTN: AMSAM-AC, Building 5303, Martin Road Redstone Arsenal AL

Zip Code: 35898-5280

Country: US
 

Record

SN00434742-W 20030917/030915213332 (fbodaily.com)
 

Source

FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)

---

| FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |