AMENDMENT_SEP82012.rtf

file_0.wmf file_1.wmf

SP4705-12-R-0015

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

ADDENDUM 52.212-1

52.212-1 ADDENDUM – INSTRUCTIONS TO OFFERORS - - COMMERCIAL ITEMS (JUN 2008)

(b)(2) Proposal shall be received no later than September 14, 2012 2:00 PM (Eastern Standard Time). Fax responses and email response will be accepted. However, hardcopy must be delivered on or prior to the due date. Submit offers to the address located in Block 9 on Page 1 of SF 1449. Advance copies of the response can be email at beverly.j.williams@dla.mil" beverly.j.williams@dla.mil. Note: All responses must include the solicitation number on the cover page. If sending an advance copy via email, the solicitation number must be included within the subject line.

(b)(12) Submit one (1) original copy of the technical proposal and one (1) copy of a technical proposal which clearly removes all mention of the contractor’s name (REDACTED TECHNICAL Proposal). NOTE: The REDACTED Technical Proposal must clearly be labeled as “REDACTED”. Failure to include a redacted copy will automatically be deemed nonresponsive.

(4) Technical Proposal: Provide a written narrative that describes your technical qualifications and addresses your ability to meet the requirements set forth in the Performance Work Statement. The proposal must identify what system will be used and the specification of the system proposed. All technical proposals must also include a completed copy of Appendix A.. The system proposed must meet all critical and mandatory requirements. Proof of any certifications mentioned within the resume must be included in the technical proposal for the person being proposed to perform the required services.

(8) Certifications and Representations. FAR clause 52.212-3, Alt I: complete applicable fill-ins.

(10) Past Performance: Offers shall include the resume of the person(s) proposed to provide the required services as within the PWS. Resume(s) shall describe the proposed personnel’s credentials. Offeror must provide past performance reference for the same or similar services provided. For past performance references provide the current points of contact information, identify any government contract number, type of services provided, a description of the services provided, and number of years services provided.

(m) Questions and/or requests for information concerning this solicitation should be submitted in writing via email, within two days of the issuance date of this solicitation/amendment, to Beverly J. Williams, at email address: beverly.j.williams@dla.mil" beverly.j.williams@dla.mil. Fax # 703-767-1172.

(End of Provision)

EVALUATION FACTORS FOR AWARD (LOW COST, TECHNICALLY ACCEPTABLE)

Award of the contract resulting from this solicitation will be made to the responsible offeror whose proposal is technically acceptable, in full compliance to all other requirements set forth in the solicitation, and the lowest cost or price. The Government reserves the right to eliminate from further consideration those proposals which are considered unacceptable and not capable of being made acceptable without major revision. To be determined technically acceptable, the offeror proposed product must meet all critical and mandatory requirements as indicated in Appendix A.

AWARD WITHOUT DISCUSSIONS

The Government may award a contract based on initial offers received, without Oral Presentations and/or discussions. Offerors are urged to ensure that their proposals are submitted with the most favorable terms in order to reflect their best possible potential, since less than the best potential could result in exclusion from consideration for award. The Government reserves the right to conduct discussions if later determined by the contracting officer to be in the Government’s best interest.

PWS - REVISED

PERFORMANCE WORK STATEMENT - Revised For Hosted COTS Student Information System (SIS) and Data Consultation Services

1.0 Overview

Executive Summary The National Defense University (NDU) is the premier joint professional military education institution in the world headquartered at Fort Lesley J. McNair in Washington, D.C., with a branch campus in Norfolk, VA, and an academic site at Fort Bragg, NC, as well as several online distance education offerings. The University currently consists of five Colleges (including the branch campus in Norfolk, VA) granting Master’s Degrees and graduate-level certificates. NDU is responsible for providing rigorous education and training that supports the joint warfighter across the globe to include military and government leaders, international officers, and industry partners. The University’s programs provide a unique graduate-level focus on security strategy for over 3,500 full-time equivalent graduate students and approximately 12,000 non-credit students annually.

NDU’s mission is:

National Defense University supports the joint warfighter by providing rigorous Joint Professional Military Education to members of the U.S. Armed Forces and select others in order to develop leaders who have the ability to operate and creatively think in an unpredictable and complex world.

As the premier joint professional military education institution, NDU requires a fully-hosted enterprise-wide Commercial Off-the-Shelf (COTS) Student Information System (SIS) on a Software-as-a-Service (SaaS) platform that is Common Access Card (CAC) enabled to provide best-in-class functionality, services, stability, security, capability, and quality. The selected hosted COTS system will integrate people, processes, technology, and strategies in order to provide a holistic, self-service, and collaborative system. The initial phase of the system will include software licensing and application, hosting, and implementation/training for approximately 15,000 students (in-resident and online) for the Academic Year 2013-2014 (approximately 3,500 full-time equivalent students annually). See Appendix A for the SIS detailed requirements.

As a University, NDU has no greater task than to ensure that students are correctly matriculated, enrolled in courses, and ultimately graduated with the necessary body of strategic knowledge to become the world's military and government leaders. NDU must also comply with the reporting requirements of the DOD, Joint Chiefs of Staff (JCS), Congress, and the Middle States Commission for Higher Education (MSCHE). The University needs to address its internal needs for enrollment management, student services, institutional research, planning and assessment. It is imperative that the student information utilized for these purposes be accurate, reliable, and valid; be accessible efficiently and effectively; and be securely housed. Thus, NDU requires a SIS that facilitates the institution’s management of student-related data and functions and increased capacity to manage academic records securely with a focus on greater efficiency and effectiveness.

NDU’s student base is uniquely comprised of senior military officers, senior government agency employees, international military officers, and select others. The current system houses over 3,500 student profiles. The proposed system should have the ability to accommodate a minimum of 20,000 active student profiles and be scalable to have the capability to accommodate annual growth in enrollment.

2.0 NDU’s Current Operating Environment

This section describes and diagrams the environment in which NDU operates and includes the systems to which it currently interfaces and some related but peripheral systems.

2.1 Definitions

Throughout this document, the definitions located in Appendix B will be used.

2.2 NDU’s External Interfaces

The Vendor will provide on-line and printed system documentation in editable format with the right to modify and reproduce for NDU’s sole use.

Vendor shall support the interfacing of the SIS software to other systems/software within the NDU environment. These include: Blackboard, Defense Civilian Personnel Data System (DCPDS), Defense Travel System (DTS), Military Personnel Data Systems (MILPDS), and the Lenel security access and badging system.

Blackboard Online course management system that allows professors to post grades, information, and assignments. They can also hold discussions and students can turn in assignments through the system.

Defense Civilian Personnel Data System (DCPDS) The civilian personnel data system of record for the DOD Defense Travel System (DTS) DTS is DOD’s enterprise-wide transactional travel system Military Personnel Data Systems (MILPDS) A term used to describe the combination of the Army, Navy, and Air Force’s personnel data systems.

Lenel Systems The security access and badging system utilized by NDU.

The Vendor shall support the on-going configuration of the system to ensure continued maximum effectiveness and efficiency of the SIS.

2.3 NDU’s System Context

The current system context for NDU’s legacy student information systems is as follows:

The core group of the legacy platforms is a Data Enterprise System (DES), an institutionally developed (home-grown) system which provides multiple functions for the various components served by NDU. DES consists of DES v.0 (Joint Forces Staff College), DES v.1.a (The Eisenhower College), DES v.1.b (National War College), DES v.1.c (College of International Security Affairs), DES v.1.d and DES v.2 (Information Resources Management College).

The second group of the legacy platforms is UNet, an Oracle based system modified from Peoplesoft.

The third group of the legacy platforms is Appnet.

2.4 NDU’s “To Be” Environment

The completion of this contract will result in the vendor establishing and hosting:

A single enterprise-wide SaaS COTS SIS that will replace NDU’s legacy systems.

The SIS will integrate and interface with NDU’s non-SIS systems, as described above.

2.5 User Types and Needs

The following table profiles the characteristics and needs of the four primary user classes that NDU currently serves: Students, Faculty, Staff, and non-NDU.

User Class Profile and Needs Student Users Student user base is comprised of approximately 2,000 degree/certificate students and 15,000 student profiles including training students.

Enrolled students will utilize the SIS to engage in a variety of educational, administrative, co-curricular and extra-curricular activities during their career as a member of the NDU student body. Prospective students will utilize SIS to explore various aspects of NDU. Student needs include:

General and Administrative functions Find general and program information related to degrees, certifications, programs, courses, etc.

Request registration/application for programs, courses, and other events Access and download their student records Access course offerings and other events and requirements Perform a program audit to determine outstanding requirements Update select student record data elements Communicate with students, faculty, staff, and functional communities Educational activities Communicate with instructors Course evaluations Faculty Users The faculty user base is comprised of approximately 300 members. They are involved in a wide range of educational, research, career path related, administrative, and extra-curricular activities. Faculty needs include:

General and Administrative

Communicate with faculty, students, staff, and communities Submit employee-related documents Attend department, college, campus and committee meetings Educational activities Serve as academic advisors and check student records Communicate with students (individually and in groups) Assign grades and submit them to the university Complete student assessment and evaluations Complete course evaluations Scholarly and Creative activities Maintain and update credentials Record research and publications Record professional development Record professional/scholarly involvement in profession—boards, panels, etc.

Staff Users The staff user base is comprised of approximately 200 administrative personnel to include system administrators. This heterogeneous group of end-users includes NDU administrative officers, administrative and clerical assistants, student support professionals, fiscal officers, facilities employees, information technology consultants, etc. Many of these individuals perform tasks similar in requirements to those of students and faculty in addition to a variety of job-specific tasks. Examples include:

Communicate with staff, faculty, students, and communities

Administration of student registration and schedules Develop and maintain schedules Helping students with support needs Budget and forecast planning and administration Paperwork and document workflow Record/data management Information dissemination Facilities management Performing a variety of other job-specific tasks Many of the same activities as students and faculty Workforce reporting Policy Off-Campus and Non-NDU Users Members of alumni, professional colleagues, curiosity seekers, community groups, industry personnel, government personnel, and prospective faculty, staff, and students will likely use the public and private portions of SIS to navigate and explore NDU-related information.

Communicate with alumni, faculty, and staff

Explore enrollment in resident or continuing learning modules Find information on NDU offerings and events

3.0 Business Model

NDU’s current business model lacks an integrated means of providing registration, student services, student management, schedule development and management, catalog requirements, database of record for transcripts, and institutional assessment/reporting. The lack of an integrated enterprise-wide student information system: a) makes rapid reporting and timely trend analysis difficult and time consuming, b) requires NDU to rely on systems to which it lacks control over upgrades, and availability, c) relies on a complex web of system interfaces that are patched and stove piped, d) uses outdated technology, e) lacks design documentation, f) uses disparate business processes, and g) is costly and time consuming to add new functionality, test, and train. We expect the new SIS to solve these issues.

3.1 Business Strategy

NDU requires an integrated enterprise-wide student information system to facilitate efficiency in execution and application of the institution’s business processes, procedures, and policies. NDU requires an integrated enterprise-wide student information system to:

replace the current legacy SIS system(s) with a new state-of-the-art hosted COTS system;

provide web access through a format compatible with any web access device and NDU computers;

provide user access 24x7x365;

include project management, configuration management, workflow, business process reengineering, quality control, testing, helpdesk, and documentation;

include comprehensive student management and student services;

include comprehensive enrollment management and registration;

include comprehensive academic and enrollment planning including cataloging, degree planning, etc.;

include a comprehensive student information database;

provide efficient and effective administrator, faculty, and student user services and support;

include data warehousing services and support;

include efficient and effective business intelligence and analytics tools;

include efficient and effective institutional research, planning, assessment and effectiveness;

include efficient and effective alumni tracking;

provide training in the use of the system;

support and enable the interface with existing NDU systems, as described above;

support and enable the interface of the SIS with other DOD systems, as described above;

provide initial operating capability (IOC) within four (4) months of contract award; and provide full operating capability (FOC) within twelve (12) months of contract award.

Provide best in class functionality and capability such as:

standard business processes and rules;

ease of use;

scalability;

web portal;

collaborative communication and reach-back capabilities to report, assess, and evaluate assets; and ability to use data as an enabler to enhance analysis, identify trends, and help drive informed decisions in areas such as:

student management and student performance;

enrollment management and academic planning;

track degrees, certificates, completions and alumni;

provide customers with a self-service, real-time, anytime, anywhere access, and management capability for:

Registration On-line course access Transcript requests Student services Faculty services Administrative services Accurate and timely monitoring and reporting of NDU academic metrics

3.2 Assumptions and Dependencies

The following are the assumptions and dependencies for the SIS:

The SIS will be a COTS product and will be on vendor’s most recent release;

The COTS SIS vendor will host the system on a DOD approved secure server site;

The selected COTS product will be able to meet all DOD security and policy constraints; for example DIACAP (DOD Information Assurance Certification and Accreditation Process) and FISMA (Federal Information Security Management Act) and Federal Risk and Authorization Management Program (FedRAMP) security requirements;

“Out of the Box” functionality will be utilized to the fullest extent possible;

The SIS will be able to interface with existing internal NDU systems and external DoD systems as necessary;

The SIS will comply with Title 40 Code of Federal Regulations, Protection of the Environment, requirements;

The system must comply with Section 508 of the American Disabilities Act;

Interim Operating Capability within four (4) months of contract award;

Operating Capability for students admitted/selected for Academic Year 2013-2014 must be available by April 1, 2013;

The system must be made available through multiple forms of authentication to include Common Access Card (CAC) and DOD Authentication;

The system will be able to mask personal identifiable information (PII), such as SSN, DoB, etc.;

The system will be extensible to allow for future growth;

The system will provide for maximum data security, data integrity, data synchronization, data accessibility, and semantic interoperability between systems within the DOD Enterprise.

4.0 Deliverables

4.1 General Description

Although NDU requires the contractor to host the service on a SaaS platform, the services will be located at National Defense University, Marshall Hall, Ft. Lesley J. McNair, Washington, DC, 20319. The process owner for the service and the point of contact for all services is the Office of Academic Affairs (202) 685-0080. The vendor shall perform the requirements of the contract on location at NDU, in coordination with the vendor-provided data center. The government will provide the vendor with an appropriate workspace and access to the NDU systems environment. Contractor personnel shall work the same shifts established for government military and civilian personnel at their respective locations, and observe the same holidays and government-sponsored events, unless otherwise called for by the SIS Project Manager. The contractor shall:

provide a Software as a Service (SaaS) Commercial Off-The-Shelf (COTS) Student Information System (SIS) in a vendor-hosted environment on a DIACAP/FISMA approved server and all associated materials and supplies for a licensing fee on a Firm Fixed Price Basis;

provide all management, supervision, labor, materials, supplies, and equipment required for implementation, integration, interfacing and training (except as otherwise specified) on a Firm Fixed Price Basis; and perform each of these in accordance with all details, requirements and sections of the contract.

4.2 Period of Performance

The period of performance for implementation of the project will be for a base year and two, one year option period. See the below for additional information:

(1) Initial Operating Capability (IOC) completed no later than 6 months starting from the date of award; Initial Operating Capability (IOC) is when acceptance takes place after all core NDU and vendor use cases are tested, corrected, accepted and working to include but not limited to, the system features of: student registrations; scheduling; cataloging; degree management; faculty and staff functions; interfaces; and workflows. All features must be compliant according to the Security Technical Implementation Guide (STIG) and pass vulnerability scans as required by DIACAP and have been tested within the scope of interim authority to test.

(2) Full Operating Capability (FOC) no later than 12 months, including the ability to begin support for AY2013-2014 students in April 2013. Full Operating Capability (FOC) is when acceptance takes place with refinement and completion of all system functional requirements and receipt of final DIACAP signoff for "authorization to operate" (ATO) and the system is moved into

Operations & Maintenance Phase.

(3) Option Periods. After FOC is reached and the system has moved into the Operations & Maintenance Phase (estimated date is 1 October 2013), the vendor shall offer an annual renewable licensing and hosting during Option Year 1 (FY 2014-2015) and Option Year 2 (FY 2015-2016). The annual renewable period renews the licensing and hosting and ongoing maintenance and training.

4.2.1 Annual Renewal of Licensing and Hosting

The vendor shall offer an annually renewable enterprise licensing and hosting fees option for a two-year period following the initial award of the contract that is fair and reasonable according to industry standards and market competition. The annually renewable enterprise licensing and hosting option shall be to provide ongoing delivery of the product (maintenance), licensing fees, and hosting costs and will comply with the requirements described in the PWS.

4.3 Information Assurance (IA) and Personal Identifiable Information (PII):

The majority of DOD workforce members use a Common Access Card (CAC) to authenticate on computer systems and websites. The SIS will need to be able to allow for multiple forms of authentication to include CAC and native security.

All software must meet strict security guidelines for IA as well as the Federal Information Security Management Act (FISMA). DOD has its own accreditation process called DIACAP (DOD Information Assurance Certification and Accreditation Process). The COTS SIS software will need to demonstrate initiation of the DIACAP process at the time of response to the RFP and pass this accreditation process within 45 days of contract award. The hosted COTS product vendor is entirely responsible for adherence to DIACAP and FISMA processes, procedures, updates and ongoing evaluations to ensure that the system is secure. Security requirements mandate periodic testing that will be performed throughout the period of performance. The hosted COTS vendor shall be committed to correcting vulnerabilities found by testing in a timely manner.

Data covered by the privacy act will be in the COTS SIS. The SIS must comply with all Privacy Impact Assessment (PIA) directives, to include record level access controls that ensure systems users only see information on those members for whom they have a valid need, and auditing of access to privacy act data.

The Federal Risk and Authorization Management Program (FedRAMP) introduced an innovative policy approach to developing trusted relationships between Executive departments and agencies and cloud service providers (CSPs). FedRAMP provides a cost-effective, risk-based approach for the adoption and use of cloud services. The hosted COTS vendor shall abide by the guidance in the Office of Management and Budget (OMB) Memorandum, dated December 8, 2011.

4.3.1 Business Systems Infrastructure

The Contractor shall provide for the architecture design, development, installation, modification, maintenance, operations, upgrades, configuration management, and security of business systems databases, application servers, and web servers.

4.3.2 Records Management

The Contractor shall provide for the design, development, installation, maintenance, operations, upgrades, configuration management, archiving, customer support, training; and security of electronic records systems and related applications including tracking systems for technical reports and data. The Contractor shall provide technical support and coordination to ensure effective and efficient Records Management and compliance with Federal Records Management mandates, including but not limited to entering records into the system; reviewing policies and procedures; supporting day to day operations; and archiving records.

4.3.3 System Administration

The Contractor shall provide products and services in order to maintain a stable, efficient, and reliable computing environment. These activities include: system software maintenance and updates, ensuring compliance with DoD IT security requirements, privileged user account management, user account management, configuration management, system upgrade / improvement, computing operations, maintenance of systems documentation and procedures, and contingency planning.

4.3.4 Information Technology Security

The Contractor shall provide a secure computing and communication environment through the protection of IT based systems, components, and information such as computers, networks, software applications, operating systems, and data protection in accordance with DoD Information Assurance Policies. The Contractor shall be responsible for developing Certification and Accreditation (C&A) documentation (following DIACAP requirements), develop detailed technical standard operating procedures complying with FISMA, OMB A-123, the Privacy Act, and DOD policies.

Technical areas of focus for IT Security include: risk analysis and assessment; system monitoring and intrusion detection; penetration testing; incident response plans and capabilities; firewall design, monitoring, maintenance, and upgrades; development, integration and deployment of public key-enabled encryption and security services; public key infrastructure and services; disaster planning and recovery; prompt application of security-relevant software patches, service patches and hot fixes; certification and accreditation in accordance with DIACAP and the protection of Personally Identifiable Information (PII).

4.3.5 Data Storage Retrieval and Archival

The Contractor shall provide the IT systems and related services necessary to store and to have reliable and secure access to large amounts of electronic data. Technical areas of focus include: systems engineering, deployment, and operations; storage for near-term, long term, and archival requirements; shared access and security features; data integrity, disaster plans, and backup systems; user interface/access systems; identifying potential sources for required products and services.

4.3.6 Information Assurance Contractor Training and Certification

(a) The Contractor shall ensure that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions in accordance with DOD 8570.01-M, Information Assurance Workforce Improvement Program. The Contractor shall meet the applicable information assurance certification requirements, including:

(1) DOD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DOD 8570.01-M; and

(2) Appropriate operating system certification for information assurance technical positions as required by DOD 8570.01-M.

(b) Upon request by the Government, the Contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions.

(c) Contractor personnel who do not have proper and current certifications shall be denied access to DOD information systems for the purpose of performing information assurance functions

Reporting: The contractor shall report loss or unauthorized disclosure of information in accordance applicable DOD policies.

Background Investigation: The contractor shall meet the background investigation requirements in accordance with DODI 8500.2 to accomplish their IT duties.

4.4 Operational Requirements

The SIS System must be capable of meeting operational requirements such as, but not limited to the following:

(a) The SIS will operate within a fully integrated web portal with an open standard, web-centric architecture, utilizing a COTS package.

(b) The SIS is expected to incorporate the following components in an enterprise environment: non-administrative users can utilize any web-enabled device to access the system without additional software; administrative users can utilize any web-enabled device to access the system with minimal additional software requirements; the load on NDU’s existing wired and wireless networks will be minimal; the SIS will be hosted on DOD approved servers in a secure environment; and for any additional software, the SIS will only utilize DIACAP/FISMA approved commercial software application packages.

(c) NDU students will access the COTS SIS from various computers and web-enabled devices. As such, they shall not have administrator privileges on these devices. The SIS must not require any elevated permissions or software for students to access or operate within the system and it must have zero footprints.

(d) Users should be able to access the system 24X7X365. The system will comply with Section 508 standards and protect personally identifiable information. The system will operate within an open standards/net centric environment.

4.4.1 Architecture - Database and Hardware

The COTS SIS vendor will secure sufficient server space for the operation of the SIS on an approved DOD server farm. The SIS vendor will provide NDU with an archive data repository/warehouse and an active data warehouse that are designed with a standard architecture that NDU is capable of replicating for an internal backup on NDU’s internal servers.

4.4.2 Telecommunications Requirements

Vendor shall route their traffic such that the service meets the requirements of the Trusted Internet Connection (TIC) program (FedRAMP requirement).

4.4.3 User-System Interactions

The system should have extensive communications functionality to serve as a one-stop portal for the student body allowing for both targeted and broadcast messaging. The system should have an intuitive and user friendly interface to allow for ease of use by students, faculty, staff, and other stakeholders. NDU anticipates using role based security to determine functions and abilities available to specific users. Each user will be assigned a defined role or roles and the associated privileges with those roles.

4.4.4 Business Process Re-engineering (BPR)

The vendor shall conduct an analysis of NDU’s current business processes and provide best practices recommendation to re-engineer processes to maximize benefits of implementing the Vendor’s COTS product. Accepted recommendations shall be incorporated into the Project Plan for implementation. The Business Process Re-engineering plan should include the tools and methodology required to execute BPR with respect to the functional requirements, describe the roles and responsibilities of NDU versus the Vendor. Vendor shall execute in accordance with the approved plans.

4.4.5 Performance Requirements

The COTS SIS will leverage the latest commercially-proven technology to optimize the learning experience and NDU’s institutional competencies.

From an individual user perspective, NDU seeks a state-of-the-art system environment that connects individual users to the full range of information and services in a quick and simple manner, without the resistance of technological limitations. From a collective perspective, NDU seeks a state-of-the-art system environment that seamlessly interconnects the functional bodies together in a way that strengthens the core competencies of NDU as a world-class institution of learning.

The SIS will be extensible with the ability to support future growth of the NDU with no degradation of system response time. Disaster recovery capabilities must exist to ensure SIS operations can continue in the case of disaster at the COTS SIS’s main data center.

4.4.6 Reporting Requirements

NDU must have the ability to report on data at both macro and micro levels. The SIS should offer standard Business Intelligence (BI) and data warehousing with dashboarding capabilities. Pre-defined standard reports with flexibility to created ad-hoc reports should be included, as well as the ability to copy standard reports, change criteria, schedule reports to run at specific times, and broadcast to groups or dashboards.

4.4.7 Vendor Service Offerings

Once a COTS SIS product has been selected and procured, the Vendor will provide comprehensive consulting support to ensure a successful implementation within the time and price parameters documented in their proposal.

COTS vendors shall provide an accurate assessment of COTS current capability, without overstatement, to fulfill the current and forecasted needs contained within this requirements document. The Vendor shall offer enterprise licensing costs that are fair and reasonable according to industry standards and market competition. The contractor will incorporate any major release of the SIS system software that was originally purchased into the implementation process during the base period while the project is underway. (For example, if release 3 becomes available to the Vendor’s client base while NDU was implementing release 2 of the software during the base period, the Vendor will migrate NDU over to the release 3; either prior to release 2 going into production or after release 2 was in production at NDU). The hosted COTS Vendor shall demonstrate, through past performance, that it has the technical and managerial ability to efficiently implement a state-of-the-art SIS, and the corporate stability and future power to continue in business to effectively support both warranty and future expansion of the SIS. The hosted COTS Vendor shall not design, install, or implement any proprietary components of SIS which would limit third party involvement in supporting the operation or maintenance of the SIS.

The vendor will need to coordinate and work with other NDU and DOD contractors in performance of this contract.

4.4.8 Project Management and Deliverables

The vendor will provide project management services to ensure that the project is delivered on-time, within budget, and provide full functionality as defined by NDU. The project management services will include a project manager, full-time and on-site from the commencement of the contract through acceptance. The project manager will be highly experienced and successful in SIS implementations and in project management of these efforts at institutions of comparable size to NDU. He/she will lead the vendor’s implementation team and work closely with NDU’s Project Manager and the SIS Core Team to determine the scope and schedule of each component of the implementation, the appropriate implementation methodology of this project, and assist with issues such as change management, decision making, and communications. Modifications or deviations to the project’s requirements or schedule must be documented and pre-approved by the NDU SIS Committee. The SIS will be installed in accordance with the project schedule outlined in the accepted project plan. The vendor shall provide timely status reporting to the NDU SIS Committee; monthly status reports for routine progress, milestone updates, project challenges, proposed solutions, forecasted activities, and action item updates; weekly status reports for urgent progress, project challenges, proposed solutions, forecasted activities, and action item updates; and immediate status reports within 24 hours of an event or issue that could impact or delay the project schedule. All reports shall be documented and furnished to the SIS Project Manager within 24 hours of status reporting. The project manager will propose “best practices” solutions and develop recommendations and options for implementing required business functions using the capabilities of the new SIS.

4.4.9 Quality Control

The Vendor shall appoint a Quality Reviewer who is qualified to oversee the operational and technical integrity of the entire development, testing, and implementation process. The Quality Reviewer shall directly support the SIS Project Manager, and provide inputs of positive or negative developments as part of the status reporting requirement above. The vendor shall implement within a quality process that provides for assessing data quality, timely and accurate execution of processes, and implementation of mitigation strategies. CMMi, ISO or other industry standard quality processes are preferred. The vendor shall provide a quality control and quality assurance surveillance plan and shall execute in accordance with the approved plans.

4.4.10 Implementation Services

The target completion timeline for implementation for the project will be at Initial Operating Capability (IOC) completed no later than 6 months starting from the date of award and be at Full Operating Capability (FOC) no later than 12 months, including the ability to begin support for AY2013-2014 students in April 2013. [Must be operational for AY 2013-2014 student body]. The Vendor shall perform the requirements of the contract on location at NDU, in coordination with the Vendor-provided data center. The government will provide the Vendor with an appropriate workspace and access to the NDU systems environment. Contractor personnel shall work the same shifts established for government military and civilian personnel at their respective locations, and observe the same holidays and government-sponsored events, unless otherwise called for by the SIS Project Manager.

Initial Operating Capability (IOC) is when acceptance takes place after all core NDU and vendor use cases are tested, corrected, accepted and working to include but not limited to, the system features of: student registrations; scheduling; cataloging; degree management; faculty and staff functions; interfaces; and workflows. All features must be compliant based on Security Technical Implementation Guides (STIG) and pass vulnerability scans as required by DIACAP and have been tested within the scope of interim authority to test (IATT).

Full Operating Capability (FOC) is when acceptance takes place with refinement and completion of all core and non-core functionality, all system functional requirements and receipt of final DIACAP signoff for "authorization to operate" (ATO) and the system is moved into Operations & Support phase.

4.4.11 Deployment Methodology

Vendor shall employ a defined standard methodology to implement and deploy the system, facilitate workforce training, production turnover and to providing system support. The methodology should be consistent with industry software implementation standards used by Project Management Professionals (PMPs) and/or System Integrators. Vendor shall execute the defined methodology.

4.4.12 Testing

The Vendors software should be developed using a proven methodology of testing and debugging prior to release. The Vendor shall conduct and support end-to-end testing of the modules implemented at NDU and across the entire system to ensure fully functional capability without bugs. Vendor shall execute in accordance with the approved plans.

4.4.13 Training

The Vendor shall equip the associated government personnel with the necessary training to effectively understand and participate in the operational and technical aspects of the full project.

The Vendor will provide software trainers to conduct all essential training for executives, decision makers, technical staff, and end users, employing modern classroom techniques in a facility provided by NDU. Each trainer must have had direct SIS training experience in his/her specialty area in comparable institutions of higher education. All formal training sessions may be videotaped for use by government employees, students, and other stakeholders. Trainers will work with the NDU team to ensure that the appropriate training software and associated database, and training materials are available prior to each formal session. All training materials prepared for these classes become the property of the government for later use, reuse, and/or modification. NDU will also readily accept and support any online and/or CBT (computer base training) training modules that the Vendor has available for its solution.

Training shall be conducted for train the trainers, technical, functional, system administration, etc. on site at Ft. McNair. At least 2 classes per functional area, plus 2 classes for system administration, super-users, databases, and reporting, as well as any other purchased modules must be conducted. Training shall be conducted with estimated 20-25 students per class. Vendor shall execute in accordance with the approved plans.

4.5 Vendor Maintenance

4.5.1 Operations & Maintenance Plan

Once the hosted COTS SIS has been implemented, the vendor will provide ongoing maintenance to NDU for the duration of the contract. NDU requires the COTS SIS to be at Initial Operating Capability (IOC) completed no later than 6 months starting from the date of award and be at Full Operating Capability (FOC) no later than 12 months.

(1) The vendor’s software upgrade process will support generally accepted change and configuration control processes including the ability for NDU to test the software in lower environments prior to a full production migration.

(2) The vendor’s software upgrade processes will be non-destructive to existing data in databases and control information that manages execution of the application.

(3) The vendor will designate a customer service liaison for managing on-going support for NDU. At a minimum, the liaison will host a monthly account session during the first 6 months of implementation, and quarterly sessions thereafter. The account sessions will include post-mortem reviews, a review of outstanding issues, and discuss vendor product direction.

(5) Product support will be available on a 24x7 basis to designated points of contact at NDU.

(6) The vendor will support a guaranteed initial response time frame of 15 minutes for emergency items adversely impacting production business operations.

(7) The vendor will support emergency escalation procedures that notify and engage the executive leadership of their company’s customer support in one business day and product management in two business days.

(8) The vendor shall maintain appropriate levels of escalation protocol, and fully support implementation of its upgrades and new releases.

(9) The vendor shall execute in accordance with the approved plans.

4.5.1.1 Annual Renewal of License and Hosting

The vendor shall offer an annually renewable enterprise licensing and hosting fees option that is fair and reasonable according to industry standards and market competition. The annually renewable enterprise licensing and hosting option shall be provide ongoing delivery the product and complies with the requirements described in the PWS.

4.5.2 Release Management

Vendor shall fully support the software version implemented for NDU and ensure successful upgrades as new releases become available.

Vendor shall provide support to NDU during upgrades and new releases.

The Vendor shall commit to making changes to its software to accommodate any mandated requirements from Congress and/or DOD to ensure timely compliance with such mandates.

4.6 User Support

4.6.1 Help Desk

Provide a helpdesk to support system administrators, super-users with software issues, upgrades, troubleshooting and questions.

Timely, unlimited telephone support.

Minimum 8:00 AM to 4:00 PM EST, to support general business hours for NDU. General NDU business hours are from 8:00 AM. to 4:00 PM., Monday through Friday, except for Federal holidays.

Extended support hours during the weeks before and after system implementation.

Guarantee of support during peak time at the start and end of every Fiscal year, when the schedule goes live for registration, as well as when the system goes live initially.

24 X 7 email/web-based support.

Online, in the application, help should be available within the software.

4.6.2 Documentation

Vendor shall provide comprehensive electronic and on-line system documentation with the initial access to the software system.

Vendor shall provide comprehensive electronic and on-line system documentation and ensure currency within 15 days of update. All documentation, programs, products, data, hardware, software, and any other items associated with this project shall remain in-house at NDU after the completion of the project.

4.7 Warranty

Vendors must give detailed information on manufacturer and/or extended warranty/guarantees that will apply to all products and services that are to be supplied under this request (i.e., length of warranty, specific coverage under warranty, servicing on or off site, response and repair times), if applicable.

Source code for NDU’s version of the product is to be kept current with a third party escrow agent. Proposers should provide information on the third party (i.e. escrow agent) who has access to the product source codes. Cost of the escrow service shall be at the Vendor’s expense.

The Vendor will warrant and guarantee their ownership and/or license rights to all software and intellectual property underlying the SIS package. The Vendor will accept legal and financial costs of intellectual property challenges to the system.

4.8 Subcontracting

If appropriate, the Vendor shall use adequate subcontracting management controls over subcontractors.

5.0 Proposal Requirements

Proposals should identify what system will be used and the specifications of that system. To determine if the product is technically acceptable, the proposal should include the attached matrix (Appendix A) filled out and forwarded with the proposal. The technical proposal must include a complete technical narrative to clearly address qualification, specifications, and the ability to meet the requirement. To be technically acceptable, the product must meet all critical and mandatory requirements as indicated on the Appendix A.

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The set aside percentage 100.00% has been deleted.

The required response date/time has changed from 10-Sep-2012 09:00 AM to 14-Sep-2012 02:00 PM.

The Acquisition Set Aside has changed from Small Business to No Preference / Not Listed.

SUPPLIES OR SERVICES AND PRICES

Global Changes

CLIN 0001 -- CLIN 0002

The FSC code U099 has been added.

The SIC code 8221 has been added.

CLIN 1001 is added as follows:

ITEM NO

SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

Months

OPTION

Maintenance Support Services

FFP

The contractor shall provide hosting, licensing, and maintenance support services in accordance with the attached Performance Work Statement.

FOB: Destination

NET AMT

CLIN 2001 is added as follows:

ITEM NO

SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

Months

OPTION

Maintenance Support Services

FFP

The contractor shall provide hosting, licensing, and maintenance support services in accordance with the attached Performance Work Statement.

NET AMT

DELIVERIES AND PERFORMANCE

The following Delivery Schedule item has been added to CLIN 0002:

DELIVERY DATE

QUANTITY

SHIP TO ADDRESS

UIC

POP 30-SEP-2012 TO

29-SEP-2013

N/A N/A

The following Delivery Schedule item has been added to CLIN 1001:

POP 30-SEP-2013 TO

29-SEP-2014

N/A

The following Delivery Schedule item has been added to CLIN 2001:

POP 30-SEP-2014 TO

29-SEP-2015

N/A

INSPECTION AND ACCEPTANCE

The following Acceptance/Inspection Schedule was added for CLIN 1001:

INSPECT AT

INSPECT BY

ACCEPT AT

ACCEPT BY

Destination Government Destination Government

The following Acceptance/Inspection Schedule was added for CLIN 2001:

INSPECT AT

INSPECT BY

ACCEPT AT

ACCEPT BY

Destination Government Destination Government

(End of Summary of Changes)