MODIFICATION
69 -- Live Virtual Constructive for Training (LVCT) Software Tools Sources Sought Corrected NAICS to 541511 Custom Computer Programing Services
- Notice Date
- 7/29/2019
- Notice Type
- Modification
- NAICS
- 541511
— Custom Computer Programming Services
- Contracting Office
- N61340 Naval Air Warfare Center Training Systems Division 12211 Science Drive Orlando, FL
- ZIP Code
- 32826
- Solicitation Number
- N6134019R0161
- Response Due
- 8/27/2019
- Archive Date
- 9/11/2019
- Point of Contact
- Fernando A. Cerpa 407-380-8475
- Small Business Set-Aside
- N/A
- Description
- 1. INTRODUCTION 1.1 BACKGROUND The Naval Air Warfare Center Training Systems Division (NAWCTSD) is seeking information from industry regarding capabilities and abilities to provide Live Virtual Constructive Training (LVCT) support. The overarching objective of LVCT is the integration of various training systems and live ranges within an integrated training environment. The complexities involve the coordination of efforts and plans between many centers, sites, platforms, and organizations. Establishing a robust System-of-Systems (SoS) LVCT capability is a massive undertaking that involves the collaboration of multiple stakeholder organizations. 1.2 PLACE OF PERFORMANCE This effort involves deliveries to the following locations: NAWCTSD/Naval Support Activity (NSA) Orlando, FL Naval Air Station (NAS) Jacksonville, FL Marine Corps Air Station (MCAS) Beaufort, SC NAS Whidbey, WA, NAS Lemoore, CA MCAS Miramar, CA Naval Surface Warfare Center (NSWC) Corona, CA NAS Oceana, VA 1.3 SCOPE The government is seeking a contractor to design, develop, test, deploy, and sustain two software tools: 1) Scheduling Tool and 2) Stakeholder Collaboration and Communication Tool. The scheduling tool shall be a secure, online tool that manages, reserves, and de-conflicts the resources necessary to execute Distributed Mission Training (DMT). The scheduling tool will be supported by a dynamic database of capabilities, limitations, and configuration management data related to pre-defined assets and missions. The Stakeholder Collaboration and Communication Tool shall be a restricted access website that serves as a collaboration and communication tool and repository for DMT stakeholders. The contractor shall provide sustainment and deficiency correction support for the Navy Surface, Live, and Joint Integration Support tool. The tool shall evaluate the distributed training proficiency within exercises involving systems from Navy Surface, Live, and/or Joint communities. The anticipated award date is 4QFY21 with deliveries commencing in 4QFY22 and completion in 4QFY26. 2. APPLICABLE DOCUMENTS American National Standards Institute (ANSI)/Electronic Industries Alliance (EIA) ANSI/EIA-649-C 2019 - Configuration Management Standard (Copies of the above document are available from www.ansi.org, http://global.ihs.com/, or Global Engineering Documents, 15 Inverness Way, East Englewood, CO 80112.) International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE) IEEE 29418-2018 - ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering IEEE 29119-2013 - ISO/IEC/IEEE International Standard - Software and systems engineering Software testing IEEE 12207-2017 - ISO/IEC/IEEE Systems and Software Engineering Software Life Cycle Processes (Copies of this document are available from www.ieee.org or IEEE Service Center, 445 Hoes Lane, Piscataway, NJ 08854-1331.) SAE International/Electronic Industries Alliance (EIA) SAE/EIA-649-1 2014 - Configuration Management Requirements for Defense Contracts (Copies of the above document are available from www.ansi.org) 3. REQUIREMENTS The Government requires the design, development, integration, and test expertise to produce and sustain the aforementioned software products and meet the Government Ready for Training (RFT) date of FY23. 3.1 PROGRAM MANAGEMENT The contractor shall organize, coordinate, and control the program activities to ensure compliance with the contract requirements and the timely delivery of the required product and services. The contractor shall provide the program management, systems engineering, materials, services, equipment, facilities, testing, technical, logistics, manufacturing, and clerical support for the efforts described in this Sources Sought. The contractor shall measure, record, monitor, and evaluate the progress of the work performed and costs incurred under the contract. 3.1.1 Risk Management The contractor shall conduct risk management to systematically control the uncertainty in the project s ability to meet cost, schedule, and performance requirements. The contractor shall provide the Government visibility into the contractor s tools, assessment, mitigation, and control techniques. The contractor shall define, document, manage, and apply a risk management process IAW IEEE 12207-2017. The contractor shall participate in the Government Risk Working Group established for this program. 3.1.2 Control of GFE The contractor shall perform the following tasks to control GFE as part of the quality management process: a. Examine upon receipt, consistent with practicality, to detect damage b. Provide storage that precludes deterioration c. Examine prior to installation, consistent with practicality, to detect damage d. Identify and protect from improper use or disposition e. Verify and audit quantity periodically 3.2 CONFIGURATION MANAGEMENT (CM) The contractor shall define, document, manage, and apply a CM process IAW IEEE 12207-2017; and SAE/EIA-649-1 2014. The contractor shall place Government-Furnished Software (GFS), Non-Developmental Items (NDI), and Commercial Item software, and each item s associated documentation under CM upon receipt. The contractor shall place Commercial Item software items under CM as disk image files of the physical media. The contractor shall define, document, manage, and apply a process to accomplish change management. The contractor shall use Engineering Change Proposals (ECPs) and Requests for Variance (RFVs) to request changes to an approved baseline. 3.3 SYSTEMS ENGINEERING The contractor shall use the system engineering processes to define the requirements for the system, to transform the requirements into an effective product, and to verify and validate the functionality of the delivered product. The contractor shall define, document, manage, and apply a requirements definition process IAW IEEE 12207-2017. The contractor shall define, document, manage, and apply a process and mechanism to accomplish traceability between the requirements, allocated design baseline, implementation configuration items, and test procedures. The contractor shall utilize an electronic tool (e.g. Doors, RequisitePro, Access Database, and Excel Spreadsheet) to accomplish the requirement traceability function. Traceability shall be bi-directional. The contractor shall define, document, manage, and apply a system integration process IAW IEEE 12207-2017. 3.4 SOFTWARE ENGINEERING The contractor shall define, document, manage, and apply software requirements analysis IAW IEEE 12207-2017. The contractor shall analyze and define software requirements IAW the criteria within IEEE 29148-2011. The contractor shall place links to the software requirements in the RTVM to accomplish bi-directional traceability. The contractor shall define, document, control, maintain, and implement a software architectural design IAW IEEE 12207-2017. The contractor shall define, document, control, maintain, and implement software detailed design IAW IEEE 12207-2017. The contractor shall place links to the software detailed design in the RTVM to accomplish traceability. The contractor shall define, document, control, maintain, and perform software implementation IAW IEEE 12207-2017. The contractor shall define, document, control, maintain, and implement software construction IAW IEEE 12207-2017. The contractor shall accomplish software unit testing IAW IEEE 29119-2013. The contractor shall define, document, control, maintain, validate, and prepare the software. The contractor shall deliver the software, and databases required to meet the performance defined in this Sources Sought. The contractor shall deliver the non-Commercial Item software with corresponding source code, build tools, executable code, configuration information, and build procedures. The contractor shall deliver the Commercial Item software with the associated vendor manuals, documentation, physical media, warranty information, licenses, and installation new procedures. The contractor shall transfer to the Government at device acceptance, the Commercial Item software licenses. 3.5 USER SUPPORT The contractor shall provide instructor-led training at each site prior to deployment. The training shall teach operational procedures and troubleshooting techniques for the software. The contractor shall deliver web-based version of training. 3.6 SYSTEM TEST AND EVALUATION The contractor shall plan, coordinate, establish, and implement a Test and Evaluation (T and E) program to verify that the software meets the technical and operational requirements as stated in this Sources Sought. The testing events shall be designated as Developmental Test (DT) and Integrated Test (IT) events. The contractor shall provide representation in the T and E working IPT (WIPT) and shall attend and participate in the T and E WIPT meetings. T and E WIPT will be the forum for discussion, coordination, and resolution of test planning goals, strategy, and issues. The contractor, working with the T and E WIPT, shall develop and document the structure and objectives of the T and E program. The contractor shall continuously reassess and refine the T and E program as software development, production, and testing progresses. 3.7 CONFERENCES AND REVIEWS The contractor shall conduct, attend, and participate in conferences and reviews to be held at both the contractor and Government facilities. The specific locations, dates, and duration of the conferences shall be as specified in the contract. Conferences and reviews will be chaired by a Government representative. The contractor shall be prepared to explain the reasoning, assumption, and methodologies in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of the tasks required by the contract. The contractor shall prepare drawings and other data to aid in the presentations. The contractor shall have key personnel and support available to carry out the conference. The contractor shall make available facilities for Government only meetings during the conferences and reviews. Subcontractors shall attend conferences and reviews when required to address key elements. 3.8 CONTRACT DATA REQUIREMENTS LISTS (CDRLS) The following table contains the tentative list of the CDRLs expected as part of this effort: Integrated Master Schedule Test Plan Test Procedure Test/Inspection Report Contractor s Progress, Status, and Management Report (CPSMR) Requirements Traceability/Verification Matrix (RTVM) Interface Control Document (ICD) Software User s Manual Software Product Package (SPP) Conference Agenda Conference Minutes Presentation Material Engineering Change Proposal (ECP) Instructional Media Package 3.9 SPECIAL REQUIREMENTS The proposed work requires a Secret Security clearance. Some work may require a Top Secret Security clearance. Security clearance shall be obtained prior to reporting on-site for work. The Contractor shall provide personnel who hold a security clearance that meets the security requirements of the program. The contractor is expected to: a. Provide Operations Security (OPSEC) protection for classified information and sensitive information. b. Adhere to security policy, procedures, and requirements for classified information. c. Safeguard classified information and meet the security requirements identified in the DD Form 254 and enforce these safeguards throughout the life of the contract d. Not process Department of Defense (DoD) information on public computers (e.g., those available for use by the general public in kiosks or hotel business centers) or computers that do not have access control. e. Protect information by no less than one physical or electronic barrier (e.g., locked container or room, login and password) when not under direct individual control. f. Sanitize media (e.g., overwrite) before external release or disposal. g. Encrypt the information that has been identified as Controlled Unclassified Information (CUI) when it is stored on mobile computing devices such as laptops and personal digital assistants, or removable storage media such as thumb drives and compact disks, using the best available encryption technology. h. Limit information transfer to Subcontractors or teaming partners with a need to know and a commitment to at least the same level of protection. i. Transmit e-mail, text messages, and similar communications using technology and processes that provide the best level of privacy available, given facilities, conditions, and environment. Examples of recommended technologies or processes include closed networks, virtual private networks, public key-enabled encryption, and Transport Layer Security (TLS). j. Encrypt organizational wireless connections and use encrypted wireless connection, where available, when traveling. When encrypted wireless is not available, encrypt application files (e.g., spreadsheet and word processing files), using no less than application-provided password protection level encryption. k. Transmit voice and fax transmissions only when there is a reasonable assurance that access is limited to authorized recipients. l. Not post DoD information to Web site pages that are publicly available or have access limited only by domain or Internet protocol restriction. Such information may be posted to Web site pages that control access by user identification or password, user certificates, or other technical means and provide protection via use of TLS or other equivalent technologies. Access control may be provided by the intranet (vice the Web site itself or the application it hosts). m. Provide protection against computer network intrusions and data exfiltration, including no less than the following: (1) Current and regularly updated malware protection services, e.g., anti-virus, anti-spyware. (2) Monitoring and control of inbound and outbound network traffic as appropriate (e.g., at the external boundary, sub-networks, individual hosts) including blocking unauthorized ingress, egress, and exfiltration through technologies such as firewalls and router policies, intrusion prevention or detection services, and host-based security services. (3) Prompt application of security-relevant software patches, service packs, and hot fixes. n. Comply with other current Federal and DoD information protection and reporting requirements for specified categories of information (e.g., critical program information, Personally Identifiable Information (PII), export controlled information) IAW the requirements of the contract. 3.10 ELIGIBILITY NAICS: 541511 Custom Computer Programing Services PSC: 6910 Training Aids 3.11 SUBMISSION DETAILS Responses to this notice should include key corporate information as well as a brief synopsis of the Contractors experience in providing services specifically as it relates to the capabilities described in this Sources Sought. Your response should provide the following information: a. Your office location b. CAGE Code c. Whether your firm currently has a DCAA approved accounting system d. Point of Contact name, phone number, and email e. Description of your firm s past experience and capability to accomplish the tasks and work defined in this Sources Sought. f. Rough order of magnitude for work defined in this Sources Sought. g. The contract numbers and task order numbers of past contracts that represent your firm s experience with the types of work described this Sources Sought. h. Your firm s past experience and capability to work with classified material up through and including Secret. If you do not have experience on requirements through the Secret classification, your response should clearly state that, and describe what security level your company has experience with. Responses should be provided in a Word document, not to exceed 5 pages, to the Contract Specialist for this solicitation, fernando.cerpa@navy.mil, by 5:00 P.M. on 08/27/2019. Use 12 point Times New Roman font. NAWCTSD is using this notice for the purpose of determining market interest, availability, and adequacy of potential business sources prior to establishing the method of services acquisition and issuance of a request for proposals. NOTE: THIS NOTICE WAS NOT POSTED TO FEDBIZOPPS ON THE DATE INDICATED IN THE NOTICE ITSELF (29-JUL-2019); HOWEVER, IT DID APPEAR IN THE FEDBIZOPPS FTP FEED ON THIS DATE. PLEASE CONTACT 877-472-3779 or fbo.support@gsa.gov REGARDING THIS ISSUE.
- Web Link
-
Link To Document
(https://www.fbo.gov/spg/DON/NAVAIR/N61339/N6134019R0161/listing.html)
- Record
- SN05385203-F 20190731/190729230117 (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 |