Loren Data Corp.

'

 
 

COMMERCE BUSINESS DAILY ISSUE OF OCTOBER 16,1996 PSA#1701

ASC/CDSK bldg 22N, 2690 C Street, Rm N222, Wright-Patterson AFB, OH 45433-7407

D -- COMPUTERIZED PARAMENTRIC COST ESTIMATING MODELS (CPCEM) SOL F33657-96-R-0017 DUE 102596 POC Contact, Buyer, Barb Fisher/Contracting Officer, Frieda Thorton, (937) 255-6816. (i). This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in FAR Subpart 12.6 and FAR 15, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation, proposals are being requested and a written solicitation will not be issued.(ii). Solicitation number F33657-96-R-0017. (iii). The solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 90-42. (iv). This is an other than full and open procurement under SIC 7379, $18.0M. The Government intends to issue follow-on contracts to Lockheed Martin PRICE Systems and Galorath Associates, SEER Technologies Division. (v). There are four contract line items: CLIN 0001 Commercial Computer Software/Documentation, CLIN 0002 Training, CLIN 0003 Calibration Research, CLIN 0004 Data - Exhibit A. (vi). Description: (1) Objective: The objective is to contract for existing estimating models providing the capability of estimating hardware and software acquisition and operating and support (O&S) costs. The estimating models shall be applicable to a wide range of systems acquired by the United States Government (such as: aircraft, missiles, avionics, electronics, radar, software, simulators, and support equipment, etc.). The models must be able to perform cost calculations and have the ability to be adjusted to specific organizations and technologies. The government does not intend to contract for estimating services under this contract, but intends to contract for models, possessed by the prime sources, that may be directly accessed on government computers. (2) Background: The Cost Division, Aeronautical Systems Center (ASC), Wright-Patterson AFB, OH, is required to provide access to Computerized Parametric Cost Estimating Models. To fulfill this requirement, the initial capability was leased by the Air Force in 1973. The models have been used to estimate computer hardware and software costs on many major weapon systems, sub-systems, support equipment, and training devices. The models are used at various government locations including extensive use at ASC. (3) General Requirements: This effort involves the acquisition of license agreements for software for use on government computers (Intel 80386 based personal computers as a minimum running MS-DOS version 3.2 or higher and/or MS-DOS/Windows 3.0 capable of performing parametric cost and schedule estimates on weapon systems and subsystems hardware and software in various phases of their life cycle (acquisition and support). The Operating and Support cost model must be able to produce model results/cost output in the standard Office of the Secretary of Defense (OSD) Cost Analysis Improvement Group (CAIG) approved Cost Element Structure as found in The Operating and Support Cost-Estimating Guide, OSD CAIG, May 1992. The model must be able to perform sensitivity studies and incorporate peculiar development characteristics, varying degrees of complexity, time constraints, and inflation. The contractor shall also perform calibration research for adjusting model inputs to actual costs and technical parameters. A calibration effort will encompass assessing feasibility of the research, determination of the adjustments, and reporting the results. (4) Specific Criteria: (A) The methodology of the models shall be capable of performing development, production, and operating and support (O&S) cost estimates and cost sensitivity studies. They must be able to estimate the impacts on cost of changes in system specifications, quantities, schedules, and other supportability parameters. (B) The hardware model(s) must have the following capabilities: (i) Be able to provide independent estimates of development, production, and O&S costs and schedules of entire systems as well as Line Replaceable Units (LRUs), Shop Replaceable Units (SRUs) (lower level equipment modules would be desirable). This independent estimation must be able to segregate, identify, and account for the costs associated with Contractor Make Items, Contractor Buy Items, and Government Furnished Equipment (GFE). The model must be able to separately provide the cost for integration and testing to assemble SRUs into LRUs, and LRUs into a complete system. (ii) The ability to generate the cost required for hardware/software integration, allow for segregation of the hardware costs contained in hardware/software integration, or allow user calibration to account for this cost element. (iii) As a minimum, segregate inputs by variables such as: (1) weight by electronics and structure, (2) quantities by development and production, (3) specification levels (airborne, ground, space, etc.), and (4) degree of technology. (iv) To segregate cost by fiscal year, phase (development and production) and functional categories (to include engineering, Systems Engineering/Program Management (SE/PM), production tooling and test equipment, and data) and to account for these categories into the Work Breakdown Structure. Use MIL-STD-881B as a guide. (v) Be able to derive and display production lot cost by fiscal year, the first unit cost, average unit production cost, and the unit cost improvement curve associated with the estimate developed. (vi) To provide capability for calibrating to known cost, technical, and program information. In addition, the capability to customize an estimate from an activity and functional standpoint is desirable. (vii) To be able to identify and estimate the key input variables required for O&S cost estimates. (viii) To be capable of accounting for the cost associated with the number of equipment levels, up to three levels of maintenance and/or supply locations, and up to three theaters of deployment and force structuring, The model must also be capable of performing cost trade-offs based on various maintenance concepts, basing concepts, operational scenarios, readiness rates, and availability rates as a minimum. (ix) To be able to account for the costs associated with the standard OSD CAIG approved Cost Element Structure explained in greater detail in The Operating and Support Cost-Estimating Guide, OSD CAIG, May 1992. For example, the length of the support period, equipment operating time, storage costs, entering and maintaining items in the supply system, programming and documentation costs for test/support equipment, and dedicated versus non-candidate maintenance crews. (x) To segregate operational and support costs by fiscal year and by the standard OSD CAIG approved Cost Element Structure found in the Operating and Support Cost-Estimating Guide, OSD CAIG, (May 1992). (C) The software model(s) must have the following capabilities: (i) Be able to provide independent estimates of development costs and schedules of entire systems as well as individual Computer Software Configuration Items (CSCIs) and the cost for integrating and testing the CSCIs into a complete system. This independent estimation must be able to segregate, identify, and account for the costs associated with contractor developed software, purchased software, and government furnished software. (ii) To segregate inputs by areas such as: (1) specification levels (airborne, ground, space, etc.), (2) software character (such as: data storage, and retrieval, on-line communication, mathematical manipulations, real time command and control, and operating systems), (3) new design and new code, (4) lines of code, (5) hardware constraints (time and memory), (6) environmental and personnel complexities, and (7) software development tools. (iii) To segregate cost by phase such as: system concept, system software requirements, software requirements analysis, preliminary design, detailed design, code, unit test and CSC testing, CSCI test, system integration and test, and operational test and evaluation. In addition, the model must segregate costs by functional category (design, programming, SE/PM, quality assurance, configuration management, and data) and be able to account for Work Breakdown Structure items. Use MIL-STD-881B as a guide. (iv) To provide for adjusting software development performance (productivity) to known cost, technical, and program information. In addition, the ability to customize an estimate from a phase and function standpoint is desirable. (v) To be able to generate the size of the software based on the functionality of the software. (vi) Provide the capability of describing and estimating the operations and support cost for contractor developed software and for discrete software additions to an existing software system. (vii) Segregate the software O&S inputs by (1) specifications levels (airborne, ground, space, etc.), (2) length of support period, (3) number of software installations, (4) software quality, and (5) amount of growth. (viii) Segregate the software O&S costs by phase (maintenance, enhancement, and growth), function (such as: SE/PM, programming, data, configuration management, and quality assurance), and the standard OSD CAIG approved Cost Element Structure explained in greater detail in The Operating and Support Cost-Estimating Guide, OSD CAIG, (May 1992). (D) Calibration research shall require the following activities: (i) The contractor shall determine the availability of cost and technical data for unique model adjustments and provide a written recommendation for comprehensive research with the related management plan for the effort (DI-MGMT-80004). This is defined as Phase I of a calibration effort. (ii) If continuation is approved by the using organization, the contractor shall perform the research on sufficiently adequate data, prepare the related inputs, operate the model, and document the inputs, methodology, outputs, and summary tables in a technical report (DI-MISC-80711). This is defined as Phase II of a calibration effort. (iii) FOR IBM COMPATIBLE PERSONAL COMPUTERS - The family of models should not exceed 30 megabytes of hard disk space and eight megabytes of random access memory (RAM). (5) Reports and data: A complete user reference manual must be provided to each person receiving formal training. Maintenance of reference manual (updates, errata, etc.) must also be provided and distributed to these same people each time a revision is necessary. Additionally, the contractor will provide new disks (4 sets) whenever the model is updated. (6) Special Instructions: (i) The contractor shall provided a system description that defines model methodology and the data base/historical data that was used to derive reference tables/factors separately if not included in the appropriate model reference manual. (ii) Release of new versions of the models to account for improvements or enhancements of the models' capabilities must be coordinated so that documentation and orientation of Government personnel is accomplished in a timely fashion. Orientation of Government personnel on new releases of the models shall be held at the contractor's facility. (iii) The contractor's training and orientation of Government personnel must be provided with a minimum of 25 percent hands-on training. On-site training will be scheduled by the Government as required. Any retraining of government personnel will be done at no cost to the Government at the contractor's facility. (iv) A technical support and continuous technical assistance must be available via telephone on normal workdays between 0800 Eastern Time and 1700 Pacific Time. On-site assistance must be available when telephone consultation does not resolve the issue and must be provided within 24 hours of notification. (vii). Date and places of delivery and acceptance shall be specified on individual delivery orders. FOB: destination. (viii). Solicitation provision at FAR 52.212-1, Instructions to Offerors - Commercial, is hereby incorporated by reference. (ix). Include a completed copy of the provision at FAR 52.212-3, Offeror Representations and Certifications - Commercial items, with the offer. (x). FAR clause at 52.212-4, Contract Terms and Conditions - Commercial Items, is hereby incorporated by reference. (xi). FAR clause at 52.212-5, Contract Terms and Conditions Required To Implement Statutes Or Executive Orders - Commercial Items, is hereby incorporated by reference. The following paragraphs apply to this solicitation and any resultant contract: (b)(1) 52.203-6, b(3) 52.219-8, b(4) 52.219-9, b(5) 52.219-14, b(6) 52.222-26, b(7) 52.222-35, b(8) 52.222-36, b(9) 52.222-37. (xii). DFAR Clause at 252.212-7001, Contract Terms and Conditions Required to Implement Statures or Executive Orders Applicable to Defense Acquisitions of Commercial Items (Nov 1995), is hereby incorporated by reference. The following paragraphs apply to this solicitation and any resultant contract: (b) 252.205-7000, 252.219-7003, 252.227-7015. (xiii). Additional Contract Terms and Conditions applicable to this procurement are: (i) Type of contract: It is contemplated that a requirements contract will be awarded. (ii) Period of Performance shall be for four years from date of contract award. (iii) FAR clauses 52.216-18, Ordering, 52-216-19, Order Limitations, and 52-216-21, Requirements. (xiv). The DPAS assigned rating for this procurement is DO-C9. (xv). See Note 22. (xvi). Signed and dated offers (one original and two copies) must be submitted to ASC/CDSK, Bldg 22N, 2690 C Street, Rm N-222, Wright-Patterson AFB, OH 45433-7407, ATTN: Frieda Thornton at or before 3:00 P.M. EDST NLT 15 days from the date this notice is published in the CBD. (xvii). An Ombudsman has been appointed to hear concerns from offerors or potential offerors during the proposal development phase of this acquisition. The purpose of the Ombudsman is not to diminish the authority of the program director or contracting officer, but to comminicate contractor concerns, issues, disagreements, and recommendations to the appropriate government personnel. When requested, the Ombudsman will maintain strict confidentiality as to the source of concern. The Ombudsman does not participate in the evaluation of proposals or in the source selection process. Interested parties are invited to contact ASC'S Ombudsman, Mr. Daniel L. Kugel, at ATTN: Mr. Daniel L. Kugel, ASC/SY Bldg 52, 2475 K Street, Ste 1, Wright Patterson, AFB OH 45433-7642, E-Mail: kugeldl@sy.wpafb.af.mil, Phone: DSN 785-3855, Commercial: (937) 255-3855. The Ombudsman should only be contacted with issues or problems that have previously brought to the attention of the contracting officer and could not be satifactorily resolved at that level. Direct all routine communication concerning this acquisition to Ms Barb Fisher, ASC/CDSK, Bldg 22N, 2690 C St, Rm N-222, Wright-Patterson AFB, OH 45433-7407, at (937) 255-6816. (0288)

Loren Data Corp. http://www.ld.com (SYN# 0020 19961015\D-0001.SOL)


D - Automatic Data Processing and Telecommunication Services Index Page