SOURCES SOUGHT
C -- To support growth, dev., improve and implementation of ARDEC Systems Engineering
- Notice Date
- 3/19/2012
- Notice Type
- Sources Sought
- Contracting Office
- US Army, Army Contracting Command, ACC New Jersey Contracting Center, Picatinny Arsenal, New Jersey 07806-5000
- ZIP Code
- 07806-5000
- Solicitation Number
- W15QKN-12-X-F019
- Response Due
- 4/9/2012
- Archive Date
- 5/9/2012
- Point of Contact
- Margaret Reed, Contract Specialist, 973-724-3273
- E-Mail Address
-
Margaret Reed
(margaret.b.reed@us.army.mil)
- Small Business Set-Aside
- N/A
- Description
- The Army Contracting Command-Picatinny (ACC-Picatinny) is conducting marketresearch of companies capable of providing support services to the Systems Engineering Directorate (SED) as follows: Infrastructure Support growth, development, improvement, and implementation of ARDEC Systems Engineering (SE) infrastructure. Includes analyzing infrastructure, documenting the findings, and recommending improvements. Infrastructure will include software tools, training, policies, and procedures pertaining to the enhancement of ARDEC SE and its competency. Software tools will be Commercial Off The Shelf (COTS) used by ARDEC to perform SE activities. Examples will include IBM Rational Tools such as DOORS for Requirements Development/Management, Change for Configuration Management, Rhapsody for architecting, etc. Also includes development, maintenance, or improvement of databases used to store SE activities. Training will include development, maintenance, improvement, and implementation of ARDECs SE training needs. The development of training material will include training modules, class material, or training guides. The maintenance and improvement will include ARDECs current SE training such as Systems Engineering Basics (SEB) and Systems Engineering at ARDEC (SEAA) courses. Policies and Procedures will include diagnosis of metrics for the development, maintenance, and improvement of the ARDEC SE Organization Standard Process (OSP). The ARDEC SE OSP includes Policies, Procedures, Processes, and Templates. Activities will include identifying industry best practices in SE, tailoring those best practices to fit the ARDEC business model and documenting the best practices. This will also include the analysis of metrics to assess the value-added to ARDECs OSP documents. Provide recommendations and support Model based Systems Engineering (MBSE). Includes subject matter expertise in MBSE methodologies, system modeling tools, and provide analyses on the application of modeling to support all process areas under SE (Stakeholder Requirements Definition, Requirements Analysis, Architectural Design, Implementation, Integration, Verification, Validation, Transition, Risk Management, Decision Analysis and Resolution, Requirements Management, Interface Management, Configuration Management, Data Management, and Peer Review). System Analysis Support to include data gathering, Decision Analysis & Resolution (DAR), software coding, operational analysis, and item level performance analysis. Data gathering: includes data to be gathered and all data relevant to performance and effectiveness of weapons and munitions; database searches, analysis and recommendations of previous studies and supporting data; threat data, weapons data, munitions data, and analysis approaches. Decision Analysis and Resolution (DAR): This includes such efforts as concept evaluation studies that trade off alternative approaches to meet requirements, considering all attributes and the importance of each to a customer. Lead / facilitate discussion in groups of subject matter experts, organize data into coherent structured decisions, and document results. Software coding: Includes coding, verification, validation, and accreditation of computer models / simulations that characterize performance and effectiveness of weapons systems and ammunition at the item and force effectiveness levels. It also includes development of logical structures for integration of multiple codes to allow High-Level Architecture (HLA) and other forms of distributed simulations to function in a coordinated fashion over a network. Includes special purpose codes to gather and reduce field test and laboratory experimental data to forms useful for prediction of performance and effectiveness of weapons and munitions. Operational analysis: Develop force effectiveness metrics that provide a customer with information necessary for decision making to improve a particular item or the Army's ability to execute its mission. Examples include development of scenarios, identification of relevant force structures, control of semi-automated forces in a battlefield simulation, logging of results, and data mining. Item level performance analysis: Use existing computer codes to generate data on performance attributes such as the probability of detection, classification, and identification of threats, the probability of hit and kill, delivery accuracy, etc. Requirements/Functional Analysis and Design Synthesis (RFAD)SE services to include Requirements Engineering, Requirements Management, Functional Analysis, and Systems Architecting on a variety of projects, to include Science and Technology (S&T) efforts and Department of Defense (DoD) Acquisition Programs of Record. Requirements Engineering: Requires ability to lead and facilitate discussions in order to elicit needs and wants from stakeholders and prioritize those needs and wants into a set of well-written stakeholder requirements. Work with project lead and teams to formulate a system concept that will meet stakeholder requirements, and translate into a set of clear, concise, verifiable and valid well-written technical requirements. Formulate requirement specifications using MIL-STD-961E as a guide. Establish traceability between various levels of requirements and ensure completeness by tracing to functional models and architectures. Develop interface requirements in accordance with defined system architectures. Requirements Management: Ensure that supported projects have a documented requirements management process that describes how changes to requirements will be made by the team. Use existing automated tools (i.e. Dynamic Object-Oriented Requirements System (DOORS)) to manage changes and traceability for sets of requirements. Maintain traceability between requirements and functional models, design elements, test cases, and other levels of requirements. Produce reports (e.g. traceability reports) and specifications for the customer. Functional Analysis: Involves capture and examination of system functionality, interfaces, and behavior (states and modes) using a variety of techniques, including use cases, activity diagrams, sequence diagrams, and state transition diagrams. This area also includes methodical decomposition of mission tasks to operational capabilities and functional/technical requirements. System Architecting: Organize operational- and system-level information (e.g. operational activities, system functionality) into particular views to convey the right set of information to stakeholders to support decision making. Construct views and models in accordance with standard frameworks (including, but not limited to DoD Architectural Framework (DODAF)). Construct and maintain the architecture model using automated tools (i.e. Magic Draw, Rhapsody). Systems Engineering Lead Management (SELM)Support to project activities described within SE Roadmap. This will include all SE Process areas: Stakeholder Requirements Definition, Requirements Analysis, Architectural Design, Implementation, Integration, Verification, Validation, Transition, Risk Management, Decision Analysis and Resolution, Requirements Management, Interface Management, Configuration Management, Data Management, and Peer Review.Project Planning: tailor template based on scenario, complexity, prepare sections within Project Plan (PP) and Systems Engineering Plan (SEP). The planning will be conducted in accordance with the ARDEC SE OSP, which will include policies, procedures, processes, and templates.Stakeholder Requirements Definition: identify stakeholder requirements; analyze, define and develop technical requirements within task order.Requirements Analysis: define functions and identify logical alternatives, develop logical analysis model(s) and resolve technical requirement issues.Architectural Design: define alternative design solutions, analyze alternatives and recommend preferred solution, generate full design solution description and baseline. Implementation: define what components will be made, reused, or bought; analyze alternative recommend preferred solution.Integration: document lessons learned from assembly and integration of products.Verification: document lessons learned from verification results.Validation: document lessons learned from validation results.Transition: provide product documentation.DAR: identify decision criteria and alternatives; recommend preferred solution and conduct sensitivity analyses.Requirements Management: establish and document requirements management approach; guide implementation; ensure maintenance of requirements management.Risk Management: establish and document risk management approach; identify and analyze risks, document risk mitigation plans; guide implementation of risk mitigation plans. Data Management: develop and document plan for data management; guide implementation of data management plan.Configuration Management: document implementation of configuration management; develop configuration change controls.Interface Management: develop and document interface management approach; guide implementation of interface management approach.Peer Review: provide peer reviews on SE documentation; analyze SE documentation; provide recommended solutions for any identified gaps/issues. Respondents should include company name and contact information (address, phone number, e-mail address); Cage Code and Type of Business (Small Business, Large Business, 8(a) Small Business, Hub-Zone Small Business, Service Disabled Veteran Owned Small Business, Woman Owned). Submissions to this Market Survey should be made within three (3) calendar weeks, NLT 9 April 2012 to: U.S. Army Contracting Command ACC-NJ, Attn.: Margaret B. Reed, Building 45C, Picatinny Arsenal, NJ 07806-5000; email: margaret.b.reed@us.army.mil. All information shall be submitted via email only; NO PHONE calls will be accepted. This notice does not obligate the Government to award a contract or otherwise pay for the information provided in response. Any contractor responding to this notice should ensure that its response is complete and sufficiently detailed to allow the Government to determine the contractors qualifications. Respondents are advised that the Government is under no obligation to acknowledge receipt of the information received or provide feedback to respondents with respect to any information submitted. All information is to be submitted at no cost or obligation to the Government. After a review of the responses received, a solicitation may be issued at a later date. However, responses to this notice will not be considered a response to any possible future solicitation.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/d7829feeeaa9b0d1f4518023a6978e25)
- Record
- SN02700405-W 20120321/120319235932-d7829feeeaa9b0d1f4518023a6978e25 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |