SOLICITATION NOTICE
70 -- Enterprise Information System Solution
- Notice Date
- 9/13/2007
- Notice Type
- Solicitation Notice
- NAICS
- 541512
— Computer Systems Design Services
- Contracting Office
- ACA, NRCC, Mission, Building 2796, Fort Eustis, VA 23604
- ZIP Code
- 23604
- Solicitation Number
- W912SU07T0046
- Response Due
- 9/21/2007
- Archive Date
- 11/20/2007
- Small Business Set-Aside
- 8a Competitive
- Description
- 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 being requested and a written solicitation will not be issued. The Northern Region Contracting Center (NRCC) intends to procure an Enterprise Information Solution, which includes hardware, software and services for the development of tests for Web Del ivery and Paper & Pencil Delivery of Defense Language Proficiency Test (DLPT). The RFQ document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 2005-19. This requirement is for a firm fixed price with a bas e period plus three option provisions. All response to this notice shall be submitted one hard copy original to Northern Region Contracting Center, ATTN: Patricia D. Paige, 2798 Harrison Loop, Fort Eustis, VA 23604, an electronic copy shall be submitted t o: patricia.d.paige@conus.army.mil. Due date for receipt of quotes is 2:00 P.M.EST on 21 Sep 2007. CLIN 1001 Professional Services (custom software development and integration services);CLIN 1002 Hardware; CLIN 1003 Software and licenses; CLIN 1004 Traini ng; CLIN 1005 Technical Support; CLIN 1006 Contract Manpower Report; CLIN 1007 Technical Data (Not-Separately-Priced); Option CLINs 2001 Technical Support; 2002 Contractor Manpower Report, Options CLINs 3001 Technical Support; 3002 Contractor Manpower Repo rt, and Options CLINs 4001 Technical Support and 4002 Contractor Manpower Report. The purpose of this contract is to provide an Enterprise-level Defense Language Proficiency Test (DLPT) and Content Management System. SCOPE: The DLPTs are delivered to DLIFL C students, Armed Forces personnel, and personnel in Department of Defense (DOD) client agencies. The client agencies are also referred to as client organizations and client testing organizations. The environments and numbers of examinees for each language being tested vary greatly. The DLPT Information Management System shall support in general: Development of tests for Web delivery and Paper & Pencil delivery. Shall not develop test or test content. All content that will be used in/on this system will be generated by Government users. The contractor will not be responsible for importing already generated test content. Registration & scheduling of examinees. Scoring, management and receipt of test results. Statistical analysis of test results. Capabilities to output WDLPT in the correct format for distribution by outside agencies under 5. 5.1 and 5.5.2. The contractor shall provide the hardware platform (server(s) and storage system) for which the system shall operate. 4. APPLICABLE DOCUMENTS/REFERENCE: US Army Regulation 25-1 and 25-2, DoD Standard 5015.2, and Defense Language Transformation Roadmap. 5. PERFORMANCE REQUIREMENTS: Shall attend an initial meeting with the government technical point of contact, other Government representatives, and Contractin g Officers Representative (COR) within five days of contract award. Shall submit in writing to the COR, a detailed timeline of task management and execution including schedule dates for completion of each tasking. (CDRL A001) In-progress review (IPR) mee tings may be held during the period of performance. The Government will approve the IPR frequency. The IPR meeting/s shall be no longer than total of three hours and shall be held between the contractor employee/s, Project Manager, Government technical PO C, and the Contracting Officer's Representative. Technical discussion between the contractor employee/s and the Government technical point of contact (POC) may occur informally.(CDRL A002) IPRs shall be scheduled to ensure that the Government is able to re view progress and task completion monthly. These IPRs will include, but not be limited to demonstrations by the contractor of task completion, review of progres s, and clarifications of requirements. Specific Tasks. 5.2.1. Shall provide a develop a Enterprise Information system Solution, which includes hardware, software and services for the development of tests for Web Delivery and Paper & Pencil Delivery of D LPTs. Shall deliver the following documentation in accordance with the (IAW) Contract Data Requirement List: 5.2.2. Shall develop a Systems Requirements Analysis for each task that shall be traceable, understandable, achievable, and measurable to mission requirement based on the functional requirements of this PWS. Shall request review/approval of the Systems Requirements Analysis from the Government before proceeding with development. 5.2.3. Upon Government approval of the Systems Requirements Analysis, s hall proceed with a detailed design of the work to be performed. Government review/approval shall be obtained before proceeding with any further task development. 5.2.4. Shall proceed with coding,implementation, and testing. 5.2.5. Shall verify and valida te the complete development, and/or troubleshooting task to ensure that the procedure/sequence/operation is correct and meets the initial software requirements analysis and the mission requirement. 5.2.6. Shall demonstrate the Proof of Concept. This demon stration shall commence on 30 may 2008. 5.2.7. Software Documentation and Training Manuals. All software coding work completed shall be documented using a standard defined process. The documentation shall include traceability of the software requirements specifications to include modification, an interactive electronic users guide, a printable users guide, training manuals, and/or tutorials, and test plans. 5.2.7.1. A complete copy of the proposed source code is required to be available in escrow upon r equest, at no additional charge to the Government. 5.2.7.2. The Government will acquire unlimited user rights to the Software Development. 5.2.8. Shall provide both electronic copy and hard copy documentation (users manual) to the DLIFLC at no extra char ge. the documentation shall include: 5.2.8.1. System overview. 5.2.8.2. Data-entry procedures explanation. 5.2.8.3. Step-by-step operating procedures. 5.2.8.4. Problem-resolution materials. 5.2.8.5. Error-message descriptions. 5.3. System Design - Hardwar e. Currently in place are multiple IBM system x3850 and a Network Appliance FAS 3070 hosted Storage Area Network. Shall provide the same or equal hardware to meet the requirements of this PWS. 5.3.1. The IBM system or equivalent shall have the following m inimum specifications: 5.3.1.1. 2x Intel Xeon Processor 714ON (3.3GHz 16MB L3 Dual Core) 5.3.1.2. 8x 2GB PC2-3200 CL3 ECC DDR2 SDRAM RDIMM. 5.3.1.3. 6x 146GB 10K 2.5 Hot-Swap SAS HDD. 5.3.1.4. 1x ServeRAID ? 8i SAS Raid Controller. 5.3.1.5. 3x 4-DIMM DDR2 Memory Card. 5.3.1.6. 2x NetXtreme? 1000S + Fiber Ethernet Adapter-PCI-X. 5.3.2. The Network Appliance FAS 3070 or equivalent shall be able to store 15 Terabytes (TB) of data with the ability to be expanded to 50 TB. 5.4. System Design Software. Enterpri se-level Defense Language Proficiency Test (DLPT) and Content Management System will have two distinct areas of operation. The first is the backend solution, records management and document tracking capabilities and shall be referred to throughout this PWS as the Content Management System (CMS). The CMS is a major subsystem of the second area which is the WDLPT Lifecycle Management providing 60-100 users with a unified environment for development and export of DLPT tests and shall be referred to throughout this PWS as the WDLPT Lifecycle Management. Shall translate software functional requirements into technical requirements as described below: 5.4.1. The CMS shall have the following attributes: 5.4.1.1. Backup features data recovery and archiving. 5.4.1.2. Restrict system access/functionality based on the user's role. 5.4.1.3. Secure remote access for personnel temporarily assigned off-post and for external revie wers. 5.4.1.4. Non-Repudiation through existing DoD PKI Common Access Card infrastructure. 5.4.1.5. Provide an audit trail of by who and when documents and files are introduced into and/or removed from the system and when documents are modified. 5.4.1.6. Managing documents and files created by industry standard office automation products (i.e. MS Office? and Adobe?) to include video, audio, e-mail, comma/tag delimited and XML. 5.4.1.7. Search functionality to include the ability to 'tag' or insert comment s relating to documents and files. The search engine shall have the capability to compare language specific differences in text. In doing so, expanding characters shall be expanded prior to comparison, so matches are found with equivalent multi-character versions. This will allow a single character to be mapped to a sequence of characters, for example the German ? is equivalent to ss. In addition, it shall have the function to support Left-To-Right (LTR) and Right-To-Left (RTL) Text. 5.4.1.8. The software shall be designed to have the function to define and collect statistical data such as but not limited to: 5.4.1.8.1. Custom Statistical Data Sets user-defined data sets. 5.4.1.8.2. Historical Data. 5.4.1.8.3. Import of Statistical Data. 5.4.1.8.4. Produ ction Reporting. 5.4.1.8.5. Document and file versioning. 5.4.2. WDLPT Lifecycle Management. The WDLPT Lifecycle Management shall have the following attributes: 5.4.2.1. Ability to create Items and Questions. Individual items within a set may be selected or de-selected during the development phases prior to test delivery, but once determined the set must be treated as sections or testlets. Information about the items and questions shall include: 5.4.2.1.1. Word counts for the reading passages. 5.4.2.1.2. T iming information (time to play) for listening passages. 5.4.2.1.3. Test authors must be able to configure the delivery of listening sets including: 5.4.2.1.3.1. Number of times to play a passage. 5.4.2.1.3.2. Scripted pauses between and after voicings or delivery of the passages 5.4.2.1.4. Auto-generate data to link passage to items and provide the ability to track this data and enforce this grouping when manually creating sections and testlets. 5.4.2.1.5. Must provide the capability to categorize and cla ssify items and questions based on their relevance and difficulty. 5.4.2.1.6. Authoring capabilities shall exist with the following response types to items and questions: 5.4.2.1.6.1. Single-answer multiple-choice items. 5.4.2.1.6..2. Constructed-Response Test (CRT) items allowing for a text response. The length of the response shall be configurable to allow test developers to limit the length of answer input from examinees. The CRT items require the ability to capture scoring protocols or evaluation rubri cs as a part of the item. The scoring protocols are multiple English text fields describing responses that would be considered correct. The custom item types for example shall be able to extend the test driver with custom item types (such as using test dri ver plug-ins). 5.4.2.2. Ability to create sections and testlets. The system shall categorize and classify sections and testlets based on their relevance and difficulty. The system shall have nest sections. 5.4.2.3. Ability to create forms and panels. The f orms and panels shall be able to be predefined and/or self-adapt to the examinees apparent ability level by scoring the testlets and routing the examinee to easier or harder testlets, as needed. 5.4.2.4. Ability to format and create layouts. The format a nd layouts shall be based on templates and What You See Is What You Get (WYSIWYG) display. 5.4.2.5. Ability to create Item Sets and Exhibits. The item sets and exhibits shall have a utility to automatically rearrange the options of each of the items while maintaining the correct key. 5.4.2.6. Ability to create pools. 5.4.2.7. Ability to create timers. 5.4.2.8. Ability to create exams capability. The exams cap ability shall include messages, help content and tutorials of text and images for informational and communication purposes to the examinees. It shall also be able to configure when review screens are available to the examinee and the items and sections tha t are visible to the examinee for review. In addition, it shall be able to scheduled breaks for examinees (based on time allotments). 5.4.2.9. Content versioning. 5.4.2.10. Ability to audit and provide reporting of answers provided by examinees for trend a nalysis and statistical findings. 5.4.2.11. Ability of review processing workflow which will allow content that is generated, modified or deleted to follow through a vetting process for validation prior to implementation. 5.4.2.12. Use the CMS resource as the data repository for all test content. 5.4.2.13. Ability for system users to input and for the system to correctly display letters, numbers and symbols of English and non-English speaking languages. 5.5. Output of the system. The output system shall hav e the following attributes: 5.5.1. Web Deliverable Digital Test. The web deliverable digital test content packages consisting of Text (XML, HTML, Unicode, etc.) and Binary files (Images, Audio files, etc.) that provides the content and resources used by t he appropriate test delivery driver. The Government will all input test content into the system. 5.5.2. Paper & Pencil Delivery Test. The Paper & Pencil delivery of tests shall include camera-ready test booklets, answer keys and audio resource files for publication of a CD to accompany the tests (MP3 and WAV formats). Shall acquire a system that creates paper copies of the tests that are generated by the test authors. The system requires the capability to burn the audio files to CD; however, contractor is not required to create audio files. The system requires audio & video inputted into the CMS (refer to PWS paragraph 5.4.1.6), the WDLPT shall use the CMS as a data repository (refer to PWS paragraph 5.4.2.12). 5.6. Install System. Shall design, deliver , and install one hardware and software system. 5.7.5. Training. Provide training within 30 days of project completion and include hard copies of all applicable documentation, manuals and training materials. Training will be accomplished by an on-site ins tructor(s)at the Governments place of business. Training will be scheduled in coordination with the COR. Training shall be conducted based on requirements for the following user roles: 5.7.5.2.1 Administrator Level Training. Shall train 5 government employ ees on the topic How to install, configure, troubleshoot, diagnose, and make changes to the software at the application level. 5.7.5.2.2. User Level Training Shall train 80 government employees on the topic How to perform the requirements described in p ara 5.4.2. through 5.4.2.8. 5.7.5.2.3. Train the Trainer Training. Shall train 2 government employees that will fulfill any training requirements after provided training is executed. These individuals will be trained on how to facilitate the training pro vided in para 5.7.5.2.1 & 5.7.5.2.2. 5.2.6. Technical Support. Shall provide a customer software support, with a toll free support line, and available email and remote diagnostics during normal business hours for Pacific Standard Time (PST) with an option to extended hour coverage (up to 24 hours x 7 days). Shall provide patches, hot-fixes and updates required to sustain security and functionality. 6. Data Considerations. 6.1. Quality. It is the responsibility of the contractor to ensure that all deliverab les (draft or final) meet the Government's evaluation standards for software maintenance, modification, development and/or troubleshooting work as described in Sections 6.1.1 thru 6.1.1.14. If draft or final deliverables do not meet the evaluation standard s for software maintenance, modification, development and/or troubleshooting during the initial Government review, the draft or final deliverables will be retur ned to the contractor for revision. It shall be the responsibility of the contractor to correct the errors without any additional cost to the Government. The Government review period will not begin until initial Government review finds that the work meets acceptable standards for technical written work and is delivered on the due date specified. 6.1.1.Technical Evaluation Standards. The following standards relating to software development, troubleshooting or maintenance shall be the basis for acceptable Gov ernment technical evaluation. Products that do not meet any or all of these specific standards will be returned for revision in accordance with paragraph 6.1, Quality. Acceptable levels are on a percentage basis. The higher the percentage, the more critic al the government standard is met. For example: It is absolutely vital that the provided system meets para 6.1.1.1. Correctness where as para 6.1.1.4. Flexibility is not as critical but still required to a minimal extent. 6.1.1.1. The extent to which a pr ogram satisfies its specification and fulfills the mission objectives. The acceptable level for this standard is 99%. (CDRL A009). 6.1.1.2. The amount of computing resources (e.g., storage space, processing time,communications bandwidth) required by a prog ram to perform a function. The acceptable level for this standard is 75%. 6.1.1.3. The relative effort to increase the software capability or performance by enhancing current functions or adding new functions or data. The acceptable level for this standard is 25%. 6.1.1.4. The ease of effort required modifying an operational program. The acceptable level for this standard is 25%. 6.1.1.5. The extent to which access to software or data by unauthorized persons can be controlled. The acceptable level for this standard is 99%. 6.1.1.6. The relative effort required for interaction between tools/systems. The acceptable level for this standard is 90%. 6.1.1.7. The ease of effort for locating and fixing a software failure within a specified time period. The acceptab le level for this standard is 80%. 6.1.1.8. The relative effort to transfer a program from one hardware configuration and/or software systems environment to another. The acceptable level for this standard is 25%. 6.1.1.9. The extent to which the software w ill perform without any failures within a specified time period. The acceptable level for this standard is 80%. 6.1.1.10. The relative effort to convert a software component for use in another application. The acceptable level for this standard is 20%. 6 .1.1.11. The extent to which the software will perform and support critical functions without failure within a specified time period when a portion of the system is inoperable. The acceptable level for this standard is 80%. 6.1.1.12. The relative effort re quired to test a program to ensure that it performs its intended functions. The acceptable level for this standard is 75%. 6.1.1.13. The relative effort required for using software (training and operation; e.g., familiarization, input preparation, executi on, and output interpretation). The acceptable level for this standard is 75%. 6.1.1.14. The relative effort required to verify the specified software operation and performance. The acceptable level for this standard is 90%. 6.2. The Government will revie w all products within 30 days of contractor completion. Government review shall not begin until such time that deliverables are received on the due date specified and that quality deliverables are received in accordance with paragraph 6.1, Quality. During the review period, if errors are discovered, it shall be the responsibility of the contractor to correct errors without additional cost to the Government. Upon completion of review, the Government may elect to request the contractor provide written clarifi cation of any portion of the documents/reports. The contractor shall provide written clarification within 10 days of the Government request. 6.3. Monthly Status Report. A project status report shall be completed monthly beginning the second month of performance (November 2007) until the end of performance (September 2008). The contractor shall deliver Defense Language Institute - Foreign Language Center, Bldg. 4 20, Presidio of Monterey, CA 93944. 8. The contractor shall accomplish software development off-site and provide the Government functionality of the software via a secure website. Software development off-site shall require the contractor to perform accept ance testing and implementation on the Government site. The contractor shall provide non-personal services for the period 28 September 2007 27 September 2008. Travel will occur and be reimbursed in accordance with the applicable Federal travel regulation s and FAR 31.205-406(a) (2). Contractor will prepare trip reports on all travel within 5 days to document purpose of travel, issues resolved and issues remaining. Trip reports shall be submitted to the designated Contracting Officer representative. The Co ntractor and the contractors employees must register their vehicles with the Provost Marshal within 48 hours prior to reporting to assigned job site at, Presidio of Monterey, CA The contractor is responsible for contacting the Provost Marshalls Office to determine what documentation is needed to register vehicles. The contractor shall provide each employee an identification (ID) badge. The ID badge shall be made of a nonmetallic material. The badge shall be easily readable and include employee name, comp any name, functional areas of assignment, and color photograph. The contactor personnel shall wear the ID badge at all times when performing work under the contract to include attending government meetings and conferences, unless otherwise specified in the contract. Each contractor employee shall wear the ID badge in a conspicuous place on the front of the exterior clothing and above the waist. The contractor personnel shall identify themselves as contractor employees when answering government telephones. W hen contractor personnel send e-mail messages to government personnel while performing this contract, the contractors e-mail address shall include the company name together with the persons name. When it is necessary for contractor personnel to have a us er address on a government computer, the government shall ensure that persons e-mail address includes the name of the company and indicates contractor. Information Security Requirements. All materials are considered Sensitive but Unclassified (SBU). Gove rnment Legal Holidays. All deliverables shall be delivered Defense Language Institute - Foreign Language Center, Bldg. 420, Presidio of Monterey, CA 93944. The deliverable are as follows: Hardware and Software Development Plan 15 Oct 2007; In-Progress Rev iew; Systems Requirements Analysis qty. 2, 15 Nov 2007; Software Design qty. 2, 15 Dec 2007; Coding, Implementation, Testing qty. 2, 30 May 2008; Installation of Hardware qty. 1, 30 May 2008; Verification and Validation 15 Jun 2008; Acceptance Test Pla n qty 2, 15 Jun 2008; Users Manual qty 2 15 Jul 2008; Corrective Action qty 2, As quality deficiencies occur; Monthly Project Status Report; Training within 30 days of project completion. The following Federal Acquisition Regulation (FAR) and Defense Fe deral Acquisition Regulation (DFARS) provisions and clauses apply: 52.204-9, 52.222-20, 52.227-17, 52.233-352.242-13, 252.204-7003, 252.204-7004 Alt A, 252.205-7000, 252.212-7001(DEV), 252.219-7011, 252.227-7020, 252.227-7026, 252.227-7027. FAR 52.212-2 i ncludes BASIS OF AWARD Award will be made to the lowest priced Technically Acceptable offeror. Option prices will be included for evaluation purposes only and will not obligate the Government to exercise the options.
- Place of Performance
- Address: ACA, NRCC, Mission Building 2796, Fort Eustis VA
- Zip Code: 23604
- Country: US
- Zip Code: 23604
- Record
- SN01405912-W 20070915/070913222304 (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 |