LOS ANGELES UNIFIED SCHOOL DISTRICT - BidNet



Proposer Response

Attachment G - Technical Evaluation Matrix

RFP 2000000170

The matrix below is to provide the Proposer with a tool to indicate how its proposed technical solution fulfills the District’s requirements. Proposers who alter the structure or the content of the matrix may be disqualified.

Code Column:

Proposers shall indicate the compliance to each function or feature by entering one of the following codes in the Code column cell to the right of the function or feature:

A = Available in the Proposed Solution. All features and functions designated with an “A” are included in the proposed solution.

B = Not available in the Proposed Solution, but the service can be modified by customizing the package. The Proposer should annotate in the Explanation column how this will be accomplished. If the feature is only offered in addition to the proposed solution, the vendor must separately provide the additional price of purchasing it in the Price Proposal volume.

C = Future feature, not yet available but planned for a future release. Provide an explanation of how the feature will be provided and an estimated release date.

D = Exception, not available in the proposed solution and the feature cannot be provided or is not being offered.

Rationale Column:

The Proposer should use the “Rationale” column to provide specific information about how a feature or function will be provided and, if appropriate, how the feature or function will be integrated. The Proposer will also use the “Rationale” column to cross reference each feature or function to its proposal."

|Requirement Type |Code |Rationale |

|Core Requirements |

|A. System capable of incorporating online content from external providers as well as those from| | |

|the Proposer which will be loaded onto the device. | | |

|B. Capable of functioning using classroom face-to-face, blended learning and asynchronous | | |

|learning formats. | | |

|C. Capability of importing and exporting data from other systems such as externally provided | | |

|student e-mail system (currently the education version of Google Mail), web conferencing | | |

|systems (currently WebEx, Blackboard Elluminate, and Collaborate), and other District-housed | | |

|applications including the Parent Portal communications, MiSIS (My Integrated Student | | |

|Information System), and MyData systems. | | |

|D. System must maintain an agnostic approach to containerizing online and pre-loaded | | |

|instructional content as well as learning management, evaluation and communications systems; | | |

|proposed system should not require lengthy programming and hybridization efforts. | | |

|E. Must be compatible on all major operating systems (Windows, Apple and IOS, Google Android | | |

|and ChromeOS) for all device types such as computers, tablets, and smart phones. | | |

|F. Must be compatible on all commonly used web browsers such as Internet Explorer, Safari, | | |

|Chrome, and Firefox. | | |

|G. Must support learner customization in terms of access to the system itself, learning | | |

|content, assignments and evaluation of classwork, in addition to the features listed in listed | | |

|in the scope of work. | | |

|H. Teaching and learning through the proposed LMS will include access to educational social | | |

|networking systems (e.g. EdModo) for collaboration: student-student, teacher-student, | | |

|school-student/parent, and teacher-parent (and vice-versa). | | |

|I. System shall be role-based in terms of access and restricted access to components as | | |

|appropriate to the user’s level in the system. | | |

|J. Content creation for the LMS by teachers, students, and school staff should not require | | |

|advanced programming knowledge but be modularized and menu driven to allow for maximum | | |

|flexibility to the user and at the appropriate role level. | | |

|K. Administration and security for the LMS shall adhere to FERPA, CIPA, and COPA requirements | | |

|in addition to tracking and monitoring of usage. | | |

|L. Access to the LMS must be through the District’s Single Sign-On (SSO) system. | | |

|M. Support for the LMS shall be provided by the proposer via a toll-free, live | | |

|operator-answered number with a waiting period of no more than 30 seconds per call. | | |

|N. Online assistance in the form of content and professional development on the use of the LMS | | |

|shall be provided. | | |

|O. A description of District resources and requirements necessary for incorporation of the LMS.| | |

|P. Prefers vendor-hosted web-based software solution for a K-12 learning management sytem but | | |

|is willing to review all solutions. | | |

|Q. System must be easy for students at all grade levels to easily participate and navigate in | | |

|the LMS with minimal expertise and with age-appropriate design and layouts. | | |

|Module Components |

|Announcements | | |

|1. Supports the posting of information for students, parents, staff and administration on main | | |

|pages and on course homepages. | | |

|B. Communication, Social Networking, and Discussion Forum | | |

|Supports a variety of discussion forum types. A discussion forum | | |

|The solution shall include communication tools in the software and methods by which the tools | | |

|are managed, including features such as: | | |

|Asynchronous threaded public or private discussions. | | |

|Synchronous chat with transcripts and logs. | | |

|Tools for collaborative working groups. | | |

|Video chat/conferencing, screen sharing, web meeting capabilities. | | |

|C. Calendar/Progress Review | | |

|Supports time-management – Calendar/Progress Review tools. Calendar/Progress Review tools | | |

|enable students to document their plans for a course and the associated assignments in a | | |

|course. | | |

|Display all events in one centralized user calendar (events for school, course, class, student,| | |

|etc.) | | |

|Link directly to other course areas and portals (ability to include events in from Google | | |

|calendar and LAUSD applications). | | |

|Provide for learners’ personal entries. | | |

|Assignment Drop Box | | |

|Supports assignment submission within the online course. An assignment drop box allows learners| | |

|to upload assignments inside the course for instructors to grade and review. | | |

|Ability to download lessons, content, and multimedia files from LMS for review and work offline| | |

|and store in online drop box folder or on user device. | | |

|Integration to Microsoft OneDrive and Google Drive cloud storage via interface with the ability| | |

|to open, edit, save, and modify documents. | | |

|Reporting Tools | | |

|The solution shall possess reporting tools such as: | | |

|Ability to aggregate assessment results/activity data at varying levels of the organization. | | |

|Ability to evaluate learner level and program level assessments. | | |

|Ability to preview reports online, including customized reports from live data. | | |

|Graphical representations of data that is easy to consume for users. | | |

|Dash-boarding capabilities for various users within the system: learner, instructor, | | |

|administrator and supervisor. | | |

|Produce usage statistics reports that include minimally the number of courses taught, number of| | |

|learners in each course, number of instructors per semester, and file size of each course. | | |

|Course Management Administration | | |

|Registration Integration | | |

|Supports a full-range of student registration tools to add students to and drop students from | | |

|an online course. Administrators and/or instructors use registration tools but students also | | |

|use them when self-registration is available. | | |

|Course Management | | |

|The solution shall, at minimum, have the functionalities listed below: | | |

|Support for course management tools for the instructor to control the progression of an online | | |

|class through the course material. Support for creating and managing courses via an automated | | |

|method (e.g. CSV, API, Database) is required. | | |

|Course-level announcements. | | |

|Automatic notification of learners to important information such as add or drop confirmation, | | |

|changes of class meeting time and place, and uncompleted work. | | |

|Learner group management for discussions, assignments, projects, collaborative exercises. | | |

|Learner access and progress/activity tracking (e.g., login frequency, duration, course | | |

|activity, content accessed, tests completed, discussion participation), including instructor | | |

|access to all learner chat logs. | | |

|Ability to import/export learner management information in non-proprietary formats (such as | | |

|common spreadsheet data formats). | | |

|The ability to control the progression of a class or specify the date and duration of the | | |

|release of course content, resources, tests, discussions, etc. based on user, performance, or | | |

|other prerequisite criteria. | | |

|Conflict identification and resolution – multiple enrollments in the same coursework is | | |

|flagged, especially after successful completion by the participant. | | |

|Discussion Management | | |

|Support for forum discussion management including all of the accessing, assessing and | | |

|scheduling associated with running a discussion forum (see above) | | |

|Provisions for notifying learners of new communications and course changes. | | |

|Ability to moderate content of training, courses, and communities/chats. | | |

|Ability to share and solicit learning opportunities from peers and others, including | | |

|integration with social media technologies. | | |

|Ability to rate course and assignment content and provide comments. | | |

|Student Tracking | | |

|Supports student tracking by the instructor to track the usage of course materials by students | | |

|and to perform additional analysis and reporting, both of aggregate and individual usage. | | |

|Support for multiple types of questions. Flexible testing features shall include multiple | | |

|choice, true/false, matching, short essay, long essay, fill-in-the-blank questions, with the | | |

|capability for providing feedback. | | |

|Testing and Assessment | | |

|Test Questions | | |

|Supports a variety of question types, including adaptive testing, that support teaching and | | |

|learning of the Common Core State Standards. | | |

|Support for multiple types of questions. Flexible testing features shall include multiple | | |

|choice, true/false, matching, short essay, long essay, fill-in-the-blank questions, with the | | |

|capability for providing feedback. | | |

|Supports the ability to technologically enhance test questions where the user can interact with| | |

|the question, scenarios or testing environment. | | |

|ELD Standards, Career Technical Education Standards and all other California State Standards | | |

|shall be included so that test questions can be associated or aligned to various standards | | |

|where appropriate. | | |

|Automated Testing Support and Management | | |

|Supports automated testing and testing management including system services for importing and | | |

|exporting tests and test banks as well as statistical analysis of test results. Automated | | |

|testing management includes the control of when and where tests may be taken and under what | | |

|conditions | | |

|Provisions for test security, including restricting access, test release time and duration, as | | |

|well as the number of possible retakes. | | |

|Provisions for graded and ungraded testing and self-tests. | | |

|Ability to enhance tests with hyperlinks and multimedia elements such as imported still or | | |

|video images, audio, scientific notation, embedded equations, and other effects. | | |

|The ability to randomize quiz questions, to select test questions randomly from a test bank, | | |

|and to randomize possible answers (ABC) in multiple-choice questions. | | |

|Make test results immediately available to learners, if instructor wishes, with the potential | | |

|inclusion of prescriptive feedback on incorrect answers. | | |

|Provide for easy method of exporting test result data. | | |

|Reporting capabilities for various users on testing, assessments, and course evaluations. | | |

|Assessment Features | | |

|Capability for courses, content or resources to be evaluated, including the ability for users | | |

|to give courses, content, resources or collaboration spaces ratings that can be shared across | | |

|networks. | | |

|Make test results immediately available to learners, if instructor wishes, with the potential | | |

|inclusion of prescriptive feedback on incorrect answers. | | |

|Provide for graded and ungraded testing and self-tests. | | |

|Reporting Tools | | |

|Provides the ability to preview reports online, including customized reports from live data. | | |

|Provides graphical representations of data that is easy to consume for users; | | |

|Contains dash-boarding capabilities for various users within the system: learner, instructor, | | |

|administrator and supervisor. | | |

|Provides usage statistics reports that include minimally the number of courses taught, number | | |

|of learners in each course, number of instructors per semester, and file size of each course. | | |

|Online Marking Tools | | |

|Provides comprehensive online marking tools for the teacher to evaluate and mark student work | | |

|while online. | | |

|Online Grade Book | | |

|Provides a comprehensive online grade book for keeping track of student progress and work | | |

|online in support of assigning course grades. A rubric creation tool must also be provided. The| | |

|grade book must support integration with LAUSD’s student information system. | | |

|Administrator Management | | |

|The solution shall include high level system administration tasks, including: | | |

|Course creation and management including copying existing courses for a new semester and | | |

|automation of these processes. | | |

|Ability to edit and align courses to performance frameworks. | | |

|Targeted and global announcements and messaging. | | |

|Testing and Course Assessments | | |

|The solution shall, at minimum, possess test/quiz/survey and assessment features: | | |

|Capability for courses, content or resources to be evaluated, including the ability for users | | |

|to give courses, content, resources or collaboration spaces ratings that can be shared across | | |

|networks. | | |

|Ability to integrate courses and content sourced from the District and third party content | | |

|providers, including a list of publishers that have pre-configured course content available for| | |

|this LMS. | | |

|Course Content Development and Organization | | |

|The solution shall permit content to be loaded, created, shared, assessed, and modified. Some | | |

|examples, but not limited to, would be: | | |

|Creation of basic web content without requiring the knowledge of HTML/CSS or JavaScript coding.| | |

|Including but not limited to music, videos, mathematical and science symbols and notations, | | |

|presentations, foreign language support and spell check. | | |

|Alignment of course content to performance frameworks, as well as content to departmental | | |

|areas. | | |

|Ability to include dynamic media such as presentations, audio playback, animations or movies | | |

|embedded in the materials. | | |

|Copying, moving, and re-ordering content (to the document level) within a course and across | | |

|courses, including Sharable Content Object Reference Model (SCORM) and IMS Learning Tools | | |

|Interoperability (LTI) capabilities. | | |

|Easy import/export of various text word processing, graphic, and presentation formats (.txt. | | |

|doc, jpg, PowerPoin.ppt, .key, .pagest, Flash, PDF, etc.) and content objects. | | |

|Capability for participant work and course content to be archived in the LMS. | | |

|Security for the content management system(s). | | |

|Training and Support | | |

|No later than ten (10) business days following contract execution, Contractor shall provide a | | |

|detailed Training Plan that includes workshop descriptions, the timing as associated within the| | |

|Implementation Plan and ongoing recommendations for follow-up for successful launch of the | | |

|proposed LMS. | | |

|Training materials (for all roles - System administrator, LMS Administrator, Help Desk, Course | | |

|Designer, Learner, etc.), and the training formats available (print, web, Vendor delivered. | | |

|etc.). | | |

|LMS Product certification options, train-the-trainer materials. | | |

|Description of recommended amount of training for end users, administrators, Help Desk, and | | |

|support staff. | | |

|No later than ten (10) business days following contract execution, Contractor shall provide | | |

|contact information for all on-going support available on a 24-hour/7-day basis to both | | |

|technical staff and end-users including hot line or toll free numbers, day and time | | |

|availability, and any restrictions. | | |

|Help Availability | | |

|The contractor shall provide: | | |

|Professional development resources within the solution including, but not exclusive to, videos | | |

|demonstrations of effective classroom practice or other models of exemplary teaching in a | | |

|variety of grade levels and subjects areas. | | |

|Security | | |

|The Contractor shall provide a secure environment that ensures that all computerized files, | | |

|student information, human resources information and data are developed, used, and maintained | | |

|in a secure manner that will protect the confidentiality of all materials, records, and files. | | |

|This security environment must be approved by the LAUSD. The security system for all | | |

|information stored, transmitted or processed by the Contractor must comply with all applicable | | |

|District information security policies, including the District Acceptable Use Policy (Bulletin | | |

|999.7), the Information Protection Policy (Bulletin 1077.1), and the Security Standards for | | |

|Networked Computer Systems Housing Confidential Information (Bulletin 1553 and Reference Guide | | |

|1551). The above-reference documents are available below. Please click on the document name to| | |

|access the file. | | |

|Bulletin 999.8 | | |

|Bulletin 1077.1 | | |

|Bulletin 1553 | | |

|Reference Guide 3757.0 | | |

|Authentication, Role Management and Site Security | | |

|Ability to authenticate users against the District’s authentication systems (LDAP or Active | | |

|Directory authentication). | | |

|Ability to support SAML version 2.0 (Active Directory Federation Services 3.0). | | |

|Support for adding users to multiple roles and multiple contexts without requiring a user to | | |

|maintain multiple accounts. | | |

|Ability to automatically configure user role-based authorization using feeds from District SIS | | |

|and HR systems | | |

|Support encrypted authentication traffic | | |

|Platforms must be housed in data centers that provide disaster recovery/business continuity. | | |

|Platforms must be housed in data centers that meet District’s minimum requirements for | | |

|information security | | |

|Platform Configuration | | |

|Contractor will develop any Platform Configurations and submit for approval by the District in | | |

|accordance with this Statement of Work, which approval will not be unreasonably withheld or | | |

|delayed; provided, however, that it will not be unreasonable for the District to refuse to | | |

|approve any Platform Configuration that | | |

|Fails to provide the Contractor Platform in compliance with all District standards for the | | |

|security and confidentiality of District Confidential Information and District Protected | | |

|Information, or fails to provide for platform configuration of the Contractor Platform without | | |

|material disruption in the use or utility of the Contractor Platform to the District or its | | |

|users. | | |

|User ID Management | | |

|The parties will manage user identification (or “ID”) information by a collaborative process. | | |

|Hierarchical Security Levels | | |

|Contractor shall provide a hierarchical userID/role management utility to which only those | | |

|individuals designated by the District shall have access. Unless otherwise specified by the | | |

|District, the Contractor’s Platform will have eight (8) security levels, which (unless the | | |

|parties should agree otherwise) will be: District Administrator, Local Education Service Center| | |

|Administrator, Multiple Site Coach/Teacher Leader/Observer, School Administrator/Coach/Teacher | | |

|Leader/Observer, Teacher, Staff, Student and Parent. The foregoing security levels are listed | | |

|in order from highest to lowest in terms of access privileges. Access privileges are as | | |

|follows: District Administrators have access to all local districts (Educational Service | | |

|Centers) and all schools, employees, students and parents; Local District Administrators | | |

|(Educational Service Center Administrators) have access to all schools, employees, students | | |

|and parents within their local district; Multiple Site Coaches have access to certain specified| | |

|schools, employees and students which may or may not be within a single local district | | |

|(Educational Service Center); School Administrator/Coaches have access to all employees, | | |

|students and parents at that site; Teachers have access to their own data, students and | | |

|parents. Students have access to their own data and Parents have access to their Student’s | | |

|data. In order to account for magnet schools that may not have separate physical locations (but| | |

|do have different location codes), Multiple Site Coach and School Administrator/Coach level | | |

|users must be able to view employee and student results for all schools that share the same | | |

|physical location. The Contractor must accommodate Coaches/Teacher Leaders/Observers who are | | |

|also Teachers, in order for those Coaches/Teacher Leaders/Observers to see their own results as| | |

|well as the results for teachers and the students that they work with. | | |

|Provisioning of User IDs. Contractor shall provide all user IDs via an automated provisioning | | |

|system using data provided by the District in the Extract File. To the extent, the provisioning| | |

|of User IDs and access levels should be an automatic process based upon the user’s role. | | |

|Batch Entry System for Intermediate Level Accounts. Contractor shall develop and implement a | | |

|batch entry interface system for user ID creation that enables the District to create, modify, | | |

|delete and query multiple School, Local Educational Service Center and Central Office level | | |

|user accounts from a single interface in a single instance. The interface will confirm actions | | |

|via a mechanism approved by the District. | | |

|Hosting Requirements. The Contractor Platform is to be hosted in its entirety in physical | | |

|locations (see Section VII.b.v above) and approved in advance, in writing, by the District. Any| | |

|changes to the physical location of the hosting environment must be approved by the District at| | |

|least 30 days before any such change takes effect. In all cases the physical environment, | | |

|whether located at a site owned and operated by Contractor or at a commercial co-location | | |

|premises under contract with Contractor, must comply with all standards for physical security | | |

|of Protected Information as defined by District Reference Guide 1551. In addition, all hosting | | |

|and performance of the Contractor Platform will be in accordance with the standards set forth | | |

|in the Service Level Agreement. | | |

|Platform and Data Management | | |

|Platform Management | | |

|Contractor shall maintain the following configurations and add any features to the Contractor | | |

|Platform in accordance with this Statement of Work. All configurations will be subject to | | |

|acceptance testing in accordance with the terms of the Agreement, and each configuration | | |

|identified in this Section is a Critical Deliverable for purposes of the Agreement. The | | |

|configurations and additional features added to the Contractor Platform under this Section, as | | |

|well as by change order hereto are referred to collectively as the “Platform Configurations.” | | |

|For any enhancements that fall outside of the scope of the SOW, the Contractor and the District| | |

|will work together to develop a mutually agreed upon timeline and price. | | |

|Contractor shall deliver the following configurations per the Statement of Work: | | |

|Consistent Appearance and Functionality. Contractor shall revise all pages and reports on the | | |

|platform that are accessible to LAUSD users to ensure that appropriate terminology is used in | | |

|order to provide a message consistent with District initiatives. Contractor will also ensure | | |

|that navigation within the site will be clear and efficient through navigation bars, excluding | | |

|buttons or links that have no function in the District’s site within the Contractor’s platform.| | |

|District Data Integration. Contractor shall modify the Contractor Platform’s roster loading | | |

|functionality to accommodate the format of District data files and the inclusion of Filter | | |

|Data. The Contractor Platform will use the Filter Data to aggregate and filter Assessment data | | |

|in reports provided under this Statement of Work. Contractor may request reasonable | | |

|modifications to the District file formats to simplify the development of these tools. The | | |

|District will have the right to reject any request that places an unreasonable burden on | | |

|District resources, but will otherwise not unreasonably withhold approval. | | |

|District Data Consolidation. Contractor shall modify the Contractor Platform to ensure that | | |

|data from the District’s local educational service areas can also be merged into a single | | |

|district, to allow District users to run aggregate District-wide reports in addition to | | |

|aggregate local service area reports. Contractor shall add appropriate access control | | |

|mechanisms to ensure that local personnel only have access to local school district data and | | |

|District-wide aggregates with no local school district, school, or personally identifiable | | |

|data. District users with Local District and Central Office user ID levels will be able to run | | |

|reports by local school districts. Contractor will provide a user interface that allows a | | |

|designated District individual and/or a designated Contractor Account Manager to specify and | | |

|edit local school district information. | | |

|Data Management | | |

|The LAUSD Educator Growth and Development Cycle requires that a significant amount of data be | | |

|developed, maintained, and accessed by a wide variety of people involved in the full range of | | |

|activities. The data to be hosted, depending upon the platform selected, either on the | | |

|Contractor’s server(s) or on the LAUSD server(s), as designated and approved by the LAUSD, | | |

|covers the data produced by the full range of activities identified. | | |

|Data shall be available via web pages, secure file transfer protocol (SFTP), and restricted and| | |

|secure user logons. If possible, the secure user logons of any server housing any District | | |

|information shall authenticate against an LDAP V3 compliant user Directory housed on the | | |

|District’s network. User account authorization provisioning shall occur within the Contractor | | |

|provided application(s). Availability shall be encrypted at the discretion of the LAUSD | | |

|commensurate to the confidentiality of the information hosted on the system. Any student level | | |

|data shall be maintained in a secure and confidential manner approved by the District. | | |

|Notwithstanding any of the above specifications, the security of all confidential data shall | | |

|meet all District standards and policies. | | |

|Databases and Applications | | |

|The Contractor shall maintain and administer databases for data captured by the Contractor | | |

|Platform and for other displayed within the Contractor Platform. Any databases and | | |

|applications proposed by the Contractor must be approved by the LAUSD. | | |

|The Contractor shall coordinate with the LAUSD to ensure consistency with the database and | | |

|application environment. | | |

|Record Layout and Data Dictionary. For every data processing system and every data element | | |

|captured by or displayed in the Contractor Platform, the Contractor shall establish and | | |

|maintain a record layout and data dictionary. The data dictionary shall include the names and | | |

|descriptions of every data element in the processing system. | | |

|Design and Usability Requirements | | |

|Configurable Look and Feel | | |

|Provides an interface for the capability to change the graphics, text and how a course looks. | | |

|This also includes the ability to institutionally brand courses. | | |

|Course Content Development and Organization | | |

|Alignment of course content to performance frameworks, as well as content to departmental | | |

|areas. | | |

|Capability for participant work and course content to be archived in the LMS. | | |

|Instructional Design Tools | | |

|Provides instructional design tools that do not require “coding” skills by the instructor. | | |

|Instructional design tools help instructors create learning sequences, for example, with lesson| | |

|templates or wizards (e.g. an integrated WYSIWYG editor). | | |

|Alignment and Mapping | | |

|Provides content, as part of the LMS solution, be mapped to multiple performance frameworks, | | |

|including the Common Core State Standards, as well as one or more programs within the District.| | |

|This alignment shall include; | | |

|Automatic recommendation of learning content and tracking of progress based on the learner’s | | |

|performance. | | |

|A clear process to manage this alignment of resources and coursework within the system. | | |

|Usability Requirements | | |

|The Learning Management System shall possess features to ensure that it is easy for teachers, | | |

|instructors, administrators, and learners to use (see also Accessibility Section IV). It shall | | |

|also address the following specific areas: | | |

|Provide for printing of content pages. | | |

|Provide support materials, such as help manuals, contextual help for user screens, tutorials, | | |

|and online resources that are available to assist both learners in the use of the platform and | | |

|instructors/developers in the creation and management of courses. | | |

|Learner-Centered Features | | |

|The solution shall possess learner-centered features such as: | | |

|Support for learner e-portfolios. Ability for students and teachers to store personal work | | |

|online with any time/anywhere capabilities and beyond school year. | | |

|Integration to Microsoft OneDrive and Google Drive cloud storage. Integration to Microsoft | | |

|OneDrive and Google Drive cloud storage via interface with the ability to open, edit, save, and| | |

|modify documents. | | |

|Ability to customize primary learner account page. | | |

|Ability for learning recommendations to be generated based on data sources (e.g., performance | | |

|data), supervisor suggestions, etc. | | |

|Search capabilities based on framework competencies, role, etc. | | |

|Ability for learners, instructors, or system administrator to create working groups of learners| | |

|within a course and across courses. | | |

|The ability for learners to review how much course content they have accessed. | | |

|Capability for third party learner portal or learner-centered feature systems with which the | | |

|LMS integrates. | | |

|Compatibility | | |

|File Exchange | | |

|Supports file uploading and attachment. File exchange tools allow learners to upload files from| | |

|their local computers and share these files with instructors or other students in an online | | |

|course. File attachments the system must support include; .pdf, .doc, .ppt, .xls, .key, | | |

|.numbers, .pages and are also required in the Discussion Forum requirement (see above). | | |

| Web Browser Compatibility | | |

|Support for web browsers such as Internet Explorer, Firefox; Safari, Chrome, and Opera, on both| | |

|the Microsoft OS and Mac OS as well as support for tablets running Windows 8, Android OS, or | | |

|iOS. | | |

|Content Interchange | | |

|Must be SCORM and IMS Learning Tools Interoperability (LTI) compliant | | |

|System itself must maintain an agnostic approach to incorporating online and pre-loaded | | |

|instructional content as well as learning management, evaluation and communications systems | | |

|that may be available from other providers including the District. | | |

|Content Migration | | |

|Support for the conversion and import of existing courses from the District’s current LMS | | |

|(MOODLE 1.9) to the new LMS. | | |

|Emerging Technologies | | |

|Support for instructional media content designed to work on tablets running Microsoft OS, | | |

|Android or iOS. | | |

|E-mail, Web-conferencing and District-housed Applications | | |

|Supports and incorporates an externally provided student and teacher e-mail system (currently | | |

|the education version of GOOGLE Mail and Office 365), Web conferencing systems (currently | | |

|WebEx, Elluminate and Blackboard Collaborate), and other District-housed applications including| | |

|the Parent Portal communications and MyData systems. | | |

|Multi-Language Support | | |

|Support for displaying and creating content in languages other than English, such as French, | | |

|German, Arabic and Spanish, as well as Unicode support. | | |

|Multimedia Repository | | |

|Supports a teacher or course creator seamlessly integrating content into courses from various | | |

|external and internal sources using a single, unified graphical repository interface. | | |

|Multimedia Content Integration | | |

|Support for playing common multimedia files (e.g. MP3, MP4, FLV) directly from and within a | | |

|course object. | | |

|Ability to embed and play streaming videos within LMS pages and activities. | | |

|Accessibility | | |

|All LMS deliverables shall comply with the applicable technical and functional performance | | |

|criteria of Section 508 unless exempt. Accessibility compliance means meeting the standards | | |

|that allow people with disabilities to access information online. For example, the blind use a | | |

|device called a screen reader to read the screen but Web pages need to be designed so that | | |

|screen readers can navigate it easily. | | |

|To be considered for award, the proposed Learning Management System and all applicable | | |

|components must meet the applicable standards and provisions of the Architectural and | | |

|Transportation Barriers Compliance Board (the "Access Board"), an independent federal agency | | |

|whose primary mission is to promote accessibility for individuals with disabilities. These | | |

|standards are codified as 36 CFR Part 1194 and may be accessed through the Access Board’s web | | |

|site at applicable standards and provisions of most systems | | |

|will be covered by sections 1194.21 and 1194.22. | | |

|§1194.21 Software Applications and Operating Systems, applies to all EIT software applications | | |

|and operating systems procured or developed under this work statement including but not limited| | |

|to “general off the shelf” and “customized off the shelf” software. In addition, this standard | | |

|is to be applied to Web-based applications when needed to fulfill the functional performance | | |

|criteria. | | |

|§1194.22 Web-based Intranet and Internet Information and Applications, applies to all Web-based| | |

|deliverables, including documentation and reports procured or developed under this work | | |

|statement. When any Web application uses a dynamic (non-static) interface, embeds custom user | | |

|control(s), embeds video or multimedia, uses proprietary or technical approaches such as, but | | |

|not limited to, Flash or asynchronous Javascript and XML (AJAX) then Section 1194.21 software | | |

|standards also apply to fulfill functional performance criteria. | | |

|Alternatively, proposals may contain components or services that provide equivalent | | |

|facilitation. Such offers will be considered to have met the provisions of the Access Board’s | | |

|standards for the feature or component providing equivalent facilitation. | | |

|Interface and Identity Management | | |

|Interface Files | | |

|The District uses six (6) master files for system integration purposes. There is a data file, | | |

|a record count file and an error file created for each of the 6 master files. A is | | |

|added as a prefix to the file name to insure the consistency between the file. A data | | |

|dictionary for each of these file types is provided as an Attachment H. Proposers must be | | |

|capable of Utilizing these files in the format described, effective 30 days from the execution | | |

|date of contract and/or purchase order. These files are provided to vendors on a nightly basis.| | |

|See the table below for the naming conventions of the 6 master files by type. | | |

|Identity Store and Management | | |

|The District’s identity store and identity management platform is in transition. Please consult| | |

|the Binding Document Los Angeles Unified School District OID Integration (Attachment I). | | |

|At a minimum, an application must be able to support the following within 30 days from the | | |

|execution date of contract and/or purchase order: | | |

|Dual identity stores – Oracle Internet Directory (OID) and Windows Active Directory. | | |

|Multiple Lightweight Directory Access Protocol (LDAP) Search Base paths. Minimum LDAP version | | |

|3. | | |

|Must support, at a minimum, Windows Server 2003 Active Directory and the ability to leverage | | |

|the District’s end state of Windows 2012 Active Directory. | | |

|Must support the District’s current level of OID. Must support the District’s current level of| | |

|OID, LDAP v3. Standard LDAP APIs may be used to bind OID to retrieve user information. OID is| | |

|setup to allow authenticated and anonymous bids. Must support SSL binds to OID. Binding | | |

|should support TCP ports: 389, 636, 3131, 3060. | | |

|The new identity management platform will incorporate Active Directory Federation Services 3.0 | | |

|(ADFS) SAML v2.0 in place of OID. | | |

|Must be able to support ADFS SAML v2.0 once implemented. | | |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download